# x402 vs ACP: what is the difference?

> x402 pays for one HTTP request at a time, with no cart and no merchant account. ACP, the Agentic Commerce Protocol maintained by OpenAI and Stripe, is a checkout standard that lets an AI agent build a cart, place an order and pass a payment credential to a merchant. ACP does not use HTTP 402. They cover different kinds of buying.

## Side by side

| | x402 | ACP |
|---|---|---|
| Full name | x402 | Agentic Commerce Protocol |
| Maintained by | x402 Foundation (Linux Foundation) | OpenAI and Stripe |
| Licence | Apache-2.0 | Apache-2.0 |
| What is bought | One request: a search, a file, a model call | An order: products, shipping, tax, fulfilment |
| Shape | Request, 402, pay, result | Create a checkout, update it, complete it, track the order |
| Uses HTTP 402 | Yes | No |
| Who is the seller of record | The API being called | The merchant, who stays merchant of record |
| Pays with | Blockchain tokens, usually USDC | The buyer's existing payment method, passed as a delegated credential |
| Needs a merchant integration | No, any server can answer 402 | Yes, the merchant implements checkout endpoints |
| Status | Version 2 | Described by its maintainers as beta. Versions are dated, first 2025-09-29 |

## Different kinds of buying

**x402 is for machine-sized purchases.** The thing bought is the HTTP response itself. There is no cart, no shipping address, no order to track. The price is usually well under a dollar, and the whole exchange takes one extra round trip.

**ACP is for shopping.** A person asks an assistant to buy something. The assistant and the merchant exchange structured messages about items, quantities, delivery and totals, over REST or MCP. When the person confirms, the assistant passes a payment credential that the merchant charges through its own payment processor. The merchant handles fulfilment, returns and support as usual.

ACP was first implemented by OpenAI, in ChatGPT, and by Stripe, whose Shared Payment Token is the delegated credential.

## Do they compete?

Mostly not. Asking which is better is like asking whether a vending machine or a shop counter is better. A weather API has no use for a cart. A furniture store cannot be reduced to a single paid request.

They could meet in the middle: an agent doing a shopping task through ACP might call paid data APIs through x402 along the way.

## Which applies to me?

- **You run an API, a dataset or a tool:** x402. Add middleware and name a price. See [how to accept x402 payments](https://www.ask402.ai/x402/how-to-accept-x402-payments).
- **You run a shop with physical or digital products:** ACP, or a similar checkout standard.
- **You build agents:** probably both in time, depending on what your agent buys.

For the wider picture, including [AP2](https://www.ask402.ai/x402/x402-vs-ap2), [MPP](https://www.ask402.ai/x402/x402-vs-mpp) and [L402](https://www.ask402.ai/x402/x402-vs-l402), see the [comparison table](https://www.ask402.ai/x402/agent-payment-protocols-compared).

## Sources

- [Agentic Commerce Protocol repository](https://github.com/agentic-commerce-protocol/agentic-commerce-protocol)
- [Agentic Commerce Protocol site](https://www.agenticcommerce.dev/)
- [x402 version 2 specification](https://github.com/x402-foundation/x402/blob/main/specs/x402-specification-v2.md)

---

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