Stripe's MPP — the Standard That Lets Agents Complete the Payment

What is the Machine Payments Protocol (MPP)

MPP is an open payments protocol co-built by Stripe and Tempo, released on March 18, 2026. It is a spec for AI agents and services to exchange payments without a human in the loop. Legacy payment APIs assume a person inputs a card and presses a button; MPP begins from the assumption that the agent takes authentication, amount, currency and merchant constraints and pays.

MPP isn't a new payment network — it's a protocol layer laid in for the agent era. The biggest difference today is that one spec carries both digital assets (stablecoins) and fiat (cards, BNPL). (Stripe Blog — Introducing the Machine Payments Protocol, Forrester — MPP signals a turning point for micropayments)

Why this launch is called an inflection point

For a decade, the grammar of digital commerce was simple: search, click a result, type a card on the landing page, pay. That grammar has been shaken twice already. First when more than half of searches ended without a click — the zero-click era. Then when AI started giving the answer directly with generative search. Spring 2026 brought the third shake — payment closing right there inside the answer is now standardized.

The reason MPP is called an inflection point is that Stripe took all the hard parts of agent payments onto itself. Until now, teams building agent payments had to solve card data storage, fraud and dispute handling, refund and settlement accounting one by one. MPP rolls all three bundles onto existing financial infrastructure (Stripe, Tempo, Visa) and collapses them into “just call the protocol.” The era of differentiating by building payments infrastructure from scratch closed; competition moves up a layer to “which brand does the agent bring out as the answer.”

• Cents-level micropayments started to make sense for the first time. Stablecoins on the Tempo chain bring transaction cost close to zero, so pricing models like “four cents per API call” or “two cents per piece of content” actually flow.
• Agents started carrying cards. Layered on top of Stripe Link's 200M+ consumer base, Link CLI and SPT establish the pattern of “the user authorizes once, the agent pays repeatedly with one-time tokens.”
• Fraud and dispute handling stay with the existing card rails. SPT settles to a final card payment, and Stripe Radar plus validator nodes on Tempo (Visa) screen for fraud. A new standard — but the trust infrastructure itself isn't rebuilt.

Related reading: Five conditions for the zero-click era and Google UCP and Agentic Commerce.

The four launch partners and where they run

Stripe's choice of launch partners alongside MPP shows clear intent. A headless browser (Browserbase), physical postal mail (PostalForm), food ordering (Prospect Butcher Co.), and a web search and research API (Parallel Web Systems) — picked to show both the areas agents will repeat most and the boundary “from digital into physical action.” A feature for automatic donations to Stripe Climate per transaction was also demoed.

The Browserbase case in particular is proof that a B2B micropayment market — agents calling other agents' infrastructure and paying automatically — is already running. It looks distant from a typical D2C brand, but it's also the moment that reframes your own APIs, content and MCP servers as assets agents pay to call.

Tempo blockchain and Visa as anchor

The stablecoin side of MPP runs on a payments-purpose blockchain called Tempo. Backed by Stripe and Paradigm, the mainnet went live in March 2026, adopting MPP as its native payment protocol. The reason for spinning up a new chain is straightforward: payments traffic needed its own consensus structure and fee model. General-purpose chains like Ethereum or Solana carry too much non-payment traffic to drive micropayment unit cost down reliably.

The message to brands is clear. Stablecoins are no longer a fringe experiment. The heavy parts — fraud handling, dispute resolution, settlement — are already carried by existing financial infrastructure, and brands don't have to think about currency or chain. The transaction shows up in the Stripe Dashboard like any other.

The Link agent wallet and SPT

If MPP is the protocol, the Link agent wallet is where ordinary consumers meet it first. Stripe Link already stores payment information for 200M+ users worldwide; Sessions 2026 added “agent delegation.” Users delegate the Link wallet to an agent via OAuth, and the agent pays with a one-time SPT (Shared Payment Token) instead of the original card on every transaction.

SPT comes with usage constraints baked in — amount, currency, merchant. The card number doesn't leave Link, so the agent cannot swipe arbitrary amounts at arbitrary merchants. At launch, every payment request requires explicit user pre-approval; Stripe says it will progressively open user-configurable spending limits and auto-approval rules.

