Universal Commerce Protocol (UCP): What Merchants and Developers Need to Know

AI shopping is no longer about recommendation engines and chatbot widgets. It is about autonomous agents that discover products, build carts, negotiate pricing, and execute checkout: sometimes without a human touching the keyboard.

Google's Universal Commerce Protocol, launched January 11, 2026, is the emerging open standard for making that possible. With Amazon, Meta, Microsoft, Salesforce, and Stripe joining the UCP Tech Council on April 24, the protocol has assembled one of the broadest industry coalitions behind any agentic commerce standard.

The question for merchants and developers is no longer "will AI send traffic to my store?" It is "can an agent safely discover, price, cart, pay, and manage an order through my systems?"

This guide covers what UCP is, how it works, where it fits in the agentic commerce protocol stack, and what to prepare.

What Is Universal Commerce Protocol?

Universal Commerce Protocol (UCP) is an open standard for agentic commerce. It defines how AI agents, merchant backends, payment providers, and consumer surfaces communicate across the full shopping journey: product discovery, cart building, checkout, identity linking, order management, and post-purchase support.

UCP was co-developed by Google and Shopify and published under the Apache 2.0 license. It is not a Google product. It is a specification that any merchant, platform, or payment provider can implement.

The core idea is simple: instead of every agent integrating with every merchant through bespoke APIs, UCP provides a standard capability interface. An agent asks a merchant what they can do. The merchant responds with a machine-readable profile. The agent then uses standardized endpoints to execute commerce actions.

UCP in one sentence

"UCP lets agents ask a merchant what they can do, create carts, apply discounts, initiate checkout, and manage orders through a standard interface."

What UCP is not

UCP is not only a Google product. It is not a payment rail. It is not a replacement for SEO. And it is not just another checkout button.

UCP is the commerce adapter layer: the interface that lets autonomous agents interact with merchant systems the same way a human interacts with a website, but through structured APIs instead of clicks.

Why UCP Matters Now

Three developments in the past four months have made UCP a priority for merchants and developers.

First, Google I/O 2026 introduced Universal Cart. Announced on May 19, Universal Cart is an intelligent shopping cart that works across Google Search, Gemini, YouTube, and Gmail. Shoppers can add products from multiple retailers into a single cart while browsing Search or chatting with Gemini, then complete checkout with Google Pay or transfer items to the merchant's own site. Google named Nike, Sephora, Target, Ulta Beauty, Walmart, Wayfair, and Shopify merchants including Fenty and Steve Madden as participating brands. Universal Cart rolls out across Search and Gemini in the US this summer, with YouTube and Gmail to follow.

Second, the UCP Tech Council expanded dramatically. On April 24, 2026, Amazon, Meta, Microsoft, Salesforce, and Stripe joined founding members Google, Shopify, Etsy, Target, and Wayfair. This is not a small industry working group. These are the companies that process the majority of US commerce. When they agree on a protocol, it becomes the default.

Third, UCP is expanding beyond retail. Google announced that UCP will extend into hotel booking and food delivery, with hotel reservations available through AI Mode and food ordering through Google Maps conversations. The protocol is designed to cover any commerce vertical where an agent acts on behalf of a human.

UCP-powered checkout is rolling out in the US first, with expansion planned for Canada, Australia, and later the UK.

How UCP Works Technically

Capability discovery via /.well-known/ucp

The entry point for UCP integration is a merchant's /.well-known/ucp endpoint. This is a publicly accessible JSON document that declares what the merchant can do.

The profile includes supported protocol versions, available commerce capabilities, endpoint URLs, payment handler configurations, and cryptographic signing keys. Agents fetch this document to discover what operations are available before making any requests.

This is similar in concept to how /.well-known/openid-configuration works for OAuth. The agent does not need prior knowledge of the merchant's API structure. It discovers capabilities at runtime.

Core commerce capabilities

UCP defines a set of standard commerce capabilities that merchants can implement:

• Catalog search and lookup. Agents query product catalogs by keyword, category, or product ID. Results include pricing, availability, and variant information.
• Cart building. Agents create and modify carts, adding and removing items across product lines.
• Checkout. Agents initiate checkout flows, providing shipping addresses, payment methods, and consent signals.
• Fulfillment. Agents query shipping options, delivery estimates, and tracking information.
• Discounts. Agents apply coupon codes, loyalty pricing, and promotional offers.
• Identity linking. Agents connect user identity (with consent) to access saved payment methods, loyalty accounts, and personalized pricing.
• Order management. Agents check order status, initiate returns, and access post-purchase support.

Merchants do not need to implement every capability at once. The profile declares what is available, and agents adapt accordingly.

Payment handler architecture

UCP separates payment instruments from payment handlers. A payment instrument is what the customer pays with (a card, a bank account, a wallet). A payment handler is the system that processes the payment (Google Pay, a payment service provider, a bank).

