Why these two chains exist on your coin list
Tron carries most of the world's retail USDT and Solana is the cheapest fast rail — we've compared those elsewhere. But a real slice of buyers hold stablecoins on EVM chains and think in terms of MetaMask, not Tron or Phantom. For them, Ethereum ERC-20 is the obvious home and also the painful one: a single USDT transfer can cost several dollars in gas, which is fine on a $2,000 invoice and ridiculous on a $20 one.
BNB Chain (BSC) and Polygon are the low-fee EVM escape hatch. Same wallet, same token standard, same dollar — but transfers cost a fraction of a cent to a few cents, and settle in under a minute. If your audience is EVM-native but price-sensitive, these are the two chains that let them pay without bridging to Ethereum or leaving the ecosystem they know.
What settlement actually looks like
Both chains are fast by Bitcoin or Ethereum-mainnet standards, with BSC slightly ahead of Polygon in how quickly we mark a payment paid:
- BNB Chain (BEP20): ~3-second blocks. We credit BNB, USDT and USDC deposits at 15 confirmations — roughly 45 seconds of wall-clock finality buffer.
- Polygon: ~2-second blocks. We credit POL, USDT and USDC at 30 confirmations — around a minute. It's a slightly deeper threshold on purpose: Polygon's shorter blocks and reorg profile earn a larger confirmation count, so it lands a touch slower than BSC. Both still clear well inside the window a customer will happily wait through at checkout.
You can raise your own confirmation threshold per coin in settings if your risk posture wants more depth; you can't lower it below the platform floor. For most merchants the defaults are the right trade between speed and safety.
The one real gotcha: 18 decimals vs 6
This is the part worth reading twice, because it's where hand-rolled integrations silently mangle amounts. A stablecoin's "decimals" is how many fractional units make up one token on-chain. Most USDT and USDC deployments use 6 decimals — that's true on Ethereum, on Tron, on Solana, and on Polygon. So $1.00 of USDC on Polygon is 1000000 base units.
On BNB Chain, USDT and USDC use 18 decimals, not 6 — the same precision as BNB itself. So $1.00 of USDT on BEP20 is 1000000000000000000 base units. A codebase that hard-codes "USDC is always 6 decimals" and reuses that constant for BEP20 will be off by a factor of a trillion — either crediting a rounding-error fraction of a cent or, worse, treating a tiny test transfer as a colossal payment. It's the classic reason a naive integration "works on Polygon" and then breaks the moment someone pays over BSC.
OrbChain reads each token's real decimals() value per contract, so USDT on BEP20 (18), USDC on BEP20 (18), USDT on Polygon (6) and USDC on Polygon (6) are each handled at their true precision. You never see base units — deposits, balances and payouts are all normalized to a plain dollar amount. We're calling it out only so you understand why we treat these as distinct assets rather than "USDC, one setting."
Enabling it
If you're already on OrbChain: Settings → Accepted Coins → enable BNB, USDT_BEP20, USDC_BEP20 for BNB Chain and POL, USDT_POL, USDC_POL for Polygon. They immediately appear everywhere you already work — hosted checkout coin picker, payment links, invoices, per-user static addresses — and pay out through the same payout API. Same webhooks, same balance model, same 0.4%. You can see the full roster on the currencies page.
Turning on the native coin (BNB, POL) alongside the stablecoins is optional but usually worth it: some customers hold the gas token itself, and it's the same rail either way.
Merchant-side cautions, honestly
- Polygon runs a touch slower: the higher confirmation count means a Polygon payment marks paid a little later than a BSC one. It's seconds, not minutes — but if you promise "instant" at the register, know that BSC is the snappier of the two.
- Wrong-network sends: the same USDC ticker lives on Ethereum, Polygon, BSC, Solana and more. A buyer withdrawing from an exchange can pick the wrong network and strand funds. Our checkout shows the target network prominently — if you build your own UI on the API, do the same, loudly.
- Native gas volatility: BNB and POL move in price. If you enable the native coins, price invoices in fiat and lean on Auto Settle so you're not holding exposure you didn't choose. The stablecoins, by definition, don't have this problem.
- Two chains, not two balances: accepting USDC on both BSC and Polygon doesn't mean babysitting two ledgers. You can settle everything to one destination and let payout rules keep stablecoins from sitting idle.
Where they fit
BNB Chain and Polygon aren't the chains to enable first — for raw USDT coverage, Tron still wins, and for cheapest-fastest, Solana does. Where these two earn their slot is the EVM-native, gas-averse customer: someone comfortable in MetaMask who'd abandon a checkout that demanded Ethereum gas or a bridge. Enable them and that buyer pays in the wallet they already have, for cents, in under a minute — with the decimals math handled correctly whether the dollar lands on BSC or Polygon.