Whether a wrong deposit comes back depends on whose address the coins finally landed on. If they reached an address Binance controls — a missing memo, a token Binance doesn't list, an EVM network it doesn't support — there's usually an official request route, but it runs in working days, can cost a fee, and often ends with the coins refunded to the address they came from, not credited to you. An old deposit address of your own is the easy case: no request needed, just [One Click Arrival] on the Transaction History page. If they already left Binance for a wrong withdrawal address, went to an address that isn't Binance's, or the deposit was below the minimum, Binance's help center says it can't assist or can't retrieve them. That's the help center as we read it in November 2026; fees and times move, and the live page wins.
Below, a table matches each mistake to Binance's published wait, fee and outcome. Then the seven mistakes one at a time: where the coins are sitting, who can still move them, and how far your own actions reach. The last section covers what the self-service recovery form accepts and the reasons Binance gives for turning requests down.
What's in here
- Where a transfer can go wrong
- What Binance says it can recover, how long, what it costs
- Mistake 1: wrong network
- Mistake 2: wrong address, or a clipboard swap
- Mistake 3: memo/tag left off
- Mistake 4: below the minimum, or an old deposit address
- Mistake 5: not enough confirmations yet
- Mistake 6: withdrawal stuck "under review"
- Mistake 7: internal transfer vs on-chain send
- A pre-withdrawal checklist
- Before you file a recovery request
Where a transfer can go wrong
A deposit or withdrawal only lands cleanly when six things hold at once. Each one that slips maps to a mistake further down:
- Right network — both ends on the same chain, or the other side never sees it.
- Right address — not one character off, and not quietly swapped during the paste.
- Right tag — coins such as XRP or TON need a memo or tag when sent to an exchange, so it knows whose money it is.
- Enough to count — below the platform's minimum deposit, it may never credit.
- Enough confirmations — the exchange waits for a set number of blocks before it calls the deposit "arrived."
- Not held by risk checks — on the withdrawal side, a security review can pause things before anything is sent.
The first four decide where the coins end up. The last two only decide when. That split matters more than anything else in this guide, because only coins sitting at a Binance-controlled address have a Binance recovery form behind them.
What Binance says it can recover, how long, what it costs
Most rows come from Binance's English page "How to Retrieve a Deposit That Hasn't Arrived With Self-Service Recovery?" (updated 2026-05-29). The old-address row and the three "no" rows come from the FAQ on incorrect deposits (updated 2025-12-05) and the same self-service page. In the first eight rows the first-column labels are Binance's own; the last four are our paraphrase of the help-center wording.
| Mistake | Where you apply | ETA | Fee | Outcome |
|---|---|---|---|---|
| Deposit without or wrong MEMO | Self-service recovery | 7 working days | Network withdrawal fee | Refund, only to the source address |
| Deposit old/delisted tokens | Self-service recovery | 5 working days | Network withdrawal fee | Refund |
| Deposit not credited | Self-service recovery | 5 working days | Free | Credit to your account |
| Deposit to hot wallet | Self-service recovery | 5 working days | Free | Refund |
| Smart retrieval | [Retrieve Now] button in your recent deposit record | 7 working days (recovery page) / "up to 14 working days" (incorrect-deposits FAQ) | 1 USDT flat | Refund |
| Deposit unlisted tokens on supported networks | Self-service recovery | 30 working days | 20 USDT | Refund |
| Deposit listed or unlisted tokens on unsupported EVM networks | Self-service recovery | 30 working days | 20 USDT | Refund |
| Deposit restricted | Self-service recovery | 14 working days | Network withdrawal fee | Refund |
| Deposit to an old or degraded Binance address | [One Click Arrival] on the Transaction History page | Not stated | Not stated | Credited once you click; "will not be credited automatically" |
| Wrong withdrawal address, funds already withdrawn | — | — | — | "we are unable to assist you" |
| Sent to an address that doesn't belong to Binance | — | — | — | No further assistance; contact the address owner or its platform |
| Deposit below the minimum deposit amount | — | — | — | "cannot be retrieved" |
Snapshot from Binance's help center, checked 2026-11-13. Binance says "Fees are subject to change and not fixed" and "successful recovery of funds is not guaranteed, and not all deposits can be retrieved." Go by the live page and the figure the form shows you.
Three details in the fine print change how long you actually wait and what you pay. The clock starts late: "request processing starts after we have received the required information and fee, not at the submission date." The fee is conditional: "Fees are only collected if the retrieval is successful." And for the missing-memo case the FAQ spells out where the money goes — "it will only be returned to the source address," and "Binance doesn't support modification of refund addresses."
The smart-retrieval row is printed two ways: Binance's two pages give different times. We list both instead of picking one. Whichever the retrieval screen shows when you click is the figure that applies to you.
Another tension worth knowing about: for wrong addresses and unlisted tokens, the FAQ's general line is "Binance generally does not offer a token/coin recovery service," with the caveat that Binance "may, solely at our discretion, assist you" and "successful token recovery is not guaranteed." Yet the self-service table lists a paid 30-day route for unlisted tokens. Our reading: you can apply, and whether it's accepted is Binance's call. Don't budget on that money coming back.
One more trap: Binance.US runs a separate help center and its own recovery tool. If your account is on Binance.US, its pages set the rules, and nothing in this table carries over.
Mistake 1: wrong network
Why it happens. The "select network" dropdown on the withdrawal screen is where most lost-coin stories start. USDT alone runs on Tron, Ethereum, BSC, Solana and more, and they don't talk to each other. Pick BSC on your end and send to a wallet that only watches Ethereum mainnet, and the coins go down a pipe the other side isn't connected to. "It's all USDT anyway" is the thought right before it goes wrong.
Where the coins are. One of two places. Either at an exchange or a wallet whose keys you hold, just on a network you didn't expect it to accept — reachable. Or at an address that doesn't exist or isn't supported on that network, which is much messier.
Who can still move them. The receiving side, and only the receiving side. If you were depositing into Binance on an EVM network Binance doesn't support for that token, that's the "unsupported EVM networks" row in the table: about 30 working days, 20 USDT, refunded. If you withdrew from Binance to another exchange on the wrong chain, Binance's table doesn't apply; that exchange's recovery rules do. If it went to your own wallet and you hold the same seed phrase on that chain, switching the wallet to that network or importing the chain may let you see and move it. A contract or unsupported address that nobody holds keys for is, on-chain, a dead end. Scenario-by-scenario calls are in how to recover USDT sent on the wrong chain.
Anyone who promises "it can definitely be recovered" — especially someone who contacts you first — is not Binance. Anything involving your funds runs through Binance's own self-service form and support. This guide only helps you work out which way to go.
How to prevent it. Order matters: find out which networks the receiving side accepts first, then pick the cheap one from that list. The method is in the complete guide to choosing a Binance withdrawal network, and the network picker gives you a starting point when unsure.
Mistake 2: wrong address, or a clipboard swap
Why it happens. An address is a long patternless string nobody can proofread by eye. Errors come from two directions. Your own: typing by hand, a partial paste, last month's address still on the clipboard. Or malware: you copy address A, and what pastes is the attacker's address B, built so the first and last few characters look alike. That's clipboard hijacking.
Where the coins are. With a valid but wrong address, they're with whoever owns that address. A string with no private key behind it that still slipped past the format check is rare, and the coins in it are as good as burned.
Who can still move them. Not Binance, once they've left. Its self-service page is blunt: "If you entered the wrong withdrawal address and your funds have already been withdrawn from your Binance account, we are unable to assist you." For an address that doesn't belong to Binance, the incorrect-deposits FAQ says Binance is "unable to provide any further assistance" and suggests contacting the relevant parties — the address owner, or the exchange or platform the address belongs to. With a private wallet, the owner sending it back is the whole plan, and nothing can force them. Which makes this mistake about prevention more than repair. The incident walkthrough is in your deposit address got changed? spotting clipboard hijacking.
Always copy and paste; never type. After pasting, compare the first 5-6 and last 5-6 characters and glance at the length — that's the last chance to catch a swap. If you can, keep regular addresses in an address book or whitelist and pick from it. To check whether an address is even valid in format, use the address validator (format only, no on-chain lookup).
How to prevent it. Send a few dollars first, confirm they reached the address you meant, then send the rest. The extra fee is cheap insurance on the full amount.
Mistake 3: memo/tag left off
Why it happens. XRP, XLM, ATOM, TON and a few others need a memo or tag (sometimes "note" or "comment") alongside the address when sent to an exchange. The exchange often collects everyone's deposits for these coins at one shared address, and the label is how it tells them apart. People trip on their first one because USDT never asked for it.
Where the coins are. At Binance's shared address, unlabelled. Binance's FAQ: "If you forgot to use or used a wrong tag, memo, or payment ID (e.g., TON, XLM, XRP, etc), your deposit won't be credited to your Binance account." Stranded, not lost.
Who can still move them. Binance, through the self-service form. Its table puts a missing or wrong memo at about 7 working days, with the network withdrawal fee charged, and the outcome is a refund rather than a credit: the FAQ says the asset "will only be returned to the source address," with no option to change the refund address. That last part matters if you sent from another exchange: the coins go back to that exchange's address, and you claim them there. Other exchanges have their own memo rules. Which coins need a memo, and the claim steps, are in what to do when you forget the XRP/TON memo; to check a coin before sending, use the memo/tag lookup.
How to prevent it. For any tagged coin, copy both the address and the memo from the receiving deposit page. Putting the address into the memo field is the classic swap.
Mistake 4: below the minimum, or an old deposit address
Why it happens. Each coin and network usually has a minimum deposit. Someone running a cautious test sends a tiny amount, and the test itself gets stuck under the threshold.
Where the coins are. The on-chain transfer succeeded; the coins reached Binance's address and simply didn't trigger crediting.
Who can still move them. Here, nobody. Binance's FAQ: "Deposits that do not meet the minimum deposit amount cannot be retrieved." There's no row for it in the recovery table, which is why we'd rather you check the number than test with spare change. The specifics are in minimum deposit amounts.
A case that looks similar but ends better: coins sent to an old or degraded Binance deposit address — say one saved months ago. Binance says those funds "will not be credited automatically," and the fix is a button rather than a ticket: [One Click Arrival] on the Transaction History page.
Small isn't the same as tiny. Make the test amount a notch above that network's minimum deposit, read off Binance's deposit page for that coin and network at the time, not copied from somewhere else.
Mistake 5: not enough confirmations yet
Why it happens. This one is a misunderstanding. After sending, the transfer needs a number of block confirmations before the exchange credits it; the count differs by network and congestion stretches the wait. Fifteen minutes in, nothing shows, and the resubmitting starts — which is how a non-problem becomes a real one.
Where the coins are. In transit. Put the transaction hash into the right block explorer (Etherscan for Ethereum, Tronscan for Tron) and you'll see the confirmations climbing.
Who can still move them. Nobody needs to. While the explorer shows the transaction valid and confirming, it credits on its own once the count is reached. Binance's self-service recovery is meant for deposits still missing an hour after they were sent, so there's no point filing before then (more in the last section).
How to prevent it. Know roughly how many confirmations the network needs before you send. The confirmations reference has each chain's requirement as a rough guide. Ethereum produces a block every dozen or so seconds and Tron is faster; the exact threshold and current speed are whatever Binance's page and the explorer show.
Mistake 6: withdrawal stuck "under review"
Why it happens. A new device, a fresh password change, an unusually large amount — Binance's risk checks pause the withdrawal before it's broadcast.
Where the coins are. Still in your account. Nothing has touched the chain, so there's no hash to look up.
Who can still move them. Only Binance's risk system. After certain security actions such as a password change, Binance suspends withdrawals for 24 to 48 hours, and its anti-scam cool-downs "typically last up to 24 hours" (both per Binance's help center, checked November 2026). The full table of messages and waits is in how long a withdrawal "under review" takes. Resubmitting doesn't help.
How to prevent it. Let a security-reset hold run out before moving anything large, send a small amount first, and whitelist regular addresses. Rough limit tiers are in the withdrawal limits lookup.
Mistake 7: internal transfer vs on-chain send
Why it happens. Between two Binance accounts there are two ways to move coins, and they behave nothing alike. Binance's page on internal transfers: "Internal transfers have zero transaction fees and transfers are credited immediately." The condition sits in the next lines: "Fee exemption and instant fund arrivals are only applicable when the recipient's address belongs to a Binance account," and if you choose [On-chain withdrawal] instead, "you will have to pay a network fee." People mix them up both ways — paying a network fee for a send that could have been internal, or assuming the recipient was on Binance when they weren't, which turns it into an ordinary on-chain withdrawal with Mistakes 1 and 2 back in play.
Where the coins are. An internal transfer to the right Binance account has already arrived. One that went on-chain is wherever the chain put it.
Who can still move them. Check the record first. An internal transfer creates no TxID: the TxID field shows [Internal], and you get an internal transfer ID instead. That ID, not a block explorer, is what you hand to Binance support if something is off. If there's a real TxID, it went on-chain and the on-chain rules above apply. More on reading that field in find the TxID, then read the explorer properly.
How to prevent it. Before sending, settle one question: is the recipient's address a Binance account? Yes means free and instant; no means network fee, network choice and an irreversible send.
A pre-withdrawal checklist
The seven mistakes, squeezed into a minute's worth of checks before each withdrawal:
| 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; recovery depends on the receiver |
| Address checked | Copy and paste, verify the first and last 5-6, guard against clipboard swaps | Coins go to a stranger; Binance can't help once withdrawn |
| Memo/tag | For tagged coins, copy both address and memo, don't swap them | Not credited; recovery request, refund to source address |
| Clears the minimum | Test amount above that network's minimum deposit | Can't be retrieved |
| Expected confirmation time | Know roughly how many confirmations to wait for; don't repeat the send | False alarm turns into a real mistake |
| Internal or on-chain | Confirm the recipient's address belongs to a Binance account | Network fee paid, or an on-chain send you didn't intend |
To work through a missing deposit step by step, use the deposit troubleshooter. For choosing a withdrawal network, use the network picker. Both tools run in your browser and don't collect the addresses you type.
Before you file a recovery request
Stop sending first. Get the transaction hash and check it on the right explorer: did it succeed, which address did it reach, how many confirmations? That answers whether you're even eligible, because Binance's self-service page sets these conditions:
- "You can only request self-service recovery for crypto deposited into your Binance account." Requests made on behalf of others are on the not-accepted list.
- "We cannot assist you if the transaction is marked as "unconfirmed" or "failed"." An unconfirmed transfer has to finish on-chain first.
- Binance's wording: if "your funds still haven't arrived after 1 hour, please fill in the self-service recovery application." Before that hour, we'd keep waiting.
- Withdrawals to a wrong address are excluded, as covered in Mistake 2.
Binance also lists why requests get rejected: "Incorrect TxID/TxHash or address", "Mismatched deposit amount", "Transaction already arrived", "Unconfirmed or unfound transaction", and "Zero transaction amount." The first two are typing problems, so copy the TxID and address straight from the explorer and the deposit record, and enter the amount exactly as the chain shows it. "Transaction already arrived" is worth a look at your balance and deposit history before you file. Binance may also ask you to "upload a video to prove the authenticity of the deposit."
Coins still at a Binance address usually have a recovery route, though a slow one that often ends in a refund to the source address. Coins already withdrawn to a wrong address, sent to a non-Binance address, or deposited below the minimum don't. Check the hash before anything else, and don't resend.
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/TON memo Your deposit address got changed? Spotting clipboard hijackingSources: Binance: self-service recovery for deposits that haven't arrived, Binance: FAQ on incorrect deposits, Binance: internal transfers to another Binance account (all checked 2026-11-13), Tronscan, Etherscan, ethereum.org. Recovery times, fees, confirmation counts and limits change; go by what Binance and the block explorers show at the time. Recovery depends on the case and isn't guaranteed.