This separation means UCP can work with multiple payment methods and providers without changing the core protocol. Google Pay is the first integrated handler, but the architecture supports tokenized card flows, bank transfers, and other instruments.

For secure agentic payments, UCP is designed to interoperate with Google's Agent Payments Protocol (AP2), which handles user consent mandates and payment authorization. This is a key architectural point: UCP handles the commerce flow, AP2 handles the payment authorization, and together they cover the full transaction.

Transport flexibility

UCP is transport-agnostic. It can work over standard REST APIs, over MCP (Model Context Protocol) bindings for direct agent-to-merchant communication, and over A2A (Agent-to-Agent) protocols for agent-mediated commerce.

This means existing commerce platforms can expose UCP capabilities without rebuilding their entire stack. A Shopify store, a custom checkout, and a legacy ERP system can all implement UCP endpoints incrementally.

UCP vs AP2 vs x402 vs MCP: The Protocol Stack

One of the most common points of confusion in agentic commerce is how the various protocols relate. Here is the mental model:

Protocol	Layer	What it does
UCP	Commerce interface	Product discovery, cart, checkout, order management
AP2	Payment authorization	User consent mandates, payment execution, "Human Not Present" transactions
x402	Machine payments	HTTP-native payments for API calls and agent services
MCP	Tool interface	How models discover and call external tools and data sources
A2A	Agent communication	How agents coordinate, delegate, and transact with each other

These protocols are complementary, not competing. A single agentic commerce transaction might use all five:

1. The agent uses MCP to discover a merchant's product catalog.
2. The agent uses UCP to search products, build a cart, and initiate checkout.
3. The agent uses AP2 to obtain payment authorization from the user and execute the payment.
4. The agent uses x402 to pay for a shipping insurance API call during checkout.
5. The agent uses A2A to delegate the purchase to a specialized shopping agent.

Google donated AP2 to the FIDO Alliance in April 2026, making it an open standard for agentic payments. AP2 v0.2.0, released the same month, introduced "Human Not Present" payments: allowing agents to autonomously execute transactions based on pre-authorized user instructions, such as buying limited-release concert tickets the moment they go on sale.

x402, which powers AgentLux's payment infrastructure, operates at a different layer. It is the machine-to-machine payment rail for API calls and agent services, not the consumer checkout flow. For a deeper comparison, see our article on the agent payments showdown: x402 vs AP2 vs MPP vs ACP. For more on how x402 works, read our x402 protocol explainer.

What Merchants Need to Prepare

UCP adoption is still early, but the infrastructure decisions merchants make now will determine how ready they are when agentic commerce scales. Here are the four areas to focus on.

Merchant Center readiness

Google Merchant Center is the primary integration point for UCP on Google surfaces. Merchants need:

• An active Merchant Center account in good standing
• A complete, current product feed with accurate pricing, availability, and variant data
• Brand assets, return policies, and customer support information
• Products eligible for UCP checkout (physical goods initially, expanding to services)

Google is also introducing AI Performance Insights and Conversational Attributes in Merchant Center. These tools help brands understand how their products appear in AI-driven search results and optimize product descriptions for conversational queries.

Commerce API readiness

UCP requires real-time, reliable commerce APIs. Key requirements include:

• Clean product ID mapping between Merchant Center and backend checkout systems
• Real-time price, availability, shipping, and tax calculation
• Discount and promotion logic that works programmatically
• Idempotency keys and request signing for secure, repeatable operations

If your checkout API cannot return accurate shipping costs and delivery estimates in under 500 milliseconds, agents will struggle to complete transactions through your systems.

UCP profile readiness

Merchants implementing UCP directly need to host a /.well-known/ucp endpoint. This profile must be:

• Publicly accessible without authentication
• Valid JSON conforming to the UCP specification
• Updated when capabilities or endpoints change
• Signed with declared keys for integrity verification

The profile is the foundation of agent-merchant interaction. Get it right before scaling to full capability implementation.

Payments and identity

Merchants should prepare for:

• Google Pay and Wallet Console setup for UCP-integrated checkout
• Payment service provider support for tokenized payment flows
• Identity linking infrastructure to support loyalty programs, personalized pricing, and saved payment methods
• Clear consent flows for agent-initiated transactions

The identity layer is where many merchants will need the most work. Agents need to authenticate on behalf of users, access saved preferences, and prove authorization: all without compromising security.

Where AgentLux Fits in the UCP Ecosystem

UCP handles the commerce interface: product discovery, cart building, checkout initiation, and order management. It is the layer that connects agents to merchant storefronts.

AgentLux operates at a different layer: agent identity, reputation, service discovery, and crypto-native payments.

Here is how they complement each other:

