Overview
Networks and token pairs supported on Atum’s Payment Gateway.Testnet support
To see which networks the gateway currently supports, ask it for its chain defaults:chain_id, it returns every chain the gateway serves, keyed by CAIP-2 id. A chain that isn’t fully configured is left out of that listing, so what comes back is what you can actually pay on. A 200 here also tells you the gateway is up. A non-200 is a gateway-side answer, not a network problem: 404 means it resolved no chains and 503 means a dependency is down — in both cases the gateway is up and you have nothing to fix locally.
Use these identifiers when constructing payment requests or calling the API:
- CAIP-2 chain ID — used in asset identifiers (
sourceAsset,destinationAsset) and the/v1/defaults?chain_id=query parameter - Chain ID — used when configuring your wallet or RPC provider (e.g. MetaMask network settings,
ethers.JsonRpcProvider)
The table is a snapshot —
/v1/defaults above is the authoritative live list.The example apps are EVM-based, so they don’t demonstrate Solana or Tron. Both are supported — use the identifiers above verbatim, since a wrong token variant is a common cause of a payment that silently doesn’t land.Mainnet support
The mainnet Payment Gateway serves Ethereum, Solana, Tron, Base, Arbitrum, Tempo, Optimism, Polygon, Avalanche, and Celo. Confirm the live list:The table is a snapshot.
/v1/defaults on the mainnet gateway is the authoritative live list.Tempo corridors are access-gated. Contact your Atum representative for access. Asset identifiers are on Supported assets.