Version 2 of x402 moved the payment terms into headers and switched to standard chain identifiers. Most of the changes are names, but a client built for one version can fail on the other.
| v1 | v2 | |
|---|---|---|
| 402 terms | JSON body, accepts | PAYMENT-REQUIRED header |
| Payment header | X-PAYMENT | PAYMENT-SIGNATURE |
| Receipt header | X-PAYMENT-RESPONSE | PAYMENT-RESPONSE |
| Network | base | eip155:8453 (CAIP-2) |
| Amount field | maxAmountRequired | amount |
A current v2 client reads the header and expects CAIP-2 networks. A seller that only speaks v1 can look fine in a browser and still be unpayable by that client. Our public probe-pass grade treats v1-only as a fail for exactly that reason.
Many sellers send the v2 header and keep a v1-shaped body for older clients. That is fine as long as the two carry the same terms. Our facilitator accepts both: base in v1 and eip155:8453 in v2.
Many facilitators, including ours, still accept v1 payments on Base, but new clients target v2.
A chain-agnostic way to name a blockchain network: eip155:8453 is Base mainnet, and solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp is Solana mainnet.
No. It is not part of the x402 specification. The price lives in the payment requirements.