USDT sent on BNB Smart Chain to an address expecting Ethereum, ETH sent on Arbitrum instead of Ethereum: whether you can get it back depends on one question. Who holds the keys to the address it landed on?
The transaction went through, the explorer says success, and the coins are not where you expected. Usually nothing is lost: the coins are sitting at the right address on a different network. Whether you can get them back depends on one question: who holds the keys to that address on that network?
Why it happens
USDT, USDC and ETH live on many networks at once. Ethereum, BNB Smart Chain, Arbitrum, Base, Polygon and the Avalanche C-Chain all use the same kind of address, starting with 0x, so a wallet happily sends USDT on BNB Smart Chain to an address the recipient only watches on Ethereum. The transfer is valid; it just happened on a network the recipient was not looking at.
Networks with different address formats (Tron addresses start with T, Bitcoin with 1, 3 or bc1, Solana uses its own format) usually protect you: most wallets refuse to send to an address that is invalid on the chosen network.
Case 1: you sent it to your own wallet
This is the good case. If the address is in a wallet where you hold the recovery phrase (MetaMask, Trust Wallet, a hardware wallet), the same key controls that address on every 0x network. Add the network the coins actually went to in your wallet, and they appear. One exception: a smart-contract wallet (a Safe, for example) exists only on the networks it was set up on, so check with its provider before assuming the coins are reachable.
- Look the transaction up on a block explorer to see which network it really used.
- Add that network in your wallet (most wallets list BNB Smart Chain, Arbitrum, Base, Polygon and Avalanche in their settings).
- To move the coins on from there, the address needs that network’s own coin for the fee, for example BNB on BNB Smart Chain or ETH on Arbitrum.
Case 2: you sent it to an exchange or a service
Here the keys belong to the exchange, so only the exchange can move the coins. Many exchanges can recover a deposit sent on a network they do not support for that coin, sometimes for a fee and sometimes after a long wait; some cannot or will not. Write to their support with the transaction hash, the network you used, the coin, the amount and the address. The sooner you ask, the better.
The same goes for a swap service’s deposit address: contact its support with the same details. Do not send a second transfer to "fix" the first one.
Case 3: the funds are really gone
- Sent to a token’s own contract address instead of a wallet: usually unrecoverable.
- Sent to an address nobody holds the key for on that network: no one can sign for it, so no one can move it.
- A missing memo or tag on networks that need one (XRP, some exchange deposits): the coins reach the exchange but not your account; support can often match them if you give the transaction hash.
How to never do it again
- Read the network name on BOTH sides before you send: the one in your wallet and the one the recipient asked for. "USDT" is not enough; "USDT on Tron" is.
- Send a small test first when the address or the network is new to you.
- Check the first and last characters of the address after you paste it.
- Add a memo or tag whenever the recipient gives you one.
On Cambio, the deposit card states the coin and the network to send on, next to the address. If anything about a deposit looks wrong, write to [email protected] with the transaction hash before sending anything else.
