Ask402

x402 vs ACP: what is the difference?

Short answer

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

x402ACP
Full namex402Agentic Commerce Protocol
Maintained byx402 Foundation (Linux Foundation)OpenAI and Stripe
LicenceApache-2.0Apache-2.0
What is boughtOne request: a search, a file, a model callAn order: products, shipping, tax, fulfilment
ShapeRequest, 402, pay, resultCreate a checkout, update it, complete it, track the order
Uses HTTP 402YesNo
Who is the seller of recordThe API being calledThe merchant, who stays merchant of record
Pays withBlockchain tokens, usually USDCThe buyer's existing payment method, passed as a delegated credential
Needs a merchant integrationNo, any server can answer 402Yes, the merchant implements checkout endpoints
StatusVersion 2Described 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.
  • 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, MPP and L402, see the comparison table.

Sources

Facts checked against these sources on . Protocols change, so the official specification wins if it disagrees with this page. Read this page as Markdown.

Who writes this. Ask402 is published by Havok Holdings LLC, which also runs Agent402, one of the x402 services covered here. Agent402 is labelled wherever it appears. Everything else is described from each project’s own documentation, and nobody pays to be listed.