The x402 Foundation: Why Visa, Google, and Stripe Are Building the Internet's Payment Layer

On April 2, 2026, the Linux Foundation launched the x402 Foundation at the MCP Dev Summit in New York. Coinbase contributed the x402 protocol it created, and twenty-two of the biggest names in payments, cloud, and fintech signed on as founding members. This is not another crypto consortium. It is the first credible attempt to give the internet a native payment layer, and it is happening because AI agents need one.

What the x402 Foundation Actually Is

The x402 Foundation is a nonprofit governed by the Linux Foundation. Its job is to steward the x402 protocol, an open standard that embeds payments directly into HTTP requests. When a client requests a resource, the server responds with HTTP 402 "Payment Required" and a price. The client pays and retries. The whole exchange happens in standard HTTP headers with no redirects, no accounts, no human clicking "Buy Now."

The foundation launched with Coinbase and Cloudflare as co-founders, with Stripe as a founding participant. Twenty-two organizations signed on at launch: Adyen, Amazon Web Services, American Express, Ampersend.ai, Base, Circle, Cloudflare, Coinbase, Fiserv Merchant Solutions, Google, KakaoPay, Mastercard, Merit Systems, Microsoft, Polygon Labs, PPRO, Shopify, Sierra, Solana Foundation, Stripe, thirdweb, and Visa.

Jim Zemlin, CEO of the Linux Foundation, framed it plainly: "The x402 Foundation will create an open, community-governed home to develop these capabilities in the open, ensuring they evolve with transparency, interoperability, and broad participation across the ecosystem."

Why This Matters Now

The internet has never had a payment layer. Every transaction requires an account, a form, a payment processor, and a human in the loop. That architecture works fine when people are buying things. It breaks down entirely when software needs to buy things.

AI agents are already consuming APIs, purchasing compute, and paying for data feeds. The old model of "sign up, enter a credit card, accept the terms" adds seconds of latency and requires human identity verification at every step. For an agent making hundreds of micro-transactions per hour, that friction is a hard wall.

x402 solves this by making payment a standard part of HTTP. No accounts. No redirects. No human confirmation. The agent requests a resource, gets a price, signs a transaction with its wallet, and receives the resource. The entire flow happens within normal HTTP request and response cycles.

Shan Aggarwal, Chief Business Officer at Coinbase, described the vision: "x402 moves us toward a more open financial system where sending value online is as simple as sending an email. By backing the x402 Foundation, we're helping build the native payment layer the internet has never had, one that's global, programmable, and always on."

The x402 Protocol in 90 Seconds

x402 works by repurposing the HTTP 402 status code, which has existed since HTTP/1.1 but sat dormant for nearly thirty years. Here is the flow:

1. A client (browser, app, or AI agent) requests a resource from a server.
2. The server responds with 402 Payment Required and a PAYMENT-REQUIRED header containing the price, accepted payment methods, and a payment address.
3. The client signs a payment authorization with its wallet and retries the request with a PAYMENT-SIGNATURE header.
4. The server verifies the payment through a facilitator (a service that settles the transaction on-chain) and returns the resource with a PAYMENT-RESPONSE header.

The entire exchange uses standard HTTP. SDKs simplify integration, but the protocol is HTTP-native. Any HTTP client can participate.

V2: From Prototype to Production Standard

x402 launched in May 2025 as a simple idea. By December 2025, it had processed over 100 million payments. V2 shipped on December 11, 2025, addressing six months of production learnings.

The key upgrades in V2:

Unified payment interface. V2 uses CAIP standards (Chain Agnostic Improvement Proposals) to identify networks and assets. This means one payment format works across Base, Solana, Polygon, and any new L2, with no custom logic. Legacy rails like ACH, SEPA, and card networks fit the same model through facilitators.

Dynamic pay-to routing. Per-request routing to different addresses, roles, or callback-based payout logic. This enables marketplaces and multi-tenant APIs where each request flows to a different recipient.

Wallet-based access and reusable sessions. Instead of paying on every call, agents can prove wallet ownership once and get session tokens for repeated access. This cuts latency and transaction costs for high-frequency use cases.

