Agentic Commerce Protocol (ACP)
An open standard developed by Stripe and OpenAI, published under Apache 2.0, that defines how buyers, AI agents, and businesses coordinate a checkout and pass payment credentials securely, with the business remaining the merchant of record.
Most explanations of the Agentic Commerce Protocol describe it as the on-ramp to selling inside AI assistants. The protocol's own documentation says something narrower, and the narrower version is the one worth knowing.
What ACP is
ACP describes itself as "an open standard for programmatic commerce flows between buyers, AI agents, and businesses." It is "open source and community-designed under the Apache 2.0 license," and it was developed by Stripe and OpenAI (agenticcommerce.dev, checked 2026-08-06).
The framing on its own site is a checkout standard, not a marketplace. "Implement the ACP specification to configure your checkout for agentic commerce, so that any compatible agent can securely initiate checkout."
Three design commitments are stated plainly:
- The business stays the merchant of record. ACP states businesses "maintain their customer relationships as the merchant of record, retaining control over which products can be sold, how they're presented, and how orders are fulfilled."
- It is integration-agnostic. "Publish your checkout configuration with a traditional API or MCP. ACP works with any integration pattern and technology stack," working alongside an existing commerce backend and payment processor.
- It covers more than one-off physical goods. The site lists "physical and digital goods, subscriptions, and asynchronous purchases."
The sentence most explanations omit
The FAQ on the protocol's own site answers the question every merchant actually has, and the answer is a flat no.
Asked whether implementing the protocol means products will automatically be listed through AI agents: "No, each AI platform will manage their own process for how businesses can participate. If your business wants to participate in ChatGPT, you'll need to apply."
That is the load-bearing fact. ACP is transaction plumbing. It is not a discovery channel, and implementing it is not a visibility strategy.
The site also states that "OpenAI is the first AI platform to implement ACP with ChatGPT," and that discovery mechanisms are still being worked on: "We're working to create discovery mechanisms for AI platforms to identify businesses that have implemented ACP."
So even the question of how a platform finds ACP-enabled merchants is, by the protocol's own account, unfinished as of 2026-08-06.
Payments, and who else is involved
On the payment side, ACP states businesses can use it "with any compatible PSP," and that "Stripe is the first compatible PSP with its Shared Payment Token." The stated security property is passing payment credentials from buyers to agents "without exposing underlying payment credentials," described as PCI compliant.
There is a parallel effort worth knowing about so you do not conflate the two. Google announced the Agent Payments Protocol, AP2, built around signed records of what a user actually authorized. Agentic commerce covers that side with its own sourcing. ACP and AP2 are separate proposals from different groups in the same emerging area, and neither has settled it.
Why it matters to a merchant who will never implement it
Because of what it implies about where the reading happens.
For most small and mid-sized merchants, ACP access is not the question. OpenAI's commerce documentation states that "onboarding product feeds in ChatGPT is currently available to approved partners" (OpenAI Developers, checked 2026-08-06), and OpenAI's merchant FAQ answers the underlying anxiety directly: you do not need a product feed if ChatGPT already crawls your site, though "feeds give you greater control over how your products appear" (OpenAI merchants, checked 2026-08-06).
Which means the discovery stage runs on your public pages whether or not you ever touch a protocol. OpenAI describes shopping research results as "organic and based on publicly available retail sites, reading product pages directly, citing sources," and states that when retailers block automated access, those sources get skipped (OpenAI, checked 2026-08-06).
There is also a direction-of-travel point that cuts against the hype. OpenAI's merchant FAQ states it is "moving away from a standalone Instant Checkout experience in ChatGPT and prioritizing better shopping discovery and merchant-owned checkout experiences." If discovery happens in the assistant and the purchase completes on your site, your product page becomes the destination rather than a formality.
Old way, new way
The old way treated a checkout as the end of a funnel a human walked down, and product data as a set of fields that made a listing look complete.
The new way splits the two. Discovery happens where a machine reads your public product information, and checkout is a separate protocol question with its own eligibility. A merchant can be excellent at one and absent from the other, and the two get fixed in completely different places.
Most of the writing about agentic commerce is about the second. Almost all of the accessible work is in the first.
The honest limit
ACP is a specification, not a growth channel. Implementing it does not list you, and the protocol says so itself. Anyone selling ACP implementation as an AI visibility service is selling you plumbing and calling it a pipeline.
Citedon has no visibility into the ACP feed pipeline, into Shopify Catalog, or into the third-party data providers OpenAI names. Our scan queries ChatGPT through OpenAI's API with web search enabled, which is the text answering path, and it does not query the shopping carousel or the shopping research flow. If your price is wrong inside a product card, our scan will not surface it.
What it measures is whether the page a machine would read directly is readable: content in real text, valid product markup, offers matching the visible page, crawlers not blocked. That is the input you own regardless of which protocols you implement.
Everything on this page is dated 2026-08-06 and this area moves faster than almost anything else we cover. Program terms, eligibility, and checkout direction have all changed inside a year. Re-check the linked sources before acting.
How to check yours
Take your bestselling product page and read only what a machine would get: a price it can parse, a stock status it can trust, a distinct record for the variant a shopper would actually order, and specs it can compare.
Run a free scan on that URL to see how engines read it today. For the catalog-level work behind it, read how to structure product data for AI shopping agents.