How exchange deposits actually work
Almost every confusing thing about a missing deposit makes sense once you know that a blockchain transfer and an exchange credit are two unrelated events, run by two different systems, with different rules. The blockchain does not tell the exchange anything. The exchange has to go looking.
This is a plain-language description of that machinery. It should let you reason about your own transfer, and in some cases resolve it yourself without paying anyone.
1. The address is the only thing connecting you to your deposit
When an exchange gives you a deposit address, it is recording that this address belongs to your account. Nothing else about the transfer identifies you: not your name, not the wallet you sent from, not the amount. The address is the whole link.
This is why a deposit sent to a stale address, or to an address generated for a different asset or network, is a problem. On-chain it succeeded. Inside the exchange, nothing connects it to you.
A handful of networks cannot work this way, because assets like XRP use one shared address for all customers. There, the destination tag or memo is the link, and a transfer without it is the equivalent of a bank transfer with no reference number.
2. A watcher has to be looking at the right network
Exchanges run watchers: processes that scan a network for transfers into their addresses. A watcher is per network, and support for an asset is decided per network too — which is how the same token can be credited when sent one way and invisible when sent another.
A wrong-network deposit is not lost in a technical sense. The funds are at an address the exchange usually controls, on a network nothing is watching for that asset. Recovery is therefore a policy question, not an engineering one, and the answer depends on whether the exchange holds the keys for that address on that network.
- Kraken: deposit networks and methods — Official exchange guidance explaining that network choice determines whether a deposit is credited.
3. Confirmations are a risk decision, not a technical constant
A confirmation means a block was built on top of the block containing your transfer. Reversing it would mean rebuilding every block since — the more blocks, the more expensive, and past a certain depth it is not worth attempting.
Exchanges choose their threshold against the loss if a chain reorganises after they credit a balance and the customer withdraws. That is why the same exchange can accept 1 confirmation on one network and several hundred on another: on a chain with two-second blocks, a hundred confirmations is a few minutes of work.
An explorer showing 'confirmed' tells you the transfer is in a block. It says nothing about whether the exchange's threshold has been met, and this gap is the single most common reason a deposit looks stuck when nothing is wrong.
- Kraken: cryptocurrency deposit confirmations and processing times — Official confirmation requirements and the exchange's explanation of why credit waits for them.
4. Minimums exist because dust costs more to move than it is worth
Every deposit an exchange eventually sweeps into its own wallets costs a network fee. Below some amount, that fee exceeds the deposit, so crediting it loses money — hence minimum deposits.
This is the one failure mode where funds are often genuinely unrecoverable: the exchange will not credit it, and returning it would cost more than it is worth. It is worth checking the minimum before sending a small test transfer, which is otherwise sensible practice.
5. Crediting is a queue, and support is a different queue
Once the threshold is met, crediting is usually a scheduled job rather than an instant reaction, which adds anything from a minute to an hour. Some deposits are also held for review — unusually large amounts, addresses flagged by screening providers, or accounts with incomplete verification.
If your transfer needs a human decision, no amount of waiting will produce it. Recognising which situation you are in is the difference between waiting calmly and opening a ticket today, and it is the main thing TXLens is for.
What to do with this, right now
- Confirm the transfer exists on-chain and reached the address you intended. This is free here, and free on any block explorer.
- Identify the network you actually used, not the network you meant to use.
- Compare your confirmation count against the destination's requirement for that network.
- Check the amount against the minimum deposit.
- If all four are fine and it has been hours, the blocker is on the platform's side, and evidence-led support contact is the route.
What you get, and what it costs
Free, always
The transaction check: network, asset, amount, both addresses, timestamp, on-chain status, confirmation count, and a copyable evidence message for support. No diagnosis.
£9.99, one-off
The diagnosis: the likely cause, recovery outlook, step-by-step instructions, the official support route, wording written for that case, and 72-hour monitoring. No subscription.
Questions
If the blockchain says it arrived, why won't the exchange credit it?
Because arriving and being creditable are different tests. The exchange has to attribute the transfer to an account, on a network it watches for that asset, above its minimum, past its confirmation threshold, and clear of any review hold. Failing any one of those leaves the funds sitting exactly where the blockchain says they are, uncredited.
Can an exchange recover a deposit sent on the wrong network?
Sometimes. It depends on whether the exchange controls that address on the network you used, and on its policy. Several large exchanges publish self-service recovery for common cases, usually for a fee. Where the address is not theirs on that network, nobody can recover it.
Is any of this something I can fix myself?
Often, yes — and this guide is written so you can. If the answer is 'wait for confirmations', waiting is the fix. TXLens is worth paying for when you need the specific cause for your transfer, the recovery likelihood, and a support case that gets handled rather than bounced.
Related
Platform requirements on this page were last reviewed 2026-08. They change without notice, which is why every diagnosis is phrased as a likely cause rather than a certainty.
TXLens is read-only. We only use your transaction ID and public blockchain data. We never ask for your private keys, seed phrase or exchange login.