Skip to main content

Release Notes: ID Verification

1.11.06.02​

October 10, 2025​

New Features​

Ability to configure Identity Verification flow through UI​

Community administrators with the idproofing.add-journey permission can now configure and manage custom ID verification journeys in AdminX under Verification > Verification Flows.

This feature enables admins to create a custom workflow according to their regional requirements and reduce fraud risk.

Key capabilities include:

  • Creating and managing verification journeys
  • Generating and sharing session links
  • Editing or deleting journeys
  • Defining accepted ID documents by country and region

For more information, see Configuring Verification Flows.

Granular Document Controls for ID Verification​

Community administrators can now define and control which identity documents are allowed or blocked during the ID Verification journey. Documents can be configured by country, region, and document type, with the ability to allow all by default or apply granular restrictions. When a user scans a document not on the allowed list (or on the blocked list), the system will end the session with a clear failure response and display the “Unsupported” screen. A new event (E_IDV_DOCUMENT_NOT_ALLOWED) is triggered with full metadata for audit and tracking.

This feature gives organizations greater control and compliance over the types of identity documents accepted, helping to meet regulatory or internal policy requirements.

Enhanced IAL2 Identity Verification Flow​

In the previous release, users could verify their identity by submitting identity documents, biometric data, and an SSN. In this release, users can enroll their liveid, to a wallet enabling future comparisons against identity documents stored in the wallet for verification purposes.

Community administrators can also configure whether the Liveid capture must appear within the verification flow or in a separate tab, based on the preferred user experience. If the initial selfie session does not start within 2 seconds, a new session is automatically created to avoid delays and ensure a smooth verification process.

1.11.03​

September 5, 2025​

New Features​

Support for One-Time IAL2 Identity Verification​

Community administrators can now create and manage a one-time Identity Assurance Level 2 (IAL2) verification flow. This new process allows users to verify their identity by submitting identity documents, biometric data, and an SSN.

Key Benefits:

  • Persistent Verification: Retains verified user information without needing to "forget" users afterward.
  • Compliance-Ready: Meets requirements for persistent identity verification.
  • One-Time Process: Unlike the existing flow, data is not deleted or reset after verification.

This update enhances compliance and streamlines the verification process for administrators. For more information, see Kantara Certified IAL2 Verification.

1.11.01​

August 9, 2025​

New Features​

Self-Service Password Reset with Identity Documents​

Users can now reset their passwords by submitting a valid identity document for verification. This feature uses advanced matching technology to compare the name on your submitted document with your account information. For more information, see the Resetting Passwords Using Identity Documents section in Resetting Account Passwords.

Manual Document Capture Support​

The verification UI now supports manual document capture when auto-capture fails, such as with documents like Yukon ID/DL where the front side isn't detected, causing the process to stall. To address this, the UI has been enhanced with fallback options including Manual Capture and Retry Auto buttons, which appear after a timeout period. For more information, see the Verifying Identity section in Verification Journey.

Enhancements to the V3 Poll API​

The V3 Poll API response has been updated with the following additions:

  • Added liveid_object key containing selfie details.
  • Included rawData for session-level raw information.
  • Added token, reason, reasonCode, and fuzzyMatchScore to the response.
  • Updated resultStatus for sessions where verification was not performed to return NOT_PERFORMED instead of FAILED.
  • When the verification status is marked as "Failed," error codes along with their corresponding reasons are displayed.
    The following table provides information on error codes:
    Error CodeDescription
    IDV0001Image quality check failed
    IDV0002Verification partially completed
    IDV0003Verification was completed only on front
    IDV0004Extraction of document failed
    IDV0005Incorrect document type presented
    IDV0006Unsupported document was presented
    IDV0007Data check failed
    IDV0008Document liveness check failed
    IDV0009Document validity check failed
    IDV0010Module '$module' failed
    IDV0011Document expired
    IDV0012One or more fraud check failed

