Supported chains and tokens
Chains, tokens, decimals, and confirmation depths.
This page lists the chains and tokens Tekmerion accepts payments on, with the confirmation thresholds that govern when a deposit is recognized and when a payment outcome becomes canonical.
Supported chains
| Chain | chain_id | N_obs | N_final |
|---|---|---|---|
| Arbitrum One | 42161 | 1 | 300 |
| Base | 8453 | 1 | 12 |
| BSC | 56 | 1 | 25 |
| Optimism | 10 | 1 | 12 |
| Polygon PoS | 137 | 1 | 128 |
| Avalanche C-Chain | 43114 | 1 | 20 |
Supported tokens
Token identity is chain-scoped. The same stablecoin on two different chains is two distinct token_id values. Use the exact token_id from the table below in API requests — the API does not accept symbol aliases.
| Chain | chain_id | Symbol | token_id | Decimals |
|---|---|---|---|---|
| Arbitrum One | 42161 | USDC | 0xaf88d065e77c8cC2239327C5EDb3A432268e5831 | 6 |
| Arbitrum One | 42161 | USDT0 | 0xFd086bC7CD5C481DCC9C85ebE478A1C0b69FCbb9 | 6 |
| Base | 8453 | USDC | 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 | 6 |
| Base | 8453 | USDT | 0xfde4C96c8593536E31F229EA8f37b2ADa2699bb2 | 6 |
| BSC | 56 | USDT | 0x55d398326f99059fF775485246999027B3197955 | 18 |
| Optimism | 10 | USDC | 0x0b2C639c533813f4Aa9D7837CAf62653d097Ff85 | 6 |
| Optimism | 10 | USDT | 0x94B008aA00579c1307B0EF2c499aD98a8ce58e58 | 6 |
| Polygon PoS | 137 | USDC | 0x3c499c542cEF5E3811e1192ce70d8cC03d5c3359 | 6 |
| Polygon PoS | 137 | USDT | 0xc2132D05D31c914a87C6611C10748AEb04B58e8F | 6 |
| Avalanche C-Chain | 43114 | USDC | 0xB97EF9Ef8734C71904D8002F8b6Bc66Dd9c48a6E | 6 |
| Avalanche C-Chain | 43114 | USDT | 0x9702230A8Ea53601f5cD2dc00fDBc13d4dF4A8c7 | 6 |
BSC USDT decimals. BSC USDT uses 18 decimals, unlike the 6-decimal convention on all other chains. Apply the correct decimal precision for the chain when converting base units to display amounts. See Amounts and decimals.
Column definitions
| Column | Meaning |
|---|---|
chain_id | Numeric chain identifier. Used verbatim in API requests and encoded as a string on the notification wire and in Proof-of-Payment artifacts. |
token_id | Canonical token identifier — on EVM chains, the token contract address. Used verbatim as token_id in API requests. Do not use symbol names as a substitute. |
| Decimals | The token's decimal precision. On-chain amounts are expressed in base units — divide by 10^decimals to obtain the human-readable figure. See Amounts and decimals. |
| N_obs | Confirmed-block depth at which a deposit is recognized as present and the post-deposit compliance pipeline begins. The outcome is still reorg-sensitive below N_final. |
| N_final | Confirmed-block depth at which a payment outcome becomes canonical and a Proof-of-Payment can be finalized. Below this threshold, observations may be corrected if the chain reorganizes. |
Confirmation thresholds
N_obs — observed threshold. A deposit that reaches this depth triggers the post-deposit compliance pipeline: sanctions screening runs, and then Tekmerion invokes the merchant's KYT endpoint. The deposit is not yet canonical at this depth; it may still be corrected by a chain reorganization before N_final is reached.
N_final — finality threshold. A payment that reaches this depth is canonical. A reorg occurring after finality is detected and recorded rather than reversed automatically. See Edge cases.
Confirmation thresholds are per-chain and reflect each network's reorganization risk profile. Chains with high N_final values — in particular Arbitrum One (300) and Polygon PoS (128) — have longer windows between observed and finalized state.
Requesting additional chains or tokens
Contact your onboarding representative to discuss adding chains or tokens not listed here.