x402 vs MPP: what is the difference?
Short answer
Both let software pay for an HTTP request by answering with status 402. x402 came from Coinbase, is run by the x402 Foundation, and settles in blockchain tokens. MPP, the Machine Payments Protocol, was written by Tempo and Stripe, uses the standard WWW-Authenticate header, and also supports cards and Lightning. One endpoint can offer both at once.
Side by side
| x402 | MPP | |
|---|---|---|
| Full name | x402 | Machine Payments Protocol |
| Started by | Coinbase, May 2025 | Tempo and Stripe, announced March 18, 2026 |
| Governed by | x402 Foundation (Linux Foundation) | Its authors, with the core submitted to the IETF as an Internet-Draft |
| HTTP status | 402 | 402 |
| Price is sent in | PAYMENT-REQUIRED header | WWW-Authenticate: Payment header |
| Payment is sent in | PAYMENT-SIGNATURE header | Authorization: Payment header |
| Receipt | PAYMENT-RESPONSE header | Payment-Receipt header |
| Pays with | Tokens on many blockchains, usually USDC | Tempo stablecoins, Stripe, cards and Lightning in production. EVM, Solana and other networks available |
| Cards | Not natively | Yes |
| Kinds of payment | Schemes: exact, upto, batch-settlement, auth-capture | Intents: charge, session, subscription |
| Error format | Its own error codes | RFC 9457 Problem Details |
How they are alike
Both start the same way: an unpaid request gets a 402 that says what to pay. Both are open, both aim at AI agents and APIs, and both avoid accounts and API keys. A one-off x402 exact payment corresponds closely to an MPP charge.
How they differ
Where they come from. x402 began in crypto and is designed around signed token transfers. MPP comes from a payments company and treats a stablecoin transfer as one payment method among several, next to cards.
How they fit into HTTP. MPP reuses HTTP's existing authentication headers, WWW-Authenticate and Authorization, with a new Payment scheme, and is being put through the IETF as a draft standard. It is an individual draft, not a finished RFC. x402 defines its own headers.
What you can pay with. If a buyer needs to pay by card, MPP has that built in and x402 does not. If a buyer holds USDC on a network such as Base or Solana, both can work.
You do not have to choose
A server can put both sets of headers in the same 402 reply. An x402 client reads PAYMENT-REQUIRED, and an MPP client reads WWW-Authenticate: Payment. MPP's own tooling can serve both from one endpoint, and Stripe supports both, recommending MPP when cards are needed.
Agent402 is one example of an endpoint that answers with both. You can see it in the 402 checker: the result lists x402 offers and MPP offers for the same request.
Which should I use?
- Buying: use whichever your client and funds support. If you want to pay by card, look for MPP.
- Selling to crypto-native agents: x402 has the larger set of wallets, facilitators and catalogs today.
- Selling to buyers who want cards: offer MPP, or both.
- Not sure: offer both. The cost is one more header.
A note on sources
The most detailed comparison available is published at mpp.dev by MPP's authors, so it is not neutral. The facts in the table above are ones we could confirm against each protocol's own specification.
Sources
- Stripe, introducing the Machine Payments Protocol (March 18, 2026)
- MPP compared with x402, mpp.dev (written by MPP's authors)
- MPP payment methods
- IETF draft, the Payment HTTP authentication scheme
- Using MPP with x402, mpp.dev
- Stripe, x402 and machine payments
Facts checked against these sources on . Protocols change, so the official specification wins if it disagrees with this page. Read this page as Markdown.
Related questions
Who writes this. Ask402 is published by Havok Holdings LLC, which also runs Agent402, one of the x402 services covered here. Agent402 is labelled wherever it appears. Everything else is described from each project’s own documentation, and nobody pays to be listed.