New Documents Support​

  • Canada, Newfoundland And Labrador - Identity Card
  • Canada, Northwest Territories - Driver's License
  • Canada, Northwest Territories - Identity Card
  • Canada, Prince Edward Island - Identity Card
  • Canada, Yukon - Identity Card
  • Canada, Nunavut - Driver's License and Identity Card
  • Liberia - Identity Card
  • Mali - Identity Card
  • UK - Military ID
  • Austria - Refugee Passport
  • Austria - Polycarbonate Refugee Passport
  • Burkina Faso - Driver's License and Paper Passport
  • Costa Rica - Residence Permit
  • Gambia - Paper Passport and Polycarbonate Passport
  • Rwanda - Polycarbonate Passport
  • South Korea - Polycarbonate Passport
  • Tanzania - Polycarbonate Passport
  • Uganda - Paper Passport and Polycarbonate Passport
  • Zambia - Driver's License and Paper Passport
  • USA, Florida - Medical Marijuana ID
  • USA, Pennsylvania - - Medical Marijuana ID

New Beta Documents Support​

  • Canada - Non Card Tribal ID
  • Dominica - Paper Passport and Polycarbonate Passport
  • UAE - Diplomatic ID
  • USA, Georgia - Medical Marijuana ID
  • Benin - Paper Passport
  • Burundi - Polycarbonate Passport
  • Chad - Identity Card
  • Kenya - Driver's License
  • Mozambique - Polycarbonate Passport
  • Spain - Registration Certificate
  • Sudan - Identity Card
  • Zimbabwe - Driver's License
  • USA, Nevada - Medical Marijuana ID
  • USA, New York - Medical Marijuana ID
  • USA, Oklahoma - Medical Marijuana ID

For more information, see Supported Documents.

Miscellaneous​

  • Improved extraction for Canada/Nunavut ID and DL by introducing error correction for "1" and "I" characters which look the same in the font used on a document.
  • Fixed document number extraction from Canada/Nunavut barcodes.
  • Introducing Barcode Anomaly check for Canadian documents with barcodes.
  • Improved data checks for Austria, Bahrain, Czechia, Croatia, Egypt, Kuwait, Oman, Pakistan, Poland, Qatar, Slovakia, Slovenia, Sri Lanka, Uruguay, USA.
  • Improved document coverage for all Canadian provinces, Tribal cards and Healthcare cards.
  • Improved Barcode Anomaly check for USA.
  • Added new data format checks for Argentina, Bahrain, Brazil, France, Germany, Haiti, Hungary, Mexico, Peru, Singapore, South Korea, and the USA.
  • Improved fraud checks for Tennessee and Wyoming documents.

1.11.00​

July 12, 2025​

New Features​

Added Two New Languages in ID Proofing Templates​

The ID proofing templates has now been enhanced to support multi-language capabilities by adding Simplified Chinese and Spanish, expanding the current support to four languages: English, French, Simplified Chinese, and Spanish.

Implemented Retry Mechanism for Unsupported Documents​

A retry mechanism has been implemented to improve handling of unsupported documents during the verification process. Two scenarios are supported: In Progress and Abandoned. Retry behavior is governed by a configurable attempt limit.

If the retry count has not been exceeded, a Retry Required option is displayed.

Once the retry limit is reached:

  • In the In Progress scenario, if only unsupported documents are submitted, the verification result is marked as "Verification Not Performed" with the reason "Unsupported document was presented".
  • In the Abandoned scenario, the final verification status reflects the previous attempt's result.
  • An E_IDV_SESSION_RETRY event is displayed when a retry attempt is made.

Display of Passport Instructional Text in Vertical Mode​

The instructional text displayed during passport scanning is now properly aligned and easily readable in both vertical and horizontal orientations.

Bypassing Verification for Specific Regions​

Verification will now be bypassed for the following regions and document type combinations:

  • Nunavut (NU): Driver’s License, Provincial ID
  • Yukon (YT): Driver’s License, Provincial ID
  • Northwest Territories (NT): Driver’s License

A configurable condition-based bypass has been implemented at the DVCID level. This allows unsupported documents to pass through the verification flow without triggering errors, enabling them to be handled successfully within the system. Additionally, the full barcodedata in the session summary certificate is logged when a fraud_detection_bypass exception is triggered. This allows us to track how many bypasses were performed and identify the originating territories, even after PII has been discarded.

