Skip to main content
Face Match and ID Check each have a page under Verifications, available to organizations that use verifications. Each page lists the project’s sessions, opens any session for review, and charts completion. A session shows the same decision, risk score and risk flags your integration receives from /verify-face or /verify-id. For how the products work and how to integrate them, see the Verifications Overview. Risk flags are defined in the Face Match and ID Check references.

Decisions follow your lists

A session linked to an account on Block shows Fake, and one on Allow shows Real, matching what the API returns. The risk score and risk flags always show the model’s own result, and the Lists field shows which lists the account is on. See Rules, Lists, and Verifications.

Session tables

Each page lists completed sessions by default. Show Incomplete Sessions, in the table menu, adds sessions that stopped before the end, with a Status showing where they stopped, such as Agreed To Terms or Liveness Failure. ID Check tables add the fields read from the document, such as ID country, type, number, name and date of birth.

Reviewing a session

Hit Rules lists the rules the session triggered, through the ID Check Completed and Face Match Completed triggers. See Building Rules. Matches draws up to 50 linked accounts. Linked accounts can be added to a list from the graph. See the multi-accounting sections of the Face Match and ID Check response signals. Incomplete sessions show only the photos and videos captured before they ended. The other tabs need a completed session, and so do Analyze with AI and Enroll Account.

Creating a session

Create Session creates a verification session and shows its link and QR code, for sharing with one person, such as a user your support team is checking manually. Generate New Session Token creates another session. Delivering the link is up to you.
Every verification session is billable, whether or not the person completes it. Opening Create Session creates a session immediately.
Sessions created this way have no account ID. Link the result with Enroll Account.

Enrolling a session

Enroll Account links a completed session with no account to an account ID, with the same effect as passing account_id when the session is created. Until then, the session has no account and later sessions are not checked against it for repeats. A session links to one account, within 30 days of creation. See Enrolling an Account ID Later.

Usage

Permissions

Admins have every permission. Start verifications is a separate permission because every session it creates is billable. View verifications includes the ID documents and selfies people uploaded. See Managing Users.

Need Help?

If you have any questions about reviewing verifications, please contact our support team at support@verisoul.ai.