Account restricted: can you still withdraw?

"My account is restricted" is not one state, it is a category. Underneath it sit at least five quite different situations, with different things you can still do, different things you should do, and wildly different timescales. Work out which square you are in before you act: that is the whole point of this piece.

First, place yourself

The basis for placing yourself is the text of the message and anything in your inbox, not how it feels. Those are the only two places carrying information. The common instinct is to go and search social platforms for what happened to other people, which is backwards — their situation is not necessarily yours.

The most common one: a cooling-off period

At least one variant needs no guesswork, because the platform publishes it. Binance’s page on managing withdrawal settings states that modifying the withdrawal whitelist may lead to a temporary withdrawal suspension of 24, 48 or 72 hours, and that disabling the whitelist triggers the same thing (checked 2026-08). The page does not say whether that window can be shortened, nor which rule decides between the three durations, so until it ends the only thing you can be certain of is that you did not break anything. Other triggers — a password change, a new device, a risk flag — are described differently by each platform, so go by the message you actually received.

This accounts for the overwhelming majority and it is a completely normal mechanism. It is usually triggered by something you did yourself:

• Changed the login password;
• Rebound the phone number or email;
• Reset or replaced the two-factor device;
• Added a new address to the withdrawal whitelist;
• Logged in from a device never used before.

Any of those typically starts a quiet period during which withdrawals are blocked. This is a protection: if the account had been taken over, that window is what gives you time to notice and intervene.

The handling is one word: wait. The duration is usually in the message. The thing not to do during it is keep adjusting security settings: every change can restart the clock.

The one that wants documents

Compliance reviews get triggered for many reasons: a change in your transaction pattern, a source of funds that needs explaining, identity documents reaching expiry, or a random sample. It does not mean you did anything wrong.

The operating principles:

1. Read what is being asked for, and send it all at once

   Partial submissions and wrong documents both push the case back in the queue. The request normally specifies document types and a time window: "within three months", "issued by a third party" — so work through it line by line.

2. Make the documents consistent with the story

   What you say about the source of funds and what the evidence shows have to match: salary statements for salary, a contract for a property sale. Do not pad with something unrelated to the explanation.

3. Official channels only

   Documents go into the platform's ticket system or the page it specifies. Anyone asking for your ID via direct message, email or a social platform gets ignored.

4. Once submitted, stop chasing

   Opening new tickets pushes the original one back. Give it a few working days before checking for a response.

One transfer stuck, everything else fine

The least worrying case, and the one most often mistaken for a serious problem. Usual causes:

• The amount crossed a risk threshold and needs a human look;
• The destination address is newly whitelisted and still cooling off;
• That chain is under maintenance;
• That asset has a current limit in place.

Testing it is direct: try again over a different chain, or with a smaller amount. Goes through, and it was a threshold or a chain issue. Still blocked, and it is time to go read your messages.

One impulse to resist: do not cancel and resubmit repeatedly. Each resubmission can re-queue, and high-frequency activity is itself something risk systems watch for, which is how a small problem becomes a larger one.

The one about your region

If the message mentions where you are, this is not about your account, it is about the platform's position there. The characteristic is that functions close in stages, with withdrawals usually last, which means the runway is longer than it feels.

The handling differs from a coin delisting because it applies to the whole account rather than one asset. Order, priorities and what remains possible at each stage are in when an exchange leaves your region.

The hard one: no explanation at all

No duration, no description, support replying with help-centre links. The first move here is not guessing. It is evidence.

Save these before anything else

• A screenshot of the portfolio overview, with a visible timestamp;
• A screenshot of the restriction message itself;
• All in-app messages and emails, as originals rather than screenshots — the originals carry signatures and are harder evidence;
• Exported trade and withdrawal history;
• Every document you submitted and when you submitted it.

Why evidence first? Because if this eventually goes to an appeal, a complaint or something more formal, your ability to explain what happened depends entirely on what you preserved at the time. What is on screen can change. What you saved does not. What to keep and how is in which transfer records are worth keeping.

