Verification requests

The Verification Requests page displays a list of created applicants. For each applicant, the status, number of verification attempts and additional information (first name, surname, date of creation of the applicant, etc.) are shown.

The following actions can be performed on each applicant:

• Edit — Modify the applicant's data: surname, first name, phone, mail, etc.
• Notify by SMS — Send the message with a link to validation.
• Close Request — Close out the applicant. Attempts to register and authorize by applicant will be rejected. And if you close an applicant which has already been registered, it will be impossible to register again with a similar face.
• Open Request — Unlock or open an applicant to reset attempts to zero or resume registration or authorization capabilities.
• Delete — Delete the applicant and all their information.

For detailed information on the applicant, click the Review button. At the appeared page you can view data for each verification attempt: the results of various checks, possible reasons for unsuccessful verification, etc. On the left you can switch between verification attempts.

Description of attempt status icons

A green circle with a check mark inside - successful attempt.

Red circle with a cross inside - failed attempt with no active risks.

Yellow triangle - there are inactive risks in the attempt.

Red triangle - there are active risks in the attempt.

Gray triangle - invalid input data was used in the attempt.

Red lightning bolt - an error occurred on the server while processing the attempt.

Forming the attempt status

When registering/authorizing by face the status of an attempt is formed on the basis of validation results, which are grouped into three blocks: Face Match, Liveness, Quality. A block is considered successful if all validations in the block are successfully passed.

The list of possible checks in a block. (depends on the system configuration)
Face Match:

• Liveness Reflection Match (Matching best shot from component and best shot from Liveness reflection video)
• Motion Control Match (Matching a best shot from a component and a best shot from a motion control video)
• Face Match (Matching a face against the entire face database or against a reference photo of the applicant)

Liveness:

• Anti Spoofing (Liveness of best shot from component)
• Liveness Reflection (Liveness by video liveness reflection)

Quality:

• Face Quality (Best shot quality from component)

Underneath the results of the attempt you can view content bound to the verification attempt. To download it, click on the upper right corner of the element. Liveness Reflection video and motion control video is only available when LRS is enabled.

At the bottom of the page you can see the applicant's data and part of the attempt metadata.

Examples of attempts with different data

Attempt example with triggered risks:

If the risk has triggered but doesn't affect the attempt, it is marked with a gray icon. If the risk is triggered and affects the attempt, it is marked with a red icon.

If you hover the mouse over the MotionControlFailed risk icon, you can see which movements were required and which failed:

Attempt example with error:

The error code is in parentheses. After the code there is a human-readable error name, and under the name there may be a description of the error

Attempt example with similar applicants info:

The list of similar applicants is filled only if the system found similar applicants during registration. Clicking on the thumbnail of a similar applicant you can go to the page of its attempts

Manual registration

If the applicant is not registered yet, it is possible to register it manually.

Registration requires a photo with one face. The checks that will be performed during registration are defined in the “Manual mode settings” section of the settings.

Example of an applicant for which manual registration is possible:

Manual registration form:

Filtering attempts by web component integration id

On the attempts page there is an option to filter by web component integration id.

To filter you need to enter the full id in the form at the top of the page: