# What is ACP, the Agentic Commerce Protocol?

> ACP is an open standard that lets an AI assistant complete a purchase from a merchant inside a conversation. The assistant and the merchant exchange structured messages to build a checkout, and the buyer's payment details reach the merchant as a secure token. OpenAI and Stripe developed it, and ChatGPT was the first assistant to use it. It does not use HTTP 402.

## The short version

ACP is for shopping. A person asks an assistant for a product, the assistant shows options from merchants, and the person buys without leaving the chat.

Its site defines it as "an open standard for programmatic commerce flows between buyers, AI agents, and businesses". Stripe and OpenAI developed it to give agents and businesses a common language for a transaction.

## How it works

Three parties are involved: the buyer, the AI agent acting for them, and the business selling.

1. The buyer tells the agent what they want.
2. The agent shows products from businesses that support ACP.
3. When the buyer picks one, the agent and the business build a checkout together: items, quantities, delivery, totals.
4. The buyer confirms. Their payment details are passed to the business as a secure payment token.
5. The business charges through its own payment processor and fulfils the order.

The business stays the merchant of record. It keeps its own payment processor, and handles delivery, returns and support as it would for any order.

A business can expose its ACP endpoints as a conventional API or through MCP.

## Key facts

| | |
|---|---|
| Developed by | OpenAI and Stripe |
| Licence | Apache 2.0 |
| First assistant to implement it | ChatGPT |
| First compatible payment processor | Stripe, whose Shared Payment Token is the secure token |
| Status | Described by its maintainers as beta. Versions are dated, the first being 2025-09-29 |
| Uses HTTP 402 | No |

## The payment token

The agent never needs the buyer's card number. Instead, a token that stands in for the buyer's payment details is passed to the business. Stripe's version is called the Shared Payment Token. The protocol is written so that other payment processors can provide their own.

## ACP and x402

They cover different kinds of buying.

| | ACP | x402 |
|---|---|---|
| What is bought | An order: products, delivery, tax | One HTTP response |
| Typical buyer | A person, through an assistant | Software, often with no person involved |
| Typical amount | Ordinary retail prices | Fractions of a cent to a few dollars |
| Needs a merchant integration | Yes | No. Any server can answer 402 |
| Pays with | The buyer's existing payment method | Tokens such as USDC |

A shop with a catalog and deliveries has little use for x402. A weather API has no use for a cart. An agent could well use both: ACP to place the order, and x402 to pay for data it looks up along the way.

The fuller comparison is in [x402 vs ACP](https://www.ask402.ai/x402/x402-vs-acp).

## ACP and AP2

ACP defines the checkout conversation. [AP2](https://www.ask402.ai/x402/what-is-ap2) defines proof that the person authorized the purchase. They address neighbouring problems and come from different organizations.

## Which applies to you

- **You sell products to people:** ACP, or a similar checkout standard.
- **You run an API, a dataset or a tool:** x402. See [how to accept x402 payments](https://www.ask402.ai/x402/how-to-accept-x402-payments).
- **You build agents:** the [comparison table](https://www.ask402.ai/x402/agent-payment-protocols-compared) shows which protocol covers which kind of purchase.

## Sources

- [Agentic Commerce Protocol site](https://www.agenticcommerce.dev/)
- [Agentic Commerce Protocol repository](https://github.com/agentic-commerce-protocol/agentic-commerce-protocol)

---

Facts checked against the sources above on 2026-11-20. Canonical page: https://www.ask402.ai/x402/what-is-acp
