x402 Multiple Tokens and Networks Explained

x402 is often introduced through USDC on Base, but that example is not the protocol boundary. Version 2 uses chain-agnostic network identifiers, separate asset identifiers and facilitator-advertised payment schemes. This guide uses an x402 Payment Coordinate so a client can distinguish broad SDK capability from the exact token-network route a facilitator can settle.

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.

Use the x402 Payment Coordinate

One payable resource is defined by four independent coordinates.

• Network — the CAIP-2 chain identifier.
• Asset — token contract or mint.
• Scheme — exact, upto or another supported payment mechanism.
• Facilitator — 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, authorisation 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 authorisation

Tokens such as USDC and EURC can support signed transfer authorisations that a facilitator submits. The buyer does not need a separate token-approval transaction for this path.

Permit2 expands EVM token support

Coinbase’s current x402 documentation says the reference EVM implementation can use Permit2 for generic ERC-20 tokens on EVM-compatible chains. The buyer authorises 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 authorisation. 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.

Current CDP facilitator networks

Coinbase’s current documentation lists hosted support for Base, Polygon, Arbitrum, World and Solana, with testnet options documented separately. That list can expand and should be queried rather than hard-coded.

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.

Use an x402 Capability Card

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 authorisation 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.

How this page avoids internal cannibalization

This page owns the technical matrix of x402 version, network, asset, scheme and facilitator. [What Is x402 Crypto Payments](https://wakeuptocrypto.com/guides/what-is-x402-crypto-payments/) should own the basic HTTP payment flow. [Paid in Stablecoins but Received No Data](https://wakeuptocrypto.com/guides/x402-security-risks-paid-but-no-data/) owns delivery and authorisation failures. [Could the Next Crypto Market Be Machine-to-Machine Commerce](https://wakeuptocrypto.com/guides/could-the-next-crypto-market-be-machine-to-machine-commerce/) owns market potential.

How this article was prepared

The existing page and the closest Wake Up To Crypto articles were reviewed first. Current primary documentation was then checked for the technical or platform rules that materially affect the answer. The page was rebuilt around a unique decision framework instead of a reusable beginner checklist. No unnamed site, wallet, payment route or earning method is presented as permanently safe.

Limitations

Interfaces, network support, fees, earning inventory and platform rules can change. Worked examples demonstrate the method rather than guaranteeing payment, security, eligibility or future availability. The live wallet prompt, provider terms and confirmation screen remain authoritative.

Sources checked on July 27, 2026

Primary wallet, protocol and FaucetPay documentation was preferred. No Google source is included.

• 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/

FAQ