Stripe's agentic commerce stack is a bundle of related products that let AI agents buy from businesses, pay for APIs, and settle in stablecoins, all while the buyer's actual card stays out of the agent's hands. The pieces shipped over a six-month window: the Agentic Commerce Protocol with OpenAI in September 2025, the Agentic Commerce Suite in December 2025, x402 with USDC on Base in February 2026, the Machine Payments Protocol in March 2026, and the Link Agent Wallet at Sessions 2026 on April 29, 2026. This piece walks through each product, the mechanisms behind them, what is generally available versus what is in preview, and where Stripe's stack sits in the wider agentic commerce landscape.
​

Stripe ships five interlocking agentic commerce products: the Agentic Commerce Suite for merchants, the Agentic Commerce Protocol (ACP) on the wire, the Link Agent Wallet for consumers, the Machine Payments Protocol (MPP) for HTTP-addressable agent billing, and x402 for stablecoin settlement in USDC on Base, Solana, and Tempo.
​

Stripe ships five distinct agentic commerce products, each solving a different problem in the agent-payment lifecycle. The Agentic Commerce Suite is the merchant-side abstraction: a single integration that exposes a business catalog to AI agent surfaces. The Agentic Commerce Protocol (ACP) is the wire protocol underneath the Suite; it defines how an agent and a merchant negotiate a checkout. The Link Agent Wallet is the consumer-side wallet; it lets a user delegate spending to an agent through one-time cards and approval flows. The Machine Payments Protocol (MPP) is Stripe's open standard for HTTP-addressable agent billing. And x402 is the stablecoin path, where the agent pays in USDC over Coinbase's open x402 protocol.
​

Each product hooks into Stripe's existing PaymentIntents API. That matters because it means agent transactions land in the same Dashboard, with the same fraud signals, the same tax handling, and the same dispute machinery as a normal card payment. Stripe is not building a separate agent payment rail; it is grafting agent-native primitives onto the rail businesses already use.
​

