Reference Table: token_id and Blockchain Mapping

This table serves as a reference for the available token_id values that can be returned in the token_options.

This table serves as a reference for the available token_id values that can be returned in the token_options response from the GET /api/orders/{id} endpoint and must be used in the request to POST /api/txs/generate/memo.

token_id	Blockchain (Chain)	Symbol / Notes
Bitcoin	Bitcoin	BTC
Ethereum	Ethereum	ETH
EthereumUsdc	Ethereum	USDC (ERC-20)
USDT	Ethereum	USDT (ERC-20)
EthMoca	Ethereum	MOCA (ERC-20)
EthereumArb	Ethereum	ETH (Bridged to Arbitrum)
Arbitrum	Arbitrum	ARB (Native Token)
ArbitrumEth	Arbitrum	ETH (on Arbitrum One)
USDC	Arbitrum	USDC (on Arbitrum One)
BaseEth	Base	ETH (on Base)
Solana	Solana	SOL
Avax	Avalanche	AVAX
XRP	XRP Ledger	XRP
Cardano	Cardano	ADA
Litecoin	Litecoin	LTC
Dogecoin	Dogecoin	DOGE
Dash	Dash	DASH
Binance	BNB Smart Chain	BNB
Rune	THORChain	RUNE
TCY	THORChain	TCY
Cacao	Maya Protocol	CACAO
Maya	Maya Protocol	MAYA
Kuji	Kujira	KUJI
USK	Kujira	USK
Radix	Radix	XRD

---

Important Notes for Developers:

1. Usage in APIs: The field used in requests to the Moca API (specifically in the body of POST /api/txs/generate/memo) is the value from the token_id column (e.g., ArbitrumEth, EthereumUsdc).

2. Purpose of the "Blockchain" Column: The "Blockchain" column is for your reference only, so your wallet knows which network to connect to in order to build and sign the transaction. It is not a parameter that is sent to the API.

3. Stablecoins: Stablecoins like EthereumUsdc (USDC on Ethereum) and USDC (USDC on Arbitrum) are different tokens. Ensure the wallet uses the correct network for the specified token_id.

4. Support: Your wallet does not need to support all tokens on this list. You can choose to integrate only those that are relevant to your users. The list of options you receive for a specific order (token_options) is determined by what the merchant has configured to accept.