Share

13 min

The short version

A plain-English guide to agentic commerce and Google's Universal Commerce Protocol: how UCP checkout and Universal Cart actually work, how the protocol compares with OpenAI's ACP and the AP2 payments layer, how merchants enroll, and the trust, legal, and coverage limits as of November 2026.

Summarize with AI

Editorial Disclosure & Affiliate Notice

This content is published for informational and educational purposes only. It is not intended as a substitute for professional, legal, financial, or medical advice. AIUnpacker is funded through clearly labeled sponsored articles and reviews, relevant paid link placements, and affiliate commissions where disclosed. Commercial partnerships help fund the free editorial library. Sponsored work is labeled, and a payment does not change the verdict.

  • For educational purposes only. Nothing here should be taken as a guarantee, recommendation, or professional recommendation.
  • AI-assisted editing. Drafts are produced with AI assistance and get a human pass before they go up.
  • Opinions are our own. Also, we are not affiliated with most tools we cover unless explicitly stated.
  • Information may be outdated. Verify pricing, features, and policies directly with the vendor.
  • Last reviewed: . Published .

Read more on our About page, Terms and Editorial Policy.

Agentic commerce is shopping where an AI agent does the work for you: researching products, comparing prices, building a cart, and sometimes completing the purchase. Google’s Universal Commerce Protocol (UCP) is the open standard that makes those handoffs safe and uniform: agents read a merchant’s UCP manifest, assemble multi-item carts, and pay with tokenized credentials backed by cryptographic proof of your consent. Its first consumer face, Universal Cart, went live in the US on October 15, 2026 in Search’s AI Mode and Gemini, with merchants keeping the seller-of-record role.

What is agentic commerce, exactly?

Agentic commerce flips the usual flow. Instead of you opening tabs and clicking “add to cart,” an AI shopping agent (Gemini, ChatGPT, a browser assistant) performs those steps on your instruction. You set the intent; the agent executes.

The idea went mainstream in under a year. OpenAI launched Instant Checkout in ChatGPT on September 29, 2025, built on the Agentic Commerce Protocol (ACP) it co-developed with Stripe. Google had published its Agent Payments Protocol (AP2) two weeks earlier, and Sundar Pichai introduced UCP in his NRF keynote on January 11, 2026. Universal Cart followed on October 15, 2026.

The early numbers explain the rush. Per Adobe’s October 2026 analysis, AI-referred traffic to US retail sites grew 127% year over year in August 2026, and in September it converted 90% better than non-AI traffic with 83% more revenue per visit. eMarketer’s December 2025 forecast puts AI-platform-driven US ecommerce at $144.45 billion by 2029, about 8.8% of total US retail ecommerce.

What is Google’s Universal Commerce Protocol?

UCP is an open-source commerce standard, licensed under Apache 2.0, that standardizes the entire transaction between AI agents and merchant systems, not just the payment moment. Per the spec site at ucp.dev, its core capabilities are “Catalog Search and Lookup, Cart Building, Identity Linking, Checkout, and Order Management.” Lodging booking exists as a draft spec; food service is coming soon.

Google built it with Shopify, Etsy, Wayfair, Target, and Walmart, and launched it with endorsements from more than 20 partners including Mastercard, Visa, Stripe, Adyen, and Best Buy. By November 2026, ucp.dev listed a wider shopping co-developer group (Amazon, Microsoft, Meta, and Salesforce among them) plus 50 endorsing organizations and dedicated lodging and food programs.

Why does a protocol matter? Google’s engineers described the problem as an “N x N integration bottleneck”: every merchant building bespoke connections for every AI surface. Under UCP, a business integrates once, and any compatible agent can transact with it.

Technically, UCP runs over REST and JSON-RPC transports, with Model Context Protocol (MCP) and Agent2Agent (A2A) support built in. Payments are deliberately modular: the spec separates what you pay with (your card, the instrument) from payment handlers, the processors that move the money, and delegates payment trust to AP2, which issues cryptographically signed mandates for each purchase.

