Agentic Commerce Protocol: Stripe and OpenAI's Checkout Standard, and What It Means If You're Not on Shopify (2026)

Stripe and OpenAI released the Agentic Commerce Protocol in September 2025, and the two companies have kept developing it in the open since, under an Apache 2.0 license and maintained on GitHub by both parties with Meta joining as a contributor. The protocol defines how an AI agent, most visibly ChatGPT, discovers products, negotiates a cart conversationally, and completes a purchase using delegated payment tokens rather than handing raw card details to the agent. The most current stable snapshot, dated April 17, 2026, added cart, feed, orders, and authentication resources along with Model Context Protocol compatibility, meaning ACP endpoints can now be exposed as MCP tools an agent calls directly. Stripe used ACP to power Instant Checkout inside ChatGPT, first for US Etsy sellers and expanding toward more than a million Shopify merchants. As of March 2026, Instant Checkout itself is being deprioritized in favor of a discovery and redirect model, but ACP remains active as the connective standard underneath.

Why two standards exist at once

ACP and UCP are not simply competing implementations of the same idea, they emerged from different starting points. ACP was built by a payments company and a model lab to solve the specific problem of an agent completing a purchase inside a chat interface, and its resource model, cart, feed, orders, authentication, reads like a payments API because that is what Stripe knows how to build. UCP was built by a commerce platform and a search company to solve the broader problem of making any merchant's catalog and checkout legible to any agent, and it leans on MCP servers scoped to catalog, cart, and checkout as separate concerns, the architecture we detailed in Shopify's Storefront MCP for cart and checkout. Notably, Stripe appears as a backer of both standards. That is less a contradiction than a hedge: Stripe processes payments regardless of which protocol wins the discovery and negotiation layer, so supporting both protects its position either way.

For a merchant, the practical difference shows up in where each protocol's customers are actually shopping. ACP is the path into ChatGPT specifically, since that is the surface Stripe and OpenAI built it for. UCP is the path into Shopify's own storefront agent tooling and into Google's AI Mode and Gemini surfaces. A brand's customers are not choosing one assistant, they are spread across ChatGPT, Gemini, and whatever else launches next, which means the standards question is not which one to pick, it is which ones you can afford to ignore.

What this means if you are not on Shopify

UCP's Storefront MCP implementation is native to Shopify. If your commerce platform is Salesforce Commerce Cloud, a commercetools based composable build, or a custom headless frontend, you do not get UCP support by default the way a Shopify Plus merchant does, and building it yourself means implementing the catalog and checkout MCP server contracts against your own platform's APIs, work we walked through the discovery side of in making a headless storefront legible to shopping agents. ACP is comparatively more platform neutral by design, since it was built to let any merchant plug into ChatGPT's commerce surface through Stripe's existing payment rails rather than through a specific storefront framework, which makes it the more tractable first integration for a non Shopify merchant that wants presence inside ChatGPT specifically.

The realistic sequencing for most non Shopify enterprise brands is to treat ACP as the nearer term integration, since it rides on a Stripe relationship many merchants already have, and to treat UCP support as a longer build that may require either a Shopify layer somewhere in the stack or a custom MCP implementation against your own commerce APIs. We covered the strategic case for UCP itself, who backs it and why it matters for a headless stack, in our earlier explainer, and that analysis holds regardless of which protocol you implement first: the transaction layer, not just the discovery feed, is what actually changes who completes the sale and where the customer relationship lives.

What to decide now

Do not wait for one standard to win, because the two are backed by parties with structurally different incentives and neither is likely to fully absorb the other in the near term. Instead, prioritize by where your actual traffic comes from: if ChatGPT referral traffic is meaningful today, ACP through your existing Stripe integration is the faster path to agentic checkout coverage. If your customers are converging on Google's AI Mode or Gemini, or your roadmap already includes Shopify somewhere, UCP is the more strategic build. Either way, keep the same guardrail discipline we have argued for across every agentic checkout implementation: the platform, not the agent, should remain the system of record for price, inventory, and order state at the moment payment actually happens.

FAQ

What is the Agentic Commerce Protocol? An open standard built by Stripe and OpenAI, released in 2025 and maintained under Apache 2.0, that defines how an AI agent discovers products, builds a cart, and completes a purchase using delegated payment tokens.

Is ACP the same as UCP? No. ACP is backed by Stripe and OpenAI and is the standard behind ChatGPT's commerce features. UCP is backed by Shopify and Google and covers Shopify's storefront agent tooling plus Google's AI surfaces. They overlap in purpose but are separate standards with separate primary surfaces.

Do I need to support both? Most enterprise brands eventually will, since customers use multiple AI assistants. Prioritize based on where your referral traffic actually originates today.

Can a non Shopify merchant use ACP? Yes. ACP was built to be more platform neutral than UCP's Shopify native Storefront MCP implementation, and typically integrates through an existing Stripe relationship.

When this applies to your stack

If your commerce platform is not Shopify and you are trying to decide whether ACP, UCP, or both belong on this year's roadmap, the decision comes down to where your customers already are and how much custom MCP integration work your platform requires versus what a Stripe backed ACP integration gets you out of the box. Mapping that against your actual traffic and building the integration that matches it is the kind of headless commerce infrastructure work we do at Contra Collective.