Supported Tokens & Networks

Supported Tokens & Networks

The values you pass for receiving_network, receiving_token_symbol, and receiving_token_address must come from the tables below (or from Receiving currencies). support_networks / support_tokens are the payer allowlist: take them from Paying currencies, or omit both to allow that full paying catalog. The lists may change with configuration.

Field-to-column mapping for receiving fields:

• receiving_network — the Chain code column (lowercase, e.g. morph).
• receiving_token_symbol — the Token column (e.g. USDT).
• receiving_token_address — the Contract address column (lowercase).

Supported chains

Chain code	Chain name	chain_id
bnb	BNB Smart Chain	56
base	Base	8453
eth	Ethereum	1
arbitrum	Arbitrum One	42161
matic	Polygon	137
morph	Morph	2818

Supported tokens

Chain code	Token	Contract address	Decimals
bnb	USDT	0x55d398326f99059ff775485246999027b3197955	18
bnb	USDC	0x8ac76a51cc950d9822d68b83fe1ad97b32cd580d	18
base	USDC	0x833589fcd6edb6e08f4c7c32d4f71b54bda02913	6
base	USDT	0xfde4c96c8593536e31f229ea8f37b2ada2699bb2	6
eth	USDT	0xdac17f958d2ee523a2206206994597c13d831ec7	6
eth	USDC	0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48	6
arbitrum	USDT	0xfd086bc7cd5c481dcc9c85ebe478a1c0b69fcbb9	6
arbitrum	USDC	0xaf88d065e77c8cc2239327c5edb3a432268e5831	6
matic	USDT	0xc2132d05d31c914a87c6611c10748aeb04b58e8f	6
matic	USDC	0x3c499c542cef5e3811e1192ce70d8cc03d5c3359	6
morph	USDT	0xe7cd86e13ac4309349f30b3435a9d337750fc82d	6
morph	USDC	0xcfb1186f4e93d60e60a8bdd997427d1f33bc372b	6

note

• A receiving (network, symbol, address) must be the combination from a single row of the token table. A mismatch returns 90120 (an unsupported chain returns 90111).
• A payer allowlist you send must be a consistent pair: support_networks equals the distinct support_tokens[].network values. Omitting both fields allows every paying-catalog chain and token.