Universal Cart is Google’s cross-surface shopping cart, announced on 19 May 2026. The Universal Commerce Protocol (UCP) is the open standard a merchant integrates with to appear inside it. The Agent Payments Protocol (AP2), published on 16 September 2025 and maintained in a public GitHub repository, sits inside UCP as an optional specialised layer for autonomous agent payments — Google’s UCP FAQ describes AP2 as “a specialized payment layer within UCP”, not a requirement for UCP-powered checkout. Google is clear on one other point that is easily misread: the retailer remains the Merchant of Record and keeps full control of customer relationships and data. This piece is a definitional read for the ecommerce marketing lead, revenue leader and GM asking what actually changes for their merchant work, and where their next actions should sit.

Short answer

Universal Cart is a Google-hosted shopping cart that persists across Search, the Gemini app, YouTube and Gmail. UCP is the open protocol a merchant integrates with to appear inside it; AP2 is an optional payment layer within UCP for autonomous agent scenarios and is not required for UCP-powered checkout today. Under UCP the merchant remains the Merchant of Record and retains full ownership of customer relationships and data, per Google’s own FAQ. The three near-term merchant actions are to keep the Merchant Center feed correct against the 14 April 2026 product data specification update, to read the UCP developer guide before scoping an integration, and to decide between the Native and Embedded checkout paths using the criteria in the guide.

The three pieces and how Google defines them

Universal Cart — the consumer product

Google describes Universal Cart as “an intelligent shopping cart and your new hub for shopping on Google”. It works across Search, the Gemini app, YouTube and Gmail. Launch partners named in the announcement include Nike, Sephora, Target, Ulta Beauty, Walmart and Wayfair, plus Shopify merchants such as Fenty and Steve Madden. Roll-out is US-first this summer on Search and the Gemini app, with YouTube and Gmail following. UCP-powered checkout is expanding to Canada and Australia in the coming months and later to the UK.

UCP — the open protocol a merchant integrates with

The UCP developer guide describes UCP as “a new open standard that unifies digital commerce” enabling “direct, instant purchases across AI surfaces like AI Mode in Google Search and the Gemini app”. It is interoperable with AP2, with Google’s Agent2Agent (A2A) protocol, and with the Model Context Protocol (MCP). It exposes a REST API transport and an MCP binding. UCP is co-developed with Shopify, Etsy, Wayfair, Target and Walmart. Merchant integration presumes an existing Merchant Center account and the UCP-powered checkout feature.

AP2 — an optional payment layer for agent scenarios

The UCP FAQ states that “AP2 can be used as a specialized payment layer within UCP” and that it is “particularly useful for future scenarios involving autonomous AI agent transactions”. The Google Cloud Blog AP2 announcement (16 September 2025) frames AP2 as “an open, shared protocol that provides a common language for secure, compliant transactions between agents and merchants” and its specification lives in a public GitHub repository (google-agentic-commerce/AP2, latest release v0.2.0 dated 28 April 2026, with sample implementations that still cite a Gemini Preview model). AP2 uses three Mandate types — Intent, Cart and Payment — each expressed as a W3C Verifiable Credential.

The two facts that follow directly from those documents: AP2 is not required for UCP-powered checkout today, and the AP2 specification is still under active version development. A merchant scoping a UCP integration therefore does not need to design an AP2 flow to begin. This is one plausible reading of the UCP FAQ and the AP2 versioning cadence; treat it as editorial guidance rather than a Google commitment.

Merchant of Record — the correction that changes the merchant conversation

Google’s UCP FAQ states, in the FAQ’s own words, “You remain the Merchant of Record, maintaining full control over your customer relationships and data.” The Merchant Center help page for the UCP-powered checkout feature repeats the position: the retailer remains the seller of record and may customise the integration to preserve specific checkout requirements. The implication is that a UCP transaction is not a marketplace transaction with respect to customer ownership. This is not a matter of interpretation on Google’s side; the FAQ addresses it directly.

This distinction matters because a merchant lead planning UCP work needs to know which of their existing operational functions still sit with them. Tax collection, fraud detection and post-purchase experience remain the merchant’s under UCP. The reader who arrives with the assumption that UCP behaves like a marketplace — that the customer relationship transfers to Google — should treat that assumption as incorrect and repositioned by the FAQ.

Native versus Embedded checkout — the two integration paths

The UCP FAQ and the Native checkout developer guide describe two integration paths.

  • Native. “You provide a deeper API integration, allowing us to handle the checkout logic directly within the AI surface.” The Native guide requires the merchant to expose a RESTful API with five endpoints — Create, Retrieve, Update, Complete and Cancel checkout-session — and to accept Google Pay tokenization data at the payment step. BigQuery for UCP events is listed as an optional analytics store.
  • Embedded. “We route the user to a checkout UX that you control, embedded within our surface.” This path is available when Native does not support specific checkout elements the merchant needs to preserve.