1.10.13​

June 14, 2025​

New Features​

Implemented WCAG compliance for ID Proofing Templates​

In this release, 1Kosmos implemented Web Content Accessibility Guidelines (WCAG) compliance for ID Proofing Templates. This enhancement ensures that the templates are accessible to users with disabilities, improving usability for all users, including those relying on assistive technologies. Additionally, Voiceover support has been introduced across all screens to enhance accessibility for visually impaired users. This ensures that key elements and instructions are now fully navigable and readable using the keyboard.

By adhering to WCAG standards, 1Kosmos provides a more inclusive experience, ensuring meeting legal and ethical accessibility requirements. This update enhances both the functionality and accessibility of the ID proofing process.

Added ReCAPTCHA on Verification Journeys​

To enhance security and prevent automated misuse, reCAPTCHA verification has been implemented on the Verification > Journeys page when an administrator creates a verification session and sends it via SMS to the user.

reCAPTCHA UI Enhancements

As part of reCAPTCHA integration on the Journeys page:

Token Capture: After creating a session, when the community administrator clicks “Share via text”, the reCAPTCHA token is captured and included in the request payload (captchaToken) for the /idvaapi/proofingsession/session/sms API.

Missing reCAPTCHA Config:

If the /proofingsession/recaptcha_config/fetch API returns an error message: “Captcha config not found”, the following UI message is shown: “Recaptcha configuration is missing, please contact your administrator.” However, the administrator can still create sessions but cannot proceed to send them via text.

Missing Token Scenario:

If the reCAPTCHA config is missing and the administrator clicks “Share via text”, the UI cannot provide a captcha_token.In such cases, the UI displays the following message:

“Recaptcha verification failed. Our security policy does not allow you to send this session via text message.”

Token Validation Failure:

If the /idvaapi/proofingsession/session/sms API returns: “Recaptcha check failed”, the UI displays the message: “Recaptcha check failed. Please contact your administrator.”

Enabled Front-Only Scanning for Select Passports​

Passports from countries such as India, Slovenia, Ireland, and New Zealand include information on both sides of a page. Previously, attempting to scan the second side resulted in frequent failures. From this release, only the front side is scanned, significantly improving the reliability and performance of passport scanning for these cases

1.10.12​

May 10, 2025​

New Features​

Implemented Retry Mechanism for ID Proofing Sessions​

Community administrators can now configure the number of retry attempts allowed when users fail to complete the verification process. This is managed in DVCID via a new parameter, maxRetries. In 1Kosmos, the status "Verification Not Performed" indicates that the captured image does not meet the required quality criteria, prompting users to retry document scanning.

By default, the maximum number of retry attempts is set to 2, but administrators can increase it up to 5. If the retry attempt count is set above 4, the UI prompts the administrator to correct the verification configuration before continuing.

If users are unable to complete verification within the allowed attempts, their status remains "Verification Not Performed." The UI also displays a number selector to show how many attempts the user has made. For more information, see the Viewing Session Results section in Verification Journey.

1.10.11​

April 12, 2025​

New Features​

Added Expired and Abandoned Statuses in ID Proofing​

1Kosmos now introduces two new statuses in ID proofing: Expired and Abandoned. These statuses can be viewed in the Status drop-down menu of the Verification tab in the AdminX interface. Additionally, the following changes have been implemented as part of this enhancement:

Two new timestamps have been added: expireSessionInMin (time to start) and abandonSessionInMin (time to complete after starting). These timestamps distinguish between Expired and Abandoned sessions. The default time for the expireSessionInMin parameter is set to 7 days, while the abandonSessionInMin is set to 1 hour.

Two new events, E_IDV_SESSION_EXPIRED and E_IDV_SESSION_ABANDONED, are triggered when the session is marked as Expired or Abandoned, respectively. For more information, see ID Verification Events.

API Enhancements​

Enhanced the /result API payload to consistently include the session ID for all session statuses.

Bug Fixes​

Fixed an issue where raw data was not deleted from the DVCID immediately after initial polling, despite specific PII retention flags being set.

