Payment Requirements
The machine-readable description of what a resource server demands for access - chain, asset, amount, recipient, facilitator, and expiry.
Related terms
- x402 - An open payment protocol built on top of HTTP 402 that lets servers demand stablecoin payment before serving a resource, and lets clients (i
- HTTP 402 - The reserved HTTP status code 'Payment Required' first defined in RFC 2068 (1997), carried forward in RFC 2616 and RFC 7231, and revived as
- Payment Proof - A signed payment payload submitted with a retried HTTP request authorising the facilitator to settle the required amount on the client's beh
Recent stories
PROTOCOL
- x402 by Coinbase goes live on Arbitrum mainnet - CDP facilitator now covers a fifth chain alongside Base, Polygon, World and Solana · phemex.com
- Jesse Pollak ships batched settlement on x402 - ERC-20 escrow + offchain signed vouchers unlock sub-$0.0001 per-request pricing, directly answering the per-request-settlement bear case · cointelegraph.com
- TACEO ships Confidential x402 on Base Sepolia - 3-party MPC + zk-proofs make every payment private at ~300k gas, 8x cheaper than heavyweight ZK alternatives · finextra.com
- Coinbase Q1 call: 99% of x402 settled in USDC, 90% of agentic stablecoin volume on Base - Choi calls x402 'the open standard for the next wave of agentic commerce' · theglobeandmail.com
- Circle ships Nanopayments on mainnet - gas-free USDC down to $0.000001 across 11 chains, fully x402 v2 compatible · circle.com