Skip to content
Feelbetter

What Is UCP? The Universal Commerce Protocol for Agentic Commerce

Universal Commerce Protocol (UCP): Google's open agentic commerce standard, launched January 2026. How it works, AP2, MCP, A2A and what it means for sellers.

Jayden (Joohyung Im)Founder, Feelbetter · PMP®

Insight7 min read

Analytics charts on a laptop screen
Photo: Luke Chesser / Unsplash

Key takeaways

  • UCP is an open standard that lets AI agents, sellers and payment providers handle everything from product discovery to checkout and post-purchase under the same rules.
  • Google unveiled it on January 11, 2026, and Shopify, Etsy, Wayfair, Target and Walmart took part in developing it.
  • Sellers keep their Merchant of Record status while connecting to multiple AI shopping surfaces through a single integration.

We're heading into an era when you can tell an AI, “Find and buy a two-person tent for weekend camping, under ₩200,000.” But if AI agents had to connect to every online store separately, that scene would stay out of reach. UCP (Universal Commerce Protocol) emerged to solve this problem as a common language for agentic commerce.

UCP is an open standard Google unveiled on January 11, 2026. It was developed with Shopify, Etsy, Wayfair, Target and Walmart, and more than 20 companies, including Adyen, American Express, Best Buy, Mastercard, Stripe and Visa, have announced their support (Google). It is sometimes loosely called the “Universal Commerce Platform,” but in the official name, the P stands for Protocol.

What Is the Universal Commerce Protocol (UCP)?

Google describes UCP as a common language that lets agents and systems work together across the entire shopping journey, from discovery and purchase to post-purchase support. The specification is published at ucp.dev, and because it is open source under the Apache 2.0 license, anyone can implement it.

UCP's basic unit is the capability. A seller declares which capabilities it supports, such as checkout, cart, catalog search and order events, along with their versions, and agents read this declaration and call the capabilities they need (UCP core concepts).

The Problem UCP Solves: The N×N Integration Bottleneck

The Google Developers Blog calls the problem UCP targets the N×N integration bottleneck. When there are many AI shopping surfaces and many sellers, each seller has to build a custom integration for every surface, and that slows the spread of agentic commerce (Google Developers Blog).

Shopify, one of the co-developers, makes the same point. Every merchant has its own payment rules, discount structures, shipping options and regional requirements, which a rigid spec can't accommodate, so the protocol needed a structure that lets you pick and extend only the capabilities you need (Shopify Engineering).

AspectBefore UCPAfter UCP
IntegrationSellers build a separate custom integration for each AI surfaceOne UCP-compliant integration works across multiple surfaces
Capability discoveryPeople check documentation for payment, discount and shipping supportAgents read the seller profile and work it out automatically
Human involvementThe transaction breaks off when the agent can't handle itHanded off to the seller's interface to continue
Post-purchaseShipping and return information varies from surface to surfaceStatus updates standardized through webhooks
Before and after UCP

How a Purchase Flows Through UCP: From Discovery to Order Management

UCP involves four parties: the platform (an AI agent or app) that calls capabilities on the user's behalf, the business (the seller) that is accountable as the merchant, the credential provider (such as a digital wallet) that holds sensitive data like payment methods and shipping addresses, and the payment service provider (PSP) that processes the actual payment (UCP core concepts).

  1. 01Discovery: The seller publishes a profile at the /.well-known/ucp path to announce its supported capabilities and payment methods.
  2. 02Capability negotiation: The agent checks which capabilities both it and the seller support and starts the transaction within that scope.
  3. 03Checkout session: A session is created with the items, quantities, shipping address and discounts, and updated as needed.
  4. 04Handoff to a human: When buyer input is needed, the status changes to requires_escalation, and the agent sends the buyer to the continue_url provided by the seller to pick up where things left off (Shopify Engineering).
  5. 05Payment: The seller's payment handlers are matched with the user's payment method. With the AP2 extension, a mandate that cryptographically proves the user's approval travels along with the payment.
  6. 06Post-purchase: Status changes such as shipment tracking and returns are delivered through webhooks.
Abstract spheres connected by lines
Connecting agents, sellers and payment providers under one set of rules is the heart of UCP.Photo: Mario Verduzco / Unsplash

How does UCP relate to AP2, MCP and A2A?

UCP was designed to work alongside existing agent protocols rather than replace them. Google says UCP is compatible with A2A (Agent2Agent), AP2 (Agent Payments Protocol) and MCP (Model Context Protocol), and the spec supports MCP and A2A as transports alongside REST (ucp.dev).

ProtocolRoleRelationship to UCP
AP2Proves the user's intent and approval in agent payments with signed mandatesAn extension for UCP's payment step. Announced by Google with more than 60 companies in September 2025 (Google Cloud)
MCPA protocol that connects AI agents to external tools and dataA transport for calling UCP capabilities from agent frameworks
A2AA protocol for agents to talk to each other and divide up workA transport for agent-to-agent commerce communication
ACPAn agentic checkout standard released by OpenAI and Stripe in September 2025A standard separate from UCP; several specs coexist in the industry (Stripe)
Key protocols in agentic commerce

