NewSarvex is now open source — Apache-2.0 →
All posts
Signal

Stripe's Agentic Commerce Playbook

Stripe made the widest bet in agentic commerce — ACP, the Link Agent Wallet, MPP, and x402, stitched into one stack. Here is the playbook, and its risk.

Matt
MattFounder, Sarvex
Updated October 8, 20264 min read

OpenAI and Google get the headlines in agentic commerce. But if you follow the money layer, one company keeps showing up in almost every story: Stripe.

Here is the thing I find interesting. Stripe did not pick one protocol and defend it. It placed a bet on nearly every layer at once, then wired them together. That is a different kind of strategy, and it is worth understanding — whether you compete with Stripe, build on it, or just want to see where this is heading.

So here is the playbook, piece by piece.

The five pieces

As of late April 2026, Stripe ships five parts that lock together:

  • The Agentic Commerce Suite — the merchant side. One integration that exposes a business catalog to AI agent surfaces.
  • ACP (Agentic Commerce Protocol) — the wire protocol underneath the Suite, co-developed with OpenAI and released 29 September 2025.
  • The Link Agent Wallet — the consumer side. A one-time virtual card per agent task, with user approval per transaction.
  • MPP (Machine Payments Protocol) — co-authored with Tempo, launched 18 March 2026, for agent-to-agent and API billing.
  • x402 support — added February 2026, for stablecoin settlement in USDC on Base and other chains.

Four of these — the Suite, ACP, MPP, and the Link Agent Wallet — became generally available together around late April 2026. That is not a series of experiments. That is a stack.

The clever part: Shared Payment Tokens

The glue is a small idea called the Shared Payment Token (SPT). It is a single-use credential, tied to one specific merchant and one specific amount, time-limited.

Why this matters: the agent never holds your real card. It holds a token that can only do one thing, once. That is the kind of design a payments person smiles at, because it shrinks the blast radius if something goes wrong. It is also the quiet reason Stripe can offer the same payment primitive across cards, stablecoins, and buy-now-pay-later.

At its Sessions event in April 2026, Stripe wired MPP into its standard Payment Intents API. Translation: any business already on Stripe can accept agent payments — in stablecoins or fiat — without rebuilding anything. That is a huge distribution advantage, and it is easy to miss.

Why the "widest bet" works

Most players are picking a lane. Coinbase owns the crypto-native rail with x402. OpenAI owns the agent surface. Google owns search and AP2 authorization.

Stripe's move is different. It sits underneath all of them:

  • It co-authored ACP with OpenAI.
  • It reportedly interoperates with Google's AP2 through Visa's Intelligent Commerce Connect.
  • It settles the actual payments either way.

So no matter which agent surface or checkout protocol a merchant chooses, the money can still run through Stripe. When you are the layer everyone else needs, you do not have to win the protocol war. You just have to be present in it. That is a strong position.

The risk in the playbook

I want to be fair here, because a playbook is not a guarantee.

The obvious risk is lock-in worry. MPP is "co-authored by Stripe and Tempo," and Tempo is a Stripe-adjacent chain. For builders who distrust lock-in, the more neutral x402 is the safer default — and plenty of them say so openly. Stripe's answer is to support x402 too, which is smart, but the tension is real: a company that is present on every layer can start to feel like a company you cannot avoid.

There is also the plain fact that early agent-payment volume is still small and noisy. Being everywhere in a market that is still forming is powerful only if the market actually arrives at the size the forecasts promise.

What to take from it

If you are building in this space, Stripe's playbook is a lesson worth copying in spirit, even if you are nowhere near its size: do not bet the house on one protocol winning. The stack is still moving. The safe position is to speak more than one protocol and keep your own core — your data, your logic — independent of any single one. Be useful on whichever rail the customer chose.

That is the real takeaway from watching Stripe. Not "Stripe wins," but "the layer that stays flexible wins."

For how these protocols fit together, see the agentic commerce protocol stack. For the other companies in the race, see the agentic commerce landscape.

Sources and further reading

Note: Stripe's agentic products and their status change often. Please check Stripe's own newsroom and docs above before relying on a specific feature or date.