Customer Journey¶
From an architecture point of view, XpressID is an orchestration like service which manages the calls to the Veridas validation service to carry the validation process and retrieving the results obtained and the files used in the process. There are four operation modes: IDV, Authentication, AgeVerification and resume.
Operation Modes¶
IDV¶
XpressID offers a suite of processes designed for identity verification. Customers can tailor these processes to their specific needs by combining them in various configurations.
These combinations are structured as a sequence of distinct processes. The first process begins automatically, and upon its completion, the next process is initiated. This sequential progression continues until all processes within a defined flow have been successfully completed.
Next, we'll provide a detailed description of each process.
Document¶
Document & country selector¶
The document and country selection enables users to select a document type from a specific country. It presents a country selector, and when a user chooses a country, it loads the allowed document types for that country. Upon selecting one of the listed document types, the process is complete, and the document type is set.
If navigator geolocation is permitted, the country selector automatically detects the user's location and selects the corresponding country
To configure this section, you can refer to the documentation here.
Autoclassification selector¶
The auto-classification is activated when the documentTypes parameter is provided with multiple documents as outlined in the Veridas documentation here. This occurs only when the document selector flow is inactive.
If multiple documentTypes or the value "XX" is passed along with the documentType XX_Passport_YYYY (Passport), an auto-classification selector will appear, offering two options. The first option enables processing the specified documents, while the second option facilitates processing with the Passport document.
This is exclusively available on the web platform.
To configure this section, you can refer to the documentation here.
Document capture¶
The document capture initiates by presenting a popup requesting permission for XpressID to utilize the device's camera. Once granted, the obverse side capture subprocess commences, displaying instructions for capturing a high-quality image in a specific and controlled manner. If the corresponding document has a reverse side, the capture subprocess for the reverse side automatically follows upon completion of the obverse side capture.
Multiple document capture¶
The document capture supports multiple iterations, allowing for up to three attempts to capture a single document. Each attempt includes the document selection or auto-classification steps, as configured.
To configure this section, you can refer to the documentation here.
Selfie Capture¶
Selfie capture commences by displaying a popup requesting permission for XpressID to access the device's camera. This encompasses two distinct methods: passive selfie and active selfie.
The passive selfie involves capturing a photo selfie. The user is prompted to center their face within an oval guide, and a photo is taken.
The active selfie begins with capturing a photo selfie. The user is prompted to center their face within an oval guide, and a photo is taken. To further verify the person's liveliness, the user is then instructed to make random head movements while another photo is captured.
To configure this section, you can refer to the documentation here.
Video Capture¶
The video capture commences by presenting a popup requesting permission for XpressID to access the device's camera and microphone. Upon granting access, it initiates a video recording prompting the user to state their name and showcase both sides of the document captured during the document validation.
To configure this section, you can refer to the documentation here.
Esign¶
The Esign process allows for secure document signing through facial biometrics when the captured document, selfie, or video results are correct. Then, the signing process begins where you can view the PDF and sign by writing your name in a box. Once signed, a PDF is generated that embeds a QR image containing signature data and a biometric credential obtained from a selfie capture of the signer.
More information about the eSign product and how to obtain the signed PDF via API can be found here.
To configure this section, you can refer to the documentation here.
Authentication¶
XpressID offers a secure and convenient way to authenticate users using facial recognition. This guide explains the enrollment and authentication processes.
Enrollment¶
During the onboarding process, you'll be prompted to take a selfie using the IDV operation mode. This selfie is securely stored on our vali-Das for a limited time to enable future biometric logins. It is important to keep your selfie confidential, store it in a safe place. This helps to ensure the security of your account.
Authentication¶
First, send an access token request along with a new selfie. You can take the selfie using the IDV operation mode. Then, XpressID compares your new selfie capture with the one captured during enrollment using a 1:1 facial recognition algorithm. Finally, the comparison score (a measure of similarity) is temporarily stored for potential future use.
To configure this section, you can refer to the documentation here.
AgeVerification¶
XpressID offers two ways to verify your age using facial recognition technology, both suitable for ages between 18 and 21:
Selfie verification, this is the simpler option where you simply take a selfie using the provided capture function and Selfie + Document verification, If your initial selfie doesn't meet the age requirements, XpressID will prompt you to capture a government-issued ID document to complete the process. This is done through the combined "selfie and document capture" option.
To configure this section, you can refer to the documentation here.
Resume¶
This functionality enables end-users to seamlessly resume their identity verification if they need to pause or exit at any stage. The process can be resumed at a later time without the need to repeat any completed steps. To initiate a resume, you can use the validationId parameter, as described in the documentation.
If the end-user discontinues the process during the validity period of their ACCESS_TOKEN, they can resume it by using the same ACCESS_TOKEN. The process will reload from the point of interruption.
If an identity verification remains incomplete, Veridas has an automated cleaning process in place, which is agreed upon between the client and Veridas. The details of this autocleaner are client-specific and depend on the specific use case. The default validation persistence time is 30 minutes in LIVE environments and 24 hours in WORK environments.
This functionality is only valid for the IDV mode.
To configure this section, you can refer to the documentation here.
Platform-Specific Functionalities¶
This section details the specific functionalities offered by the application on web, iOS, and Android platforms. It is crucial to understand the differences and similarities in the user experience on each platform to ensure a consistent and satisfying user experience.
Below is a table comparing key functionalities across the three platforms:
| Functionality | Web | iOS | Android |
|---|---|---|---|
| QR capture | ✅ desktop only | - | - |
| Document capture | ✅ | ✅ | ✅ |
| Document & country selector | ✅ | ✅ | ✅ |
| Autoclassification selector | ✅ | - | - |
| Multiple document capture | ✅ | ✅ | ✅ |
| Selfie capture | ✅ | ✅ | ✅ |
| Video capture | ✅ | - | - |
| Esign | ✅ | - | - |
| Authentication | ✅ | ✅ | ✅ |
| AgeVerification | ✅ | - | - |
| Resume | ✅ | - | - |