Identity verification keeps failing? Work through it in this order
The standard advice is to upload the document again. If the document were the problem it would have failed the first time for a reason the notice would have named — and usually it did not.
In one line: verification is two separate checks that fail for unrelated reasons. Work out which one rejected you before you change anything, then change one variable at a time.
The single highest-yield change: light. Even, front-on, nothing bright behind you. A large share of face-check failures are a backlit silhouette and nothing more.
First: which half rejected you
Verification is a document check and a liveness check bolted together. They fail for entirely unrelated reasons, and the fix for one does nothing for the other.
- The document check is a data problem: is the document valid, legible, unexpired, and does the extracted data match what you typed?
- The face check is an imaging problem: can a live capture be matched against the document photo?
Most people who get stuck are failing the second and fixing the first. They resubmit a perfectly good passport ten times and conclude the platform is broken.
How to tell which: the flow itself usually tells you, by where it stopped. If you never reached the camera step, it is the document. If you completed the camera step and were rejected afterwards, it is more likely the face check or a mismatch between the two. And the rejection notice, if it says anything specific at all, says which — see below.
Document problems
In rough order of how often they are the actual cause:
- Expired. Check the date before anything else. It is the most common cause and the least suspected, because people know their document and do not re-read it.
- Glare. Laminated cards and holographic security features reflect. Move out of direct overhead light and away from windows; indirect, diffuse light is what you want. Tilting the document a few degrees usually solves it faster than rearranging the room.
- Cropping. All four corners inside the frame. Some checks read the machine-readable zone along the bottom edge, and a crop that clips it fails silently.
- Name mismatch. Enter the name exactly as printed on the document — same order, same hyphens, same accents, same transliteration. If the document renders your name in a form you never use, use the document's form. This is a string comparison, not a person reading it.
- Not the original. A photocopy, a scan displayed on a screen, or a photo of a photo will generally be detected. Use the physical document.
- Wrong document type for your region. Which documents are accepted differs by country. If your national ID card keeps failing, a passport is often the more reliably accepted option.
Face-check problems, in order
Change one variable at a time, cheapest first. The reason for the discipline is practical: some accounts hit a retry cap and have to wait, so scattergun attempts burn your budget and teach you nothing about which change helped.
- Light. Face a window or a lamp; do not have one behind you. Backlighting turns your face into a silhouette and defeats the comparison outright. Avoid strong side lighting too — half a face in shadow is nearly as bad. This one change resolves more cases than everything below it combined.
- Occlusion. Glasses off — reflective lenses are worse than they look. Hat off, hair off the forehead, mask off, earphones out. Anything that shadows or covers the face is a candidate.
- The lens. Wipe it. A phone camera that lives in a pocket is smeared, and the result is a soft image that fails matching without looking obviously wrong to you.
- The device. If it still fails, switch. A recent phone's front camera substantially outperforms a typical laptop webcam, and moving from laptop to phone resolves a meaningful share of stubborn cases on its own.
- Distance and motion. Eye level, arm's length, face filling the guide. Follow the prompts slowly — rushing the head turn is a common cause of a failed capture that gets blamed on the document.
- Connection and app version. A capture interrupted mid-upload can present as a rejection. Use a stable connection; update the app; if you were on the web, try the app, or the reverse.
- Appearance versus the document photo. If your document photo is a decade old, or your appearance has changed substantially since, the match is genuinely harder. Nothing to do here except try to present as close to the document photo as is reasonable, and expect to end up in manual review.
Reading the rejection notice
Whatever text you were given is the most reliable information you have. Read the words literally. "Document unclear" and "information does not match" point at different halves; "unable to verify" usually means it went to review rather than being rejected on a specific criterion.
When the notice says nothing specific, work the list above from cheapest change to most expensive. Do not invent a diagnosis from other signals.
When to stop retrying
Stop and open a support ticket when any of these is true:
- You have genuinely worked the list — different light, different device, no glasses, document in date — and it still fails.
- The notice points at something you cannot change, such as a region or document-type restriction.
- You have hit a retry limit.
- Your submission has been in review for a long time. The common advice is that resubmitting during an open review sends you back to the end of the queue; we have not found an official source that says so, so treat the mechanism as unverified. What holds without it: there is no published way for a resubmission to speed up a review, so the cautious default is to wait for a decision and then act on what it says.
What makes a ticket effective: the exact wording of the rejection, the timestamps of your attempts, and a plain list of what you have already tried. That last item is what stops the reply being a copy of the checklist you already worked through.
Support has to go through the platform's own official help centre. There is no third party with an inside line, and anyone who offers one is running a scam whose mark is specifically people stuck at this step.
Two things that make it permanently worse
Do not use someone else's documents. Not a family member's, not a purchased set. It usually gets through the door and then fails at exactly the wrong moment — when you try to withdraw, and the identity on the account does not match the person operating it. That is not a warning; that is a frozen balance and no path to recover it, because you cannot prove ownership without admitting the problem.
Do not open a second account to bypass the first. Binance's Terms of Use limit each user to one account, so the duplicate is not a second chance — it sits outside the terms from the moment it exists. What the platform does about such an account is not written into the terms, and we are not going to predict it for you. If you were doing this to recover a missed referral code, it is an even worse trade: swapping a working account for a doubtful one to save a fraction of a percent on fees. If you believe your situation genuinely is an exception, ask official support rather than testing it.
The uncomfortable but honest ending: sometimes verification does not succeed, for reasons of region, document type or policy that you cannot influence. If you reach that point, the answer is to accept it rather than to route around it. Every technique for routing around identity verification ends with an account you cannot get money out of.