← Articles

ACP vs. UCP vs. Visa Intelligent Commerce: Agentic Commerce Protocols Explained

Published July 29, 2026Updated July 29, 2026Protocols

Key takeaways

  • ACP, the Agentic Commerce Protocol from OpenAI and Stripe, and UCP, the Universal Commerce Protocol introduced by Google with partners including Shopify, are merchant-side commerce protocols: they define how an agent reads a catalog and places an order.
  • Visa Intelligent Commerce and Mastercard Agent Pay sit a layer lower, at the card networks. They define agent-initiated payment credentials, not how a merchant exposes products.
  • AP2, the Agent Payments Protocol that Google created and donated to the FIDO Alliance, addresses authorization: how an agent carries a signed record of what the user approved.
  • Web Bot Auth and Visa's Trusted Agent Protocol are identity layers: they let an agent prove which agent it is when it makes a request.
  • The specifications overlap less than the names suggest. The largest shared gap is that none of them makes a merchant that has adopted nothing purchasable by an agent.

ACP, UCP, and Visa Intelligent Commerce are not competing versions of the same thing. ACP and UCP are merchant-side commerce protocols that define how an agent finds products and places an order. Visa Intelligent Commerce is a card network framework for agent-initiated payment credentials. Web Bot Auth is an identity layer that lets a merchant verify which agent sent a request.

Why are there several agentic commerce protocols at once?

There are several agentic commerce protocols because agent purchases fail at several different layers, and different organizations own each layer. When you look at the stack, the apparent competition is mostly a division of labor.

  • Merchants had no agent-readable interface: Storefronts were built for people with browsers, and checkout flows assume human data entry. ACP and UCP define a structured way for software to browse and order.
  • Networks could not mark agent-initiated payments: Card messages assumed a human at the point of purchase. Visa Intelligent Commerce and Mastercard Agent Pay let an agent-initiated transaction be presented as one.
  • Nobody could tell which agent was calling: Merchants and CDNs saw anonymous automated requests and blocked them. Web Bot Auth gives an agent a cryptographic identity, which the other layers depend on.
  • User authorization had no standard record: An agent needs to show what the user approved. AP2 defines signed mandates for that purpose.
  • The ecosystems differ: Protocols written inside the OpenAI ecosystem and inside the Google ecosystem reflect different distribution channels, which is one reason two merchant-side specifications exist.

What is the Agentic Commerce Protocol (ACP)?

The Agentic Commerce Protocol is an open merchant-side specification developed by OpenAI and Stripe. It defines how an agent retrieves a merchant's product information and completes a checkout through structured endpoints, instead of by operating a human interface.

  • Who runs it: OpenAI and Stripe. Its main distribution surface is ChatGPT. OpenAI removed the first version of in-chat Instant Checkout in March 2026, and merchants can now use their own checkout flows.
  • What it covers: Agent-driven merchant checkout: product data, cart and order construction, and completion of a purchase through a defined interface.
  • Strongest where: Merchants that want to reach shoppers in ChatGPT and that accept the payment relationships that come with the specification.
  • Limitation: ACP covers merchants that adopt it. A builder of a separate consumer agent must still handle user consent, payment credentials, and merchants outside ACP.

What is the Universal Commerce Protocol (UCP)?

The Universal Commerce Protocol is an open merchant-side specification introduced by Google and developed with commerce partners including Shopify. Like ACP, it makes catalog and checkout operations available to agents through structured interfaces.

  • Who runs it: Google, with commerce platform partners. This combines search and assistant surfaces with platforms that host many merchants.
  • What it covers: Agent-accessible catalog and checkout operations. Adoption at the platform level can enable many merchants at once.
  • Strongest where: Merchants on a platform that supports it, and agent experiences close to Google's surfaces.
  • Limitation: Adoption depends on the merchant and its platform, and a second merchant-side protocol gives agent builders two specifications to track.

What is Visa Intelligent Commerce (VIC)?

