Three things to check first after sending USDT on the wrong network
One: is the recipient an exchange or your own wallet? An exchange deposit address is controlled by the platform, so a deposit on the wrong network can only be sorted out by the platform. An address in your own wallet is controlled by your private key, and whether you can get the funds back depends on whether you hold that key.
Two: was it the chain that was wrong, or the address? If the chain was wrong but the address really is yours or the recipient's, the funds are at the same address on a different chain and there is still a chance of getting them back. If the address itself was wrong, the funds are in a stranger's hands and are as good as unrecoverable.
Three: did the transfer go through a bridge? A direct transfer is the simplest case. With a bridge, what arrived may already be a different token, and the status of the transaction has to be checked through that bridge's official support channel.
Once you know which case you are in, handle it as one of the three below.
Deposited to an exchange on the wrong network: can it be recovered?
An example: you withdraw USDT from Exchange A to Exchange B. You pick BSC (BEP20) as the withdrawal network, but the address you paste is the 0x address from Exchange B's ERC20 deposit page. BSC and Ethereum use the same address format, so nothing blocks the withdrawal. It goes out and shows as successful on-chain, yet it may never appear in Exchange B's deposit history. The chain was wrong and the address was right, which puts this among the cases that can still be recovered.
Step one: go back to the receiving exchange's USDT deposit page and see whether the networks it lists include the chain you actually sent on. Exchanges differ in which networks they support and change them over time, so go by the networks shown on the deposit page at that moment.
Step two: in the receiving exchange's help center or live support, find the entry for wrong-network deposits or deposit recovery and submit a request as instructed. You will generally need the transaction hash (TxID), the time of the transfer, the amount, the sending address and the receiving address.
Whether recovery is possible, how long it takes and whether a handling fee applies differ from exchange to exchange, and the platform may not support your chain or token at all. Go by what its recovery page and the ticket reply say, and ask about the fee before you submit. If the deposit still has not arrived, submit early instead of waiting.
Submit a recovery request only on the platform's official website or in its official app. If someone messages you claiming to be support and asks for your seed phrase, password or verification code, or tells you to send a handling fee to some address first, give them nothing.
Sent to your own wallet on the wrong chain: how to find it
An example: you withdraw USDT from an exchange to your own MetaMask, meaning to use ERC20, and select BSC as the network by mistake. The funds are not lost. They are on the BSC side of your address. EVM chains such as Ethereum, BSC, Polygon and Arbitrum share the same kind of address beginning with 0x, and one address has a separate ledger on each chain, with balances kept apart. You will not see the money while the wallet is on the Ethereum network. Switch to BSC and it is there.
How to do it in MetaMask, with steps taken from the Help Center pages on adding a network and displaying tokens:
- Add the chain. Browser extension: menu in the top right → Networks → find the network under Additional networks (or use the search bar) and click Add. Mobile app: tap the networks dropdown at the top of the Tokens tab → scroll to Additional networks at the bottom → tap the + icon and confirm.
- Switch to that chain and look at the balance. Token autodetection is on by default in MetaMask, and BNB Smart Chain and Polygon are both among the supported networks, so after you switch the USDT balance may show up without further steps.
- If it does not show up, import it manually. In the extension, click the three dots in the tokens section → Manage tokens and search by name. If the search finds nothing, scroll to the bottom and click Add custom token, paste the contract address → Next → Import.
- Get a little gas, then transfer out. A transfer on BSC pays gas in BNB. Send a small amount of BNB to the address first, then send the USDT to where you actually wanted it.
Where the contract address for a manual import comes from: in that chain's block explorer, find your transfer by its transaction hash. The transaction details show which token came in, and clicking it takes you to its contract address. Obtained this way, it is certain to be the token you actually received. Do not import something just because a name search returns a token called USDT. Anyone can give a token any name, and a matching name does not make it the same token.
If the network is not in the list and you have to add a custom network by hand, take the parameters from that chain's official documentation. For BNB Smart Chain Mainnet, for example, the chain ID is 56 and the available RPC endpoints are listed in BNB Chain's official documentation. Do not fill in an RPC URL from a tutorial of unknown origin.
A mix-up between other EVM chains is handled the same way: add the chain the funds are actually on, switch to it and get a little of that chain's gas. Polygon's gas token is now POL. According to Polygon's official announcement, it replaced MATIC from September 4, 2024.
The hard case is crossing to a non-EVM chain, for example between ERC20 and TRC20. According to TRON's developer documentation, a Tron address is shown in wallets as 34 characters starting with T, a different format from an EVM 0x address. Because the formats differ, a withdrawal page normally rejects the mismatch before anything is sent; if a transfer did go out, find out who controls the receiving address (an exchange, your own multi-chain wallet, or someone else) and follow that section.
The address itself was wrong: can the funds be recovered?
Here the address is what went wrong: malware replaced what was on the clipboard, a character was dropped when copying by hand, or someone else's address was copied from the transaction history. The funds are at an address someone else controls, and you do not have the private key. On-chain transfers cannot be reversed, and no support agent can pull back a transfer that is already on-chain.
One thing is still possible: look the address up in a block explorer (Etherscan, BscScan, Tronscan) and see whether it carries an ownership label. If it is labeled as belonging to an exchange, you can contact that exchange, explain what happened, provide the transaction hash and proof of where your funds came from, and ask for its help. This route rarely works out. The exchange has its own compliance process, and the address quite possibly belongs to no exchange at all.
If you ask for help on social media after a transfer goes wrong, accounts calling themselves an on-chain technical team or a hacker recovery service may approach you. They ask for the transaction hash to assess the difficulty, then for an upfront payment, and afterwards keep asking for more under the name of handling fees or miner fees. On-chain transfers cannot be reversed, and nobody can take coins back out of a stranger's address. Treat anyone who approaches you first and wants payment in advance as a scam.
Three habits that prevent the next wrong transfer
Send a small amount first. The first time you send to a new address, send a small amount, confirm that it arrives, and then send the large amount. It costs one extra fee and means a large sum cannot be lost in one go. I suggest doing this every time you send to a new address.
Check the full address character by character. After pasting, compare the whole string from beginning to end, the middle characters included. MetaMask's Help Center page on address poisoning explains why checking only the start and end is not enough: scammers generate a lookalike address with the same first and last characters as one you use often, slip it into your transaction history with a zero-value transfer, and wait for you to copy it from there next time. So do not copy addresses from your transaction history. Verify a frequently used address once, save it in the wallet's address book (called Contacts in MetaMask), and pick it from there afterwards.
Check the network before withdrawing. First confirm on the receiving side which chain it supports, then go back to the withdrawal page and select the same chain. Look at the network name once more on the withdrawal confirmation screen.
If the problem is not a transfer but a suspected leak of your seed phrase or private key, the order of steps is in what to do if a private key or seed phrase leaks.