Verify & Enroll User
Once a FaceMatch session is complete, use the Verisoul API to complete the workflow.
There are two core use cases for FaceMatch:
Uniqueness (1-N): verify a face is unique and has not been previously enrolled with another account (prevent multi-accounting)
Authentication (1-1): match a face session to an already enrolled account to ensure it is the same user (prevent account takeovers)
*Note: both uniqueness and authentication will validate that the user is a real human
Uniqueness
Workflow
When you want to check whether a user is unique:
Verify Uniqueness
Call the /verify-uniqueness endpoint
Parse
matches
. If the user has zero matches, then the face is not already enrolled to another account
Enroll face and tie to an account
If the user has zero matches and is unique, use the /enroll endpoint to link that face to the new account
If the person already has an existing account, you can:
Choose to not enroll the user (our recommended approach)
Choose to enroll the user, but then block them (or take other action)
How customers use Uniqueness in their Apps
One-person one-account sign-ups
Before a transaction or withdrawal
As a step up verification if Verisoul Platform determines user is
Fake
orSuspicious
or has high probability of multi-accounting
Authentication
Workflow
When you want to use FaceMatch for auth:
Enroll Account
When a new account signs up, include the FaceMatch as part of the sign up workflow
Call /enroll with the sign up session_id and new account identifier
Verify Identity
When the account signs in (or when you want to verify user identity), make the user go through FaceMatch again
Call /verify-identity endpoint with new session to ensure the same user that was enrolled is accessing the account
Use Cases
At sign-in
Prior to large transactions
Prior to withdrawals
Last updated