On March 18, 2026, two seemingly independent yet deeply interconnected events unfolded in the payments sector: Stripe and Tempo officially launched their mainnet and introduced the Machine Payment Protocol (MPP), while Coinbase rolled out a major upgrade to the x402 protocol, enabling support for any ERC-20 token. This wasn’t a mere coincidence—it signaled that the battle over "how AI agents will pay" had reached a pivotal stage.
As AI agents evolve from simple information processors to autonomous economic actors—making decisions, calling APIs, renting compute power, and purchasing data—their payment infrastructure must meet three essential criteria: machine readability, millisecond response times, and zero human intervention. Traditional credit card networks and manual approval processes simply cannot function in this context.
Currently, x402, MPP, and AgentKit (the cryptographic extension layer of Google’s AP2 protocol) are the three most prominent technical solutions in this space. Drawing on the latest production data and protocol documentation, this article compares these approaches across technical architecture, adoption status, and ecosystem philosophy, and explores potential future developments.
Protocol Launch Surge and First Production Data
On March 18, 2026, the Tempo blockchain mainnet went live, and the MPP protocol was launched simultaneously, introducing the concept of "sessions"—agents can pre-authorize spending limits and stream micro-payments within a session, without requiring each transaction to be recorded on-chain. That same day, Coinbase upgraded x402 to version V2, integrating Uniswap’s Permit2 and gas sponsorship extensions. This allows developers to accept USDT, DAI, and various native project tokens, with users no longer needing to hold ETH for gas fees.
Within the same week, ClawMerchants (an agent-native marketplace for data and skills) released the first real-world production data on x402 adoption: as of March 17, its endpoints had received over 500 agent probe requests but completed only 5 purchases—a conversion rate of about 1%, with total revenue of $0.11. This data offers a rare benchmark: agent payments are still in their infancy. Most agents "probe, read the 402 response, and parse prices," but lack actual payment capabilities.
From Dormant Status Code to Standards Battle
The name x402 is derived from the HTTP status code "402 Payment Required," which has been reserved since the early days of the internet but remained unused for decades. In May 2025, Coinbase formally released the x402 standard, aiming to embed crypto payments directly at the HTTP protocol layer—servers return a 402 response containing the amount, token type, recipient address, and blockchain info. Agent clients then complete an on-chain payment to access the service.
In September 2025, Google launched AP2 (Agent Payments Protocol), partnering with Mastercard, PayPal, American Express, and over 60 other organizations to establish an AI authorization framework based on "verifiable credentials." Unlike x402’s crypto-native approach, AP2 focuses on building a "trust semantic layer" atop existing financial systems. Notably, Google also announced a collaboration with Coinbase to launch the "A2A x402 extension," positioning x402 as a "production-grade solution for agent crypto payments." This detail suggests the two systems are not strictly opposed—they may be complementary.
In December 2025, x402 released its V2 upgrade, with key improvements including a unified multi-chain payment interface, session-based deferred settlement, integration of crypto and fiat hybrid channels, persistent wallet identity, and support for dynamic payment routing. In just seven months, x402 processed over 100 million autonomous payments, totaling $24 million, with daily transaction volumes surpassing $500,000.
The launch of MPP on March 18, 2026, pushed competition to a new level. Jointly developed by Tempo and Stripe, MPP supports native settlement on the Tempo chain, connects to the Bitcoin Lightning Network via Lightspark, and extends to traditional card payments through Visa. This means that in the future, agents can complete MPP payments using only Stripe credentials, without holding any crypto assets.
Technical Comparison of the Three Protocols
From a technical perspective, the three protocols differ significantly in payment granularity, asset support, settlement models, and dependencies. Based on the latest protocol documentation and production data, here’s a comparative overview:
| Comparison Dimension | x402 (V2) | MPP | AgentKit (AP2 Extension) |
|---|---|---|---|
| Payment Granularity | Per-request payments, now with session mode | Native session-based streaming payments | Batch payments based on "authorization directives" |
| Asset Support | Any ERC-20, unified multi-chain interface | Stablecoins + fiat (cards/wallets/BNPL) | Credit cards/bank transfers + stablecoins |
| Settlement Model | On-chain final settlement | Tempo chain settlement + fiat channels | Traditional payment networks + optional crypto |
| Dependencies | Optional facilitators, supports P2P | Requires Tempo chain and Stripe | Requires AP2-compatible wallets and verification services |
| Identity Mechanism | Persistent wallet signature sessions | Session pre-authorization | Verifiable credentials + delegated authorization |
| Use Cases | API calls, data purchases, compute rentals | High-frequency micropayments, streaming services | E-commerce, complex bookings, compliant transactions |
The "facilitator" design in x402 V2 is noteworthy—it’s akin to traditional payment service providers, but with a twist: facilitators don’t custody funds or control private keys. Agents authorize "what to do" (e.g., send up to $X from payer to payee) to a facilitator, who then handles "how to do it" (choosing the chain, paying gas fees). This preserves non-custodial security while greatly lowering the technical barrier for agent integration.
MPP’s session model addresses the bottleneck of high-frequency transactions at the architectural level. In the original x402 mode, every API call required a separate on-chain transaction—even on low-cost L2s like Base, gas costs and latency scale with frequency. MPP allows agents to pre-authorize spending limits, enabling real-time deductions and periodic batch settlements within a session, much like how humans use credit cards.
AgentKit (the cryptographic extension of AP2) stands out for its "authorization directive" system. It introduces two types of cryptographic signature contracts: Cart Mandate for real-time transaction confirmation, and Intent Mandate for preset conditional execution. This mechanism creates undeniable audit trails for every transaction, solving the issue of "who authorized this AI payment."
Industry Opinions: Philosophical Divides and Market Response
Clear lines have been drawn in the industry debate around these protocols, with three main points of contention: permissionless vs. payment optimization, crypto-native vs. traditional compatibility, and protocol neutrality vs. ecosystem lock-in.
x402 supporters emphasize its permissionless nature. x402 can operate peer-to-peer, facilitators are optional, and anyone can run them—the protocol doesn’t depend on any single entity for survival. In ClawMerchants’ tests, agents can use x402 for on-chain payments or MPP for session-based streaming payments; the same endpoint supports both protocols—"protocol support is not mutually exclusive at the technical level, but can coexist."
MPP advocates value its optimized payment experience. The integration of Tempo and Stripe brings fiat channels, fraud protection, and tax handling—complete commercial capabilities. For developers not native to crypto, adding MPP support to their existing Stripe dashboard is far more convenient than integrating an on-chain payment gateway. "If I wanted to add micropayments to The Defiant today, I’d probably choose MPP—fiat acceptance is critical for non-crypto audiences, and I already use Stripe for payments."
AgentKit is praised for its compliance framework. Google’s collaboration with over 60 payment and e-commerce institutions gives the standard inherent trust in the traditional business world. Backing from giants like Ant International, UnionPay International, and Adyen suggests AgentKit could become the "universal language" connecting AI agents to existing e-commerce systems.
Insights from Production Data
ClawMerchants’ 500 probes, 5 purchases, and $0.11 in revenue provide the most authentic snapshot yet of agent payment adoption. This data reveals several realities often obscured by grand narratives:
First, agent probing doesn’t equal agent payment. Many agents can read the 402 response, parse prices, record endpoints, and understand payment requirements, but very few actually execute payments. Some even build "scanners" that probe payment endpoints without completing transactions.
Second, wallet absence is the biggest bottleneck. The most common scenario among probing agents: they correctly parse the 402 response and know USDC on Base is needed—but lack a private key, wallet, or any payment credentials. Payment modules remain the weakest link in the agent capability stack.
Third, "skills" convert far better than "data." In ClawMerchants’ catalog, skill assets (capability modules agents can directly invoke) have a conversion rate of 14–33%, while data assets convert at less than 1%. This suggests agents prefer to purchase immediately executable functions rather than information requiring secondary processing.
These findings provide a sober backdrop to the protocol debate: the core challenge at this stage isn’t which protocol is technically superior, but how to ensure agents actually "have wallets and are willing to pay."
Industry Impact Analysis: Three Layers of Value Reconstruction
Agent payment protocols are reshaping value flows in the digital economy at three levels:
Protocol Layer: Financial extension of HTTP. The 402 status code has evolved from dormant to a foundational primitive for the machine economy. In the future, every API call may carry a payment invoice, marking the first time the internet protocol stack natively supports value transfer.
Settlement Layer: Continuous asset flows. The shift from solid assets (monthly subscriptions) to liquid assets (microprofits credited every second) is underway. Streetlights bid for electricity based on real-time foot traffic, energy storage devices balance the grid in milliseconds—these scenarios depend on a settlement layer that natively supports streaming payments.
Trust Layer: The dawn of machine credit. When agents can defer payments and pre-authorize spending limits, credit assessment extends from humans to code. Spectral Finance’s MACRO system is already experimenting with on-chain transaction histories to generate credit scores for AI agents, enabling low- or even zero-collateral lending.
Scenario Evolution Forecasts
Based on the current landscape and production data, three possible evolutionary paths emerge:
Scenario One: Long-term protocol coexistence. The protocols are not a zero-sum game—ClawMerchants supports both x402 and MPP at the same endpoint. Agents can choose their payment path based on their capabilities: crypto-native agents use x402, those with Stripe credentials use MPP, and high-value e-commerce transactions go through AgentKit’s compliance framework. The market stratifies by use case, with interoperability as a core requirement.
Scenario Two: MPP dominates the commercial side. If most developers, like The Defiant’s founder, "prioritize fiat acceptance and integration with existing tools," MPP could quickly gain commercial adoption thanks to Stripe’s merchant network. x402 would retain share in crypto-native scenarios, but mainstream e-commerce and SaaS services would gravitate toward the more familiar payment stack.
Scenario Three: x402 becomes the de facto "HTTP for payments." With support from infrastructure giants like Cloudflare and Google Cloud, x402 could infiltrate the internet like TCP/IP, forming the backbone of value transfer. The decentralized facilitator network makes it resistant to control by any single commercial entity, positioning it as a potential public utility in the long run.
Conclusion
What currency will AI agents use for transactions? The answer may not be a single protocol or token. x402, MPP, and AgentKit each represent a distinct path—crypto-native, payment optimization, and compliance-first—playing to their strengths at different layers of the tech stack.
ClawMerchants’ $0.11 in revenue is a reminder: the infrastructure for the agent economy is still in the "probing stage." A true breakthrough will require agent wallet adoption to leap from "less than 1%" to "the majority." But the direction is clear—when every machine has its own wallet, every API call comes with an invoice, and every agent possesses verifiable credit, a new economic paradigm will naturally emerge. As of March 19, 2026, Gate market data shows USDC circulation and trading remain active on the Base network. The competition over agent payment standards is only just beginning.