One principle appears in every document: merchants “remain the Merchant of Record.” The merchant (not Google, not the agent) owns the customer relationship, sends the confirmation, and handles returns.

How a UCP purchase works, step by step

Here’s the flow per Google’s UCP developer guide and its January demo, where an agent bought flowers from a sample shop end to end.

  1. The agent finds the merchant’s manifest. It fetches the JSON manifest at /.well-known/ucp and reads which capabilities the business supports, in the demo, a service called dev.ucp.shopping with checkout, discount, and fulfillment. No manifest, no agentic purchase.
  2. Discovery and catalog search. The agent queries the catalog for products, prices, variants, availability, and ratings.
  3. Cart building. The spec’s cart capability assembles a multi-item cart that persists across AI surfaces: what shoppers see as Universal Cart.
  4. Identity linking (optional). Through OAuth 2.0, the agent can attach your loyalty account without ever seeing your password.
  5. Checkout session created. The agent POSTs line items, buyer information, and payment handlers to the merchant’s /checkout-sessions endpoint. The merchant replies with a checkout ID and full totals, including tax and shipping.
  6. The agent updates the session. In Google’s demo it applied the discount code “10OFF” and the total dropped from $35.00 to $31.50.
  7. Payment authorization. AP2 issues payment mandates and verifiable credentials creating “cryptographic proof of user consent.” Google’s implementation draws on cards saved in Google Wallet, kept separate from the payment handlers doing the processing.
  8. Order and post-purchase. The merchant (still the seller of record) sends the confirmation and handles support. Order Management covers real-time webhooks for tracking, returns, and refunds. At any point you can transfer the cart to the merchant’s own site instead.

What shoppers actually see: Universal Cart in AI Mode and Gemini

Universal Cart is UCP’s first big consumer rollout: per Google’s October 15, 2026 launch post, it’s live in the US across Search (including AI Mode) and the Gemini app, timed for holiday shopping.

Here’s what you see: a cart that travels with you across Google surfaces, price-drop and restock alerts powered by Google’s Shopping Graph of 60+ billion listings, and promo-code and card-perk suggestions built on Google Wallet. On eligible listings, a “Buy” button starts UCP checkout; you pay through Google Pay in a few taps, or transfer items to the merchant’s own cart.

Google named Nike, Sephora, Target, Ulta Beauty, Walmart, and Wayfair as launch partners, alongside many Shopify merchants, with merchants staying the seller of record.

How merchants join UCP (and what it costs)

Enrollment runs through Google Merchant Center, and Google’s help page is blunt about access: UCP checkout is “available for select merchants at this time.” The integration guide says it’s rolling out US-first, with Australia and Canada next, for US-sold products only.

The steps, per Google’s Merchant Center preparation guide:

  1. Start with a Merchant Center account in good standing, with products approved for free listings.
  2. Complete account settings. Add an account-wide return policy (cost, window, full-policy link) and customer support contact info: this powers the “Contact Merchant” link on order confirmations.
  3. Review the product restrictions. UCP checkout excludes subscriptions, installments, personalized goods, refurbished and final-sale items, pre-orders, age-restricted goods, rentals, services, and virtual items, among others.
  4. Update your feed attributes. The key one is native_commerce(checkout_eligibility), which defaults to FALSE: items only show the “Buy now” button if you set it TRUE. Cart inclusion is opt-out via native_commerce(cart_eligibility), and products needing regulatory warnings use notice_type and notice_message fields.
  5. Build the integration. Native checkout is the default; an embedded iframe option exists for approved merchants with bespoke branding needs.
  6. Test and declare readiness. The UCP integration hub in Merchant Center validates endpoints in sandbox and production (checkout creation, shipping updates, transaction completion, and cart transfers) before you go live.

The protocol itself is free and open source on GitHub. Google’s docs don’t publish a separate participation fee for UCP or Universal Cart as of November 2026. Real costs come from payment processing rates and integration engineering. Merchants must create a Google Pay & Wallet Console account, and direct integration without a PSP requires encryption setup plus PCI compliance documentation. Confirm fees with Google and your processor before budgeting.

