In 1997, the Internet Engineering Task Force reserved an HTTP/1.1 status code: 402 Payment Required , with a note indicating it was "reserved for future use." For nearly three decades, while digital payment systems evolved significantly, this status code remained unused—until May 2025, when Coinbase introduced the X402 protocol.
On April 2, 2026, the Linux Foundation announced at the MCP Developer Summit in New York the establishment of the X402 Foundation , placing this Coinbase-originated open-source protocol under a neutral governance framework. Founding members include more than 20 organizations such as Google Cloud, Microsoft, AWS, Visa, Mastercard, American Express, Stripe, Cloudflare, Shopify, Circle, the Solana Foundation, and Polygon Labs.
This development reflects a rare alignment between crypto infrastructure providers and traditional payment networks, marking the early stage of a broader effort to standardize internet-native payment infrastructure.

A Protocol Migration Involving Major Industry Participants
The X402 protocol was initially released by Coinbase in May 2025. In September 2025, Coinbase and Cloudflare announced plans to form an independent foundation. In April 2026, the Linux Foundation formally adopted the project and launched the X402 Foundation as a neutral governance structure.
The participating organizations span three primary categories:
- Payment networks: Visa, Mastercard, American Express, Adyen, KakaoPay, Fiserv Merchant Solutions
- Cloud and infrastructure providers: Google Cloud, AWS, Microsoft, Cloudflare
- Crypto-native infrastructure: Circle, Base, Solana Foundation, Polygon Labs, Thirdweb
In addition, participation from Shopify and Ant International suggests the protocol is designed not only for crypto-native use cases but also for broader commercial payment infrastructure scenarios.
Linux Foundation Executive Director Jim Zemlin stated:
"The internet is built on open protocols. The X402 Foundation will provide a neutral, community-driven governance structure to ensure transparent and interoperable development."
A Concept Originating from the Early Web Architecture
The origin of HTTP 402 dates back to the early design of the web. In 1991, HTTP architects Tim Berners-Lee and Roy Fielding reserved status code 402—Payment Required—with the intention of enabling native digital payments within the protocol layer.
However, due to technological constraints at the time—including the lack of low-cost digital cash systems, inefficient cross-border settlement infrastructure, and limited micropayment feasibility—the status code was never activated.
For decades, internet payment systems relied on external infrastructure such as credit card forms, third-party gateways, subscription systems, and API key-based authorization. These mechanisms were primarily designed for human users and are increasingly less suitable for autonomous AI-driven systems.
As Zemlin noted:
"X402 integrates payments directly into the structure of the web protocol."
Protocol Development Timeline
- May 2025: Coinbase introduces X402 protocol, enabling HTTP 402 usage
- September 2025: Coinbase and Cloudflare announce foundation initiative
- Oct–Nov 2025: Protocol upgrade phase; total transactions exceed 100 million
- February 2026: Coinbase launches Agentic Wallets for AI agents
- March 2026: Stripe and Paradigm’s Tempo release Machine Payments Protocol; Visa introduces machine-oriented payment tools
- April 2, 2026: Linux Foundation establishes X402 Foundation
- April 20, 2026: Agentic.market launches as an AI agent application marketplace built on X402
Within one year, X402 transitioned from a corporate initiative to a foundation-governed standard under the Linux Foundation.
On-Chain Activity and Market Narrative
Protocol Activity Overview
According to Artemis Analytics, as of April 2026, X402 has processed approximately 97 million transactions on Coinbase’s Base network, with an estimated 54,900 daily transactions. The Solana network accounts for approximately 65% of total transaction volume, reflecting its suitability for high-frequency micropayment scenarios.
According to Circle data, AI agents executed over 140 million payment transactions in the nine-month period ending March 2026, with a total settlement volume of approximately $43 million. Around 98.6% of these transactions were settled in USDC, and more than 400,000 AI agents participated in on-chain payment activity.
Transaction Slowdown and Activity Quality Considerations
According to Dune Analytics, X402 experienced a sharp increase in activity during late 2025, with weekly transaction peaks reaching approximately 13.7 million.
However, in 2026, activity declined significantly. Daily transaction volume decreased from approximately 731,000 in December 2025 to around 57,000 in March 2026, representing a decline of roughly 92%.
Independent analysis from Artemis Analytics suggests that a portion of peak activity may have included non-economic transactions used for ecosystem visibility or testing purposes. After adjusting for estimated artificial activity, organic transaction levels are significantly lower than peak figures.
Separate research estimates that actual daily processed value during this period ranged approximately between $14,000 and $28,000, depending on classification methodology and inclusion of experimental transactions.
Broader Market Context
Despite short-term fluctuations in protocol-level activity, the broader Web3 payments market continues to expand. Industry research estimates global Web3 payment infrastructure will grow from approximately $10.5 billion in 2025 to $13.9 billion in 2026, representing growth of over 30%, with long-term projections exceeding $40 billion by 2030.
Growth drivers include increased stablecoin usage, cross-border settlement demand, and early-stage adoption of blockchain-based payment infrastructure by institutional participants.
Technical Architecture: Payments as a Protocol Primitive
The core design principle of X402 is to reposition payments from an application-layer feature to a protocol-level primitive embedded within HTTP .
The system consists of three roles:
- Client: Human user or AI agent with a cryptographic wallet
- Server: Resource provider requiring payment for access
- Middleware: Payment infrastructure responsible for validation and settlement
Payment Flow
- Client requests a resource via HTTP
- Server responds with HTTP 402 and payment instructions
- Client signs payment authorization using a wallet (EIP-3009 permit-based mechanism)
- Middleware broadcasts the transaction to the blockchain
- Server verifies payment and grants access to the resource
Key Design Characteristics
- No traditional accounts required: Wallet-based interaction model
- Near real-time authorization: Sub-second request-response cycle
- Micropayment support: Enables low-value transactions economically
- Chain-agnostic architecture: Primarily uses USDC, with potential multi-chain expansion
Comparison with Alternative Protocol Designs
Stripe and Paradigm’s Machine Payments Protocol (MPP) adopts a session-based model, allowing AI agents to pre-authorize spending sessions for multiple transactions without repeated authorization.
In contrast, X402 focuses on single-request settlement tightly integrated into HTTP infrastructure, reflecting a different design assumption about machine-to-machine payment behavior.
Industry Perspectives: Convergence and Divergence
Infrastructure Standardization Perspective
Supporters of X402 view it as an incremental infrastructure evolution for the internet, similar in concept to earlier protocol layers such as SSL/TLS. Industry participants from Coinbase, Circle, Google Cloud, and Stripe emphasize that AI-driven systems require open and interoperable payment standards.
From this perspective, X402 represents an early-stage attempt to define a shared settlement layer for autonomous digital systems.
Cautious Perspective: Demand Maturity Considerations
From a data-driven standpoint, analysts highlight that while infrastructure development is advancing, large-scale autonomous agent-driven economic activity remains in an early experimental phase.
Transaction volatility and variability in network activity suggest that usage patterns are still evolving rather than stabilized.
Competitive Landscape
X402 is part of a broader ecosystem of competing standards. Stripe, Visa, OpenAI, and other institutions are developing parallel machine payment frameworks. Google Cloud has integrated X402 into its Agentic Payments infrastructure, while Circle is building additional settlement layers on top of it.
Rather than a single dominant standard, the current landscape reflects parallel experimentation across multiple protocol designs.
Industry Impact
Traditional Payment Networks
Visa and Mastercard’s participation in the X402 Foundation reflects increased institutional interest in machine-oriented payment infrastructure. These organizations are actively exploring stablecoin settlement systems and blockchain-based payment rails as part of long-term infrastructure development.
Web3 Infrastructure Evolution
Public blockchain networks are increasingly being evaluated not only by DeFi activity but also by payment efficiency and settlement performance. This shift may influence how infrastructure value is assessed over time.
AI-Driven Payment Models
X402 introduces the possibility of transitioning from subscription-based pricing models to usage-based micropayment systems for AI services. This may enable more granular alignment between computational usage and payment flows, particularly in cross-border environments where settlement efficiency is critical.
Conclusion
The significance of X402 lies not in the revival of a dormant HTTP status code, but in the attempt to reposition payment functionality as a core component of internet protocol infrastructure.
However, protocol standardization is a long-term process. While governance by the Linux Foundation and participation from major industry players provide structural support, the gap between early-stage network activity and broader economic adoption remains significant.
At this stage, X402 can be viewed as an emerging infrastructure experiment positioned ahead of its demand curve. Whether it becomes a foundational layer of machine-driven payment systems will depend on the evolution of real-world AI agent usage and the maturation of on-chain economic activity over time.


