Chains and tokens

The API accepts more chains and tokens than it can confirm. A payment on a combination that is not watched is created normally, shows an address, and never confirms, with no error anywhere. Offer your customers only the combinations marked live below.

There is no endpoint that lists payable combinations; this page is the list. It was last checked on 2026-09-19.

Mainnet

So the stablecoins you can accept on mainnet today are USDC on BNB Chain, USDC on Sui, USDC on Arc and USDG on Robinhood Chain. "Not yet" rows are registered, so the API accepts them, but api.thru.la is not watching them, and a payment made with one would not be detected. Do not offer them until this page marks them live.

Native coins (BNB, SUI, ETH) are live but are charged in coins: thru does no currency conversion, so "amount": "25" with "token": "BNB" asks for 25 BNB. For dollar prices, use stablecoins.

Testnet

Test on Arc testnet ("chain": "arc", "network": "testnet", "token": "USDC"), with test USDC from Circle's faucet. It is the only testnet api.thru.la watches today.

Rails a custom-amount product may use

A custom_amount product (products) charges the session amount in units of the rail's token, 1:1: "amount": "37" on a USDC rail asks for 37 USDC, and on a BNB rail it asks for 37 BNB. thru does no currency conversion, so for dollar-denominated credit list stablecoin rails only. POST /v1/products and PATCH /v1/products/:id refuse a rail (the product's own chain/token, every networks row and every enabledChains entry) whose token is not registered for that chain and network, or whose chain thru does not watch — with <token> on <chain>/<network> is not a token thru detects or <chain> cannot be a rail on a custom_amount product. As of the date above, the stablecoin rails that are live are:

• mainnet: USDC on bnb, USDC on sui, USDC on arc, USDG on robinhood;
• testnet: USDC on arc.

Native coins (BNB, SUI, ETH) pass the check and are charged in coins. Fixed-price products are not restricted.

Chains the API accepts but never confirms

• ethereum, polygon, arbitrum, optimism, avalanche, fantom, gnosis, linea, scroll, zksync, mantle, celo, blast and bsc are accepted by POST /v1/payments (201), but no token is registered for them, so a payment on them never confirms. ethereum is the one people reach for first; it is not live. For BNB Smart Chain, use bnb, not bsc.
• A token that is not in the tables above is also accepted and never confirms. For example, "token": "DAI" on bnb creates a payment that will never be detected.

Chains the API rejects

aptos, bitcoin, litecoin, dogecoin, xrp, ton, near, cosmos, polkadot and cardano return 400 on create, because thru has no wallet on them that could receive funds.

Notes per chain

• Arc. USDC is Arc's native asset (it also pays gas), registered with 18 decimals and no contract address. Arc also exposes the same balance through an ERC-20 interface at 0x3600000000000000000000000000000000000000 with 6 decimals. That is the same money, not a second token, and thru does not watch it. Payers must send USDC as a normal wallet transfer of the native asset.
• Native coins on EVM chains (BNB, ETH on Robinhood Chain, USDC on Arc) are detected from the value of a top-level transaction. A native transfer made from inside a smart contract, which many smart-contract wallets and some exchange withdrawals do, is not detected. Tokens such as USDC on BNB Chain are detected from their transfer events and do not have this limitation.
• BNB Chain USDC and USDT use 18 decimals, not the 6 they use on most chains. Amounts in the API are in token units, so this matters only if you work with atomic amounts.
• Robinhood Chain has no USDC; its dollar stablecoin is USDG.
• token accepts the symbol or the contract address or coin type from these tables, and thru stores the symbol.