UCP Checkout on Google: How to Set Up UCP-Powered Checkout in AI Mode and Gemini

Short answer: UCP-powered checkout puts a Buy button on your product listings inside Google's AI surfaces, so a shopper completes the purchase with Google Pay without leaving AI Mode or the Gemini app. To enable it you meet the technical requirements in Google's developer documentation, submit the interest form, add the native_commerce(checkout_eligibility) attribute to your product data, keep your Merchant Center feed complete and current, and create a Google Pay and Wallet Console account. It is early access, limited to products eligible in the United States, Canada, and Australia, and you remain the seller of record.

What UCP checkout actually is

UCP is the Universal Commerce Protocol, the open standard Google and Shopify announced at NRF on January 11, 2026. Checkout is one capability inside it, named dev.ucp.shopping.checkout in the specification, and it handles the purchase session: cart contents, totals, tax calculation, and the payment step, with or without a human present.

The version most US merchants will meet first is Google's implementation of that capability. Instead of the old flow where a shopper clicks through to your product page and works through your checkout, the transaction completes inside Google's surface. Google's Merchant Center documentation describes it plainly: a Buy button appears on eligible product listings, and the customer pays with a card already stored in their Google Wallet.

The important detail buried in that documentation is who owns the sale. You remain the seller of record, and Google states merchants may be able to customize the integration to preserve their own checkout requirements. This is not a marketplace listing. It is your sale, your customer relationship, and your fulfillment obligation, executed through someone else's interface.

Where UCP checkout appears and who can use it today

Two surfaces at launch: AI Mode in Google Search, and the Gemini app. Both are conversational, so the listing your product appears on is generated in response to a question rather than a keyword search, which changes what your product data has to carry.

Availability is narrower than the announcement coverage suggested. Google's help documentation limits it to products with eligibility in the United States, Canada, and Australia, and to participating merchants and partners. The feature is in early access, which in practice means the interest form is a gate rather than a formality. Payment support is currently standard funding primary account numbers, the FPANs a user has saved in Google Wallet, with expansion left open.

How to set up UCP-powered checkout: the five steps Google publishes

1. Meet the technical requirements. These live in Google's developer documentation for UCP, not in Merchant Center. Read them before you fill in anything else, because they determine whether the rest of the work is a week or a quarter.
2. Submit the interest form. Early access is gated. This is the step that decides your timeline, so do it first even if your data work is not finished.
3. Add the native_commerce(checkout_eligibility) product attribute. This is how you tell Google which of your products can be bought this way. It is per product, not per account, which means you can pilot on a subset of your catalog rather than opening everything at once.
4. Make your Merchant Center product data current and comprehensive. This is the step teams underestimate. An agent answering a shopping question reads your attributes, not your product photography. Missing sizes, stale stock, thin descriptions, and absent shipping data all reduce the odds your product is the one the agent surfaces.
5. Create a Google Pay and Wallet Console account. The payment leg runs through Google Pay, so this account is a hard dependency rather than an optional integration.

What Shopify merchants have to do differently

Considerably less. Shopify co-developed the protocol, and its engineering team published Checkout Kit, which implements UCP capabilities with what Shopify describes as only a few lines of code. If your store runs on Shopify, most of the protocol-level work is already handled and your effort collapses back to product data quality and the Google-side enrollment steps.

That gap is worth naming, because it explains the early volume distribution. A large share of the first UCP transactions will run through Shopify stores, not because those merchants moved faster but because their platform absorbed the integration cost. If you are on a custom stack, budget for building the capability endpoints, the /.well-known/ucp profile, and the checkout state machine yourself.

What is UCP embedded checkout for?

Not every cart can be completed by an agent. Subscriptions, age-restricted goods, custom configuration, unusual tax situations, and anything requiring a signature all break autonomous checkout. UCP handles this with an escalation path rather than pretending it does not exist: the merchant returns a continue_url, and the shopper finishes in an embedded checkout, with the session state preserved.

Treat that as a design requirement rather than a fallback. Some meaningful percentage of agent-initiated carts will land on a human checkout page, and if that page is slow or confusing you lose a sale that an AI surface already did the hard work of sourcing. It is worth taking the time to audit the copy, layout, and CTAs on the page where those handed-off shoppers land, because agentic discovery raises the cost of a leaky checkout rather than removing it.

Does UCP checkout cost merchants a fee?

Google has not published one. The Merchant Center documentation for UCP-powered checkout discloses no take rate, and the protocol itself is free: the specification is on GitHub under the Apache 2.0 license, so there is no licensing cost and no vendor approval to obtain. What you can count on paying is ordinary payment processing on the transaction plus the engineering time to implement.

You will find third-party posts quoting confident percentage figures for UCP against other protocols. Those numbers do not trace back to a Google or Shopify source. If a specific rate matters to your business case, get it in writing through the early access process rather than from a comparison blog, and revisit it, because commercial terms on a preview feature usually land later than the technical spec.

UCP checkout or ChatGPT Instant Checkout first?

They are distribution channels, not competing architectures, and the honest answer is that most US retailers will run both by the end of 2026. The question is sequencing.

Pick based on where your buyers already ask questions. If your category gets researched in Google, the UCP path reaches AI Mode and Gemini and, because it is an open standard rather than one platform's integration, any future agent that implements it. If your traffic skews toward ChatGPT, the setup detail and fee structure for that route is in our ChatGPT Instant Checkout guide for merchants, and the protocol itself in the Agentic Commerce Protocol explainer.

What breaks after you turn it on

Three things, consistently. Order volume arrives without session context, so your attribution model shows a spike of traffic you cannot source. Returns get stranger, because the buyer never saw your returns policy page and an agent summarized it. And customer service inherits questions about a purchase the customer only half remembers making, since the conversation that produced it lived in a chat log you cannot see.

None of that is a reason to skip UCP. It is a reason to fix the data plumbing before the volume shows up rather than after. We walked through the wider readiness checklist in agentic commerce for merchants, and the short version is that clean structured product data solves most of it.

The other side of the counter

Everything above is written from the merchant's seat. If your company is also the one running agents that buy, the same protocol looks completely different, because UCP defines nothing about what a purchasing agent is allowed to spend. There is no per-agent budget in the specification, no approval threshold, and no merchant allowlist for the buyer. Those controls belong to whatever issues the payment credential your agent presents, which is a separate decision from any of this. The category map for that side is in our comparison of AI agent payment platforms.

The short version

UCP-powered checkout is Google's implementation of an open standard, live in early access on AI Mode and Gemini for products eligible in the US, Canada, and Australia. Setup is five documented steps, the heaviest of which is product data quality rather than code. Shopify merchants get most of the integration free through Checkout Kit. No fee has been published. And whichever protocol you adopt, you stay the seller of record, which means the operational work lands on you either way.