Every extra chain is a recovery policy you now owe. “We accept USDC everywhere” without a wrong-chain runbook is a support budget in disguise.
Pick a default
For most B2B: USDC on Ethereum or Polygon. Add Tron if that is where your clients already live (USDT). Add BSC if they live there. Do not add a chain because a conference booth said so.
Invoice must name chain + asset + address
The pay page should make it hard to pay the right token on the wrong network. Exchanges still will. Your status should be wrong_chain, not paid.
Rate locks
USD invoice, USDT on Tron vs USDC on Ethereum are not the same operational object even if the ticker looks dollar-like. Lock per invoice.
Settlematic
Collect: USDC, USDT, EURC, ETH, BTC across Ethereum, Polygon, BSC, Tron, Bitcoin; Solana is native SOL in production. Gateway sandbox. We would rather you enable three chains well than six chains as a slogan.
Canonical: how to accept stablecoin payments multi-chain. settlematic.com
Top comments (0)