x402 Multiple Tokens and Networks Explained
x402 is usually introduced with USDC on Base, but that example isn't the limit of the protocol. Version 2 uses chain-agnostic network identifiers, separate asset identifiers and payment schemes that each facilitator advertises. The useful skill is reading four things in a server's payment terms, so you can tell what an SDK could do in theory from the exact token and network a facilitator will actually settle.
FaucetPay serves a different small-payment use case for human faucet rewards; create a FaucetPay account only when a reward source documents that separate route.
Set up FaucetPay to collect small rewards →The direct answer
x402 is not restricted to one token or one blockchain. Version 2 identifies networks using CAIP-2, separates payment schemes from assets and lets each facilitator publish the combinations it can verify and settle. The official EVM SDK supports EIP-3009 tokens and generic ERC-20 tokens through Permit2, while the Solana SDK supports SPL Token and Token-2022 assets. A seller must still advertise an exact asset, network and payment scheme accepted for one resource.
Four things define one payable route
One payable resource is defined by four independent values. If any one doesn't match what your wallet and facilitator can do, there's no route.
- Network: the CAIP-2 chain identifier.
- Asset: the token contract or mint.
- Scheme: exact, upto or another supported payment mechanism.
- Facilitator: the service able to verify and settle that combination.
HTTP 402 is the status code, not the asset list
The server returns payment requirements with the resource response. x402 defines the headers, authorization and settlement flow around HTTP 402; the protocol does not make every token acceptable to every server.
CAIP-2 gives networks unambiguous identifiers
x402 v2 uses values such as eip155:8453 for Base mainnet, eip155:137 for Polygon and a Solana namespace with the cluster genesis hash. This avoids vague labels such as mainnet or USDC network.
The asset is identified separately from the network
The same ticker can exist through different contracts or mints. A seller should specify the exact asset accepted on the declared network.
EIP-3009 enables off-chain transfer authorization
Tokens such as USDC and EURC can support signed transfer authorizations that a facilitator submits. The buyer does not need a separate token-approval transaction for this path.
Permit2 expands EVM token support
Coinbase's x402 documentation says the reference EVM implementation can use Permit2 for generic ERC-20 tokens on EVM-compatible chains. The buyer authorizes a PermitWitnessTransferFrom message and the facilitator executes the transfer.
Permit2 can require an existing approval
Without a gas-sponsorship extension, the payment token must first approve the Permit2 contract on-chain. The first payment can therefore have a setup step that later payments do not.
Gas sponsorship changes who submits the setup transaction
The official documentation describes EIP-2612 and generic ERC-20 gas-sponsoring extensions that let a facilitator handle the Permit2 approval using signed authorization. Support depends on the token, facilitator and implementation.
Solana uses a separate SDK family
The x402 SVM package supports SPL Token Program and Token-2022 assets on compatible Solana clusters. Solana mints and cluster identifiers must be treated separately from EVM contracts.
Reference SDK support is not facilitator support
A protocol library can support a broad class of chains while one hosted facilitator enables only a smaller set. The facilitator’s supported endpoint is the source of truth for a live deployment.
Coinbase's hosted facilitator in October 2026
On October 31, 2026, Coinbase's x402 documentation listed hosted support for Base, Polygon, Arbitrum, Monad, World and Solana, with Base Sepolia, World Sepolia and Solana Devnet for testing. EVM networks offered the exact, upto and batch-settlement schemes; Solana offered exact and upto. Pricing was 1,000 free on-chain transactions a month, then $0.001 each, with verification free. The list grows, so query the facilitator rather than hard-coding it.
The supported endpoint makes capability discoverable
The CDP x402 API provides a supported-kinds endpoint returning protocol version, scheme, network, extensions and signer information. Clients can inspect capability before attempting payment.
One service can offer several payment choices
A server can advertise multiple acceptable requirements for one resource. The client can choose a supported token-network route according to wallet balances and policy.
Multiple choices create routing risk
An agent must not choose only the lowest nominal token amount. It should compare token decimals, contract identity, network, approval state, gas policy and spending limits.
Stablecoin ticker equivalence is not route equivalence
USDC on Base and USDC on Solana can target the same dollar-denominated price while using different wallets, identifiers, settlement paths and failure modes.
Describe each accepted payment precisely
Describe each accepted payment precisely.
- x402 version
- Scheme
- CAIP-2 network
- Token contract or mint
- Decimals
- Facilitator
- Approval or EIP-3009 path
- Gas sponsorship
- Maximum payment
- Settlement evidence
Worked example: USDC on Base
A server requests an exact USDC payment on eip155:8453. The token supports EIP-3009, and the selected facilitator can settle the route. The buyer signs the bounded authorization for that resource.
Worked example: generic ERC-20 on Polygon
The seller accepts a specific ERC-20 contract on eip155:137 through Permit2. The client checks whether the token already approved Permit2 or whether gas sponsorship is available before attempting the first payment.
Worked example: unsupported combination
A client owns the correct stablecoin on Ethereum, while the server and facilitator advertise only Base and Solana. The ticker matches but the payment coordinate does not, so no valid route exists without another transaction.
Limitations
Networks, schemes and facilitator pricing change, sometimes within weeks. The examples show how to read payment terms, not a guarantee that any route works today. The facilitator's supported endpoint and the wallet's signing prompt are what to trust.
Sources
Protocol and Coinbase documentation. The Coinbase network-support page and x402.org were re-checked on October 31, 2026; the rest on July 27, 2026.
- x402 network and token support: https://docs.x402.org/core-concepts/network-and-token-support
- Coinbase x402 network support: https://docs.cdp.coinbase.com/x402/network-support
- Coinbase x402 overview: https://docs.cdp.coinbase.com/x402/welcome
- CDP supported payment schemes endpoint: https://docs.cdp.coinbase.com/api-reference/v2/rest-api/x402-facilitator/get-supported-payment-schemes-and-networks
- x402 official site: https://x402.org/
Be careful with websites that promise unrealistic rewards, ask for deposits before withdrawal, or require suspicious wallet connections. Small reward sites should never need your seed phrase.
FAQ
Does x402 support more than USDC?
Yes. The current EVM reference implementation supports EIP-3009 assets and generic ERC-20 tokens through Permit2.
Does x402 support several blockchains?
Yes. Version 2 uses CAIP-2 network identifiers and has EVM and Solana SDK support.
Does every facilitator support every x402 network?
No. Facilitator support is narrower and must be queried.
What identifies an EVM network?
A CAIP-2 value such as eip155:8453 for Base mainnet.
What is EIP-3009 used for?
It lets supported tokens use signed transfer authorizations without a separate approval transaction.
Why can Permit2 require gas first?
The payment token may need a one-time on-chain approval to the Permit2 contract.
Can a seller accept multiple payment options?
Yes. The server can advertise several acceptable network, asset and scheme combinations.
Why is the ticker not enough?
The exact contract or mint, network and facilitator support determine whether the route is valid.