Carried forward from v1
- Shared types independent of transport and scheme.
- Facilitator verify and settle as the default settlement path.
- Scheme plug-ins (exact remains the baseline).
- Transport-agnostic response semantics: success, payment required, invalid request, server error.
What v2 adds
- Structured resource metadata (URL, description, tags, icons) on payment required responses.
- More payment schemes in one deployment: exact, upto, batch settlement, auth capture, and others documented under payment schemes.
- HTTP v2 wire signaling (PAYMENT-REQUIRED and PAYMENT-SIGNATURE headers) in transport specs.
- An extensions object for optional capabilities such as discovery, sign-in, gas sponsoring, and builder attribution.
- Payment flow models beyond authorize-then-settle when a scheme declares them.
Highlighting Request
Request
Wallet, agent, or app that selects an offer and signs payment.
Same request → 402 → pay → settle rhythm as v1.
Same request → 402 → pay → settle rhythm as v1.
Same request → 402 → pay → settle rhythm as v1.
Sells access and publishes payment requirements.
Same request → 402 → pay → settle rhythm as v1.
Verifies signatures and submits chain transactions on behalf of merchants.
402
Wallet, agent, or app that selects an offer and signs payment.
HTTP v2 wire signaling uses PAYMENT-REQUIRED. An extensions object carries optional capabilities.
HTTP v2 wire signaling uses PAYMENT-REQUIRED. An extensions object carries optional capabilities.
HTTP v2 wire signaling uses PAYMENT-REQUIRED. An extensions object carries optional capabilities.
HTTP v2 wire signaling uses PAYMENT-REQUIRED. An extensions object carries optional capabilities.
HTTP v2 wire signaling uses PAYMENT-REQUIRED. An extensions object carries optional capabilities.
HTTP v2 wire signaling uses PAYMENT-REQUIRED. An extensions object carries optional capabilities.
HTTP v2 wire signaling uses PAYMENT-REQUIRED. An extensions object carries optional capabilities.
HTTP v2 wire signaling uses PAYMENT-REQUIRED. An extensions object carries optional capabilities.
{ "x402Version": 2 }Sells access and publishes payment requirements.
HTTP v2 wire signaling uses PAYMENT-REQUIRED. An extensions object carries optional capabilities.
Verifies signatures and submits chain transactions on behalf of merchants.
Pay and retry
Wallet, agent, or app that selects an offer and signs payment.
The retry carries PAYMENT-SIGNATURE.
The retry carries PAYMENT-SIGNATURE.
The retry carries PAYMENT-SIGNATURE.
Sells access and publishes payment requirements.
The retry carries PAYMENT-SIGNATURE.
Verifies signatures and submits chain transactions on behalf of merchants.
Verify
Wallet, agent, or app that selects an offer and signs payment.
Sells access and publishes payment requirements.
Facilitator verify and settle stay the default settlement path.
Facilitator verify and settle stay the default settlement path.
Facilitator verify and settle stay the default settlement path.
Verifies signatures and submits chain transactions on behalf of merchants.
Facilitator verify and settle stay the default settlement path.
Settle
Wallet, agent, or app that selects an offer and signs payment.
Sells access and publishes payment requirements.
Facilitator verify and settle stay the default settlement path.
Facilitator verify and settle stay the default settlement path.
Facilitator verify and settle stay the default settlement path.
Verifies signatures and submits chain transactions on behalf of merchants.
Facilitator verify and settle stay the default settlement path.
Response
Wallet, agent, or app that selects an offer and signs payment.
Success returns the resource. Payment schemes decide how value moves.
Success returns the resource. Payment schemes decide how value moves.
Success returns the resource. Payment schemes decide how value moves.
Sells access and publishes payment requirements.
Success returns the resource. Payment schemes decide how value moves.
Verifies signatures and submits chain transactions on behalf of merchants.
How to read the spec
Read the overview and core types first, then the facilitator interface, then the payment scheme that matches your chain. Pair the core document with the v2 transport spec for your wire format and the scheme specs for on-chain logic.
On this site
Payment schemes explains how value moves with visualizers. Extensions summarizes optional capabilities, including CDP Bazaar discovery.
