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

What was announced at Stripe Sessions 2026

Stripe Sessions 2026 drew over 9,000 attendees to Moscone Center on April 29–30. Under the slogan “economic infrastructure for the AI era,” Stripe released 288 launches; co-founder John Collison and data and AI lead Emily Sands presented the keynote “Indexing the economy,” surfacing data that “agents have emerged as a new economic actor.”

If you pick one item with the most weight, it's the Machine Payments Protocol (MPP). The standard for payment moving from “a button a human clicks” to “an API the agent calls” was unveiled here. (Stripe Blog — Everything we announced at Sessions 2026, Stripe Newsroom — 288 launches)

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.

Browserbase (a headless browser for agents)

Every time an agent spins up a headless browser session, payment is settled per session automatically — no humans entering card data or handling invoices.

PostalForm (a postal-mail API for agents)

The agent finishes the digital decision and then executes the physical postal action right after. A clean example of how MPP works across the boundary from digital payment into physical action, not just digital-only flows.

Prospect Butcher Co. (autonomous sandwich ordering)

The agent compares menu, picks price and pickup or delivery options, and then closes payment via MPP. Only the final pickup-or-delivery choice is left to the human.

Parallel Web Systems (a web search and research API for agents)

Every call to Parallel's search and research API is metered and auto-paid per call. A real-world example of micropayments running while AI agents browse the web on a human's behalf.

Parag Agrawal, founder of Parallel Web Systems, said the team integrated Stripe payments in just a few lines of code, and now agents autonomously pay per API call to access the web.

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.

Important update — April 14, 2026

Visa joined as an anchor validator on Tempo. A card network has stepped directly into a blockchain outside the card rails as a validator-node operator — and the fraud and dispute trust the card network built carries through to the Tempo chain.

Sources: CoinDesk — Visa to operate an anchor validator on Stripe's Tempo blockchain, PYMNTS — Visa teams with Stripe on agent payments

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.

01 Discovery — the agent brings your brand out as the answer

Users type natural language into ChatGPT, Perplexity, Google Gemini, Google AI Mode or Microsoft Copilot, and AI narrows down a shortlist of brands and products. If you don't make it out as the answer, no payment ever starts. This is the narrowest bottleneck of the zero-click era and the inlet of the funnel that flows all the way through MPP.

Checklist

• Apply Product, Organization, Offer and FAQPage JSON-LD to brand and product pages (Schema.org standard)

• Reorganize specs, ingredients, usage and sizes on product detail pages as AI-readable tables

• Explicitly allow AI crawlers (GPTBot, PerplexityBot, ClaudeBot, Google-Extended) in robots.txt and llms.txt

• Measure brand citation rate and Share of Voice for long-tail queries

• Monitor rank and mention sentiment vs. competitors inside AI answers

02 Transaction — the agent completes payment inside the conversation

This is the stage MPP newly defines. The user closes the purchase without leaving the agent screen. The agent pays via SPT or a Tempo stablecoin; merchants see the transaction in their usual Stripe Dashboard (processed via PaymentIntents API and settled on the normal payout schedule). Micropayments at four cents per API call and ordinary e-commerce checkouts flow over the same protocol.

Checklist

• Ensure real-time consistency in product catalog data (variants, inventory, pricing)

• Document idempotency, retries and refund policy so the agent can call payments safely

• Audit integration paths for Stripe Agentic Commerce Suite and for Shopify, Wix, BigCommerce and WooCommerce

• Review global payment routing scenarios with Korean PGs (Toss Payments, KG Inicis, NICE Payments)

• Check that you have a digital asset, content or API priced sensibly for micropayments (cents-level)

03 Post-purchase — the agent guides CS and re-purchase

After the agent finishes payment, tracking, refunds, exchanges and re-purchase need to live in the same flow. If your order, CRM, shipping and CS data are disconnected here, the customer experience breaks and LTV drops. And without a feedback loop to correct mistakes the agent made, long-term Share of Voice erodes.

Checklist

• Keep order/shipping status APIs consistent with CS channels (KakaoTalk channels, email, in-app chat)

• Redesign loyalty, membership and points around agent-payment scenarios

• Make re-purchase trigger events (replenishment, seasonality, bundles) legible to agents

• Build a real-time loop to detect and correct misinformation the AI gave out

• Structure reviews, ratings and UGC via Schema.org Review/AggregateRating and keep them current

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.”

Three conditions to close the citation → payment loop

• ① AI legibility. Product data and content have to be structured so the agent picks you as the real answer. Schema.org Product, Organization, Offer and FAQPage are the basic qualification.

