Bitcoin sent but not received
Bitcoin deposits are usually a question of confirmations rather than compatibility: there is only one Bitcoin network, so wrong-network mistakes are rare. What varies is how many confirmations the receiving platform waits for, and how long the fee you paid takes to get you there.
What usually causes this
These are the common explanations for this category of problem. Which one applies to your transfer depends on your transaction, the network it used and the destination's deposit rules — that is what the check above works out.
- Still in the mempool because the fee was below the going rate
- Confirmed but below the destination's confirmation requirement
- Sent to an address from a different account or wallet
- Below the destination's minimum deposit
Where BTC is credited, by network
BTC exists on several networks and every platform picks its own subset. A transfer over a network outside that subset confirms perfectly and is never credited, which is why "I definitely sent it" and "they definitely have not received it" are both true at once.
| Platform | Networks credited | Approximate minimum |
|---|---|---|
| Binance | Bitcoin | 0.000006 BTC |
| Coinbase | Bitcoin | 0.000001 BTC |
| Kraken | Bitcoin | 0.0001 BTC |
| Crypto.com | Bitcoin | 0.0001 BTC |
| Bybit | Bitcoin | 0.0005 BTC |
| OKX | Bitcoin | 0.001 BTC |
| KuCoin | Bitcoin | 0.0008 BTC |
| Revolut | Bitcoin | 0.0001 BTC |
Approximate, reviewed 2026-08.
Confirmations required, platform by platform
The same transfer is 'not yet confirmed enough' at one platform and long since credited at another, because the threshold is a business decision rather than a property of the network. Comparing them is the quickest way to see whether your wait is normal.
| Platform | Bitcoin | Ethereum | TRON | Polygon | Solana |
|---|---|---|---|---|---|
| Binance | 1 | 6 | 1 | 100 | 32 |
| Coinbase | 3 | 35 | 1 | 200 | 32 |
| Kraken | 4 | 20 | 20 | 120 | 32 |
| Crypto.com | 1 | 12 | 1 | 100 | 32 |
| Bybit | 1 | 6 | 1 | 100 | 32 |
| OKX | 1 | 12 | 1 | 100 | 32 |
| KuCoin | 2 | 12 | 1 | 100 | 32 |
| Revolut | 3 | 30 | 20 | 150 | 32 |
Approximate, reviewed 2026-08. A dash means the platform does not credit deposits on that network, or does not publish a figure.
Where the platform deposit figures come from
- Binance support centre
- Coinbase support centre
- Kraken support centre
- Crypto.com support centre
- Bybit support centre
- OKX support centre
- KuCoin support centre
- Revolut support centre
Policy snapshot 2026-08; verify in-account.
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
How long do Bitcoin confirmations take?
About ten minutes each on average, though it varies. If an exchange needs three, expect roughly half an hour after the transaction is first mined.
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.