universal-commerce-protocol

Universal Commerce Protocol (UCP)

• Name: Universal Commerce Protocol (UCP)
• URL: https://ucp.dev/
• Category: merchant-integration protocol / agentic-commerce interoperability standard / checkout-and-order-lifecycle control plane
• Summary: UCP is a merchant-side interoperability protocol, not a payment rail and not a storefront product. The useful split is between merchant capability publication, checkout-state exchange, identity linking, and post-purchase order handling. That keeps merchant integration logic separate from the payment-authorization rails sitting underneath it.
• What it does:
  • Defines an open protocol for platforms and businesses to exchange structured commerce capabilities around checkout, identity linking, order management, and related extensions
  • Uses discovery documents and capability negotiation so businesses can publish what UCP features they support and platforms can adapt without bespoke integrations for each merchant
  • Supports multiple transports, including REST, MCP, and A2A, while keeping schemas and specifications separate from any one transport binding
  • Standardizes secure identity linking with OAuth 2.0 and exposes a path for AP2-backed checkout and payment mandates so payment authorization can be cryptographically tied to a specific checkout state
  • Preserves merchant ownership of customer relationships and checkout logic while still letting AI surfaces such as Google AI Mode and Gemini route users into direct-buying flows
• Key claims:
  • The official UCP site calls it “the common language for platforms, agents and businesses” and says it is designed to cover the commerce lifecycle from discovery through post-purchase support
  • The GitHub README says UCP addresses fragmented commerce by giving platforms, businesses, payment providers, and credential providers a standardized common language and functional primitives
  • The spec overview shows that UCP is transport-agnostic and organized around business profiles, services, capabilities, extensions, and schema composition rather than one fixed API surface
  • Google’s merchant guide says UCP is an open standard for direct buying in Google AI Mode and Gemini while merchants remain Merchant of Record, which is the cleanest signal that UCP sits above merchant systems rather than replacing them
  • The official docs explicitly describe UCP as compatible with AP2, A2A, and MCP, reinforcing that it should be read as a merchant-interoperability layer inside a broader agentic-commerce stack
  • The UCP-and-AP2 materials frame AP2 as the signed checkout and payment-mandate layer while UCP handles the broader merchant capability, identity-linking, and order-lifecycle surface
• Whitepaper: No canonical standalone UCP whitepaper or litepaper surfaced in this pass. The clearest current source of truth is the official UCP site and specification, the public GitHub repository, the Google merchant guide, and the official UCP/AP2 integration docs; see ../../whitepapers/universal-commerce-protocol-primary-sources-2026-05-02.md.
• Sources:
  • https://ucp.dev/
  • https://ucp.dev/latest/specification/overview/
  • https://ucp.dev/documentation/ucp-and-ap2/
  • https://raw.githubusercontent.com/Universal-Commerce-Protocol/ucp/main/README.md
  • https://developers.google.com/merchant/ucp

Internal linkages

• Signed agent-checkout and payment-mandate layer sitting nearest to UCP: agent-payments-protocol
• Pre-settlement coordination and policy-exchange contrast: transaction-authorization-protocol
• Account-discovery and grant-negotiation payment rail beneath the commerce layer: open-payments

Control surface

• The leverage sits in who publishes the merchant capability profile, who controls checkout-state transitions, how OAuth identity linking is handled, which extensions become de facto mandatory, and which AI platforms get preferred integration paths.

• That is why the note matters. UCP is the merchant-integration control plane above checkout and order systems, not the settlement layer below them.

• Keep it pointed at AP2, TAP, and Open Payments rather than at a long tail of checkout wrappers.

• Last reviewed: 2026-06-06 UTC