HTTP 402 payments on Canton

Settle machine-to-machine access with non-custodial verification and Canton-native settlement. Deploy the payer client on your infrastructure, or register your APIs to accept x402, both through one facilitator.

Get started

Choose your integration path

Coming soon

Integration paths launch soon

Payer SDK and merchant portal access unlock on launch day. Countdown below.

00 Days

00 Hours

00 Mins

00 Secs

Payer infrastructure

Set up as a payer

Run our SDK on your premises to discover holdings, obtain transfer context, prepare transactions on your participant, and sign x402 payment payloads, without exposing private keys to the facilitator.

Install the Canton x402 client SDK
Connect to your ledger API and signing keys
Point at this facilitator for verify and settle

View SDK on GitHub →

Merchant onboarding

Register as a merchant

Gate APIs behind HTTP 402, issue payment quotes, and settle incoming x402 payments through the facilitator. Configure pricing, monitor settlements, and manage API credentials from the merchant portal.

Create your merchant profile and Canton party
Configure resources, pricing, and API keys
Integrate x402 middleware on your endpoints

Open merchant portal →

01

Non-custodial

Payers sign on their own participant. The facilitator verifies and executes; it never holds payer keys or selects UTXOs on their behalf.

02

Canton-native

Settlement uses Splice Token Standard transfer factories on Canton Network, with disclosed contracts and interactive submission.

03

Standards-aligned

Built on the x402 v2 wire format: payment quotes in 402 responses, signed payloads in X-PAYMENT, facilitator verify and settle.

Transaction lifecycle

From gated request to settled access

One HTTP retry carries the signed payment. Custody stays on the client; the facilitator verifies and settles on Canton.