What is MPP, the Machine Payments Protocol?
Short answer
MPP is an open protocol that lets software pay for something inside an ordinary HTTP request. A server answers with status 402 and a challenge, the client pays and retries with a credential, and the server returns the result with a receipt. It was written by Tempo and Stripe, announced in March 2026, and works with stablecoins and cards.
The short version
MPP solves the same problem as x402: letting a program, often an AI agent, pay for a request with no account and no checkout page. Its authors describe it as "an open protocol co-authored by Tempo and Stripe". Stripe announced it on March 18, 2026.
Where x402 grew out of crypto payments, MPP was designed to carry several kinds of payment through one protocol, cards included.
How a payment works
- The client asks for a resource.
- The server replies 402 with a Challenge: the payment options it accepts.
- The client pays and repeats the request with a Credential: proof of payment.
- The server checks it and returns the resource with a Receipt.
| Part | Travels in | What it is |
|---|---|---|
| Challenge | WWW-Authenticate: Payment header | "Server-issued payment requirements" |
| Credential | Authorization: Payment header | "Client-submitted payment proofs" |
| Receipt | Payment-Receipt header | "Server acknowledgment of successful payment" |
WWW-Authenticate and Authorization are the headers HTTP has always used for logging in. MPP adds a new scheme to them, named Payment.
Three kinds of payment
MPP calls these intents.
| Intent | Meaning, in the protocol's words |
|---|---|
charge | "One-time payment that settles immediately" |
session | "Streaming payment over a payment channel" |
subscription | "Recurring fixed payment for paid access across billing periods" |
A charge is the equivalent of a standard x402 payment.
What you can pay with
The overview says MPP "works with stablecoins, cards, and bank transfers". Stripe's announcement describes accepting payments from agents "in stablecoins as well as fiat with cards and buy now, pay later payment methods".
Each way of paying is a payment method with its own identifier, such as tempo or stripe. Which ones a given server takes is listed in its challenge. The current list and the status of each is on MPP's payment methods page.
Who is behind it
| Authors | Tempo and Stripe |
| Announced | March 18, 2026 |
| Specification | Submitted to the IETF as an Internet-Draft. It is a draft, not a finished standard |
| SDKs | mppx for TypeScript (the reference implementation), pympp for Python, mpp-rs for Rust, mpp-go for Go |
Stripe's announcement named early users including Browserbase, PostalForm, Prospect Butcher Co. and Parallel Web Systems.
MPP and x402
They are close relatives and they can share an endpoint. A server can send x402's PAYMENT-REQUIRED header and MPP's WWW-Authenticate: Payment header in the same 402 reply, and each client reads the one it understands.
The differences, and which to pick, are in x402 vs MPP.
Why it matters if you do not hold crypto
MPP is the usual route for paying a machine-priced API by card. If a service offers an MPP card method, a client can pay without a wallet. See using x402 services without a crypto wallet.
See one
The 402 checker reads MPP challenges as well as x402 offers. Paste an endpoint and it lists each payment option, labelled by protocol.
Sources
- MPP overview, mpp.dev
- MPP protocol, mpp.dev
- Stripe, introducing the Machine Payments Protocol (March 18, 2026)
- IETF draft, the Payment HTTP authentication scheme
- MPP payment methods
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.