UCP vs ACP: Which Agentic Commerce Protocol Should Retailers Implement?

Retailers should implement both protocols, in sequence. The Agentic Commerce Protocol from OpenAI and Stripe goes first, because it already processes live orders and reaches shoppers inside ChatGPT. Google's Universal Commerce Protocol follows, covering the whole buying journey rather than the checkout moment alone and connecting to Google's discovery surfaces. Both are open source, so licensing costs will not decide this. Timing will. One protocol is production-ready today; the other is where the industry is clearly heading. Walmart and Shopify have committed to both, the strongest available signal that the market expects coexistence rather than a single survivor. Treat the decision as an ordering problem rather than a bet, and the risk of guessing wrong mostly disappears.

Two competing protocols now define how AI agents will shop on behalf of consumers. OpenAI and Stripe’s Agentic Commerce Protocol (ACP) launched in September 2025. Google’s Universal Commerce Protocol (UCP) launched in January 2026. Both are open source under Apache 2.0, and both will shape the $3 trillion to $5 trillion global agentic commerce market projected by 2030.

I’ve analyzed both protocols across scope, architecture, payments, integrations, and ecosystem adoption. This comparison covers what matters for retailers evaluating implementation. Read to the end for specific recommendations based on your existing infrastructure.

Don’t choose. Layer them. Use ACP for speed today, and build UCP for scale tomorrow.

ACP has a three-month head start and powers ChatGPT’s 700 million weekly users. UCP covers the full commerce lifecycle and connects to Google’s search ecosystem. Walmart and Shopify are implementing both. This isn’t about picking a winner. It’s about sequencing: ACP gets you live in weeks, UCP builds the foundation for years.

The two protocols differ on five axes: coverage, payment mechanics, integration path, production maturity, and audience reach. ACP is narrow and shipping. UCP is broad and new. That asymmetry explains most of the rest. ACP is Stripe-native, built around the transaction moment, and it inherits both Stripe's tooling and Stripe's boundaries. UCP runs through Google Merchant Center and reaches for the whole journey, which brings more flexibility and more configuration. Neither wins on every axis. Most retailers find that one protocol matches the systems they already run and the customers they already reach, which turns an apparently technical comparison into a question about existing infrastructure and existing traffic.

1. Scope of coverage. ACP handles checkout transactions only. UCP handles discovery, checkout, order management, and post-purchase support. ACP solves one problem well; UCP attempts to standardize the entire journey.

2. Payment approach. ACP uses Stripe’s Shared Payment Tokens, which are single-use, time-bound, and merchant-scoped. UCP uses the Agent Payments Protocol (AP2) with cryptographic mandate chains that create audit trails from intent to payment.

3. Integration path. ACP is Stripe-native. If you already use Stripe, enabling agentic payments takes one line of code. UCP integrates through Google Merchant Center and offers more flexibility across payment processors.

4. Production maturity. ACP has three months of live transaction processing. ChatGPT Instant Checkout with Etsy has been processing real orders since September. UCP launched at NRF 2026 with pilots announced but no production volume yet.

5. Ecosystem reach. UCP connects to Google Search, which still drives the majority of product discovery. ACP connects to ChatGPT, which processes 50 million shopping queries daily. Different platforms, different customer segments.

My read: this is a land grab for the interface between shoppers and products, and whoever owns that interface collects the margin behind it. Two companies with different revenue to protect wrote two specifications with different shapes, and both used the word open. Neither specification is a neutral public good. Retailers should not wait for the argument to resolve, because the shopping behaviour it concerns is already happening at scale inside ChatGPT. Everything I would tell a marketing leader about UCP and ACP reduces to that. The specifications are the visible part of the story. What sits underneath them is a change in where people start a purchase, and that is the part worth planning around.

I’ve been tracking agentic commerce since OpenAI announced Operator in late 2024. The protocol war was inevitable once ChatGPT started processing shopping queries at scale. What surprised me was how fast Google responded with broader scope.

The strategic positioning is clear. OpenAI and Stripe built ACP to capture transaction revenue as AI becomes a shopping interface. Google built UCP to protect its search and advertising business by owning the infrastructure layer. Neither company is being altruistic with “open source.” Both are racing to become the default before the market fragments.

For marketing leaders watching this space, the protocol debate matters less than what it signals: AI agents are becoming a commerce channel with real transaction volume. I’ve written before about how to build AI marketing agents that connect to these systems. The retailers who treat protocols as infrastructure investment will capture share. Those who wait for a “winner” will build integrations under competitive pressure later.

UCP wins on scope. It defines the commerce lifecycle end to end, from product discovery through post-purchase support, and organises it into Services, Capabilities and Extensions. ACP defines the checkout transaction and stops, deliberately, at four endpoints. Neither choice is careless. One specification is scoped to ship quickly, the other is scoped to last. That single difference is the root of most of the others, including integration effort, ongoing maintenance and how much custom engineering a retailer has to supply around the protocol. A retailer choosing here is really answering one question: do you want a protocol for the moment of payment, or a protocol for the whole customer journey?

