Who is behind UCP?

Google says it co-developed UCP with Shopify, Etsy, Wayfair, Target and Walmart, and that more than 20 other companies endorsed it at launch (Google, TechCrunch, InfoQ).

The specification is open source, published on GitHub under the Apache 2.0 licence (the repository, PPC Land). A Tech Council steers its technical direction. The founding members were Google, Shopify, Etsy, Target and Wayfair, so Walmart helped write the standard without a founding seat on the council. Amazon, Meta, Microsoft, Salesforce and Stripe joined on 24 April 2026 (the UCP release, PPC Land).

How does UCP work?

A business publishes a JSON profile at /.well-known/ucp that lists the services it supports, the capabilities inside them and the payment handlers it accepts (the UCP specification, PPC Land). An agent reads that file and finds the store's features, endpoints and payment options without a hard-coded integration (Google Developers Blog, Shopify Engineering).

Google's launch post named checkout, identity linking and order management as the first capabilities (Google Developers Blog), and TechCrunch described the standard as covering discovery through to post-purchase support (TechCrunch). On 19 March 2026 Google added Cart, so an agent can put several items from one store in a basket, and Catalog, which pulls live prices and stock. Identity linking lets a shopper carry loyalty pricing and member benefits across platforms (Google, Search Engine Journal). Search Engine Journal notes that Cart and Catalog were published as draft specifications.

The same capability can be offered over a REST API, the Model Context Protocol (MCP) or Agent2Agent (A2A) (Google Developers Blog, TechCrunch).

What is a payment handler?

UCP keeps the payment instrument, such as a card or a wallet, separate from the handler, the processor that takes it (Google Developers Blog, InfoQ). A store lists the handlers it accepts in its profile, and each checkout response says which ones are available for that basket (PPC Land, Shopify Engineering).

The handler is the part a merchant's existing processor supplies. Worldline launched one on 14 September 2026 through Global Collect, its cross-border platform, so a Global Collect merchant declares its payment configuration once and takes cards, mobile wallets and European payment methods on any UCP-connected AI platform (Worldline, Electronic Payments International). Worldline describes itself as one of the first in Europe to do it. The 14 September brief covers what the release left out.

How is UCP different from ACP and AP2?

ACP, the Agentic Commerce Protocol, is the checkout standard OpenAI and Stripe published with Instant Checkout in ChatGPT on 29 September 2025 (Stripe, PPC Land). The difference the sources draw is how the agent finds the store. PPC Land's explainer says ACP has merchants apply and submit catalogues while UCP relies on the agent discovering the store for itself, and Forrester describes OpenAI compressing the path from discovery to instant checkout (PPC Land, Forrester).

AP2, the Agent Payments Protocol Google announced in 2025, sits under UCP for the payment itself. Google says UCP is compatible with it, and InfoQ describes UCP integrating with it for secure payments (Google Developers Blog, InfoQ, TechCrunch). The ACP and AP2 page sets those two side by side.

Where can shoppers use UCP?

In the United States first. UCP-powered checkout began rolling out on 11 February 2026 for Etsy and Wayfair in AI Mode in Search and the Gemini app, with Shopify, Target and Walmart named as coming soon (Google, PYMNTS).

At Google Marketing Live in May, Google said checkout would reach Canada and Australia in the coming months and the UK later (Google, PPC Land). On 15 September Google's business page still says checkout rolls out to Canada and Australia soon (Google Business), and its Merchant Center help tells merchants in the United States, Canada and Australia that shoppers may see it soon (Merchant Center help).

What does UCP leave unsolved?

Who pays when an agent's purchase goes wrong. The store stays merchant of record (Google, PPC Land), and Google's FAQ adds that it keeps full control of the customer relationship. The protocol does not set how fraud and liability are handled. Merkle lists it among the things UCP leaves undefined, and Forrester asks who is liable for processing the return when an agent places a wrong order because the product content it read was generated inaccurately (Merkle, Forrester).

Worldline's release says nothing about disputes on agent-initiated purchases either (Worldline), a gap the news desk flagged the day it came out. Google's FAQ puts the merchant-of-record duties on the store, so the dispute terms that matter sit in the store's own processor contract. The liability page covers the wider question.

What should a merchant do now?

If you sell through Google Merchant Center, onboarding runs there, and Google said in March it was simplifying that process over the coming months (Google, Search Engine Journal). Before building a checkout of your own, ask your processor whether it publishes a UCP payment handler and what its terms say about a disputed agent purchase. The second answer is the one Worldline's release left blank.