Visa Intelligent Commerce is a Visa framework for payments that AI agents initiate, not a merchant API. It addresses how a payment credential works when an agent acts for a person, which is a different question from how the agent found the product.

  • Who runs it: Visa, as the card network. Participation runs through Visa's programs for issuers, acquirers, and technology partners.
  • What it covers: Agent-specific payment credentials: how an agent-initiated transaction is presented to the network, how tokens are requested, and how the relationship between the agent and the cardholder is expressed.
  • Why it complements ACP and UCP: A merchant-side protocol still needs a payment to clear. Network-level agent credentials let the issuer authorize that payment with more information than an anonymous card-not-present charge carries.

Visa's Trusted Agent Protocol, developed with Cloudflare, is a companion to Visa Intelligent Commerce. The credential framework says how an agent pays, and the Trusted Agent Protocol helps a merchant recognize which agent is making the request.

What are Mastercard Agent Pay and AP2?

Mastercard Agent Pay is Mastercard's program for agent-initiated payments, and AP2 is an open protocol for carrying a user's payment authorization. Google created AP2 and donated it to the FIDO Alliance in April 2026. They address the network layer and the authorization layer.

  • Mastercard Agent Pay: Mastercard issues agentic tokens, which are network tokens bound to a registered agent, so a merchant and an issuer can recognize an agent-initiated transaction. Its role is similar to that of Visa Intelligent Commerce.
  • AP2 (Agent Payments Protocol): AP2 describes signed records called mandates. A checkout mandate records approval of specific items and purchase details, and a payment mandate authorizes a payment with a specific payment instrument. The first version supports card payments.

Where does Web Bot Auth fit?

Web Bot Auth is the identity layer beneath the commerce protocols. Cloudflare proposed it, and it is developed through IETF drafts. An agent signs each HTTP request with HTTP Message Signatures (RFC 9421) and publishes its public keys in a directory, so a merchant or CDN can verify the signature.

It matters because the default outcome for an anonymous agent is a block. Bot detection services cannot tell a legitimate agent that acts for a real customer from abusive automation unless the agent can prove its identity.

How do ACP, UCP, VIC, and Web Bot Auth compare?

ACP and UCP answer the same question at the merchant layer, while Visa Intelligent Commerce and Web Bot Auth answer different questions at the network and identity layers.

ACPUCPVisa Intelligent CommerceWeb Bot Auth
LayerMerchant commerce APIMerchant commerce APICard network credentialRequest identity
Who runs itOpenAI and StripeGoogle, with partners including ShopifyVisaIETF drafts, proposed by Cloudflare
Core question answeredHow does an agent order from this merchant?How does an agent order from this merchant?How is an agent-initiated payment represented?Which agent is making this request?
What a merchant doesExpose an ACP-compatible interfaceAdopt it, often through its commerce platformAccept agent credentials through its payment processingVerify signatures, usually at the CDN
What an agent builder getsStructured checkout at adopting merchantsStructured checkout at adopting merchantsPayment credentials the network recognizesAn identity that avoids the default block
CoverageAdopting merchants onlyAdopting merchants and platforms onlyDepends on issuer and processing pathStrongest where CDNs verify signatures

Where do the protocols overlap, and where are the real gaps?

ACP and UCP overlap, because both are merchant-side commerce interfaces, while Visa Intelligent Commerce, Mastercard Agent Pay, AP2, and Web Bot Auth answer different questions. The gaps are in the places no specification covers.

  • Merchants that adopted nothing: This is the largest gap. If a merchant supports no agentic protocol, specification support does not help an agent buy from it.
  • Consent inside the builder's app: The merchant-side protocols do not define how a person approves a specific basket in an agent product's own interface, with a record that remains available for a dispute. AP2 describes the record, and the product must still provide the approval experience.
  • The payments burden: A protocol does not give an agent builder tokenized card storage, network program access, or PCI DSS compliance. Those are still required to move money.
  • Translation across specifications: A builder that wants broad coverage must support several specifications with different shapes, plus a path for merchants outside all of them.

What do these protocols mean for a merchant?

