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:

โ€‹
How to choose the right chain

โ€‹
Chain identifiers

Each supported chain is identified by a chain_id, which is a string identifier (for example, ETH or TRON), not a numeric ID. The token_id used throughout the Payments API combines the chain identifier with the token symbol in the format {chain_id}_{token_symbol} (for example, ETH_USDC or TRON_USDT). Some chain identifiers themselves contain underscores (for example, AVALANCHE_C), and some token symbols are not the plain ticker. Always use the exact token_id values listed in the supported tokens table above rather than constructing them by hand. The following table maps each chain_id to its full chain name and network. These chains are supported for payment collection on the Starter Live and Enterprise plans. To retrieve the live set of supported chains and tokens programmatically, use the List supported chains and List supported tokens operations.

โ€‹
Token decimals

Each supported token has a decimal value โ€” the number of decimal places used to convert between the tokenโ€™s smallest on-chain base unit and its human-readable display value. For example, a token with a decimal of 6 represents one display unit as 1000000 base units on-chain. TRON_USDT uses a decimal of 6, which is the USDT standard. Payments API order and transaction amounts are expressed as decimal strings in display units (for example, 10.5), not base units, so you do not need to apply decimal when you create orders or read amounts from the Payments API. The decimal value matters mainly when you reconcile Payment activity against raw on-chain base-unit amounts. The decimal value for each token is returned in the decimal field of the List supported tokens operation. Decimal precision can differ between chains for the same stablecoin, so always read the authoritative value from this operation rather than assuming a fixed value.

โ€‹
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.

โ€‹
Testnet

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

โ€‹
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.