Protocols & news

Machine Payments Protocol (MPP): Stripe and Tempo's agent payment standard

Listen · 10 min

Narrated by an AI voice. Code examples are on the page.

Short answer

The Machine Payments Protocol (MPP) is an open protocol, co-authored by Stripe and Tempo and announced on March 18, 2026, that lets an AI agent pay for an API, service or web resource inside the HTTP request itself. The server answers with HTTP 402 and its price, the agent pays and retries, and the server returns the resource with a receipt. Unlike x402, which Stripe supports for stablecoins only, MPP also covers card payments on Stripe.

Key takeaways

  • MPP lets agents pay per request over HTTP 402, with a receipt.
  • On Stripe it takes cards and stablecoins; x402 takes stablecoins.
  • It fits paid APIs and services more than a store's cart checkout.

What is the Machine Payments Protocol?

The Machine Payments Protocol (MPP) is an open protocol that lets an AI agent pay for something in the same web request it uses to ask for it. There is no sign-up form, pricing page or checkout screen in between.

Stripe announced MPP on March 18, 2026, as "an open standard, internet-native way for agents to pay—co-authored by Tempo and Stripe." Tempo is a blockchain network. Stripe's documentation lists it as one of the networks it accepts stablecoin payments on, and the MPP site describes it as well suited to settling machine payments, though MPP does not require it.

Stripe's announcement explains the problem it is trying to solve. Buying something today "can require an agent to create an account, navigate a pricing page, choose between subscription tiers, enter payment details, and set up billing—steps that often require human intervention." MPP replaces those steps with a short exchange that software can complete on its own.

For a one-paragraph definition, see our MPP glossary entry.

How does an MPP payment work?

The server asks for payment, the agent pays and asks again, and the server hands over the resource with a receipt.

The MPP site describes the flow in five steps:

  1. The agent requests a resource, such as GET /resource.
  2. The server answers 402 Payment Required, with its payment options in a WWW-Authenticate: Payment header.
  3. The agent pays: it signs a transaction, pays an invoice or completes a card payment.
  4. The agent sends the request again, with proof of payment in an Authorization: Payment header.
  5. The server checks the payment and returns 200 OK, with a Payment-Receipt header.

The status code in step 2 is HTTP 402, "Payment Required." It has been part of the web for decades without an agreed use. MPP is one of the protocols now giving it one.

MPP is not limited to single charges. Its site describes three kinds of payment, which it calls intents: a one-off charge, a subscription, and a session. A session lets an agent deposit funds once and then pay for many small requests, charged per query or per token, without a separate on-chain payment each time. The MPP site also describes a way to carry the same flow over MCP, so an MCP server can charge for a tool call.

How do you accept MPP payments with Stripe?

You add an MPP endpoint to your API using Stripe's libraries. The payments then show up in your Stripe account like any other.

Stripe's docs describe MPP as a way to let "agents pay for your APIs and services programmatically without a checkout UI." According to Stripe, at the time of writing:

  • Cards work by default. Stripe's MPP endpoint accepts cards through Shared Payment Tokens, which Stripe describes as "scoped grants that let an agent use a customer's payment method." The minimum card charge is 0.50 USD.
  • Stablecoins are an extra step. You create a deposit address. Stripe lists USDC.e on Tempo and USDC on Solana for MPP, with a minimum of 0.01 USDC. Stablecoin payments are open to businesses in all US states except New York. Businesses elsewhere are asked to email Stripe.
  • Money lands in your balance. Stripe's announcement says MPP payments "appear in the Stripe API and Dashboard like any other transaction" and settle in your default currency on your normal payout schedule. Refunds work through the usual Refunds API and Dashboard.
  • It is new. Stripe labels the MPP docs "Frontier," and the guide uses a preview version of Stripe's API.

Stripe's launch post named early users: Browserbase, which lets agents pay per browser session, PostalForm, which prints and sends physical mail, and Prospect Butcher Co., which takes sandwich orders for pickup or delivery in New York City.

Card networks are paying attention too. In April 2026, Visa unveiled Intelligent Commerce Connect, then in a pilot with select partners, and said it enables merchants to accept payments started through several agent protocols, naming MPP alongside Trusted Agent Protocol, ACP and UCP.

How is MPP different from x402?

Both use HTTP 402 to ask for payment. The biggest practical difference today is that MPP covers card payments on Stripe, while Stripe's x402 support is for stablecoins only. The Linux Foundation describes x402 as covering methods "ranging from traditional cards to stablecoins," but the working x402 integrations we reviewed settle in stablecoins.

x402 came from Coinbase and is now run by the x402 Foundation under the Linux Foundation, which calls it "the open standard for internet-native payments over HTTP." Stripe supports both, and its own docs show the split. Stripe says machine payments on its platform work best with MPP, which "is able to accept card and stablecoin payments," and that it "also supports stablecoin payments over the x402 protocol." Stripe's x402 guide says that if you want cards as well as stablecoins, you should also integrate MPP.

