Coinbase Goes Left, Stripe Goes Right: The Agent Payment Showdown Between x402 and MPP

Original Title: Stripe's MPP vs. x402: What Actually Happened Today

Original Author: Nick Sawinyh, defiprime.com

Original Compilation: Peggy, Blockbeats

Editor's Note: Regarding the question of how Agents should pay, x402 and MPP propose two almost opposite paths.

x402 takes the minimalist protocol approach: embedding payment directly into HTTP requests, achieving pay-per-request in the simplest way. No accounts, no intermediaries, resembling the open, permissionless design of the early internet, suitable for long-tail developers and decentralized scenarios.

MPP is the maximalist system approach: solving high-frequency transactions, risk control, and fiat integration through sessions, streaming payments, and a compliance framework. It doesn't pursue purity but prioritizes meeting real-world business needs, making it more suitable for enterprise-level and large-scale applications.

The difference between the two is essentially two solutions to the same problem: whether to make payment a part of the protocol or a layer of the system.

Therefore, they are not in complete competition but rather distributed across different segments. x402 covers the long-tail needs of the open web, while MPP handles high-frequency and commercialized traffic. In a yet-to-be-formed Agent economy, this divergence is perhaps inevitable.

The following is the original text:

The HTTP status code 402, defined in the HTTP/1.1 specification since the late 1990s, has been waiting for a purpose. Its meaning is "Payment Required." The original vision was to embed payment capabilities into the protocol layer of the Web, allowing machines to purchase resources as easily as requesting a webpage.

But this vision largely failed to materialize. Over the years, this status code only occasionally appeared in niche scenarios, such as Shopify's rate-limiting responses or Apple Mobile Me's billing errors, but no one truly built the micro-payment future it implied. Instead, credit cards, subscription-based paywalls, and API Key mechanisms took over—systems essentially designed for human-operated interactions.

Today, two competing paths to realize this future have emerged, both announced on the same day. Next, I want to outline what they are, their differences, and why Stripe is betting on both routes simultaneously.

x402: The Simpler Solution

Coinbase officially launched x402 in May 2025. Its core idea is almost radically minimalist. A client requests a resource; the server returns an HTTP 402, informing the client: how much to pay, which token to use, and on which chain to complete the payment. After the client completes the payment on-chain, it attaches the payment proof to the re-initiated request, and the server delivers the resource.

It's that simple. No account system, no API Key, no subscription mechanism. Just one HTTP request round trip with a payment inserted in the middle.

Today, Stripe provides native support for x402 within its payment system, allowing merchants to receive such payments directly through their existing backend. However, fundamentally, x402 remains a protocol led by Coinbase, governed by the x402 Foundation co-founded with Cloudflare in September 2025. The protocol is fully open-source (Apache 2.0 license) and offers multi-language SDKs including TypeScript, Go, and Python.

Regarding support scope, Coinbase's official documentation shows current support for ERC-20 payments on Base, Polygon, and Solana. Meanwhile, the ecosystem is exploring extensions to other chains like Avalanche, Sui, and Near, with varying levels of maturity.

Now, looking at adoption data, it gets slightly more complex. Coinbase states that x402 has processed over 50 million transactions through its Agentic Wallet infrastructure. That sounds impressive, but according to CoinDesk on March 11th, citing Artemis on-chain analysis data: daily transaction volume is about 131,000, total value around $28,000, with an average payment of just about $0.20. Roughly half of these appear to be test or gamified behavior rather than real commercial transactions.

But this isn't necessarily bad. Because this protocol is designed for a market that doesn't truly exist yet—a world where AI agents make micro-payments (even below 1 cent) for API calls and data queries. The merchants serving this market are also just beginning to emerge.

For example, Google's Agentic Payments Protocol (AP2, part of the A2A framework) has integrated x402; Lowe's Innovation Labs demonstrated a demo where an AI agent can complete the entire process from product discovery, research to ordering in one flow. Also, World (initiated by Sam Altman) released AgentKit this week, adding human identity verification capabilities to x402 wallets.

