Agentic commerce · May 22, 2026 · Updated Jul 1, 2026 · 2 min read
The Agentic Commerce Protocol (ACP), Explained for Brands
ACP is the open standard — from OpenAI and Stripe — that lets AI agents complete purchases against a merchant's own backend. What the protocol covers, who's adopted it, and what a brand should actually do.
Every platform shift gets its plumbing standard — the web got HTTP, payments got the card networks, and agent-driven buying is getting the Agentic Commerce Protocol. ACP, developed by OpenAI with Stripe and published as an open spec, is the rails under ChatGPT's Instant Checkout, with Etsy and the Shopify merchant ecosystem as its launch-scale adopters.
You don't need to read the spec. You need the shape of it — because the shape decides who owns the customer when an AI buys from you.
What the protocol standardizes
ACP covers three interfaces between an AI agent and a merchant:
- Product data — a feed format for exposing catalog, pricing, and availability to agent surfaces, so recommendations run on current truth.
- Checkout — a standardized way for an agent to compose an order with the merchant's own commerce backend: create, update, complete.
- Payment — delegated payment credentials (Stripe's shared payment tokens at launch) authorizing a specific transaction without handing the agent your customer's stored card.
The design principle threaded through all three: the merchant stays the merchant. Orders execute on your rails, land in your system, carry your policies. The agent is a client of your store, not a middleman that owns your buyer.
Why 'open' matters
OpenAI publishing ACP openly — rather than gatekeeping a proprietary ChatGPT checkout — sets up a standards race instead of a walled garden. Other assistant platforms can adopt it; Google is developing its own agent-payments effort; wallets and PSPs are picking sides. For merchants, the likely end-state is a small number of interoperable protocols, the way EMV or OAuth shook out.
The practical implication: readiness work is protocol-portable. Clean feeds, true availability, canonical policies, and structured product truth are the inputs every one of these standards consumes. You're not betting on OpenAI by preparing; you're betting on agents buying things, which is the safest bet in commerce right now.
What a brand should do (and skip)
Do: get your commerce data to the standard the protocol assumes — the feed, variant truth, and policy canonicalization we cover in the readiness checklist. Decide how agent-originated orders will be labeled in your reporting. If you're on Shopify, most of the protocol plumbing arrives platform-side; your job is the data it serves.
Skip: custom ACP integrations, for all but the largest brands. This is platform work — Shopify's job, your PSP's job. The differentiating work is above the protocol: whether an agent picks your product, describes it correctly, and whether the shopper who clicks through converts. That's catalog intelligence and on-site experience — Kinect's layer — not spec implementation.
Frequently asked questions
Is ACP only for ChatGPT?
It launched powering ChatGPT's Instant Checkout, but it's an open spec designed for any agent surface. Adjacent efforts (like Google's agent-payments work) are converging on the same shape: delegated authority, merchant-of-record preserved.
Do I need a developer to adopt ACP?
On major platforms, no — the protocol arrives via your platform and payments stack. Your work is data quality and measurement, not integration code.
Is it safe? Who's liable for an AI-initiated order?
Delegated payment tokens scope authorization to a specific confirmed transaction, and the human confirms the purchase. Disputes flow through existing card-network rails — the liability model is deliberately boring.
Related reading
See Kinect on your store
An AI sales rep on your storefront and an agent-ready store behind it — trained on your catalog and policies, live the same day, measured against your own baseline.