# Machine Payments Protocol (MPP)

> An open, HTTP-native standard co-authored by Stripe and Tempo that lets an agent request, authorize and settle a payment within the same HTTP request.

_The Agentic Web Lexicon · /glossary/mpp · [JSON](/api/glossary/mpp) · [all The Agentic Web Lexicon](/glossary)_

- **term:** Machine Payments Protocol (MPP)
- **category:** commerce
- **short_def:** An open, HTTP-native standard co-authored by Stripe and Tempo that lets an agent request, authorize and settle a payment within the same HTTP request.
- **long_def:** MPP is an internet-native machine-to-machine payment standard, proposed to the IETF, that lets agents pay for services inline across stablecoins, cards and other methods using Shared Payment Tokens (SPTs). Businesses configure spend limits, merchant-category restrictions and approval workflows in advance, so agents transact only within explicitly granted permissions.
- **see_also:** x402, agentic-commerce, ap2
- **etymology_origin:** Co-authored by Stripe and Tempo and announced on 18 March 2026; an open machine-to-machine payment standard built on HTTP and Shared Payment Tokens (SPTs).
- **related_to:** x402, agentic-commerce, ap2, ucp
- **contrast_with:** Unlike x402, which settles natively in stablecoin over the HTTP 402 status, MPP is method-agnostic — it coordinates stablecoins, cards and BNPL through Shared Payment Tokens within the same HTTP request.
- **example:** Stripe and Tempo announced the Machine Payments Protocol on 18 March 2026; named launch adopters include Browserbase, PostalForm and Prospect Butcher Co.
- **source:** https://stripe.com/blog/machine-payments-protocol
- **status:** emerging
- **why_it_matters:** MPP gives a business one inline, permissioned rail to accept agent payments across stablecoins and cards, with budgets and merchant rules enforced before the agent ever transacts.
- **sameAs:** —
- **bridge_entity:** protocols/payments/mpp
- **last_verified:** 2026-06-15
- **md_twin:** /glossary/mpp.md