What Happens During Those Hours in the Review Queue

Search how long verification takes and you get a spread: a few minutes, a few hours, one to three working days, two or three weeks if it stalls. Those numbers contradict each other because they are measuring different things — some describe the automated stage, some the total once a case has gone to a human.

The better question is: which stage am I in right now? Because the stages behave differently. In one, waiting is exactly right. In another, waiting will never produce anything. In a third, there is something for you to supply.

The stages, and which ones need a person

There is one verifiable anchor. On its proof-of-address page, one platform states that a proof of address may take one to two working days to review, after which you will be notified automatically with no need to contact support. Set that against the first two rows and the structure is visible: the seconds-scale stages and the working-days-scale stages were never the same thing.

On the automated side there is a public figure worth knowing: NIST's September 2023 evaluation tested 82 purely software-based face presentation attack detection algorithms from 45 developers. These run on ordinary 2D imagery and are built to return in seconds. So if you have been waiting a day, that is almost certainly not what you are waiting on.

Why queues form at all

Not simply understaffing — it is structural. Automated capacity scales almost without limit; human review does not. So the moment any condition routes you off the automated path, you are in a categorically different queue.

The usual routing conditions, described generically rather than for any platform's implementation:

• the automated stage returned a borderline score — not confident enough to pass, not clear enough to reject;
• screening produced a near match that a person has to adjudicate;
• you submitted something that has to be read, such as a proof of address or a source-of-funds explanation;
• your situation does not fit the template — a single name, a non-Latin script name, a document and residence in different countries, an unusual address format;
• enhanced due diligence was triggered — the higher-risk band in the regulations.

That last one has a clear legal source: Article 18(1) of Directive (EU) 2015/849 requires obliged entities to apply enhanced customer due diligence measures in the specified cases and other cases of higher risk. The contractual counterpart is clause 7.4: additional information, further records or documents, or a face-to-face meeting with a representative may be required. At that point, waiting is no longer the only available move.

Why the rules allow an account before the check

Worth explaining: why do some flows let you register, and sometimes deposit, while verification is still pending?

Not a loophole — a written rule. The default in Article 23(1) of Regulation (EU) 2024/1624 is that verification shall take place before the establishment of a business relationship or the carrying out of an occasional transaction. Two derogations follow:

• paragraph 2: verification may be completed during the establishment of a business relationship where necessary so as not to interrupt the normal conduct of business and where there is little risk of money laundering or terrorist financing, to be completed as soon as practicable after initial contact;
• paragraph 3: a credit or financial institution may open an account provided there are adequate safeguards ensuring that transactions are not carried out by the customer or on its behalf until the relevant customer due diligence measures are complete.

Paragraph 3 is precisely the confusing in-between state: the account exists, you can log in, and you can do nothing. Not a malfunction — the rule as drafted. The same logic explains withdraw-only style states for unverified accounts, covered separately in using an account without completing KYC.

Why a rejection often has no reason attached

The most maddening part, and it has two distinct causes. Neither is a support agent fobbing you off.

Contractual: clause 20.2(b) of Binance's terms states that decisions to terminate, suspend or restrict may be based on confidential criteria essential to its risk management and security protocols, and that it is under no obligation to disclose the details of those procedures to you.

Regulatory: anti-money-laundering regimes carry a no-tipping-off principle, and to make it work Article 41(4) of Directive (EU) 2015/849 requires Member States to legislate to restrict, in whole or in part, the data subject's right of access, so as not to obstruct enquiries. In some situations, not telling you is a legal requirement rather than a choice.

Setting these out is not resignation. It is so you stop spending effort on extracting a reason. What is adjustable is the input, not the explanation. The boundaries of the related rights are in where your identity documents actually go.

Wait, act, or supply: telling them apart

1. A failure returned within seconds is the automated stage. Change the input and go again: lighting, obstruction, filters, document legibility. Mechanics in what a liveness check is actually testing; to sort yourself into a category, the face failure self-check. Nothing here needs waiting for.
2. “Under review” usually means you have left the purely automated path. Waiting in working days is reasonable. Resubmitting repeatedly returns you to the back of the queue, and most flows cap attempts.
3. A request for more documents is good news. It means the case is alive and it has told you what is missing. Supply exactly that; do not attach unrelated extras.
4. Count weekends and local public holidays. “One to two working days” is not one to two days.
5. Contacting support only helps once you are clearly past the stated range. Inside it you will get the same automated reply — the proof-of-address page itself says you will be notified automatically and need not contact support.

Questions people actually ask