FEATURES

Multi-chain

One handle, six chains. The same @yourname resolves to your wallet address on Base, BSC, Solana, Ink, Celo, and Tempo — Tab settles whichever stablecoin the buyer is paying with into that wallet on the chain they pay on.

How routing works

The buyer chooses a chain at checkout (or accepts the default). Tab's router contract on that chain pulls the buyer's stablecoin and forwards it to your address on the same chain. There is no bridging in the hot path — funds stay on the chain they were paid on.

Why no bridging

Bridges add latency, fees, and a non-trivial trust assumption. Tab's job is to settle payments, not to consolidate balances. If you want all your USDC on Base regardless of where customers pay, that's a job for a treasury tool downstream — Tab will not sneak a bridge into your payment flow.

What you'll see in the dashboard

Balances per chain, per stablecoin. Each row links to the explorer for that network so you can reconcile against the on-chain record if you want.

What about new chains?

Deploying TabRouter to a new EVM chain is mostly mechanical — the contracts are immutable and per-deployment. We have an open backlog of requests at our community page; the bottleneck is operational (running relayers, monitoring) rather than contractual.