x402 Explained: HTTP 402 for Machine-Native Payments

x402 is Coinbase’s open protocol that revives the long-dormant HTTP 402 “Payment Required” status so that software can pay for resources programmatically, typically with stablecoins, in amounts and at frequencies that card rails handle poorly. It is not a consumer-checkout protocol. It sits at the settlement layer and exists for software paying software: an agent paying for an API call, compute, data, or content.

How payment flows

The mechanism is the elegant part. A client requests a resource from a service; the service responds with a 402 and a payment requirement; the client pays; and a facilitator verifies and settles the payment on-chain on the merchant’s behalf before the resource is delivered. The facilitator model is what makes x402 practical: the merchant does not have to run blockchain infrastructure itself, it relies on the facilitator to verify and settle. Settlement is in stablecoins such as USDC, which suits micro-transactions and per-call billing where traditional rails are too slow or too expensive.

Who is behind it

x402 comes from Coinbase, and is crypto-native by design. Coinbase and Cloudflare announced their intent to form an x402 Foundation in September 2025 to steward the protocol, and it moved under the Linux Foundation in 2026, giving it neutral, multi-party governance. That early move to a foundation is a familiar pattern: the crypto-native standard leans on neutral stewardship sooner, while provider-backed standards often start under their sponsors.

In mid-2026 the protocol gained meaningful infrastructure backing. AWS made x402 settlement generally available at the edge through CloudFront and AWS WAF, and Cloudflare opened a waitlist for a Monetization Gateway that lets sites charge for pages, APIs, datasets, or MCP tools via x402, both settling in stablecoins (primarily USDC) through Coinbase’s facilitator. Then, on July 14, 2026, the Linux Foundation announced the operational launch of the x402 Foundation under formal, open governance, with Coinbase’s contribution of the protocol complete and 40 members on board. The premier tier is striking for a crypto-native rail: it now spans the major card networks and payment providers (Visa, Mastercard, American Express, Stripe, Adyen, Fiserv), platforms (Google, Shopify, AWS, Cloudflare), and crypto infrastructure (Coinbase, Circle, Ripple, and the Solana and Stellar foundations). Two hyperscalers enforcing the same payment protocol at the edge, and every major card network signing on to help govern it, is a signal that agent-to-service micropayments are moving from concept to infrastructure, though open questions remain around tax, invoicing, and how sellers distinguish paying agents from ordinary traffic.

The handover is now visible in the code as well as the governance. The canonical repository is github.com/x402-foundation/x402; Coinbase’s original coinbase/x402 repository was moved under the Foundation, with issues and pull requests transferred, and now serves as a development fork. The published documentation moved with it, to docs.x402.org. Worth noting alongside the stablecoin framing: the project’s own principles describe x402 as network, token, and currency agnostic, and the Linux Foundation describes it as supporting “payment types ranging from traditional cards to stablecoins.” Stablecoins are current practice, not a limit written into the specification.

Where it sits in the stack

x402 is one of two machine-native settlement standards, alongside MPP. Both build on HTTP 402 and target the same agent-to-agent and micro-transaction use cases; the difference is sponsorship and rails, and Stripe supports both. For a side-by-side, see x402 vs MPP.

It also connects to the authorization layer. An A2A x402 extension, built by Google with Coinbase, the Ethereum Foundation, and MetaMask, brings x402-style stablecoin payments to the A2A agent-to-agent protocol, which is how AP2 composes with crypto settlement. So x402 handles the money movement, while AP2 and A2A handle authorization and coordination around it. For the full map, see the protocol stack.

FAQ

What is x402? Coinbase’s open protocol reviving HTTP 402 so software can pay for resources programmatically, typically in stablecoins. It is a settlement-layer standard for machine-to-machine and micro-transaction use cases.

How does payment work? A 402 response carries a payment requirement, the client pays, and a facilitator verifies and settles on-chain before the resource is delivered, so the merchant needs no blockchain infrastructure of its own.

How is it different from MPP? Both are HTTP 402-based settlement standards. x402 is Coinbase’s stablecoin-focused, on-chain protocol; MPP is Stripe and Tempo’s, settling in stablecoins as well as cards and BNPL through Stripe. Stripe supports both.