Skip to content

Glossary Agentic Commerce

What is agentic commerce?

Definition

Agentic commerce is a purchase or sale that an AI agent carries out on behalf of a person, following that person's instructions, through open protocols such as the Agentic Commerce Protocol (ACP) or the Agent Payments Protocol (AP2).

On the left, a person with a speech bubble holding a list with orange check marks; in the middle, an AI agent paying at a shop on the right with an orange card; an orange parcel travels back to the person, on a dark blue ground.
On this page 5
  1. What agentic commerce means
  2. How it works
  3. Why it matters
  4. Best practices
  5. Common mistakes
In brief

Agentic commerce is a purchase or sale an AI agent executes for a person, following their instructions, through open protocols such as ACP or AP2.

On the left, a person with a speech bubble holding a list with orange check marks; in the middle, an AI agent paying at a shop on the right with an orange card; an orange parcel travels back to the person, on a dark blue ground.

What agentic commerce means

An AI agent that compares prices or fills out a form is already touching your website. Agentic commerce goes a step further: the agent completes the entire transaction, from finding the product to paying for it, without the person having to open the merchant's site themselves. For the merchant, that means part of its sales can close without anyone ever visiting its product page the usual way, with their own clicks and their own cart.

There's no single standard for this yet. This entry looks at two open protocols, which don't cover quite the same thing. The Agentic Commerce Protocol (ACP) was developed jointly by OpenAI and Stripe and released on September 29, 2025 under the Apache 2.0 license; Meta is now also listed as a lead maintainer. OpenAI launched it with Instant Checkout in ChatGPT, but in March 2026 it said merchants can use their own checkout while it focuses on product discovery, and it extended ACP for that purpose. What is left of shopping in ChatGPT today is covered in our article on ChatGPT Shopping. The Agent Payments Protocol (AP2) was created by Google, which announced it on September 16, 2025 with more than sixty payments and technology companies, including Mastercard, PayPal, and Adobe. On April 28, 2026, Google donated it to the FIDO Alliance, where work on the specification continues. AP2 deals with authorizing and signing the payment: catalog and checkout are out of scope, and it operates within a commerce protocol such as the Universal Commerce Protocol (UCP).

Both protocols address the same underlying problem: how to let an agent pay with a credential limited to that purchase, and how to keep a record that the person authorized it.

How it works

Under ACP, the agent reads the merchant's catalog, in a format built for machines, and builds a cart. Once the person confirms what they want to buy and with which payment method, a single-use token is created through the payment provider, with a maximum amount and an expiry, tied to that checkout session and that merchant. Stripe was the first compatible provider, with its Shared Payment Token, and ACP allows others. The agent sends the token to the merchant, who charges it like any other payment. If the merchant charges through a payment provider, it doesn't receive the card details: in OpenAI's specification, ChatGPT collects them and sends them directly to that provider, preferably as a network token and otherwise as the card number. The exception is PCI DSS Level 1 merchants with their own vault, which can integrate directly and then handle that data themselves. Before that step, the protocol includes a capability negotiation: the merchant declares which payment forms it accepts (Stripe's token, another provider's own token, or the seller's own handler), and the agent picks one of the ones the merchant allows. That leaves the merchant with real control over which methods reach its checkout, even though the whole prior conversation happened inside an AI assistant.

AP2 solves the same problem with a different mechanism: mandates, signed credentials that authorize the agent. The current specification, v0.2 of April 28, 2026, defines two. The Checkout Mandate proves to the merchant that the agent is authorized to complete that purchase. The Payment Mandate proves the same for the payment to the credential provider and the payment processor. Each can be open, with conditions such as an amount range or allowed merchants, or closed, bound to one specific checkout. Verifiers always receive the closed ones; what changes is who signs them. In Direct mode, the person sees the closed checkout and approves it. In Autonomous mode, the person approves the open mandates beforehand, and the agent later signs the closed ones with its own key, within those conditions. According to the AP2 FAQ, the protocol prevents the agent from accessing sensitive card or personal data; the agent still receives a payment credential, which the credential provider scopes.

The two mechanisms differ in form but share the same idea: the agent never decides to spend money on its own without leaving a verifiable trail that a person authorized it, whether through a limited token or signed mandates.

Which of these three paths would you accept in your shop?

Why it matters

For a store that already sells well through Google and social media, this is the first concrete GEO question with a direct revenue effect: if a customer asks their assistant to buy something for them, can your store take part in that purchase, or does it get left out?

