Challenge-response sessions
Active sessions use bounded actions, deadlines and server-judged steps rather than accepting a client-declared liveness flag.
LIVENESS SECURITY
Selfie capture and actual liveness verification—kept separate.
A selfie is evidence capture, not proof that a live person was present. A liveness workflow must issue a real challenge, evaluate the response, handle spoof/replay signals and store the provider-backed result.
Capabilities built around the actual customer journey.
Implementation and testing status is stated separately from commercial activation, so your team can evaluate what is genuinely available.
Replay and spoof controls
Frame timing, near-replay hashes, subject consistency and failed/review states help prevent static or reused evidence from becoming approval.
Fresh capture for reusable KYC
Saved-document reuse supplies only eligible document evidence. It never stages or skips a new selfie and liveness sequence.
Fail-closed availability
If the configured provider or evaluator is unavailable, the workflow remains unavailable or review-required instead of fabricating success.
Where this can be used.
- Live customer onboarding
- Repeat KYC with fresh evidence
- Spoof and replay review
- Sandbox liveness-pilot evaluation
- Provider acceptance planning
A controlled implementation path.
- 1Initialize camera permission and capture
- 2Issue the configured liveness challenge
- 3Evaluate timing, quality and spoof signals
- 4Record the actual provider result
- 5Use retry, review or unavailable states honestly
Current availability and acceptance limits
General production ACTIVE liveness is off. The current pilot is sandbox-only. Worker challenge and anti-replay logic have synthetic integration evidence, but that is not real-provider acceptance and does not make paid liveness commercially ready.
Frequently asked questions
Is selfie capture the same as liveness?
No. A selfie is only an image. Liveness requires an actual challenge/evaluation and a provider-backed result.
Can reusable KYC skip a new liveness check?
No. Fresh selfie and liveness is a non-overridable invariant for saved-document reuse.
What happens when the provider is unavailable?
The flow fails closed or remains review-required. It does not return LIVENESS_APPROVED or claim a successful provider result.
Evaluate the exact workflow before you go live.
Review the documentation, test the actual document and provider path, or ask our integration team for a scoped technical assessment.