Face Verification Failed
Understanding and fixing this common KYC rejection
⚠️ What This Error Means
Face verification failed means the biometric check that compares your live selfie to your ID photo could not confirm you are the same person, or could not even complete the scan. It is a catch all result, not a single specific problem, and it covers everything from a camera that never turned on to a match score that came in a few points too low.
The important thing to understand is that this error hides two very different situations behind one message. A technical failure means the system never got a usable scan in the first place, because the camera permission was blocked, the connection dropped mid scan, the app crashed, or too little of your face was actually in frame. A confidence failure means the scan completed just fine and the system did get a clear look at your face, it simply decided the similarity between your live selfie and your ID photo did not clear the threshold it needs to approve you.
These two situations need completely different fixes. If the scan never finished, retaking a photo in better lighting will not help you, since the problem is your camera access or your network, not your face. If the scan finished and still failed, checking your permissions is a waste of time, and the real issue is how closely you resemble your ID photo in that specific frame. Most platforms show the exact same generic message for both, which is why figuring out which bucket you are actually in is the first real step, not the last one.
✅ How to Fix It
- Check camera permission first. Confirm the browser or app actually has camera access at the system level, not just inside the app's own settings, since a blocked OS level permission is one of the most common causes of an instant failure.
- Get on a stable, VPN free connection. Live face scans stream data in real time, so a connection that drops or slows mid scan can kill the attempt without ever showing you a connection error, it just shows "failed."
- Close anything else using your camera. Video calls, other camera apps, or a stuck background tab can all hold the camera open and cause the scan to crash or freeze partway through.
- Fix your lighting and framing. Face a light source directly so your whole face is evenly lit, hold the device at eye level, and make sure your entire face stays inside the frame with nothing cropped off.
- Remove glasses, hats, and anything covering your face. Pull hair back from your forehead and brows so the system has a clean, unobstructed view to work with.
- Match your current appearance to your ID photo. Keep a neutral expression and reduce the visual gap between how you look right now and how you look in the document, since this is what actually moves a low confidence score.
Technical Failure vs Confidence Failure
Use what actually happened during the scan to figure out which category you are dealing with before you try again.
| Symptom | Likely Cause | What To Do |
|---|---|---|
| Scan freezes or the app crashes partway through | Technical failure, usually a connection drop or another app holding the camera | Close other camera apps, confirm a stable connection, restart the flow fresh instead of resuming |
| Error appears instantly with no scan attempt at all | Technical failure, almost always a blocked camera permission | Check OS level camera permission for the app or browser, not just in-app settings |
| Scan completes fully, you see your face on screen, but it still fails | Confidence failure, your match or liveness score came in below threshold | Fix lighting, remove glasses or hats, match your expression to your ID photo, then retry |
| Fails only on this device, worked fine for someone else or on another device | Technical failure specific to that device's camera, browser, or OS settings | Try a different device or updated browser before assuming anything is wrong with your identity data |
| Fails repeatedly even with perfect lighting and a clean, centered face | Confidence failure tied to a real gap between your current look and your ID photo | Stop retrying blindly, contact support and ask about manual review |
Let Us Help You Fix This
Try our free AI analysis first, or let our experts fix it for you.
Frequently Asked Questions
Is face verification failed the same as face not matching?
No. Face not matching is one specific cause inside the broader face verification failed category, meaning the system got a clean scan but your similarity score came in too low. Face verification failed can also mean the scan never completed at all, due to a camera, connection, or app problem.
Why does it fail every time on my phone but worked on a friend's device?
This points to a device specific technical issue rather than your face, things like an older camera sensor, a browser that handles camera permissions differently, or background apps holding the camera open. Try the exact same verification link on a different device before assuming anything is wrong with your identity data.
Does a bad internet connection cause this error?
Yes, this is one of the more common technical causes. Live face scans usually stream data to a server in real time, and if your connection drops or slows mid scan, the system often cannot finish processing and returns a generic failure instead of a clear connection error.
How many times can I retry face verification?
Most platforms allow a handful of attempts, often three to five, before locking the flow or pushing you into manual review, though the exact number is rarely published. If two clean attempts under good conditions both fail, stop retrying blindly and check whether the issue is technical or a match score problem first.
Can lighting alone cause a face verification failure?
Yes, on both sides of this error. Poor lighting can stop the system from detecting enough face in frame in the first place, which reads as a technical failure, and it can also degrade the image enough to drop your match confidence score, which reads as a confidence failure.