First: which half rejected you
Every mainstream verification flow is two checks bolted together, run by different systems, failing for different reasons.
The document check
This one reads your identity document: it looks for the security features it expects on that document type from that country, extracts the printed fields, and compares them to what you typed into the form. It is essentially a reading task. It fails when it cannot read something, or when what it read does not match what you claimed.
The face check
This one does two things at once: it decides whether it is looking at a live human rather than a photo, a screen or a recording, and it compares that face to the portrait on the document. It is essentially a photography task, and it fails for photography reasons — light, angle, motion, sensor quality.
How to tell which one you failed
Look at where the flow stopped, not at the wording of the message. If you were bounced before the camera step ever opened, it is the document. If you got as far as being asked to turn your head or blink and then failed, it is the face check. If the notice arrived minutes or hours later by email, it went to a human reviewer, and the reason will be more specific than anything the automated stages produce.
This matters because the two have almost no overlap in remedies. Retaking your document photo does nothing for a lighting problem, and moving to a window does nothing for a document whose expiry date has passed. Most people who are stuck are applying the fix for the half that did not reject them.
Set the room up before the next attempt
Almost everyone retries in exactly the conditions that just failed, because the retry button is right there. Two minutes of setup beats five more attempts.
- Face a window or a lamp, do not sit in front of one. The camera exposes for the brightest thing in frame. If that is behind you, your face becomes a dark shape.
- Take your glasses off, and anything on your head. Reflections in lenses defeat the face-matching stage more often than people expect.
- Find a plain wall. Busy backgrounds, other people in frame, a television playing — all of it gives the liveness check things to be uncertain about.
- Clean the camera lens. A phone that lives in a pocket has a film on it, and the result is a soft image that reads as a photograph of a photograph.
- Get on a stable connection. The face check uploads video. A connection that drops halfway produces a failure that has nothing to do with your face.
- Charge the phone past 30%. Low-power mode throttles the camera on many devices.
Document problems
The document itself
- Expired, or expiring within a short window. Some checks reject a document that is technically still valid but close to its expiry date.
- A type the platform does not accept from your country. The accepted list is per-country, not global. A document that works for one nationality may not be on the list for another, and the notice rarely explains this.
- Physical damage across a security feature or the photo. A crease through the portrait is worse than a crease through a corner.
- A copy, a scan, or a photo of a screen. Modern checks detect all three. The document has to be the physical object, in your hand, in the room.
The capture
- Glare on the laminate. The single most common document failure. Tilt the document rather than the camera, and move away from any point light source overhead.
- Cropped edges. All four corners inside the frame, with a margin. The check uses the edges to confirm the document shape.
- A shadow across the print. Usually your own hand or head. Move the document, not the light.
- Motion blur. Rest your elbows on a table. The autofocus needs a stationary subject and half a second.
- Both sides, when both sides are asked for. An ID card's back carries fields the check wants, and half of the submissions that "keep failing" are missing it.
Name and date mismatches
This is the failure that looks like a system error and is actually a typing error. The extracted fields have to match the form. Common causes: middle names present on the document but not in the form, a name order reversed, diacritics dropped, a date entered in the wrong format, a place of issue confused with a place of birth.
Fix it by copying what the document says, character for character, including the parts that look redundant. The check does not know which of your names you normally use.
Face-check problems, in order
Change one thing at a time and retry. Changing four things at once tells you nothing about which one mattered.
1. Light
Even, from the front, no bright window or lamp behind you. If you can only find one light source, put it between you and the camera at head height. Overhead light alone produces shadows in eye sockets that the matcher dislikes.
2. The device
Phone front cameras are generally better at this than laptop webcams, and phone apps usually implement the capture step more carefully than a browser can. If you have failed twice on a laptop, switching to the phone app is the highest-yield single change after light.
3. What your face is doing
Neutral expression, eyes open, mouth closed, face square to the camera and filling the frame as instructed. When it asks you to turn your head or blink, do it slowly — the instinct is to do it fast, and fast reads as a glitch rather than a movement.
Remove anything the document photo does not have: hat, mask, headphones, heavy makeup that changes face shape. Facial hair that has appeared or disappeared since the document photo is a legitimate mismatch and sometimes needs a human reviewer.
4. What is behind you
Plain wall. No other faces, no screens, no posters with faces on them. The liveness check is looking for reasons to be suspicious, and a second face in frame is a good reason.
Reading the rejection notice
Rejection messages come in three flavours, and they carry very different amounts of information.
- Instant and generic — "verification failed, please try again". An automated stage. The cause is almost always capture quality. Change the environment, not the paperwork.
- Instant and specific — names a field, a document type or an expiry. Believe it literally. This one is telling you exactly what to fix.
- Delayed, arriving by email — a human looked at it. The reason given is the real reason, and it is worth reading twice before you resubmit anything.
Keep the notices. If this ends in a support ticket, the sequence of messages is the most useful thing you can attach.
When it asks for proof of address
Higher verification tiers, and some jurisdictions at any tier, ask for a document proving where you live. This is a separate check again, with its own rules, and it fails for its own reasons.
- It must be recent. Usually within three months. An older statement is rejected on the date alone.
- It must show four things together: your full name, the full address, the issuer, and the issue date. A screenshot showing only the address will not do.
- The address must match the form. Including the parts you would normally abbreviate.
- Mobile phone bills are frequently excluded, and so is anything you could plausibly have produced yourself. Bank statements and utility bills are the reliable options.
- A downloaded PDF is usually fine, a photo of a screen usually is not — the same rule as documents.
When the country field is the real problem
Sometimes nothing about the photograph is wrong. The account was opened under one country and the documents say another, or the country you selected has a restricted feature set, or the platform does not serve it at all. Verification then fails in ways that read like a technical fault and are not.
The check that costs five minutes: open the platform's own terms and its list of restricted jurisdictions, and confirm your country is served for the account type you want. Do that before the next retry, because no amount of lighting fixes a policy.
If you have genuinely moved country since opening the account, that is a change-of-residence request through support, not a re-verification. Doing it in the wrong order — resubmitting foreign documents against an old country setting — is what produces the mismatch failures people then cannot explain.
When to stop retrying
Stop after two failures with the same message and no change in between. Beyond that you are consuming attempt allowance, and most platforms have one — sometimes per day, sometimes per document, sometimes before a cooling-off period starts.
The sequence that works is: fail, read the notice, change exactly one thing, retry. If two deliberate changes have not moved it, the next step is support rather than a third guess.
Writing a support ticket that gets read
Support tickets about verification get resolved fast or slowly depending almost entirely on how they are written. A ticket that says "KYC not working, please fix" starts at the back of the queue.
Include, in this order:
- Document type and issuing country. The first thing a reviewer needs.
- Which stage failed — document upload, or the camera step — and how far it got.
- The exact wording of the message, copied rather than paraphrased, plus the time it appeared.
- What you have already changed between attempts. This is what stops the reply that tells you to try better lighting.
- How many attempts you have used.
Then wait. Opening a second ticket about the same issue usually resets your position in the queue rather than escalating it.
One thing worth being blunt about: the support channel you reach by logging in yourself is the only one. Nobody who contacts you first — by direct message, by phone, in a comment reply — works for the platform, however much they know about your problem.
Things that make it permanently worse
- Using someone else's documents. Verification ties an identity to an account permanently. Once it is done with the wrong identity, every later dispute, recovery and withdrawal belongs to that person and not to you. This is the single most expensive mistake in this entire subject.
- Buying a "verified account". Same problem, plus the seller keeps a copy of the credentials and the recovery route.
- Editing the document image to fix glare or brightness. Manipulation detection catches it, and a manipulated submission is treated as fraud rather than as a bad photo.
- Opening a second account to start over. Duplicate accounts are usually detected and closed together, and now the original problem has a policy violation stapled to it.
Questions people ask afterwards
How long does verification take when it works?
The automated path is minutes. Anything that goes to a human reviewer is measured in hours to days depending on queue depth, and queue depth spikes when markets do. A delay is not a rejection, and resubmitting during the wait can put you back at the start.
Can I use a passport instead of a national ID?
Usually, and it is often the better choice: passports are the most consistently recognised document type across systems because the format is internationally standardised. Check the accepted list for your country first.
My name has changed since my document was issued. What now?
Use the name exactly as printed on the document you are submitting, and raise the change with support separately. Entering the new name against an old document is a guaranteed mismatch.
Why did it work on my phone after failing on my laptop?
Because the camera and the capture code are both better. The phone app controls exposure, focus and the frames it sends; a browser gets whatever the webcam produces. This is not a trick, it is the intended path.
Does failing verification hurt my account?
Failed attempts themselves do not. What hurts is exhausting attempt limits, and submitting anything that looks manipulated or belongs to someone else. Those go on the record.