Six places withdrawals actually go wrong

These six are ordered by how hard they are to undo, worst first. That is not the same as most frequent, but I think it is the more useful ordering: you are going to read all of them anyway, so start with the expensive ones.

One: the network was wrong

Recoverability: worst.

A withdrawal form has two dropdowns, coin and network. Attention goes almost entirely to the address, and the network field usually gets left at whatever it defaulted to. Meanwhile Ethereum, BNB Smart Chain, Polygon and Arbitrum all use the same forty-character hex string beginning 0x: the system validates the format, and a valid format passes.

The result: the money genuinely arrives at the address you typed, on a chain you did not intend. That address on that chain usually belongs to nobody, or to an exchange that does not support the chain.

Preventing it

• Always read the network list on the receiving side's deposit page first, then pick the same one on the sending side;
• Name whitelist entries with the chain in them — "Binance USDT TRC20", not "Address 1";
• First transfer to any new address is a small one. This is the only thing that reliably catches this class of error.

If it already happened

Find the transaction hash, then work out which chain it landed on and who owns that address. Your own wallet address, and importing the key usually recovers it; an exchange address on a chain they support, and a ticket has a decent chance; a chain they do not support, and the odds are poor but a ticket still costs nothing. The full table of cases is in which chain to withdraw on.

Two: a contract address mistaken for a deposit address

Recoverability: effectively zero.

The typical version: you see a 0x string somewhere and assume it is a deposit address, when it is the token's contract address: the token's own identity on-chain, not anybody's wallet.

Sending to a contract address is like posting money into a room with no door. The overwhelming majority of token contracts have no recovery mechanism, and the issuer cannot help either.

Preventing it

The distinction is clean: deposit addresses come from a deposit page; contract addresses come from token information pages. Anything copied from a price page, a token overview or a block explorer's token page is not for sending money to. Build one habit: the address comes only out of the box on the deposit page with the copy button next to it, and nowhere else.

Three: a memo left blank

The consequences here have an official statement behind them. Binance’s guide to recovering a deposit with a wrong or missing tag/memo says retrieval carries a fee (generally that coin’s transfer fee) and that if what remains after the fee falls below the minimum withdrawal amount, they cannot help you retrieve it (checked 2026-08). Which means the smaller the amount, the more likely this mistake simply becomes a permanent loss.

Recoverability: moderate, via a manual process.

For coins like XRP, XLM and EOS, an exchange's deposit address is shared by every user, with an extra identifier — memo, tag, label, telling them whose money arrived. Leave it out and the funds reach the platform but cannot be attributed to you.

Recoverable, but through a ticket: transaction hash, amount, time, account details, then waiting for someone to attribute it manually. Turnaround in weeks is unremarkable and success is not guaranteed.

Preventing it

If the deposit page shows a memo, carry it across with the address as one action, and confirm the withdrawal form has a field for it. Some interfaces tuck the memo field behind an expander, so it is invisible unless you open it.

Four: the clipboard swapped the address

Recoverability: poor.

This is not fat fingers. It is a real category of malware: something watching the clipboard, and when it sees a crypto address get copied, replacing it with the attacker's. To survive a casual glance, the substitute usually has similar leading and trailing characters.

Which means the habit everyone uses — check the first few and last few: is precisely the habit being targeted.

Preventing it

1. Check the middle, not the ends

   After pasting, compare a section from the middle against the source. An attacker can generate matching ends; they cannot match the whole thing.

2. Use the QR code where offered

   Scanning never touches the clipboard and is immune to this by construction.

3. Put frequent addresses in the whitelist

   Save once, then pick from a list every time afterwards and never copy anything. The lowest-effort long-term answer.

Five: stuck on a minimum

First, whether this category is recoverable at all. Binance’s retrieval application guide contains a rule that is particularly unkind to small amounts: retrieval carries a fee (that coin’s transfer fee), and if what remains after the fee falls below the minimum withdrawal amount, they cannot help you retrieve it (checked 2026-08). Which is to say: on threshold problems, the smaller the amount the less likely it comes back. That is why the fee gets subtracted before you type the number, not afterwards.

Recoverability: good, but tedious.

There are two separate thresholds here and most people only know about one:

The second is the awkward one: the money did leave, the chain accepted it, and the receiving end declines to credit it because it is too small. That normally means a ticket, and some platforms simply do not handle small amounts.

Plus one easily missed piece of arithmetic: the withdrawal fee comes out of the amount you entered. Enter 20, fee is 1, 19 arrives, and if the other side's minimum deposit is 20, you are stuck. When the amount is near a threshold, calculate on the post-deduction figure.

Preventing it

Look at both thresholds, take the larger, then add headroom for the fee. If it really is only crumbs, it may not be worth withdrawing at all — the options are in leftovers below the minimum withdrawal.