1.10.10​

March 15, 2025​

New Features​

Adding Affidavit on behalf of a User​

1Kosmos enables community/helpdesk administrators to add an affidavit to a user’s web wallet allowing them to become IAL2 certified users without the need to physically scan their documents, but instead rely on notarized physical copies to assert their identity. Affidavit in 1Kosmos is a declaration made by the administrators certifying the authenticity of another user's passport (PPT), Driving License (DL), or SSN. The administrator who creates the affidavit assumes responsibility for verifying the accuracy of the document. However, only administrators with the following permissions are authorized to add the affidavit. For more information, see Bypassing Verification Using Notarized Documents.

note

New users will no longer be required to enter a PIN.

  • user.affidavit.add
  • users.view-user
  • users.edit
  • users.all-users

Filter Verification Results by Journey Name and UID​

Two new filters, Journey Name(DVCID) and uid filter have been added to the Verification > Verification page allowing you to filter sessions and download more granular results. For more information, see Verification Journey.

1.10.08​

December 14, 2025​

New Features​

Introduced New Verification Status in ID Proofing​

In certain situations, fraud verification may return a Not Performed result. This generally occurs when the user fails to capture clear, high-quality images. To enhance tracking and provide more accurate verification insights, a new status, Verification Not Performed, has been introduced. This status helps to distinguish cases where fraud verification could not be completed due to poor image quality and also enables businesses to analyze verification trends more effectively. The Verification Not Performed status will appear under the following circumstances:

  • When the verification process is partially completed.
  • When the front side of the document is processed, but it’s unclear whether there is a backside to the document.
  • When the document extraction process fails.
  • When an unsupported document is submitted for verification.

For more information, see Verification Journey.

1.10.07​

November 8, 2024​

New Features​

Filtering Verification Events in ID Proofing​

You can now filter verification events for a specific journey using the following new values:

  • Authenticator ID
  • Device ID
  • Mobile Document ID
  • Mobile Session ID

1.10.04​

April 28, 2024​

New Features​

Introduced the Fraud detection Panel​

When users complete an identity verification request, the 1Kosmos platform runs several checks against the document. In this feature, community administrators are allowed to view which specific check has failed to deem the verification as fraudulent. This gives more visibility and offers options to create an exception mechanism when identity verification fails.

Confidence Score Retention while discarding PII​

1Kosmos now enables community administrators to selectively discard PII (Personally Identifiable Information) according to their preferences. With this enhancement, all PII linked to a user is removed, while the confidence scores for the verification journey are retained. A new <summary> object within the session result now stores the confidence scores for all verification checks.

Introduced ID Verification Session Metrics​

The new analytics page displays the count of verification session completed, passed and all sessions generated. A time-series graph is also available to show the trend of verifications within the community over 90 days (about 3 months).

Reduced time taken to complete verification​

Significant performance optimizations have been made to reduce the overall time required to submit images and receive a verification result.

1.10.01​

March 2, 2024​

ID verification sessions with status ‘In Progress’ will now show session events to give a clear picture of where the user dropped off in the journey.

1.10.00​

February 10, 2024​

New Features​

  • We have introduced a new multi-language template for identity verification that allows customers to add a new language through HTML. This template allows the user to switch the language on the first screen. User’s preferences are carried forward from one screen to the next.
  • Bug fixes around Events fired at the time of document capture.
  • Administrators are now able to create new sessions for a verification journey. When created, the verification session using text message.
  • Administrators can use the scan ID card flow to scan Driver’s license and Passport.

Enhancements & Bug fixes​

  • Bug fixes to address incorrect user agent display for Chrome browser on iOS devices.

1.09.01​

January 27, 2024​

New Features​

  • A new template is being introduced for scanning that allows the user to scan the front and back within the same camera frame.
  • Selfie capture has been made manual to ensure that an accurate image of the user is being captured.
  • If document or image selfie submission fails, a resubmit button appears on the preview page for easy retry.
  • Support added for bypassing Fraud detection when fake documents are presented, facilitating customer testing without the need to share personal data.