• ② Measurability. You have to know which queries got you cited by which agents. Citation rate, Share of Voice and mention tone become the KPIs.

• ③ Payability. Once cited, the user has to be able to walk to payment without friction. Agentic Commerce Suite, Shopify/Wix/WooCommerce integrations, and idempotency-and-retry handling in your own checkout matter.

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.

Frequently asked questions

What is the Machine Payments Protocol (MPP)?

MPP is an open payments protocol jointly built by Stripe and Tempo, released on March 18, 2026. It is a specification for AI agents and services to send and receive payments without a human in the loop. Its most distinctive trait is that one protocol carries both stablecoin payments (on the Tempo chain) and fiat methods (cards, Klarna, Affirm — via the Stripe Shared Payment Token). At launch, four real use cases shipped alongside it: Browserbase, PostalForm, Prospect Butcher Co., and Parallel Web Systems.

What was unveiled at Stripe Sessions 2026?

On April 29–30, in San Francisco's Moscone Center, Stripe rolled out 288 new products and features all at once. The headline theme was “economic infrastructure for the AI era.” Under that umbrella sat MPP, the Link agent wallet, the general release of Stripe Projects, Streaming Payments, Checkout Studio, Bridge Open Issuance, and partnerships with Google, Meta and Amazon AgentCore. Attendance topped 9,000; the keynote, “Indexing the economy,” was delivered by co-founder John Collison and data and AI lead Emily Sands.

How does GEO (Generative Engine Optimization) connect to MPP?

GEO is the layer where AI is made to cite and recommend the brand. MPP is the layer where the agent completes payment right where it cited you. The two stack: before AI brings you out as the answer to a query, you need structured data and content authority; only then can MPP add transaction layers like micropayments, recurring payments and stablecoin payments and make “agent pays” real. Wire up MPP without a GEO foundation and the payment never starts — because you weren't on the recommendation list.

How is MPP different from other agentic payment standards like UCP and x402?

“Different layer” is the more accurate framing than “different feature.” Google's Universal Commerce Protocol (UCP) defines commerce-domain transaction rules end-to-end — catalog, identity, checkout. The Coinbase-led x402 is a stablecoin payment standard built on the HTTP 402 response code. MPP sits in between as the payment execution layer. Its key distinction is that one protocol contains both stablecoin (Tempo) and fiat (SPT) rails. At Sessions 2026, Stripe paired with Google to route payments inside AI Mode and the Gemini app through UCP, and AWS Bedrock AgentCore Payments uses the Stripe Privy wallet as a payment connection. Stripe is building the bridges between the protocols at the same time.

What can Korean brands prepare for right now?

Start with five things. (1) Verify that variants, inventory and pricing in your product catalog stay consistent in real time across your own store, marketplaces and feeds. (2) Use Google Rich Results Test to verify that Product / Offer / Organization / FAQPage JSON-LD are applied to every page per Schema.org. (3) Update llms.txt, robots.txt and sitemap.xml so AI crawlers (GPTBot, PerplexityBot, ClaudeBot, Google-Extended) are explicitly allowed. (4) Measure how your brand and products actually appear in Google AI Mode, ChatGPT, Perplexity and Gemini. (5) For the coming agent-payment scenarios, document idempotency, retries and refund flows across your API, checkout and CS. Villion supports (4) out of the box.

Does our brand feel the impact immediately now that MPP has launched?

Honestly, not yet. MPP just launched; the early use cases attached first to digital-asset payments (APIs, MCP servers) and infrastructure-style services like Browserbase and PostalForm. For ordinary D2C brands, the moment when “the agent completes payment on our store” becomes real probably lands in the 6–12 month window as Google UCP, Stripe's Agentic Commerce Suite and Amazon Bedrock AgentCore each hit GA. But the gap between “prepared brands” and “unprepared brands” at that point will widen faster than it did in the SEO era. The reason is simple: once an agent narrows the shortlist and learns from it, the result gets reused for other users.

How do Stripe Privy, Tempo and Link CLI relate?

Three layers of the agent-payment infrastructure. Tempo is a payments-purpose blockchain sponsored by Stripe and Paradigm; its mainnet went live in March 2026, and Visa joined as an anchor validator on April 14. Privy is the non-custodial wallet infrastructure Stripe acquired, letting users or agents hold and move digital assets including USDC across 150+ markets. Link CLI is the developer tool that lets users delegate the Stripe Link wallet (200M+ consumers) to an agent via OAuth — the agent then pays with a one-time SPT (Shared Payment Token) instead of a raw card. In short: Tempo is the chain, Privy is the wallet, Link CLI is the delegation interface.

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