What to do when a withdrawal gets stuck: five real causes, and how to check each one

Behind "my withdrawal was three days ago and still hasn't arrived" there are at least five completely different situations, and the correct response to each contradicts the others: one person needs to top up turnover, another needs to change an address, a third needs to do nothing at all because they hit a weekend. If you cannot tell which one you are in, you will do the worst possible thing — resubmit repeatedly, withdraw to a different address, argue with support — and each of those makes it slower.

This article does not guess. We read the server code that processes withdrawal requests: it validates in a fixed order, gate by gate, and returns a fixed error string when one fails. So "where am I stuck" has an objective answer: which error message you are looking at. Below we list the eight gates and their exact wording in one table, then go through the trigger conditions and the action for each, and finally use real order data from this site to calculate how long topping up turnover actually takes, and what the 5 USDT fixed fee really is as a percentage of a small withdrawal.

1. Start with the table: which error are you seeing

The server's validation order is hard-coded, so which gate you hit first is also determined. Many people assume every withdrawal is slowly eyeballed by a human; in fact the first five gates are instant machine checks, and only the last one enters a manual queue.

Basis for the order: the server's withdrawal endpoint evaluates the rows above top to bottom and aborts with the corresponding message at the first failure (server.py lines 875–930, read 2026-10-25). Item 9 is not a rejection: the record is written with a review status, and it is the only one that needs a person.

There is a technique to reading this table: the error text is the only reliable locator; do not infer from "how long ago I submitted". Three days with nothing arriving could be a queue at item 9, or it could be item 4 and you never actually submitted at all. Go back and read the message, then jump to the matching section.

2. Gate 4: the address — whatever you deposited from is the only place you can withdraw to

This is the one most often mistaken for "the platform doesn't want to pay out", yet it is the most rigid design on the site. The mechanism is simple: the account holds an address table (addresses) recording, for each network, the address you used to deposit and when that binding happened. On a withdrawal request the system looks your entered address up in that table, and if it is absent — or present with no binding timestamp — it rejects outright.

Note the parenthesis: this address cannot be changed. That is not a hint, it is the design goal. The benefit is concrete: even if your email and password both leak, an attacker has only one option — send the money back to your own wallet, because a stranger's address cannot get onto the whitelist. The cost is flexibility: the network and address you chose at deposit time lock in your future withdrawal route.

That produces three frequent mistakes, in descending order of frequency:

• Switching wallet apps and assuming the address is the same. Only an address restored from the same seed phrase is identical; creating a new wallet creates a new address and will always be rejected.
• Mixing up TRC20 and ERC20. On the same exchange, the TRC20 and ERC20 USDT deposit addresses are two completely different strings. Withdrawing to an ERC20 address on TRC20 is not just rejected — a transfer sent to the wrong network cannot be recovered at all.
• Treating an "address change" as editing a field. Changes go through a different table (addr_change), default to pending, are decided by a human and are not guaranteed. If you genuinely need one, prepare proof of ownership of the new address, and do not submit the change request in the same minute your withdrawal was rejected.

3. Gate 6: KYC is two checks, not one

The site splits verification into two independent states: identity verification (kyc_state) and address verification (kyc_addr_state). Both must be approved before a withdrawal is released. Passing only the ID check still blocks you, and the error text is the same sentence, which is why so many people insist "but I already verified".

Address verification means proving that the receiving address really is yours. It is a different question from identity: identity answers "who are you", address verification answers "does this wallet belong to you". For overseas Chinese users this step usually snags on three details:

• Inconsistent name spelling. The ID says ZHANG WEI while the bank or exchange account says Wei Zhang or ZHANGWEI, and manual review sends it back. Keep the same order and spacing as the document.
• Glare or cropped edges in the ID photo. All four corners must be complete and the expiry date legible. Photos of a screen taken with a phone are almost always rejected.
• Expired proof of address. Utility bills and bank statements are generally required within three months, with name and address matching the registration.

This gate has the widest variance in duration: under ten minutes when documents are complete, up to a business day when a human has to fill gaps. That is why it should be done before your first deposit, not when you want to withdraw — every wait at that point carries emotion, and people make worse decisions, like "I'll just register another account".

4. Gate 8: 1× turnover, counted on stake rather than on P&L

This is the most misunderstood rule and the most common real reason a withdrawal "doesn't arrive". The rule is clear: after depositing, you must complete settled volume equal to 1× the deposited amount before withdrawing (standard AML practice, not unique to this site). What matters is what counts as volume:

• Only settled orders count — status win or loss. Open positions that have not expired do not.
• What is counted is the stake, not the P&L. Winning 8 USD does not add 8 USD of volume, and losing does not reduce it.
• Orders placed by a bot are excluded (venue=bot), and practice mode does not count.
• The measure is cumulative: total deposits × 1, so multiple deposits stack the requirement.

So "is my turnover enough" is something you can work out from your own order history without asking support. To give the number a reference point, we counted the site's 29,222 settled orders (bots excluded): median stake 28.05 USD, mean 56.05, p90 134.74. Converting at the median stake, the number of orders and the minimum time needed to complete turnover are:

