# x402 glossary: what do the terms mean?

> A plain-English list of the words used around x402. The three roles are the client (who pays), the resource server (who sells) and the facilitator (who checks and settles the payment). The three headers are PAYMENT-REQUIRED, PAYMENT-SIGNATURE and PAYMENT-RESPONSE. Everything else describes what is paid, in which token, and on which network.

## Who is involved

| Term | Meaning |
|---|---|
| Client | The software that asks for something and pays for it. Also called the buyer. Often an AI agent |
| Resource server | The service that charges. Also called the seller or merchant |
| Facilitator | A service that checks a payment is valid and submits it to the blockchain, so the seller does not have to. See [what a facilitator is](https://www.ask402.ai/x402/what-is-an-x402-facilitator) |
| x402 Foundation | The body that governs the standard, hosted by the Linux Foundation. See [who runs x402](https://www.ask402.ai/x402/who-runs-x402) |

## The exchange

| Term | Meaning |
|---|---|
| 402 Payment Required | The HTTP status code a server sends when a request needs payment. See [what HTTP 402 is](https://www.ask402.ai/x402/what-is-http-402) |
| `PAYMENT-REQUIRED` | The header the server sends with a 402. It lists the price and the ways to pay |
| `PAYMENT-SIGNATURE` | The header the client sends with its signed payment |
| `PAYMENT-RESPONSE` | The header the server sends back with the result. It is the receipt |
| Offer | One way to pay, as listed in the 402 reply. A reply can hold several |
| Verify | The facilitator's check that a payment is valid, before anything moves |
| Settle | Submitting the payment to the blockchain so the money actually moves |

The field names inside each header are on the [headers and fields](https://www.ask402.ai/x402/x402-headers-and-fields) page.

## What is being paid

| Term | Meaning |
|---|---|
| Scheme | The rule for how a payment is made. `exact` pays a fixed amount. Others are `upto`, `batch-settlement` and `auth-capture`. See [payment schemes](https://www.ask402.ai/x402/x402-payment-schemes) |
| Network | The blockchain the payment is made on, written as a CAIP-2 identifier such as `eip155:8453` for Base |
| Asset | The token being paid, given as its contract address |
| `amount` | The price, as a whole number in the token's smallest unit. For USDC, `10000` is one cent |
| `payTo` | The address that receives the money |
| `maxTimeoutSeconds` | How long the payment authorization stays valid |

## Money words

| Term | Meaning |
|---|---|
| Stablecoin | A token designed to hold the value of a currency, usually the US dollar |
| USDC | The dollar stablecoin that most x402 endpoints charge in |
| Gas | The fee a blockchain charges to process a transaction. In x402 the buyer usually does not pay it. See [fees and gas](https://www.ask402.ai/x402/x402-fees-and-gas) |
| Wallet | Software that holds the key used to sign payments |
| Test network | A copy of a blockchain where tokens have no value, used for trying things out. Base Sepolia and Solana Devnet are the usual ones |

## Technical words

| Term | Meaning |
|---|---|
| EIP-3009 | The token feature that lets a transfer be authorized by signature. It is what makes the standard x402 payment work on EVM networks. See [what EIP-3009 is](https://www.ask402.ai/x402/what-is-eip-3009) |
| Permit2 | A fallback for tokens that lack EIP-3009. It needs a one-time approval |
| EVM | Ethereum Virtual Machine. Shorthand for Ethereum and the many networks that work like it, such as Base |
| CAIP-2 | A naming scheme for blockchains, used for the `network` field in version 2 |
| Nonce | A one-time number inside a payment so it cannot be used twice. See [replay protection](https://www.ask402.ai/x402/x402-replay-protection) |
| MCP | Model Context Protocol, the way AI assistants call tools. See [x402 with MCP](https://www.ask402.ai/x402/x402-with-mcp) |
| Bazaar | The discovery layer where paid endpoints are listed. See [the Bazaar](https://www.ask402.ai/x402/x402-bazaar-discovery) |

## Neighbouring standards

| Term | Meaning |
|---|---|
| MPP | Machine Payments Protocol, from Tempo and Stripe. Also uses status 402. See [what MPP is](https://www.ask402.ai/x402/what-is-mpp) |
| L402 | A Lightning Network payment standard from Lightning Labs. See [what L402 is](https://www.ask402.ai/x402/what-is-l402) |
| AP2 | Agent Payments Protocol, about proving a person authorized a purchase. See [what AP2 is](https://www.ask402.ai/x402/what-is-ap2) |
| ACP | Agentic Commerce Protocol, a checkout standard. See [what ACP is](https://www.ask402.ai/x402/what-is-acp) |

To see these terms in a real reply, paste a paid endpoint into the [402 checker](https://www.ask402.ai/tools/402-checker).

## Sources

- [x402 version 2 specification](https://github.com/x402-foundation/x402/blob/main/specs/x402-specification-v2.md)
- [x402 documentation](https://docs.x402.org/)
- [Schemes overview, x402 documentation](https://docs.x402.org/schemes/overview)
- [Network and token support, x402 documentation](https://docs.x402.org/core-concepts/network-and-token-support)

---

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