This article explains how to set up a Mitek integration hub to enable authentication and data extraction of a customer’s personal ID document. The integration also supports biometric identity verification by comparing the document photo to a live selfie. Once the integration is set up, you can incorporate Mitek features into a collaboration session in several ways.
Key capabilities of the Mitek integration
Document authenticity check – Detects whether the uploaded ID is genuine.
Data extraction – Automatically pulls structured data (e.g., name, ID number, expiration date) from the document.
Biometric identity match – Uses facial recognition to compare the ID photo with a live selfie for identity confirmation.
Use cases in the Lightico platform
Session entry verification - For identity verification before entering a collaboration session (see Customer authentication).
Photo ID verification Workflow step - For document and identity verification and data extraction (see Customer verification as a Workflow step)
Document Request Workflow step - For data extraction (see Add Document Requests to a Workflow)
Customer view of authentication
Configure a Mitek integration hub in Lightico
To use Mitek technology in Lightico, you must first configure a Mitek integration hub. This setup is required for all use cases involving Mitek, including both session-level and Workflow-level authentication and data extraction.
The connectivity settings in the hub apply universally across all use cases. However, other settings in the hub—such as document options and some authentication attempt limits—are specific to session entry authentication. These distinctions are noted in the instructions below.
Where Workflow-level authentication requires configuration outside the hub (such as in the Workflow builder or system settings), this is also clearly indicated.
Set up the hub and configure connectivity settings
The following steps are necessary for session entry as well as Workflow-level authentication.
From the Admin Center, go to Integrations and click the Mitek hub.
In the Mitek hub, enter a name and description for the hub and click Save.
On the Connectivity tab, enter your Mitek credentials.
Define document options
Authentication requires the customer to provide one form of photo identification. You can either require a specific document type—such as a driver’s license—or allow the customer to choose from multiple options, such as a driver’s license, ID card, or passport. Mitek authentication supports both approaches.
The following steps apply to session entry authentication.
To define document options:
On the Documents settings tab, select one or more document types for session entry authentication.
Choose whether to scan the front only or both front and back for each type.
Enter a customer-facing name for each document type.
This name will appear in the customer UI during authentication.
Note
Document options for a Photo ID verification Workflow step are configured in the Workflow builder in the properties pane for the Document Request or Photo IDV step. See Add Document Requests to a Workflow.
Define authentication attempts
You can configure how many times a customer can attempt to authenticate before being locked out or permanently banned.
For session-level authentication, attempts are divided into individual attempts and series of attempts. A Photo ID verification Workflow step only allows one series of attempts.
The following steps apply only to session-level authentication unless otherwise indicated.
On the Authentication attempts tab, define the following:
Number of series – How many lockout cycles are allowed before the customer is permanently banned.
Retries inside series – Number of attempts allowed before a temporary lockout occurs.
Also applies to Photo ID verification Workflow step.Delay between series – Time the customer must wait before retrying after a lockout.
Number of corrective actions – Mitek distinguishes between retry attempts due to image quality issues (such as glare, blur, or cut edges) and those triggered by suspicious or potentially malicious behavior. In this setting, you can define how many non-suspicious corrective attempts are allowed without counting them toward the maximum number of permitted attempts in a verification sequence.
Also applies to Photo ID verification Workflow step.
Note
As noted above, only the Retries inside a series and Number of corrective actions are relevant to a Photo ID verification Workflow step.
Binding Attributes to extracted data
Binding data extracted by Mitek to Lightico Attributes ensures that this customer information can be reused in the session and reported in the IDV completed event.
For more information about Lightico Attributes, see Understanding Attributes.
The following step applies only to session-level authentication.
On the Attributes tab, select a Lightico Attribute from the Attribute dropdown.
Note
Attributes bound in the Mitek hub apply only to session-level use cases. For Workflow-level document processing, data binding is configured when you create the Document Request type. See Create Document Requests.
Types of documents supported by Mitek
Mitek can authenticate and extract data from a range of standard document types. These types are used across different Lightico features that rely on Mitek processing.
Note
While the list below includes general supported types, we recommend validating with your Lightico Customer Success representative whether the specific documents your company works with are supported.
Driver’s license
Identification card
Passport
ICAO-compliant passport card
Residence permits