Method: trades = deposit ÷ 28.05, rounded up; time = trades × expiry in seconds, excluding the gap between entries and the queue for settlement — a theoretical floor. Median stake from the 29,222 settled orders queried on 2026-10-25 00:50.

This table explains a counter-intuitive result: using the smallest stakes to complete turnover is the slowest possible method. On the same 500 USD deposit, the median 28 USD stake needs 18 trades, while 5 USD minimums need 100 — 100 minutes even on the 60-second tier, and any single "I'll pick it up tomorrow" stretches that to days. If you really must top up, use amounts near the median and trade consecutively on a fixed tier; it is far faster than scattering small orders.

5. Gate 7: two hard 24-hour lines, and they are rolling windows, not calendar days

Two limits apply to frequency and amount, and both are rolling 24 hours, not "reset at midnight":

• At most 2 requests in 24 hours. The third is rejected at submission with the count limit stated explicitly. Anyone planning "three small withdrawals" is stuck after the second.
• Cumulative withdrawals within 24 hours may not exceed 100% of balance. The ratio is currently 100%, meaning in theory you can withdraw the whole balance in a day, but any request exceeding the balance is rejected. The balance is taken at the moment of submission, and margin tied up in open positions does not count as available.

Add the 5 USDT fixed fee and the requirement that the net amount be positive, and a practical conclusion follows: many small withdrawals are both slower and more expensive. Withdrawing 50 USD costs 5 USD (10%); 500 USD also costs 5 USD (1%); and 24 hours only gives you two chances. Spending those two chances on larger amounts is the only sensible arrangement.

6. Gate 9: manual review — currently every withdrawal enters it, and it is not about you

This is the stage most often misread as "I've been flagged". The site has a manual review threshold setting, currently 0, which means every withdrawal enters the review queue, not just large ones. So when the status sits at "under review", the first conclusion should be: this is the default process, not an abnormality marker.

By this stage the amount has already been deducted from the balance and the record is in the database. This step does not speed up because you chase it, but it does speed up when documents are complete. Review actually checks four things:

• Address consistency: whether the receiving address matches the deposit record (gate 4 already blocked once automatically; a human checks the network again).
• Genuineness of turnover: whether the same minute contains repeated open-and-close trades hedging both directions purely to build volume. Such wash trading passes the automated turnover check but gets sent back here.
• Login environment: a different location, a large deviation from historical devices, or multiple accounts on one device.
• Source of funds: may be requested for large amounts; supplying the deposit txid is the fastest way.

Acceleration documents, ranked by value for effort: deposit txid (on-chain hash) → proof of address ownership → source of funds statement → photo holding your ID. The first is close to universal, because it proves both address ownership and the fact of the deposit at once. Conversely, a purely textual chase ("please hurry") creates no priority whatsoever in the review queue.

7. One more category of stuck, unrelated to the platform: on-chain, weekends and maintenance windows

If all eight gates above are ruled out and the money still has not arrived, what remains is external. The signature is: status already "sent" or "processing", the money has left the platform, it just has not landed at your address.

On-chain confirmation: not congested right now

Measured at 2026-10-25 00:52 (Beijing): Bitcoin's fastest fee rate was 1 sat/vB (fastest, half-hour, one-hour and economy tiers all at 1), block height 972,950, and the last three blocks contained 6,572 / 5,135 / 6,534 transactions. That is a very empty period: a normal-sized transaction confirms in the next block, about 10 minutes. If your USDT-TRC20 withdrawal is unconfirmed for over an hour during such a window, check whether the txid exists rather than keep waiting — no txid means it was never broadcast and the problem is on the platform side.

The real on-chain cost of TRC20

Tron chain parameters (getchainparameters, fetched at the same moment): energy price 100 sun, bandwidth 1,000 sun per byte, account creation fee 100,000 sun. Taking the commonly published USDT transfer consumption of 31,000 to 65,000 energy, that is roughly 3.1 to 6.5 TRX, or about 1.0 to 2.1 USD at 0.3286 USD per TRX. This is an estimate rather than a bill measured on this site, but it is enough to conclude that the on-chain portion is less than half of the 5 USDT fixed fee.

Weekends and the daily maintenance window (Beijing time)

/api/config currently returns this closure note: closed from Friday 20:00 UTC to Monday 00:00 UTC, with daily maintenance from 20:00–24:00 UTC. In Beijing time that is closed from Saturday 04:00 to Monday 08:00, and daily maintenance 04:00–08:00. Withdrawals themselves are not affected by the market closure, but manual review is noticeably slower outside staffed hours, so a withdrawal submitted on Friday night usually only starts counting on Monday. That is not an excuse, but it is a fact you can plan around.

Bank routes

If you are on a fiat route (withdrawing after a wire deposit), cross-border SWIFT transfers are typically T+1 to T+3 business days, plus another hop for a correspondent bank. No platform can accelerate that, and it should not be counted as "the platform is holding my money".

8. Work out the cost: what is actually expensive about 5 USDT

Put the fixed fee next to the spread and the real cost structure of a withdrawal becomes clear. Using the measured spread of 0.662 USD from 2026-10-25 00:50, one lot (100 oz) costs 132.40 USD in spread for a round trip; 0.01 lots costs 1.324 USD.

