Skip to main content

​
Overview

This document helps you understand which tokens, chains, and currencies are supported for different payment scenarios:
  • Payment collection: Accept stablecoin payments from your customers
  • Pricing: Set prices in familiar fiat currencies
  • Off-Ramp: Convert stablecoins to fiat currency
The tokens listed in this document are specifically supported for Cobo Payments. While Cobo Portal supports a broader range of tokens, only the stablecoins listed below will be automatically credited when received. Other tokens sent to Payment addresses will not be automatically processed.

​
Plans and Supported Scope

Supported tokens and chains vary by plan:
  • Starter Test: TRON Nile testnet only — accepts USDT test tokens. Test tokens have no real value and are intended for validating your business flow.
  • Starter Live / Enterprise: Supports all mainnet tokens and chain combinations listed below.

​
Supported tokens and chains for payment collection

The following stablecoin and chain combinations are available for Starter Live and Enterprise plans:
StablecoinChainToken IDConfirmationsMin AmountGas Token
USDCEthereumETH_USDC640.05 USDCETH
ArbitrumARBITRUM_USDCOIN320.05 USDCETH
BaseBASE_USDC1000.05 USDCETH
PolygonMATIC_USDC21280.05 USDCMATIC
BNB Smart ChainBSC_USDC150.05 USDCBNB
SolanaSOL_USDC10.05 USDCSOL
Avalanche C-ChainAVALANCHE_C_USDC180.05 USDCAVAX
MorphMORPH_USDC1000 USDCMORPH
AptosAPT_USDC10 USDCAPT
USDTTRONTRON_USDT200.05 USDTTRX
EthereumETH_USDT640.05 USDTETH
ArbitrumARBITRUM_USDT320.05 USDTETH
BaseBASE_USDT1000.05 USDTETH
PolygonMATIC_USDT1280.05 USDTMATIC
BNB Smart ChainBSC_USDT150.05 USDTBNB
SolanaSOL_USDT10.05 USDTSOL
TONTON_USDT50.05 USDTTON
Avalanche C-ChainAVALANCHE_C_USDT180.05 USDTAVAX
MorphMORPH_USDT1000 USDTMORPH
AptosAPT_USDT10 USDTAPT

​
How to choose the right chain

PriorityRecommended ChainsWhy
Lowest Gas FeeBNB Smart Chain, Arbitrum, BaseLayer 2 or low-cost networks — lower Gas Fees for payers
Widest compatibilityEthereumMost widely supported
Off-Ramp ready (no bridging fee)Ethereum (ETH_USDC, ETH_USDT), TRON (TRON_USDT)No additional bridging fees required

​
Supported pricing currencies

When creating a payment order, you can use the following fiat currencies as the pricing currency (pricing_currency). The system will automatically calculate the payable amount based on the real-time exchange rate of the currency. Exchange rates are updated every 10 minutes. You can query the current exchange rate using the Get exchange rate operation.
You can only specify the following currencies as pricing currencies during payment collection. After cryptocurrencies are deposited, if you need to perform Off-Ramp operations, only USD is supported for conversion.
  • USD — United States Dollar
  • CAD — Canadian Dollar
  • MXN — Mexican Peso
  • BRL — Brazilian Real
  • ARS — Argentine Peso
  • CLP — Chilean Peso
  • COP — Colombian Peso
  • PEN — Peruvian Nuevo Sol
  • EUR — Euro
  • GBP — British Pound Sterling
  • CHF — Swiss Franc
  • SEK — Swedish Krona
  • NOK — Norwegian Krone
  • DKK — Danish Krone
  • PLN — Polish Zloty
  • CZK — Czech Koruna
  • HUF — Hungarian Forint
  • CNH — Chinese Yuan Offshore
  • HKD — Hong Kong Dollar
  • JPY — Japanese Yen
  • KRW — South Korean Won
  • SGD — Singapore Dollar
  • TWD — New Taiwan Dollar
  • THB — Thai Baht
  • MYR — Malaysian Ringgit
  • IDR — Indonesian Rupiah
  • INR — Indian Rupee
  • AUD — Australian Dollar
  • NZD — New Zealand Dollar
  • PHP — Philippine Peso
  • VND — Vietnamese Dong
  • AED — United Arab Emirates Dirham
  • SAR — Saudi Riyal
  • QAR — Qatari Rial
  • KWD — Kuwaiti Dinar
  • BHD — Bahraini Dinar
  • ZAR — South African Rand
  • EGP — Egyptian Pound
  • NGN — Nigerian Naira
  • KES — Kenyan Shilling
  • TRY — Turkish Lira
  • ILS — Israeli New Sheqel
  • MAD — Moroccan Dirham

​
Off-Ramp support

The following table lists the supported token and chain combinations for Off-Ramp operations, and their support status in the development and production environments.
Token and chain combinations marked as “bridging fee required” incur additional bridging fees on top of regular fees when performing Off-Ramp operations. For example, converting BASE_USDC through Off-Ramp in the production environment requires an additional bridging fee.
Token and ChainDevelopment EnvironmentProduction Environment
ETH_USDCSupportedSupported
ARBITRUM_USDCOINNot supportedSupported (bridging fee required)
BASE_USDCNot supportedSupported (bridging fee required)
MATIC_USDC2Not supportedSupported (bridging fee required)
BSC_USDCNot supportedSupported (bridging fee required)
SOL_USDCNot supportedSupported (bridging fee required)
AVALANCHE_C_USDCNot supportedNot supported
MORPH_USDCNot supportedNot supported
APT_USDCNot supportedNot supported
TRON_USDTSupportedSupported
ETH_USDTSupportedSupported
ARBITRUM_USDTNot supportedSupported (bridging fee required)
BASE_USDTNot supportedNot supported
MATIC_USDTSupported (bridging fee required)Supported (bridging fee required)
BSC_USDTSupported (bridging fee required)Supported (bridging fee required)
SOL_USDTNot supportedSupported (bridging fee required)
TON_USDTNot supportedNot supported
AVALANCHE_C_USDTNot supportedNot supported
MORPH_USDTNot supportedNot supported
APT_USDTNot supportedNot supported

​
Testnet

The TRON Nile testnet is currently supported. It accepts USDT test tokens, which have no real value and do not involve real funds.
TokenTestnetToken IDContract AddressFaucet
USDTTRON NileTTRON_USDT1TXYZopYRdj2D9XRtbG411XZZ3kM5VkAeBfGet test tokens

​
Important notes

Always verify the network before sendingSending tokens on the wrong network may result in permanent loss of funds. For example:
  • Sending USDT on TRON to an Ethereum address will not be credited
  • Each Token ID corresponds to a specific chain — always match them exactly
If you or your customer accidentally sends tokens on an unsupported network, contact Cobo Support with the transaction hash for assistance.
Token ID usageWhen integrating with the Cobo API, always use the exact Token ID (such as ETH_USDC or TRON_USDT) as specified in this document. Using incorrect Token IDs will result in API errors.