Liveness check
Confirm a real person is present
Use active, passive, or adaptive liveness methods to detect presentation attacks and add proof of presence to an identity workflow.
- Configurable workflow
- Hosted, API, and webhooks
- White-label experience
Proof of presence
A selfie is useful only when the capture is genuine
Replay videos, printed images, masks, deepfakes, and injected streams can imitate a real user. Liveness adds a configurable real-presence check before a verification decision.
Passive liveness
Use a short prompt-free capture for lower-friction sessions and baseline presentation-attack protection.
Active liveness
Use guided actions when a session requires a stronger, interactive proof of presence.
Adaptive liveness
Select or step up the liveness method according to configured workflow and risk signals.
How it works
Liveness in four steps
The experience stays short while the decision logic remains configurable.
Prepare the user
Clear on-screen guidance helps the user position their face, remove obstructions, and improve capture quality.
Capture a selfie video
The browser or application records a short passive or guided active capture.
Analyze presentation signals
The liveness process evaluates configured indicators associated with replays, masks, deepfakes, and stream injection.
Return a result
The session can pass, fail, retry, or continue to Face Match or review according to workflow rules.
Capabilities
Balance assurance and completion
Apply the liveness mode that matches each part of the customer journey.
Discuss your workflow- 01Active prompts
- 02Passive capture
- 03Adaptive step-up
- 04Replay and screen-presentation checks
- 05Stream-injection defenses
- 06iBeta Level 2 ISO 30107-3 certification
Use cases
Where liveness fits
- Pre-arrival guest verification
- Remote onboarding
- Face Match workflows
- Account recovery
- Authentication step-up
- Sensitive account actions
Security and compliance
Built for controlled identity workflows
Apply configured access, evidence, retention, and result-handling rules while using the approved security and compliance controls of the DocinVault platform.
Level 2 ISO 30107-3
CCPA compliant
SOC 2 Type 2
eIDAS compliant
FAQ
Frequently asked questions
Key implementation and workflow questions for liveness check.
What is the difference between active and passive liveness?
Passive liveness uses a short capture without user prompts. Active liveness asks the user to complete guided actions. The workflow can select either method or use adaptive routing.
Does liveness prove the user owns the document?
Liveness proves presence. Pair it with Face Match to compare the live capture with the portrait stored on an identity document or supported NFC chip.
Which certification supports DocinVault liveness?
The approved liveness technology is iBeta Level 2 certified against ISO 30107-3 for biometric presentation attack detection.
Configure your flow
See Liveness check inside a DocinVault workflow
We will map the module to your customer journey, operating market, and review requirements.