Stripe / TempoMilestone

Stripe and Tempo Launch Machine Payments Protocol: An Open Standard for Agent-to-Service Payments

Published 18 March 2026Last Updated 28 March 202611 min read
Read original source

Key Takeaways
  • Stripe and Tempo launched the Machine Payments Protocol (MPP) - the third major payment protocol in the agentic commerce stack, alongside ACP and x402. MPP enables agents and services to coordinate payments programmatically without human interfaces.

  • The protocol reduces commerce to its essence: request, price, pay, deliver. Shared Payment Tokens (SPTs) provide programmable, time-limited, context-bound authorisations - the financial implementation of delegation design.

  • Over 100 services listed in the MPP directory at launch, from headless browsers to sandwich shops, demonstrating the long tail of the agent economy is already forming.

  • The protocol proliferation problem is intensifying: merchants must now navigate ACP, MPP, x402, UCP, and network-specific protocols simultaneously. Multi-protocol readiness is becoming a structural requirement.

  • Visa's endorsement of MPP for card-based payments signals that card networks are becoming protocol-agnostic trust layers rather than building walled gardens.


AXD Analysis

Stripe and Tempo's Machine Payments Protocol (MPP) is the third major payment protocol to emerge in the agentic commerce stack - alongside Stripe's own Agentic Commerce Protocol (ACP) and the x402 HTTP-native payment protocol. MPP provides a specification for agents and services to coordinate payments programmatically, enabling microtransactions, recurring payments, and agent-to-service commerce. The protocol's design is architecturally significant: an agent requests a resource from any HTTP-addressable endpoint, the service responds with a payment request, the agent authorises payment, and the resource is delivered. This is commerce reduced to its protocol-level essence - request, price, pay, deliver - with no human interface required at any step. Stripe businesses receive MPP payments through the same PaymentIntents API they use for human transactions, with the same fraud protection, tax calculation, and reporting infrastructure. The early adopters reveal the emerging agent economy: Browserbase (agents paying per browser session), PostalForm (agents paying to send physical mail), and Prospect Butcher Co. (agents ordering sandwiches for human pickup). The AXD discipline notes that MPP supports both stablecoins and fiat payments via Shared Payment Tokens - the same dual-rail approach the Institute identified as necessary for the protocol convergence phase. The protocol proliferation problem is intensifying: merchants must now navigate ACP, MPP, x402, UCP, and network-specific protocols simultaneously.


What is the Machine Payments Protocol and why does it matter?

What is the Machine Payments Protocol and why does it matter?

The Machine Payments Protocol (MPP), launched by Stripe and Tempo on 18 March 2026, provides a specification for AI agents and digital services to coordinate payments programmatically. It is the third major payment protocol to emerge in the agentic commerce stack, joining Stripe's Agentic Commerce Protocol (ACP) and the x402 HTTP-native payment protocol.

MPP's architecture is deliberately minimal: an agent requests a resource from any HTTP-addressable endpoint, the service responds with a payment request, the agent authorises payment, and the resource is delivered. This four-step sequence is commerce reduced to its protocol-level essence, with no human interface required at any point in the transaction.


How do Shared Payment Tokens work?

How do Shared Payment Tokens work?

MPP introduces Shared Payment Tokens (SPTs) - programmable, time-limited, context-bound authorisations that allow agents to spend within defined parameters. An agent receives scoped authority through an SPT, not raw credentials. The token specifies what the agent can purchase, how much it can spend, and for how long the authorisation remains valid.

This is the financial implementation of the AXD delegation design principle. The human principal defines the boundaries; the agent operates within them. If the agent attempts to exceed its SPT parameters, the transaction is rejected at the protocol level, not after the fact.


What does the early adopter landscape reveal?

What does the early adopter landscape reveal?