UCP vs ACP vs AP2: which protocol does what

In one line: UCP and ACP overlap on checkout, UCP uses AP2 for payment trust, and ACP runs parallel on the OpenAI side.

ProtocolBacked byStatus (November 2026)What merchants should do
UCP. Universal Commerce ProtocolGoogle, co-developed with Shopify, Etsy, Wayfair, Target, Walmart; Amazon, Microsoft, Meta, and Salesforce now listed at ucp.devOpen source (Apache 2.0); powers Universal Cart and agentic checkout: live for selected US merchants; Canada, Australia nextClean up Merchant Center data and submit the interest form if you sell eligible US goods
ACP. Agentic Commerce ProtocolOpenAI with StripeOpen standard; first implemented in ChatGPT; Instant Checkout retired March 2026, purchases moved to retailer appsKeep ACP on your roadmap; define per-agent accept/decline rules in checkout
AP2. Agent Payments ProtocolGoogle-originated, donated to the FIDO Alliancev0.2 spec advancing in FIDO’s agentic authentication and payments working groupsNo direct action needed; watch card-network launches like Mastercard Agent Pay and Visa Intelligent Commerce

The relationships matter more than the acronyms. UCP builds on AP2 for payment mandates, so they’re complementary, not competitors. ACP is the OpenAI-side checkout standard, per agenticcommerce.dev, businesses can accept or decline transactions “on a per agent, per transaction, or custom logic basis.” Large merchants will realistically end up supporting both.

The honest limitations of agentic commerce right now

Four problems are real as of November 2026.

Access is narrow. UCP checkout is limited to selected US merchants, and the ineligible-category list is long: anything subscription-based, personalized, pre-orderable, or age-restricted is out. If you sell those, agentic checkout isn’t an option yet.

In Worldpay’s 2026 survey of more than 8,000 consumers across seven markets, 74% would let an AI agent compare prices for them, but only 21% would let an agent actually complete the purchase.

That trust gap is the biggest constraint on the whole category.

Retailers are conflicted. A CNBC-reported audit of 51 large US retailers’ robots.txt rules (September 2026) found 37 of them blocking AI shopping agents (mostly by accident, through legacy anti-bot rules) and only 11 with a deliberate, explicit position. Amazon blocks external agents while pushing its own “Buy For Me” tool, and DataDome reported spoofed AI agents made up 70.9% of the bad bot traffic it observed. Agents aren’t guaranteed access to any store.

The law is only partially settled. On August 4, 2026, the Ninth Circuit vacated the injunction against Perplexity’s Comet browser in Amazon’s suit, holding that an agent acting on a user’s instruction isn’t the developer “accessing” a computer under the CFAA: the human user is the responsible party. That covers one circuit, one statute, and one stage of one lawsuit. If you’re a retailer setting access policy, get actual legal counsel.

The first big experiment already failed. OpenAI retired Instant Checkout in March 2026, roughly six months after launch, after only about a dozen merchants went live; TechCrunch reported that purchases moved to retailer apps. That doesn’t kill agentic commerce (Universal Cart is a different architecture) but it’s a warning against treating any timeline as inevitable.

What to do next

  • If you’re a shopper: try Universal Cart in AI Mode for holiday price-drop tracking: it’s free, and you can transfer any item to the retailer’s own cart instead. Review the cards and permissions you’ve linked in Google Wallet first.
  • If you run a small store: do the Merchant Center basics now: accurate prices and inventory, approved free listings, return policies, support contacts. They help with free listings today and make you eligible for UCP tomorrow. Selling eligible physical goods in the US? Submit the interest form.
  • If you’re at a larger retailer: evaluate UCP and ACP side by side, set a deliberate robots.txt position on AI agents instead of inheriting one, and brief your legal team on the Comet ruling.
  • If you’re a developer: start with the spec on GitHub and the manifest format; Google’s integration hub sandbox is the practical testing ground.

FAQ

What is agentic commerce?

