The 402 response is the price tag. Everything a client needs to pay is in it, and anything missing is a reason a client will give up.
scheme: how payment works, usually exact (pay exactly this amount).network: the chain, for example eip155:8453 for Base.asset: the token contract, for USDC on Base 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913.amount: in the token's smallest unit. USDC has 6 decimals, so 10000 is $0.01.payTo: the address that receives the money.maxTimeoutSeconds: how long the seller will wait.extra: scheme details, such as the token's EIP-712 name and version, and the facilitator URL.Use the root facilitator field and accepts[].extra.facilitator. Leave it out of accepts[].facilitator: that is not a v2 PaymentRequirements field, and because clients echo the accepted requirements back with the payment, a strict client can fail to match it.
{
"x402Version": 2,
"accepts": [{
"scheme": "exact",
"network": "eip155:8453",
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"amount": "10000",
"payTo": "0x...",
"maxTimeoutSeconds": 60,
"extra": {"name": "USD Coin", "version": "2",
"facilitator": "https://x402-agent-pay.com/facilitator"}
}],
"facilitator": "https://x402-agent-pay.com/facilitator"
}Check any endpoint's 402 with our free endpoint report.
USDC uses 6 decimals, so 10000 base units is 0.01 USDC.
In x402 v2 the PAYMENT-REQUIRED header is the authoritative copy. A body is optional and should carry the same terms.
Common reasons are a v1-only response, an unsupported network or asset, a missing payTo, or a facilitator named in a field the client does not expect.