Winner: UCP

UCP covers the entire commerce lifecycle from product discovery through post-purchase support. It organizes commerce into Services (vertical domains), Capabilities (functional areas like Checkout), and Extensions (optional features). At launch, UCP supports Checkout, Identity Linking, and Order Management capabilities with roadmap items for catalog management and loyalty programs.

ACP defines four core endpoints: Create Checkout, Update Checkout, Complete Checkout, and Cancel Checkout. That’s the complete specification. It’s deliberately narrow, solving the transaction moment without prescribing how discovery or post-purchase should work.

Our take: ACP’s narrow scope means faster implementation but more custom work for everything outside checkout. UCP’s broader scope requires more upfront investment but provides fuller coverage. For teams building long-term infrastructure, UCP’s architecture is more forward-looking.

Architecture is a tie. The two specifications optimise for different things, and each does what it set out to do. ACP is a REST interface with a small endpoint surface, webhook notifications, and Shared Payment Tokens for credential handling, and it can also be exposed as an MCP server. UCP is modular by design and speaks REST, MCP and Google's A2A protocol for agent-to-agent communication. One reflects payment-processing habits, the other platform-building habits. Neither is technically weak. The honest way to score this category is that the better architecture is the one your team can actually operate, which is a statement about your engineers rather than about Stripe or Google.

Winner: Tie

ACP’s architecture reflects Stripe’s payment processing DNA. It’s a RESTful interface with four endpoints, webhook notifications for order updates, and Shared Payment Tokens for secure credential handling. You can also implement it as an MCP server for tighter agent integration.

UCP’s architecture reflects Google’s platform thinking. Services contain Capabilities which support Extensions. This modularity means you implement only what you need. The protocol supports REST, MCP, and Google’s A2A for agent-to-agent communication.

Our take: ACP is simpler to understand and implement. Four endpoints, familiar REST patterns, and Stripe’s existing SDKs. UCP is more complete but requires understanding multiple abstraction layers. Choose based on your team’s capacity for complexity.

ACP wins on payments for one reason: it has already moved real money. Both protocols solve the same problem, letting an agent pay without exposing a shopper's credentials, and they solve it differently. ACP issues Shared Payment Tokens that expire and are bound to a merchant and an amount, with Stripe Radar supplying fraud signals. UCP uses AP2 Mandates, a chain of cryptographic proofs covering intent, cart and payment. On paper the mandate chain records consent more rigorously. In practice, payment infrastructure earns trust by processing transactions without incident, and only one of these has done that at volume. For a retailer weighing elegance against evidence, that record decides it.

Winner: ACP

Both protocols solve the same security problem: AI agents need to initiate payments without exposing user credentials. ACP uses Shared Payment Tokens that are single-use, time-bound, and scoped to specific merchants and amounts. Stripe Radar provides fraud detection signals. The system is production-tested with millions of transactions.

UCP uses AP2 Mandates with cryptographic proofs. An Intent Mandate defines agent permissions. A Cart Mandate captures buyer approval. A Payment Mandate authorizes the transaction. This chain creates non-repudiable evidence of consent at each step, but it’s more complex to implement.

Our take: ACP’s payment model is battle-tested and Stripe-native. If you’re already on Stripe, it’s the obvious choice. UCP’s mandate chain is theoretically more robust but has no production track record yet. For most retailers, ACP wins on proven reliability.

UCP wins on ecosystem, on the strength of who signed up before it shipped. Its launch coalition covers retailers, card networks and payment processors at a scale no previous commerce standard has matched. ACP's answer is different in kind: merchants already transacting, enrolled in bulk through the platforms they were on anyway. Breadth on one side, live volume on the other. For a retailer, the practical question is not which list is longer but which list contains the platforms that run your storefront and process your payments. If Shopify, Stripe or Etsy sit in your stack, part of this decision has already been made for you, and the remaining work is smaller than the coalition announcements suggest.

Winner: UCP

UCP launched with the broadest coalition in e-commerce history. Co-developers include Shopify, Walmart, Target, Etsy, and Wayfair. Payment endorsers include Mastercard, Visa, American Express, Stripe, PayPal, and Adyen. Retail endorsers include Best Buy, Home Depot, Macy’s, and Sephora.

ACP has a three-month head start in production. Etsy’s entire US seller base (over 5 million sellers) has been automatically enrolled since September. Over one million Shopify merchants are eligible. Stripe’s Agentic Commerce Suite launched in December with URBN, Ashley Furniture, Coach, and Kate Spade.

Our take: UCP has broader industry backing. ACP has more production traction. The fact that Stripe, Shopify, and Etsy support both protocols tells you the industry expects coexistence. Neither will “win” in the near term.