For developers, Link CLI is the fastest entry point. A single command — link-cli spend-request create — produces a request containing payment method, merchant, amount and transaction context; once the user approves, the agent completes payment with SPT. It's the “the agent carries the card” interface, directly.

Sources: Stripe Blog — Giving agents the ability to pay, GitHub — stripe/link-cli, Stripe Docs — Agents

Deal map — Stripe × Google × Meta × AWS

MPP isn't a standard Stripe carries alone. At Sessions 2026, Stripe built payment bridges to three large platforms at the same time — each bridge defines a path from a surface where the agent meets the user into the payment track.

In short, Stripe is laying payment tracks under every surface where agents meet users, simultaneously. Whether the user starts on Gemini, on a Facebook ad, or via an enterprise's own agent calling APIs in the background, payment runs on the same Stripe infrastructure. From the brand's side, the question “which platform do we have to line up behind?” gets less urgent.

Sources: AWS ML Blog — Bedrock AgentCore Payments with Coinbase and Stripe, PYMNTS — Stripe brings merchant checkout to Google's AI apps

Where MPP sits inside agentic commerce

Stripe splits commerce into five steps by the depth of agent autonomy. Step 1 is payment-form auto-fill (Meta's in-app checkout is the representative case). Step 2 is shopping assistance (ChatGPT inferring conditions like “a gift for a 38-year-old brother, $100 budget, uncommon sporting goods” and presenting candidates). Steps 3–5 are autonomous payments where the agent decides and executes on its own. From the brand side, those five steps regroup into three flows.

GEO → MPP — closing the loop from citation to payment

GEO and MPP get discussed separately, but in the real user journey they form one closed loop. The step where the agent brings your brand out as the answer is GEO; the step where that answer flows straight into payment is MPP. Either alone doesn't produce revenue. No citation, no payment to make. No payment track, and you get “recommended but the transaction happens elsewhere.”

Villion automates the first two stages of this loop — measuring how accurately AI knows your brand and hardening page structure and data layers so citations rise. Stage three, the payment track, is already laid down by Stripe, Shopify and your own PG. What brands need to chase first is being in a state to be cited.

Strategic choices for Korean brands

MPP is a U.S.-originated standard running on global payment infrastructure — Tempo, Visa, Stripe. It can feel distant from Korea right now, but three reasons to prepare from today. The AI surfaces Korean consumers use most (ChatGPT, Gemini, Perplexity, Claude) are already plugged into global standards. Brands going global as D2C — K-beauty, K-fashion, K-food — need to be ready the moment an overseas user tries to “pay through an agent.” And Korean sellers on Shopify, Wix, BigCommerce or WooCommerce stand a strong chance of being auto-onboarded into the Agentic Commerce Suite path via platform updates alone.

Related reading. What is GEO?, Five conditions for the zero-click era, Google UCP and Agentic Commerce, E-commerce AI visibility strategy.

FAQ

Frequently asked questions

Primary references

• Stripe Blog — Introducing the Machine Payments Protocol
• Stripe Blog — Everything we announced at Sessions 2026
• Stripe Newsroom — Stripe builds out the economic infrastructure for AI with 288 launches
• Stripe Blog — Giving agents the ability to pay
• Stripe Sessions 2026 — Indexing the economy
• Stripe Sessions 2026 — Machine payments and the protocols behind agentic commerce
• Stripe Docs — Add Stripe to your agentic workflows
• GitHub — stripe/link-cli
• CoinDesk — Stripe-led Tempo blockchain goes live
• CoinDesk — Visa operates anchor validator on Tempo
• PYMNTS — Visa teams with Stripe on agent payments
• AWS ML Blog — Bedrock AgentCore Payments
• PYMNTS — Stripe brings merchant checkout to Google's AI apps
• Forrester — Why MPP signals a turning point for micropayments
• Coresight Research — Agentic payments are open for business
• Constellation Research — How Stripe sees agentic commerce developing