The shape of the bundle reflects a strategy the Collison brothers spelled out in their 2026 annual letter: agentic commerce will arrive in stages, not as a single platform shift. Stripe is shipping the primitives that work at level one and two of that progression (a person specifying a purchase, then approving the agent's transaction) and previewing the pieces aimed at later stages where the agent acts more autonomously. For developers, the practical takeaway is that some of the surface is generally available today, and a meaningful portion is still gated to preview. The broader category context, including how ACP, MPP, and x402 sit alongside protocols from Google, Visa, Anthropic, and Coinbase, is covered in the agentic commerce primer.
​

Stripe Link Agents is a consumer-side feature of Stripe's Link wallet that lets users delegate spending to AI agents through real-time approvals, one-time-use cards, and scoped payment tokens. The user retains credential control while the agent receives a per-task token. Supported clients at launch include Claude, OpenAI agents, and custom agents.
​

Stripe announced the Link Agent Wallet at Sessions 2026 on April 29, 2026, with a dedicated landing page at link.com/agents. Link is Stripe's consumer wallet, which the company describes as having more than 250 million users globally. Agents enters the picture as a feature that lets those users delegate spending to AI agents without surrendering credentials.
​

The mechanism centers on three primitives. Real-time approvals run through the Link app: when an agent is ready to make a purchase, the user receives a notification and confirms the transaction. One-time-use cards and payment tokens are issued per task, so the agent never holds a reusable credential. Purchase history surfaces through the Link dashboard, giving the user an audit trail of every agent-initiated transaction.
​

The product page lists Claude, OpenAI agents, and "custom agents" as supported clients. Two capabilities are flagged as upcoming on link.com/agents itself: granular controls (so a user can pre-authorize categories of spending without per-transaction approval) and additional payment methods including digital currencies and what Stripe calls "next-generation protocols." The Sessions 2026 recap added Pix in Brazil and stablecoin acceptance to the live feature set, with UPI in India listed in preview. A third upcoming feature, saved preferences, lets agents read a user's purchase history to make better recommendations on repeat buys.
​

For now, the consumer-facing Link Agent Wallet primarily moves money over card rails. The Shared Payment Token mechanism is what hides the user's card from the agent, but the underlying settlement still runs through Visa, Mastercard, and the local-method networks Link supports. Stablecoin and crypto rails are listed as additions to the wallet, not the default path.
​

That choice tracks the actual behavior of the consumer side of agentic commerce. ChatGPT Instant Checkout, the highest-profile consumer agent surface, settled every transaction on cards through Stripe before OpenAI retired the feature in March 2026. Mastercard's Agent Pay rolled out across Citi and US Bank cardholders before opening to all US cardholders in late 2025; Visa's Trusted Agent Protocol launched on the card network. The consumer-side fight is happening on cards, not stablecoins, and Link Agent Wallet enters that fight from the wallet side rather than the network side.
​

The legal-language version of all this lives in the Stripe Services Agreement, which now carries sections for "Stripe Agentic Commerce Agent Services (Preview)" and "Stripe Agentic Commerce Seller Services (Preview)." Both are flagged as preview services in the agreement, which suggests Stripe is treating the consumer-side terms as still iterating even as the product is publicly available.
​

Stripe x402 is a preview integration that lets agents settle HTTP-addressable charges in USDC on Base, Solana, or Tempo using the open x402 payment-required protocol. Stripe issues temporary deposit addresses through PaymentIntents, and the agent signs an EIP-3009 or Permit2 payload. Today the path supports US businesses only.
​

Stripe added x402 support on February 10, 2026, with USDC on Base as the launch pair. The announcement came from Stripe product manager Jeff Weinstein and was reported by The Block the same day. As of April 2026, the integration remains in preview. The Stripe x402 documentation requires the 2026-03-04.preview API version and lists three USDC contracts: Base (`0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`), Solana (`EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v`), and Tempo (`0x20c000000000000000000000b9537d11c60e8b50`). US businesses are the only ones that can accept stablecoin payments through this path today.
​

The mechanism reuses x402's HTTP 402 model with Stripe-issued deposit addresses underneath. A developer creates a PaymentIntent with `mode: "deposit"` and `type: "crypto"`. Stripe returns a temporary deposit address along with the supported tokens for that network. The agent receives the address, signs a payload using EIP-3009 or Permit2 against the deposit contract, and sends the signed payload through the PAYMENT-SIGNATURE header. The server verifies the payment through a facilitator, then returns the resource. The whole exchange runs over standard HTTP, with no separate API key handshake on either side.
​

Stripe shipped purl alongside the x402 launch. purl is an open-source CLI tool for testing machine-payment endpoints. Running `purl http://localhost:3000/paid` makes an unauthenticated request, gets a 402 response, signs a payment payload, and returns the resource, all from one command. Sample integrations exist for Node.js (using `@x402/hono` and `@x402/core/server`) and Python.
​

Real-world endpoints already use it. CoinGecko activated x402 for its API in February 2026, charging $0.01 USDC per request for price and onchain data with no API key required. That ticket size is a useful calibration point: the entire stablecoin economy as of late April 2026 holds roughly $318 billion in supply, dominated by USDT at $189.5 billion and USDC at $77.3 billion (per DeFiLlama), but the typical x402 transaction is sub-cent. Stripe x402 was built for that regime, not for retail purchases.
​

The economics matter to the design. A card-rail charge typically costs the merchant 2.9% plus 30 cents through Stripe's standard processing; at a one-cent ticket, that pricing makes no sense. USDC on Base settles for fractional cents in network fees regardless of ticket size, and Stripe's machine-payments path skips the per-transaction processing fee on the stablecoin leg. The result is a developer surface where billing an agent for a single API call costs almost the same as billing for ten thousand calls, which is the whole point of the protocol. The same low-fee economics drive the broader category of stablecoin automation platforms, which agent-payment systems increasingly depend on for treasury and settlement work.
​

For a closer read on x402 itself, see the x402 protocol explainer. The article in your hands focuses on Stripe's specific integration and what it means for builders.
​

Machine Payments Protocol (MPP) is Stripe and Tempo's open standard for billing AI agents over HTTP. It sits one layer above x402: agents discover, request, and authorize payments across services, MCP endpoints, and APIs in stablecoins, cards, or BNPL, with funds settling through Stripe PaymentIntents and the merchant's standard Dashboard.
​

Stripe and Tempo released the Machine Payments Protocol (MPP) on March 18, 2026. MPP is an open standard for billing agents over HTTP. It sits one level up from x402: x402 defines the wire format for a payment-required handshake, while MPP defines how agents discover, request, and authorize payments across services, APIs, MCP endpoints, and any HTTP-addressable resource.
​

The mechanism is straightforward. An agent requests a resource. The service responds with a payment request that lists the price, the accepted methods, and the metadata. The agent authorizes payment using whatever method the service supports, which can include stablecoins, cards, Klarna, or Affirm through Shared Payment Tokens. Funds settle through Stripe PaymentIntents and appear in the merchant's standard Stripe Dashboard with the same fraud, tax, and accounting integrations as any other charge.
​

MPP is positioned as a multi-method protocol; x402 is one of its accepted payment methods, but not the only one. That distinction matters for developers: x402 alone is stablecoin-native and HTTP-402-shaped, while MPP can wrap a card-rail payment in the same agent-friendly request flow. A service can run MPP and accept either USDC over x402 or a Shared Payment Token from the Link Agent Wallet, depending on what the agent presents.
​

Tempo is the second author of MPP and a payments-focused L1 blockchain that went live in March 2026. Stripe's docs list USDC on Tempo alongside USDC on Base as a supported x402 token; the Sessions 2026 recap framed Tempo as the settlement chain for what Stripe calls streaming payments, where token-level usage on AI products is billed in real time against a stablecoin balance.
​

One implication for developers: MPP and x402 are not redundant. A team running x402 alone gets a stablecoin-only billing path. A team running MPP gets a billing surface that abstracts away the payment method, where the same endpoint can settle in USDC, in card-rail dollars through SPTs, or in BNPL through Klarna or Affirm. The trade-off is integration depth. x402 is HTTP-native and roughly 50 lines of middleware on the server side; MPP demands a Stripe account, a PaymentIntents integration, and the merchant's normal Stripe setup. For agent-to-agent payments where neither side is a registered Stripe merchant, x402 is the simpler path. For agent-to-business payments where the business already runs Stripe, MPP wins.
​

The Agentic Commerce Suite is Stripe's merchant-side bundle for selling across AI agent surfaces through one integration. It handles catalog upload, agent permissions, fraud signals, and the Agentic Commerce Protocol that ChatGPT, Gemini, and Claude speak. Launch merchants include Coach, Kate Spade, URBN, Revolve, Etsy, Wix, and BigCommerce.
​

The Agentic Commerce Suite shipped on December 11, 2025. Stripe describes it as "a low-code solution for businesses, letting them sell across AI agents with a single integration." The Suite handles the merchant side of the agentic commerce equation: catalog upload, agent-access permissions, fraud signals, and the wire protocol (ACP) that AI surfaces speak.
​

The merchant lineup at launch included Coach, Kate Spade, URBN (Anthropologie, Free People, Urban Outfitters), Revolve, Ashley Furniture, Halara, ABT Electronics, and Nectar on the brand side, with Etsy as the commerce platform. The Sessions 2026 update extended platform integration to Wix, BigCommerce, WooCommerce, Squarespace, and commercetools, which together cover most of the long tail of small and mid-sized merchants that do not run a custom Shopify build. The Suite is generally available; Stripe lists "platform support" (the path for connected accounts to inherit the Suite's capabilities) as still in preview at the time of Sessions 2026.
​

The Google partnership announced at Sessions 2026 extends the Suite to Google AI Mode and the Gemini app via Google's Universal Commerce Protocol (UCP). Quince, Fanatics, and JD Sports were named as upcoming launch merchants. The mechanism translates the Stripe Suite's ACP-shaped catalog into UCP for discovery inside Google's surfaces; the payment leg still runs through Stripe.
​

The Suite's underlying protocol is ACP, which Stripe and OpenAI co-developed and announced on September 29, 2025 alongside ChatGPT Instant Checkout. ACP defines the message flow between an agent and a merchant for product discovery, cart construction, and payment authorization. It uses Shared Payment Tokens as its credential primitive: the agent never sees the user's card, only a scoped token bound to one merchant and one purchase.
​

For a working list of which platforms speak which protocol and how the protocol layer composes, the cross-chain messaging protocol roundup covers an analogous landscape on the settlement side; the agentic commerce protocols are the consumer-side analogue. The agentic payments deep-dive goes further on the protocol composition.
​

The Agentic Commerce Suite, MPP, ACP, and Link Agent Wallet are generally available as of late April 2026. The x402 stablecoin path remains in preview, restricted to US businesses on three USDC contracts. Stripe's Google UCP integration is preview-only with launch merchants pending. Several Link wallet features ship over the coming quarters.
​

The fast launch cadence makes the live-versus-preview question harder than it looks. Stripe's own marketing collapses both into "now available" language; the legal terms tell a different story. The table below breaks out each product against its public status as of late April 2026.

OpenAI's retirement of Instant Checkout on March 24, 2026 is a useful data point. The feature, which used Stripe's ACP and SPTs end to end, never reached more than a small set of Etsy listings and a thin slice of Shopify merchants before OpenAI shifted to dedicated retailer apps inside ChatGPT (Walmart, Target, and Instacart at launch). The protocol survived; the consumer surface that pushed it did not. Stripe's response was to repackage the same primitives as the Agentic Commerce Suite (the merchant side) and the Link Agent Wallet (the consumer side), with each side independently usable across multiple agent surfaces.
​

Stripe is also an early implementer of Visa's Trusted Agent Protocol, which signs an agent's identity into HTTP request headers so merchants can verify that the request comes from a legitimate, user-authorized agent rather than a scraper. TAP solves the agent-side trust problem; ACP and SPT solve the credential-handling problem. The two compose: a TAP-signed request that carries an SPT through ACP gives the merchant both an authenticated agent identity and a scoped, fraud-monitored payment credential.
​

The catch is that none of this is symmetrical across markets. x402 is US-only on the merchant side. The Link Agent Wallet's stablecoin acceptance is generally available, but the broader Pix and UPI payment-method support varies by region. Sessions 2026 announced that Stripe stablecoin payment acceptance now covers 32 additional markets, but that figure measures the businesses Stripe can settle to, not the agent surfaces a merchant in those markets can sell into.
​

The five Stripe products share one PaymentIntents API, one Dashboard, and overlapping primitives like Shared Payment Tokens. A consumer flow runs over ACP and Link cards. A machine-to-machine flow runs over x402 in USDC. A mixed B2B flow runs over MPP, accepting either rail through the same agent-payment shape.
​

The five products above are not five separate stacks. They share the same PaymentIntents API, the same Dashboard, and overlapping primitives like Shared Payment Tokens.
​

A consumer-side flow looks like this. A user asks Claude to find and buy hiking boots under $200. Claude queries merchants over ACP through the Agentic Commerce Suite. The user's Link Agent Wallet receives an approval request. The user confirms in the Link app. Stripe issues a Shared Payment Token scoped to that merchant and amount. The agent passes the token to the merchant. The merchant runs the charge through its normal Stripe processor; the funds settle. Visa TAP signatures may sit on top of this flow if both ends support it. None of x402 or MPP enters the picture for a card-rail purchase.
​

A machine-to-machine flow looks different. An AI agent calls a CoinGecko price endpoint. CoinGecko returns HTTP 402 with payment-required headers. The agent constructs an EIP-3009 signature against USDC on Base, sends it back, and gets the price data. The whole exchange runs over x402; no card, no merchant onboarding, no human in the loop. MPP wraps that flow in a slightly higher-level protocol when the service wants the option to also accept SPT-backed cards or BNPL through the same agent-payment shape.
​

A B2B flow that mixes both is increasingly common. A SaaS vendor billing agents for usage might run MPP on its API, accept USDC over x402 from agents that hold stablecoin balances, and accept SPT-backed cards from agents tied to a corporate Link Agent Wallet. The vendor sees one Stripe Dashboard regardless. That convergence is the strategic point of the bundle: an agent-native business should not need to pick between card rails and stablecoin rails, because the developer surface for both runs through the same API. Treasury orchestration around that flow is a parallel category, covered in the broader B2B stablecoin payout API roundup.
​

What Stripe is not building is multi-chain stablecoin orchestration. Its x402 path is USDC on three specific chains today; non-USDC stablecoins are not natively supported, and cross-chain settlement (where the merchant accepts USDC on Base but the agent's treasury sits on Solana, Polygon, or Tron) is left to the integrator. That is a deliberate scope cut, and it is where the broader ecosystem of stablecoin developer tooling and stablecoin swap aggregators picks up the slack. For builders evaluating which protocol to bet on at the agent layer, the agentic payments deep-dive (linked above) compares ACP, AP2, MPP, and x402 head to head.
​

Sources and methodology. Stripe product details verified against Stripe Sessions 2026 announcements and Stripe newsroom releases linked inline. x402 stats from Cryptonews' April 2026 reporting. Stablecoin supplies pulled from DeFiLlama on April 30, 2026. Figures refresh quarterly.
​

Eco extends Stripe's USDC-on-Base, Solana, and Tempo agent path to the 12 other chains where agent treasuries actually live. Stripe handles fiat plus the three native stablecoin chains. Eco's stablecoin execution network handles the routing, solver selection, and finality so an agent can settle from any source chain into Stripe's surface.
​

Stripe's stablecoin agent payments handle USDC on Base, Solana, and Tempo through x402. That covers a meaningful slice of agent-payment volume, but agent treasuries do not always live on those three chains. Eco operates as a stablecoin execution network across 15 chains, abstracting routing, solver selection, and finality so an agent paying in USDC on Base can settle from a counterparty whose treasury sits on Solana, Arbitrum, Polygon, or Tron without writing the bridging logic itself. Stripe handles fiat plus the USDC-on-Base agent-payment surface; the orchestration network handles the multi-chain reality behind the scenes. For teams wiring Stripe x402 into a production agent stack with non-Base stablecoin holdings, that division of labor is the difference between integrating one execution surface and stitching together a bridge, a swap aggregator, and a settlement layer per chain.
​