Withdrawals Blocked for Now: Three Cooldowns, Three Different Fixes

Three 24-hour rules, three different things

Side by side, you can usually spot your own column in one pass:

Which one	What triggers it	When the clock starts	What happens at the end
Account protection window	Setting, changing or resetting any security setting	The moment you made the change	Restores by itself, nothing to apply for
Purchase unlock	The amount bought through fiat / P2P trading	After that purchase completes	That amount becomes withdrawable
Retry window	Your last withdrawal failed to send	After the failure	The system retries, or refunds the coins to your account

The only thing the three share is the number in the documentation. Even the question of who acts at the end differs: in the first case you press withdraw again yourself; in the third the system acts and you just read the outcome.

Treat those durations as whatever the help page shows when you open it. Checked September 2026.

One: you changed a security setting

The one from the opening. It is also the only cooldown you can trigger without noticing, because the trigger is deliberately broad — setting, changing or resetting any security setting counts. The examples the help centre gives are completing KYC for the first time, changing your Google Authenticator, and updating your phone number.

Three details worth keeping:

• The clock starts when you made the change, not when you noticed the block. Those two moments can be hours apart.
• It cannot be cancelled. The documentation says so plainly, and the reasoning is blunt: if the change wasn't made by you, those 24 hours are the window the real account holder gets to react in. Wanting to bypass it is wanting an account that can be emptied immediately after someone else touches its settings.
• You can calculate the exact release time yourself. The English help page gives the path as Account Setting - Security Setting - Security Logs, and links straight to it. Menu names differ between language versions of that page, so go by what your account shows. Find the entry, add 24 hours, done. No one needs to be asked.

If you arrived here through a lost-authenticator recovery, the same cooldown lands at the end of that process; the full route is in recovering a lost 2FA and isn't repeated here. Same for a phone number change — steps in changing your phone number.

Two: the balance came from a fiat or P2P purchase

The second one has nothing to do with security and everything to do with where the money came from. The help centre states it in one line: crypto bought through P2P trading can only be withdrawn after 24 hours.

Note that it locks that purchase, not your account. Which produces a genuinely confusing screen: five hundred USDT in the balance, three hundred withdrawable, because two hundred of it was bought this morning. That's not a limit, it's a clock, and it clears on its own.

The same section carries a neighbour that gets confused with it: if you have active merchant orders in the P2P market, the account has to keep a required balance as a security deposit. That one is not a clock at all — waiting does nothing, you have to deal with the orders.

One thing the documentation does not do is set out a different waiting time per funding method. It states the rule for crypto bought through P2P trading and leaves it there, so if you funded by card or bank transfer, check what your own withdrawal screen offers rather than assuming this clause covers you.

Three: your last withdrawal failed

This one has a precondition: a withdrawal request was successfully submitted and then failed. The four common causes listed officially are a wrong address, an address of the wrong length, a missing Tag or Memo where one is required, and network delays.

The official wording carries a condition: if the failure was not one of the cases above, the system normally retries or refunds within 24 hours, and only after that does a ticket make sense. A wrong address is handled differently — the documentation says the coins are returned automatically and the record is marked as a cancelled withdrawal, so there is nothing to sit out.

What separates this from the first two: there is a record to read. The withdrawal detail page states the actual failure reason. Read that line before resubmitting anything. Waiting is the least useful response available — a mistyped address will not become correct by next year.

Telling them apart without asking support

One test: check whether the withdrawal request exists.

The first two cooldowns act before you press confirm — the request never gets created, the withdrawal history has nothing in it, and the page either shows a notice or simply offers a smaller withdrawable amount. The third acts after creation, so there is always a row in the history, marked failed or cancelled.

Open the withdrawal history once. Nothing there → check the security log (case one) or what you bought today (case two). One failed row → read its failure reason (case three).

The one move that restarts the clock

Blocked, the instinctive reaction is to "go check the security settings" — and while in there, flip a toggle or re-bind something.

That restarts the 24 hours from zero. The clock runs from the most recent change, not the first one. Looking is fine; changing is not. During a cooldown, that page is read-only as far as you're concerned.

Two more things not to do. Resubmitting the withdrawal repeatedly doesn't accelerate anything and only generates more failed rows. And any service offering to "unfreeze" an account or "fast-track" a withdrawal wants your password or your codes — hand those over and you have created exactly the situation the 24-hour window exists to protect against.

A fourth case: the coins aren't in the available balance

One more case looks identical from outside: the total looks unchanged while the withdrawable part is smaller.

Sitting in a savings product that hasn't been redeemed, locked by an open order, waiting for release inside a P2P order, pledged against a loan. None of these is a cooldown, because there is no single countdown to sit out: some do carry time (a fixed-term savings product matures, a P2P order waits on the counterparty), others never clear on their own at all — an open order and a pledge stay put until you unwind them. Working out where the rest sits is covered in available vs total balance.

And one more that isn't a wait either: withdrawals aren't open at all until identity verification is complete.

What to have ready before you open a ticket

The documentation points you at a ticket in exactly two places: a protection window still in force more than 24 hours after the change, and a failed withdrawal that has been neither retried nor refunded after 24 hours. Everything else on this page resolves itself or resolves by you unwinding something.

What you bring differs by case, and bringing the wrong artefact costs a round. For the protection window: the timestamp from the security log and the fact that more than 24 hours have passed since it. For a failed withdrawal: the record itself and the failure reason printed on its detail page. Those are two different pieces of evidence, and neither substitutes for the other.

Worth knowing before you write: the protection window is documented as impossible to cancel — not by you and not on request. So a ticket opened inside those hours has nothing to act on.

One vocabulary note if you're reading the documentation in English: what the Chinese pages call fiat trading appears as P2P trading in the English version, and the withdrawable-after clause sits under that heading. Same rule, different word — worth knowing when searching the help centre.