If you sell online in 2026, the ACP vs UCP question is no longer academic. These two protocols, OpenAI’s Agentic Commerce Protocol and Google’s Universal Commerce Protocol, determine whether AI assistants like ChatGPT, Gemini, and Google’s AI Mode can find your products, present them to shoppers, and complete a purchase on your behalf. Understanding the difference between them is now as fundamental to ecommerce strategy as understanding the difference between organic and paid search was a decade ago.
The two protocols emerged within months of each other, they solve overlapping problems, and they are frequently confused with one another. But they represent fundamentally different philosophies about how agentic commerce should work: one is a curated, partner-driven program born from a single AI company’s product roadmap, and the other is an open, community-governed standard designed to work across any AI surface, any platform, and any payment provider.
This guide breaks down the ACP vs UCP comparison in full: where each protocol came from, how each one works under the hood, what they cost, which platforms support them, what happened when OpenAI pulled back from Instant Checkout in March 2026, and how merchants should think about implementation today.
TL;DR: ACP vs UCP at a Glance
Short on time? Here is the ACP vs UCP comparison in five sentences. ACP (Agentic Commerce Protocol) was created by OpenAI and Stripe to power purchases inside ChatGPT, launched with Instant Checkout in September 2025, and charged participating Shopify merchants a reported 4% fee per completed sale before OpenAI retreated from in-chat checkout in March 2026. UCP (Universal Commerce Protocol) was developed by Google together with Shopify, Etsy, Target, Walmart, Wayfair, and more than 20 other companies as an open-source standard, is free to implement, and went live with real US retailer checkout at Google Marketing Live on May 20, 2026. ACP today functions primarily as a product discovery layer for ChatGPT, with transactions completing on the merchant’s own store. UCP changes the transaction layer itself, allowing AI agents to complete checkout through a standardized, protocol-native flow across Google’s AI surfaces and beyond. Most merchants should prepare for both, but if you can only prioritize one, the open protocol with live, expanding checkout deserves your attention first.
What Is the Agentic Commerce Protocol (ACP)?
The Agentic Commerce Protocol is an open specification co-developed by OpenAI and Stripe. It defines how an AI agent, such as ChatGPT, communicates with a merchant’s commerce backend to display products, transmit order information, and initiate payment. Stripe announced the protocol alongside OpenAI’s launch of Instant Checkout on September 29, 2025, positioning it as the connective tissue between conversational AI and existing merchant infrastructure. You can read the original announcement on the OpenAI blog and the technical framing in Stripe’s announcement.
The core promise was compelling. A ChatGPT user asks for a product recommendation, sees organic results ranked by relevance, taps Buy, confirms the order details, and completes the purchase without ever leaving the conversation. The merchant remains the merchant of record, processes payment through existing systems, and handles fulfillment exactly as before. For merchants already on Stripe, integration reportedly required as little as one line of code. Merchants not on Stripe could participate through the Shared Payment Token API or by adopting the Delegated Payments Spec.
At launch, Instant Checkout supported single-item purchases from US Etsy sellers, with over one million Shopify merchants queued for onboarding, including brands like Glossier, SKIMS, Spanx, and Vuori. The protocol itself was published under the Apache 2.0 license, which makes it technically open source, though the distribution channel that mattered, ChatGPT itself, remained fully controlled by OpenAI.
How ACP Worked in Practice
ACP defines a merchant-side API surface that the agent calls during a shopping session. The agent transmits the minimum information necessary to complete the order, the merchant confirms availability and pricing, and payment is executed through a tokenized handoff, so the agent platform never holds full card credentials. ChatGPT acted as an intermediary rather than a marketplace: no inventory ownership, no fulfillment role, just the conversation layer and the checkout handshake.
Participation, however, was gated. Merchants applied through OpenAI’s merchant program, and OpenAI decided who got access to Instant Checkout. On Shopify, eligibility flowed through the platform’s agentic sales channel settings rather than an individual integration. This is the first structural difference worth flagging in any ACP vs UCP evaluation: ACP was open as a specification but closed as a distribution channel.
The Fee Question
OpenAI described the cost to merchants as a small fee on completed purchases, free for users, with no effect on product ranking. Reporting in early 2026 put the figure at 4% of each sale for Shopify merchants, stacked on top of standard payment processing costs. For context, that is roughly the margin many DTC brands spend on their entire paid acquisition budget per order. The fee was the price of access to ChatGPT’s massive user base, and for some merchants it was worth it. But it set up an uncomfortable dynamic: the more agentic commerce grew, the more a single company sat as toll collector between merchants and their customers.
What Is the Universal Commerce Protocol (UCP)?
The Universal Commerce Protocol is an open-source standard for AI-driven commerce developed by Google in collaboration with Shopify, Etsy, Wayfair, Target, Walmart, and an endorsement roster of more than 20 global companies including Best Buy, The Home Depot, Macy’s, Flipkart, Zalando, and payment heavyweights Adyen, Mastercard, Visa, and notably Stripe itself. Google published the specification and reference implementation publicly, and the project is governed as a community-driven open-source effort on GitHub. Google’s engineering deep dive on the Google Developers Blog is the best primary source on the architecture, and Shopify’s engineering write-up covers the platform perspective.
Where ACP was born as the plumbing for one product (Instant Checkout in ChatGPT), UCP was designed from day one as a common language for commerce across any AI surface. The specification establishes shared functional primitives so that a merchant implements the protocol once and any compliant agent, whether it lives in Google Search’s AI Mode, the Gemini app, or a third-party assistant, can discover products, build a checkout session, and complete a purchase.
How UCP Works Under the Hood
UCP standardizes commerce functions into capabilities, which are modular building blocks like checkout and product discovery, with extensible additions such as discounts and loyalty. A merchant advertises supported capabilities through a manifest file at a well-known URL (/.well-known/ucp), which functions like a robots.txt for agentic commerce: any agent can read it and know exactly how to transact with that store.
From there, the agent creates a checkout session containing line items and buyer information, and can modify that session to apply discounts, update quantities, or change fulfillment options before completion. Identity is handled through account linking, and payments are deliberately decoupled: UCP separates payment instruments from payment handlers, so merchants can plug in Google Pay, Shop Pay, or their existing payment service provider without re-architecting anything. For secure agent-initiated payments, UCP integrates with the Agent Payments Protocol (AP2), which provides the cryptographic mandate structure that proves a human authorized the agent to spend.
Integration is flexible by design. Businesses can connect via plain REST APIs, the Agent2Agent (A2A) protocol, or the Model Context Protocol (MCP), which means the same UCP implementation serves Google’s surfaces today and any future agent ecosystem that adopts the standard.
From Specification to Live Checkout
UCP moved from announcement to production deployment in roughly four months. Google confirmed at Google Marketing Live on May 20, 2026 that UCP-powered checkout is live with major US retailers, with expansion into Canada and Australia in the coming months and the UK to follow. Google’s reference implementation already powers checkout inside AI Mode in Search and the Gemini app, with stored Google Pay wallet credentials completing the flow.
There is no application gate and no protocol fee. Any merchant who implements the specification and meets the data quality requirements can participate. That single fact does a lot of work in the ACP vs UCP debate, and it is worth dwelling on why.
ACP vs UCP: The Head-to-Head Comparison
Here is the ACP vs UCP comparison across the dimensions that matter most to merchants.
| Dimension | ACP (Agentic Commerce Protocol) | UCP (Universal Commerce Protocol) |
|---|---|---|
| Creators | OpenAI and Stripe | Google with Shopify, Etsy, Target, Walmart, Wayfair, and 20+ endorsing companies |
| First announced | September 29, 2025 | January 2026 (public spec), checkout live May 20, 2026 |
| License and governance | Apache 2.0 spec, roadmap controlled by OpenAI | Open source, community-driven on GitHub |
| Access model | Application and approval required for checkout | Open to any merchant who implements the spec |
| Cost to merchants | Reported 4% fee per completed sale (Shopify, January 2026); no published fee for the current discovery model | No protocol fee |
| Where it runs | ChatGPT and custom GPTs | Google AI Mode, Gemini app, and any compliant agent surface |
| Checkout status (August 2026) | In-chat Instant Checkout discontinued March 2026; discovery with handoff to merchant site or partner apps | Native checkout live with US retailers, international rollout underway |
| Payments | Stripe-centric, Shared Payment Token API, Delegated Payments Spec | Payment-provider agnostic, AP2 integration, Google Pay and Shop Pay handlers |
| Discovery mechanism | Merchant feed and platform catalog integration | /.well-known/ucp manifest plus product feed |
| Integration paths | Merchant API implementation or platform channel (Shopify Agentic) | REST, A2A, or MCP |
| Cart support | Single-item purchases only during checkout era | Multi-item sessions with modification support |
Table stakes acknowledged, the deeper story is not in any single row. It is in the trajectory of the two protocols, and that story turned decisively in March 2026.
The March 2026 Turning Point: OpenAI’s Checkout Retreat
Roughly five months after launching Instant Checkout, OpenAI scaled it back. In early March 2026, reporting confirmed that OpenAI was routing transactions through third-party apps like Instacart, Target, and Booking.com instead of completing purchases natively inside ChatGPT, and by late March in-chat checkout had ceased entirely. Industry analysis, including a widely shared piece in Forbes, characterized the original product as never having left pre-alpha maturity: single-item orders only, no promo codes, no multi-item carts, unresolved sales tax handling, and only about a dozen Shopify merchants ever live.
The retreat does not mean ACP is dead. The protocol still powers product discovery in ChatGPT, with confirmed retail participants including Target, Sephora, Nordstrom, Lowe’s, Best Buy, The Home Depot, and Wayfair surfacing catalog data through it. Shoppers discover products in conversation and complete the purchase on the merchant’s own store. That is a real and valuable channel, and merchants should absolutely keep their feeds eligible for it.
But the episode illustrates the structural risk in the ACP vs UCP choice. When one company owns both the protocol roadmap and the only distribution surface, merchants inherit that company’s strategic pivots. OpenAI is simultaneously building hardware, advertising products, and frontier models, and commerce infrastructure lost the internal resource battle. An open standard with multi-party governance spreads that risk: if any single participant deprioritizes UCP, the specification, the tooling, and the other surfaces remain.
It is also worth noting who endorsed UCP: Stripe, the co-author of ACP, is on the UCP endorsement list. The payments industry is signaling that it expects the open standard to become the common rail, with proprietary programs plugging into it rather than competing against it.
Why the Difference Between ACP and UCP Matters for Your Margins
Protocol architecture sounds abstract until you translate it into unit economics. Consider a merchant doing $2 million in annual online revenue who expects 10% of orders to originate from agentic surfaces by the end of 2026, a conservative figure given current AI search adoption curves.
Under the checkout-era ACP model, that $200,000 in agent-originated revenue carried a reported 4% platform fee, or $8,000 per year, before payment processing. Under UCP, the protocol layer costs nothing: you pay only your existing payment provider’s rates, exactly as you do for your website orders today. The fee delta compounds as the agentic share of commerce grows, and every analyst projection has that share growing steeply through 2027.
There is a second margin effect that is easy to miss. Because UCP decouples payment handlers from the protocol, merchants retain the freedom to negotiate processing rates and switch providers without touching their agentic integration. A protocol that hard-wires a single payments partner removes that leverage permanently. In the long run, the difference between ACP and UCP is not just a fee line; it is who holds pricing power over your checkout.
Platform Support: Shopify, WooCommerce, and Everyone Else
Shopify
Shopify sits in both camps, which tells you something about how platforms are hedging. Shopify merchants get ACP-based discovery in ChatGPT through Shopify Catalog and the Agentic sales channel toggle in admin settings. On the UCP side, Shopify co-developed the standard, and eligible products flow into UCP surfaces when they are tagged for native agentic commerce. For most Shopify merchants, readiness is less about custom development and more about catalog hygiene: complete product data, accurate availability, and correct tagging so products are eligible on both protocols.
WooCommerce
WooCommerce merchants have more assembly to do, and this is where implementation support matters most. A working UCP setup on WooCommerce typically involves a UCP plugin to expose the manifest and checkout session endpoints, a payments integration compatible with agentic flows, and a Google Merchant Center feed that identifies which products are eligible for native agentic checkout, either through a global setting or a supplementary feed. ACP eligibility runs through Stripe’s tooling, which supports WooCommerce alongside BigCommerce, Wix, and Squarespace. The two integrations are separate projects with separate failure modes, so validation tooling that checks your endpoints against the actual specifications saves days of debugging.
Enterprise and Custom Stacks
Enterprises with custom commerce stacks implement UCP directly against the specification, choosing REST, A2A, or MCP as the integration surface. The capability-based architecture works in their favor: a phased rollout can ship discovery first, then checkout, then extensions like discounts and loyalty, without any big-bang migration. ACP participation for enterprises currently means feed-level discovery integration, since the native checkout program is shelved.
ACP vs UCP: Which Should Merchants Implement First?
The honest answer to the ACP vs UCP prioritization question is both, eventually. The protocols are not mutually exclusive, they serve different traffic sources, and the marginal cost of the second integration is low once your product data is in order. But sequencing matters, and the decision framework is straightforward.
Prioritize UCP first if any of the following describe you. You want native, in-agent checkout rather than a handoff to your website, because UCP is the only protocol with that capability live and expanding today. You are fee-sensitive and unwilling to cede a percentage of every agentic sale to a platform intermediary. You want one integration that serves multiple AI surfaces rather than a per-platform build. Or you simply want to be early on the standard that the largest retail and payments companies have collectively endorsed.
Prioritize ACP-based discovery first if ChatGPT is already a measurable referral source in your analytics, which is increasingly common for brands with strong organic presence, or if you are on Shopify where enabling the channel is nearly free effort. Since current ACP participation carries no checkout fee and no checkout integration, the cost-benefit is favorable even though the capability ceiling is lower.
Either way, treat the difference between ACP and UCP as a portfolio decision rather than a religious one. Your product feed quality, structured data, and checkout API hygiene are shared assets that make both integrations better.
A Practical UCP Readiness Checklist
Whichever side of the ACP vs UCP debate you land on for sequencing, the preparation work overlaps heavily. Here is the punch list we walk merchants through:
- Audit your product feed. Complete titles, accurate pricing, live availability, GTINs where applicable, and high-quality images. Agents penalize ambiguity harder than human shoppers do.
- Publish your UCP manifest. Expose
/.well-known/ucpwith your supported capabilities and endpoints. This is the discovery handshake; without it, compliant agents cannot see you. - Implement checkout sessions. Support session creation, modification, and completion, including discount application if you run promotions.
- Wire up payments. Confirm your payment handler configuration, and if you support agent-initiated payments, validate your AP2 mandate handling.
- Tag native commerce eligibility. In Google Merchant Center, mark eligible products either globally or through a supplementary feed.
- Validate before you assume. Run your store through a protocol checker to confirm your manifest parses, your endpoints respond correctly, and your feed eligibility is recognized. Fix what fails, then re-validate.
- Enable ACP discovery in parallel. If you are on Shopify, switch on the agentic channel. On other platforms, confirm your feed reaches the ChatGPT catalog through your platform’s integration.
- Measure from day one. Add agentic surfaces as a distinct channel in your analytics so you can see order origin, AOV, and return rates separately from web and app traffic.
Most merchants can complete this list in two to four weeks, with the manifest and checkout session work representing the bulk of the engineering effort on non-Shopify platforms.
ACP vs UCP Timeline: How We Got Here
Context makes the current state of the ACP vs UCP landscape easier to navigate, so here is the compressed history.
September 29, 2025. OpenAI launches Instant Checkout in ChatGPT for US Etsy sellers, announcing the Agentic Commerce Protocol co-developed with Stripe. Single-item purchases only, US users only, with over one million Shopify merchants slated to follow.
Q4 2025. Shopify merchants begin onboarding through the Agentic sales channel. Reports surface of a 4% per-sale fee for Shopify merchants participating in Instant Checkout. Meanwhile, Google quietly assembles retail and payments partners around a draft open standard.
January 2026. Google publishes the Universal Commerce Protocol specification publicly, with Shopify, Etsy, Target, Walmart, and Wayfair as co-developers and an endorsement list spanning more than 20 companies including Stripe, Visa, Mastercard, and Adyen. The spec, reference implementation, and roadmap land on GitHub under community governance.
March 2026. OpenAI retreats from native checkout. Transactions route to partner apps and merchant sites, and in-chat Instant Checkout winds down entirely by late March. ACP continues as the discovery layer for ChatGPT shopping.
May 20, 2026. Google confirms at Google Marketing Live that UCP-powered checkout is live with major US retailers inside AI Mode and the Gemini app, with Canada and Australia next and the UK to follow.
Today. UCP is the only protocol with native agentic checkout running in production at scale, while ACP remains a meaningful discovery channel. That asymmetry, more than any spec-level detail, defines the practical difference between ACP and UCP for merchants planning their 2026 roadmap.
Where Agentic Protocols Meet Your Search Strategy
There is a strategic layer to the ACP vs UCP decision that goes beyond checkout mechanics: visibility. AI agents are becoming a discovery channel in their own right, and protocol participation directly affects whether your products appear when an agent goes shopping on a customer’s behalf.
Traditional SEO optimized pages for human readers arriving through blue links. Answer engine optimization extends that work to AI-generated responses. Protocol readiness is the third layer: it makes your catalog machine-transactable, not just machine-readable. A product that an agent can discover, price-check, and purchase through a standardized flow will systematically win recommendations over a product that forces the agent to scrape a website and hand off to a human. Structured product data, accurate availability, and a valid UCP manifest are ranking assets in the agentic era in the same way page speed and backlinks were ranking assets in the search era.
The compounding effect works in your favor. The feed hygiene you do for UCP eligibility improves your Google Shopping presence today. The structured data you publish for agents strengthens your visibility in AI-generated answers. Merchants who treat the difference between ACP and UCP as part of a unified search and commerce strategy, rather than an isolated IT project, extract value from the work immediately instead of waiting for agentic volume to arrive.
Frequently Asked Questions
Is ACP the same as UCP?
No. ACP (Agentic Commerce Protocol) is the OpenAI and Stripe specification that connects ChatGPT to merchant systems, currently used for product discovery. UCP (Universal Commerce Protocol) is the Google-initiated, community-governed open standard that powers native agentic checkout across Google’s AI surfaces and any compliant agent. The ACP vs UCP distinction matters because they differ in governance, fees, checkout capability, and reach.
Does ACP still work after OpenAI discontinued Instant Checkout?
Yes, in a narrower form. ACP continues to power product discovery inside ChatGPT, and major retailers actively participate. What ended in March 2026 was native in-chat checkout; purchases now complete on the merchant’s store or through partner apps.
How much does UCP cost?
The protocol itself is free. There is no application fee, no approval gate, and no per-transaction protocol fee. You pay only your existing payment processing costs. Implementation effort varies by platform, from configuration-level work on Shopify to plugin and feed setup on WooCommerce.
Did ChatGPT really charge merchants 4%?
Reporting in January 2026 indicated Shopify merchants paid a 4% fee on Instant Checkout sales. OpenAI officially described it only as a small fee on completed purchases. Since the checkout program ended, no transaction fee currently applies to ACP discovery participation.
Can I implement both protocols?
Yes, and for most merchants that is the right endgame. They draw from the same underlying assets: clean product data, accurate feeds, and solid checkout APIs. Running both maximizes your surface area across ChatGPT and Google’s agentic ecosystem.
Which AI surfaces does UCP reach today?
Google’s AI Mode in Search and the Gemini app run UCP-powered checkout now, live with major US retailers as of May 2026 and expanding to Canada, Australia, and the UK. Because UCP is an open standard with REST, A2A, and MCP integration paths, additional agent surfaces can adopt it without merchants changing their implementation.
Does UCP replace my existing checkout?
No. UCP adds an agentic transaction path alongside your web and app checkout. You remain the merchant of record, keep your payment provider, and fulfill orders exactly as you do today.
How do I know if my store is set up correctly?
Validate rather than guess. Run your domain through a UCP validation tool to check your manifest, endpoints, and feed eligibility, and fix anything it flags. This is exactly the gap UCPhub exists to close.
The Bottom Line on ACP vs UCP
The ACP vs UCP story is ultimately a story about two theories of agentic commerce. ACP bet that a single dominant AI assistant could own the transaction end-to-end, and the market pushed back within six months. UCP bet that commerce infrastructure wants to be a standard, the way HTTP and email are standards, and it has the endorsements, the live deployments, and the international rollout to show for it.
For merchants, the practical takeaway is refreshingly simple. Keep your products discoverable everywhere agents look, including ChatGPT through ACP. But build your durable agentic commerce foundation on the Universal Commerce Protocol, because it is open, free, live at checkout, and backed by the broadest coalition in retail. The stores that implement UCP correctly in 2026 will be the ones AI agents can actually buy from while their competitors are still reading comparison posts like this one.
Ready to find out where your store stands? UCPhub gets you UCP-ready: we audit your setup, implement the protocol across Shopify, WooCommerce, and custom stacks, and validate everything against the live specification. Book a discovery call and make your store agent-ready before your competitors do.
