If you accidentally sent ERC20 USDT to a TRC20 address, or the other way around, Binance Official Site support can help recover most of these cases, and you can also file a ticket through the Official Binance App — though a small number of extreme cases genuinely can't be recovered. If you're setting up on a new device, follow the iOS Install Guide first before doing any of this. Below, we draw a clear line between "recoverable" and "not recoverable," and walk through the actual recovery process.
Binance's recovery service isn't unconditional. Recovery is possible only when the sending network and receiving network use compatible address formats (meaning the same wallet private key can control addresses on both).
The most common "compatible address format, different network" combinations that Binance can recover include:
| Wrong-network scenario | Recoverable | Recovery fee |
|---|---|---|
| ERC20 USDT sent to a BSC address | Yes | ~100-200 USDT |
| BSC BNB sent to an ERC20 address | Yes | ~100-200 USDT |
| Polygon USDC sent to an ERC20 address | Yes | ~100-200 USDT |
| Arbitrum USDT sent to an ERC20 address | Yes | ~100-200 USDT |
| Optimism ETH sent to an ERC20 address | Yes | ~100-200 USDT |
| TRC20 USDT sent to an ERC20 address | No | Not recoverable |
| BTC sent to an ETH address | No | Not recoverable |
| Solana sent to an ETH address | No | Not recoverable |
The underlying logic: if two networks share the same address format (both are 0x-prefixed, 42-character EVM-compatible addresses), the same private key controls both sides, and Binance can move the funds back from the other chain. If the address formats differ (one is 0x, another is T, another is 1...), the private keys aren't interchangeable, and coins sent to the wrong chain are permanently locked.
TRC20 USDT and ERC20 USDT are the two versions of USDT that beginners confuse most often. Their address formats are completely different: TRC20 addresses start with "T" and are 34 characters long, while ERC20 addresses start with "0x" and are 42 characters long.
In theory, if you send ERC20 USDT to a "T"-prefixed address, the transaction will simply be rejected on-chain due to the address format mismatch. So this particular "reverse mistake" usually doesn't even go through, and your funds stay in your original wallet.
But if the mistake happens "between two EVM chains" (both using 0x addresses), the transaction will actually go through on-chain, and the funds end up on the wrong network. This is the scenario that counts as a true "wrong-network deposit."
Steps for submitting a recovery ticket to Binance support:
Step one, log in to your account and go to "Customer Support" → "Submit a Ticket." Step two, select the issue type "Deposit/Withdrawal - Wrong Network Recovery." Step three, fill in the details: the deposited coin, the network it should have used, the network it actually used, the TXID, the amount, and your Binance account email.
Step four, upload screenshots. Recommended screenshots include: the withdrawal confirmation page from the sending wallet, the transaction detail page from a block explorer, and your Binance deposit history page (if there's a failed-deposit record).
Step five, wait for review. Binance support typically responds within 12-72 hours to confirm whether recovery is possible. If it is, they'll send a "recovery quote" stating the fee and expected processing time. Once you agree to the quote and pay the recovery fee, Binance begins processing.
| Step | Average time | User action |
|---|---|---|
| Submit ticket | Instant | Fill form, upload screenshots |
| Initial support review | 12-72 hours | Wait |
| Quote | 2-5 business days | Accept/decline |
| Recovery processing | 5-15 business days | Wait |
| Funds arrive | 1-3 days | Check your Binance wallet |
The entire process usually takes 10-25 business days. Binance will send updates through app notifications and email along the way, and you can check your ticket's progress anytime.
Binance charges recovery fees based on "difficulty tier," not as a percentage of the amount. Common fee tiers are 100, 150, 200, or 500 USDT equivalent.
Factors that determine the fee: first, how many networks are involved in the process; second, how popular the coin is (obscure coins cost more to process); third, whether a multi-signature process or cross-chain bridge is required.
If the amount involved is small (say, you sent 50 USDT but the recovery fee would be 100), it's not worth pursuing — the cost exceeds the benefit. Binance support will proactively flag this in the quote, suggesting you abandon recovery if the amount is below the fee.
Not every submitted ticket ends in successful recovery. Common reasons for failure:
First, the address doesn't belong to Binance. If the "0x address" you mistakenly sent to is a deposit address that Binance itself issued, recovery is possible; if it's someone else's wallet address (outside of Binance's system entirely), Binance has no way to intervene.
Second, the network you sent to isn't one Binance supports. For example, if you sent USDT to a Tezos or Cosmos network, but Binance doesn't accept deposits of USDT on that network, there's no technical path to process it.
Third, the transaction hasn't been confirmed. In rare cases, an on-chain transaction gets stuck in the mempool for days without being included in a block — Binance can't recover a transaction that was never actually confirmed on-chain.
A few habits before you deposit can prevent 99% of wrong-network mistakes.
First, double-check the network type. When you copy an address from Binance's deposit page, Binance displays that network's label at the top ("BNB Smart Chain (BEP20)" or "Ethereum (ERC20)"). When you initiate the transfer from your wallet, confirm both sides show exactly the same network label.
Second, test with a small amount first. The first time you send funds to a new address, send a small test amount of 5-10 USDT first. Only send the full amount after confirming it arrived on-chain. This costs an extra 1-2 USDT in gas fees, but it prevents a catastrophic mistake.
Third, copy and paste instead of typing manually. The letters and numbers in an address can look deceptively similar (like 0 and O, or 1 and l) — a single mistyped character sends your funds to the wrong address entirely. After pasting, double-check that the first 4 and last 4 characters match.
Fourth, pay attention to Memo/Tag fields. Coins like XRP, EOS, and XLM require a Memo in addition to the address. Binance's deposit page will mark "Memo required" below the address — make sure to fill it in when sending.
Q: Is there a minimum amount for Binance's recovery service?
Binance doesn't publish an official minimum, but support usually flags requests under 50 USDT as "below the cost threshold." In theory, recovery requests worth several hundred USDT or more are generally worth submitting.
Q: Will Binance freeze my account during the recovery process?
No, your account won't be frozen. All other operations continue normally, and the recovery ticket is processed separately in the background. However, if the system flags the mistaken deposit as high-risk (for example, coming from a mixer address), the related assets may be temporarily locked.
Q: Can BTC sent to an ETH address be recovered?
No. The BTC and ETH networks are completely independent systems using different cryptographic algorithms, so their private keys aren't interchangeable. Once BTC is sent on-chain to an ETH address, the private key has no ability to control the corresponding address on the ETH chain. The funds are permanently locked.
Q: How long after reporting a wrong-network deposit to Binance support will I get my funds back?
On average, 10-25 business days. Fastest case is about a week; slowest can take up to a month. Cases involving large amounts or multiple chains may take longer. Avoid resubmitting the ticket or repeatedly following up during this time, as it can slow processing down.
Q: Can I refuse to pay the recovery fee and just get Binance to return my funds anyway?
No. Recovery requires Binance's engineers to spend time and effort, and the fee is part of the process. If you decline to pay, Binance will hold onto your mistakenly deposited assets but won't process the recovery — meaning your funds are locked, but not lost.
Q: Does money shown as "pending" in my Binance wallet count as a recovery case?
No. "Pending" simply means the on-chain confirmation is still in progress, or the coin is under maintenance — it'll be credited automatically once confirmation completes or maintenance ends. "Recovery" specifically refers to funds sent to the wrong network or an abnormal address that require manual processing.