Agentic commerce is buying where an AI agent (Gemini, ChatGPT, or a browser assistant) does the shopping work for you: researching products, comparing prices, building carts, and sometimes completing checkout on your behalf. It emerged through 2025 launches (OpenAI’s Instant Checkout and Google’s AP2 payments protocol) and went mainstream with Google’s Universal Commerce Protocol in January 2026 and Universal Cart in October 2026. You set intent; the agent executes.

What is Google’s Universal Commerce Protocol (UCP)?

UCP is an open-source commerce standard, licensed under Apache 2.0, announced by Google on January 11, 2026 with Shopify, Etsy, Wayfair, Target, and Walmart. It gives AI agents and merchants a shared language for catalog search, cart building, identity linking, checkout, and order management. Merchants expose a machine-readable manifest, agents build carts and checkout sessions through defined APIs, and payments ride on AP2’s cryptographic mandates. Merchants stay the merchant of record.

How does Google Universal Cart work?

Universal Cart, live in the US since October 15, 2026, is a single cart that works across Google Search’s AI Mode and the Gemini app. You save items from different retailers in one place, get price-drop and restock alerts from Google’s Shopping Graph of 60+ billion listings, and check out with Google Pay, or transfer items to a merchant’s own cart. Merchants stay the seller of record and handle confirmations and support.

How do merchants join Universal Cart and UCP?

Merchants start with the UCP integration interest form in Google Merchant Center. Google says the program is open to selected merchants first, US-only at launch with Canada and Australia next. You need a Merchant Center account in good standing with products approved for free listings, account-wide return policies, support contact info, and the native_commerce(checkout_eligibility) feed attribute on eligible items. Then integrate the UCP APIs, test in the integration hub, and declare readiness.

What is the difference between UCP, ACP, and AP2?

They cover different layers. UCP (Google) standardizes the whole commerce journey: catalog, cart, identity linking, checkout, and orders. ACP (OpenAI with Stripe) focuses on checkout sessions and passing payment credentials securely to agents. AP2 (Google-originated, now under the FIDO Alliance) is the payments trust layer: cryptographically signed mandates proving the user authorized a specific purchase. UCP builds on AP2 for payments; ACP is a parallel checkout standard merchants may need to support separately.

Is agentic commerce safe to use?

The rails are designed for safety: UCP payments use tokenized credentials, and AP2 mandates create a cryptographic record of exactly what you approved, which helps against runaway or hallucinated purchases. But the ecosystem is young. A Ninth Circuit ruling in August 2026 eased the legal status of agents browsing websites, spoofed-agent fraud is rising per DataDome, and consumer trust remains low. Check your agent’s permissions and payment settings before delegating purchases.

How much does UCP cost merchants?

The UCP spec itself is free: it is open source under Apache 2.0. Google’s documentation does not list a separate UCP or Universal Cart participation fee as of November 2026; costs come from payment processing through your PSP and integration engineering. Merchants need a Google Pay & Wallet Console account, and direct integration without a PSP requires encryption setup and PCI compliance documentation. Confirm fees with Google and your processor before budgeting.

What are the main limitations of agentic commerce today?

Coverage is thin: UCP checkout is limited to selected US merchants, and Google excludes subscriptions, pre-orders, personalized goods, rentals, and more. Consumer trust lags: only 21% in Worldpay’s survey would let an agent complete a purchase. Many retailers still block agents through legacy bot rules; a CNBC-reported audit found 37 of 51 big US retailers doing so. And OpenAI retired Instant Checkout after roughly six months. It’s early days.

What should my business do about agentic commerce next?

Start with basics that pay off regardless: a clean Merchant Center feed with accurate prices and inventory, approved free listings, clear return policies, and reachable support contacts. If you sell eligible physical goods in the US, submit the UCP integration interest form and watch the rollout. Larger retailers should evaluate both UCP and ACP and set a deliberate robots.txt position on AI agents rather than relying on legacy anti-bot rules.

Sources

Weekly digest

Get our weekly AI digest

The latest AI tools, prompts, and insights — short, useful, every week.

No spam. Unsubscribe anytime.

AIUnpacker Editorial

Articles are written for a specific question. Sponsored work is labeled.