The Native guide explicitly documents Google Pay as the payment handler and requires the merchant’s Payment Service Provider (PSP) to process Google Pay tokens; “most major global PSPs support Google Pay” per the UCP FAQ. The Native guide does not name additional third-party handlers, and the Merchant Center help page for the feature currently references Funding Primary Account Numbers stored on Google Wallet as the payment source.

Reporting — what the docs say and what they do not

The Native checkout developer guide lists “BigQuery for UCP events (optional)” as an analytics store the merchant can wire up. Neither the UCP FAQ, the UCP-powered checkout Merchant Center help page nor the Native checkout guide document a specific Merchant Center report dedicated to UCP transactions today. The implication for a merchant lead is that the measurement design for UCP transactions is not yet a plug-and-play Merchant Center dashboard; it is an event pipeline the merchant chooses to build. This is editorial inference from the state of the guides, not a Google commitment.

The classic assumption that a completed transaction generates a session on the merchant’s own website is worth re-examining in this light. When the payment step happens inside a Google surface via Google Pay tokenization, a merchant should not assume a classic web-analytics session will be there to attribute against. A UCP-aware measurement design can plausibly join UCP event data (BigQuery when configured) with existing web analytics rather than expect an automatic hand-off. This is a reasonable reading of the Native architecture; the guides do not spell out an end-to-end attribution recipe.

Where UCP actually surfaces the checkout

The UCP FAQ names “AI Mode in Google Search and the Gemini app” as the AI surfaces where UCP enables direct, instant purchases. The Universal Cart announcement blog additionally names YouTube and Gmail as surfaces where the cart persists. The two sources are consistent, but a merchant lead should not read them as saying that every classic Google Search result now includes a checkout. AI Mode is a specific Search experience; the classic ten-blue-link result page is not the same surface. This is worth internalising before writing an internal brief that overstates where the cart appears today.

Comparing UCP to paths a merchant already knows

The comparison below is only useful once the Merchant of Record correction is in place. A UCP transaction is not the same as a marketplace transaction, precisely because customer ownership stays with the merchant.

PathWhere the transaction completesMerchant of RecordCustomer data ownership
Classic organic Search → merchant site → merchant checkoutMerchant’s own siteMerchantMerchant
Shopping ad → merchant site → merchant checkoutMerchant’s own siteMerchantMerchant
Marketplace listing (Amazon, Walmart marketplace)MarketplaceMarketplaceMarketplace
UCP-powered checkout (Native or Embedded) on AI Mode / Gemini appGoogle surfaceMerchant (per UCP FAQ)Merchant (per UCP FAQ)

Academic research — what a merchant should know about the security posture

Peer-reviewed literature specifically on UCP or Universal Cart is not yet available as of the verification date; the searches recorded in the audit for this article did not identify a peer-reviewed venue publication. Preprint literature on the AP2 security posture does exist and is worth naming. Debi, Zhu and Sen Gupta’s “Whispers of Wealth: Red-Teaming Google’s Agent Payments Protocol via Prompt Injection”, submitted 30 January 2026 (revised 18 May 2026), applied an AI red-teaming methodology to an AP2-based shopping agent built with Gemini 2.5 Flash and the Google ADK framework. Two attack techniques — the Branded Whisper Attack and the Vault Whisper Attack — reportedly manipulated product ranking and extracted sensitive user data. The paper’s contribution is to demonstrate that simple adversarial prompts can subvert agent behaviour in AP2-mediated purchase flows.

The scope boundary is important. The Whispers of Wealth study evaluates an AP2-based agent, not the full Universal Cart product surface or the wider UCP integration flow. The findings are therefore most directly informative about future AP2-mediated agent scenarios, which the UCP FAQ describes as the current use case for AP2. A merchant scoping AP2 work should read the paper before designing the flow; a merchant scoping UCP-only (non-AP2) checkout has a different threat model that this specific study does not cover directly.

What a merchant can actually do now

Three actions carry the current period, and all three are independent of a final integration decision.

  • Confirm the Merchant Center product data specification is met by the current feed and that the 14 April 2026 update is reflected — the new video link attribute begins serving and quality validation on 30 June 2026.
  • Read the UCP developer guide end-to-end, plus the Native checkout guide, before deciding between Native and Embedded — the decision is a scope decision, not a positioning decision.
  • Read the AP2 GitHub repository once, note the version cadence and the preview-model note in the samples, and put an AP2 review on the calendar rather than in the current sprint.

