A withdrawal that has not arrived is the most common support question in crypto, and the least useful advice online is “just wait”. Waiting is correct for about an hour and wrong for about a week — and the difference between those two situations is visible in the first ten minutes if you know which two things to check.
This guide is the sequence we run. It starts with the blockchain, not with support, because the chain tells you immediately whether the problem is on your side of the venue or inside it. Then it covers the evidence a support team actually needs, how long each stage normally takes, and the specific signals that mean a pending withdrawal is no longer a delay but an exit problem — the situation CoinEx users are in until December 22, Extended users until October 21, and Mt. Gox creditors until October 31.
🔍Start With the One Question That Splits the Problem in Two
Before you contact anyone, find your transaction hash (txid) if the venue gave you one. A txid means the exchange has broadcast a transaction from its wallet, and you can check it on a block explorer: if the transfer is confirmed and the destination address matches yours, your money has arrived on-chain and the problem is a display, crediting or address issue. If the txid exists but is unconfirmed, the network is still working on it. If there is no txid at all, the withdrawal is still inside the exchange — and that is the category where delays turn into incidents.
This single step changes the tone of every support conversation that follows, because it tells you which side of the fence you are asking about. It also stops the most expensive mistake in the whole process: opening a second withdrawal for the same funds while the first one is in flight.
📋The Five Reasons a Withdrawal Sits Pending
| Cause | Typical duration | How it resolves |
|---|---|---|
| Venue processing queue (no txid yet) | Minutes to a few hours | Internal review completes; the venue broadcasts. Nothing you can do but wait and keep the ticket open |
| Wallet or chain maintenance on the venue side | About 1 hour to a few days | The exchange reopens the route after maintenance. The announcement is usually published before the pause |
| Network congestion or a fee spike | Minutes to hours | The transaction confirms when the fee market clears. TRON block times stay near 3 seconds, so this is rarely the cause on TRC20 |
| Compliance or risk review hold | 24 hours to several weeks | Support requests documentation; the hold is lifted or the withdrawal is returned to your balance. Unresolved source-of-funds questions are the slowest category |
| Platform wind-down or insolvency | Open-ended | There is no resolution inside the platform. It becomes a deadline problem — withdraw inside the published window or lose the route |
🧭The Seven-Step Triage, in Order
- 1Check the txid on a block explorer
Search the hash on TronScan for TRON, Etherscan for Ethereum, BscScan for BNB Chain. Read three fields: confirmations, the amount, and the destination address. Any mismatch between the destination and the address you submitted is the most serious version of this problem and needs the venue notified immediately.
- 2Confirm network and address type
A USDT transfer sent on the wrong network is not slow, it is lost — the tokens exist on a chain the receiving platform does not credit. Check that you selected the same network the receiving address supports, and that the address itself matches the chain. New addresses also need a first transfer to activate on TRON, which is documented in the walkthrough that covers network choice, minimums and the arrival sequence for a Binance to TRON withdrawal.
- 3Check the exchange's status page and announcements
Maintenance windows and chain pauses are always announced, usually on a dedicated status page or an announcements section. If the route you used is covered by an active notice, stop here — you have your answer and the timing.
- 4Check minimums and balance coverage
A withdrawal below the venue minimum, or one where the fee leaves a negative balance after deduction, is rejected rather than processed. Fees are charged on top of the transfer amount, and the minimums across venues vary by a factor of ten — the table in the comparison of withdrawal minimums and monthly limits at eleven exchanges is the fastest way to confirm you cleared both thresholds.
- 5Open a ticket with an evidence pack
Send it once, with everything in the first message. Support queues triage on completeness, and a ticket that needs three follow-up rounds starts three days late.
- 6Escalate on a clock, not on frustration
No txid after 24 hours: ask for a written status and an expected resolution window. No funds and no txid after 72 hours: escalate to a complaint channel and ask for the ticket to be routed to the payments or risk team. After seven days with no explanation: treat it as a platform problem, not a support problem, and run the checks in the next section.
- 7Never re-send until the first transfer is resolved
If the first withdrawal is pending inside the venue, a second request can double-spend your balance or trigger a duplicate risk review. If the first is confirmed on-chain with the wrong destination, a second transfer does not recover the first one.
📎What Belongs in the First Ticket
| Item | Why support needs it |
|---|---|
| Withdrawal order ID | It identifies the internal record; without it support has to search by timestamp and amount |
| Transaction hash, if issued | It proves whether the venue broadcast anything at all |
| Amount and asset exactly as submitted | Rules out fee deduction and minimum-threshold confusion in one line |
| Network selected and destination address | The two fields where most genuine losses originate |
| Date and time of the request, in UTC | Removes the time-zone ambiguity that delays first responses |
| Screenshot of the withdrawal record and account balance | Establishes the balance was deducted, which is the venue's responsibility to reconcile |
⏱️How Long Each Stage Normally Takes
On-chain arrival is fast and predictable when the route is working. A TRC20 transfer confirms in about a minute with blocks near 3 seconds; BEP20 and Solana are comparable or faster; ERC20 depends entirely on gas and congestion and can range from a minute to half an hour. The delay almost never lives in the network — on TRON it is measured in seconds, which is why a TRC20 withdrawal that has no txid after an hour is an internal processing question.
The exchange side is where the clock stretches. A standard processing queue is minutes to a couple of hours. A wallet maintenance window is typically an hour and can run to a few days for chain-level work. A compliance hold is 24 hours at the short end and can run for weeks — and it is the category where a clear, documented answer to a source-of-funds question is the only real lever you have.
On the cost side, the transfer layer is cheap enough that it should never drive your decision to test first. A standard TRC20 USDT transfer costs about $0.56 in rented energy at this week's price of 26 SUN against a 100 SUN burn price — the full arithmetic is in the guide to paying for TRON energy when you send USDT. On a $1,000 withdrawal, testing with a small amount first costs less than the fee on the main transfer.
🚨Three Signals That Mean It Is Not a Delay Anymore
When a venue is running out of exits, the first visible symptoms are administrative rather than technical, and they arrive in this order. First, deadlines appear where none existed — a withdrawal cut-off, a conversion date, a wind-down schedule. CoinEx's notice ended non-USDT balances and set December 22, 02:00 UTC as the last date to withdraw anything, after which balances move to custody under a 5% monthly fee; we worked through the arithmetic in the analysis of what the CoinEx deadline charges users who wait. Extended's Arc migration gives USDT and wBTC holders until October 21, 12:00 UTC, after which balances above $1 restrict the account and affected positions are liquidated at the mark price.
Signals cost money to ignore: uncapped or rising withdrawal fees, a new custody fee on balances that used to be free, a withdrawal page that now requires a form or a manual review, and marketing that becomes unusually loud about a token rather than about the platform. A venue that needs deposits to keep operating will tell you so in the language of opportunity rather than risk.
The third signal is silence. Support responses that shift from answers to acknowledgements, then to automated replies, then to nothing, mark the transition from operational problem to insolvency problem. At that point the correct action is not to escalate harder — it is to withdraw whatever the platform will still send, stop depositing, and keep a dated record of every attempt.
This is not theoretical. September produced three separate withdrawal-halt episodes we covered in the review of three halts in seven days and what each one cost users, and each of them started with the same administrative tell: a date.
📝What to Record While You Wait
Keep a single document with the withdrawal order ID, the txid if one exists, the amount, the asset, the network, the destination address, the timestamp in UTC, every ticket number, and a screenshot of each support reply. Two reasons. It compresses your next escalation into one message, and if a platform fails, the record is what establishes your claim and its date.
Two habits make the record useful rather than decorative. Timestamp in UTC, because a platform's support, its status page and the block explorer may all be in different time zones. And keep the account-balance screenshot showing the deduction, because the dispute is usually about whether the venue owes you a transfer, not about whether you requested one.
If the worst happens and the platform enters a rehabilitation or insolvency process, the process will ask for exactly these items, usually through a portal with a deadline of its own. Mt. Gox creditors are on their third such deadline — the current one falls on October 31, with roughly 34,500 BTC still undistributed as of October 5 and about 4,500 claims unresolved, and the trustee has said corrections filed in the final week may not be processed. Filing early is free; filing late is not available.
Check the chain first, then the venue's status page, then support — in that order, with the six-item evidence pack in the first message. Wait an hour for a processing queue and escalate on a 24/72-hour clock. And watch for the administrative signal that outranks all of them: a new date on the platform's own notices. A deadline is not a delay, and it is the only warning most platforms give.