The one-sentence answer: UCP (Google) runs the cart and order. ACP (OpenAI + Stripe) executes the payment. MCP (Anthropic) feeds real-time data to the agent. In the best 2026 implementations, all three run together. See also: How to Identify AI Agent Traffic in Google Analytics 4. See also: Cookieless Affiliate Tracking. See also: WebMCP Is Here. See also: 2026 UCP Compliance and Risk Checklist for Merchants.
Why This Comparison Matters Now
Three major AI-ecosystem protocols are most often compared for agentic commerce in 2026. Merchants, developers, and enterprise architects are being asked to choose — or to explain to leadership why they might need all three. This guide cuts through the noise with a definitive breakdown of what each protocol actually does, where it operates in the stack, and when you need it.
Protocol Overview at a Glance
| Protocol Specification | Primary Champion | Core Focus | Transport Protocol | Payment Settlement Model | Interoperability Strategy |
|---|---|---|---|---|---|
| Universal Commerce Protocol (UCP) | Google, Shopify, and Retail Industry Consortium. | Universal machine commerce standard across all AI surfaces. | REST, JSON-RPC 2.0, and WebSockets. | FIDO AP2 hardware-attested cryptographic clearing. | Master standard; bridges natively to ACP and MCP. |
| Agentic Commerce Protocol (ACP) | OpenAI and Stripe. | In-chat product feed discovery and checkout sessions. | HTTP REST and Webhooks. | Stripe PaymentIntents and virtual machine cards. | UCP manifest maps directly into ACP product entities. |
| Model Context Protocol (MCP) | Anthropic. | Standardized client-server tool invocation runtime. | JSON-RPC 2.0 over stdio and Server-Sent Events (SSE). | Ephemeral token clearing via MCP commerce tools. | Expose UCP tools via MCP servers for Claude. |
| Convergence Architecture | Unified Industry Working Group. | Cross-protocol message translation and adapters. | Dual-stack REST and SSE edge gateways. | Multi-network token routing (Visa, Google Pay). | Deploy UCP as core; wrap with ACP and MCP adapters. |
| Enterprise Recommendation | Independent Merchants and Platforms. | Eliminates proprietary walled-garden vendor lock-in. | Open W3C standards and decentralized manifests. | Hardware-bound biometric non-repudiation. | Build to UCP first for 100% universal market coverage. |
UCP — Universal Commerce Protocol
Developed by: Google, co-designed with Shopify.
What it does: UCP is an open REST standard that defines how AI agents interact with merchant storefronts end-to-end. It covers the commerce lifecycle: product catalog discovery, real-time inventory queries, cart creation, checkout initiation, and fulfillment status. It operates via the /.well-known/ucp discovery endpoint that merchants publish on their domain.
Who uses it: Any merchant wanting to sell through Google AI Mode, or any AI agent that follows the UCP standard for cross-platform shopping. Merchants implement UCP by publishing a structured endpoint and ensuring their product feed meets Google Merchant Center requirements.
Strengths: Backed by Google’s distribution (Universal Cart Oct 15, 2026; US + Canada checkout), open REST standard with REST as the recommended default transport, works across UCP-compliant agents (not just Google’s).
Limitations: Live checkout for shoppers in the US and Canada (Canada shopper-side checkout live since Nov 4, 2026 — lululemon, select Shopify merchants, Shoppers Drug Mart, Simons; single-item at launch; retailer remains seller of record). Does not handle the payment layer directly — relies on processors like Google Pay (on Google AI surfaces, allowed_auth_methods effectively PAN_ONLY in the UCP flow). Requires Merchant Center validation; simplified Merchant Center self-serve integration is a 2027 item.
ACP — Agentic Commerce Protocol
ACP is OpenAI’s protocol and is outside this site’s November 2026 verified sheet coverage. The ACP details below are vendor-described and unverified — check OpenAI/Stripe docs before acting.
Developed by: OpenAI, built with Stripe as the payment infrastructure layer.
What it does: ACP focuses specifically on the payment execution step — the moment an AI agent needs to move money on behalf of a user. It defines how agents hold, present, and use Shared Payment Tokens: cryptographic credentials that authorize an agent to charge a stored payment method without exposing raw card data.
Who uses it: OpenAI’s ChatGPT Shopping uses ACP for its Etsy integration. Merchants who want their Shopify stores accessible via ChatGPT’s Instant Checkout flow need ACP-compatible payment handling (Stripe makes this automatic for Stripe-powered merchants).
Strengths: Purpose-built for agent payment security. Shared Payment Tokens prevent raw card data exposure to agents. Stripe’s network means instant compatibility for millions of merchants already on Stripe.
Limitations: Vendor-described as payment-only (does not handle product discovery or order management in vendor materials — unverified).
MCP — Model Context Protocol
Developed by: Anthropic (introduced Nov 2024; under Agentic AI Foundation since Dec 9, 2025; current revision 2026-07-28; transports stdio + Streamable HTTP; authorization optional OAuth 2.1). Broad ecosystem adoption claimed in vendor/ecosystem materials — unverified roster.
What it does: MCP is the data access layer of the agentic stack. It defines how an AI agent (Claude or any MCP-compatible agent) connects to external systems — your ERP, inventory database, pricing engine, or CRM — to pull real-time context before making commerce decisions. MCP is not a checkout protocol. It’s a secure, permissioned API bridge: the merchant runs an MCP server that defines exactly what the agent can query, read, and write.
Who uses it: Developers building agents that need real-time inventory or personalization data via an MCP server. See how Claude Marketplace uses MCP for agentic commerce.
Strengths: Protocol-agnostic — an MCP server can feed data to agents running on UCP, ACP, or any other protocol. Merchant controls the data surface it exposes. GDPR and ecosystem-breadth claims are vendor/ecosystem-described and unverified.
Limitations: Not a checkout or payment protocol — cannot complete a purchase on its own. Requires merchant to run and maintain an MCP server (UCP-over-MCP is Early Access Beta; REST is the default).
How They Fit Together: The Full-Stack Architecture
The three protocols are not competitors — they operate at different layers of the same transaction. Here is how a complete agentic commerce transaction flows through all three:
- Agent receives user intent (“Buy me new running shoes under $120, size 10, same brand as last time”)
- MCP layer: Agent queries the merchant’s MCP server for real-time inventory, the user’s purchase history, and current pricing rules
- UCP layer: Agent uses the merchant’s /.well-known/ucp endpoint to confirm product availability, create a cart, and initiate checkout
- ACP layer (vendor-described, unverified): Agent presents payment credentials per OpenAI/Stripe materials
- UCP layer: Order confirmation and fulfillment status flow back through UCP to the agent and user
A merchant fully implemented on all three layers is reachable by any AI agent — Google’s, Anthropic’s, OpenAI’s, or a third-party agent built on any of these standards.
Decision Guide: When to Prioritize Which Protocol
| Your Situation | Start With | Then Add |
|---|---|---|
| Shopify merchant wanting Google AI Mode visibility | UCP | MCP for personalization |
| Etsy seller or Stripe-powered DTC brand | ACP | UCP for broader agent reach |
| Enterprise with SAP/Oracle ERP, B2B focus | MCP | UCP for transaction layer |
| EU merchant with strict GDPR requirements | MCP (data residency control) | UCP with GDPR-compliant processors |
| Regulated industry (healthcare, financial services) | MCP (audit trail control) | UCP after compliance clearance |
| DTC brand wanting maximum agent reach | UCP + ACP simultaneously | MCP for personalization layer |
The Protocol War Is Not a Zero-Sum Game
Early coverage framed UCP vs ACP vs MCP as a standards war with a single winner. That framing is wrong. These protocols solve different problems at different layers of the same stack. UCP declares an MCP transport binding (UCP-over-MCP Beta, REST default); Mastercard Verifiable Intent and Visa TAP are separate network frameworks, not UCP features.
Merchants often implement UCP for transactions alongside MCP for data access; any ACP decision should be checked against current OpenAI/Stripe docs (unverified here). UCP requires the /.well-known/ucp endpoint and feed; MCP requires running a server (stdio + Streamable HTTP).
Related Resources
- UCP Merchant Implementation Guide
- Configure Your /.well-known/ucp Discovery Endpoint
- Claude Marketplace and MCP: How Anthropic Fits the Agentic Stack
- Where Can You Use Agentic Commerce Today?
- UCP ERP Integration Guide
Related reading
Updated November 8, 2026: Updated Nov 2026 to correct checkout geography to US + Canada shopper-side live (Nov 4, 2026), add UCP spec/platform version and MCP revision/governance details, and bound unverified ACP and endorsement claims to vendor docs. First published May 8, 2026.
Frequently Asked Questions
How do UCP, ACP, and MCP differ in their approach to agentic commerce?
UCP provides an open, vendor-neutral commerce standard for catalog discovery and settlement; ACP is OpenAI and Stripe’s protocol optimized for ChatGPT; and MCP is Anthropic’s general client-server tool runtime used by Claude.
Can a single ecommerce store support all three protocols simultaneously?
Yes, by deploying the UCP manifest as the underlying source of truth, developers can expose ACP endpoints for ChatGPT and an MCP server for Claude using lightweight translation adapters.
Which protocol should developers implement first to maximize AI assistant coverage?
Developers should implement UCP first because its open specification maps cleanly into both ACP and MCP, ensuring compatibility across Google Gemini, OpenAI, Claude, and independent agent frameworks.

Leave a Reply