Glossary

What is x402?

Definition

x402 is an open protocol for paying over HTTP. A server answers a request for a paid resource with status 402 Payment Required and the payment details, the client pays and retries the request with proof of payment, and the server returns the resource. Stripe's implementation, for example, settles payments in the USDC stablecoin.

Why it matters

x402 lets software pay for something in the same request-and-response exchange it uses to fetch it. The payment happens inside that exchange rather than on a separate checkout page. That suits AI agents and apps that need to pay small amounts for things like an API call, a data lookup or a single article.

For most online stores selling physical goods, x402 is less central than checkout standards such as UCP or ACP. It matters most if you sell digital access by the request or by the item.

How it works

x402 builds on the HTTP status code 402, Payment Required. Stripe's documentation summarizes the flow: "When a client requests a paid resource, your server returns an HTTP 402 response with payment details, including a Stripe deposit address. The client pays, then retries the request with authorization."

The steps are:

  1. The client asks for a paid resource without paying.
  2. The server answers 402 with its payment requirements.
  3. The client pays and retries with a payment credential.
  4. A facilitator verifies the payment and settles it on-chain, and the server returns the resource.

In Stripe's implementation, x402 payments are in USDC on the Base network, and Stripe records each settled payment as a normal PaymentIntent. Stripe says that to accept card payments alongside stablecoins, you should also integrate its Machine Payments Protocol (MPP).

Coinbase contributed x402 to the x402 Foundation, which the Linux Foundation announced as operational on July 14, 2026, with 40 member organizations. The release calls x402 "the open standard for internet-native payments over HTTP" and describes it as supporting several payment types, from cards to stablecoins. Google also launched an A2A x402 extension alongside AP2 in September 2025.

Example

An agent requests a paid report from your site. Your server replies:

HTTP/1.1 402 Payment Required
payment-required: eyJ4NDAyVmVyc2lvbiI6MiwiZXJyb3IiO...

The header carries the price and where to pay, encoded. The agent pays 0.01 USD in USDC, then repeats the request with its payment credential. Once the payment is verified, your server returns the report. For how x402 compares with card-based agent checkout, see ACP, AP2, UCP and x402 compared.

Also called: x402 protocol, HTTP 402 payments

Sources

  1. Stripe Docs: x402 · checked 17 Nov 2026
  2. Stripe Docs: Machine payments · checked 17 Nov 2026
  3. Linux Foundation: Operational launch of the x402 Foundation · checked 16 Nov 2026
  4. Google Cloud: Announcing Agent Payments Protocol (AP2) · checked 16 Nov 2026

The Sill Signals Team · Updated 17 Nov 2026

See which AI agents visit your site, and decide what they may do.

Scan your site free