The core assumption behind it is: if you make payment as lightweight as an HTTP request, use cases will naturally emerge. Whether this holds true remains to be seen.

MPP: The Full-Stack Solution

Stripe and Tempo have chosen a different path. The Machine Payments Protocol (MPP) was released today alongside the Tempo mainnet launch. Unlike x402, which is a lightweight wrapper layer on top of existing blockchains, MPP is specifically designed for the scenario of high-frequency transaction agents.

Its core mechanism is sessions. Instead of initiating an on-chain transaction for every resource request, an agent can first authorize a spending limit once and then continuously make micro-payments within that limit. If you are an AI that needs to query data sources thousands of times per hour, you absolutely don't want to sign and broadcast an on-chain transaction each time. Sessions are designed to solve this problem.

The Tempo chain is also built around this need. It supports tens of thousands of transactions per second, has sub-second confirmation times, and has no native gas token. Users can pay fees directly with stablecoins, eliminating the hassle of buying some random token just to transfer funds.

Another component worth understanding is: Stripe's Agentic Commerce Suite includes Shared Payment Tokens (SPTs). This is not part of MPP itself but Stripe's extension mechanism, which can be used in conjunction with it. SPTs allow an agent to securely pass a user's bank card or wallet credentials to a merchant without exposing the real data. These credentials are single-use and time-limited, essentially a programmable, self-destructing authorization. In practice, this means an agent paying via MPP can use either USDC on Tempo or a user's linked Visa card, or even a combination of both.

According to the Tempo mainnet launch blog, its partners include Anthropic, DoorDash, Mastercard, Nubank, OpenAI, Ramp, Revolut, Shopify, Standard Chartered, and Visa. The Block reported that at launch, the MPP payment directory already had over 100 services, including Alchemy, Dune Analytics, Merit Systems, and Parallel Web Systems. Matt Huang, co-founder of Tempo and Paradigm, told Fortune in an interview that this field is still in its early stages, and MPP is designed to eventually scale to environments beyond just the Tempo chain.

Why Stripe Supports Both

If you're already integrated with Stripe, the most practical answer is: you don't need to choose between them.

Stripe supports x402 and MPP through two separate integration paths, rather than abstracting them into a unified interface. For x402, its documentation mainly covers generating deposit addresses, monitoring on-chain activity, and settling funds into Stripe accounts—you handle returning the 402 response, and Stripe handles the underlying crypto payment infrastructure. Currently supports USDC on Base, with more to come. For MPP, merchants can receive session-based streaming payments through the same PaymentIntents API.

Stripe's Agentic Commerce Suite, released in December 2025, is built on top of these two payment rails. Merchants simply upload their product catalog, select the AI agents they want to connect with, and Stripe handles product discovery, checkout flow, fraud prevention, and tax processing. Currently, URBN, Etsy, Coach, Kate Spade, and Ashley Furniture are already using it, and platforms like Wix, WooCommerce, BigCommerce, Squarespace, and commercetools have completed integration.

The strategy is actually quite clear: control the abstraction layer and let the underlying protocols compete freely.

Comparison

At a macro level, these two protocols are doing the same thing: enabling machines to pay for resources via HTTP. But the real differences lie in the details.

x402 (led by Coinbase) vs MPP (Stripe + Tempo)

Standardization

x402: Fully open-source (Apache 2.0), promoted by the x402 Foundation for multi-party participation (Coinbase, Cloudflare, Visa, Google).

MPP: Open standard, jointly developed by Stripe and Tempo, part of Stripe's Agentic Commerce Suite.

HTTP Mechanism

x402: Revives HTTP 402, initiates requests via PAYMENT-REQUIRED header, uses PAYMENT-SIGNATURE for retry completion.

MPP: Also uses a challenge-response mechanism but employs the Payment HTTP Authentication Scheme (IETF draft), binding challenge IDs via HMAC.

Payment Rails

x402: Designed to be chain-agnostic, currently supported on Base, Polygon, Solana, with exploration ongoing for other chains.

MPP: Based on the Tempo blockchain—an L1 optimized for payments, supporting 10k+ TPS, sub-second confirmation, no native gas token; long-term goal is cross-chain compatibility.

