Standard Identity Verification Workflow
Creating an efficient ID verification workflow is crucial for businesses that require identity verification to ensure user authenticity and compliance with regulatory standards. This guide outlines a common ID validation workflow that incorporates essential modules and best practices.
Standard Identity verification workflow verifies users by capturing their identification document (ID) and Face data, making sure person on the ID is the one performing the identity verification, checking for an ID validity in terms of tampering, altering, date of expiration and many more.
Steps in the standard Identity Verification workflow
Data Sharing Consent Module
The Data Sharing Consent module is critical for legal compliance and trust-building. It ensures that users are informed and agree to the processing of their personal and biometric data before proceeding with the verification process. Use Incode default consent language, or specify your own. Learn more how to setup your own consent language here Data Sharing Consent.
ID Capture Module
This module allows the capture of user identity documents. It can be configured to accept specific document types, catering to the verification requirements of different regions or services (e.g., passports, driver's licenses). Limit the number of capture attempts to enhance security and user experience. A reasonable limit ensures users are deliberate in capturing their ID, reducing errors and potential fraud.
ID Validation Process
After ID capture, the ID Validation module is essential for ensuring the document's validity. It conducts checks for expiration, authenticity (detecting screen or printed document replicas), and various fraud checks safeguarding the integrity of the verification process.
Face Capture Module
This module captures a live image of the user's face. It can include liveness detection to prevent spoofing and ensure the presence of a real person during the capture. Quality checks are also available to ensure the captured image meets the criteria necessary for accurate verification.
Face Match Process Node
It is advisable to skip the face match animation in production environments to prevent providing feedback to potential fraudsters. This module offers various configuration options, including sensitivity settings for matching the captured face image with the photo on the ID document.
Condition Node
A straightforward application of condition nodes is to evaluate the overall results of ID validation, face recognition, and liveness checks to determine the session outcome. Additional conditions can be tailored to specific requirements, adding flexibility to the verification process.
Final Session Results
Based on the outcomes evaluated by the condition node(s), set up the final session results to reflect the verification status:
- OK: Verification successful.
- FAIL: Verification failed.
- MANUAL: Requires manual review.
Additional Settings
- Give name to your workflow
-
Specify redirect URL: After successful completion of identity verification, redirect your users to desired page. Redirect url must be in https://your.desired.url format
-
Redirect desktop attempts to mobile: This is recommended setting. If user opens workflow link on desktop they will be presented with QR code and asked to continue on their mobile phone device
When opening workflow url on desktop, user will be asked to scan QR code with their mobile device
-
Disable launch screen: If checked, this option will skip the initial launch screen, allowing users to directly start the workflow. This is helpful if user is already inside your app experience and there is no need for a launch screen. Launch screen features your logo.
User would not see this screen
- Disable SMS option: If checked, this option remove the support for users to send SMS with the link to their phone, allowing them only to scan QR code.
- Automatically create an identity on successful workflow execution: When this option is checked, a user identity is automatically created upon successful completion of the workflow.
If your workflow does not have Face capture module in all user paths, then this options should not be used. Identities are created only if user face is collected.
- Mark session as expired: Set up a timeout that would mark session as expired after a period of user inactivity
To configure onboarding link expiration (prior to user opening it) go to Configuration -> General -> Onboarding link duration
Publish and Test
Once your workflow is configured:
- Publish: Make your workflow live to start handling real user verification sessions.
- Testing: Utilize the unique link generated for your workflow to conduct thorough testing. This ensures the workflow operates as expected under various scenarios and with different types of IDs.
- Review results: For every session you can review results, data collected, steps user went through and many more in the single session view.
Using Templates for Identity Verification Workflow
Creating an Identity Verification Workflow can be efficiently accomplished by utilizing the available template within the Workflows platform. This template includes all the essential modules detailed in this guide, pre-configured for a standard Identity verification process. This approach saves time and ensures best practices are followed.
By leveraging templates, you can deploy an Identity Verification Workflow quickly, ensuring a secure, compliant, and user-friendly verification process. To create this workflow from a template, follow the guide on how to create a workflow from a template Creating a Workflow from a Template
Updated 29 days ago
Learn more about customization of your Workflow and how to user Conditionals to craft unique user journeys