MPP x402
Created by Stripe and Tempo Coinbase, now the x402 Foundation
Signals payment with HTTP 402 HTTP 402
Card payments on Stripe Yes, via Shared Payment Tokens No, stablecoins only
Stablecoins on Stripe USDC.e on Tempo, USDC on Solana USDC on Base
Spec status Individual IETF Internet-Draft Governed by the x402 Foundation

The MPP team also lists differences of its own, so read these as MPP's claims, not a neutral review. Its FAQ says MPP is "payment-method agnostic," while "x402 registers schemes for blockchain networks." It says MPP treats idempotency, expiry and protection against tampered requests as built-in features. It compares MPP sessions with x402's upto and batch-settlement schemes for usage-based billing.

The two are not rivals in every setup. The MPP FAQ says x402's "exact" payments "map directly onto MPP's charge intent," and that its TypeScript library can serve x402 and MPP clients from the same endpoint.

Is MPP an official standard?

Not yet. Its core is an individual Internet-Draft at the IETF, which is a proposal, not an approved standard.

MPP is split into two layers. The core is "The 'Payment' HTTP Authentication Scheme," published as draft-httpauth-payment. The version we checked, -01, is dated September 9, 2026, and its authors are listed with Tempo Labs and Stripe. The draft's header gives Standards Track as its intended status, which is the authors' aim, not a decision by the IETF. The MPP site says this core is "submitted to the IETF standards track." The IETF's own page for the draft says it is "not endorsed by the IETF" and has "no formal standing" in the standards process, which is normal for an individual draft.

The second layer is payment methods: how cards, a specific blockchain or Lightning plug into the core. The MPP site says each one is maintained by the company or network behind it, and anyone can publish a new one without approval.

MPP is also still changing. On November 11, 2026, the MPP blog announced tools that let a paid endpoint check who is calling, for example a verified email or an API key, "before it shows a price."

Should an online store use MPP?

Probably not for selling physical products through a cart, at least for now. MPP is built for paying per request, which suits APIs, data, AI tools and other services sold by the call.

MPP is worth a look if you:

  • run an API, data feed or tool that agents might pay for one request at a time
  • already use Stripe and want agent payments to land in the same account
  • want to accept cards from agents, not only stablecoins

For a store's normal checkout, agent purchases mostly run through other standards. UCP is behind checkout in Google's AI surfaces, and ACP came from OpenAI and Stripe. Our comparison of ACP, AP2, UCP and x402 and our guide to agentic commerce protocols show where each one fits.

Note. MPP and Stripe's support for it are moving quickly. Check Stripe's current docs and mpp.dev before you build.

Does Sill support MPP?

No. Sill does not support MPP or x402 today.

Sill shows you which AI agents and bots visit your site and what they ask for and buy. When an agent places an order, your rules approve it, decline it or hold it for a person to review, and every decision is signed and recorded. Sill is not a payment processor, and Stripe is the only live payment rail. Run a free readiness scan to see how your site looks to AI agents.

Questions people ask

Who created the Machine Payments Protocol?

Stripe and Tempo. Stripe's announcement calls MPP an open standard "co-authored by Tempo and Stripe", and the core specification's authors are listed with Tempo Labs and Stripe.

Is MPP free to use?

The MPP site says the protocol is free and open, with no licensing fees. Your payment provider still charges its own fees, and each seller sets its own prices.

Can an AI agent pay with a card through MPP?

Yes, on Stripe. Stripe's docs say MPP supports card payments through Shared Payment Tokens, scoped grants that let an agent use a customer's card, with a minimum charge of 0.50 USD.

Do I need a crypto wallet to accept MPP payments?

No. Stripe's MPP endpoint supports card payments through Shared Payment Tokens by default. Stablecoin payments are an extra step, using a deposit address Stripe creates for you.

Sources

  1. Stripe blog: Introducing the Machine Payments Protocol · checked 17 Nov 2026
  2. Stripe Docs: MPP · checked 17 Nov 2026
  3. Stripe Docs: Machine payments · checked 17 Nov 2026
  4. Stripe Docs: x402 · checked 17 Nov 2026
  5. MPP: Machine Payments Protocol · checked 17 Nov 2026
  6. MPP: What is MPP? · checked 17 Nov 2026
  7. MPP: Frequently asked questions · checked 17 Nov 2026
  8. MPP: Governance · checked 17 Nov 2026
  9. MPP blog: Expanded identity primitives · checked 17 Nov 2026
  10. IETF Datatracker: draft-httpauth-payment, The "Payment" HTTP Authentication Scheme · checked 17 Nov 2026
  11. Visa: Visa Opens the Door to AI-Driven Shopping for Businesses Worldwide · checked 17 Nov 2026
  12. Linux Foundation: Operational launch of the x402 Foundation · checked 17 Nov 2026

Written by The Sill Signals Team. Last reviewed 17 Nov 2026.

Share this articleLinkedInXBlueskyEmail

Keep reading

See which AI agents visit your site, and decide what they may do.

Scan your site free