Binance Facial Verification Failed? Run a 60-Second Check First

Run a 60-second check before you retry

When face verification fails, don't press Retry straight away. Spend a minute on these four things:

• Keep your full face clearly visible and centered, with your eyes open. Remove hats and glasses and do not use a beauty effect or filter.
• Use enough light for facial features to be visible. Avoid a strong light behind you that darkens the face; clean the lens if it is smudged or covered.
• Hold the device steady and complete the on-screen steps in order. Do not switch apps, refresh the browser, or let your face leave the frame during capture.
• Use a connection that can complete the upload. If the page shows a specific network error, note the wording and deal with that error.

If a nod or head-turn prompt won't register, keep your whole face inside the frame for the entire movement and make sure nobody else is in the shot. If the web flow keeps stalling, start again and choose the QR code option at the ID-upload step to finish on your phone (see State 1). If the screen tells you to wait, stop and wait. Binance's guide says little about the movement itself; the detail is in the nod and head-turn section below.

If all four are fine and it still fails, write down where the screen stopped, the exact wording and how many attempts you've made, then work through the five states below. A camera that never opens is a different problem from a completed capture followed by a denial: the first starts with permission and the entry point, the second with the ID, your personal details or platform review.

Binance's current personal identity-verification guide says your full face should be clearly visible and centered, your eyes should be open, you should not wear hats or glasses or use filters, and lighting should be sufficient. On the website, the document step also offers a QR code so you can continue on your phone. Binance also warns not to refresh the browser during the process and not to quit the verification flow in the app.

Which of five states you are in

Choose the state that matches what you can actually see, and troubleshoot only that stage:

1. The camera is black, permission is denied, or capture never opens. You are before face capture. Fix camera access and the web/app entry point.
2. Your face appears, but framing or liveness capture does not complete. Follow the live prompt and correct face visibility, centering, lighting, and obstructions.
3. Capture completes, then the verification application is denied. Do not only change the lighting. Recheck the document image and the consistency of the personal details.
4. The screen tells you to wait before trying again. Stop retrying and follow what it says; Binance's public guide gives no number.
5. The account requests more documents, manual review, or support. Submit only through official entry points. If needed, the Binance team may initiate a video check.

If the message is unclear, the face-failure diagnostic tool can help you label the state. It is a routing aid, not a substitute for the in-account prompt or an official support decision.

State 1: camera is black or capture will not start

The platform does not yet have a usable face image, so do not begin by wondering whether your face matches the ID. Work through the shortest relevant checks:

• Confirm camera access is allowed. Binance's official flow explicitly requires camera permission. If the browser or operating system was previously set to Block, allow it for the current site or official app.
• Close another application that may be using the camera, then return through the Binance website or official app. Do not log in through a lookalike result or hand your ID to a remote “verification helper.”
• If the web flow keeps stalling, use the QR option the page offers at the document step to continue on your phone. Binance documents this as a normal route, but it is not evidence that a phone always has a higher pass rate.
• Once capture begins, do not refresh or leave the process. The web instructions warn against refreshing the browser; the app instructions warn against quitting the verification flow.

Once the camera displays your face normally, stop using the “camera would not start” route and move to the capture checks below.

State 2: your face appears but capture fails

Follow only the action prompt visible in the current flow. Old videos may tell users to blink, turn, open their mouth, or read digits, but prompts can vary by device, region, and flow version. Adding an action that is not currently requested makes the failure harder to diagnose.

Before a new attempt, go back through the 60-second check at the top, and don't assume every capture failure is the connection.

In that check, the face, hat, glasses, and filter points and the no-refresh warning come from the current public guide; the backlight, lens, steady-device, and connection points are our own troubleshooting habits. We did not sign into an account or submit a real face for this update, so we do not claim that a certain wall color, phone model, or movement has a better success rate.

A nod or head-turn prompt that won't register

If the prompt asks you to nod or turn your head and the capture sits there however many times you do it, Binance's public guide won't tell you much more: the website steps say only to follow the instructions on the screen, and the app steps say to center your face in the frame and follow the instructions. It doesn't describe the movements themselves. What it does list is in the checklist above (face visible and centered, eyes open, no hat, glasses or filter, enough light), plus camera access, which the website steps ask you to turn on. Keeping your face inside the frame for the whole movement is our reading of "centered"; the guide doesn't spell it out.

