# How the multi_token parameter works By default, an address from [ticker create](/api/tickercreate) accepts only the ticker you asked for. If you create it with `trc20/usdt`, only USDT on Tron counts as a payment. With [`multi_token=1`](/api/tickercreate#multi_token), the address accepts every coin and token CryptAPI supports on that blockchain, native coins included. The parameter is optional and its default is `0`. ## Supported blockchains - **Tron**: TRX and TRC-20 tokens - **EVM networks**: the native coin and tokens of every EVM network (see below) - **Solana**: SOL and SPL tokens - **TON**: supported TON tokens (Jettons) Other blockchains, such as Bitcoin and Litecoin, ignore the parameter and return no error. ## What EVM networks are EVM stands for Ethereum Virtual Machine, the software that runs Ethereum. Many other blockchains run it too, so they share Ethereum's address format: an address that starts with `0x` exists on all of them. CryptAPI supports these EVM networks: - Ethereum (`eth` and `erc20/...` tickers) - BNB Smart Chain (`bep20/...`) - Polygon (`polygon/...`) - Arbitrum (`arbitrum/...`) - Avalanche C-Chain (`avax-c/...`) - Base (`base/...`) - Optimism (`optimism/...`) - Linea (`linea/...`) - Berachain (`bera/...`) - Monad (`monad/...`) See the [cryptocurrencies page](https://cryptapi.io/cryptocurrencies) for the current list of networks and tokens. CryptAPI gives your callback URL one EVM address, used on every EVM network. With `multi_token=1`, that address accepts any supported coin or token on **any** of these networks, not only on the network of the ticker you used. An address created with `erc20/usdt` also accepts BNB on BNB Smart Chain or USDC on Base. Each payment goes to your `address` on the network it arrived on. ## Before you enable it - **Your `address` must accept everything that can arrive.** We forward each payment in the asset it arrived in, on the network it arrived on. We can't reverse a forwarded payment. - **Don't use an exchange deposit address.** Exchanges often credit only the asset and network you chose for the deposit, so they may never credit other payments. - **On EVM networks, use a wallet whose address works on every network.** A wallet that you hold the keys to (such as MetaMask) has the same address on all EVM networks. A smart-contract wallet, such as a Safe multisig, exists only on the networks where it was deployed. - **Read the `coin` field in every callback.** [`coin`](/webhooks/custom-payment-flow-webhooks#coin) names the asset received, such as `trx`, `bep20_usdc` or `erc20_usdt`, and `value_coin` is in units of that asset. If you expect 1000 USDT and the customer sends 1000 TRX, the callback has `coin=trx` and `value_coin=1000`, which is worth far less. Convert the value before you mark the order paid. With `convert=1`, the callback includes [`value_coin_convert`](/webhooks/custom-payment-flow-webhooks#value_coin_convert) in fiat. - **Each asset has its own minimum.** The `minimum_transaction_coin` returned by ticker create covers only the ticker you asked for. We ignore any payment below the minimum of the asset received, and we can't recover it. Check the minimums on the [cryptocurrencies page](https://cryptapi.io/cryptocurrencies). ## Good to know - The setting belongs to the callback URL. Once you turn it on, it stays on: a later call without `multi_token=1` doesn't turn it off. For an address that accepts a single token, use a new callback URL. - Without `multi_token=1`, you can't reuse a callback URL for another ticker on the same blockchain (for EVM, on any EVM network). The API returns [`Non multi_token address already created for another token`](/get-started/error-handling). - Without `multi_token=1`, we don't forward other assets sent to the address, and we send no callback for them. If this happens, [contact our support](https://cryptapi.io/contacts). - When the setting is on, the ticker create response includes `"multi_token": true`.