| title | FAQ |
|---|
x402 is an open‑source protocol that turns the dormant HTTP 402 Payment Required status code into a fully‑featured, on‑chain payment layer for APIs, websites, and autonomous agents.
Is x402 a CDP Product?
No. While Coinbase Developer Platform provides tooling and are the creators of the standard, it is an open protocol (Apache-2.0 license) and you don't need any Coinbase products to use it. We look forward to further clarifying this distinction and making x402 a credibly neutral payment standard.
Traditional rails require credit‑card networks, user accounts, and multi‑step UI flows.
x402 removes those dependencies, enabling programmatic, HTTP-native payments (perfect for AI agents) while dropping fees to near‑zero and settling in ~1 second.
No. Any web API or content provider—crypto or web2—can integrate x402 if it wants a lower‑cost, friction‑free payment path for small or usage‑based transactions.
Typescript, Python, and Go are reference implementations, but x402 is an open protocol.
Nothing prevents you from implementing the spec in Rust, Java, or other languages. If you're interested in building support for your favorite language, please open an issue and let us know, we'd be happy to help!
Multiple organizations operate production facilitators. The protocol is permissionless—anyone can run a facilitator. See the x402 Ecosystem for available options, including:
- Community‑run facilitators for various networks and assets
- Private facilitators for enterprises that need custom KYT / KYC flows.
Every x402 PaymentPayload is signed by the buyer and settled directly on‑chain.
A facilitator that tampers with the transaction would fail signature checks and would not be able to settle the transaction.
There is no single answer, but common patterns are:
- Flat per‑call (e.g.,
$0.001per request) - Tiered (
/basicvs/proendpoints with different prices) - Up‑to (work in progress): "pay‑up‑to" where the final cost equals usage (tokens, MB, etc.)
Yes. x402 handles the payment execution. You can still meter usage, aggregate calls, or issue prepaid credits in Metronome and only charge when limits are exceeded. Example glue code is coming soon.
| Network | CAIP-2 ID | Asset | Fees* | Status |
|---|---|---|---|---|
| Base | eip155:8453 |
Any ERC-20 token | fee-free | Mainnet |
| Base Sepolia | eip155:84532 |
Any ERC-20 token | fee-free | Testnet |
| Solana | solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp |
Any SPL token or Token-2022 token | fee-free | Mainnet |
| Solana Devnet | solana:EtWTRABZaYq6iMfeYKouRu166VU2xqa1 |
Any SPL token or Token-2022 | fee-free | Testnet |
* Gas paid on chain; many facilitators offer zero facilitator fees (see ecosystem for details).
Support for additional chains and assets is on the roadmap and community‑driven.
Not natively. However, facilitators or third‑party gateways can wrap x402 flows with on‑ and off‑ramps.
No. The recommended pattern is:
- Buyers (clients/agents) sign locally in their runtime (browser, serverless, agent VM). You can use CDP Wallet API to create a programmatic wallet.
- Sellers never hold the buyer's key; they only verify signatures.
The current exact scheme is a push payment—irreversible once executed. Two options:
- Business‑logic refunds: Seller sends a new USDC transfer back to the buyer.
- Escrow schemes: Future spec could add conditional transfers (e.g., HTLCs or hold invoices).
Agents follow the same flow as humans:
- Make a request.
- Parse the
PAYMENT-REQUIREDheader. - Choose a suitable requirement and sign a payload via the x402 client SDKs.
- Retry with the
PAYMENT-SIGNATUREheader.
Yes. Programmatic wallets (e.g., CDP Wallet API, viem, ethers‑v6 HD wallets) let agents sign EIP‑712 payloads without exposing seed phrases. For Solana-based payments, agents can use @solana/kit to sign transactions (see the Solana buyer quickstart for an example).
Tracked in public GitHub issues + community RFCs. Major themes:
- Multi‑asset support
- Additional schemes (
upto,stream) - Discovery layer for service search & reputation
Why is x402 hosted in the Coinbase GitHub?
We acknowledge that the repo is primarily under Coinbase ownership today. This is primarily to leverage our best-in-house security and auditing team to ensure the spec is safe and nobody accidentally creates legally ambiguous payment flows. We intend to eventually transfer ownership of the repo to a steering group or open-source committee.
- Signature is invalid (wrong chain ID or payload fields).
- Payment amount does not exactly match the required
amountin the payment requirements (the exact scheme requires strict equality - no overpayment or underpayment). - Address has insufficient USDC or was flagged by KYT.
Check theerrorfield in the server's JSON response for details.
- Ensure you set
network: "eip155:8453"(Base mainnet) instead of"eip155:84532"(Base Sepolia). - Confirm your wallet has mainnet USDC.
- Gas fees are higher on mainnet; fund the wallet with a small amount of ETH for gas.
• Reach out in the Discord channel
• Open a GitHub Discussion or Issue in the x402 repo