Universal Commerce Protocol (UCP)
The Universal Commerce Protocol (UCP) is an open standard that lets AI agents, apps, and other platforms work with businesses through one shared language. It covers the commerce journey from catalog search and cart building to checkout, payment, and order updates.
Each business publishes a machine-readable profile that declares what it supports. Any compatible platform can read that profile and use those capabilities without a custom integration.
UCP launched for retail in January 2026. The same model applies to B2B buying, and a draft specification extends it to hotel bookings. Throughout, the business remains the merchant of record and controls pricing, terms, fulfillment, and the customer relationship.
Why the Universal Commerce Protocol exists
As AI agents reshape retail discovery, every new interface risks becoming another channel to build and maintain. A business selling through Gemini, ChatGPT, Microsoft Copilot, or a customer’s procurement agent could otherwise need a separate connector for each one. Those connectors may use different data structures and rules for products, carts, inventory, delivery promises, and payment authorization. Multiply that work across many agents and businesses, and the point-to-point model quickly becomes impractical.
UCP replaces those one-off connections with a shared contract. It is not a hosted marketplace, nor does it replace your commerce engine. PIM, ERP, payment, and order management systems remain responsible for product data, pricing, inventory, transactions, and fulfillment. UCP defines how outside platforms discover and use those capabilities, whether the underlying stack is monolithic or built on a composable commerce architecture.
Google introduced UCP in January 2026 after co-developing it with Shopify, Etsy, Wayfair, Target, and Walmart. Google uses the standard for direct buying in AI Mode and Gemini, while Shopify uses it to make merchant capabilities available to agent-led channels. “Shopify UCP” refers to Shopify’s implementation, not a separate protocol. Amazon, Meta, Microsoft, Salesforce, and Stripe joined the UCP Tech Council in April 2026. The public Universal Commerce Protocol GitHub repository provides the specification, SDKs, samples, and conformance tests under the Apache 2.0 license.
UCP vs. MCP, A2A, AP2, and ACP
UCP shares parts of the transaction path with MCP, A2A, AP2, and ACP, but each protocol has a different primary job. Their relationship also goes beyond general compatibility: MCP and A2A can carry UCP interactions, and AP2 can extend UCP checkout with verifiable authorization.
Protocol | Primary job | Relationship to UCP |
Connects AI models to external tools and data. | UCP capabilities map to MCP tools. A business can expose operations such as catalog search or checkout through an MCP server. | |
A2A (Agent2Agent) | Lets agents discover one another, exchange information, and hand off tasks. | UCP can use A2A as a transport. A business can declare UCP support through its A2A agent card so another agent can transact with it using structured commerce data. |
AP2 (Agent Payments Protocol) | Records verifiable purchase intent and authorization through signed mandates. | AP2 is an optional UCP checkout extension. When both parties support it, the business receives cryptographic evidence tying the buyer’s approval to a specific checkout state. |
OpenAI and Stripe’s open standard connecting AI agents (starting with ChatGPT) to merchant commerce services. | ACP overlaps with UCP but remains a separate standard. OpenAI has moved away from standalone Instant Checkout toward product discovery and merchant-owned checkout, so businesses appearing on Google and ChatGPT may support both protocols. |
In practice, several protocols may support one purchase. A shopping agent could find a merchant agent through A2A, call the UCP catalog and checkout operations through MCP, and attach an AP2 mandate that proves what the buyer approved.
MCP and A2A handle the interaction, UCP defines the commerce objects and behavior, and AP2 provides verifiable authorization. ACP uses scoped payment tokens, and AP2 records buyer intent and approval through signed mandates. These roles reflect the current specifications, and their boundaries may change as governance, capabilities, and implementations develop.
How does the UCP work?
The Universal Commerce Protocol works through discovery and negotiation. A business publishes what it supports in a public profile, and any compatible AI agent or platform reads that profile to complete a purchase without a custom integration. The business controls every step, from cart pricing to order creation.
- The business hosts a JSON profile at /.well-known/ucp that lists its protocol version, services, capabilities, payment handlers, and transports.
- Before any commerce call, the agent fetches that profile to learn what the business offers and which endpoints to use.
- The agent sends its own profile with each request. The business matches it against its own capabilities and version dates and switches on only the ones both profiles list.
- The agent searches the catalog and adds items to a cart the business manages. The business’s systems provide prices, taxes, and stock.
- If a step requires the buyer, like accepting terms or verifying age, checkout pauses, and the business returns a link for the buyer to complete it.
- The agent shows the buyer the final cart, including taxes, shipping, and delivery estimates, and waits for explicit approval.
- The agent obtains a payment token through a handler the business accepts and completes checkout. The business’s payment provider processes the payment, and the business creates the order.
- Shipped, delivered, and returned events reach the agent as signed webhooks.
An agent can only add what it can find, so intent-based catalog enrichment often determines whether step 4 succeeds.
Core architecture of Universal Commerce Protocol
The eight steps above rely on a small set of building blocks defined in the UCP specification. Each block has a single job, so a business can add or update one capability without touching the rest of its implementation.
Building block | What it does |
Roles | Four parties take part. The platform, an agent, or an app acts for the buyer. The business sells and stays a merchant of record. The credential provider holds the buyer’s payment credentials. The payment service provider (PSP) processes the payment. |
Business profile | The public entry point at /.well-known/ucp declares what commerce operations the business supports. Platforms publish a profile too. During negotiation, the business picks the highest version both sides support and drops any extension whose parent capability isn’t active. |
Services | Top-level domains that group related capabilities and their endpoints. Shopping is the main service today, and lodging is in draft. |
Capabilities | Single commerce features, including catalog, cart, checkout, order, and identity linking. Each defines the baseline schema and API contract for one task and carries its own date-based version, so a business can adopt a newer checkout without upgrading everything else. |
Extensions | Add-ons that specialize a capability without changing its core schema, like discounts, fulfillment, or AP2 mandates. Any company can publish extensions under its own domain name. |
Payment handlers | Specifications published by payment providers, like Google Pay or a regional wallet. The business lists the ones it accepts, and the agent works with tokens instead of raw card details. |
Transports | REST suits standard web endpoints. MCP and A2A suit agent runtimes. Embedded loads the business’s own checkout inside the platform’s interface. |
Trust | Requests and order updates are cryptographically signed, so a business can verify a platform it has never dealt with before. Identity linking uses OAuth 2.0 when a platform acts on a buyer’s account. |
Few enterprises will hand-build every binding. A protocol-aware agentic commerce platform can expose one catalog and checkout through UCP, ACP, MCP, and A2A together, so adding a protocol or a version becomes a connector change, not a rebuild.
UCP capabilities across the commerce journey
Each UCP capability covers one stage of a purchase, from finding a product to tracking the order. A business chooses which capabilities to declare in its profile. It can start with checkout alone and add the others as its systems are ready.
The shopping service currently defines five capabilities:
- Catalog makes the business’s products available to platforms, so they can search the range and retrieve details like variants, prices, and availability. Results come from the business’s own search, so its search and merchandising rules still apply.
- Cart keeps the buyer’s basket on the business’s side while they shop. The business calculates the totals and updates them as items change.
- Checkout turns the cart into a purchase. It collects shipping and payment details and redirects the buyer to merchant-hosted pages when a step requires direct interaction (such as terms acceptance or age verification).
- Order reports what happens after the purchase. It sends shipment, delivery, and return updates from the business’s order management system to the platform.
- Identity linking lets buyers connect their existing account with the business to the platform through OAuth 2.0, so saved details and loyalty benefits carry over.
Not every platform supports every capability yet. What a buyer can do depends on both sides: the capabilities a business declares and the ones a platform has built. Google uses UCP to power direct buying in AI Mode and Gemini currently offers checkout on eligible product listings for selected US merchants through Merchant Center. Payment runs through Google Pay, with PayPal support announced. In October 2026, Google began rolling out a Merchant Center hub where selected merchants can test their UCP integration.
The same model works beyond consumer retail. UCP defines roles by who offers a capability and who uses it, not by industry, so it fits B2B commerce buying flows as well. A draft lodging service applies it to hotel search and booking, and food ordering is listed as coming soon. Both are still in development, so check their status before planning around them.
Business value and merchant control
For merchants, the primary return on UCP is integration leverage. A profile and its underlying endpoints connect to any compatible platform, whether an assistant like Google AI Mode, a consumer shopping agent, or an enterprise procurement tool. Retailers operating across web, mobile, and physical stores through a unified commerce platform can expose existing product, price, and order data to agentic channels without deploying a parallel stack.
Crucially, UCP preserves the merchant-of-record model. The seller continues to set list prices and promotions, calculate applicable taxes, fulfill orders, handle returns, resolve payment disputes, and maintain regulatory compliance. Third-party platforms facilitate discovery and capture purchase intent, but the customer relationship and order record remain under the merchant’s control.
Maintaining that authority is essential as automated agents mediate more consumer demand. Every enterprise entering agentic channels must manage the trade-off between discovery reach, customer ownership, and transactional control.
How to prepare for the Universal Commerce Protocol
Adopting UCP is mainly a matter of making existing commerce systems accessible to AI agents and other platforms. A structured sequence helps engineering and digital commerce teams pilot the protocol without disrupting operations.
- Start with a narrow pilot. Choose one journey, like checkout for a single product category or region, and decide which platforms you want to reach first.
- Audit product data and business policies. Agents rely on clear, unambiguous attributes to judge whether a product fits a request. Product feeds need structured variants, accurate inventory, and explicit shipping, tax, return, and warranty policies. AI catalog enrichment can close attribute gaps at scale, and an AI discoverability checklist helps identify what agents can’t read today.
- Expose core commerce services through stable APIs. Your UCP endpoints pass each request to backend services, so the commerce engine needs reliable APIs for search, cart management, inventory reservations, tax calculation, and order creation. API-first stacks map to UCP capabilities directly. Monolithic platforms often need an adapter layer first, the kind of groundwork involved in modernizing a legacy platform. Merchants on Shopify start further ahead, because Shopify implements UCP for its merchants.
- Decide between native and embedded checkout. In native checkout, the platform collects delivery preferences and passes a tokenized payment credential directly to your backend. In embedded checkout, your own responsive checkout page opens inside the platform’s interface. Native checkout reduces friction for the buyer. Embedded checkout makes it easier to keep complex promotions or custom verification steps.
- Align payments and publish your business profile. Confirm with your payment provider which payment handlers and tokens it supports. Then create the JSON profile declaring your protocol version, capabilities, endpoints, and payment handlers, and host it at /.well-known/ucp. Keep the first version minimal and declare only what the pilot covers.
- Test edge cases and failure paths. Before routing live traffic, test failed capability negotiation, unsupported versions, stale inventory, price recalculations, payment declines, session timeouts, cancellations, duplicate requests, and hand-offs to the buyer.
- Measure and expand. Track how much of your range platforms can discover, session completion, checkout success, error and retry rates, response times, and how often purchases need human help. Add capabilities or platforms one at a time, and assign an owner for profile changes and version upgrades.
Security, operations, and limits
UCP specifies the messages that platforms and businesses exchange, but it doesn’t run the systems behind them. Keeping every UCP interaction safe and reliable, from catalog search to order updates, depends on the trust architecture a business builds around the protocol. The table shows where the protocol’s job ends and the business’s begins.
Area | What UCP provides | What the business still owns |
Duplicate requests | Idempotency keys on requests that change state, like completing checkout | Backend systems that honor those keys, so a retried request never charges twice or splits an order |
Platform access | Public profile discovery and signed requests | Deciding whether to accept unfamiliar platforms and protecting services with rate limiting, signature verification, and abuse detection |
Buyer data and consent | OAuth 2.0 identity linking | Granting each platform only the access it needs, sharing the minimum data per step, and recording buyer consent |
Fraud and chargebacks | Tokenized payment credentials | Screening transactions with merchant-side risk engines |
Privacy and compliance | Not covered by the protocol | Meeting privacy and regulatory obligations in each market |
Failed multi-step flows | Checkout status updates and a hand-off link to the buyer | Orchestration with retries, timeouts, compensating refunds, and a route to a person |
When a purchase fails partway
Most production issues show up in that last row. Picture a UCP checkout where the payment goes through but the order fails to save in the business’s systems. The business needs to catch the mismatch, refund the buyer, send an accurate order update back to the platform, and pass the case to support staff, ideally with conversational AI that already has the order details in front of them. Recovery like this is what keeps a UCP integration dependable across every platform it serves. It relies on the same retry and monitoring practices any agentic AI system needs in production.
Before you publish a UCP profile, an agentic commerce readiness assessment can show whether your product data, commerce APIs, payment controls, and operating model are ready to support the capabilities you plan to declare.