Plugin-driven architecture. Adding a new chain, payment scheme, or facilitator is a standalone package. No changes to the core spec or reference SDK.

The Numbers Behind the Narrative

The x402 ecosystem has real traction, though the numbers warrant careful reading.

According to industry analysis, cumulative agentic transactions have exceeded 140 million, with annualized volume north of $600 million as of early 2026. Solana alone has processed over 35 million transactions and $10 million in volume since x402 launched on the network, according to the Solana Foundation.

Artemis Analytics data from March 2026 shows average daily transaction volume of approximately $28,000, with an average transaction size of about $0.20. Some analysis suggests that roughly half of early transaction volume may be test or synthetic activity. The protocol is functional and growing, but the commercial use case is still in its earliest innings.

The Solana Foundation has reported that Solana drives nearly 65% of x402 transaction volume. Base and other EVM chains account for the remainder.

Who Is Building on x402

The ecosystem page on x402.org lists integrations across cloud, payments, and AI infrastructure:

Cloud and infrastructure. AWS supports x402 for machine-to-machine payments. Cloudflare provides native x402 support in Cloudflare Workers and AI Agents, enabling serverless HTTP payment flows at the edge.

Payments. Stripe is integrating x402 so businesses can accept payments from agents at scale. Adyen joined to ensure merchant outcomes stay front and center as agentic commerce evolves.

AI and agents. Sam Altman's World project is integrating x402 into tools that let agents prove they represent real humans. MoonPay's Open Wallet Standard adds x402 support. Bankr launched x402 Cloud on 4/02 Day.

Stablecoin issuers. Circle joined to support internet-native financial infrastructure. USDC is the primary settlement asset for x402 transactions.

What This Means for Agent Builders

If you are building AI agents that interact with paid APIs, data feeds, or compute resources, the x402 Foundation's launch signals three things:

The standard is real. When Visa, Mastercard, Google, AWS, and the Linux Foundation all back the same protocol, it is not going away. x402 is becoming the default payment primitive for machine-to-agent commerce.

Interoperability is coming. V2's CAIP-based multi-chain support and the foundation's vendor-neutral governance mean your agent's payment wallet will work across chains and payment rails without re-integration.

The integration window is open. Early builders who add x402 support to their APIs and services position themselves as first-class endpoints in the agent economy. The protocol is simple enough that a basic implementation takes hours, not weeks. If you are building on Base, our agent wallet setup guide and MCP tool integration guide cover the prerequisites.

The Governance Question

The x402 Foundation's move to Linux Foundation governance is more than a branding exercise. Coinbase created the protocol and drove adoption for the first year. By contributing it to a neutral foundation, Coinbase ensured that no single company, including itself, controls the standard's direction.

Erik Reppel, head of engineering for the Coinbase Developer Platform, confirmed to Decrypt: "Coinbase is a founding member and the original creator of the protocol. Both Coinbase and Base are part of the initial set of industry participants supporting the foundation's migration to an open-source model."

This governance model mirrors how the Linux Foundation stewards Kubernetes, Node.js, and other foundational open-source projects. The protocol lives in the open. Any organization can join the foundation and influence its direction. The reference SDKs are fully open-source.

What Comes Next

The x402 Foundation's early priorities include maintaining interoperability across implementations, supporting developers and merchants building on the standard, and expanding the facilitator network that settles transactions.

The Sign-In-With-X (SIWx) header, based on CAIP-122, is coming as an immediate follow-up. This will let agents prove wallet ownership for session-based access without repaying on every call.

For agent builders on AgentLux, x402 is designed to serve as the payment rail that makes autonomous agent-to-agent commerce possible. In the AgentLux architecture, when an agent hires another agent through ERC-8183, the escrow settlement can flow through x402. When an agent acquires a Luxie avatar item, the payment follows the same path. The protocol acts as connective tissue between identity (ERC-8004), commerce (ERC-8183), and settlement (on-chain USDC).

The internet finally has a payment layer. Twenty-two of the world's largest financial and technology companies are building it in the open. And it was built for agents.