Then, in this order

1. Open one clear ticket: describe the symptom, attach the screenshots, and state what you want to know, for instance, the type of restriction and the expected duration;
2. Confirm the account itself is not compromised: check login history, API keys, and whether any device is unfamiliar;
3. If part of the account still works, trading but not withdrawing, say — do whatever that allows;
4. Give it a reasonable amount of time, without opening a new ticket daily.

Step two gets skipped routinely. One class of "account restricted" is the platform having stopped an intruder on your behalf: someone logged in from elsewhere, funds were being moved out, and risk controls froze it. In that version the restriction is doing you a favour, and your job is to change the password, replace two-factor and end every active session as fast as possible.

How to write to support so it helps

The same situation, described two ways, gets handled several times faster or slower. A few things that genuinely work:

Facts first, request second

Put the key information in the opening two sentences: when, what happened, what you already did. "Withdrawals on my account have been restricted since [date]. The message reads '...'. I have checked login history and API keys and found nothing unusual." A ticket opening like that tells the reader immediately where to look.

Compare with "why can't I withdraw??? urgent!!!", which costs two rounds of questions just to establish the basics.

Ask a question they can answer

More effective than "please lift the restriction" is "please tell me which category of restriction this is and what documents you need from me". The first is a request they may not be authorised to grant; the second is a question they can simply answer. And once you have the answer, you at least know what you are waiting for.

One ticket, followed through

Do not open new ones. Add information as a reply on the original. Every new ticket re-queues and costs the handler the context.

Keep the feeling separate from the facts

Not a request to suppress anything, a practical observation: an emotional message tends to get filed under "needs reassurance" rather than "needs action", and action is what you want. If it genuinely is urgent, express the urgency as a fact: "the withdrawal window closes on [date]" carries far more weight than "I am very worried".

Reducing how often this happens

Most restrictions are avoidable, because the things that trigger them are a small set of behaviours.

Do not change security settings mid-migration

Password changes, phone rebinding and whitelist additions all tend to start a quiet period. Make those changes before you start moving, not partway through. This single rule prevents the most common version of "why can I suddenly not withdraw".

Do not log in from unfamiliar places repeatedly

Changing device, network or city is all normal, but doing several in quick succession looks suspicious to a risk engine. If you need to move a large amount while travelling, log in from there a day or two beforehand and let the system get used to it.

Do not test amounts against a threshold

People who discover that a certain size triggers manual review sometimes split it into several transfers just under the line. That pattern is specifically what risk systems look for. Send the large one honestly and let it be reviewed; it is usually faster.

Keep identity information current

Expired documents and an unchanged address after moving do not affect ordinary use, but they become the blocking item the moment a review triggers. When the platform prompts you to update, do it then rather than discovering it while trying to withdraw.

After it lifts, verify before you move

Getting the "restriction removed" message is not a reason to send everything immediately. Do three things first:

• Send a small transfer and confirm the path is genuinely open: sometimes only part of the functionality returns;
• Audit the security items: devices, active sessions, API keys, withdrawal whitelist. If the restriction was risk controls catching something, the underlying problem may still be there;
• Check the message came from the platform and not from a convincing imitation: this scam targets people who have just been restricted, because you are waiting for exactly this news.

That last one deserves emphasis: "your account has been restored, please click here to verify your identity" is among the most effective phishing templates there is, precisely because it says what you most want to read. The test is whether the email carries your anti-phishing code, and the rule is not to click links in it — open the site yourself and log in.

An honest word about timescales

I cannot tell you how many days it usually takes, because it depends on the platform, the type and whether your documents were complete. Anyone quoting a specific number is making it up. What can be said is direction:

And one thing that may not land well but should be said: if everything you own sits on one platform, any restriction is a total event for you. Diversifying is not about returns, it is about turning moments like this into partial problems. How much to split and how far is at the end of signs a platform is in trouble.