Why Does a Withdrawal Show as Complete on the Exchange but Never Arrive?

15 October 2026

A withdrawal that the exchange marks as "complete" or "sent" but never arrives in your wallet is almost always a problem with the transaction itself - not the exchange. The exchange has broadcast the transaction to the blockchain, but something has prevented it from being properly included in a block and confirmed. The most common causes are a low fee that keeps the transaction stuck in the mempool, an incorrect destination address or tag, or a blockchain-specific issue like a failed smart contract interaction.

What "Complete" Actually Means on the Exchange

When an exchange shows a withdrawal as "complete," it means the exchange’s internal system has:

• Deducted the funds from your exchange account balance.
• Signed and broadcast the transaction to the blockchain network.

It does not mean the transaction has been confirmed on the blockchain. The exchange considers its responsibility fulfilled at the broadcast stage. From that point, the transaction’s fate depends on network conditions, the fee you paid (or the exchange paid on your behalf), and whether the receiving address or destination tag is correct.

The three most likely reasons it never arrives

1. The Transaction Is Stuck in the Mempool with a Low Fee

This is the most common cause. The exchange set a fee that was too low for current network congestion. Your transaction sits in the mempool, waiting for miners to prioritize it. Meanwhile, the exchange shows it as "complete" because it was broadcast.

What to check: - Look up the transaction ID (TXID) the exchange gave you on a block explorer (e.g., Etherscan for Ethereum, Blockchain.com for Bitcoin). - If the block explorer says "Pending" or "Unconfirmed," and the transaction has not been included in a block after many hours (or days for Bitcoin), the fee is likely too low. - Some block explorers show the fee rate (sat/vB for Bitcoin, gwei for Ethereum). Compare it to current recommended fees on a fee estimator site.

What actually unblocks it: - Replace-by-Fee (RBF): If the exchange used a wallet that supports RBF (most modern exchanges do), you may be able to "bump" the fee by broadcasting a new transaction with a higher fee using the same inputs. This requires the private key or access to the wallet - you cannot do this from the exchange. Contact the exchange’s support and ask if they can RBF the transaction. - Child-Pays-for-Parent (CPFP): If the stuck transaction has unspent outputs, you can create a new transaction spending those outputs with a high fee. Again, this requires wallet access. - Wait for network congestion to clear: On Ethereum or other fee-market chains, a stuck transaction may eventually drop from the mempool after a few days (typically 2 - 14 days depending on the node). The exchange will then need to re-send it, or you may need to request a new withdrawal.

2. You Entered an Incorrect Address or Destination Tag

If the address is wrong but valid (e.g., a typo that still produces a valid checksum), the funds will be sent to that address. The exchange cannot reverse this. If the address is invalid (e.g., wrong length), the transaction will likely fail on the blockchain, and the funds will return to the exchange’s wallet after a timeout (hours to days for some chains, never for others).

What to check: - Verify the address you entered against the wallet you intended. - For coins like XRP, XLM, or EOS that require a destination tag or memo: a missing or incorrect tag means the receiving exchange or wallet cannot credit the funds. The transaction will appear "complete" on the sending side but the recipient will not see it.

What actually unblocks it: - If the address is wrong but valid, you must contact the owner of that address. The exchange cannot help. - If the address is invalid, wait for the transaction to fail and the funds to return. Then withdraw again with the correct address. - For missing or wrong tags, contact the receiving exchange or wallet support. They can manually credit the funds if they can identify the transaction. Provide the TXID.

3. The Transaction Failed Due to a Smart Contract or Token-Specific Issue

For tokens (ERC-20, BEP-20, etc.), the exchange may have sent the token to a contract address or used an incompatible network (e.g., sending BEP-20 tokens to an ERC-20 address). This often results in a successful broadcast but the tokens never appear in your wallet because the receiving address cannot process them.

What to check: - Look at the transaction on the block explorer. If it shows a "Failed" status, the smart contract call reverted. - Check the network (e.g., Ethereum mainnet vs. Binance Smart Chain). If the exchange sent on the wrong chain, the funds are on that chain and your wallet may not show them unless you add the custom network.

What actually unblocks it: - If the transaction failed, the tokens remain in the exchange’s wallet. Contact support to re-send. - If sent on the wrong chain, import the receiving wallet’s private key into a wallet that supports that chain (e.g., MetaMask with Binance Smart Chain added). The funds are there, just not visible on the chain you expected.

What to Do in Order

1. Find the TXID from the exchange’s withdrawal history.
2. Search the TXID on a block explorer for the relevant blockchain.
3. Check the status:
4. "Unconfirmed" or "Pending" → low fee.
5. "Success" but not in your wallet → wrong address, tag, or chain.
6. "Failed" → contract issue.
7. Contact the exchange’s support with the TXID and explain what the block explorer shows. Be specific: "The TXID shows unconfirmed for 48 hours on Bitcoin. Can you RBF it?"
8. If the address is wrong, accept that the funds are likely lost unless you can contact the recipient.
9. If the tag is missing, contact the receiving platform’s support, not the sending exchange.

When the Exchange Is Actually the Problem

Rarely, the exchange’s "complete" status is a lie - the transaction was never broadcast. This happens during system glitches or if the exchange’s hot wallet runs out of funds (covered in the linked article). In that case, the TXID will not exist on the block explorer. Contact support and request the transaction hash or a re-send. If they cannot provide a valid TXID, the withdrawal was not actually sent.

Back to withdrawals