Coinbase transferred x402 to the Linux Foundation. Stripe, Visa, Mastercard, Google, AWS, and Cloudflare are founding members. The protocol turns HTTP into a payment rail for AI agents using stablecoins. No checkout page. No card number. No human.

The internet was supposed to have a payment layer from the start. HTTP status code 402, "Payment Required," has been sitting in the spec since 1997, reserved for future use. Twenty-nine years of future use. Today, Coinbase and the Linux Foundation announced the x402 Foundation, and that dormant status code just became the most important three digits in payments.

The founding coalition reads like someone merged the attendee lists of Money20/20 and re:Invent into a single org chart. Stripe, Visa, Mastercard, American Express, Google, AWS, Microsoft, Cloudflare, Shopify, Circle, and Polygon Labs are all in.

We first covered x402 in depth when Coinbase was still building it internally. What happened today changes the calculus completely.

Strip away the jargon and x402 does something surprisingly simple. When a machine hits a resource that costs money, the server returns an HTTP 402 response. That response contains a standardised payment request: how much, which token, which address. The client settles via a pre-authorised wallet. The server verifies the transaction on-chain. The resource unlocks.

No checkout page. No card number entry. No redirect to a payment processor. No human clicking "confirm."

The protocol uses stablecoins and ERC-20 tokens as the settlement layer. It launched on Base, Coinbase's Layer 2 network, but is designed to be blockchain-agnostic. Cloudflare already has its Agents SDK supporting live transactions on the Base Sepolia testnet using USDC. This is not theoretical. x402 has processed over 15 million transactions on Base already.

Here is the thing. Card networks were built for a world where a human pulls out a piece of plastic and a merchant terminal reads it. That model breaks when the "customer" is a software agent making 400 API calls per second, each costing a fraction of a cent. Try running a $0.0003 transaction through Visa's rails. You cannot. The interchange floor alone would eat the entire payment.

Protocols are cheap. Coalitions are not.

Coinbase could have kept x402 proprietary. They built it, they ran it on their own L2, and it was already processing millions of transactions. Instead they handed the intellectual property to the Linux Foundation and invited every company that should, in theory, want to kill it.

Look at that founding list again. Visa and Mastercard are founding members of a protocol that routes payments around card rails. Stripe is backing a standard that settles on blockchain instead of through traditional acquiring. AWS and Google are endorsing a payment mechanism baked into the HTTP layer of the web they host.

None of these companies are doing charity work. They are placing a hedge. If agentic commerce scales the way the industry expects, the volume of machine-to-machine transactions will dwarf human commerce within a decade. The card networks would rather be inside the tent shaping the rules than outside watching a new rail eat their lunch.

The Linux Foundation governance model is the glue that makes this coalition possible. No single company controls the spec. That is the same structure that gave us Linux, Kubernetes, and Node.js. Corporate rivals can collaborate on shared infrastructure because the foundation acts as neutral ground.

x402 does not exist in isolation. It is one piece of a three-protocol stack that is emerging for agent commerce.

Google's AP2 (Agents-to-Payments) protocol handles governance, authorization, and auditing. Who is this agent? What is it allowed to spend? Who is liable when it overpays? AP2 answers those questions.

Stripe's ACP (Agent Commerce Protocol) adapts existing payment infrastructure to agent workflows. It is the bridge layer, letting agents interact with merchants who still run on traditional rails.

x402 sits underneath both. It is the settlement primitive. The moment money actually moves.

Think of it as a layer cake. ACP at the top handles the commercial logic. AP2 in the middle handles trust and compliance. x402 at the bottom handles value transfer. Each protocol does one job. Together they give an AI agent everything it needs to discover, negotiate, pay for, and receive a service without a human ever knowing it happened.

Nearly 80 percent of surveyed acquirers reported being "at least somewhat prepared" to support seamless omnichannel shopping for agentic commerce. The infrastructure providers are not waiting for demand. They are building ahead of it.

We need to be direct about what is happening here. The payments industry just endorsed a settlement layer that does not need the payments industry.

Stablecoin settlement on a public blockchain is faster, cheaper, and more programmable than card-based settlement. x402 makes that settlement native to HTTP. Every web server, every API endpoint, every cloud function can now accept payment as a first-class protocol feature, the same way they accept authentication headers today.

That does not mean card networks disappear. Human consumers still want the fraud protection, the rewards points, the chargeback rights that come with a Visa or Mastercard. But agents do not care about airline miles. Agents need speed, programmability, and the ability to transact at sub-cent amounts thousands of times per second.

The real question is not whether x402 works. It already works. Fifteen million transactions prove that. The question is whether the governance structure holds. Open-source foundations can fracture. Corporate members can fork. Standards can stall in committee while the market moves on.

But the signal from today is unambiguous. When Visa, Mastercard, Stripe, Google, AWS, and Cloudflare all agree to sit at the same table and build a blockchain-based payment rail together, something fundamental has shifted. The internet is getting the payment layer it was promised in 1997. It just took AI agents to finally make it necessary.

The internet has had a "Payment Required" status code for nearly three decades. Now it finally has a protocol to back it up. The question is: when your AI agent starts settling transactions on-chain without asking you, will you even notice?