Stripe plays three distinct roles in the Machine Payments Protocol (MPP), and most coverage misses two of them. The company co-authored the open standard alongside Tempo, but its contribution extends far beyond simply processing credit card transactions. Stripe serves as a payment rail, a compliance infrastructure layer, and the maintainer of developer tools that make the protocol accessible to millions of businesses already on its platform.

What Exactly Is the Machine Payments Protocol?

The Machine Payments Protocol is an open standard that launched in March 2026, enabling AI agents to pay for digital services autonomously within a single HTTP request, with no account signup, no checkout flow, and no human approval required. The protocol replaces traditional checkout flows with a challenge-credential-receipt cycle embedded directly in HTTP requests. Think of it as a way for AI agents to buy things on the internet the same way humans do, except the entire transaction happens in the background without any human clicking a button.

MPP is not a Stripe product. Instead, Stripe is one payment rail within a multi-rail ecosystem. Tempo handles stablecoin payments, Lightspark manages Bitcoin Lightning transactions, and Stripe handles fiat card settlement. All three can be advertised on the same endpoint simultaneously, giving agents multiple payment options.

How Does Stripe Actually Process Payments Without Human Approval?

The process works through a six-step cycle that completes in a single round trip for one-time payments. An agent sends a standard HTTP request to a resource. The server responds with a 402 Payment Required status and payment terms in the header. The agent evaluates the challenge against its pre-set spending policy. If approved, the agent presents a Stripe Shared Payment Token (SPT), a one-time merchant-scoped token, in the Authorization header. The server confirms the SPT, processes the charge via Stripe, and returns the resource. Finally, the response includes a Payment-Receipt header referencing the completed PaymentIntent.

For high-frequency use cases such as continuous API calls, token streaming, and compute metering, MPP supports a session model. The agent pre-authorizes a spending cap once, then streams micropayments using lightweight off-chain vouchers. Settlement batches periodically, achieving sub-100 millisecond latency and near-zero per-request fees. This session primitive is what makes sub-cent billing, as low as $0.001 per API call, economically viable for the first time.

What Three Roles Does Stripe Play in MPP?

• Payment Rail Provider: When an API server accepts card payments through MPP, Stripe handles the actual charge. The agent presents a Shared Payment Token, and Stripe processes it as a standard PaymentIntent. The transaction settles into the merchant's existing Stripe balance on their normal payout schedule.
• Compliance and Fraud Layer: Every MPP transaction routed through Stripe inherits Stripe Radar fraud detection, automatic tax calculation, refund processing, and accounting integrations. This enterprise-grade infrastructure is something most crypto-native payment protocols simply do not have.
• SDK and Tooling Maintainer: Stripe maintains the mppx SDK, available in TypeScript, Python, and Rust, and the official MPP documentation at docs.stripe.com/payments/machine/mpp. Stripe's developer tooling is what makes MPP accessible to the 5 million plus businesses already on its platform.

What Makes Stripe's MPP Implementation Unique?

Stripe's specific contribution to MPP is fiat-native settlement with enterprise-grade controls, something no other agent payment protocol currently offers in the same package. An API server can advertise stablecoins, fiat cards, and Bitcoin simultaneously in the same 402 response, allowing the agent to select based on its own wallet and policy. No other agent payment protocol currently enables this combination on one endpoint.

Because Stripe processes the actual charge, merchants get inherited infrastructure including fraud detection via Stripe Radar, automatic tax calculation, refund and dispute handling, dashboard reporting identical to standard Stripe payments, and existing payout schedules with no new settlement infrastructure needed. Stripe's MPP implementation also supports transaction values as low as $0.001, enabling granular billing for compute-heavy agent workflows where billing per token, per request, or per millisecond is the only accurate model.

Who Is Already Using Stripe MPP?

MPP launched on March 18, 2026 with over 100 integrated services from day one. By mid-2026, the network had grown to 3,700 plus indexed servers and surpassed 1.1 million transactions. Early adopters span developer infrastructure, physical goods, and enterprise platforms.

• Developer Infrastructure: Browserbase lets AI agents spin up and pay for headless browser sessions per use. Alchemy and QuickNode offer pay-per-request blockchain data access. fal.ai charges per image generation request. Parallel Web Systems lets agents pay per API call for web research.
• Enterprise Integration: Visa built a CLI tool enabling real card transactions over MPP within days of seeing the spec. Cloudflare added native MPP support to its Agents SDK. Twilio was the first major platform to integrate MPP at launch. Anthropic, OpenAI, and Shopify serve as design partners.
• Physical Commerce: PostalForm lets agents pay to print and send physical mail. Prospect Butcher Co. accepts sandwich orders from agents with New York delivery. This spread from developer infrastructure to physical goods signals that MPP is not being positioned as a niche protocol for crypto-native APIs.

Stripe processed $1.9 trillion in total payment volume in 2025, a 34 percent year-over-year increase. MPP sits at the leading edge of Stripe's bet that a growing share of that volume will originate from machines rather than humans.

How to Evaluate MPP for Your Business

• Assess Your Payment Frequency: If your business involves high-frequency micropayments or per-request billing, MPP's sub-cent transaction support and session model eliminate the infrastructure barriers that previously made such pricing economically unfeasible.
• Consider Multi-Rail Requirements: If you want to accept payments from AI agents using different settlement methods, MPP's ability to advertise stablecoins, fiat cards, and Bitcoin on the same endpoint provides flexibility that traditional payment processors do not offer.
• Evaluate Compliance Needs: If your business requires fraud detection, tax calculation, and refund handling, Stripe's inherited infrastructure within MPP provides enterprise-grade controls without requiring you to build custom compliance layers.

The emergence of MPP represents a fundamental shift in how machines will conduct commerce. By embedding payment logic directly into HTTP requests and supporting sub-cent transactions, the protocol removes operational barriers that have forced businesses to rely on subscription pricing for decades. Stripe's role as payment rail, compliance layer, and SDK maintainer positions the company at the center of this transition, making its infrastructure the default choice for businesses seeking to accept payments from AI agents.