What can you pay with in MPP? Payment methods explained
Short answer
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 a payment method is
MPP's documentation defines it simply: payment methods "define how a buyer pays a seller for a resource protected by the Machine Payments Protocol".
The protocol's four messages stay the same whatever the method. Only the proof of payment changes. See how an MPP payment works.
The methods listed today
This is the list on MPP's own site at the time of review.
| Method | Name in a challenge | Kinds of payment | Status | Maintained by |
|---|---|---|---|---|
| Tempo | tempo | Charge, session, subscription | Production | Tempo |
| Stripe | stripe | Charge, session | Production | Stripe |
| Card | card | Charge | Production | Visa |
| Lightning | lightning | Charge, session | Production | Spark |
| EVM | evm | Charge | Available | Tempo |
| Solana | solana | Charge, session | Available | Solana Foundation |
| XRPL | xrpl | Charge, session | Available | Ripple |
| Stellar | stellar | Charge, session | Available | Stellar |
| Monad | monad | Charge | Available | Monad |
| NEAR Intents | nearintents | Charge | Available | Defuse Protocol |
| RedotPay | redotpay | Charge | Available | RedotPay |
Anyone can also write a custom method.
What the status words mean
MPP's site defines them:
- Production: used for live payments today.
- Available: an SDK has been published by its maintainer. The site says to ask the maintainer about production readiness.
It also notes that sessions on Stellar are experimental.
The four in production
Tempo. Stablecoin payments on the Tempo network. It is the only method listed with all three kinds of payment, including subscriptions. See what Tempo is.
Stripe. Described as "traditional payment methods through Stripe". Stripe's announcement says businesses can take payments from agents in stablecoins and in ordinary money, with cards and buy now, pay later methods.
Card. "Card payments via encrypted network tokens", maintained by Visa.
Lightning. "Bitcoin payments over the Lightning Network".
Kinds of payment
The middle column uses MPP's three intents:
| Intent | What it is |
|---|---|
| Charge | One payment that settles immediately |
| Session | A stream of small payments over a payment channel |
| Subscription | A recurring fixed payment for access over billing periods |
Every listed method supports a charge. Sessions and subscriptions depend on the method.
How a seller's choice reaches you
A seller decides which methods to accept. Its 402 reply lists them, and your client pays with one it supports. If the seller only takes Tempo and you only hold a card, you cannot pay it.
To see what a particular endpoint accepts, paste it into the 402 checker. It shows each MPP offer with its method.
SDK coverage
The reference library, mppx, is TypeScript and covers Tempo, Stripe and EVM. Tempo also has SDKs in Rust, Python, Go and Ruby, and Stripe in Rust, Python and Ruby. Most other methods ship as a separate TypeScript package from their maintainer.
Compared with x402
x402 has one family of payment: tokens on blockchains, most often USDC. It covers many networks, but not cards. See which blockchains and tokens x402 supports.
MPP's evm method is described as having "inline x402 exact compatibility", so the two protocols can meet on EVM stablecoin payments. For the wider comparison see x402 vs MPP.
If you want to pay by card
This is the practical reason many people look at MPP. If a service lists the card or stripe method, you can pay it without holding crypto. See using paid services without a crypto wallet.
Sources
- MPP payment methods
- MPP protocol, mpp.dev
- Stripe, introducing the Machine Payments Protocol (March 18, 2026)
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.