AI Agents Can Finally Pay: Stripe MPP and the New Payment Rails

AI agents can reason, plan, and execute multi-step tasks — but until recently, every transaction still required a human at checkout. Two competing protocols are changing that now.

Context

The payment infrastructure underpinning modern commerce was designed for human principals. A person authenticates, authorizes, and confirms each transaction. That model breaks when the principal is an AI agent operating autonomously. An agent that can book a service, spin up cloud resources, purchase API credits, or route a payment between vendors has been hitting the same wall: no standardized way to transact without routing control back to a human approval step.

This gap has become urgent as agentic AI systems mature beyond prototypes. Bedrock AgentCore and similar platforms have given agents the execution infrastructure they need; OpenAI’s Symphony has given them the coordination layer. Payment capability was the remaining structural gap — the one that kept agents tethered to a human at the point of settlement.

The Detail

Stripe’s Machine Payments Protocol (MPP) is an open standard co-developed with Tempo that specifies how software agents should initiate and settle payments programmatically. The core primitive is the Shared Payment Token (SPT): a credential that an agent holds and presents to a merchant’s MPP-enabled endpoint, triggering settlement without a human checkout flow. Stripe exposes MPP through its existing PaymentIntents API in a few lines of code, with transactions appearing in the standard Stripe Dashboard using normal settlement cycles. Payment methods span stablecoins and fiat, with buy now, pay later support available.

Real deployments show the spectrum of use cases. Browserbase allows agents to pay per headless browser session — a per-use microtransaction that would be impractical to approve manually at scale. PostalForm lets agents pay to print and send physical mail. Prospect Butcher Co. enables agents to order food for human delivery in New York City. These aren’t demos — they’re live merchant integrations already running over MPP.

iWallet, a fintech startup, launched its Autonomous Settlement Protocol (ASP) in parallel, targeting the same infrastructure gap with a different architecture. Where MPP is anchored to Stripe’s existing payment graph, ASP is designed for multi-party autonomous settlements — more relevant for agentic workflows involving agents transacting with each other rather than with human merchants, and for stablecoin-native settlement across complex multi-agent systems.

The simultaneous emergence of two protocols from different parts of the ecosystem signals that this is no longer a niche problem. Payment capability is a prerequisite for any autonomous agent operating in a world where services cost money.

Source: Stripe

Content created with AI assistance and reviewed for accuracy.