UCP vs ACP vs x402: which agentic commerce protocol matters for your business?

“Agentic commerce protocol” can refer to several different things. A product discovery feed, a checkout API and an HTTP payment challenge may all help software buy something, but they solve different problems. Picking one because it has the newest acronym can send a team toward the wrong integration.

As of October 2026, three names worth separating are Google's Universal Commerce Protocol (UCP), OpenAI's Agentic Commerce Protocol (ACP), and x402. The comparison below is about their documented roles, not a prediction about which will win.

Protocol	Main job	Where it fits	Merchant question
UCP	A common commerce interface for agentic shopping and buying	Google's AI Mode and Gemini commerce experiences	Are our catalog and checkout systems eligible and prepared for the current Google integration?
ACP	A checkout flow that lets an agent initiate, update and complete a checkout session	OpenAI's commerce integrations	Can our backend expose a reliable checkout session while keeping order and payment state authoritative?
x402	Payment for an HTTP resource or tool call using a 402 response and payment instructions	Paid APIs, data, content or tools	Is the thing we sell a metered digital resource that can be priced per request?

UCP: commerce inside Google's surfaces

Google presents UCP as an open standard for agentic commerce on AI Mode in Search and Gemini, starting with direct buying. Its overview says merchants remain the Merchant of Record and describes integration options for native and, for approved merchants, embedded checkout. It also points merchants to existing Merchant Center product feeds.

For a retailer, that makes product information and checkout compatibility the practical starting point. Confirm that identifiers, variant details, prices, stock and fulfillment information are accurate in the systems Google uses. Then check the current program requirements and merchant access. Google's overview includes a waitlist, so a protocol being documented does not mean every store can turn the feature on immediately. The UCP guide is the source of truth for current availability.

ACP: checkout sessions for an assistant integration

OpenAI's ACP specification describes a structured checkout session rather than a general way to publish every product or charge for arbitrary web requests. The documented lifecycle includes creating a session, updating it as the cart changes, and completing it. The merchant remains responsible for returning authoritative checkout state and handling the resulting order flow.

That is relevant if your business is evaluating a ChatGPT checkout integration. It is not a reason to rebuild the storefront before confirming platform access, payment support, country coverage and operational requirements. Start with the Agentic Checkout specification, then map each operation to the backend that owns inventory, price, tax and order status.

x402: charge for a request

x402 uses HTTP's 402 Payment Required response to tell a client that a resource has a price and to describe acceptable payment options. The client can authorize payment and repeat the request. Cloudflare's current docs describe x402 for paid HTTP content and for charging per MCP tool call.

This can make sense for a paid data endpoint, a specialized API or another digital resource with clear per-request value. It is not a replacement for a retail catalog, a shipping calculator, returns management or a full shopping-cart protocol. A retailer still needs to decide what gets purchased, which options are valid and how the resulting order is fulfilled. See Cloudflare's x402 guide and its MCP tool payment example.

A quick way to choose

Ask what the customer is trying to buy and where the purchase should happen.

• If the goal is to make products discoverable and purchasable in a specific shopping assistant, evaluate that platform's commerce program and its requirements. UCP and ACP fit this category in different ecosystems.
• If the product is an API response, file, data query or tool call sold by usage, evaluate a payment challenge such as x402. Model the unit, price, refund behavior and payment failure path before adding it.
• If your product is a normal website transaction, first fix the source catalog, cart and checkout. A protocol cannot compensate for stale inventory, inconsistent prices or an order endpoint that creates duplicates on retry.

These choices are not necessarily mutually exclusive. A company might sell subscriptions through a web checkout, expose a separate MCP tool for account support, and later join a platform commerce program. Each interface should have its own access rules, data ownership and test plan.

Test your current journey before adding a protocol

Try one realistic customer request from discovery through the point where payment is authorized. Record which facts the agent can see, whether it can keep a selected item through checkout, and when the customer must approve. Use a test environment for purchases. A protocol demo is not evidence that your production inventory, payment or fulfillment path is ready.

Dedica's free agent-readiness scan checks public website signals that can block discovery or use. It does not certify a UCP, ACP or x402 integration, so pair it with the relevant platform's conformance tests and your own end-to-end checkout tests.

For a step-by-step storefront test, see Can an AI agent buy from your store?.

Sources

• Universal Commerce Protocol guide, Google for Developers.
• Agentic Checkout specification, OpenAI Developers.
• x402 payments, Cloudflare Agents docs.
• Charge for MCP tools with x402, Cloudflare Agents docs.