Fixed fee as % = 5 ÷ withdrawal amount; "equivalent round trips" = 5 ÷ 1.324, independent of amount and always 3.8 — meaning that whatever you withdraw, the fixed fee equals 3.8 extra complete 0.01-lot round trips.

Put that cost back on the trading side and it bites harder. The 60-second tier pays an expiry yield of 0.68, so the break-even win rate is 1 ÷ (1 + 0.68) = 59.5%; the 300-second tier pays 0.80, a break-even of 55.6%. A withdrawal followed by a re-deposit not only costs 5 USDT, it also means paying the spread again on the next entry, pushing the break-even line up once more. For a small account, fewer withdrawals and fewer deposits is itself a form of risk control.

9. Check in order: a 30-minute action list

Finally, a table you can follow. The principle is to start with the cheapest, fastest, most certain check and not open with a support ticket.

Work through this table and you end with a definite conclusion: which gate, what to do, roughly how long. Then open a ticket and write "I'm stuck on turnover: settled 412, deposited 500, 88 short" rather than "my withdrawal hasn't arrived in three days, please reply urgently". The two are not in the same league for resolution speed.

10. The three most common misconceptions

• Misconception 1: many small withdrawals are safer. The opposite is true. The 5 USDT fixed fee peaks as a percentage at small sizes (10% on 50 USD), and 24 hours only gives you two chances. Two withdrawals of 25 USD do not even work — anything below the minimum is rejected outright.
• Misconception 2: withdrawing to a new address is faster. Addresses are whitelist-based and cannot be changed by you; a new address only triggers a gate 4 rejection and burns one submission. If you truly need a change, file the change request — and not at the same moment your withdrawal was rejected.
• Misconception 3: support can waive the turnover requirement. Turnover is checked at the very front of server-side request handling; if it fails nothing is written to the database and support cannot even see the request. All they can do is tell you how much you are short, not let you through.

Frequently asked questions

How long after submitting does a withdrawal arrive?

Three stages, and only the first is under your control. Stage one is server validation, which completes instantly on submission and returns an error the moment any gate fails. Stage two is manual review: the current setting is wd_big=0, meaning every withdrawal enters the review queue rather than only large ones, and speed depends on staffed hours. Stage three is on-chain confirmation: measured at 2026-10-25 00:52 (Beijing), Bitcoin's fastest fee rate was 1 sat/vB, block height 972,950, and the last three blocks held 6,572 / 5,135 / 6,534 transactions — an extremely empty period, where a transaction usually confirms in the next block, about 10 minutes. None of the three promises a fixed duration; if you are in a hurry, judge by the on-chain state at the last stage.

What do I do about "withdrawals may only use the address bound at deposit"?

That is the fixed error of the address gate, triggered when the withdrawal address does not appear in the account's addresses table, or the record has no deposit binding time (bound_ts empty). There is only one fix: go back to the address you deposited from. The same wallet on a different network is not the same address — USDT-TRC20 and USDT-ERC20 must be treated separately. If you genuinely need a different receiving address, file an address change request (addr_change), which is manually reviewed and not guaranteed; once bound, an address is designed to be unchangeable by you, so that even a stolen email cannot redirect funds to a stranger.

I'm slightly short on turnover — can I withdraw part of it?

No. The turnover check rejects the entire request rather than allowing a proportional release: as long as settled volume is below 1× the deposited amount, any withdrawal request returns "AML requirement: 1× turnover must be completed after deposit before withdrawal", together with both the deposited and completed figures. The gap can only be closed by placing more trades. Watch the definition: only settled orders with status win or loss count, practice and bot orders are excluded, and unsettled positions do not count. At the 28.05 USD median stake across 29,222 settled orders, a 500 USD deposit needs about 18 trades, or roughly 18 minutes at minimum on the 60-second tier.

Is the minimum withdrawal 50 USDT or 20 USDT?

The two figures disagree, which we found while checking for this article. The settings table records a minimum of 50 USD (wd_min_usd=50), and the withdrawal info endpoint returns 50 to the front end; but the server's amount check reads a different key, wd_min, which does not exist in the settings table, so the code default of 20 USD takes effect. In other words the page says 50 while the real barrier is 20. Plan around 50 and do not sit on the 20–50 boundary, to avoid repeated submissions caused by the mismatch between stated and actual behaviour.

Is the 5 USDT withdrawal fee expensive?

Two separate questions. The real on-chain cost: at 2026-10-25 00:52 (Beijing), Tron's energy price was 100 sun and bandwidth 1,000 sun per byte (measured via getchainparameters), TRX traded at 0.3286 USD, and a USDT-TRC20 transfer at the commonly published 31,000–65,000 energy works out to about 1.0–2.1 USD on-chain, leaving roughly 2–4 USD of the 5 USDT for processing and staff. The pain of a fixed fee is at small sizes: 5 USD on a 50 USD withdrawal is 10%, on 500 USD it is 1%, on 5,000 USD just 0.1%. What is expensive is frequent small withdrawals, not the rate itself.