UCP's Expansion in 2026: Governance and New Verticals

Since launch, UCP has grown quickly. Most striking is that even companies that compete with one another have joined its governance.

DateMilestone
January 11UCP unveiled and first version released. Checkout in AI Mode and the Gemini app announced for US merchants
April 24Technical committee expanded to 16 seats, with Amazon, Meta, Microsoft, Stripe and Salesforce joining (ucp.dev)
April 28Stripe joins the steering committee, following Google and Shopify
May 20Universal Cart spanning multiple merchants and buy now, pay later with Affirm and Klarna announced. Expansion to Canada, Australia and the UK and moves into hotel booking and food delivery previewed (Google)
July–AugustFood and lodging technical committee formed, with DoorDash, Uber Eats, Booking.com, Expedia, Marriott and others taking part
August 25New version released, with 3DS2 payment security, independent versioning for each capability and groundwork for grocery shopping support
September 25Draft specification for a lodging booking capability published
Key UCP milestones in 2026 (based on ucp.dev announcements and the Google blog)

Korea was not among the expansion countries Google announced in May. But because UCP itself is a public specification anyone can implement, sellers and platforms in Korea can start preparing against the spec now.

What UCP Means for Sellers, D2C Brands and Buying Agents

Sellers: stay the merchant, widen your reach

Under UCP, the seller remains the Merchant of Record and directly owns the customer relationship and business logic (Google Developers Blog). When integrating with Google's surfaces, approved merchants can choose an embedded option that displays their own checkout as is, in addition to the default native checkout (Google merchant guide).

D2C brands: your product data is your store

Agents read data, not screens. Product names and options, inventory, prices, and shipping and return policies have to be structured and accurate in real time before a product can be recommended and bought. That's why the quality of product data now matters as much as product pages do.

Buying agents: when buying on someone's behalf gets common rules

UCP uses the term platform for the party that invokes capabilities on a user's behalf, and gives AI shopping assistants as an example. In effect, finding and buying things for someone else is getting a common set of rules. Still, the protocol won't make the judgment calls for you: whether a product is genuine, whether a seller can be trusted, or whether cross-border shipping and customs clearance are possible. (More on overseas buying agents)

Example scenario

An agent buys a gift from a seller that supports UCP

  1. 1A user asks an AI agent for “a scented candle in the ₩50,000 range for a friend's birthday, arriving by Friday.”
  2. 2The agent reads several sellers' UCP profiles and uses catalog search to pick products that match the criteria.
  3. 3It creates a checkout session, but a gift message is needed, so the status changes to requires_escalation.
  4. 4The agent hands the user off to the seller's checkout page, where the user enters the message and approves the payment.
  5. 5After the order, shipping status arrives through webhooks, and the agent lets the user know the estimated delivery date.

The user hands off searching and comparing, the seller keeps the customer relationship, and a person steps in only when human judgment is needed.

Why Feelbetter, an AI Shopping Concierge, Is Watching UCP

Feelbetter is an AI shopping concierge: customers describe what they want in words, a link or a photo, AI structures the request into a brief, and a human concierge finds and verifies sellers in Korea and abroad, then emails a purchase link within 60 minutes. Turning a fuzzy request into structured criteria points in the same direction as what UCP sets out to do between agents and sellers.

As agentic commerce runs on standards, the time it takes to find sellers and check terms will keep shrinking. The industry is heading that way, and Feelbetter is looking in the same direction. At the same time, we believe the value of a person checking whether a link can be trusted will only grow.

Read moreOfficial UCP announcementsFollow version releases and governance changes straight from the source.ucp.dev

Frequently asked questions

Does UCP stand for Universal Commerce Platform?

The official name is Universal Commerce Protocol. It isn't one company's platform but an open set of communication rules that AI agents, sellers and payment providers all follow, hence the name protocol.

Who created UCP, and who manages it?

Google developed it with Shopify, Etsy, Wayfair, Target and Walmart and unveiled it in January 2026. In April 2026, Amazon, Meta, Microsoft, Stripe and Salesforce joined the technical committee.

How are UCP and AP2 different?

UCP is the common language for the whole commerce process, from discovery to checkout and post-purchase, while AP2 is a payment protocol that proves the user's approval at the payment step with signed mandates. UCP can use AP2 as a payment extension.

Can sellers in Korea use UCP?

The UCP spec is open source, so anyone can implement it. However, UCP checkout on Google's surfaces started in the US, and in May 2026 Google announced plans to expand to Canada, Australia and the UK. Check the official guidance for the countries each service supports.

  • #UCP
  • #Universal Commerce Protocol
  • #Agentic Commerce
  • #AI Shopping
  • #AP2
  • #Google
Feelbetter

Jayden (Joohyung Im) Founder, Feelbetter · PMP®

Started Feelbetter in 2020 as an overseas buying agent and now builds it as an AI shopping concierge. Leads commerce and AI projects backed by Distribution Manager and PMP® certifications.

All articles →