Machine Payments Protocol (MPP)

What is the Machine Payments Protocol (MPP)?

The Machine Payments Protocol (MPP) is a payment infrastructure protocol developed by Stripe and Tempo that enables AI agents and automated systems to execute payments programmatically across multiple payment rails. Launched on March 18, 2026, MPP provides a unified interface for agent-driven commerce, allowing AI systems to initiate, manage, and complete financial transactions without human intervention.

A useful analogy

Like a universal adapter for AI wallets — just as a travel adapter lets you plug your devices into different electrical outlets around the world, MPP lets AI agents plug into different payment networks (traditional rails, stablecoins, card networks) through a single interface.

How it works

1. Agent-initiated transaction: An AI agent identifies a need to make a payment (e.g., purchasing compute resources, paying for API calls, settling with another agent).
2. Payment rail selection: MPP determines the optimal payment rail based on factors like cost, speed, settlement finality, and merchant acceptance.
3. Multi-rail execution: The protocol can route payments through traditional card networks (Visa, Mastercard), stablecoin transfers, or direct bank transfers.
4. Settlement and confirmation: The payment settles on the chosen rail, and the agent receives confirmation of completion.

Key features

• Multi-rail architecture: Supports traditional payment rails, stablecoins, and emerging payment methods through a unified API.
• Agent-native design: Built specifically for autonomous systems rather than human-operated checkout flows.
• Visa integration: Visa developed specifications for credit/debit card payments by agents, with support announced on launch day (March 18, 2026).
• Paradigm partnership: Paradigm co-developed Tempo (the blockchain powering MPP) alongside Stripe; MPP was co-released by Paradigm, Stripe, and Tempo.
• Session-based authorization: Agents receive upfront spending limits and consume budget across multiple calls, with session expiry and limit enforcement.

Why it matters

MPP represents a critical infrastructure layer for the agentic economy. As AI agents become capable of autonomous decision-making, they need the ability to transact independently. MPP provides the payment rails that allow agents to purchase services, settle with other agents, and participate in economic activity on behalf of their users. This is essential for the growth of agentic commerce, where AI agents discover, negotiate, and complete transactions without human intermediation.

Common questions

How is MPP different from traditional payment APIs?
Traditional payment APIs are designed for human-operated checkout flows — they expect a human to click ‘buy’ and enter payment details. MPP is designed for autonomous systems. It can execute payments programmatically, route across multiple payment rails, and handle the complexities of agent-to-agent transactions that traditional APIs weren’t built for.

Can any business use MPP, or is it limited to Stripe customers?
MPP was developed by Stripe in partnership with Tempo (a blockchain incubated by Stripe and Paradigm), with Visa as a launch partner. While it leverages Stripe’s infrastructure, the protocol is designed to support the broader agentic commerce ecosystem. Businesses building AI agents or automated systems can integrate with MPP to enable their agents to make payments.

What payment methods does MPP support?
MPP uses a multi-rail architecture that supports traditional card networks (Visa support announced on launch day), stablecoin transfers, and direct bank transfers. The protocol automatically selects the optimal payment rail based on factors like cost, speed, and merchant acceptance.

Is MPP secure for autonomous payments?
MPP uses session-based authorization: agents receive upfront spending limits and consume budget across multiple calls, with session expiry and limit enforcement. Payments route through Stripe’s existing infrastructure, which includes fraud protection and reporting. Organizations needing additional approval workflows may require external control layers.