batch-settlement

batch-settlement is an x402 scheme for many small payments between one payer and one payee. Instead of settling every request on-chain, the payer locks funds in an on-chain escrow channel, then issues signed off-chain vouchers — one per paid request. The payee redeems accumulated vouchers in a single on-chain claim. Thousands of sub-cent requests become one transaction.

Operation lifecycle

A batch-settlement payment payload carries a type field that selects one of four on-chain operations:

1. deposit — the payer funds the escrow channel. The channel’s identity commits to its configuration (channelConfig), including the payer and the authorizer address below.
2. claim — the payee redeems a set of vouchers in one transaction. Each voucher represents one paid request; the payload’s claims array carries them.
3. settle — closes out the channel balance.
4. refund — returns unclaimed funds to the payer.

All four operations flow through the same /verify and /settle endpoints as any other scheme — the type field does the multiplexing. x402 client SDKs construct these payloads; see the @x402/evm package for the channel and voucher wire formats.

The receiver authorizer

For batch-settlement kinds, GET /supported advertises an extra.receiverAuthorizer — an EIP-712 signing address operated by Solvador that co-signs claim and refund messages. The authorizer address is committed into each channel’s identity at deposit time, so clients must use the address currently advertised in /supported when opening a channel.

Billing units

Availability

batch-settlement is registered on all 11 EVM networks. Settlement executes on chains where the canonical x402 batch-settlement contract is deployed (a deterministic CREATE2 deployment, so it has the same address on every chain that has it).