For the complete documentation index, see llms.txt. This page is also available as Markdown.

Configurations

Community administrators—or users with the idproofing.add-journey permission—can create and manage verification journeys in the AdminX interface under Verification > Verification Flows.


Configuring Verification Flows

Journey Type
Description

KYC with Selfie

Combines document verification with face liveness and selfie matching. Users are prompted to scan an identity document and then capture a selfie for comparison.

Document Verification Only

Enables standalone document verification without any selfie or liveness check.

Each journey is created in three steps:

  1. Select workflow type — Choose between KYC with Selfie or Document Verification Only, and provide details such as the workflow name, type, last modified date, and creator.

  2. Select verification configuration — Restrict allowed documents by country, region, and type; configure PII data retention policies; and enable first and last name matching for identity comparison.

  3. Manage face liveness and face matching threshold — Configure Face Liveness (Soft, Regular, or Hardened) and set the Face Comparison Threshold (default: 50%) to control the sensitivity of biometric matching.


Configuring KYC with Face Comparison

The KYC with Face Comparison journey consists of two main steps:

  1. Defining documents for verification — Specify the list of documents accepted for verification.

  2. Configuring face liveness settings — Set the liveness calibration and face matching threshold.

Step 1: Defining Documents for Verification

Field
Description

Journey Name

Specify a name for the verification journey.

Unique Tag

Specify a unique tag used by API callers to create sessions. The tag must be unique and cannot be changed once set.

Allowed characters: /^[a-zA-Z0-9\_-]\*$/i

Allowed Document Types

Select which document types are permitted for verification based on country and region. Only the selected types are accepted.

By default, the Allow toggle is selected and the Allowed Document Types dropdown is displayed. Switching the toggle to Block displays the Blocked Document Types dropdown instead, where you select the documents to restrict.

• In the Allowed Document Types window, click Allow all documents to permit all supported documents.

• Specify the country and region to narrow down which documents are available for selection.

The region determines whether the document format is national (used across the country) or regional (specific to a state or locality):

• Region: National — the document follows a country-wide format.

Example: Country: India, Region: National, Document Type: Driver License → Displayed as INDIA, DRIVER LICENSE. Although NATIONAL is not shown in the label, this refers to a standardized national document format.

• Specific region (e.g., state)

Example: Country: India, Region: Andhra Pradesh, Document Type: Driver License → Displayed as INDIA, ANDHRA PRADESH, DRIVER LICENSE.

National and regional formats must be selected individually — choosing one does not automatically include the other.

Allow/Block Toggle

Choose whether the selected documents are explicitly allowed or blocked.

Data Configuration

Specifies how long verification data is retained for each session outcome (Success, Failed, Not Performed, Review, and Abandoned). Options:

• Discard data immediately

• Discard data after caller retrieves result

• Discard data after specified time

Discard Data After (appears only when Discard data after specified time is selected)

Specify the number of days or minutes after which the verification data is discarded.

Use Case

Field
Description

Context

Defines the verification use case, such as remote or in-person verification.

Document Verification Policy

Sets the policy for document analysis. Standard is recommended for most use cases. Options: Permissive, Standard (recommended), Strict, Very Strict.

Retry Count

Maximum number of retry attempts allowed during the verification process.

Expiration Intervals

Field
Description

From Session Creation

Sets how long a session remains valid if it has not been accessed.

From Session Start

Sets how long a session remains valid after it has been started by the user.

Data Comparison

Field
Description

Select from the list

Choose which user data (e.g., First name, DOB) is compared against document data.

Ignore middle names

When enabled, middle names are excluded from name comparison during ID proofing to improve match accuracy between directory data and identity documents. Only the first word of the first name is evaluated from both the user metadata and the identity document; any additional names in the document's first name field are ignored. Last name comparison behavior is unchanged.

Fuzzy Match (First Name)

Enables approximate matching for the first name. Useful for handling spelling variations.

Fuzzy Match (Last Name)

Enables approximate matching for the last name.

Fuzzy Match Slider

Adjusts the threshold for fuzzy matching (recommended range: 70–80%).

Date of Birth Comparison

Compares the entered date of birth with the extracted document data. Exact match only.

Continue

Proceeds to the next step in setting up the verification journey.

Behavior of Fuzzy Match and Ignore Middle Names

The Ignore Middle Names option can be used on its own or together with Fuzzy Match.

  • When both options are enabled, fuzzy matching is applied to the first word of the first name.

  • Fuzzy matching continues to apply to the full last name value.

Example Scenarios

First Name (User)
First Name (Document)
Ignore Middle Names
Fuzzy Match
Result

Mike

Mike Johnson

Enabled

—

Pass

Mike Alexander Johnson

Mikee Alexander Johnson

Enabled

Enabled

Pass

Mike Alexander Johnson

Mikee Alexander Johnson

Enabled

Disabled

Fail

Step 2: Configuring Face Liveness Settings

Field
Description

Liveness Levels

Determines the calibration level for liveness detection to balance convenience and security:

• Regular — Default setting. Provides acceptable security with higher user convenience.

• Soft — Reduces false rejections of genuine users while maintaining some error tolerance in detecting spoofing or presentation attacks.

• Hardened — Highest security setting. Strongly reduces spoofing risks but increases the chance of mistakenly rejecting legitimate users.

Face Matching Score

Defines the threshold for similarity between a live face and the reference image. Recommended range: 50–80%. Adjustable using the slider.

Back (button)

Navigates back to the previous step in the verification flow setup.

Create Verification Flow (button)

Saves the configuration and creates the verification flow.

Last updated

Was this helpful?