A wrong-network transfer looks the same for everyone: the wallet marks it as sent, the explorer shows confirmations, and the casino balance stays exactly where it was. What usually follows is a second transfer "just in case", which only makes the situation harder to unpick. Here is what is actually going on.
The network is not the ticker
USDT runs on TRC-20, ERC-20, BEP-20, TON and SOL; USDC on ERC-20 and BEP-20. These are separate blockchains with different address formats, speeds and fees, connected only by the token name. A deposit address is issued for one specific coin/network pair, which is why "USDT is USDT" is an expensive way to think.
EVM-compatible chains are a trap of their own. An address on Ethereum, BNB Smart Chain and Ethereum Classic looks identical — "0x" followed by 40 characters. The wallet will accept it without complaint and the coins will travel on whichever chain the network selector says, not the one you had in mind.
What happens to the coins
They do not disappear or burn. They remain a blockchain entry at the receiving address — just on a chain the system does not watch for that address. No automatic credit follows, because the service only listens to the networks the address was issued for.
From there, the outcome depends on which scenario you hit.
Case 1: compatible addresses, different chains
The classic version is a "0x" address with coins routed through BNB Smart Chain instead of Ethereum, or the other way round. The private key behind that address is the same across EVM chains, so the funds are technically reachable. This is the most workable case, but any review is manual and depends on the specifics — the outcome is not promised in advance.
Case 2: an entirely foreign network
When the address format does not match the target chain, a sane wallet refuses to send at all. If those checks are missing and the transfer goes through anyway, the coins land at an address neither you nor the platform holds a key for. Transfers like that do not come back — that is a property of blockchains, not a decision anyone made.
Case 3: right network, missing extra field
Some networks rely on more than an address. If the deposit page displays additional data and the sending wallet was left without it, the payment physically arrived but was not tied to an account. Nothing is lost here; it is a matching problem that starts from the TXID.
What to do immediately
- Stop. Do not send a second transfer — it will not catch up with the first one.
- Save the TXID and open the transaction in an explorer for the network that was actually used.
- Write down the coin, the network, the sending and receiving addresses, the exact amount and the time.
- Send support a single message containing all of it: on-site chat, @TonzaSupportBot or [email protected].
Describe what happened plainly, including the step where it went wrong: the chain shows the real sequence regardless, and a tidied-up version only stretches the review out.
How to stop it happening again
- Take the address from the cashier every single time; never keep it in notes or old messages.
- Set the network in two places — the sending side and the cashier — and confirm they are the same one.
- Do not trust a wallet that guesses the chain from the address format: "0x" is shared by several of them.
- Check that the sending exchange actually withdraws on that chain rather than on its cheapest default.
- For a large amount, send a minimal test transfer first.
Supported networks and per-coin details live on the coin pages, for example USDT, ETH or TON. Five minutes of checking costs less than any post-factum investigation.
