Explainer · TIER_B
x402 vs MPP
Two HTTP 402 families. Different payloads, facilitators, and settlement stories.
zFinia published 7 September 2026
x402, launched publicly by Coinbase in May 2025, typically settles stablecoins through a facilitator such as CDP. MPP, co-authored by Stripe and Tempo in March 2026, is designed to be rail-agnostic including cards and stablecoins into existing merchant balances.
Cover both. Do not pretend they are the same protocol. Routing is a product.
Updated 11 September 2026
x402 vs MPP in 2026
The useful comparison is not which acronym wins. It is which payment contract a buyer and seller can both execute safely. x402 and MPP overlap around machine-readable payment requests, but their current integrations and payment-method surfaces differ.
| Question | x402 | MPP |
|---|---|---|
| Core job | Turn an HTTP 402 challenge into a machine-executable payment and retry. | Coordinate programmatic agent payments for HTTP-addressable resources, including APIs and MCP servers. |
| Payment surface | Commonly crypto-native: the live challenge advertises the network, asset, amount and payee. | Payment-method extensible. Stripe documents stablecoins plus fiat methods including cards and buy now, pay later. |
| MCP relationship | Can gate an HTTP resource used by an MCP integration; MCP itself remains the tool protocol. | Stripe explicitly describes MPP payment requests for APIs, MCP servers and other HTTP endpoints. |
| Interoperability | Independent protocol with its own live challenge and settlement contract. | MPP's mppx SDK added compatible x402 exact handling on EVM networks in June 2026. |
| Current public measurement | 186,351,811 settlements and $41,715,352 settled volume reported by Agent Economy as of 10 Sep 2026 UTC. | 45,766 Tempo MPP channel events across 1,850 unique payers and 90 payees reported by Agent Economy as of 10 Sep 2026 UTC. |
Those activity counters are not comparable one-to-one. Agent Economy explicitly notes that an MPP channel event is not a payment and one channel can carry many payments. Treat them as separately scoped observations, not a league table.
The protocols are becoming more interoperable, not less distinct
MPP's official site now documents EVM and x402 support in the same SDK: a client can select among payment methods exposed by a request, while a server can add x402 exact support alongside an EVM charge method. That reduces integration friction, but it does not make live terms interchangeable. Agents should still verify protocol, amount, asset, network, payee and response contract before spending.
A practical selection rule
- • If an endpoint already exposes a valid x402 contract your buyer can settle, use the live contract instead of adding abstraction for its own sake.
- • If a seller needs Stripe's existing merchant stack or multiple payment methods, MPP is specifically designed for that surface.
- • If both are exposed, choose deterministically from supported payment methods, price, settlement policy and required guarantees.
- • Do not infer economic adoption from incompatible counters; measure successful independent paid deliveries and reuse.
Continue from comparison to execution
Use zFinia's discovery and verification guides to inspect the live service contract rather than selecting a rail from a marketing summary.