Moving crypto out of an exchange, or in from somewhere else, looks like nothing: copy an address, tap confirm a couple of times. But when one step goes wrong, it's not like ordering the wrong takeout. On-chain transfers are irreversible, and there's no support agent who can hit undo for you. People have sent a few thousand dollars of USDT on the wrong network and watched the other side never receive it. Others had malware quietly change one character of the address they pasted, and the money walked straight into a stranger's wallet.
This is the master list. We lay out every mistake that can lose your crypto or strand it, and we run each one through the same structure: why it happens, where the money actually is right now, whether you can recover it, how to try, and how to dodge it for good next time. Read it top to bottom to get the full picture, or jump straight to the one that's happening to you.
What's in here
- First, a map of where crypto can go missing
- Mistake 1: wrong network, the other side never gets it
- Mistake 2: wrong address, or a clipboard swap
- Mistake 3: a memo/tag was needed and you left it off
- Mistake 4: below the minimum deposit, so it never credits
- Mistake 5: not enough confirmations, and you assume it's lost
- Mistake 6: withdrawal stuck "under review"
- Mistake 7: mixing up internal transfers and on-chain sends
- A pre-withdrawal checklist
- FAQ
First, a map of where crypto can go missing
Before we pick the mistakes apart one at a time, look at the whole thing. For a deposit or withdrawal to go through cleanly, several conditions all have to hold at once, and if any one of them slips, the money can get stuck or lost. Lay those conditions out and you've got a troubleshooting map:
- Right network — the sending and receiving ends have to be on the same chain, or the other side simply never gets it.
- Right address — not one character off, and watch out for a paste getting swapped out from under you.
- Right tag — some coins (XRP, EOS and a few others) need a memo or tag attached when you send to an exchange, so it knows whose money it is.
- Enough to count — go below the platform's minimum deposit and it may not credit at all.
- Enough confirmations — the chain has to rack up enough block confirmations before the exchange treats it as "arrived."
- Not held by risk controls — on the withdrawal side, a security review can put it on pause.
Keep those six in your head and, when something goes sideways, you can work down the list like a checklist at airport security instead of just panicking. Here they are, one at a time.
Mistake 1: wrong network, the other side never gets it
Why it happens. That "select network" dropdown on the withdrawal screen is the number-one source of lost-crypto stories. One coin, say USDT, runs on several separate chains: Tron, Ethereum, BSC, Solana and more. Pick BSC on your end and send to a wallet that only listens for Ethereum mainnet, and the money goes down a pipe the other side has no connection to. Plenty of people think "it's all USDT anyway" and that's exactly where they come unstuck.
Where the money is now. Two situations. In one, you sent to an exchange or to your own wallet where you hold the keys, and just picked a network it "also supports but you weren't expecting" — that crypto is somewhere you can still reach. In the other, it went to an address that doesn't exist or isn't supported on that network, and that's a lot messier.
Whether you can recover it, and how. It all comes down to the receiving side. If the exchange you sent to happens to support the network you picked by mistake, you can usually find it in its deposit history or claim it through support. If it went to your own wallet and you hold the same seed phrase or private key on that chain, you may be able to switch the wallet to that network, or import that chain, and see and move the funds. But if it went to a contract or an unsupported address where nobody holds the keys, on-chain is irreversible and it's essentially gone. For the case-by-case call and the appeal routes, see how to recover USDT sent on the wrong chain.
"Can I recover crypto sent on the wrong chain" has no standard answer. It depends entirely on where the money went, whether the receiving side supports that chain, and what the platform's policy is. Don't trust anyone who says "it can definitely be recovered." Anything involving your funds goes by Binance's own self-service recovery and support replies. All we do here is help you figure out which way to go.
How to prevent it. Lock in the order: confirm which networks the receiving side supports first, then pick a cheap one from the networks it does support. How to pick a cheap one without losing crypto is the whole point of the complete guide to choosing a Binance withdrawal network. When you're unsure, the network picker can point you in a direction.
Mistake 2: wrong address, or a clipboard swap
Why it happens. A blockchain address is a long, patternless string of characters, and no human eye can really memorize or proofread it character by character. Errors come from two places. One is your own doing: typing it by hand, a bad paste, pasting last time's old address. The other is nastier — your computer or phone has malware, you copy address A, and what pastes in is quietly swapped to the attacker's address B, with the first and last few characters made to look similar on purpose so you won't catch it at a glance. That trick is called clipboard hijacking.
Where the money is now. If the address is validly formatted but not the one you meant, the money has genuinely landed in that address's owner's hands. If it's gibberish with no corresponding private key (and it somehow slipped past the format check, which is rare), it's basically gone into a black hole.
Whether you can recover it, and how. This is the hardest kind to recover. Send to a valid but wrong address, and once it confirms on-chain it's irreversible. Your only hope is that the address happens to belong to someone or some exchange you can reach — if it's an exchange address and they're willing to help, there's a slim chance of coordinating through an appeal; if it's a private wallet, all you can do is hope the owner sends it back, and nothing can force them. So the point of this mistake isn't the fix, it's the prevention. For how to handle the incident in detail, see your deposit address got changed? spotting clipboard hijacking.
1) Always copy and paste, never type by hand. 2) After pasting, check the first 5-6 and last 5-6 characters one by one, and glance at the overall length too — this step is your last line of defense against a clipboard swap. 3) If you can use an address book or whitelist, save your regular addresses there and pick from the list, so you're not copying fresh every time. Want to check whether an address is even validly formatted first? Use the address validator (it checks the format only, not on-chain balances).
How to prevent it. On top of those three moves, a small test transfer before a big one earns its keep here — send a few dollars over, confirm it landed at the address you meant, then send the rest. That bit of extra fee is insurance on the whole amount.
Mistake 3: a memo/tag was needed and you left it off
Why it happens. Some coins — XRP, XLM, EOS, ATOM and others — need an extra label called a memo or tag (some call it a note or comment) filled in alongside the address when you send to an exchange. The reason: for these coins, the exchange often collects everyone's deposits at one shared address, and that label is how it tells whose deposit is whose. Leave it off and the system doesn't know whose account to credit. First-timers with these coins are the ones who trip, because there's no such field when you send USDT and the like, so you're on autopilot.
Where the money is now. The good news: a missing memo usually doesn't lose the money, it strands it. The funds reached the exchange's shared address, they just don't have a label, so the platform holds them in an unclaimed or unmatched state, waiting for you to claim them. They didn't vanish, they're just not credited to your account yet.
Whether you can recover it, and how. This kind you'll probably get back. Most exchanges have a self-service recovery page or a support ticket: you submit the transaction hash, the coin, the amount and your account UID, and once they verify it they credit it to your account. The process, the wait, and whether there's a fee depend on each platform's policy. For which coins need it and the exact appeal steps after you've missed it, see what to do when you forget the XRP/EOS memo. Not sure whether a given coin needs one? Check first with the memo/tag lookup.
How to prevent it. Before sending any coin that "carries a tag," get in the habit of copying both the address and the memo/tag off the receiving side's deposit page. Don't drop either, and don't swap them (putting the address in the memo field is a common one).
Mistake 4: below the minimum deposit, so it never credits
Why it happens. Platforms usually set a minimum deposit per coin and per network, and a transfer below that amount may not auto-credit. Someone trying to "run a small one" sends a tiny test amount, which ends up stuck for being under the threshold — a problem they invented for themselves.
Where the money is now. The on-chain transfer itself went through — the money reached the exchange's address, it just didn't trip the auto-credit logic. It's on the platform's side, but it's not in your available balance.
Whether you can recover it, and how. Most of the time you can get it credited through support or a self-service appeal, but it's usually a hassle, and some platforms are stricter about small below-minimum deposits. Whether it can be credited, and whether there's a fee, goes by the platform's rules at the time.
Testing with a small amount is a good habit, but "small" isn't "tiny." The test amount has to be above that network's minimum deposit, or the test itself gets stuck. What the minimum actually is goes by whatever Binance's deposit page shows for that coin and network at the time — don't copy a number from somewhere else.
How to prevent it. Before you send, check the minimum deposit for that coin and network on the receiving side's page, and set your test amount a notch above it.
Mistake 5: not enough confirmations, and you assume it's lost
Why it happens. This isn't really a mistake, it's a misunderstanding. Once an on-chain transfer is sent, it has to wait for a number of block "confirmations" before the exchange decides it's arrived and credits it. Different networks require different numbers, and if the chain is congested, the wait gets longer. The impatient look after fifteen minutes, see nothing in their account, assume the money's gone, and start fiddling or even resubmitting — which is how you turn a non-problem into a real one.
Where the money is now. On its way. Take the transaction hash to the right block explorer (Etherscan for Ethereum, Tronscan for Tron, and so on) and you'll see it racking up confirmations, plain as day.
Whether you can recover it, and how. Nothing to recover — just wait. As long as the explorer shows the transaction as valid and the confirmations climbing, it auto-credits once it hits the required count. The real job is to not panic and not repeat the action.
How to prevent it. Before you send, have a rough sense of how many confirmations that network needs and how long that takes. Each chain's confirmation requirement and rough feel for the wait (qualitative — the explorer is the real-time source) is in the confirmations reference. In short: Ethereum produces a block roughly every dozen or so seconds, Tron blocks come fast — protocol-level facts like that are worth knowing, but the exact confirmation threshold and current speed go by what Binance's page and the block explorer show.
This is our referral link. Signing up through it gets you the fee discount; we earn a referral commission, and it doesn't cost you extra or change your fees. Check that Binance is available where you live first — if your region is restricted, don't sign up, and don't use a VPN or fake details to get around it.
Mistake 6: withdrawal stuck "under review"
Why it happens. The withdrawal side has its own trap, except it's usually not lost crypto, it's "held for a bit." When the system thinks a withdrawal looks risky — you just switched to a new device, just changed your password, you're pulling out far more than usual, or the pattern is off from your normal behavior — it puts it into a security review and pauses to verify. That's the platform protecting your account, not an error.
Where the money is now. Still in your account, just frozen in "under review," not actually broadcast on-chain.
Whether you can recover it, and how. Most of the time it clears if you're patient. How long the review takes, which actions trigger risk controls, and when you should reach out to support is its own piece — see how long a withdrawal "under review" takes, we won't rehash it here. The key point: don't keep resubmitting just because it didn't go through instantly — that only makes the risk controls more cautious.
How to prevent it. After you change a password, link a new device, or reset a security setting, there's usually a temporary hold on withdrawals, and that's normal. Before a big withdrawal, run a small one through first and add your regular receiving addresses to the whitelist — both cut the odds of getting flagged. For the rough limit tiers, see the withdrawal limits lookup.
Mistake 7: mixing up internal transfers and on-chain sends
Why it happens. To move crypto between two accounts on the same exchange, some platforms offer an "internal transfer" — it runs on the platform's own books, never touches the chain, so it's often free, instant, and doesn't ask you to pick a network. The trouble is people confuse it with a regular on-chain withdrawal: either they could have used an internal transfer but sent on-chain and overpaid the fee, or they assumed the other side supported internal transfers, used an on-chain address, and got the network wrong anyway.
Where the money is now. If you used an internal transfer and got the recipient's account identifier right, it's basically instant and there's nothing lost. If you thought it was internal but it actually went on-chain, you're back to the calls in Mistake 1 (network) and Mistake 2 (address).
Whether you can recover it, and how. An internal transfer sent to the wrong recipient is handled by the platform's rules and there's usually a trail; once it's on-chain, judge whether it's recoverable by the on-chain rules. The key is to first work out which one you actually used.
How to prevent it. Before you send, be clear on it: is the recipient on the same exchange, and are you using the platform's internal identifier or an on-chain address? The way you fill them in, the fees, and whether they can be reversed are completely different, so don't mix them up.
A pre-withdrawal checklist
Squeeze those seven down into a checklist of actions. Spend a minute running through it before every withdrawal and you'll head off the vast majority of accidents before they happen. One aside: if you don't have a Binance account yet and want somewhere to run this whole flow, you can sign up for Binance with our invite code BNB986 — entering the code at signup also gets you up to 20% off trading fees* (whatever Binance's page shows).
| Check | What to do | If you skip it |
|---|---|---|
| Network matches both ends | See which chains the receiving side supports, then pick from those | Other side never gets it, crypto may be lost |
| Address checked character by character | Copy and paste, verify the first and last 5-6, guard against clipboard swaps | Money goes to a stranger, basically unrecoverable |
| Memo/tag | For tagged coins, copy both the address and memo, don't swap them | Stranded as unclaimed, needs an appeal |
| Clears the minimum | Test amount above that network's minimum deposit | Doesn't auto-credit |
| Expected confirmation time | Know roughly how many confirmations to wait for, don't repeat the action | Assume it's lost, repeat and go wrong |
| Small amount first | New address or new network, send a few dollars to scout it | Puts the whole amount at risk in one shot |
Need to work through a problem step by step? Try the deposit troubleshooter. Not sure which network this transfer should take? Let the network picker point you in a direction. Both tools run entirely in your browser and don't collect the addresses you type in.
The moment you think you sent it wrong or it didn't arrive, stop. Don't keep resending, and don't fire off another transfer. Step one is to get the transaction hash and check it on the right block explorer: did it succeed on-chain? Which address did it reach? Enough confirmations yet? Pin down the facts, then decide whether to wait, claim, or file an official appeal. Repeating actions in a panic usually stacks one small problem into several.
FAQ
My deposit hasn't shown up in ages. Is it gone?
Usually it's not gone, it's stuck or still confirming. Take the transaction hash to a block explorer: if it hasn't hit enough confirmations, wait. If it's confirmed but not credited, the usual culprits are the wrong network, an amount below the minimum deposit, or a missing memo. Work through those, and if it's truly stuck, use Binance's self-service recovery. Whether you get it back depends on the case, and nothing's guaranteed.
I typed the wrong withdrawal address. Can I get it back?
Depends where it went. To another valid address whose keys someone else controls, you can only ask them to send it back — there's no way to force it. To an address nobody holds the keys to, it's irreversible on-chain and almost certainly gone. So before a big transfer, always test with a small amount and check the start and end character by character.
Can I recover coins I sent without the memo/tag?
Sent to a shared exchange address, the memo is the label that says who it belongs to, and leaving it off usually strands it as unclaimed rather than losing it. Most platforms have self-service recovery or a support appeal, and you'll need the transaction hash and other proof. Whether it comes back, and how long it takes, depends on the platform's policy. Follow the official route, no guarantee.
How do I stop making these mistakes in the first place?
Three things: the network has to match on both ends, so check which chain the receiving side supports; don't type the address, paste it and check the start and end character by character, and watch for clipboard swaps; before a big transfer, send a few dollars to scout it and wait for it to arrive before sending the rest. There's no undo button on-chain.
Losing or stranding crypto comes down to a handful of holes: network, address, memo, minimum, confirmations, risk controls, and internal vs on-chain. Run the checklist before every action, and test with a small amount before a big one. If it goes wrong, check the transaction hash first and don't repeat the action. Recovery isn't guaranteed — Binance's official appeal is what counts.
Read next
The complete guide to choosing a Binance withdrawal network How to recover USDT sent on the wrong chain (by scenario) What to do when you forget the XRP/EOS memo Your deposit address got changed? Spotting clipboard hijackingSources: Binance Help Center, Tronscan, Etherscan, ethereum.org. Fees, confirmation counts and limits are live figures — go by whatever the platforms and block explorers show at the time; whether recovery is possible depends on the case and isn't guaranteed.