What Universal Cart, UCP and AP2 are not

Four misreadings are easy to acquire from summary coverage and are worth naming.

  • Not a replacement for classic Search. Merchants not integrated with UCP continue to appear in classic Search results as before. UCP adds a checkout surface; it does not remove existing ones.
  • Not automatic. Merchant Center enrolment does not enrol a property in UCP. The integration is explicit and requires the developer work described in the UCP guide.
  • Not a marketplace on customer ownership. The UCP FAQ is explicit that the merchant remains the Merchant of Record and retains customer data and relationships.
  • Not an AP2-mandatory flow. AP2 is described by Google as a specialised payment layer within UCP, particularly for autonomous agent scenarios. UCP-powered checkout does not require the merchant to design an AP2 flow to begin.

Sources and evidence

Primary Google sources used:

Academic preprint referenced:

  • Debi, T., Zhu, W. and Sen Gupta, P. (2026). Whispers of Wealth: Red-Teaming Google’s Agent Payments Protocol via Prompt Injection. arXiv preprint 2601.22569 (submitted 30 January 2026, revised 18 May 2026). arxiv.org/abs/2601.22569.

FAQ

Does UCP make the merchant lose the customer relationship?

No. The UCP FAQ states directly: “You remain the Merchant of Record, maintaining full control over your customer relationships and data.” A UCP transaction is not a marketplace transaction on the question of customer ownership.

Is AP2 required for UCP-powered checkout today?

No. The UCP FAQ describes AP2 as “a specialized payment layer within UCP” that is “particularly useful for future scenarios involving autonomous AI agent transactions”. UCP-powered checkout uses Google Pay tokenization and the merchant’s PSP; AP2 sits alongside as an optional layer.

What is the difference between Native and Embedded checkout?

Native means the merchant exposes a REST API (five endpoints) and Google handles the checkout logic within the AI surface. Embedded routes the shopper to a merchant-controlled checkout UX embedded inside the Google surface. The Native checkout guide is the developer reference for the API contract.

How are UCP transactions reported?

The Native checkout guide lists BigQuery for UCP events as an optional analytics store. Neither the UCP FAQ nor the Merchant Center help page documents a dedicated Merchant Center report for UCP transactions today. A merchant designing measurement should treat UCP event data as a pipeline to build rather than an automatic dashboard.

Which Google surfaces run UCP-powered checkout?

The UCP FAQ names “AI Mode in Google Search and the Gemini app” as the AI surfaces enabling direct instant purchases. The Universal Cart announcement adds YouTube and Gmail as surfaces where the cart itself persists. The classic ten-blue-link Search result page is not the same surface as AI Mode.

Is there any academic research on AP2 security?

As of the verification date, peer-reviewed literature specifically on UCP or Universal Cart is not yet available in the searches recorded for this article. On AP2 specifically, Debi, Zhu and Sen Gupta’s arXiv preprint “Whispers of Wealth” red-teams an AP2-based shopping agent and reports two prompt-injection attacks (Branded Whisper, Vault Whisper). A merchant scoping AP2 work should read the paper before designing the agent flow.

Anchor the merchant work in the Merchant Center feed and the UCP integration decision, and put AP2 on the calendar rather than in the sprint

Universal Cart, UCP and AP2 sit at three different maturity levels — a consumer product rolling out, an open integration protocol with a documented developer guide, and a specialised payment layer whose specification is still under active version development. Google’s own FAQ is explicit that the merchant retains Merchant of Record status and customer ownership under UCP, and that AP2 is optional for UCP-powered checkout today. The immediate merchant actions are to keep the Merchant Center feed correct against the 14 April 2026 specification update, to read the UCP developer guide and pick between Native and Embedded on scope grounds, and to note the Whispers of Wealth findings when scoping any future AP2 work. Any framing that presents UCP as a marketplace, AP2 as a requirement, or Universal Cart as a shift that removes the merchant’s classic session by default is running ahead of what the Google documentation says. Start from the documents; treat the rest as editorial reading.

If your team is scoping a Universal Cart integration or trying to distinguish what UCP requires from what AP2 might require later, a focused editorial and merchant-data review can produce a specification-aware readiness map — Merchant Center feed correctness, Native versus Embedded selection, and a review of the AP2 posture using the Whispers of Wealth findings.

Request a UCP integration readiness map

For merchants not yet integrating UCP, the same discipline applies inward: an audit of the Merchant Center feed against the 14 April 2026 specification update, so that the feed is not the bottleneck when the integration decision arrives.

Have your Merchant Center feed audited against the 2026 specification update