AI-driven commerce is moving from product discovery toward completed transactions. That shift creates a clear challenge for commerce leaders: a storefront can be optimized for human shoppers and still be difficult for an AI system to understand, operate, and trust.
That is where the Universal Commerce Protocol (UCP) comes into play.
UCP is an open standard designed for AI-driven commerce. It enables agentic actions and direct buying on AI Mode in Google Search and Gemini, with additional surfaces planned. Rather than requiring every AI platform to build a separate custom connection to every merchant, UCP establishes a shared language for capabilities such as product discovery, checkout, payments, and order management.
For merchants, UCP may become an important channel for high-intent shoppers. However, it is not a plug-in that eliminates commerce architecture work. It requires clean Merchant Center data, reliable APIs, tokenized payment processing, accurate inventory, and strong operational controls.
What Is the Universal Commerce Protocol?
UCP connects merchants, AI surfaces, payment providers, and other commerce participants through a common, open standard.
At launch, UCP enables direct buying experiences on:
- AI Mode in Google Search
- The Gemini web application
- The Gemini mobile application
The goal is to reduce the distance between a customer’s request and a completed purchase. Instead of searching, visiting several product pages, and navigating a traditional checkout, a shopper may be able to discover a product and complete the transaction within an AI-led interaction.
This is a significant development in agentic commerce, but the merchant remains central to the transaction.
Merchants remain the Merchant of Record
UCP does not transfer ownership of the customer relationship to Google. Merchants remain the Merchant of Record, retaining:
- Customer data and relationships
- Responsibility for fulfillment and service
- Control over post-purchase experiences
- Responsibility for shipping, returns, and applicable policies
- Their own terms and conditions
Google displays the merchant’s terms during checkout, and the customer must accept them. Standard privacy regulations and consent requirements continue to apply.
Google retains standard order information on the user’s “My orders” page until the user requests deletion. Merchants must still follow their own retention, financial recordkeeping, and compliance policies within their systems.
How UCP Changes the Commerce Journey
UCP is broader than a payment protocol. It is intended to support the wider commerce journey, from discovery through checkout and order updates.
That distinction matters. AP2, the Agent Payments Protocol, focuses on secure agent-led payment transactions. UCP orchestrates the broader purchase lifecycle, while AP2 can operate as a specialized payment layer within UCP, particularly as more autonomous agent scenarios emerge.
UCP is also designed to interoperate with:
- AP2 for agent-led payments
- A2A for agent-to-agent communication
- MCP for Model Context Protocol integrations
- REST APIs and MCP bindings
- Adapters for other protocols
Its primitives are intended to map directly to familiar retail operations. Native SDKs are also available through the UCP GitHub organization.
The practical implication is straightforward: brands should not think of UCP as a replacement for their commerce platform. It is an interface layer that exposes selected commerce capabilities to approved AI surfaces.
Native vs. Embedded Checkout
Google currently describes two integration paths.
Native checkout
Native checkout integrates checkout logic directly with Google’s AI surfaces. It is the default path, designed to unlock the full agentic potential of UCP as the standard expands.
Native checkout is likely the stronger long-term option for merchants that can expose reliable commerce services through APIs. It offers a more direct experience, but it also requires deeper technical readiness.
Embedded checkout
Embedded checkout is an optional path for approved merchants with highly bespoke branding or complex checkout flows that require an iframe-based solution.
While embedded checkout may preserve more of an existing checkout presentation, it is not the default path for every merchant. Approval is required, and teams should evaluate whether an iframe experience introduces additional performance, security, analytics, or operational complexity.
In contrast, native checkout requires more direct integration work but aligns more closely with the direction of agentic commerce.
What Implementing UCP Actually Requires
Google’s implementation guide outlines a practical sequence for merchants pursuing UCP.
1. Prepare Merchant Center
Merchant Center remains the foundation for product discovery. Before implementation, review:
- Product feeds and identifiers
- Shipping configuration
- Return policies
- Brand assets
- Business contact information
- Product availability and pricing
This is more than a feed audit. AI systems need complete and consistent information to compare products and make safe recommendations. As Red Van’s guide to machine-readable product data for agentic commerce explains, thin catalog data can become a conversion problem when machines cannot confidently interpret your products.
2. Join the waitlist and receive approval
UCP is still an early program. Merchants must join Google’s UCP waitlist, work through the integration process, and receive approval before going live on Google’s AI surfaces.
That approval requirement is an important planning consideration. UCP should be treated as an emerging channel, not as an immediate replacement for existing acquisition and checkout channels.
3. Configure the Google Pay payment handler
UCP supports tokenized payments through payment handlers. Your payment service provider must be able to process Google’s tokens; most major global PSPs support Google Pay.
You do not need to offer Google Pay checkout on your own website or mobile application to implement UCP. However, Google Pay configuration must be explicitly provided in your UCP profile because UCP is a separate integration.
Pay close attention to the implementation details:
- UCP configuration uses snake_case parameters rather than camelCase.
- Google AI surfaces currently support PAN_ONLY for allowed_auth_methods.
- Other methods may be included in configuration but are not used in the UCP checkout flow.
4. Publish a UCP profile
The UCP profile allows Google to discover your supported services and capabilities. It also exposes payment handlers and public keys used for signature verification.
This profile is central to capability negotiation. It tells the consuming surface what your commerce stack can support, rather than requiring the platform to assume that every merchant behaves the same way.
5. Implement native checkout endpoints
Native checkout requires three core REST endpoints for:
- Session creation
- Session updates
- Session completion
These endpoints must connect reliably to your existing cart, pricing, inventory, tax, shipping, payment, and order systems. This is where API readiness becomes critical.
As Red Van’s API readiness guide for autonomous commerce outlines, agent-ready APIs need durable checkout state, clear contracts, idempotency, machine-readable errors, and predictable recovery paths.
6. Choose guest or account-linked checkout
Guest checkout is the default and requires no additional identity implementation.
Merchants can also support account-linked checkout through OAuth 2.0 identity linking. This can support deeper experiences over time, including loyalty and member benefits, but it introduces additional decisions around authentication, consent, account matching, and data access.
7. Sync order status
Merchants remain responsible for order operations after payment. UCP uses Google’s webhooks to support order lifecycle updates.
Your order management and fulfillment systems must therefore provide accurate status information. A successful checkout followed by unclear or stale order updates will quickly undermine customer trust.
Operational Details That Can Make or Break UCP
UCP does not relieve the merchant of responsibility for their commerce systems. It makes weaknesses more visible.
Inventory must be checked in real time
Merchants are responsible for real-time inventory validation. If an item becomes unavailable during checkout, the merchant API must return the out_of_stock error code so Google can show an appropriate message.
An inventory feed that updates every few hours may be insufficient for high-demand products, limited releases, or complex multi-location fulfillment.
Address validation remains the merchant’s responsibility
Google does not automatically validate or block international shipping addresses. Destination details, including address_country, are passed to the merchant during Create Checkout or Update Checkout calls.
If an address falls outside supported shipping zones, the response should use an appropriate UCP error such as:
- address_undeliverable
- address_unverifiable
Error severity also matters. Recoverable errors must be marked with the severity recoverable in the messages array. Otherwise, the customer may see a blocking error screen instead of being prompted to correct the issue.
Monitoring and security require deliberate controls
Google may send health checks with:
User-Agent: Google-UCP-Prober/1.0
Merchants should verify genuine Google requests using reverse DNS lookups or published IP ranges. Country-based geo-restriction is not a reliable control because Google dynamically manages outbound traffic. Firewalls should instead authenticate requests using OAuth 2.0 bearer tokens or other secure signatures.
For version migration, Google recommends creating a separate API endpoint for the newer UCP specification. This isolates traffic and gives Google a path to route traffic back to the original endpoint if problems occur.
What Commerce Teams Should Do Now
Most brands do not need to implement UCP immediately. They should, however, prepare the foundations that UCP and other agentic commerce standards will require.
Start with four workstreams:
Audit Merchant Center data
- Review product feed completeness.
- Confirm the accuracy of variant, price, and availability.
- Clean up brand assets, shipping, and returns information.
Check machine-readable commerce data
- Make product attributes, policies, and fulfillment constraints structured and consistent.
- Identify conflicts between your PIM, ERP, storefront, Merchant Center, and OMS.
Test API and inventory readiness
- Confirm that cart and checkout APIs support session creation, updates, and completion.
- Test real-time inventory checks and price recalculation.
- Review errors, retries, idempotency, authentication, and logging.
Review payment and governance controls
- Ask your PSP whether it can process Google’s tokens.
- Define how UCP traffic will be identified and monitored.
- Establish guardrails for automated checkout, rate limits, and customer data access.
These recommendations build directly on Red Van’s 5-Point AI Agent Readiness Check and its guidance on governance and trust in agentic commerce.
What Is on the UCP Roadmap?
The public UCP roadmap points toward deeper support for the full consumer journey, including:
- Multi-item carts
- Loyalty and member benefits through account linking
- Native cross-sell and upsell modules
- Post-purchase capabilities
- Broader global market support
- Localized payment interoperability
- Expansion into industries such as lodging and food
The roadmap is directional rather than a delivery commitment. Its significance is that UCP is being designed to move beyond isolated purchases toward a broader commerce layer.
UCP is also open source, with the standard available on GitHub. That gives commerce teams an opportunity to review the specification, monitor changes, and contribute feedback as the ecosystem develops.
The Strategic Takeaway
Choosing native UCP integration does not improve product ranking in Google listings. UCP-integrated offers simply gain a direct purchase option.
The more important question is whether your commerce stack can reliably support that option.
UCP may create a new route from high-intent discovery to purchase, while merchants retain control of their customer relationships, data, policies, and fulfillment. But that opportunity depends on the fundamentals: machine-readable commerce, dependable APIs, accurate inventory, tokenized payments, and clear governance.
For brands evaluating their next step, the right starting point is not necessarily a full platform rebuild. It is an assessment of your current data, integrations, checkout services, and operational controls.
Red Van Workshop’s commerce services team helps B2C, D2C, and B2B brands evaluate complex Salesforce and Shopify environments, improve API readiness, and build practical paths toward AI-ready commerce. If UCP is on your roadmap, we can help you identify the gaps and prioritize the work without overcommitting to an emerging standard.
Frequently Asked Questions
Does UCP replace my ecommerce platform?
No. UCP is an integration standard that connects your commerce capabilities to Google’s AI surfaces. Your existing commerce platform, payment provider, order systems, and fulfillment operations remain important.
Will Google own my customer relationship?
No. Merchants remain the Merchant of Record and retain ownership of customer relationships and data, subject to applicable privacy, consent, and retention requirements.
Do I need Google Pay on my website?
No. Your website or app does not need to support Google Pay checkout. However, your PSP must be able to process Google’s tokens, and the Google Pay configuration must be explicitly provided in your UCP profile.
Is UCP ready for every merchant today?
Not yet. UCP is an early, evolving standard. Merchants must join the waitlist and receive Google approval before going live. The broader protocol ecosystem, including AP2, A2A, and MCP, continues to mature.
How should I prepare for UCP?
Begin with Merchant Center data quality, shipping and returns policies, payment tokenization readiness, inventory synchronization, checkout APIs, error handling, monitoring, and governance. These investments support UCP and other future AI commerce channels.