Why Stripe shipped x402 support and then shipped MPP

What Stripe shipped, and what nobody can date

Start with the part I cannot verify. No source in the verified record behind this site documents a distinct February 2026 Stripe x402 release. The claim circulates widely. The primary document that exists and carries a date is Stripe's Machine Payments Protocol announcement, published 18 March 2026. That is the one to read.

What is checkable about February 2026 is that x402 had a bad month. BlockEden.xyz records daily x402 transactions falling from about 731,000 in December 2025 to about 57,000 in February 2026, a decline of over 92%. Stripe then shipped a billing standard into a trough.

That sequence looks like a hedge. Read the two specifications side by side and it stops looking like one.

What one HTTP 402 response can and cannot express

x402 is a settlement primitive, not a billing system. According to the x402 protocol documentation, the protocol charges no fee of its own and payers cover network fees only. It is blockchain-agnostic, supporting EVM chains and Solana.

According to the Coinbase x402 repository, the spec defines an exact scheme that transfers a specific amount, wraps it in PaymentPayload and PaymentRequirements objects, and delegates verification to a facilitator role. Reference SDKs and middleware ship for TypeScript, Python and Go.

That is a complete, well-specified answer to one question: pay this amount for this call.

It cannot answer four others.

• How much has this agent consumed since the period started?
• When does the current period end, and what happens at the boundary?
• What does cancellation mean once a payment has already settled?
• How do you reconcile usage metered downstream against money that arrived upstream?

Those are not gaps in the implementation. They are outside the scope of a 402 response by design. A single request-response exchange has no memory of the exchange before it.

What MPP adds

Subscriptions, streaming usage, cancellation and reconciliation.

Those are the words Stripe uses for what the Machine Payments Protocol covers, and they are precisely the four things a one-shot 402 cannot express. MPP is HTTP-native, built with Tempo, the payments-optimised blockchain Stripe built with Paradigm on which MPP is designed to run, according to Tempo, and aimed at the same buyer: software that needs to bill software.

The Stripe post is explicit that this covers ground one-shot HTTP 402 does not. Take that at face value. It is a description of scope, not a competitive claim.

Where the two overlap and where they compose

They overlap on exactly one thing: a single call with a single price. Both can bill it.

They compose everywhere else. x402 handles the settlement of the individual request. MPP handles the relationship that produces a series of requests. If you are metering API access monthly, x402 settles each call and MPP governs the account those calls belong to.

The membership list settles the hedge question. Stripe is one of the seventeen premier members named in the Linux Foundation's operational launch announcement for the x402 Foundation on 14 July 2026, alongside Adyen, AWS, American Express, Circle, Cloudflare, Coinbase, Fiserv, Google, Mastercard, the Monad Foundation, MoonPay, Ripple, Shopify, the Solana Foundation, the Stellar Development Foundation and Visa. The Foundation launched operationally with 40 member organisations.

A company hedging against a standard does not sit on its premier council. Stripe is building above x402 while paying into x402.

Which one to reach for

Reach for x402 when the transaction is one call and the counterparty is a stranger. That is what the current volume looks like. According to CoinDesk, citing Artemis, x402 was doing around $28,000 of real daily volume at an average payment of around $0.20, against roughly 131,000 daily transactions. Twenty cents per call is a one-shot problem. Subscriptions solve nothing at that size.

Reach for MPP when you are selling access over a period. Metered API tiers, seat-based agent access, anything where the buyer asks "what will this cost me this month" before they ask "what does one call cost".

Reach for neither if you are a publisher charging crawlers. That is what Cloudflare's Monetization Gateway addresses, published 1 July 2026, letting Cloudflare customers charge for any protected asset and settling in stablecoins over x402. The billing unit there is crawl access, not a call an agent chooses to make.

If you sell one endpoint to agents you will never identify, x402 only. If you sell a quota, an allowance or a period of access, MPP is the layer that describes it, and x402 underneath is still how the money moves.

Why the volume numbers do not settle the argument

They cut both ways, and that is the point.

According to TRM Labs, roughly $52.7 million settled across 198.9 million x402 settlements on Base, Solana and Polygon since May 2025. Only $25.62 million screens as plausible commerce, and 0.6% to 7.5% of that appears agentic. 99.6% of the value settled in USDC.

According to Chainalysis, cumulative x402 transactions on Base passed 100 million through Q1 2026, and payments of $1 or more rose from 49% of value in early 2025 to 95% by early 2026. Tester-to-payer conversion improved fourfold in six months.

Read those together. Transaction counts are enormous, values are tiny, and the share that is genuinely agentic is a rounding error on a good day. A one-shot payment protocol is being used the way people use a faucet: to test whether the tap works. Nobody has demonstrated that recurring agent billing is a larger market than per-call settlement, because recurring agent billing barely exists yet.

What to do with this

If you run an endpoint, the useful move is not to pick a side in a standards argument. It is to separate the two questions you are being asked. Price per call is one question. Terms over a period are another. x402 answers the first and MPP answers the second, and you can adopt the first today without committing to the second.

Stripe shipped MPP four weeks after a 92% collapse in daily x402 transactions. That timing is the whole story. The settlement layer had already been built and standardised. What was missing was everything that happens after the first successful payment. You can see how the endpoint discovery side works in the x402 Bazaar explained, and how Cloudflare priced the equivalent problem for publishers in Cloudflare's Monetization Gateway.

For how these figures were collected and scored, see how the corpus was measured, or common questions, answered.