Check that nobody else is in the shot, too. Binance has a separate FAQ for accounts whose withdrawals were suspended after face verification picked up someone other than the account holder; getting them back takes a video with everyone who appeared, sent to customer service, which is a lot more work than a clean retake on your own. If the movement still won't register and the screen puts you on a wait, go to State 4 below; if the account asks for documents or a video check, go to State 5.

State 3: capture completes, then the application is denied

A completed face capture does not prove that the cause sits in the face step. Binance asks that all the personal information you enter is consistent with your ID documents. Also check that the ID photo you uploaded is complete and readable, with no edge cropped off. Because confirmed personal information cannot simply be edited within that flow, check the upstream record before taking more face captures.

• Compare the name, date of birth, document country or region, and document type against the document you submitted.
• Review whether the document image is complete, readable, and uncropped. If you need to organize the items first, use the KYC checklist generator.
• Do not use another person's ID or ask someone else to complete the face step. Binance's guide says an account cannot be transferred to another person and another person's ID cannot be substituted for yours.

If you correct the details and submit again, note that Binance's FAQ says submitted documents are usually reviewed within 48 hours, though some cases take longer. That is its general wording, not a promise from this site; use the case status and support response for the actual timing.

State 4: the screen tells you to wait

If the screen tells you to wait before trying again, stop and follow the time or instruction it gives. When we re-read Binance's personal identity-verification guide on September 12, 2026, it gave no daily attempt number and no fixed waiting period, so what your account shows is what counts. An earlier version of this page cited a 10-attempt, 24-hour rule from that guide; the guide does not contain it, and the corrections log records the change.

Use the wait to check permission, document details, and capture conditions, but no one should promise the next attempt will pass. We also do not claim that repeated clicks extend the wait; the official page cited here does not say that.

Until the face check clears, the account can't take deposits or trades, so if you registered less than 30 days ago, this gap is also when you can still add a referral code you skipped at sign-up. Question 4 of Binance's Referral Pro FAQ allows it within 30 days of registration when the account has no deposit or trading activity, has no referrer yet and meets a few other account conditions; you do it logged in, on the Bind Referral Pro Code page. If you'd like to use ours, the code is BTC9188 (the Binance sign-up walkthrough shows where it goes and how a late bind works). The chance ends at day 30 or with your first deposit, whichever comes first.

State 5: documents or support video review

If the account asks for a supplementary document, use the checklist shown inside the account rather than an upload link sent through a third-party chat. If self-service cannot complete, contact Binance customer-service live chat from the official Help Center and state that face verification failed, including the exact wording and stage.

Binance publishes a separate support video-verification process. It is not a number that users call directly:

1. The user first raises the identity-verification problem through official customer-service live chat.
2. The Binance team reviews the case and, if a video check is necessary, the team calls the user.
3. Before the call, prepare the same document used for KYC, a well-lit location, a quiet place with clear audio, and the consent required by the page.
4. During the call, follow the agent's request to show yourself and the document. The result or next requirement returns through the customer-service chat.

The public instructions explicitly say that users cannot call the team; the team calls the user. An off-site stranger who initiates a call, asks for an authentication code, or wants remote screen control is not following this published process.

Face-data and off-site-help boundaries

Binance's Privacy Notice dated January 5, 2026 says it may collect biometric information and compare a facial scan generated from a selfie or video with the photograph in a government-issued ID to meet identity-verification requirements. The notice also describes KYC and anti-money-laundering providers that may process relevant data in the stated circumstances. Legal bases, rights, and handling can vary by jurisdiction.

Keep convenience separate from data boundaries: submit only through Binance's official domain, official app, or a verification route clearly linked from inside the account. Do not send an unredacted ID, selfie video, password, or authentication code to a forum user, group administrator, or paid agent. For the precise processing basis and your rights, read the current privacy notice rather than relying only on this summary.

What to record before contacting support

Support can see internal state, but a precise description still prevents the case from being routed to the wrong step. This is our organizing template, not a mandatory Binance form:

• Failure stage: camera did not open, capture did not complete, capture completed and was denied, or the screen told you to wait.
• Exact prompt: copy the wording. If you take a screenshot, cover your name, document number, QR code, and all account information.
• Time and attempt count: record local time and how many attempts you made before the wait appeared, so support can see whether it still applies.
• Entry point and device: web or official app, operating-system or browser major version, and whether camera access is allowed.
• Checks already completed: list only actions you actually took. “Tried everything” does not identify a state.

If support gives you an appeal or manual-review route, use the Binance verification appeal and manual-review guide to organize the requested material.

Frequently asked questions