To sell through Google AI Mode and Gemini with a native Buy button, a merchant needs Google's Universal Commerce Protocol (UCP) checkout: a Merchant Center feed with the native_commerce attribute, a UCP checkout integration and a Google Pay & Wallet Console account. As of November 2026 Google limits it to selected merchants with US, Canadian or Australian product eligibility. AP2, Google's Agent Payments Protocol, is a separate layer for proving what the shopper authorised. This guide explains both from the merchant's side, based on Google's developer and help pages; we have not completed an onboarding ourselves.

UCP announced at NRF
11 Jan 2026
Product eligibility for UCP checkout on Google
US, CA, AU
You, per Google's help page
Seller of record
UCP and AP2 licences
Apache 2.0

What is UCP, and who is behind it?

UCP is an open standard for agents to discover products, build a cart and check out on a merchant's own system. Sundar Pichai announced it at NRF on 11 January 2026, saying a Buy button paid with Google Pay was coming to AI Mode and Gemini. The UCP site lists Google, Shopify, Etsy, Wayfair, Target, Walmart, Amazon, Microsoft, Meta, Salesforce and Stripe as co-developers, with Visa, Mastercard, American Express, PayPal and Adyen as endorsers. It states plainly: "You remain the Merchant of Record."

Stripe's UCP page describes the building blocks as checkout, OAuth identity linking, order webhooks and payment-token exchange. Stripe sits on UCP's Tech Council.

Google's developer page adds that UCP supports REST and MCP bindings, offers native SDKs, and is compatible with AP2, A2A and MCP. It is expanding beyond retail: Lodging and Food are waitlist-only verticals.

How does UCP checkout work on Google?

  1. Your products are already in Merchant Center. UCP uses your existing shopping feeds.
  2. Listings that carry the native_commerce (checkout_eligibility) attribute are eligible to show a Buy button. Google's help page says only those listings display it.
  3. When the shopper taps Buy, the agent negotiates the order with your checkout through UCP.
  4. The shopper pays with Google Pay using details saved in Google Wallet. Google says the feature currently uses standard card numbers (FPANs).
  5. You receive the order as seller of record and handle fulfilment.

Native or embedded checkout?

Google offers two paths:

Path Who it suits How it works
Native checkout (default) Most merchants Your checkout logic integrates directly with AI Mode and Gemini
Embedded checkout (optional) Specific approved merchants with bespoke branding or complex flows An iframe-based checkout inside Google's surface

Google's developer page says the Gemini app integration is "coming soon", while Shopify's March 2026 post says UCP already powers checkout for select brands in "the Gemini app". Treat Gemini app coverage as partial and check your own Merchant Center account.

What is not documented yet

Google's developer page lists loyalty account linking and post-purchase tracking and returns as roadmap items rather than shipped features. It does not publish a full list of feed rules or payment-provider certification steps. If you depend on those, ask Google during onboarding rather than assuming.

How do you sign up?

  1. Check eligibilityProducts eligible in the US, Canada or Australia.
  2. Submit the interest formLinked from Google's Merchant Center help page.
  3. Implement UCP checkoutNative path by default, via REST or MCP, or a platform that supports UCP.
  4. Create a Google Pay & Wallet Console accountRequired for the Google Pay flow.
  5. Add native_commerce to listingsOnly tagged products get the Buy button.
  6. Accept the UCP Checkout termsGoogle publishes separate terms of service.

Google says the protocol "will be available in phases" through an early access programme.

If you are on Shopify

Shopify co-developed UCP and manages Google surfaces through Agentic Storefronts. In September 2026, Search Engine Roundtable reported that Google emailed Merchant Center users on UCP-capable platforms and enabled native checkout for matched Shopify stores. Merchants who want shoppers to finish on their own site can reportedly turn it off under Sales channels > Agentic in Shopify admin. See Shopify and agentic commerce.

Where does AP2 fit?

AP2, the Agent Payments Protocol, launched on 16 September 2025. It answers a different question from UCP: not "what is in the cart" but "can this agent prove the shopper approved this payment?" It does that with signed mandates.

The current AP2 site describes two mandates, each with two stages:

Mandate Open stage Closed stage
Checkout Mandate Constraints set in advance, for autonomous buying Approval of one specific final checkout
Payment Mandate Payment limits set in advance Approval of one specific payment

The launch spec called these the Intent and Cart mandates; you will still see those earlier names in older material. AP2 covers both human-present and human-not-present purchases, is an extension of Google's A2A protocol, has a v0.2 release and has been donated to the FIDO Alliance. Mastercard was a named launch partner; we found no Visa statement on AP2. The AP2 GitHub repository is Apache-2.0 and showed no tagged releases when checked.

For a merchant, AP2 matters most in the "human not present" case, such as Google buying when a tracked price drops. A mandate gives you and your payment provider evidence of what the shopper authorised in advance. Our plain-English AP2 explainer covers the shopper's view.

Do you need to implement AP2 directly?

Probably not yet. Google's merchant docs present UCP as the integration and AP2 as a compatible protocol, and payment providers and card networks are where mandate handling is most likely to live. Watch your payment provider's roadmap rather than building mandate verification yourself.

How does this compare with ACP?

UCP and OpenAI's ACP solve similar problems for different agent platforms. Both keep you as merchant of record and both have you host checkout logic. ACP's main live surface is ChatGPT merchant integrations; UCP's is Google AI Mode and Gemini. Many merchants will end up on both, which is why a single clean product feed matters. Compare them in ACP vs AP2 vs UCP and read ACP for merchants.

Pros and cons

Pros

  • Backed by Google, Shopify, Walmart, Target and major card networks
  • Uses your existing Merchant Center feed
  • You stay seller of record

Cons

  • Limited to selected merchants and three countries as of November 2026
  • Returns, tracking and loyalty linking are still roadmap items
  • Google Pay with standard card numbers only, per the help page

Bottom line

If you already run Merchant Center, UCP is the shortest path to a Buy button in Google's AI surfaces: add native_commerce, apply, and integrate checkout or let Shopify do it. Leave AP2 to your payment provider for now. For shoppers' expectations on the other side of the button, see Gemini Spark and Google's agentic checkout, and for the broader checklist, making your store agent-ready.