The early adopters listed in the MPP payments directory reveal the emerging shape of the agent economy. Browserbase enables agents to pay per browser session. PostalForm allows agents to pay to send physical mail. Prospect Butcher Co. enables agents to order sandwiches for human pickup. These are not demonstration projects - they are live commercial services accepting machine-initiated payments.

The diversity of use cases - from digital infrastructure to physical goods - demonstrates that agent-to-service commerce is not confined to a single vertical. The long tail of the agentic economy is forming across every category of commercial activity.

  • Browserbase: agents paying per browser session (digital infrastructure)

  • PostalForm: agents paying to send physical mail (physical services)

  • Prospect Butcher Co.: agents ordering sandwiches for human pickup (food and beverage)

  • Over 100 services listed at launch across multiple categories


How does MPP relate to the protocol proliferation problem?

How does MPP relate to the protocol proliferation problem?

The launch of MPP intensifies the protocol proliferation problem the AXD Institute has been tracking. Merchants must now navigate at least five distinct protocol standards: ACP (Stripe/OpenAI), MPP (Stripe/Tempo), x402 (Coinbase), UCP (Google), and network-specific protocols from Visa and Mastercard.

Stripe's strategic decision to support both MPP and x402 confirms the AXD observation that the agentic payment layer will be multi-protocol, not winner-take-all. The question is not which protocol wins but how the stack converges - and who provides the trust verification layer that sits above all protocols.


What does Visa's endorsement signal?

Visa's decision to support MPP for card-based payments across its global network is a protocol convergence signal. When the world's largest card network endorses an open payment protocol co-authored by a payment processor and an AI infrastructure company, the strategic direction is clear: card networks are positioning themselves as protocol-agnostic trust layers.

Rather than building walled gardens for agentic payments, Visa is becoming the trust verification layer that validates agent identity and authorises transactions regardless of which protocol initiated them. The infrastructure stack is crystallising: protocols at the application layer, card networks at the trust layer, and issuers at the authorisation layer.



Frequently Asked Questions

What is the Machine Payments Protocol (MPP)?

The Machine Payments Protocol (MPP) is an open standard launched by Stripe and Tempo that enables AI agents and digital services to coordinate payments programmatically. It uses a four-step sequence - request, price, pay, deliver - that requires no human interface. MPP introduces Shared Payment Tokens (SPTs) for programmable, scoped authorisations.

How does MPP differ from other agentic payment protocols?

MPP focuses on agent-to-service payments with streaming micropayment capabilities via Tempo's runtime. ACP (Agentic Commerce Protocol) handles broader agent-merchant commerce flows. x402 uses the HTTP 402 status code for chain-agnostic thin-layer payments. UCP (Universal Commerce Protocol) from Google focuses on discovery and full-cycle commerce. Each serves a different layer of the agentic commerce stack.

What is the protocol proliferation problem?

The protocol proliferation problem refers to the growing number of competing standards that merchants must support simultaneously - ACP, MPP, x402, UCP, and network-specific protocols. Rather than a single standard emerging, the agentic commerce infrastructure is forming a multi-protocol stack. Merchants need multi-protocol readiness, and card networks are positioning as protocol-agnostic trust layers above the application protocols.

Can MPP handle both crypto and traditional card payments?

Yes. MPP supports both stablecoins and fiat payments via Shared Payment Tokens. Visa has extended MPP to card-based payments across its global network, and Lightspark has extended it to Bitcoin Lightning. This dual-rail approach - supporting both traditional and crypto payment methods - is the architecture the AXD Institute identified as necessary for the protocol convergence phase.


About the Author
Tony Wood

Founder, AXD Institute

Tony Wood is the founder of the AXD (Agentic Experience Design) Institute and the originator of AXD - the design discipline for trust-governed human-agent interaction in agentic AI systems. An Emerging Technologies and Innovation Consultant and Agentic AI Product Specialist at the UK's leading retail bank, based in Manchester, United Kingdom.



Continue Reading

Return to the full intelligence feed for more curated analysis of the agentic commerce landscape.

All News & Intelligence