Payment Methods

x402: Pure stablecoins, fully on-chain.

MPP: Supports USDC on Tempo + SPTs (Stripe's mechanism), enabling crypto-fiat hybrid payments (bank cards, wallets, BNPL).

Settlement Method

x402: Settles on-chain (approx. 200ms to several seconds), with facilitators like Coinbase responsible for verification and settlement.

MPP: Tempo sub-second confirmation, Stripe automatically credits accounts and handles compliance.

Merchant Integration

x402: Open-source middleware (Express, Hono, Next.js, etc.), can be self-built or use a facilitator.

MPP: Direct integration with Stripe's PaymentIntents API, with built-in risk control, tax, refunds, and reporting.

Core Innovation

x402: Extreme simplicity, no vendor lock-in, akin to the Unix philosophy for payments.

MPP: High throughput + fiat integration, enabling streaming payments and micro-payment aggregation via sessions, plus programmable spending controls based on SPTs.

Key Partners

x402: Coinbase, Cloudflare, Google (A2A/AP2), Visa, World, Anthropic (MCP).

MPP: Stripe, Visa, Lightspark, Anthropic, DoorDash, Mastercard, OpenAI, Shopify, Revolut, Standard Chartered.

x402 is more like your go-to solution when building open systems: independent developer APIs, decentralized data markets, or any service that doesn't want to rely on a payment processor. Its specification can fit into a whitepaper, and integration just requires a middleware and a wallet address. This purity is attractive—though the limitation to pure crypto also means its audience is narrower.

MPP is a completely different paradigm. If your agent needs to make hundreds or even thousands of transactions in a single session without going on-chain each time, then it's the more sensible choice. The session mechanism keeps most interactions off-chain until final settlement; Stripe's compliance framework handles risk and taxes; and the hybrid mode of SPTs allows agents to go beyond stablecoins and directly utilize user payment methods like Visa. It's less elegant but closer to reality.

Interestingly, they aren't exactly in competition. x402 covers long-tail open scenarios, MPP covers enterprise-level high-frequency traffic. Stripe's strategy is also clear: don't bet on a single protocol, but ensure that whichever path wins, funds ultimately flow into Stripe's account system.

Reality Check: Where Are We Actually At?

To be honest, there's almost no real scaled transaction volume yet.

According to Coinbase's x402 launch information, early partners include Hyperbolic (GPU inference payment) and Anthropic (MCP protocol integration). Stripe's blog mentions agent scenarios for pay-per-API-call (e.g., CoinGecko). Tempo's launch directory had 100+ services. Cloudflare's Agents SDK natively supports x402, and some small projects on Base L2 are experimenting with x402 as a payment gateway.

But overall: transaction volume is small, merchant count is limited, and most activity remains experimental.

This isn't surprising. Any new payment infrastructure starts like this. So-called partner lists sometimes have a big gap between signing a letter of intent and being live in production, and these announcements often don't distinguish clearly.

What's more noteworthy are the heavyweight players behind the infrastructure. Stripe processed $1.9 trillion in payments in 2025, with total volume growing 34% year-over-year. Meanwhile, Coinbase, Cloudflare, Visa, Google, and Tempo's entire partner network have entered the field.

In other words, the rails are laid. The only question left is: In 2026, will AI agents truly need to transact on these rails at scale? Or is this more like laying fiber optics in 1998—demand hasn't arrived yet, but the infrastructure is built first.

So Which One to Choose?

If you're building an open, permissionless system—x402 is the more natural choice. No platform registration, no payment provider integration, just import middleware and bind a wallet to receive payments. The trade-off: you handle compliance, risk control, and fiat settlement yourself.

If you're already within the Stripe ecosystem and want to tap into agent traffic—MPP is more suitable. Sessions, streaming payments, fiat+crypto hybrid, and a full compliance system essentially feel like a configuration upgrade rather than a system overhaul.

If you only care about one thing: being able to get paid regardless of which protocol the agent uses. Then the answer is simply: use Stripe. It supports both.

HTTP 402 finally has a use. It just took about 27 years.

Original Link