ACP vs UCP vs AP2 compared for November 2026: who runs each protocol, what each covers, how they fit together, and what Shopify brands actually build.
Every week another vendor tells you to "get ready for ACP" or "implement UCP," usually with a slide that puts three acronyms in a row like they're competing for the same job. They aren't. Treating them as rivals is how brands end up paying an agency to build something their platform already ships.
ACP, UCP and AP2 sit at different layers of an AI purchase. Two of them decide how an agent finds your products and checks out. The third proves the shopper actually said yes. Once you see which layer each one owns, the "which should I pick?" question mostly answers itself.
This guide compares all three as of November 2026: who runs each one, what each covers, how they work together in a single purchase, and what a Shopify brand has to do about any of it.
TL;DR
- ACP (Agentic Commerce Protocol) is OpenAI and Stripe's open standard, released on September 29, 2025, for agents to read a merchant's catalog and complete a purchase. Since March 24, 2026, ChatGPT uses it mainly for product discovery and sends shoppers to the merchant's own checkout (Retail Gazette, March 2026).
- UCP (Universal Commerce Protocol) is the open standard Google and Shopify announced on January 11, 2026, covering catalog, cart, identity, checkout and orders across Google AI Mode, Gemini and Universal Cart. Its latest release is v2026-08-25 (ucp.dev, 2026).
- AP2 (Agent Payments Protocol) is a payments-only trust layer from Google. It doesn't find products or run checkout. It proves what the shopper approved. Google donated it to the FIDO Alliance on April 28, 2026 (The Paypers, 2026).
- They stack, not compete. A UCP checkout can carry AP2 mandates, and Stripe maintains ACP while sitting on UCP's Governing Council.
- Shopify brands don't build any of them. Shopify's Agentic Storefronts connects eligible stores to ChatGPT and Google's AI surfaces. Your job is product data, policies and owning the customer after the first agent-led order.
What are ACP, UCP and AP2?
ACP, UCP and AP2 are three open protocols that let AI agents shop on a person's behalf. ACP and UCP define how an agent discovers products and completes checkout with a merchant. AP2 defines how an agent proves the shopper authorized the payment. All three are free to implement under the Apache 2.0 license.
The quickest way to keep them straight is by who built them and which assistant they serve:
- ACP came from OpenAI and Stripe. OpenAI, Stripe and Meta are listed as lead maintainers in the protocol's GitHub repository. Its home surface is ChatGPT. Our Agentic Commerce Protocol guide covers it in depth.
- UCP came from Google and Shopify, with Etsy, Wayfair, Target and Walmart at launch. Its home surfaces are Google AI Mode, the Gemini app and Universal Cart. The full merchant walkthrough is in our Universal Commerce Protocol guide.
- AP2 came from Google in September 2025 with 60+ payments and technology partners, and now lives at the FIDO Alliance, the body behind passkeys.
If you only remember one line: ACP and UCP move the order, AP2 moves the proof.
ACP vs UCP vs AP2: side-by-side comparison
The table below reflects each protocol's public status as of November 12, 2026.
| ACP | UCP | AP2 | |
|---|---|---|---|
| Built by | OpenAI and Stripe | Google and Shopify, with Etsy, Wayfair, Target and Walmart | Google, with 60+ partners |
| Who runs it now | Lead maintainers OpenAI, Stripe and Meta | Governing Council (Google, Shopify, Stripe) plus technical councils | FIDO Alliance working groups (since April 28, 2026) |
| First release | September 29, 2025 | January 11, 2026 | September 2025 |
| Latest version | 2026-04-17 | v2026-08-25 | v0.2 (April 2026) |
| Layer | Catalog feed, cart, checkout, orders | Catalog, cart, identity linking, checkout, orders | Payment authorization only |
| How agents find you | Merchant sends a product feed to the AI platform | Merchant publishes a profile at /.well-known/ucp on its own domain | Not applicable |
| Main surfaces | ChatGPT | Google AI Mode, Gemini, Universal Cart | Any agent that supports it, including UCP checkouts |
| Proof the shopper agreed | Scoped payment tokens (for example Stripe Shared Payment Tokens) | Payment handlers, with an optional AP2 mandates extension | Signed Checkout and Payment Mandates |
| Live status | Feeds power ChatGPT shopping; checkout mostly happens on the merchant's site | Live in US Google Search and Gemini via Universal Cart (since October 15, 2026) | Spec and reference builds; standardization under way at FIDO |
| What a Shopify brand does | Nothing to build; Agentic Storefronts handles it | Nothing to build; direct checkout is on by default for eligible stores | Nothing; your payment provider handles it |
Sources: ACP GitHub changelog and MAINTAINERS file; ucp.dev announcements; The Paypers (April 29, 2026); Shopify Help Center; Google (October 2026).
Two rows matter more than the rest. "How agents find you" is the real philosophical split between ACP and UCP. "What a Shopify brand does" is the row most vendor comparisons leave out, because the honest answer is "very little."
What's the difference between ACP and UCP?
The main difference between ACP and UCP is who controls discovery. With ACP, the merchant pushes a product feed to OpenAI, which decides what ChatGPT shows. With UCP, the merchant publishes a profile on its own domain that declares what it supports, and any compliant agent can read it. Scope differs too: UCP covers more of the journey.
That push versus pull split has practical consequences.
ACP is platform-mediated. You (or your platform) apply, send a catalog in OpenAI's feed format, and ChatGPT ranks what it receives. ACP's 2026-04-17 release added cart, product feed, orders, authentication and an MCP binding, which tells you where OpenAI's attention went after it pulled back from in-chat checkout in March 2026. ChatGPT now sends most shoppers to the merchant's own checkout, and the brand stays merchant of record.
UCP is merchant-hosted. A business declares its capabilities, such as checkout, identity linking or order tracking, in a discovery document, and agents negotiate what both sides support. UCP runs over REST, MCP, A2A or an embedded checkout, so one implementation reaches several kinds of agent.
The governance gap is narrowing. UCP's Tech Council added Amazon, Meta, Microsoft, Salesforce and Stripe on April 24, 2026, and Stripe joined Google and Shopify on the Governing Council four days later (ucp.dev, 2026). Meta sits on both sides as well. The two camps share more members than the "OpenAI vs Google" framing suggests.
{{cta}}
Where does AP2 fit in?
AP2 is the trust layer for payments. It gives the merchant and the payment processor signed, verifiable proof of exactly what the shopper approved: these items, this price, this limit. It doesn't list products or run a cart. Any commerce protocol can carry it, and UCP has a dedicated extension for it.
UCP's own documentation describes the flow. The merchant signs the checkout state. When the shopper consents, the agent's platform generates two credentials: a Checkout Mandate tied to a hash of that exact cart, and a Payment Mandate carrying the payment authorization. The merchant verifies the first, the processor verifies the second, and only then does the order go through (ucp.dev, 2026). Because the mandate is bound to the cart, an agent can't swap items or change the amount after the shopper says yes.
Two 2026 changes made AP2 more relevant:
- It left Google's hands. Google donated AP2 to the FIDO Alliance on April 28, 2026, and FIDO set up working groups for agentic authentication and payments, with Mastercard and Visa chairing the payments group (The Paypers, April 2026).
- It added "human not present" payments. AP2 v0.2, released alongside the donation, lets an agent buy later on instructions the shopper pre-authorized, such as "buy these sneakers the moment they drop under $120."
The card networks are building the same idea into their own rails. Our agentic payments guide covers Visa Intelligent Commerce and Mastercard Agent Pay in detail.
How do ACP, UCP and AP2 work together in one purchase?
In a single AI-led purchase, the commerce protocol handles discovery and checkout while AP2 (or a card network token) handles authorization. Here is how one order moves through the stack on a Google surface today:
- Discovery. A shopper asks Gemini for a waterproof running jacket under $150. Gemini reads product data that Shopify syndicated through Agentic Storefronts and Merchant Center.
- Capability check. The agent reads the brand's UCP profile and sees it supports checkout and identity linking.
- Cart. The agent builds a cart, possibly next to other merchants' items in Universal Cart.
- Signed commitment. The merchant returns the checkout state with its signature, so the price can't drift mid-flow.
- Authorization. The shopper confirms. If AP2 is in use, the platform issues the Checkout and Payment Mandates; otherwise it passes a tokenized card through a payment handler.
- Order. The merchant completes the order as merchant of record and sends status updates back to the agent.
Swap Gemini for ChatGPT and steps 2 through 5 mostly happen on your own Shopify checkout, because OpenAI now routes shoppers there. Same product data, different handoff point.
Do I need both ACP and UCP?
If you're on Shopify, you already have both and built neither. Shopify's Agentic Storefronts lists eligible stores' products in ChatGPT and switches on direct checkout in Google AI Mode and Gemini by default, with no extra Shopify channel fee beyond standard payment processing (Shopify Help Center, 2026). Neither spec sets a transaction fee of its own.
For brands on a custom stack, the answer is "eventually, yes, but not in the order vendors pitch it." The decision comes down to where your buyers already ask questions:
| Your setup | Start with | Why |
|---|---|---|
| Shopify store, any size | Neither; audit product data and policies | Agentic Storefronts handles both protocols |
| Custom stack already on Stripe | ACP through Stripe's Agentic Commerce Suite | Stripe hosts the endpoint and handles tokens and fraud signals |
| Custom stack with a strong Google Shopping program | UCP through Merchant Center | Universal Cart and AI Mode sit on top of the Shopping graph |
| Enterprise with its own payments team | Both, plus card network programs | Visa's Intelligent Commerce Connect, piloting since April 2026, accepts ACP and UCP payments through one integration (Visa, 2026) |
Nobody should build AP2 directly unless they are a payment service provider or an agent platform. For merchants, it arrives through Stripe, Adyen, PayPal or whichever processor you already use. Several of them sit on UCP's Payments Technical Council, formed September 2, 2026 (ucp.dev, 2026).
How do MCP and A2A relate to these protocols?
MCP and A2A are transport and coordination layers, not commerce protocols. MCP (Model Context Protocol) is how an AI tool calls an outside system, and A2A (Agent2Agent) is how two agents talk to each other. ACP and UCP both offer MCP bindings, and AP2 began as an A2A extension.
For Shopify brands, the MCP piece shows up as Shopify's Catalog, Cart and Checkout MCP servers, which now sit behind the UCP endpoint. Our Shopify MCP guide lists every official server and what each one can do.
You'll also see "llms.txt vs MCP" in these debates. They don't compete either. An llms.txt file is a static summary that helps a model read your site. MCP is a live connection that lets an agent act on it.
What the protocols don't decide for your store
Every protocol on this page optimizes the first purchase. None of them gives you the second.
When an agent buys from you, the shopper's relationship stays with the assistant. They didn't browse your collections, didn't see your bundles and probably didn't opt in to anything. The protocols carry order status back to the agent, not a way to reach that customer again.
That makes the channels you own more valuable as agent traffic grows:
- Your mobile app. No AI cart renders inside it, and a shopper who installs it talks to you directly.
- Push notifications. A back-in-stock or price-drop alert to someone who opted in to your brand doesn't depend on any agent ranking you.
- An assistant inside your own store. Appbrew's AI Concierge answers shopper questions inside your app, using your catalog and your rules.
Clean product data serves both worlds. The same titles, attributes and variant structure that help ChatGPT and Gemini pick your products also power search and recommendations in your own app. Our guide to product descriptions AI shopping assistants can parse is the best place to start, and the broader picture is in what agentic commerce means for Shopify brands.
Frequently asked questions
Is UCP replacing ACP?
No. Both protocols are actively maintained. ACP shipped its 2026-04-17 release and powers ChatGPT's product feeds, while UCP shipped v2026-08-25 for Google's surfaces. Several companies, including Stripe and Meta, take part in both. Expect them to coexist the way different ad platforms do.
Is AP2 part of UCP?
AP2 is a separate protocol that UCP supports through an optional extension. A UCP checkout can carry AP2's Checkout and Payment Mandates to prove what the shopper approved, but a UCP checkout can also run on a standard tokenized card. Since April 28, 2026, AP2 is developed under the FIDO Alliance.
Which agentic commerce protocol does Shopify use?
Shopify co-developed UCP and runs its agent-facing Catalog, Cart and Checkout endpoints on it. It also connects eligible merchants to ChatGPT, where shoppers complete purchases on the merchant's own Shopify checkout. Merchants manage both from the Agentic Storefronts settings in the Shopify admin, with no code.
Do agentic commerce protocols charge fees?
Neither ACP nor UCP sets a transaction fee; both are open source under Apache 2.0. Costs come from the channel and the processor. Shopify charges no extra channel fee for direct checkout in Google AI Mode and Gemini, only standard payment processing. Check each AI platform's merchant terms for its own fees.
Who is liable if an agent buys the wrong thing?
The merchant stays merchant of record under both ACP and UCP, so refunds and disputes run through your normal process. AP2 mandates and card network tokens exist to settle these disputes faster, because they record exactly what the shopper approved. Your published return policy still governs the outcome.
Pick the layer, not the logo
The acronym fight is mostly a vendor story. For a Shopify brand, the protocols are plumbing your platform already laid, and the work that moves revenue sits on either side of them: product data good enough for an agent to choose you, and owned channels good enough to bring that shopper back without one.
{{cta2}}
If you want the second half sorted, book a demo and see how brands turn first orders into app customers.
Milo builds your app from your Shopify catalog and drafts every change, then waits for your yes.








.webp)



