Ask402
The MPP guide

MPP, explained.

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. Read the full answer

MPP, question by question

What it is, how to pay with it and how to accept it.

What is MPP, the Machine Payments Protocol?

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.

How does an MPP payment work, step by step?

An MPP payment is four HTTP messages. The client asks for something. The server replies 402 with a challenge in the WWW-Authenticate header. The client pays and asks again with a credential in the Authorization header. The server checks it and returns the result with a receipt. The same exchange works whether the money is a stablecoin, a card or Lightning.

How do I pay for an MPP API?

Install an MPP client, give it a way to pay, and make your request through it. The reference client, mppx, patches fetch so that a 402 reply is paid and retried for you. With the Tempo method you need a wallet holding a stablecoin on Tempo. Other methods let you pay by card or Lightning. Clients exist for TypeScript, Python, Rust and Go.

How do I accept MPP payments on my API?

Add MPP middleware to your server, tell it which payment methods you take and who receives the money, and wrap each paid route with a charge. The reference library, mppx, has middleware for Next.js, Hono, Elysia and Express. Start on the test network, validate with the command-line tool, then switch to live. Stripe users can accept MPP through Stripe.

What can you pay with in MPP? Payment methods explained

MPP separates the protocol from the money. Each way of paying is a payment method with its own name. Four are listed as in production: Tempo stablecoins, Stripe, cards through Visa, and Bitcoin Lightning. Others, including EVM chains, Solana, XRPL, Stellar and Monad, have published SDKs. A seller chooses which to accept and lists them in its 402 reply.

What is Tempo, the network MPP payments settle on?

Tempo is a blockchain built for stablecoin payments. It is compatible with Ethereum tooling, charges its network fees in dollar stablecoins instead of a separate gas coin, and is designed to confirm payments in under a second. Tempo co-wrote MPP with Stripe, and the tempo payment method is the most complete one in MPP. Tempo is one way to pay with MPP, not the only one.

MPP beside x402

The two protocols solve the same problem and can share an endpoint. A server can offer both in one 402 reply, and each client reads the one it understands.

Read the x402 guide →

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.

Answers last checked against their sources on November 20, 2026. For AI readers: every answer is also available as Markdown (add .md to the address), with an index at /llms.txt.