Ask402

What are x402 payment schemes (exact, upto and the rest)?

Short answer

A scheme is the rule for how a payment is made. "exact" pays a fixed amount and is by far the most common. "upto" authorizes a maximum and the seller charges what was actually used. "batch-settlement" pays many small amounts off-chain and settles them together. "auth-capture" places a hold that can be captured, voided or refunded.

The four schemes

SchemeWhat it doesGood forWhere it works today
exactPays one fixed amountA lookup, a search, a file: anything with a known priceWidely. Specified for 18 network families
uptoBuyer authorizes a ceiling, seller settles the actual cost, onceModel calls and other work whose cost is only known afterwardsEVM (through Permit2) and Solana
batch-settlementBuyer funds an escrow or channel and signs small vouchers that are redeemed togetherVery many tiny payments, where a transaction per call would cost too muchEVM and Solana in the SDKs
auth-capturePlaces a hold that the seller can capture, void or refundPurchases that may be cancelled or adjustedSpecified for EVM only, in the TypeScript and Go SDKs

Each offer in a 402 reply names its scheme in the scheme field. A server can offer the same resource under more than one.

Not every facilitator handles every scheme. Coinbase's CDP facilitator, for example, lists exact, upto and batch-settlement.

How "exact" works on EVM chains

The buyer signs a message authorizing a transfer of a specific amount to a specific address, valid for a short time window, with a one-time number so it cannot be replayed. No transaction is sent by the buyer. The facilitator submits it and pays the gas.

There are three ways the transfer can be authorized:

  • EIP-3009 (the default). The token itself supports signed transfers. USDC does.
  • Permit2. For tokens without EIP-3009. It needs a one-time approval first.
  • ERC-7710. Delegation from a smart account.

With exact, the amount must match the price exactly. Paying more than the price fails, the same as paying less.

How "exact" works on Solana

The buyer builds a token transfer transaction and signs their part of it. A sponsor named in the offer adds the fee-payer signature and submits it. The buyer does not need SOL for fees.

When the money moves

Version 2 also names three payment flows, which describe the order of events:

  • authorization (the default): verify the payment, deliver the resource, then settle.
  • upfront: settle first, then deliver.
  • escrow: settle into escrow, deliver, then settle the final amount.

What about "deferred"?

A deferred scheme was proposed in 2025 and is mentioned as an example in the version 1 specification, but there is no scheme by that name in the repository today. Payments that settle later are handled by batch-settlement.

Sources

Facts checked against these sources on . Protocols change, so the official specification wins if it disagrees with this page. Read this page as Markdown.

Who writes this. Ask402 is published by Havok Holdings LLC, which also runs Agent402, one of the x402 services covered here. Agent402 is labelled wherever it appears. Everything else is described from each project’s own documentation, and nobody pays to be listed.