For a merchant, these protocols are a distribution decision: an agent-readable interface makes the store purchasable inside assistants, and the choice usually follows the merchant's commerce platform.

  1. 1

    Start with your platform: If your commerce platform supports a protocol, adoption is mostly configuration, which is the cheapest path.

  2. 2

    Set your bot policy deliberately: Blanket blocks on automated traffic also block legitimate agents that buy for real customers. Verifiable agent identity makes a selective policy possible.

  3. 3

    Understand the payment relationship: Protocols differ in who is the merchant of record and which payment rails they use. This is a commercial decision as well as a technical one.

  4. 4

    Expect to support more than one: No single merchant-side protocol has emerged as the standard, so plan for coverage across the surfaces that send you demand.

What do these protocols mean for an agent builder?

For an agent builder, protocol support alone is not enough, because users name merchants, not protocols. A merchant serves only the agents that come to it, but a builder must buy from whichever merchant the user names.

  • Users ask for specific merchants: A user who wants dinner from a specific restaurant does not know which specification it uses. An agent that can buy only at adopting merchants fails many requests.
  • A wallet and consent are separate infrastructure: Reading a catalog is not paying. Approvals, tokenized cards, and an authorization record are what users and issuers rely on.
  • Identity comes first: Verifiable agent identity decides whether a merchant serves the request at all, before any commerce protocol applies.
  • Integrations multiply: Support for several specifications plus a fallback, for each merchant category, can turn a small agent team into a payments and integrations team.

Protocols make some merchants readable to agents. They do not, on their own, make every purchase possible.

How should a builder choose?

A builder should choose by starting from the merchants its users name, then covering each layer separately: ordering, payment credentials, agent identity, and user consent.

  1. 1

    Start from your users' merchants: List the merchants your users will name, and check how many support an agentic protocol.

  2. 2

    Separate the layers before you evaluate: Catalog and ordering, payment credentials, agent identity, and user consent are four different problems. A specification that solves one does not replace the others.

  3. 3

    Prefer translation to a single bet: A commitment to one merchant-side protocol ties your coverage to its adoption. Support across protocols reduces that risk.

  4. 4

    Require a consent record: Bind a specific human approval to a specific purchase, and use network programs so disputes go through the user's bank as normal.

ACP and UCP make merchants readable to agents. Visa Intelligent Commerce and Mastercard Agent Pay make agent payments visible to the networks. AP2 records what the user authorized, and Web Bot Auth lets an agent prove its identity. The gap that none of them closes is the merchant that has adopted nothing.

Frequently asked questions

What is the difference between ACP and UCP?

ACP and UCP are both open merchant-side protocols that define how an agent reads a catalog and places an order. ACP, the Agentic Commerce Protocol, was developed by OpenAI and Stripe. UCP, the Universal Commerce Protocol, was introduced by Google with commerce partners including Shopify. Each works at the merchants that adopt it.

Is Visa Intelligent Commerce a competitor to ACP or UCP?

No. Visa Intelligent Commerce works at the card network layer and defines how agent-initiated payment credentials work. ACP and UCP define how a merchant exposes products and accepts an agent-driven order. They are complementary layers.

How is AP2 different from ACP and UCP?

AP2, the Agent Payments Protocol that Google created and donated to the FIDO Alliance, addresses payment authorization, not merchant checkout. It defines signed mandates that record what a user authorized an agent to buy. ACP and UCP define how an agent reads products and completes checkout at a merchant.

Do I need to support every agentic commerce protocol to build an agent that buys things?

No single protocol covers every merchant, so broad coverage needs support for several protocols or infrastructure that translates across them. A builder also needs payment credentials, agent identity, and a user consent record, which the merchant-side protocols do not provide.

What happens if a merchant supports no agentic commerce protocol?

If a merchant supports no agentic commerce protocol, protocol support cannot help an agent buy from it. The agent needs another path, such as completing the merchant's existing checkout with a verified agent identity and a tokenized card, within terms the user approved.

Where does Web Bot Auth fit relative to ACP, UCP, and VIC?

Web Bot Auth sits beneath all of them as the identity layer. It uses HTTP Message Signatures (RFC 9421) and a published key directory so an agent can prove which agent it is on each request. Without a verifiable identity, anonymous agents are often blocked before any commerce protocol applies.

Related articles