There's no public figure comparing how much volume each protocol moves today; any claim about which one is winning would be a guess, not a verified number. What does depend on a concrete decision is catalog readiness: the structured product data an agent needs to find and correctly describe an item is the same, whichever payment protocol gets chosen later. Putting off that preparation until it's clear which protocol wins in two years keeps a store out of agentic commerce during that whole stretch, whoever ends up winning.

There's a second, more operational decision: what happens with a chargeback when an agent triggered the purchase. Under ACP, settlement, refunds, and chargebacks stay with the merchant and its payment provider, according to OpenAI's specification. Under AP2, the mandates and their signed receipts can be brought together as evidence of the transaction if a charge needs investigating; how the dispute is resolved is outside its specification. A merchant that turns on either protocol without first deciding how to handle those disputes is putting off that decision until an angry customer is already on the line.

Best practices

  • Publish a machine-readable product feed before deciding which payment protocol to implement; that work serves both.
  • Don't bet all your development on a single protocol while neither one clearly and verifiably dominates the market.
  • Check whether your current payment processor already supports ACP or AP2 before building your own integration from scratch.
  • Decide whether you accept purchases where the buyer doesn't approve the final cart and, if you do, check that they meet the conditions the buyer authorized.
  • Keep the record of every agentic transaction, whether token or mandate, so you can respond to a chargeback.
  • Keep the same fraud and stock rules you use at human checkout; no protocol replaces them on its own, no matter how reliable the token or mandate looks in a given case.

Common mistakes

  • Treating ACP and AP2 as if they were interchangeable; they cover different parts of the purchase, and neither one's documentation mentions the other.
  • Assuming an agent can complete a purchase with no human approval at any point in the process.
  • Giving the agent card details outside the protocol's flow instead of a credential limited to that purchase.
  • Ignoring agentic commerce on the assumption it doesn't generate volume yet, without checking that against your own store's data.
  • Confusing agentic commerce with a customer-service chatbot that only recommends products without being able to charge for them.
Manuel Riveiro Rodriguez CEO & Digital Strategist

A technical audit covers this and everything else in one pass.

Request an audit

Frequently asked

Is agentic commerce the same as a shopping chatbot?

No. A shopping chatbot recommends or describes products within a conversation, but the person finishes the purchase on the merchant's own site. In agentic commerce, the agent completes the entire transaction, including payment, without the person having to open that site.

Are ACP and AP2 compatible with each other?

No official bridge is on record: AP2's documentation doesn't mention ACP, and ACP's doesn't mention AP2 (checked on November 3, 2026). They also don't cover the same thing. ACP defines the catalog, cart, and checkout between agent and merchant; AP2 authorizes and signs the payment within a commerce protocol such as UCP. A merchant wanting to cover both needs to implement them separately.

Do I need to implement both protocols at once?

There's no public figure showing which of the two moves more volume today, so there's no single answer. What's worth doing without waiting is preparing your product data, because that work is needed for either protocol.

Can an agent pay without me approving anything?

Not without any approval at all, according to both specifications. Under ACP, the token is single-use, has a maximum amount and an expiry, and is tied to a checkout session. Under AP2, you approve the closed checkout or, if you won't be present, you approve open mandates with conditions beforehand. In that second case, the agent signs the specific purchase within those conditions, without you seeing it first.

What should I prepare first in my store?

Structured product data: price, availability, variants, and features in a format an agent can read without ambiguity. Without that, no payment protocol is worth anything, because the agent can't even properly describe what you're selling.

Sources

  1. Stripe Newsroom, joint announcement with OpenAI of the Agentic Commerce Protocol and the Shared Payment Token
  2. Agentic Commerce Protocol, official protocol website
  3. Google Cloud Blog, announcement of the Agent Payments Protocol (AP2), September 16, 2025, v0.1 state
  4. AP2 Protocol, official protocol website
  5. AP2 Protocol, specification v0.2, published April 28, 2026, retrieved November 3, 2026
  6. AP2 Protocol, FAQ, retrieved November 3, 2026
  7. Google, donation of AP2 to the FIDO Alliance, April 28, 2026
  8. OpenAI, Delegated Payment Spec, retrieved November 3, 2026
  9. OpenAI, Powering Product Discovery in ChatGPT, March 24, 2026
  10. Agentic Commerce Protocol, repository maintainers, retrieved November 3, 2026