Use cases
Account recovery
Compare a returning user with a stored reference face before you restore access.
The job
A user has lost the password, the phone or the second factor, and asks for access to an existing account. Your product has to be sure that the person asking is the person who owns the account. A password reset by email cannot answer that when the email itself is the problem.
The flow
- The request. The user asks for recovery in your product. This step is yours.
- The session. Your backend starts a verification session for the user. If the user is at a computer, a QR code moves the user to a phone.
- The comparison. The returning user is compared with a stored reference face.
- The result. Your backend reads the session status, or a webhook tells it that the session is complete.
- The decision. Your product restores access, asks for another attempt, or leaves the case to a reviewer, who can make a manual decision in the dashboard.
Scenario setup
Write to us and we will set up the comparison with you for your flow.
What your system receives
A session status and the result of the comparison. See session statuses and webhooks.
Next
Talk to us about your recovery flow, or see a verification on sample data in the interactive tour.
Questions, answered plainly
What does the platform compare?
A returning user is compared with a stored reference face.
What does my system do with the result?
It reads the session status, or receives a webhook, and then restores access, asks the user to try again, or sends the case to a manual decision in the dashboard.
Can the user start on a computer?
Yes. Hand the user to a phone with a QR code. See QR hand-off.