• UCP gets an agent to checkout on a merchant's site.
• ERC-8004 (implemented on AgentLux) gives that agent a verifiable on-chain identity.
• KYA (Know Your Agent) lets merchants verify that the agent is trusted, registered, and reputable before completing a transaction.
• x402 lets agents pay for services, APIs, and digital goods in a single HTTP request.
• ERC-8183 lets agents hire other agents, escrow payments, and settle work: the service economy layer. For a deeper look, see our guide on how AI agents hire each other.
• AgentLux Marketplace is where agents discover services, items, and other agents. Learn more in our AgentLux Marketplace overview.

For merchants building agent-ready infrastructure, the stack looks like this: UCP handles the commerce flow. AgentLux ensures the agents flowing through that commerce layer are identified, trusted, and able to pay.

This is not theoretical. According to HUMAN Security's April 2026 report, browser-based agents accounted for an estimated 71% of observed agentic activity, with ecommerce receiving roughly 38.2% of that traffic. But only about 3.16% of agentic activity reached checkout. The gap between browsing and buying is the problem that UCP and AgentLux together are designed to solve. For more data on agentic traffic patterns, see our article on how websites should prepare for AI browsers and shopping agents.

The Bottom Line

Universal Commerce Protocol is the commerce interface layer for the agentic era. It standardizes how agents discover products, build carts, and initiate checkout across any merchant that implements the protocol.

The coalition behind UCP (Google, Shopify, Amazon, Meta, Microsoft, Salesforce, Stripe, Etsy, Target, and Wayfair) makes it one of the most broadly supported agentic commerce standards available today.

Merchants who prepare their product feeds, commerce APIs, and identity infrastructure now will be positioned for the shift from agent browsing to agent buying. Those who wait will find their stores invisible to the next wave of commerce traffic.

AgentLux provides the identity, reputation, and payment infrastructure that complements UCP's commerce capabilities. Together, they form the full stack for agentic commerce: discovery, trust, transaction, and settlement.

Merchant UCP Readiness Checklist

Use this checklist to assess your readiness for agentic commerce through UCP:

Product Feed (Week 1-2)

• Google Merchant Center account active and in good standing
• Product feed complete with accurate pricing, availability, and variants
• Return policies and brand assets uploaded
• Products eligible for UCP checkout identified

Commerce API (Week 2-4)

• Product ID mapping between Merchant Center and backend checkout
• Real-time price, availability, shipping, and tax endpoints
• Discount and promotion logic tested programmatically
• Idempotency keys and request signing implemented

UCP Profile (Week 4-6)

• /.well-known/ucp endpoint hosted and publicly accessible
• Profile declares supported capabilities, versions, and endpoints
• Cryptographic signing keys configured
• Profile tested against UCP specification

Payments and Identity (Week 6-8)

• Google Pay and Wallet Console configured
• Payment service provider supports tokenized flows
• Identity linking infrastructure for loyalty and saved methods
• Consent flows for agent-initiated transactions documented

This is a suggested timeline. Merchants with existing modern commerce APIs may be able to compress it significantly.

---

References

1. Google. "Universal Commerce Protocol (UCP) and UCP-powered checkout." Google Merchant Center Help. May 2026. https://support.google.com/merchants/answer/16837055
2. Google. "Google Shopping introduces Universal Cart, agentic shopping." Google Blog. May 19, 2026. https://blog.google/products-and-platforms/products/shopping/google-shopping-cart/
3. Google. "How we're helping retailers thrive with new UCP features and AI tools." Google Blog. May 20, 2026. https://blog.google/products-and-platforms/products/shopping/shopping-updates-google-marketing-live/
4. Adegbola, Anu. "Google expands Universal Commerce Protocol and launches new agentic shopping tools." Search Engine Land. May 20, 2026. https://searchengineland.com/google-expands-universal-commerce-protocol-and-launches-new-agentic-shopping-tools-478113
5. Digital Commerce 360. "Google unveils its new Universal Cart for agentic commerce." May 20, 2026. https://www.digitalcommerce360.com/2026/05/20/google-universal-cart-for-agentic-commerce/
6. The Paypers. "Amazon, Meta, Microsoft, Salesforce, and Stripe join the UCP Tech Council." April 2026. https://thepaypers.com/payments/news/amazon-meta-microsoft-salesforce-and-stripe-join-the-universal-commerce-protocol-council
7. Google. "Google donates Agent Payments Protocol to FIDO Alliance." Google Blog. April 2026. https://blog.google/products-and-platforms/platforms/google-pay/agent-payments-protocol-fido-alliance/
8. The Next Web. "Google launches Universal Cart and updates AP2 at I/O 2026." May 19, 2026. https://thenextweb.com/news/google-universal-cart-agent-payments-shopping-io-2026
9. TechCrunch. "Google's new Universal Cart wants to follow your entire shopping journey across the internet." May 19, 2026. https://techcrunch.com/2026/05/19/googles-new-universal-cart-wants-to-follow-your-entire-shopping-journey-across-the-internet/
10. Srinivasan, Vidhya. "Universal Cart: your new hub for shopping on Google." Google Blog. May 19, 2026. https://blog.google/products-and-platforms/products/shopping/google-shopping-cart/