> ## Documentation Index
> Fetch the complete documentation index at: https://cobo.com/payments/llms.txt
> Use this file to discover all available pages before exploring further.

# Supported tokens and chains

> Learn about supported tokens, chains, and currencies for payment collection and Off-Ramp scenarios.

## 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

<Note>
  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.
</Note>

## 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:

| Stablecoin | Chain             | Token ID           | Confirmations | Min Amount | Gas Token |
| ---------- | ----------------- | ------------------ | ------------- | ---------- | --------- |
| **USDC**   | Ethereum          | ETH\_USDC          | 64            | 0.05 USDC  | ETH       |
|            | Arbitrum          | ARBITRUM\_USDCOIN  | 32            | 0.05 USDC  | ETH       |
|            | Base              | BASE\_USDC         | 100           | 0.05 USDC  | ETH       |
|            | Polygon           | MATIC\_USDC2       | 128           | 0.05 USDC  | MATIC     |
|            | BNB Smart Chain   | BSC\_USDC          | 15            | 0.05 USDC  | BNB       |
|            | Solana            | SOL\_USDC          | 1             | 0.05 USDC  | SOL       |
|            | Avalanche C-Chain | AVALANCHE\_C\_USDC | 18            | 0.05 USDC  | AVAX      |
|            | Morph             | MORPH\_USDC        | 100           | 0 USDC     | MORPH     |
|            | Aptos             | APT\_USDC          | 1             | 0 USDC     | APT       |
| **USDT**   | TRON              | TRON\_USDT         | 20            | 0.05 USDT  | TRX       |
|            | Ethereum          | ETH\_USDT          | 64            | 0.05 USDT  | ETH       |
|            | Arbitrum          | ARBITRUM\_USDT     | 32            | 0.05 USDT  | ETH       |
|            | Base              | BASE\_USDT         | 100           | 0.05 USDT  | ETH       |
|            | Polygon           | MATIC\_USDT        | 128           | 0.05 USDT  | MATIC     |
|            | BNB Smart Chain   | BSC\_USDT          | 15            | 0.05 USDT  | BNB       |
|            | Solana            | SOL\_USDT          | 1             | 0.05 USDT  | SOL       |
|            | TON               | TON\_USDT          | 5             | 0.05 USDT  | TON       |
|            | Avalanche C-Chain | AVALANCHE\_C\_USDT | 18            | 0.05 USDT  | AVAX      |
|            | Morph             | MORPH\_USDT        | 100           | 0 USDT     | MORPH     |
|            | Aptos             | APT\_USDT          | 1             | 0 USDT     | APT       |

### How to choose the right chain

| Priority                         | Recommended Chains                                 | Why                                                      |
| -------------------------------- | -------------------------------------------------- | -------------------------------------------------------- |
| Lowest Gas Fee                   | BNB Smart Chain, Arbitrum, Base                    | Layer 2 or low-cost networks — lower Gas Fees for payers |
| Widest compatibility             | Ethereum                                           | Most widely supported                                    |
| Off-Ramp ready (no bridging fee) | Ethereum (ETH\_USDC, ETH\_USDT), TRON (TRON\_USDT) | No additional bridging fees required                     |

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

| chain\_id     | Chain             | Network |
| ------------- | ----------------- | ------- |
| `ETH`         | Ethereum          | Mainnet |
| `ARBITRUM`    | Arbitrum          | Mainnet |
| `BASE`        | Base              | Mainnet |
| `MATIC`       | Polygon           | Mainnet |
| `BSC`         | BNB Smart Chain   | Mainnet |
| `SOL`         | Solana            | Mainnet |
| `AVALANCHE_C` | Avalanche C-Chain | Mainnet |
| `MORPH`       | Morph             | Mainnet |
| `APT`         | Aptos             | Mainnet |
| `TRON`        | TRON              | Mainnet |
| `TON`         | TON               | Mainnet |

To retrieve the live set of supported chains and tokens programmatically, use the List supported chains and [List supported tokens](/payments/en/api-references/payment/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](/payments/en/api-references/payment/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.

## <a name="pricing-currency" />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](/payments/en/api-references/payment/get-exchange-rate) operation.

<Note>
  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.
</Note>

* `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.

<Info>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.</Info>

| Token and Chain    | Development Environment           | Production Environment            |
| ------------------ | --------------------------------- | --------------------------------- |
| ETH\_USDC          | Supported                         | Supported                         |
| ARBITRUM\_USDCOIN  | Not supported                     | Supported (bridging fee required) |
| BASE\_USDC         | Not supported                     | Supported (bridging fee required) |
| MATIC\_USDC2       | Not supported                     | Supported (bridging fee required) |
| BSC\_USDC          | Not supported                     | Supported (bridging fee required) |
| SOL\_USDC          | Not supported                     | Supported (bridging fee required) |
| AVALANCHE\_C\_USDC | Not supported                     | Not supported                     |
| MORPH\_USDC        | Not supported                     | Not supported                     |
| APT\_USDC          | Not supported                     | Not supported                     |
| TRON\_USDT         | Supported                         | Supported                         |
| ETH\_USDT          | Supported                         | Supported                         |
| ARBITRUM\_USDT     | Not supported                     | Supported (bridging fee required) |
| BASE\_USDT         | Not supported                     | Not supported                     |
| MATIC\_USDT        | Supported (bridging fee required) | Supported (bridging fee required) |
| BSC\_USDT          | Supported (bridging fee required) | Supported (bridging fee required) |
| SOL\_USDT          | Not supported                     | Supported (bridging fee required) |
| TON\_USDT          | Not supported                     | Not supported                     |
| AVALANCHE\_C\_USDT | Not supported                     | Not supported                     |
| MORPH\_USDT        | Not supported                     | Not supported                     |
| APT\_USDT          | Not supported                     | Not 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.

| Token | Testnet   | Token ID     | Contract Address                     | Faucet                                                |
| ----- | --------- | ------------ | ------------------------------------ | ----------------------------------------------------- |
| USDT  | TRON Nile | TTRON\_USDT1 | `TXYZopYRdj2D9XRtbG411XZZ3kM5VkAeBf` | [Get test tokens](https://nileex.io/join/getJoinPage) |

## Important notes

<Warning>
  **Always verify the network before sending**

  Sending 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](https://support.cobo.com) with the transaction hash for assistance.
</Warning>

<Note>
  **Token ID usage**

  When 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.
</Note>

## Related resources

* [List tokens supported by Payment](/payments/en/api-references/payment/list-supported-tokens) — Query the tokens supported for Payment programmatically (returns only Payment-supported tokens, not all Cobo-supported tokens)
* [Create a pay-in order](/payments/en/guides/create-orders) — Learn how to create payment orders with pricing currencies