Six: the confirmation screen got skipped

Recoverability: depends what you skipped.

After clicking withdraw there is normally a confirmation panel: coin, network, address, amount, fee, amount received. That panel is the last free chance to fix a mistake, and it looks like a formality asking you to click again, so it gets clicked through at a high rate.

A worse variant: to save time, some people disable the email or authenticator confirmation, or develop the habit of typing in codes without reading the message. That verification email usually states the amount and the last characters of the destination: it exists to be read, not to be transcribed.

Preventing it

Give yourself one hard rule: say the network field out loud, every time.

Not look at it, say it. This sounds ridiculous, but it forcibly drags attention off "is the address right" and onto the field that actually fails. I do this, because being more careful does not help — you are already careful, the care just points the wrong way. One exception worth stating: if this is an address you have sent to successfully before and you picked it out of the whitelist, you can skip the step, because the chain is pinned to the whitelist entry and you cannot change it by hand. The rule exists for new addresses.

A few that did not make the top six

Sitting on the form until it expires

Some withdrawal forms time out. Take a phone call and come back and it may have lapsed. Expiry itself is harmless; the danger is that some people then refill it quickly and skim the checks: the second pass is often worse than the first, because it feels like you already checked. Treat a refill as a fresh attempt.

Several platforms open at once, wrong address copied

During a migration the browser typically has four or five tabs open. Copy an address at A, switch to B, paste: one wrong tab switch and you have pasted a different platform's address. The fix is handling one coin and one chain at a time, closing it, then opening the next.

Using an address from someone's screenshot

Ask in a group how to withdraw something and someone posts a screenshot of their own screen, address included. Convenient, and it means sending money to a stranger. A deposit address comes only from your own account's deposit page, always. This sounds too basic to state, and it happens every year, usually for meaningful amounts.

Confusing withdrawal with internal transfer

Some platforms support transfers between their own users by email or ID — off-chain, usually free. Good feature, but check which one you are on: an internal transfer identifier and an on-chain address are unrelated things. Systems generally catch the mismatch, but some interfaces make it easy to conflate them.

Why "just be careful" does not work

Nearly every one of the above comes with standard advice to check carefully. If care were sufficient, these would not keep happening to experienced people every year.

The reason is that attention has a default destination. Transferring money, it goes to two places: the amount and the address. Those are the most visual, the most obviously about money. The field that actually kills you: the network: reads like a settings widget rather than something financial, so the brain files it as background.

So the effective interventions are not "be more careful" but changes to the process that route attention through the dangerous spot:

• Put the chain name in the whitelist entry. Choosing the address then makes you read the chain, with no willpower required;
• Say the network aloud on the confirmation screen. Turning a visual act into a verbal one genuinely recruits attention;
• Small first, large second. Converts an irreversible error into the price of one fee, and is the only defence that does not depend on your state at the time.

The third matters most, because the first two assume you are alert, unhurried and not doing three things at once. Accidents concentrate precisely when you are none of those.

And: do not operate inside an emotion

Notice just published, price falling, group chat scrolling — when those coincide you are at your highest error rate. If your hands are unsteady, close the tab and do something else. Go and check which day the notice says withdrawals stop: most of the time you will find there is more room than it feels like, and no single transfer is worth completing in a panic.

The first hour after something goes wrong

If one of these did just happen, what you do in the first hour determines whether there is any room left.

1. Find the hash

   It is in the withdrawal history. With a hash there is an objective anchor; without one, every request for help starts from nothing.

2. Establish where the money went, using a block explorer

   Status, which chain, which destination address. All three are things you can determine yourself without waiting.

3. Decide whether this is recoverable

   Sent to an address you control, even on the wrong chain, and there is usually a route. To an exchange over a chain they support, a ticket has a chance. To a contract address, essentially not.

4. Ask for help only through official channels

   The receiving platform's ticket system, or the sending platform's support. Do not post a hash publicly asking for help: that publishes your address and its balance.

The six compressed into an action list

If you remember one thing, remember this: the first transfer to any new address is a small one that just clears the minimum. It covers five of the six above by itself.

The full sequence:

1. Open the deposit page at the receiving end; copy the address and memo if there is one; note the network name and the minimum deposit;
2. Back on the sending side, match coin and network, paste the address, check a section from the middle rather than the ends;
3. Set the amount so that after the fee it still clears the other side's threshold;
4. On the confirmation screen, say the network field out loud;
5. Read the second-factor email or prompt, the amount and address are in it;
6. Small transfer lands and reconciles, then send the rest.

There is a tickable version of this in eight checks before you hit withdraw, which writes a short summary you can paste into your own records once everything is ticked.