Network Identifiers Use CAIP-2
Theaccepts[].network in x402 v2 is a CAIP-2 identifier, not an abbreviation such as base or solana. Clients must compare networks by CAIP-2 string:
Support Matrix
upto is currently only provided on Base. The actual available items are subject to the accepts returned by the API. You can also check the Facilitator:
/supported:
exacton Base and Solana is a fixed-amount payment path.- Only Base provides the
uptopost-metering path, which depends on Permit2 approve. - The
extra.facilitatorAddressin theuptoentry is the address that must be written into the witness when the client signs, and it must be consistent with the value returned by the server.
Base
Base uses the official USDC contract:exact scheme, the client signs EIP-712 TransferWithAuthorization. The signing content includes:
from: payment wallet addressto: Ace Data Cloud receiving addressvalue: payment amount for this transactionvalidAfter/validBefore: signature validity time windownonce: 32-byte random nonce
transferWithAuthorization on-chain to complete the transfer.
Base is the most recommended production integration network, especially suitable for upto post-metering, because the Permit2, USDC, and wallet ecosystems are more mature.
Example of the Base exact verification result:
- The API paid retry returns the model content
ADC_BASE_E2E_OK. - The on-chain transaction can be found on BaseScan, and the block number is
46726299. 95215atomic USDC corresponds to0.095215USDC, which is the actual settlement amount for this API call.
exact:
- The final status of the platform order is
Finished. - The order
pay_idis written with the same Base transaction hash. 1200000atomic USDC corresponds to1.2USDC, which is the historical actual payment amount for this 10 Credits order under the old policy; new orders no longer receive an additional X402 payment method discount, and the specific signing amount is subject to the 402 response for this transaction.
Solana
Solana uses SPL USDCTransferChecked. The client constructs a transfer transaction, signs and submits it, and then puts the transaction signature or serialized transaction into the PAYMENT-SIGNATURE envelope.
Characteristics of Solana:
- Uses Solana wallet adapter or base58 secret key;
- The asset is Solana USDC mint;
- Currently only supports
exact; - The Facilitator verifies the mint, destination, authority, and amount of the transfer instruction.
exact verification result:
- The paid retry has returned HTTP 200, and the model output is
ADC_SOLANA_E2E_OK. - Public RPC queries for on-chain signatures may encounter rate limits.
- Because public RPC queries may be rate-limited, the Solana explorer is not included here. When strict reconciliation is needed, please use your own Solana RPC or platform-side settlement records to confirm the transaction signature.
How to Choose
No matter which chain you choose, do not hardcode prices on the client. Prices are determined by the
accepts[].maxAmountRequired returned by the server.
Add New EVM Networks
Code support has been provided for native USDC fixed-amount payments on the following networks, and they are being enabled one by one by network. Availability is subject to theaccepts returned by the order or API; this does not mean that all networks have been enabled in production.
These networks support only
exact, with a token precision of 6. Do not use bridged USDC with the same name.
When using the official TypeScript/Python X402 Client, you can pass the alias or CAIP-2 identifier in the table.
The client constructs signatures using the target chain ID; the wallet must support the target network.
The official support table for the Phantom extension wallet lists Arbitrum and Polygon; Optimism and Avalanche
are currently not included in that table, and Rabby or MetaMask that supports the target chain can be used. EVM addresses can be the same across different chains,
but balances are independent of each other, and Solana addresses do not apply to EVM USDC.
See the Phantom wallet support table.
New network gradual rollout entry
New chain entries are hidden by default. When accessing the console or Studio, you can use?features=x402-arbitrum
to enable the corresponding chain, and separate multiple flags with commas. To disable a single chain, use ?features=-x402-arbitrum,
and use ?features=none to clear local overrides. Switches are stored separately for each domain.
Order quotes and payment retries use the same switch, and the server independently validates them; existing payment records can still be viewed.
Enabling only the page flag will not enable chains that have not yet been configured; the specific payable networks are still subject to real-time accepts.
