Cowrie Research

universal-commerce-protocol

3 min read

Universal Commerce Protocol (UCP)

  • Name: Universal Commerce Protocol (UCP)
  • URL: https://ucp.dev/
  • Category: agentic commerce protocol / merchant-integration standard / checkout-identity-order interoperability infrastructure
  • Summary: UCP is better cataloged as the merchant-side interoperability layer for agentic commerce rather than as a payment rail, wallet, or shopping app. The official materials position it as a common language for businesses, AI platforms, payment providers, and credential providers to interoperate around discovery, checkout, identity linking, and post-purchase order handling without custom one-off integrations. The decisive clue is that UCP keeps merchants as Merchant of Record while standardizing capability profiles, checkout objects, OAuth-based identity linking, order-event flows, and AP2-compatible payment-authorization hooks. In practice, it looks like an open commerce control plane sitting above merchant systems and alongside AP2, A2A, and MCP rather than a direct settlement network.
  • 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 facilitate the full commerce lifecycle from discovery through post-purchase support
    • The GitHub README says UCP addresses fragmented commerce by giving platforms, businesses, payment service providers, and credential providers a standardized common language and functional primitives
    • The spec overview shows UCP is transport agnostic and built around business profiles, services, capabilities, extensions, and schema composition instead of a single fixed API surface
    • Google’s merchant guide says UCP is an open standard for the future of commerce, meant to turn AI interactions into direct buying on Google AI Mode and Gemini while letting the merchant remain Merchant of Record
    • The official docs explicitly describe UCP as compatible with AP2, A2A, and MCP, which reinforces that it should be understood as an interoperability layer within a broader agentic-commerce stack
    • The UCP-and-AP2 materials frame AP2 as the trust layer for signed checkout and payment mandates while UCP handles the broader merchant integration and 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:

Internal linkages

Graph View

Backlinks