Start
Your server creates the liveness session and passes an opaque token.
Face Liveness
Establish presence. Connect it to identity.
A short, guided camera experience verifies that a real person is present and can compare the live frame with a known identity.
Presence detectedLive · 99.2%
ID portraitLive frameMatch
Guided, not mysterious
A few seconds to prove there is a person there.
The person consents, allows camera access, and follows the on-screen guide. AWS Rekognition Face Liveness evaluates the capture and Mojo Verify returns a confidence result. When a reference face is available, the same flow can return a face match.
≈5 secguided captureLivepresence confidenceMatchoptional reference face
01 / Flow
From consent to result.
A focused experience keeps the person moving while your backend keeps control of the session.
Consent
The person sees what the camera check does before proceeding.
Capture
A guided camera flow evaluates the live presence signal.
Result
Receive confidence plus an optional reference-face comparison.
02 / Modes
One liveness engine, three useful contexts.
KYC verification
Pair liveness with government ID so the live person can be connected to the portrait on the document.
Standalone proof
Run presence detection when you need a live-human signal without a complete identity workflow.
Supervised or kiosk
Embed the focused capture experience in a controlled onboarding or check-in flow.
Privacy by contract
Use opaque client tokens and temporary credentials. Keep detailed results behind authenticated server calls.
Request liveness
Compose it with the rest of KYC.
Enable liveness when you create a verification request, or start it as a focused standalone session.
Read the liveness docs{ "require_liveness": true, "require_gov_id": true, "notification_method": "both" }liveness.completedconfidence · face match
A stronger human signal
Know who is really there.
Pair a clean liveness experience with the identity and risk evidence your workflow needs.
Talk to Mojo Verify ↗