If your app matches a face — at onboarding, at a gate, in a KYC step — you need to know the face is real and present, not a printed photo or a replayed video. A Face Liveness API adds that defence without you building anti-spoofing yourself.
What liveness solves
Face matching answers does this face match the record; liveness answers is this a live person right now. Without it, print and replay attacks — and increasingly synthetic faces — slip through. See liveness detection and anti-spoofing and why deepfakes make it matter more.
How the integration works
- Your app captures a live selfie in your own UI.
- You call the Face Liveness endpoint with the capture.
- You get back a liveness result — and, where you have a reference photo, a match score.
- Your flow decides: pass, escalate to a human, or retry.
Passive vs active
Passive liveness analyses a single capture with nothing extra asked of the user — fastest and least intrusive. Active liveness prompts a small action for higher assurance. Choose based on your risk and friction tolerance.
Handle the face data responsibly
A face image is personal, and potentially sensitive, data. Keep the check consent-based and purpose-limited, and don't build a face database on the side — in line with biometric data and the DPDP Act. This is general information, not legal advice.
Face Liveness with Certopact Verify
The Certopact Verify Face Liveness API lets you add anti-spoofing liveness to your own app, alongside the OVSE API. For the full identity product with screens built in, see Certopact Entry.