The explorer says success. Receiving address, amount, timestamp — all of it checks out. Your deposit history, meanwhile, shows nothing at all, and when you search the asset list for that token it isn't there. The exchange never listed it.
This piece covers that one case: the token you sent is not listed on the exchange, or isn't on the network list its deposit page gave you. Every other flavour of "not credited" has its own home. Confirmations still climbing is a normal wait — see how long a deposit takes. Confirmations long past the threshold with nothing credited is confirmations done but not credited. Never mined at all is stuck at pending. A tag chain without the tag is the memo you forgot. Under the floor is minimum deposit amounts. And if the address wasn't the exchange's at all, that's sent to the wrong address.
What's in this guide
Three cases that look identical and end very differently
"Unsupported" gets stretched across three different problems. What you see in the deposit history is near enough the same in all three, but the route out and the odds are not. Work out which one you're in first:
| Case | How to spot it | Where the coins sit | Likely outcome |
|---|---|---|---|
| 1. Token never listed | Search the deposit page and the token isn't there; you used an address issued for a different token on the same chain | At the exchange's receiving address on that chain, with no ledger entry | A request channel exists — fee, queue, no guarantee |
| 2. Network not enabled | The token is listed, but the network you used isn't in its list | Depends which chain and which address it actually reached | Common between EVM chains and usually requestable; across different address formats the send rarely goes through at all |
| 3. Both supported, wrong one picked | Token and network are both on the list; you chose the wrong network at the sending end | The same address, on a different chain | The most common and the most recoverable — see wrong-network recovery |
Case 3 is out of scope here, but it's worth saying why it's the easy one: both the token and the chain are already switched on at the exchange's end, so someone has walked that path before. Cases 1 and 2 are harder precisely because nothing in the crediting logic was ever built for that token or that chain. Sorting them out means a human fishing the funds out of a wallet and sending them back by hand — which is the whole reason recovery carries a fee and is measured in working days. Binance's own page says as much: reviewing, consolidating and safely returning unlisted tokens takes significant resources to manage.
One distinction that trips people up: delisted and never listed are not the same thing. A delisted token used to have a working deposit channel and lost it, and Binance asks outright that you not deposit delisted tokens to your account. A token that was never listed never had one. Both look like "not on the deposit page" from where you're standing, but a delisting normally came with an announcement, and that announcement is worth going back to read.
Recovery turns on one thing: who can sign for that address
"Can the exchange get my coins back" is too vague to answer. Two sharper questions decide it: does the platform hold a key that can sign from the address those coins are sitting at, and is it willing to run a manual process for that amount? The first is technical, the second is policy, and you need both to come back yes.
Take the technical half. A deposit address isn't a reference number the exchange made up — it's a real address it controls on that chain. Which address your coins land at is decided by the chain; whether the exchange counts the deposit is decided by its own ledger. Those two can disagree, and that's exactly what has happened to you. Once you see it that way, the three kinds of address sort themselves out:
- Addresses beginning 0x: one key, and the identical address on every EVM-compatible chain. MetaMask puts it plainly — your address on Ethereum Mainnet and on BSC is exactly the same, while the assets and transaction history on each network stay separate. So if you sent a BSC token to the Ethereum deposit address you were given, the coins really are at that same address over on BSC, and the exchange does in principle hold a key that can sign there. That fact is what makes most wrong-token and wrong-network cases recoverable at all.
- A different address format usually stops you before you send. Tron addresses starting with T, Bitcoin addresses starting with bc1, and the various chain-specific formats each have their own length and checksum. Paste one into a wallet that expects something else and it refuses, generally with an invalid-address error. Frustrating in the moment, but being blocked means nothing was lost.
- A contract address is the third kind, and the worst. A contract isn't a person and has no key behind it. Whether anything can come back out depends on whether that contract was written with a way to retrieve it, and the ERC-20 token standard itself carries no interface for pulling out assets sent there by mistake, so one exists only where whoever wrote the contract added it. Where nobody did, the coins stay put.
Now the policy half. Holding the key doesn't mean the platform will act. Manual recovery consumes wallet operations, review and consolidation time, so exchanges draw a line somewhere by amount, token and network. Two people in technically identical positions — one with fifty dollars stuck, one with five thousand — can get very different answers.
Take the TXID to the right explorer and nail down three things: which address received it, which chain it actually travelled on, and the token's contract address. Etherscan for Ethereum, BscScan for BSC, Tronscan for Tron. Until those three are settled you can't tell which of the three cases you're in, and everything after that is guesswork. The deposit troubleshooter walks the branches with you.
The routes the platform actually offers
With the diagnosis done, there are three routes, in order:
- Check the deposit history for a self-service button first. Binance runs a Smart Retrieval process covering specific tokens on certain networks, and where a deposit qualifies a Retrieve Now control appears against it in your recent deposit records. If it's there, use it — it's by far the least painful route.
- No button means the self-service recovery form. It sits under the not-credited deposit flow and wants the TXID and the surrounding details. Go in with the official wording in mind: the help centre says Binance "generally does not offer a token/coin recovery service", that where you have "suffered a significant loss" it "may, solely at our discretion, assist you", and that "successful token recovery is not guaranteed". That is a discretionary favour, not an obligation.
- One special channel exists, with a high bar. If the coins went to a smart contract address on BSC and are BNB, a wrapped token such as WBNB or a pegged token such as BTCB, the BNB Pioneer Burn Program may apply. That announcement, published in September 2020, is specific: the transaction has to be visible on BscScan, the assets have to be permanently out of circulation, and the loss has to be worth more than a thousand US dollars, with a ceiling tied to the next quarter's projected burn, and with Binance investigating and confirming the trigger conditions. The announcement is not recent and the terms may have moved since, so check the current page before applying. Most ordinary mis-sends never reach that bar anyway.
On fees and turnaround, take the method rather than a number: the charges and processing times are banded by scenario, the bands aren't necessarily identical from one help page or entry point to the next, and the pages get revised. Read the figures off the form at the moment you file, and don't treat a number copied from anywhere else as a promise. One thing is stable: this is a manual queue counted in working days, not hours.
Cases the help pages already rule out
Before you spend two weeks hoping, check whether you've landed on one of these. All of them are stated outright in Binance's help centre:
- Sent to an address that isn't the exchange's at all. The wording is blunt: if you sent tokens to an incorrect address that doesn't belong to Binance, "we're unable to provide any further assistance". What's left is tracking down whoever controls that address, and chain addresses rarely lead to a name.
- Below the minimum deposit amount. Deposits that don't meet the minimum cannot be retrieved. This one catches people out because it's a separate gate from whether the token is supported — fail either and nothing gets credited.
- NFTs and Ordinals. Binance does not support NFT or Ordinal NFT deposits, and says it can only help recover NFTs on the BSC and ETH networks — meaning other networks are out.
- You're not the recipient. Self-service recovery excludes withdrawal transactions, cases where you were the sender, and applications filed on someone else's behalf.
- It went to an unsupported contract address. Deposits to a contract address outside the BNB Pioneer Burn Program are listed as ineligible — for the reason in the previous section. No key, no signature, no way out.
And one that isn't on any official list but is just as final: if the coins reached an address nobody holds a key for — a string somebody typed by hand, say — no process anywhere can retrieve them. If someone then contacts you offering to trace and recover them for a fee, that's the second scam arriving on the back of the first.
Do the arithmetic before you file
Recovery generally isn't free. Depending on the case there's a flat handling fee, a network withdrawal fee taken out of whatever comes back, or both. Put that next to what's actually stuck before you start. Recovering forty dollars of a token nobody trades, after a fee and a wait counted in working days, is a worse deal than most people assume — and if the amount is genuinely material, the opposite is true and you should file without agonising over it.
Have this ready before you open the form. Read it off the explorer, not off memory:
- The TXID. The one thing nobody can work without.
- The network the transaction actually travelled on — as shown by the explorer, not the one you meant to use.
- The token's contract address. Same-named tokens are different contracts on different chains, and this removes the ambiguity.
- Amount, approximate time, your account, and an address to receive the funds.
Check where it would come back to. The rules differ by case: for a missing or wrong tag, the official line is that recovered assets are returned only to the source address, while the self-service form asks you to supply the address you want the funds sent to. That difference matters if you funded the transfer by withdrawing from another platform — the "source address" is that platform's hot wallet, and it isn't yours. Read that line before you submit.
Then leave it alone. Filing the same case a second time doesn't move it up the queue; it just muddles your own ticket history.
FAQ
My balance shows nothing. Are the coins gone?
On-chain ownership and exchange bookkeeping are two separate things. If the explorer shows the transfer succeeded, the coins are credited to that receiving address; the exchange simply has no ledger entry for a token it never listed. Whether they can come back to you depends on who holds the key to that address, and on whether the platform is willing to run a manual process for the amount involved.
Can I move the coins out of the deposit address myself?
No. A deposit address is an address the exchange controls on that chain. You don't hold the key, so you cannot sign anything from it. Any service offering to pull funds out of an exchange address for you, or asking for an up-front payment to do it, is a scam; anything asking for your seed phrase or a verification code doubly so. The only legitimate route is a recovery request filed from your own account.
If I file a recovery request, will I definitely get the tokens back?
No. Binance's help pages say it generally does not offer a token recovery service, that it may assist at its own discretion where the loss is significant, and state plainly that successful recovery is not guaranteed. Treat it as a discretionary favour rather than an entitlement. Once filed, it queues in working days, and opening a second ticket for the same case does not speed anything up.
Does it cost anything, and is it worth filing for a small amount?
Recovery is generally not free. Depending on the case there is a flat handling fee, a network withdrawal fee deducted from what comes back, or both, and the exchange explains the charge by pointing to the manual review and consolidation work involved. Check the current figures on the form itself, then compare them with what is actually stuck. For a few dollars of a token nobody trades, the fee and the wait can cost more than the tokens.
Work out whether the token was never listed, the network was never enabled, or you simply picked the wrong network — the three are fixed in different ways. Then use the TXID to pin down the receiving address, the chain and the contract address, and ask whether the platform can sign from that address: usually yes for a 0x address across EVM chains, almost never for a different address format because the send won't go through, and never for a contract. Use the self-service button if it's there, otherwise the form, accepting the official "discretionary, not guaranteed" framing. Small amounts may not be worth the fee. Fees, timings and eligibility are platform policy and change; read them off the page at the moment you file.
Read next
Picked the wrong network — are the funds safe? Sent USDT on the wrong network: what's recoverable Minimum deposits: how low is too low Check token and network on the network tableSources reviewed 2026-08-31. Platform rules: Binance, Frequently Asked Questions on Incorrect Deposits, Binance, retrieving a deposit with self-service recovery, Binance, BNB Pioneer Burn Program announcement. Address and key behaviour: MetaMask, EVM networks and sidechains. Status lookups: Etherscan, BscScan, Tronscan. Recovery fees, processing times, eligibility and feasibility are platform policy and can change at any time — whatever Binance's own pages show at the time is what applies, and no recovery is guaranteed.