Documentation [DRAFT]

Identomat System Manual & Integration Guide

Untitled sync page

Explore

Identomat System Manual & Integration Guide

Quickstart Guide

Client Application

End-User Experience

⁠

⁠

⁠
https://demo.identomat.com/try/?company=insert_company_name_here⁠
⁠

Screenshots of the Demo Web App showcasing end-user experience

Depending on the configuration of the host application’s integration of Identomat, user can undergo different flows. Most common flow involves Capturing user’s ID, Checking their Liveness, and assessing the match between their Photo ID and Selfie extracted from Liveness video feed:

Access to the camera

If the app/widget does not have device camera access, the end-user is prompted to grant permissions t the system.

ID Capture step

User captures their ID by any one of the three methods depending on the system configuration: Live Capture, Upload, or NFC.

Liveness Check ( Video selfie ) step

User undergoes Liveness Check by taking a selfie video with (Active) or without (Passive) prompts based on the system configuration.

(Background Process) Face Match

If Identomat system successfully determines user’s liveness, the photo extracted from the identification document and the photo from the video selfie are compared to determine the similarity rating, expressed as percentages that can be manually pre-determined by the clients themselves. At this stage the information from the MRZ zone of the document gets compared to the textual data from the document;

(Background Process) Screening

If enabled, user’s PII which was extracted from their ID is automatically screened against 1000s of watchlists including Global Sanctions, Politically Exposed Persons (PEP), Export Control, Law Enforcement Most Wanted, Regulatory Enforcement, Contract Debarment and more.

(Background Process) Address Verification

Automated OCR and address validation for Proof of Address documents like bank statements, utility bills, etc., combined with location signals from IP & GPS.

Getting verification results

At the end of the process, the host system gets verification results (Approve/Reject/Pending) from the system and end-user is able to continue back at the host application flow.

Back Office & Dashboard

Settings

Login to your company dashboard

⁠

⁠
https://manage.identomat.com/⁠
Dashboard Login page

Creating API Keys for Integration

⁠

2024-02-28-17-10-manage.identomat.com.png

⁠

User List and Creating a New User

Each company can create unlimited* number of users with one of the following roles: /Admin/Operator/Call Center Operator/ to access their back office account.

⁠

2024-02-28-17-11-manage.identomat.com.png

⁠

Agent Experience

Dashboard

⁠

2024-12-12-16-09-manage.identomat.com.png

⁠

Dashboard Usage and performance overview for all sessions in the specified date-range

AML Screening - Sanctions, PEP, etc.

Companies can also perform on-demand screening of their customers by entering their name and DOB in the search dialog on Screening page.

⁠

Sessions

Browse verification sessions

Sessions are collated by their statuses in separate tabs:

Done - Approve or Reject result is produced.

Pending - Requires Manual Review.

All - All sessions regardless of their status.

In progress - Unfinished sessions.

⁠

Dashboard / Sessions / Done All completed verifications are displayed in this table

Sessions Table Structure

Parameter

Description

Value(s)

Status

Thumbnail

Name

Source

Document

Location

Date

Config

Liveness

Screening

Similarity

There are no rows in this table

⁠

Sessions Search and Filtering

Filter

Description

By Keyword

By Date

By Result

By ID Type

By Config

By Reject Reason

By Screening Result

There are no rows in this table

⁠

Session Details

Auto-Approved Session

Depending on the company configuration, if the ID-to-Liveness match score falls within preset ranges for Manual Verification, the session will be assigned the Pending status

⁠

Manually Reviewing Sessions

Pending Sessions

Depending on the company configuration, if the ID-to-Liveness match score falls within preset ranges for Manual Verification, the session will be assigned the Pending status

⁠