Skip to content

Module experimental 4 min

Agentic Commerce Protocols

UCP, ACP and AP2 give shopping agents a standard way to discover products, build carts and pay; commerce answers become commerce actions.

  1. Agentic Commerce Protocols
  2. 1The protocol stack: UCP / ACP / AP2
  3. 2Who runs which layer
  4. 3Getting a catalog agent-ready
20+ launch partners on Google's UCP at NRF, Jan 2026: Shopify, Walmart, Target and Best Buy among them

Why it mattersWhen an assistant can complete the purchase, being the product it retrieves is the whole funnel.

01

Definition & Foundation

When the assistant can complete the purchase

Agentic commerce protocols give shopping agents a standard way to discover products, build a cart, and pay, turning a commerce answer ("here are three options") into a commerce action ("bought, confirmed, on its way"). The stack got real fast: ACP (OpenAI + Stripe, Sept 2025) standardized agent checkout; Google answered with AP2 for agent payment authorization (Sept 2025, donated to the FIDO Alliance in April 2026) and UCP (the Universal Commerce Protocol) launched at NRF in January 2026 with 20+ partners including Shopify, Walmart, Target, Best Buy, Stripe, Visa and Mastercard, covering discovery, cart, checkout and post-purchase.

The protocols layer rather than compete: MCP for tool discovery, UCP or ACP for the retail flow, AP2 or a card-network token for the payment signature. For most merchants the near-term work is unglamorous and familiar: accurate structured product data, live availability and pricing feeds, and a checkout an agent can drive without dark patterns. When an assistant can complete the purchase, being the product it retrieves is the whole funnel: there is no landing page to convert, no cart to rescue, just whether your catalog was the one the agent could trust and transact. This node carries no impact score (the surface is early), but for a retailer it is the frontier shift most likely to touch revenue first.

02

The Protocol Stack, Untangled

Who runs which layer, and why they coexist

OpenAI + Stripe · Sept 2025

ACP: Agentic Commerce Protocol

Standardizes how an agent completes a checkout: the flow that lets ChatGPT-style assistants turn a product recommendation into a paid order. It defines the retail transaction handshake between the agent and the merchant.

Google · NRF Jan 2026

UCP: Universal Commerce Protocol

A broader spec covering discovery, cart, checkout and post-purchase, launched with 20+ partners (Shopify, Walmart, Target, Best Buy, Stripe, Visa, Mastercard). It aims to be the end-to-end retail rail agents use across merchants.

Google → FIDO · 2025–26

AP2: Agent Payments Protocol

Handles the payment-authorization signature: proving an agent is authorized to pay on a user's behalf. Donated to the FIDO Alliance in April 2026, it's the trust layer beneath the retail flow, not a competitor to it.

the mental model

They layer, not compete

MCP discovers the tool, UCP or ACP runs the retail flow, AP2 or a card-network token signs the payment. A merchant doesn't "pick a winner"; you make your catalog and checkout legible to the stack, and the layers slot together.

03

Myths vs Reality

Common misreadings, corrected

Myth"We need to bet on one protocol and build a custom integration for it now."
RealityThe protocols layer rather than fight, and platforms (Shopify, Stripe, the card networks) are absorbing them into infrastructure you already use. The durable work isn't a bespoke ACP-vs-UCP integration; it's the accurate product data, live feeds, and drivable checkout that every protocol needs underneath. Do that and you're ready for whichever layer your platform adopts.
Myth"Agentic commerce is a payments problem; that's our processor's job."
RealityPayment authorization (AP2 / card tokens) is the processor's layer, but discovery and cart are yours. If your product data is stale, your availability wrong, or your prices only rendered client-side, the agent never reaches the payment step; it transacts with a competitor whose catalog it could trust. The GEO work is upstream of payment.
04

Putting It to Work

Get the catalog agent-ready

You don't implement the protocols directly for most merchants; your platform does. Your job is to make the product data and checkout underneath them accurate, live, and drivable, so an agent can retrieve and transact with confidence.

The agent-ready commerce playbook

1

Get product data clean and structured

Emit complete, accurate Product schema (title, GTIN/SKU, price, currency, availability, shipping, returns) on every product page. This is the discovery layer every protocol reads; gaps and ambiguity here are where agents drop your products from consideration.

2

Keep availability and pricing live

Agents act on real-time state. A price or stock level that's hours stale produces failed or wrong transactions, which train the agent to avoid you. Ensure your feeds and structured data reflect current availability and pricing, not an overnight snapshot.

3

Make the checkout agent-drivable

Audit your purchase flow for anything that assumes a human: forced account creation, interstitials, dark patterns, or a payment step an agent can't complete. The cleaner and more standard the checkout, the more readily an agent, via UCP/ACP, can drive it to completion.

4

Ride your platform's protocol support

Track what Shopify, your payment processor, and the card networks ship for UCP/ACP/AP2, and turn it on deliberately when it lands. Being on a platform that's a launch partner means most of the protocol plumbing arrives as configuration, not a build.

5

Decide it as strategy, not an SEO ticket

Whether and how far to lean into agentic commerce is a business decision; it affects margins, brand control, and channel mix. Bring it to the same table as your access-policy and go-to-market decisions, not just the technical backlog.

05

Verification Checks

How to know it's really done

0/4 verified

You're agent-commerce-ready when your catalog is legible and your checkout is drivable. Click a check to mark it verified:

06

Update Cadence & Dependencies

Keeping it alive

Continuous feeds · quarterly protocol review
Continuously Keep availability and pricing feeds accurate; stale state produces failed agent transactions.
Quarterly Re-audit product schema completeness and re-test the checkout for agent-drivability.
On platform releases When Shopify, your processor, or the card networks ship protocol support, evaluate and enable it deliberately.

Go deeper from Frontier

Always current

These links resolve live: what you get is generated or filtered the moment you click.

Sources