ACP wins on integration effort, and the margin is large. For merchants already on Stripe, switching on agentic payments is a configuration change measured in days. Shopify Payments merchants and Etsy sellers were enrolled without doing anything at all. UCP asks for more: a choice between Google's own checkout interface fed by Merchant Center or keeping your custom checkout and wiring agentic transactions into it. Both paths involve real configuration. Weeks to months against days to weeks is the honest comparison, and it narrows only as platforms build enablement into their admin surfaces. A retailer deciding what to do this quarter should treat ACP as the cheap move and UCP as the project.

Winner: ACP

For Stripe merchants, ACP integration is remarkably simple. Enable agentic payments with one line of code. Shopify merchants using Shopify Payments are automatically eligible with no integration required. Etsy sellers were enrolled automatically when ACP launched.

UCP offers two paths: Native (use Google’s checkout interface with your Merchant Center feeds) or Embedded (maintain your custom checkout while enabling agentic transactions). Both require more configuration than ACP’s Stripe-native approach, though Shopify is building admin-level enablement.

Our take: If you’re already on Stripe, ACP takes days to implement. UCP takes weeks to months depending on your integration approach. For teams prioritizing speed to market, ACP wins decisively.

Neither protocol charges for itself. Both are free under Apache 2.0, Google Merchant Center adds no platform fee, and ACP introduces nothing beyond standard Stripe processing rates. Under UCP, processing cost varies with the processor you pick. So the real budget line is engineering, not licensing. ACP's narrow surface takes days to weeks to implement and carries a lighter maintenance load afterwards. UCP's broader scope takes weeks to months and more upkeep, because there is simply more of it to keep working. Anyone costing this should price the first year of maintenance rather than the build alone. Figures verified January 2026; confirm current requirements in each protocol's official documentation before committing budget.

Value analysis: Both protocols are free to use. The real cost is integration effort. ACP’s Stripe-native approach means minimal engineering time for existing Stripe merchants. UCP’s broader scope means more upfront work but potentially less custom development for full-lifecycle features like order management and returns.

Verified January 2026. Check official documentation for current requirements.

When to Choose UCP

• Google Search and Gemini are primary discovery channels
• You need full lifecycle support including order management
• You want flexibility across multiple payment processors
• You’re building long-term agentic commerce infrastructure
• You need custom checkout experiences with brand control

When to Choose ACP

• You’re already using Stripe for payment processing
• You’re on Shopify or Etsy and want automatic enablement
• ChatGPT is a significant traffic source for your audience
• You prioritize speed to market over comprehensive features
• Your checkout is already optimized and you don’t want to rebuild

Across seven scored categories the result is a tie. UCP takes scope, long-term architecture, ecosystem coalition and payment flexibility. ACP takes initial integration speed, production maturity and developer experience. Four to three, with the overall score level. A tie at the bottom of a scorecard usually means the scorecard is measuring two different jobs, and that is what has happened here. The two protocols are not competing on one axis, so averaging them produces a number that describes neither. Retailers should ignore the overall row and read the category rows against their own constraints: budget, timeline, existing payment stack, and where their customers currently start looking for products.

Reading the scores: ACP wins on speed metrics (initial integration, developer experience, production maturity). UCP wins on depth metrics (scope, architecture, ecosystem). This is why most enterprises are layering both: ACP for immediate ChatGPT coverage, UCP for long-term infrastructure.

Layer both. The verdict is not a choice between two protocols; it is an order of operations, because the shoppers each one serves are not the same shoppers. ACP puts you inside ChatGPT. UCP connects you to Google's discovery surfaces. Implement only one and you have decided which half of agent-driven demand to ignore. Sequence by your own constraints: retailers already on Stripe get ACP working first, and retailers whose customers start in Google build toward UCP. Both, eventually. This is an infrastructure decision rather than a bet, so the useful question is not which protocol is better. It is how soon your storefront becomes reachable by agents already shopping on behalf of real customers.

ACP wins on speed to market and production maturity. Three months of live transactions, minimal integration effort for Stripe merchants, and automatic enablement for Shopify and Etsy. If you need to move fast, start here.

UCP wins on scope and ecosystem coalition. Full lifecycle coverage, broad industry support, and connection to Google’s search traffic. If you’re building infrastructure for the next decade, UCP’s architecture is more comprehensive. For a deeper technical dive, see my complete UCP implementation guide.

Choose UCP first if: Google is your primary discovery channel, you need full lifecycle support beyond checkout, or you want flexibility across payment processors. The broader coalition suggests UCP will be the long-term standard.

Choose ACP first if: You’re already on Stripe, ChatGPT is relevant to your audience, or you need something live in weeks rather than months. The production track record provides confidence.

Best of both: Implement ACP now for immediate ChatGPT coverage, then add UCP as it matures. This is exactly what Walmart and Shopify are doing. Follow the enterprise playbook.