Demo: 25 May 2026 | Production: 1 June 2026

Dashboard

Enhancements

eKYC

• A new US eKYC source, US Credit Telco, is now available. It verifies first name, last name, date of birth or SSN (at least one required), along with optional address fields and phone number. The single session view displays individual field match results (exact, fuzzy, no match, or unknown) for each verified field along with an overall match level.
• The single session view now correctly handles Canada eKYC credit file results for files less than 3 years old. When AML regulations prevent returning the credit file number and creation date, placeholder values are displayed instead of empty or incorrect fields.
• Update The eKYC module in the Flow builder now supports display mode configuration for fields sourced from ID OCR or Proof of Address. Each field can be set to Editable (default, preserving existing behavior), Read-only (pre-filled and visible but not editable by the end user), or Hidden (not shown during onboarding). Fields sourced from user input are unaffected.

WORKFLOWS & FLOWS

• A new Enforce Capture Image Attempts setting is available in flow and workflow settings under User Experience > Session Control. When enabled, users who reach the configured maximum number of capture attempts receive an error and cannot retry.

GENERAL

• When submitting an escalation through Dashboard, you can now select multiple values in the Issues drop-down. All selected values are included when creating or uploading an escalation.
• The Hong Kong KYB session results in the Dashboard now display the ownership percentage alongside each verified UBO name.
• The Trust Graph risk indicator for the Known Fraudster Liveness category now displays as "used in a Liveness Spoof Attack" in the Dashboard. The fraud vector modal defaults to Physical Liveness.
• The Privacy Policy and Terms of Use links displayed in the default user consent screen have been updated to point to the latest versions on incode.com. The ML data consent checkbox text has also been updated to remove an outdated reference.

Fixes

• Fixed an issue in Workforce where the Directory Information user list was truncated to 20 or 40 entries after opening a directory profile or applying a filter. The full list is now displayed correctly in all cases.
• Fixed an issue in the Upload Escalation flow where the "Add to Escalation" button remained enabled after removing the uploaded CSV file. The button now correctly resets to a disabled state when the file is removed, preventing unintended resubmission.
• Fixed an issue in the Workflow builder where adding a condition and selecting the No path caused both the Yes and No branches to default to Session PASS. The No branch now correctly defaults to Session FAIL.
• Fixed a missing configuration option in the Workflow builder's ID capture module: the "Add watermark to cropped ID" setting and its tooltip were absent. The option is now available and configurable, consistent with its presence in the Flow builder.
• Update Fixed an issue in the Dashboard's Candidate Verification page where changing the link validity duration would retroactively update the confirmation message for a previously generated link. Each link's confirmation message now correctly reflects the validity duration it was generated with.
• Hotfix Fixed an issue where sessions flagged for manual review could not be approved or rejected when depth information was missing from the capture data. Affected sessions can now be correctly actioned in the Dashboard.

Web App (Onboarding)

Enhancements

• Improvements to the KYB onboarding form layout:
  • Input fields are now displayed side-by-side for a more compact form
  • A container outline has been added around the form
  • The overall presentation is better aligned with standard web form patterns
• Update Updated the China KYB onboarding form to use a single address input field, replacing the previous multi-field address layout. The address field is now mandatory and maps correctly to the corresponding API field. This change resolves an error that prevented China KYB onboarding sessions from submitting successfully.
• Update The browser-based Device Fingerprint now collects an additional set of browser signals, expanding the data available for device identification and fraud detection.

Fixes

• Fixed an issue where custom fields of type decimal (double) could not be submitted in onboarding flows, even when correctly configured in the Dashboard. Users can now enter and submit decimal values in custom fields.
• Fixed an issue where the eyes closed notification during selfie capture was not displayed in the user's configured language. The notification now correctly respects the onboarding language setting.
• Fixed an issue where valid phone numbers were incorrectly rejected with an invalid format error. Phone number validation now correctly accepts properly formatted numbers for all supported country codes.
• Corrected Polish translations for the face capture and verification screens in Webflow integrations. Three text strings have been updated to use more natural and grammatically accurate Polish language.
• Update Fixed an issue where OAuth2-secured onboarding flows failed to redirect correctly when reaching the authentication step.
• Hotfix Fixed an issue where the Deepsight Camera Trust check consistently failed for sessions completed on Windows desktop using Google Chrome, even when no genuine camera or device risk was present. The check now correctly reflects actual device risk on Windows Chrome sessions.

Server

Enhancements

• OCR results now include detailed version metadata for all sub-components used during document processing, including the visual option version, classification set version, and entity extraction pipeline version for each processed side.
• China KYB now uses Incode's in-house algorithm and LLM-based matching on raw data instead of relying on the provider's matching results. This improves accuracy for business names and addresses in Pinyin format.
• Improved edge case handling for Colombia government validation via the Tus Datos provider. Matching accuracy has been improved for sessions where OCR extraction produces names in formats not covered by the standard logic.
• A new error code has been added for AAMVA DLDV verification. Document Number Mismatch represents scenarios where the driver’s license number does not match, but one or more other identity data attributes do match, signifying that the person may be deceased or has been issued a newer driver’s license number. The status for this error code will be FAIL, and this error code will be exposed in Business Rules for handling/decisioning. Contact your Incode Representative or submit a support request if you have questions about this change.
• US government data verification now supports New York for ID documents issued after 2005. This can be provisioned as a separate provider alongside AAMVA DLDV.
• Sessions presenting Indian AADHAR (UIDAI) identification cards are now automatically rejected and no data is processed or stored, in compliance with applicable data protection requirements.
• Organizations can now configure whether set-password invitation emails are sent when new Dashboard users are created. When disabled, new users can only log in via SSO, preventing password-based login bypass. This setting is enabled by default, preserving existing behavior.
• Government Verification for California driver's licenses and IDs now includes digital signature verification for 2025-generation documents. A successful digital signature check confirms the document was issued by the CA DMV and that the barcode data has not been tampered with, enabling accurate distinction between data match and face match results in DMV Face Match sessions.
• Extended EU and UK driver's license restriction code extraction to additional non-standard vehicle classes, including F, K, L, N, P, Q, and others not previously covered. Issue and expiration date extraction for these classes is also now supported.
• The flow configuration API response now includes a digitalIdConfig field with per-method configuration for Digital ID capture methods. Each enabled method specifies the requested identity attributes, supporting selective disclosure for mobile Driver's Licenses (mDL/ISO 18013-5).
• The add/front-id endpoint (v1 and v2) now accepts an extractIdFace boolean parameter. When set to false, face extraction and biometric template creation are skipped for that capture. All other processing (OCR, classification, tamper checks, barcode/MRZ) continues normally. Existing behavior is preserved when the parameter is omitted. Required for Quebec CAI/Law 25 compliance and similar privacy regimes.
• Motion attack detection now uses an ML-based scoring model. The ML result feeds directly into the Behavior trust score with a severity level. When no ML result is available, the existing motion check is used as a fallback, preserving current behavior.
• Organizations can now configure multiple OIDC client credentials integrations simultaneously. Previously, OIDC was limited to a single, auto-created integration.
• Added input validation to the omni/add/device-fingerprint endpoint. String fields now enforce maximum length limits and requests exceeding those limits return a 400 error with a descriptive message.
• The CSV session export now includes Deepsight score columns: physical attack, digital attack, evasion attack, face overall, document overall, overall, device trust, behavioral trust, and camera trust — each with a status and value field.
• Improved the accuracy of government validation result reporting. Error outcomes are now determined by a defined priority order, and sessions that previously returned an incorrect or overly broad error code now surface the correct result, including individual field match details where applicable.
• Update Improved China KYB tax ID matching accuracy. When a tax ID returns no match due to letter case differences between the submitted value and the registry value, the system now performs its own comparison and returns the correct match result.
• Update Updated SCIM role mapping for organizations migrated to Convergence phase 2. Legacy Workforce role identifiers used in SCIM configurations are automatically mapped to their current equivalents, preserving existing role-based access behavior.
• Update The digital attack check has been split into two distinct checks: deepfake attack and digital manipulation attack. These checks are now available separately in session scores and API responses. The existing digital attack check is preserved for backward compatibility.
• Update Improved Colombia government validation to correctly handle sessions where multiple OCR fields return unknown values. Sessions with two or more unextractable fields no longer fail government validation when core identity fields are present and matched.
• Update Re-applied the third-generation browser Device Fingerprint signal collection on the server side, which had been temporarily rolled back as part of an OAuth2 hotfix.

Fixes

• Fixed an issue where Entra EAM enrollment for Workforce failed because the authentication endpoint was receiving a GET request instead of the required POST. Entra External Authentication Method verification now completes successfully.
• Fixed an issue where Gov Validation was incorrectly triggered for sessions presenting documents from countries not provisioned for the client. Sessions from non-provisioned countries now skip the Gov Validation module entirely and are not scored as failures.
• Fixed an issue where PDF documents with oversized page dimensions were rejected during processing. Instead of rejecting, the service now scales the rendering DPI proportionally, ensuring correct processing of PDFs where page dimensions are specified in pixels rather than points.
• Fixed an issue where the document number match type was omitted from Trust Graph continuous monitoring webhook notifications. Webhook payloads now correctly include all match types when a fraud report is found.
• Fixed an issue where sessions completed via the helpdesk verification flow returned an overall score of 0.0 despite passing. The overall score now correctly reflects the session result when Face Authentication is present in the flow but fails due to no existing customer record.
• Fixed multiple data accuracy issues in OCR and MRZ processing: corrected address field extraction for Mexican documents, resolved MRZ data redaction for back-side captures, fixed MRZ parsing for Nigerian ID cards and German driver's licenses, and resolved front barcode parsing for several document types.
• Fixed an issue where onboarding selfie images were incorrectly deleted when the PII deletion job ran, even when the "Retain onboarding selfie & face template" setting was enabled. The setting now correctly prevents selfie data from being removed during PII deletion.
• Fixed a mismatch between SDK-level Deepsight motion configuration and the server-side flow configuration. The flow and workflow configuration endpoints now correctly return motion settings for all relevant capture modules, and server-side validation ensures consistency between SDK flags and the configured flow.
• Update Fixed an issue where the Risk AI model received incorrect face recognition score data (reporting a failure status and no confidence value) even for sessions with a passing face recognition result.
• Update Fixed an issue where customer identities were not reliably created after successful workflow sessions, even when automatic identity creation was enabled. Identity creation now completes correctly for all qualifying sessions.
• Update Fixed an issue where the CURP value extracted from a physical ID document was silently overwritten with an updated CURP returned by the government validation provider.

ML

• Deployed updated ML model versions:
  • Tamper Check 7.0
  • Barcode PDF417 1.14
  • Fake ID Check 1.19
• Deployed a new custom ZXing-based PDF417 barcode reader to the ML preprocessing service, improving accuracy and decoding reliability for documents with PDF417 barcodes.
• Improved injection attack detection accuracy for web-based onboarding sessions. The frame duplication check has been extended to cover additional points during the capture flow, reducing missed detections.
• Improved the accuracy of Deepsight behavioral and replay attack detection in web-based onboarding sessions, reducing missed detections and strengthening protection against reused video injection attempts.
• Fixed an issue where switching context during the loading screen could break the webcam display in web onboarding flows when Deepsight was enabled.
• Added a new injection attack detection check for mobile onboarding flows. The check runs during the post-capture uploading screen for both ID and selfie capture phases, and is not applied on non-mobile devices.
• Added a new virtual camera detection check for mobile onboarding flows. The check runs during the post-capture uploading screen for both ID and selfie capture phases, may add approximately one second to the uploading screen, and is not applied on non-mobile devices.
• Update Improved PDF417 barcode read accuracy across multiple document types and issuing states, reducing incorrect barcode check failures for recently issued documents.

ID Templates

New supported templates

NEW ID SUPPORT

• Fiji
  • DriversLicense / LEARNERS_PERMIT / 2010
• Georgia
  • ResidenceDocument / TEMPORARY_RESIDENCE_CARD / 2025
• Kyrgyzstan
  • IdentificationCard / IDENTIFICATION_CARD / 2025
• Mexico
  • Tabasco
    • DriversLicense / DRIVERS_LICENSE / 2019
• Nigeria
  • IdentificationCard / IDENTIFICATION_CARD / 2008
  • TravelDocument / CONSULAR_CARD / 2018
• Qatar
  • ResidenceDocument / RESIDENCE_PERMIT / 2020
• United States of America
  • Nebraska
    • DriversLicense / DRIVERS_LICENSE / 2026
  • Oklahoma
    • DriversLicense / DRIVERS_LICENSE_UNDER21 / 2026
    • DriversLicense / LEARNERS_PERMIT / 2026
    • IdentificationCard / IDENTIFICATION_CARD_UNDER21 / 2026

NEW CLASSIFICATION SUPPORT

• Laos
  • IdentificationCard / IDENTIFICATION_CARD / 2023
• Mexico
  • MedicalCard / MEDICAL_CARD / 2026
• United States of America
  • TribalIdentification / TRIBAL_IDENTIFICATION_CARD / 1839
  • TribalIdentification / TRIBAL_IDENTIFICATION_CARD / 1840
  • Louisiana
    • IdentificationCard / IDENTIFICATION_CARD / 2001
  • Nebraska
    • DriversLicense / DRIVERS_LICENSE_UNDER21 / 2026
    • IdentificationCard / IDENTIFICATION_CARD_UNDER21 / 2026
    • IdentificationCard / IDENTIFICATION_CARD / 2026

Changes to current templates

FEATURE UPDATE

• France
  • DriversLicense / DRIVER_LICENSE / 2013 r2
    • FRA-ALL-DriversLicense-DRIVER_LICENSE-2013-r2
• Germany
  • DriversLicense / DRIVER_LICENSE / 2011 r3
• Indonesia
  • Passport / NATIONAL_PASSPORT / 2015 r2
• Italy
  • DriversLicense / DRIVER_LICENSE / 2000 r1
  • DriversLicense / DRIVER_LICENSE / 2013 r5
• India
  • IdentificationCard / IDENTIFICATION_CARD / 2015 r3
• Portugal
  • DriversLicense / DRIVERS_LICENSE / 2013 r1
• United Kingdom
  • DriversLicense / DRIVER_LICENSE / 2013 r3
  • DriversLicense / DRIVER_LICENSE / 2015 r2
  • DriversLicense / PROVISIONAL_DRIVER_LICENSE / 2013 r1
  • DriversLicense / PROVISIONAL_DRIVER_LICENSE / 2015 r1
  • DriversLicense / PROVISIONAL_DRIVER_LICENSE / 2021 r1
  • Wales
    • DriversLicense / DRIVER_LICENSE / 2013 r1

ID CLASSIFICATION IMPROVEMENT

• Romania
  • IdentificationCard / IDENTIFICATION_CARD / 2022 r3

ID OCR EXTRACTION IMPROVEMENT

• Cameroon
  • Passport / NATIONAL_PASSPORT / 2021 r1
• Germany
  • IdentificationCard / IDENTIFICATION_CARD / 2010 r5
  • ResidenceDocument / RESIDENCE_PERMIT / 2019 r3
• Lithuania
  • IdentificationCard / IDENTIFICATION_CARD / 2021 r1
• United Arab Emirates
  • ResidenceDocument / GOLDEN_CARD / 2022 r3 - Incode MRZ

Demo: 11 May 2026 | Production: 18 May 2026

Dashboard

Enhancements

FACE AUTHENTICATION

• There is a new setting called Stateless face match in the Face Authentication module configuration. When enabled, Face Authentication uses a selfie submitted via API instead of a stored biometric template. This allows users who have deleted their biometric data after onboarding to still use Face Authentication.
• Updated the warning label in the Face Authentication module configuration. Now you will see this warning: "For webflows, please use OAuth Secured sessions.”

eKYC

• Updated the display name for the Spain eKYC phone register source in module configuration from Spain - Telephone Register to Spain Phone Register 2 to align with updated naming conventions.
• Added two new sources to eKYC for Nigeria:
  • Bank Verification Number (BVN): Displayed in module configuration as MONO BVN NG
  • National Identification Number (NIN): Displayed in module configuration as MONO NIN NG Both sources include Name, Phone, Date of birth, and Tax ID Number. Update Government checks for both sources also support Face Match — the selfie captured during the session is compared against the image from the government verification response, and the result is factored into the session's government verification score.

ID CAPTURE

• Update A new Require Date of Birth setting is available in the ID capture module. When enabled, users are prompted to capture the back of their ID if date of birth was not detected on the front side, even in front-only flows. Disabled by default. Contact your Incode representative if you are interested in this feature.

WORKFORCE

• Improved the global email template UX for the Pegasystems Workforce integration, including layout and visual consistency updates across email notifications.
• Update Workforce now supports configurable default link durations for Candidate and Helpdesk verification. The default TTL (time-to-live) can be set in Configuration > General and overridden per-verification on the Candidate Verification page.
• Update Added an option in the Workforce MDM configuration to hide the enrollment selfie from the verification session.

GENERAL

• Fixed column padding in the Compliance tab's Audit Log table to align with the design system specifications used in other tables across the Dashboard.
• Updated the display label for the selfie quality error code in the single session view. The title now reads "Selfie Image Quality Check Failed" instead of "Selfie Checks Failed" for improved clarity.
• The government verification feature has been renamed to GovMatch in single session view. The tab, score summary, and section titles have been updated to reflect the new product name.
• Update Risk AI Shadow Mode is now available in the Dashboard. When enabled at the organization level, Risk AI scores are calculated in shadow mode without affecting session decisions. Shadow results are visible to Incode Admins in a dedicated Risk AI Shadow tab in the single session view. Shadow mode can be configured independently at the flow and workflow level; when live Risk AI is active, it takes priority over shadow mode.

Fixes

• Fixed a critical issue in the single session view where ID Verification, OCR data, and Capture Attempts from a second captured ID were overwriting results from the first ID. Each document's results are now displayed independently.
• Fixed an issue where ID verification results were showing as N/A when a second ID was submitted via manual upload. Results are now correctly attributed and displayed for both documents.
• Fixed an issue where quickly tapping through the Voice Statement consent prompts allowed users to bypass the voice consent step entirely. The consent flow now correctly enforces completion before proceeding.
• Update Fixed a display issue in single session view where issue type and submitted issue fields did not render correctly when multiple values were present. Both fields now display all values accurately.
• Update Fixed an issue where uploading a logo in the Dashboard's email configuration would cause the logo preview to fail to load. The preview now displays correctly after saving.

Web App (Onboarding)

Enhancements

• Improved the color contrast of Privacy Policy links on the Biometric Consent screen to meet WCAG 2.2 AA accessibility standards.
• The ID document upload flow now enforces a maximum file size of 5 MB for PDF uploads. If a user selects a file that exceeds this limit, a clear error message is displayed and they can select a different file to retry.
• Updated German translations on the Start screen and Age Step Up screen to improve accuracy and clarity.
• The US KYB onboarding flow now includes address autofill. Users can begin typing their business address and select the correct option from a dropdown, which then populates all address fields automatically. This reduces friction and entry errors.
• Update The KYB onboarding form has been redesigned with a desktop-first layout, improving the experience for business users completing onboarding on desktop. The updated form provides a more polished and professional presentation while maintaining consistency across desktop and mobile.

Fixes

• Fixed an issue on the eKYC desktop flow where date entry fields appeared dimmed (inactive) after being populated with a valid value.
• Fixed an incorrect placeholder hint shown for the State Code field in the Argentina eKYC flow. The field now displays the correct format hint (e.g., B, C, K).
• Fixed an issue where custom branding colors for the Data Sharing Consent screen were not reflected on the checkboxes. Checkboxes now correctly adopt the configured styling.
• Fixed an issue where the manual capture fallback screen always displayed ID card placement instructions regardless of the document type being captured. Guidance now correctly reflects the document type selected by the user (e.g., passport vs. ID/driver's license).
• Update Fixed an issue where the Deepsight device trust check incorrectly failed for users completing onboarding on a desktop browser using the built-in camera.

Server

Enhancements

• The third-party onboarding authentication endpoint is now publicly documented in the Swagger API reference.

• The Digital ID document submission endpoint now accepts PDF files passed via image URL in addition to the already-supported base64 format.

• Updated the Slack integration to route users in V2 organizations to the onboarding app, ensuring the correct application is used for verification flows triggered via Slack.

• Added HMAC-authenticated variants of several session creation and session management endpoints: omni/hmac/start, omni/hmac/add/phone, omni/hmac/executive/log-in, omni/hmac/external/send-sms, and omni/hmac/onboarding-url. These endpoints behave identically to their standard counterparts but require two additional headers: RequestDate and an Authorization header containing an HMAC signature. This allows integrators to authenticate API calls using a shared secret key.

• Added a new ONBOARDING_STATUS_CHANGE_ENRICHED webhook type, triggered on ONBOARDING_FINISHED, which includes full OCR and score data in the payload and is signed with HMAC headers for recipient verification.

• EU and UK driver's licenses can now be evaluated against configurable restriction codes extracted from the back of the document (row B, 4th column). Flows and Workflows can be configured to automatically reject licenses based on specific class codes, such as automatic-only driving restrictions.

• Improved the logic for resolving the user's IP address during device fingerprinting. The system now correctly falls back to the IP address provided in the request body when the header IP is local or invalid, ensuring accurate IP capture for sessions using end-to-end encryption.

• Added two new data deletion modes:

  • Biometrics-only deletion (removes images, videos, and biometric templates while retaining other session data)
  • Minimum data mode (retains only the selfie image and face template needed for authentication). These modes provide more granular control over data retention and deletion.

• Updated name parsing for the following Mexican residence document types: MEX|ALL|ResidenceDocument|TEMPORARY_RESIDENCE_CARD|2022, MEX|ALL|ResidenceDocument|TEMPORARY_RESIDENCE_CARD|2000, MEX|ALL|ResidenceDocument|PERMANENT_RESIDENCE_CARD|2022, MEX|ALL|ResidenceDocument|PERMANENT_RESIDENCE_CARD|2000, MEX|ALL|ResidenceDocument|VISITORS_PERMIT|2020, and MEX|ALL|ResidenceDocument|VISITORS_PERMIT|2022. Three changes are included:

  • The firstName, givenName, and fullName fields now return the name in title case as it appears on the document, rather than uppercase
  • Last name separation logic now correctly executes for last names of three letters or fewer
  • When more than two last name parts are present, the full compound surname is preserved in paternalLastName rather than attempting an inaccurate split. The machineReadableFullName, givenNameMrz, and lastNameMrz fields are unchanged.

• Updated the Canada eKYC credit file source to comply with AML regulations: credit file number and creation date are now only returned when the file is at least 3 years old. If the file was created more recently, placeholder values are returned instead.

• Update Under specific configuration, the server now sends a SESSION_FAILED webhook when a Workforce verification link expires, with a failureReason of LINK_EXPIRED. Contact your Incode representative if you are interested in this feature.

Fixes

• Fixed an intermittent 500 error that occurred during ID processing in Workflows when Deepsight was enabled, caused by a concurrency issue in session node handling.
• Fixed a 500 error that occurred when loading a single session in the Dashboard for sessions where a Face Authentication module had been executed and subsequently cleaned.
• Fixed an issue where OCR data was not always deleted when a full session deletion was performed. OCR results are now reliably removed as part of the full deletion process.
• Fixed an issue where the Fraud Risk AI model was not receiving complete cross-check data due to reliance on stale score data. Data collection for the Fraud Risk API call now reads directly from the appropriate source entities.
• Fixed an issue in the Colombia verification flow where the middle name check incorrectly returned FAIL for users with three or more names. The check now returns UNKNOWN, and the Government Validation score is no longer penalized for this field.
• Improved error handling for Idemia integration. The server now correctly parses and maps 400 and 500 error responses from Idemia to the appropriate error codes instead of defaulting to a generic Connection Error.
• Fixed an issue where users were unable to log into Okta after completing an Okta IDP verification flow when a previous Okta IDV flow had already been finished for the same user.
• Update Fixed an issue where a Workforce verification link could be reused without any record of the attempt. Now, if a link is opened a second time, the original session fails immediately and the reuse event is recorded.
• Update Fixed an issue where subsequent onboarding sessions failed after a user's identity had been manually approved in the Dashboard. Selfie capture would fail repeatedly on the next attempt, preventing the session from completing.
• Update Fixed an issue where users with the HIPAA Admin role received a 403 error when attempting to access the Configuration page.
• Update Fixed an issue where sessions using end-to-end encryption displayed an incorrect local IP address instead of the actual public IP address in the single session view. IP addresses are now captured and displayed correctly across Web, iOS, and Android.

ML

• Fixed an issue where the Proof of Address module returned synthetic placeholder address data instead of empty values when the uploaded document was of insufficient quality for address extraction. The module now correctly returns empty or null values in these cases.
• Updated the ID validation service with the following model improvements:
  • Fake ID Check 1.18 — new text-based rules added
  • Screen ID Liveness 7.0
  • Paper ID Liveness 7.0
  • Damaged ID 3.11
  • ID Alteration 3.11
  • Deepsight for Documents 3.11
  • Voided ID 3.11
  • Barcode PDF417 1.13
• The Colombia birth certificate document type now supports extraction of the place of birth field.

ID Templates

New supported templates

Mexico

• Digital Insurance Agents ID / DIGITAL_INSURANCE_AGENTS_ID_PDF / 2026

Nicaragua

• Identification Card / IDENTIFICATION_CARD / 2026

United States of America

• Oklahoma
  • Identification Card / IDENTIFICATION_CARD / 2026

New classification support

United States of America

• Tribal Identification / TRIBAL_IDENTIFICATION_CARD / 1946
• Oklahoma
  • Identification Card / IDENTIFICATION_CARD / 2026

Changes to current templates

FEATURE UPDATE

Bolivia

• Passport / NATIONAL_PASSPORT / 2018 r5

Germany

• Driver's License / DRIVER_LICENSE / 2013 r2

Ghana

• Voter Identification Card / VOTER_IDENTIFICATION_CARD / 2010 r2

Guatemala

• Identification Card / IDENTIFICATION_CARD / 2016 r5

Portugal

• Driver's License / DRIVERS_LICENSE / 2014 r1

United Kingdom

• Driver's License / DRIVER_LICENSE / 2022 r1

ID OCR EXTRATION IMPROVEMENT

Argentina

• Identification Card / IDENTIFICATION_CARD / 2023 r4

Ghana

• ECOWAS Card / ECOWAS / 2019 r3

Guatemala

• Identification Card / IDENTIFICATION_CARD / 2025 r1

Indonesia

• Driver's License / DRIVER_LICENSE / 2023 r1
• Identification Card / IDENTIFICATION_CARD / 2000 r5

Nigeria

• Identification Card / IDENTIFICATION_CARD / 2016 r2

Peru

• Identification Card / IDENTIFICATION_CARD / 2000 r2
• Identification Card / IDENTIFICATION_CARD / 2025 r1

Philippines

• Identification Card / IDENTIFICATION_CARD / 2021 r4

Saudi Arabia

• Driver's License / DRIVERS_LICENSE / 2012 r1

Thailand

• Identification Card / IDENTIFICATION_CARD / 2001 r2

United Kingdom

• Driver Card / DRIVER_CARD / 2018 r2

Vietnam

• Identification Card / IDENTIFICATION_CARD / 1999 r2

Demo: 27 April 2026 | Production: 4 May 2026

Release Highlights

Redesigned Dashboard Navigation

The Dashboard navigation panel has been redesigned. These changes provide a simpler way to interact with and navigate Dashboard in day-to-day operations.

First, pages have been organized into a structured, grouped layout that replaces the previous flat page list. Pages are now organized into three named sections:

• Build & Verify: Includes Sessions, Identities, Authentications, and Flow Builder. The Flow Builder entry expands to reveal Flows and Workflows as sub-options.
• Operations: Includes Analytics, Custom Watchlists, Compliance, Escalations, Case management, and Status.
• Manage: Includes Users, Configuration, Integrations, and Services. The Services entry expands to reveal Directory information, Helpdesk Verification, and Candidate Verification as related to Integrations.

The availability of some of these pages is dependent on your configuration. Contact your Incode Representative for more information.

Next, the organization selector moved from the top of the navigation to the bottom, keeping it out of the way during day-to-day use.

Finally, you can now set a custom start page by clicking the star icon at the top of the navigation. Choose any page from the list and save your preference. The next time you log in, that page will open automatically. Home is selected by default.

Dashboard

Enhancements

SINGLE SESSION VIEW

• Updated the Gov Verification tab of the single session view to align with the Dashboard design system.

eKYC

• There is a new source for eKYC Canada called CA Credit Bureau FINTRAC. This source collects a user’s full name, address, and date of birth in onboarding. The single session view displays matching results for data collected.
• Improved the logic for eKYC Sessions to allow for multiple additional checks to be displayed in the Session results. This means that when Email Check, Phone Check, and Advanced Phone Check are all configured in a Flow or Workflow, all of these checks are run during the onboarding and are displayed in the single session view results.
• A new US eKYC source, US Credit Bureau 3, is now available for credit bureau verification. This check verifies name, date of birth, address, SSN, phone, and email against US credit bureau records, and returns individual field match results along with an overall match level. Contact your Incode representative if you are interested in this feature.

DATA & PRIVACY

• The minimum data mode configuration now supports immediate data deletion scoped to specific session score statuses. When Immediate data deletion at session completion is enabled in Configuration > Data, you can select which score statuses trigger deletion (OK, Fail, Manual, etc.) rather than applying deletion to all statuses uniformly. Deletion is also triggered when a session in Manual review transitions to a new status after approval or rejection.
• Update Updated the maximum number of days for data deletion from 180 to 500.

Fixes

• Fixed an issue that caused Helpdesk employee search to fail. This issue only affected directories with 4000+ employees.
• Fixed an issue that caused the Copy Flow ID and Copy Workflow URL buttons to not work in Safari.
• Fixed the “Enabled On” filter in the Identities list so that future dates cannot be selected.
• Updated the Workflows menu options to display “Workflow” instead of “Flow”.
• Fixed an incorrect empty state message in Compliance > Data Management. When filters are applied that return no results, the page now displays "No sessions" instead of "No deleted data.”
• Update Fixed an issue that caused custom watchlist matches to now display the watchlist ID in the Risk tab of the single session view. Now, when a session triggers a custom watchlist match, the matched record ID is displayed for both onboarding and authentication sessions.

INTEGRATIONS ECOSYSTEM

• Fixed multiple issues in the Integrations Marketplace that were introduced with its initial release.

  Functional fixes:

  • Fixed 500 errors that occurred when:
    • Updating existing Helpdesk, Candidate Verification, and Self-Serve Portal integrations.
    • Saving a Microsoft Entra Directory integration after returning from the Microsoft consent redirect.
    • Attempting to create a second Slack integration. Instead of throwing an error, this is now not an option. By design, only one Slack integration can be configured per organization.
  • Fixed a critical bug where completing the Microsoft Entra Directory admin consent flow returned a 403 Forbidden error instead of redirecting back to the Dashboard. The admin consent flow now completes successfully and redirects as expected.
  • Fixed the browser back button to correctly restore the previously selected tab when navigating away from an integration detail page.
  • Fixed a notification that incorrectly displayed "updated successfully" when creating a new integration for the first time.
  • Fixed a bug where opening an integration configuration would reload and reset unsaved changes every few seconds, preventing users from making edits.
  • Fixed a bug where searching for a term that returned no results on an integration page showed no feedback to the user. A "no results" message is now displayed.
  • Fixed a bug where generating a new client secret in an OpenID Connect integration immediately hid the value instead of displaying it to the user.
  • Fixed a bug where a hardcoded "Workflow1" entry appeared in the workflow selection list for every integration, even when no such workflow existed. The list now correctly reflects only the workflows that have been created.
  • Fixed a missing "Identity verification with a third-party" configuration section that was absent from the Okta IDV Standard integration page.
  • The browser now correctly preserves the current integration page on refresh, rather than redirecting back to the previous integrations list.

  Visual and design fixes to align with the design system include:

  • Incorrect text headings, fonts, and colors across integration detail pages
  • Incorrect image sizes and missing image borders
  • Incorrect logos for Microsoft Entra, Ashby, and OpenID Connect
  • Incorrect background colors for ATS & HR category integrations
  • "Coming soon" section incorrectly displaying with a grey overlay
  • Added a missing demo video on integration detail pages.
  • Fixed broken title and description text for OpenID Connect on the Marketplace page
  • Fixed incorrect authentication method heading and Generate button styling in the Okta IDP integration
  • Fixed the broken Generate button and adjusted styling for the Microsoft Entra integration
  • Fixed incorrect field placeholders, titles, and headings in the OpenID Connect integration

Web App (Onboarding)

Enhancements

• Standardized the placement of error messages in the eKYC Verification module. Error messages for all fields are now displayed under the field.
• Changed the color contrast level on the Unsupported Browser screen to align with a11y standards.
• The Web SDK now supports the alwaysCaptureBackOfId flow configuration flag. When enabled, back-of-ID capture always proceeds regardless of front ID classification result. When disabled or not set, the existing behavior is preserved — back ID capture is skipped if classification fails on the front.
• The KYB onboarding form now validates tax ID format before submission and displays a clear error message when the entered value does not match the expected format for the selected country. Supported formats include CNPJ for Brazil, company registration and VAT numbers for the UK, VAT and registration formats for Germany, the Netherlands, Spain, and Italy, RFC formats for Mexico, and several others. Previously, an invalid tax ID resulted in a generic error after submission.
• Update Updated the expired ID error screens in the Web App to display messaging specific to the expired ID state, including the list of accepted document types where applicable. Also fixed several related issues: retry counters now persist correctly across page refreshes, redirect logic between front and back ID capture works reliably in all flows, and attempt counters are displayed accurately throughout the capture experience.
• Update The Face Match step in the Web App no longer makes a redundant call to retrieve scores after processing a face. The face match result is now determined directly from the face processing response, reducing unnecessary API calls during the step.

Fixes

• Fixed the US Smart Capture flow to display the correct instructional messaging for ID Capture.
• Fixed an issue that caused sessions with multiple document capture modules (including proof of address) to only execute the first one and skip any after that. Now, multiple document capture modules can be used in a single session.
• Fixed element alignment and spacing in the Geolocation step to match the specifications from the design system.

Server

Enhancements

• The platform now verifies encrypted barcode data on driver's licenses and IDs from both South Carolina and Wisconsin. This validation improves document authenticity checks for credentials issued from these states.
• The maximum session retention period for automatic deletion has been extended from 180 days to 500 days, giving organizations greater flexibility in configuring their data retention policies.
• Improved the accuracy of Mexican car invoice (Proof of Address) validation by extracting issuer RFC, recipient RFC, and digital tax stamp UUID from the document's QR code. These QR-derived values are returned as new fields alongside the existing OCR-extracted fields.
• Updated extraction logic for Colombian driver's licenses to support documents with multiple expiration dates across different vehicle categories. Previously, only the first expiration date was extracted, which could cause incorrect rejections for licenses that remain valid for other categories.
• A new API endpoint, /omni/b2b/v1/authentications/add-selfie-to-identity, allows you to add a selfie from an existing session to a user's identity. This supports automated selfie update workflows without requiring manual intervention through the dashboard.
• The platform now enforces end-to-end encryption for face result submissions. Requests that do not use encryption will return an access denied error unless the organization has explicitly enabled non-encrypted submissions.
• Removed a legacy behavior that could override a liveness Fail result with a Warn status when the score fell in a specific range. Liveness scores are now passed through directly from the ML model, ensuring scoring accuracy and preventing potential Deepsight bypass.
• The US KYB API response for business name now returns "Unverified" instead of "Alternate Name" when a TIN is associated with a different business. A separate "Mismatch" label in the TIN task response has also been standardized to "Unverified.”
• The US KYB API response for business name now consistently returns "Approximate Match" instead of "Similar Match," bringing it in line with the standardized KYB response format used for all other countries.
• Updated event logging for the document signing endpoints (/process/sign and /process/signQes) to distinguish between certificate generation calls and actual signing calls. This corrects analytics data that previously double-counted signing events.
• The Pushed Authorization Request (PAR) endpoint now accepts optional customFields, which are passed through to the session start call. This restores the ability to include custom metadata at session initiation when using OAuth2-based flows.
• Updated the reminder configuration for QES (Qualified Electronic Signature) requests sent through Trust Cloud. Signature request reminders are now sent less frequently, reducing notification volume for end users waiting to sign documents.
• Update Continued improvements to Brazil eKYC name matching accuracy. The updated logic enforces correct name order. If first and last names are swapped in the input, the result is now returned as No Match rather than a partial match. Additionally, at least 50% of the full name string must now match the source of truth to be considered a Match or Approximate Match, reducing false positives on partial name overlaps.
• Update Improved phone number validation to block numbers identified as invalid or suspicious, including formally invalid numbers, even when the validation service returns a non-authentication-related error. Also fixed an issue to prevent sensitive data being exposed in endpoint URLs during validation calls.
• Update Added a face quality filter for Facial Validation and Face and Data Validation in select regions. Prior to sending a session to a Government Verification provider, the system now evaluates the quality of the captured selfie image to filter out poor-quality selfies, reducing error rates caused by quality-related failures (e.g. connection errors or incorrectly rejected sessions). Contact your Incode Representative for more details.
• Update Video Selfie recordings can now be uploaded via a dedicated API endpoint using multipart upload, as an alternative to the pre-signed S3 URL approach. This supports environments where direct S3 access is not permitted. The video is split into chunks of up to 10 MB each; the client initiates the upload, sends chunks sequentially, and calls a completion endpoint to signal that the upload is finished. Contact your Incode Representative if you are interested in this feature.
• Update There is a new setting in the Custom Watchlist module called Use fallback search. When enabled, this setting ensures a fallback solution for fetching records. If the primary identifier doesn’t match, the system will attempt a secondary match using other watchlist fields. This increases match coverage, but it also may increase false positives. This setting is off by default.
• Update Added a new fallback government validation provider for Peru (RENIEC) to improve approval rates and reduce verification failures when the primary provider underperforms. This helps maintain onboarding continuity by routing eligible Peru gov-validation checks through the fallback when needed, minimizing drops in pass rates and the need for workarounds or reverts to a different integration.

Fixes

• Fixed a issue where the full name field was incorrectly overwritten with the mother's name value during document processing for Brazilian IDs. Full name is now returned accurately.
• Fixed a parsing error that caused the First Name field to always return as FAIL in responses, regardless of the actual verification result. First Name now correctly reflects the verified status.
• Fixed an issue where ID-only sessions returned a Deepsight overall score without a numeric value. Deepsight now consistently returns a numeric score of 100.0 when the status is Pass and no face capture is included. Deepsight requires additional licensing. Contact your Incode Representative for more information.
• Fixed a bug where the eKYC source was not being saved correctly for Nigeria NIN verification. The configured source is now persisted and returned as expected.
• Fixed a bug where flows configured with External Policy (Claims Matching) would return a 500 error when a PAR request was not used. The flow now completes successfully in this configuration.
• Fixed a bug where the liveness/physical attack score was counted twice when calculating the total face authentication score. The Face Authentication score is now calculated correctly.
• Resolved the root cause of intermittent 500 errors occurring on the /add/front-id/v2 and /add/back-id/v2 endpoints. These endpoints now handle edge cases that previously caused server errors.
• Fixed a 500 error that occurred during certificate issuance when a password was included in the request. Certificate issuance now completes successfully.
• Fixed a bug where the /omni/add/rfc-by-curp endpoint was not storing CURP validation results in the session. Both CURP and RFC results are now stored and returned by omni/get/scores, and the RENAPO check is now visible in the Dashboard without requiring a separate omni/add/curp call.
• Fixed a critical bug where users were not redirected after completing a successful verification session in an OAuth2-secured flow, preventing them from obtaining an authorization code. Redirection now completes as expected following successful verification.

ML

• Fixed an issue where name casing normalization applied to Mexican residence documents was interfering with server-side name splitting logic. Name fields on Mexican Temporary Residence Cards, Permanent Residence Cards, and Visitor Permits are now returned with consistent casing that supports accurate field parsing.
• Updated the document readability model to use mean aggregation instead of minimum score aggregation, and adjusted the detection threshold accordingly. This reduces false rejections on documents where a single word or region scores below threshold, improving acceptance rates for legible documents.

ID Templates

New supported templates

Cameroon

• ResidenceDocument / RESIDENCE_PERMIT / 2023

Ethiopia

• IdentificationCard / DIGITAL_IDENTIFICATION_CARD / 2025

Mexico

• Other / DIGITAL_CURP_CERTIFICATE_FOR_MEX_CITIZENS_PDF / 2026
• Update IdentificationCard / DIGITAL_INSURANCE_AGENTS_ID_PDF / 2026

Slovenia

• ResidenceDocument / RESIDENCE_PERMIT / 2020

New classification support

Cambodia

• ResidenceDocument / PERMANENT_RESIDENCE_CARD / 2025

Iraq

• ResidenceDocument / IMMIGRATION_CARD / 2023

Changes to current templates

ID OCR EXTRACTION IMPROVEMENT

Cameroon

• IdentificationCard / IDENTIFICATION_CARD / 2025 r1

Colombia

• DriversLicense / DRIVER_LICENSE / 2013 r3

France

• DriversLicense / DRIVER_QUALIFICATION_CARD / 2020 r1

India

• Karnataka
  • DriversLicense / DRIVERS_LICENSE / 2005 r2

Ivory Coast

• DriversLicense / DRIVERS_LICENSE / 2014 r1

Japan

• DriversLicense / DRIVER_LICENSE / 2000 r2

Mexico

• ResidenceDocument / TEMPORARY_RESIDENCE_CARD / 2022 r3

Netherlands

• ResidenceDocument / RESIDENCE_PERMIT / 2014 r2

Philippines

• IdentificationCard / DISABILITY_IDENTIFICATION_CARD / 1987 r1
• IdentificationCard / IDENTIFICATION_CARD / 2023 r2 — Updated to cover both physical and digital card variants, improving OCR accuracy for on-screen and laminated digital IDs.

Rwanda

• IdentificationCard / REFUGEE_IDENTIFICATION_CARD / 2022 r1 — Corrected field extraction order for full name.

South Korea

• DriversLicense / DRIVER_LICENSE / 2000 r6 — Resolved misclassification of 2000-series licenses as 2020, and fixed full name extraction.
• DriversLicense / DRIVER_LICENSE / 2020 r4

United States of America

• California
  • DriversLicense / DRIVERS_LICENSE / 2018 r3

Demo: 13 April 2026 | Production: 20 April 2026

Release Highlights

INE Fingerprint Validation

You can now configure fingerprint capture and validation as part of the Mexican INE (Instituto Nacional Electoral) government identity verification flow. In the Government Record Verification module, when Mexico is the selected country, three new fields are available:

• Fingerprint Validation
• Minimum Passing Fingerprints
• Fingerprint Match Override Score

When this feature is configured in a Workflow or Flow, users can upload biometric fingerprint data alongside facial and ID information during an onboarding session. This data is then submitted to INE for identity confirmation. The platform automatically selects the optimal fingerprints to submit, preferring a matched pair from both hands, and returns per-finger confidence scores alongside face match results and ID data comparison results.

This feature supports both remote and in-person (assisted) onboarding modes and is compatible with ANSI, WSQ, and RAW fingerprint image formats. Contact your Incode representative if you are interested in this feature.

Dashboard

Enhancements

WORKFLOWS & FLOWS

• Updated the Workflow Builder canvas to improve usability. Changes include:
  • Made the add-node button is always visible (previously hover-only)
  • Added a ghost node preview on hover
  • Display node descriptions with consistent color-coded icons in the add-node dropdown

MODULES

• There is a new setting in the Face Capture module called On-Device Processing. This setting allows you to enable on-device liveness and age verification, supporting use cases where biometric images must not leave the SDK. Contact your Incode Representative to enable this feature in your organization. Once available, the setting is Off by default.
• Update Added support for Directors in the KYB onboarding flow. When Directors are enabled in the KYB module configuration, an optional Directors input field is available in the onboarding form, similar to the existing UBOs field. Directors and UBOs can be enabled independently. Director input is supported for organizations in the UK, France, Spain, Netherlands, Italy, and Germany.

CONFIGURATION

• There are two new settings in Configuration > Data:
  • Immediate data deletion at session completion: When enabled, session PII data is deleted as soon as a session is completed, rather than following the organization's scheduled retention policy.
  • Retain onboarding selfie & face template for authentication: When enabled, the user's selfie image and face template are preserved after session completion to support re-authentication and claims matching. If any claim-matching fields are configured for retention, this setting must also be enabled. Disabling this setting will clear all claim-matching field selections.

SINGLE SESSION VIEW

• Improved the Gov Verification tab in the single session view to display data fields in a more logical order.
• Added a results display for fingerprint government validation in the single session view. The tab shows pass/fail status for each submitted finger across left and right hand sections, with color-coded indicators for matched, unmatched, and unavailable fingers. A summary banner displays the number of fingerprints matched against the number required to pass. Optional metadata such as device, resolution, image type, and quality score are shown when available.
• Update The single session view now displays additional detail for face ML model results, including a category classification and a text-based description to help explain the outcome of liveness and spoof detection checks.

OTHER

• Added French-Canada (fr-CA) as a selectable language when creating custom consent screens.

Fixes

SESSION RESULTS

• For sessions with more than one attempt, fixed an issue where Dashboard showed the Fake ID Check result from the first verification attempt instead of the most recent one.
• Fixed an issue where a rule applied to second ID validation was being displayed in the first ID section of the single session view.
• Fixed an issue where the Claims Match status did not automatically update after a manual review request was approved or rejected.
• Fixed an issue where sessions failed to display when the candidate session modal was reopened for the same identity.

WORKFLOWS & FLOWS

• Fixed the preview panel in the Flow Builder so that modules are displayed in the order they execute during onboarding rather than mirroring the module list.
• Fixed an issue where leaving the Workflow Builder without saving could leave an async node in an invalid position, causing a 400 error when attempting to re-open the workflow for editing.
• Fixed an issue with Conditions in Workflows that caused the last step to be deleted if any previous step was deleted.
• Updated the Flow Builder “unsaved changes” confirmation dialog so that all text is visible. Previously, there was a heading in white text on a white background.

FILTERS & DATA DISPLAY

• Fixed an issue where combining the "Created At" and "Number of Sessions" filters on the Workflow list returned no results.
• Fixed an issue in Safari where the arrow navigation in date picker filters did not change the displayed month.
• Fixed an issue where applied filter labels displayed the placeholder text "Selected title" instead of the filter name. This change was applied to filters for Workflows, Escalations, Custom Watchlist, and Compliance.
• Fixed an issue with date range filters where the start and end date labels appeared in reversed order.
• Fixed an issue where sorting Identities by Last Verification had no effect.

INTEGRATIONS

• Fixed an issue that prevented users from adding more than one redirect URI when creating or editing an OIDC integration.

ACCESSIBILITY

• Fixed a keyboard navigation issue where the toggle inside the Live Flow button received its own focus state. This fix aligns with WCAG 2.2 AA standards.
• Fixed WCAG accessibility issues in the Flow Builder search filter, including a missing region role/aria-label on the wrapper and missing live region announcements for filter results.
• Updated the color values for the "YES" and "NO" branch labels in the Workflow Builder condition node to meet WCAG 2.2 AA contrast requirements.

Web App (Onboarding)

Enhancements

DESKTOP CAPTURE

• Updated desktop ID capture to attempt the highest available resolution first and step down only on failure. This means that images captured at up to 1920×1080 are now possible on desktop.

FORMS

• Updated dropdown fields in custom forms to show a "Select option" placeholder as the default selected value, requiring users to make an explicit selection before the Done button is enabled.

DOCUMENT CAPTURE

• Update The web document capture flow now supports a variable number of pages for multi-page document types. After capturing the first page, users are prompted to add additional pages or finish the submission. All pages are submitted as part of the same document session, and previously captured pages are preserved if an error occurs.

Fixes

eKYC

• Fixed an issue in the eKYC form where a submission error for the postal code field persisted alongside a new inline validation error when the user began re-entering the field.
• Fixed an issue where clicking the Address field in the eKYC form did not move focus to the input on iOS, requiring users to scroll up to see what they were typing. A minor focus glitch on Android was also resolved.
• Fixed an issue where the Address field could not be typed into on eKYC forms. Additionally, ensured the mandatory state of fields was respected prior to submission.

FACE CAPTURE

• Fixed feedback messages during face capture appearing too far from the face capture frame and too close to the bottom of the screen.
• Fixed an issue introduced by webcam resolution updates that caused the desktop face capture camera preview to be excessively zoomed in, requiring users to move far from their camera to fit their face in the frame. This issue was resolved for both UXv1 and UXv2.
• Fixed an issue where both auto capture and manual capture were completely non-functional during selfie capture in Incode Verify V2 flows.

ANDROID WEB VIEW

• Fixed an issue on Android 8 devices where tapping and holding within the face capture frame caused the touchscreen to become fully unresponsive, requiring a hard reset to recover.
• Fixed an issue on the HONOR 200 Lite (Android 14) where the screen went black during face capture and subsequently blocked all web flows from accessing the camera, requiring a device restart to resolve.

OFFLINE MODE

• Fixed the Retry button being unresponsive when Incode ID is used with FMF verification in offline mode.
• Fixed QR code misalignment when saving as PDF on Android devices during offline mode. QR codes are now centered and fully displayed regardless of paper size or orientation.

PRIVACY & NAVIGATION

• Fixed an issue where refreshing the Privacy Center page loaded the Privacy Policy screen instead, and navigation back to the Wallet was unreliable until the page was refreshed again.

GENERAL

• Fixed a blank screen displayed when launching an onboarding session from a workflow link.
• Update Fixed an issue in the Accept and Sign (AES) screen where the terms and conditions hyperlink was not functional, preventing end users from accessing linked content during the document signing step.
• Update Fixed an issue where tutorial media assets embedded in web-based onboarding flows were inadvertently loading non-essential cookies during end-user sessions. Affected assets now load without passing website-level cookies, ensuring end-user workflows remain isolated from site-level cookie behavior.
• Update Resolved an issue where consent links in embedded and web flows caused broken navigation and resulted in empty sessions. Consent link handling has been corrected to maintain proper flow state.

LOCALIZATION

• Fixed error message translations not being applied on the phishing resistance error screen.

CUSTOMIZATION

• Fixed the "Continue on Desktop" button on the mobile redirection screen not respecting the custom color set in Dashboard settings.

EMAIL

• Fixed emails from the Candidate Verification module incorrectly displaying "Help Desk Verification" instead of "Candidate Verification" in the email content.

FAN ID

• Fixed the 'Registration of minors' icon rendering at a larger size than other icons, with misaligned text, in the Tips for Best Experience section on desktop.

ACCESSIBILITY

• Update Fixed WCAG accessibility issues on the mobile redirect screen:
  • The QR code image was missing an accessible label
  • Instructional text did not meet minimum color contrast requirements
  • Focus was not directed to the page heading for screen reader users.
• Update Fixed a WCAG 2.2 AA compliance issue where animations on ID capture and face capture tutorial and capture screens ran indefinitely without a way to stop them. Animations now end within 5 seconds.
• Update Updated the unsupported browser screen in IDV2 to:
  • Use the updated design
  • Display before the Start screen is shown
  • Meet WCAG 2.2 AA accessibility requirements including sufficient color contrast and correct screen reader handling for decorative images.
• Update Resolved an accessibility issue where users navigating the Combined Consent (Data Sharing Consent) screen with VoiceOver were unable to interact with checkboxes or proceed through the flow. Consent checkboxes are now properly accessible to assistive technologies, and the screen includes appropriate ARIA labeling and focus management.

Server

Enhancements

ID CAPTURE

• When Deepsight is enabled, liveness checks now run whenever any liveness check type is selected, regardless of whether the physical check is turned on. Previously, liveness was not executed if the physical check was disabled. Deepsight requires additional licensing. Contact your Incode Representative if you are interested in Deepsight.
• Improved city extraction from Canadian ID barcodes for Nova Scotia 2017 templates.
• Added support for the "T" (Transgender) gender value in OCR extraction, barcode parsing, and validation for Colombian National IDs issued starting in 2026.
• Added backend support for a new credential emission number field extracted from Mexican INE documents via Proof of Address processing.

DOCUMENT CAPTURE

• Update Additional fields from Finance Settlement Letter (FSL) documents are now available for use in crosschecks and rules. The vehicle registration number can be crosschecked against other document fields, and new presence-based rules are available for FSL-specific data points including vehicle registration number, agreement reference, account number, sort code, and settlement figure.

eKYC

• Added support for US address verification via a new eKYC source (US_Address_1). This integration validates US street addresses against USPS deliverability data and returns granular match results for street, city, state, and ZIP code, as well as name matching, deliverability status, address validity, and risk-level reason codes. Contact your Incode Representative if you are interested in this feature.

eKYB

• Update The UK KYB flow now accepts 9-digit VAT numbers without a country prefix. When a 9-digit tax ID is submitted, the country prefix is automatically appended before the verification request is sent, reducing submission errors for users who enter the numeric portion of their VAT number only.

LIVENESS & FACE PROCESSING

• Updated the face processing service to use an improved face occlusion model, providing more accurate detection across low, medium, and high severity levels.

ON-DEVICE PROCESSING

• Added a new endpoint for submitting face validation results processed on-device, supporting use cases where biometric data must not leave the SDK. This feature is disabled by default. Contact your Incode representative if you are interested in this feature.

DATA & PRIVACY

• Added support for configuring minimum data retention on the Omni platform. Organizations can now specify which claim matching fields to retain after session cleanup via the removal policy settings.
• Update Improved disaster recovery data replication reliability. The replication process now uses the same session approval method as the source environment, and correctly handles cases where a session already exists in the target environment, preventing data duplication when replication runs more than once.

SECURITY

• Updated the CryptoService to use FIPS-compliant cryptographic libraries. This change has no impact on external behavior.

GOVERNMENT VALIDATION

• Update Middle name is now included when performing government validation for Colombia, improving identity match accuracy and reducing fraud risk for users with middle names on their government-issued documents.

Fixes

DEEPSIGHT

• Fixed an issue where the score API response was missing the Deepsight component in the reason message when a session ended in warning status due to Deepsight thresholds. Deepsight requires additional licensing. Contact your Incode Representative if you are interested in Deepsight.

ID CAPTURE

• Fixed a caching issue in ID capture pre-processing where documents submitted with different ID type parameters were incorrectly returning cached results from a prior request.
• Fixed an issue where the full name field for Brazilian Identification Cards (2020) issued in the state of Amapá was incorrectly extracted with "AMAPÁ" included as part of the name.
• Fixed MRZ line format and composite check digit validation failures affecting Korean passports.
• Fixed an issue where US Smart Capture mode was not functioning correctly on Android and iOS, causing the flow to proceed as a standard front + back + selfie capture instead of the Smart Capture flow.

WEBHOOKS

• Fixed an issue where webhook authentication configuration was missing for organizations created via cloning, causing webhook auth updates to fail.

GENERAL

• Fixed an incorrect class reference in the Risk AI flow module configuration that was causing Risk AI flows to fail.

ML

• Updated Fake ID Check to add text-based validation rules for Polish, American, Filipino, and British documents.
  • Update Extended US text-based validation rules to additional state-issued driver's licenses and ID cards.
• Updated Barcode PDF417 to introduce validation warnings for additional barcode fields and reduce both false rejections and false accepts.
• Added extraction of the credential emission number field from Mexican INE documents via Proof of Address processing.
• Improved extraction of name, full address, and issue date from EU and UK Proof of Address documents.
• Update Updated the digital liveness detection model to v10.2.0. This release significantly improves detection of synthetic face spoofs, including deepfake-generated images, reducing missed spoof detections from approximately 75% to under 5% for the affected attack types. Performance on other hard synthetic spoof categories is also improved.

ID Templates

New supported templates

Federated States of Micronesia

• DriversLicense / DRIVERS_LICENSE / 2023

Guinea

• VoterIdentification / VOTER_IDENTIFICATION_CARD / 2017

Iceland

• ResidenceDocument / RESIDENCE_PERMIT / 2020

India

• Bihar
  • DriversLicense / DRIVERS_LICENSE / 2024

Laos

• IdentificationCard / IDENTIFICATION_CARD / 2024

Moldova

• ResidenceDocument / RESIDENCE_PERMIT / 2023

United States of America

• TribalIdentification / TRIBAL_IDENTIFICATION_CARD / 1905
• Oklahoma
  • DriversLicense / DRIVERS_LICENSE / 2026

New classification support

Update China

• TravelDocument / EXIT_ENTRY_PERMIT / 2014

Dominican Republic

• DriversLicense / DRIVERS_LICENSE / 2026

Ecuador

• DriversLicense / DRIVERS_LICENSE / 2015

Romania

• ResidenceDocument / RESIDENCE_CARD / 2020

United States of America

• Oklahoma
  • IdentificationCard / IDENTIFICATION_CARD / 2026

Changes to current templates

ID OCR EXTRACTION IMPROVEMENTS

Andorra

• Passport / NATIONAL_PASSPORT / 2017 r2

Australia

• Tasmania
  • DriversLicense / PROVISIONAL_DRIVERS_LICENSE / 2015 r4

Brazil

• FederalID / DOMESTIC_IDENTIFICATION_CARD / 2004 r5
• FederalID / IDENTIFICATION_CARD / 2020 r6

Colombia

• IdentificationCard / IDENTIFICATION_CARD / 2020 r4

Ireland

• DriversLicense / DRIVER_LICENSE / 2013 r1

Malaysia

• IdentificationCard / IDENTIFICATION_CARD / 2012 r3

Mexico

• Baja California Sur
  • DriversLicense / DRIVERS_LICENSE / 2016 r1
• Puebla
  • DriversLicense / DRIVERS_LICENSE / 2018 r1

Netherlands

• DriversLicense / DRIVER_LICENSE / 2018 r6
• IdentificationCard / IDENTIFICATION_CARD / 2014 r5

Nigeria

• IdentificationCard / IDENTIFICATION_CARD / 2022 r4

South Korea

• Passport / NATIONAL_PASSPORT / 2008 r4 - Incode MRZ
• Passport / NATIONAL_PASSPORT / 2022 r4 - Incode MRZ

Ukraine

• Passport / NATIONAL_PASSPORT / 2015 r5

United States of America

• Hawaii
  • DriversLicense / DRIVERS_LICENSE / 2021 r2 - Incode OCR
• Mississippi
  • DriversLicense / DRIVER_LICENSE_UNDER21 / 2024 r2
• New York
  • DriversLicense / LEARNERS_PERMIT / 2022 r3
• North Carolina
  • DriversLicense / LEARNERS_PERMIT / 2024 r2
• US Virgin Islands
  • DriversLicense / DRIVERS_LICENSE / 2018 r2
• Vermont
  • DriversLicense / DRIVERS_LICENSE_UNDER21 / 2019 r2
• Wisconsin
  • DriversLicense / DRIVERS_LICENSE / 2023 r2

Demo: 30 March 2026 | Production: 6 April 2026

Release Highlights

Updates to Expired ID Handling

📘

Currently available for Web implementations only.

Starting in this release, expired documents are always detected, classified, and flagged. This impacts the clarity and accuracy of reporting and downstream workflows, especially for compliance and audit use cases. The Document Expiration Detected test determines the expiration status of the document as a fact, but does not impact the score or the result.

You still control whether an expired document should block the user. When a document is determined to be expired, the Document Expired test evaluates it against your configurations to determine if the session should pass or fail. By default, expired IDs are not accepted. If you want to specify a different policy, you need to configure the Disable Expiration Date Check and expiration tolerance settings in the ID Validation module.

With the changes in this release, even if you choose to allows expired IDs, reviewers still have full visibility that the ID was expired in the session results for compliance and audit needs.

If you choose to not accept expired IDs, users get clear and immediate feedback in the Onboarding flow and will be prompted to try a different ID. This helps reduce cases where users complete the full flow only to fail at the end due to using expired ID.

Dashboard

Enhancements

General:

• Updated the UI and behavior for fields in the Integrations section to align with the look and feel of the rest of Dashboard.
• When creating or editing a user with the “Executive with custom permissions” role, you can now assign them permissions related to Directory Information, Integrations, Helpdesk verification, and Candidate verification.

Single Session View:

• The Government Verification tab in the single session view has been updated with the following improvements:

  • Updated terminology: "Gov Verification" has replaced "Gov Validation" to align with the official naming convention for the feature.
  • Streamlined section titles: "Data Match" and "Face Match" have replaced redundant "score" labels.
  • Clarified comparison labels: "Document Data vs Government DB Data" and "Selfie vs Government DB Portrait"
  • Reordered layout: Data Match is placed before Face Match to reflect the actual verification workflow.
    These enhancements unify the look and feel of the Gov Verification tab with other areas of Dashboard to deliver a more intuitive experience that helps teams quickly understand and act on identity verification results.

• Added a new field to the ID OCR section of the single session view called Credentials Provider. When the ID submission method is Imported credential (as opposed to camera capture or manual entry) this field displays whether the import came from Apple, Google, or Digilocker.

• Improved the Government Verification results in single session view to align the design system used elsewhere in Dashboard.

Workflows & Flows:

• There is a new setting in Workflow and Flow settings called Enable new user experience. This setting allows administrators to enable UXv2 at the Workflow/Flow level, which helps control when and how you roll out enhanced interface improvements to their end users. UXv2 must be enabled on the backend by your Incode representative before this setting is visible.
• Implemented multiple WCAG accessibility improvements in the Workflow builder and settings. Improvements include new aria-labels for several fields and more descriptive labels for option buttons on nodes. These improvements ensure a quality experience for users that rely on assistive technologies.
• Implemented multiple WCAG accessibility improvements in the Flow builder and settings. Improvements include ensuring links are focusable and indicated as links, adding missing heading labels, correctly assigning aria-labels to buttons, and improving the usability of the search filters. These improvements ensure a quality experience for users that rely on assistive technologies.

Modules:

• The Image Quality check in Face Capture and Face Authentication modules is now enabled by default and cannot be turned off. This ensures the minimum necessary quality is maintained for downstream product performance (like Deepsight or Face Match). The threshold drop-down is still editable and is set to Ultra Low by default. No existing thresholds for this check are impacted by this update.
• Added US TELCO 5 as a new data source for phone-based identity verification in the US eKYC module. The Onboarding user must enter phone number as a required input, with optional name, address, date of birth, SSN, and email fields. Session results include granular match signals for individual name components (first, middle, and last name), address components, and phone activity data.
• Added India PAN as a new data source for PAN-based identity verification in the eKYC module. The Onboarding user must enter name and PAN number as required inputs. Session results include match signals for PAN number and name, along with additional PAN details such as status, status description, holder type, and last updated date.
• Removed the option for Third ID configuration support from the ID Capture module. You should use the Document Capture module instead.
• Update You can add Phone Number Risk and Advanced Phone Number Risk checks to any eKYC source. When these checks are added, the phone number field becomes required in the onboarding flow. For eKYC sources that don’t include phone number by default, including these checks adds the required phone number field to the onboarding flow.
• Update You can add the Email Risk check to any eKYC source. When this check is added, the email field becomes required in the onboarding flow. For eKYC sources that don’t include email by default, including this check adds the required email field to the onboarding flow.

Fixes

• Country-specific document capture settings now save reliably and display correctly in exception views. Admins can configure options for a specific document type without those changes incorrectly applying to other document types. These fixes give administrators complete visibility and control over custom configurations across all workflows and document types.
• Fixed an issue with the Sessions list filter where applying certain date filters would switch to a different filter type.
• Fixed an issue where the City input from eKYB was not shown in the single session view.
• Fixed an issue where Helpdesk and Candidate Verification Sessions were not loaded and displayed in the proper order. Now, these Session lists are sorted in ascending order, with the newest at the top.

Web App (Onboarding)

Enhancements

• The qualified electronic signature (QES) consent flow now includes comprehensive checkboxes to ensure full regulatory compliance with EU eIDAS standards.
• The biometric consent experience now includes enhanced accessibility features with properly labeled headings, titles, and checkboxes. This makes it easier for all users, including those using assistive technologies, to understand and navigate the consent process with confidence.
• Update The OTP entry field has been redesigned from six separate digit inputs into a single unified input field. This update improves compatibility with native device autofill, allowing verification codes received via SMS or email to populate automatically. Users can also paste a code directly into the field, and verification triggers automatically once all six digits are present.
• Update Enhanced the security of data transmission during the verification flow by migrating to a more secure and performant implementation. This change provides stronger protection for user data without any change to the onboarding experience.

Fixes

• The eKYB form now includes improved error handling when users change country selections, ensuring validation messages only appear when users interact with fields.
• Reordered the input fields in the KYB onboarding form so the mandatory fields are listed first.
• Phone numbers captured in earlier steps now automatically populate the eKYC module including the country code, ensuring seamless data transfer and reducing user errors during identity verification.
• The biometric consent workflow now seamlessly transitions users from ID capture to the next step.
• The document capture experience now flows seamlessly without repeating tutorials, ensuring users can complete their verification journey smoothly, especially on devices with varying performance levels.
• Fixed an issue with the UXv2 ID Capture and Face Capture modules on Web where manual review was not triggered after a user failed all selfie capture attempts. Manual Review now reliably triggers as expected when configured in these modules, ensuring sessions are properly routed for review when needed.
• Fixed a UI issue in the UXv2 CURP verification step on Web where a “Try again” button could appear even though users couldn’t actually retry. The screen now only shows the appropriate next actions (for example, “Continue” or “Verify manually”), reducing confusion and keeping the onboarding flow consistent.
• Fixed an issue that caused a configured custom subtitle to be replaced by the generic “Demo app” subtitle.
• Fixed an issue for specific Android devices that caused the touchscreen function to stop working during the Face Capture step of Onboarding.
• Update Fixed an issue that caused a flow to not start on devices running iOS 14.
• Update Fixed an issue in the Forms and Data Entry module that caused the Done button to be unavailable even after all fields were filled out.
• Update Fixed an issue where postal codes in incorrect formats were accepted without error during UK voter registration. Users who enter an invalid UK postal code will now see a validation error prompting them to enter a correctly formatted value.
• Update Fixed a layout issue on desktop where verification flow pages were aligned to the top of the screen instead of the center. Pages now display centered on desktop as intended.
• Update Fixed an issue where users were prompted to capture the second page of a document twice during the document capture step. The flow now proceeds correctly after the second page is captured and validated.
• Update Resolved a performance issue that started after a prior release that caused a significant increase in onboarding session time. Model loading now completes in the expected timeframe, reducing overall session duration.
• Update Fixed an issue on Android where the selfie tutorial was briefly displayed again after a user tapped "Try Again" following a failed selfie capture. The flow now proceeds directly to the selfie camera without replaying the tutorial.
• Update Resolved an issue where the Deepsight liveness physical check was failing for legitimate users during onboarding in the Android Web View. The physical check now passes correctly under normal onboarding conditions.

Server

Enhancements

General:

• Added support for including personally identifiable information (PII) fields when exporting session data to CSV. This setting is OFF by default, but organizations that already have this capability through another method retain current behavior. Contact your Incode representative if you are interested in this feature.

• Updated backend services to operate in FIPS-compliant mode. None of these changes affect external-facing functionality or service behavior.

• Improved the accuracy of backside document recognition for US IDs. The system now considers a broader set of possible document types when identifying the back of a document and selects the best match based on what was captured on the front. This results in more reliable classification results.

• Updated the Apple Wallet integration to follow security best practices for preventing replay attacks. The integration now generates a unique, single-use request token for each session, and both the native and web Apple Wallet flows now support requesting the same specific set of user data fields, ensuring a consistent experience across integration types.

• Three new NFC-related rules are now available in the Rules Engine (Flows) and as Conditions (Workflows) under a dedicated NFC section:

  • NFC Step Skipped (Yes/No): indicates whether the user skipped the NFC scanning step
  • NFC Data Present (Yes/No): indicates whether NFC data was successfully captured
  • NFC Data Integrity Check (OK/Fail): indicates whether the NFC chip data passed integrity validation
    These can be used to enforce NFC requirements. For example, you can use these rules to automatically fail a session when NFC scanning was skipped or when a chip was expected but no data was captured.

• Added a new configuration option, alwaysCaptureBackId, to the omni/onboarding/flow API response. This allows the frontend to control whether the back of an ID is always captured, even when front ID classification is unsuccessful. The option defaults to off to maintain existing behavior. API documentation has been updated to reflect this addition.

• Improved Deepsight's ability to detect AI-generated and synthetic media through enhanced content provenance checks. Contact your Incode representative if you are interested in this feature.

• The POST omni/b2b/onboarding/request-new endpoint now includes interviewId in its response, allowing downstream integrations to correlate the onboarding request with the corresponding onboarding completion webhook.

• The Microsoft Entra ID SCIM integration now supports the incodeDashboardRole attribute, allowing organizations to provision and manage Incode Dashboard user roles directly through their Entra ID directory sync.

• Improved address match logic for US KYB to handle cases where only partial address fields are provided. When a postal code is submitted without a city, cityMatch is no longer returned and postalCodeMatch reflects the verification result. When a city is submitted without a postal code, postalCodeMatch returns as Unverified and cityMatch reflects the verification result. In both cases, addressMatch returns as Approximate Match.

• The OAuth Secured Sessions authorize call now accepts a language parameter, supporting the same ISO language tags as the standard session start endpoint. This allows the onboarding language to be specified when initiating OAuth-secured sessions.

• Fixed an issue where certain session-related records were not fully removed when a session was deleted, including workflow execution tracking, verification results, external integration session data, capture attempts, and other associated data.

Government Verification:

• Improved the accuracy and interpretability of error codes returned by the US Government Verification API. Error codes now reflect the highest-signal result based on available information, distinguishing between input validation failures, connection errors, and provider-level results. Validation and configuration errors that prevent a provider call from being made now return UNKNOWN status rather than FAIL, ensuring results accurately reflect what the system was and was not able to determine. Refer to the developer documentation for detailed information on what’s changing and the actions you need to take. For questions about how these changes may affect your implementation, contact your Incode representative.
• Removed raw provider response data from the US Government Verification API fetch/scores response. The API response now only contains fields defined for customer consumption, improving clarity and ensuring customers are not exposed to unprocessed or potentially misleading provider-specific data.
• Updated provider labels in the US Government Verification Dashboard tab to align with current product naming. AAMVA DLDV provider displays "DMV DATA MATCH".
• Improved the interpretability of US Government Verification session results in the Omni Dashboard. Error codes are now correctly mapped to Data Match and Government Verification summary section scores, making it easier to understand what passed or failed in a given session without additional assistance.
• Updated the Data Match response for US Government Verification to improve consistency and completeness across providers.
• Update Added support for a new 451 response code introduced by the government validation service used for Brazil buyer verification. The platform now correctly maps and handles this response code, ensuring accurate verification outcomes and metrics.

ID support requests:

• Added extraction of the Mother's Maiden Name field from the back of the Hungary Identification Card.
• Improved classification accuracy for the back side of the Mexico City (CDMX) 2025 Driver's License.
• Added support for the new Nicaragua Cédula de Identificación issued beginning February 2026.

Fixes

• Fixed an issue where the NFC Personal Number crosscheck was consistently failing for Chilean IDs, causing an incorrect deduction to the ID Validation score. The fix addresses two encoding patterns specific to Chilean IDs:

  • Non-EXTRANJERO IDs: The NFC chip encodes the Personal Number with a three-character MRZ prefix not present in the OCR value. The crosscheck now strips this prefix before comparison.
  • EXTRANJERO IDs: When the NFC chip stores only a three-character stub, the crosscheck now returns Irrelevant rather than a failure, since a full comparison cannot be made.
    In both cases, formatting characters (. and -) are stripped from the OCR value prior to comparison to prevent false mismatches.

• Resolved an issue where OCR fields containing special characters caused an exception during the redaction process. The redaction logic now handles and processes special characters in OCR fields correctly.

• Fixed an issue where deleting a Microsoft Entra directory integration returned a 500 Internal Server Error. The directory now deletes successfully without errors.

• Fixed an issue where submitting a verification ID retrieved from a webhook to GET omni/incode-id/verification/<verificationId> returned an "Invalid mongo ID format" error. The endpoint now returns the expected verification data.

• Fixed an issue where Okta directory sync could become blocked when a sync process that obtained a lock failed to release it, preventing subsequent sync attempts until the lock expired or the service restarted.

• Fixed an issue where ML fraud checks (paper, screen, and ID alternation) produced inconsistent results depending on whether redaction or Age Assurance was enabled in the flow. These checks now behave consistently regardless of other features enabled in the flow configuration.

• Fixed a response format mismatch in the Mexico KYB Lite API. The name and tin fields now return Verified or Unverified instead of true or false, the registrationStatus field now returns title-case values (Active, Inactive, Unknown) instead of all-caps, and the entityType field response structure has been updated to be consistent with other KYB country responses.

• Update Resolved an issue where logout requests were failing with a 403 error on Demo and SaaS environments due to incorrect CORS filtering behavior. The connect/logout endpoint is now correctly allowlisted, and logout functions as expected across all environments.

• Update Fixed an issue where the /omni/fetch-identities endpoint returned a 400 error instead of the expected identity list. The endpoint now returns results successfully.

• Update Fixed an issue where the logo in Incode Verify and Workforce welcome emails was not loading due to an access error. Logos now display correctly in all outbound verification emails.

ID Support Requests:

• Fixed an issue where the "Full name (OCR)" field for the Honduras Identification Card was extracted with the extraneous label "FORENAME" included in the value.
• Fixed an issue where the "Full name (OCR)" field for the Great Britain Passport was extracted incorrectly.
• Fixed an issue where the "Full name (OCR)" field for the Rwanda Identification Card was returned in last name, first name order. The field now returns names in first name, last name order to match standard extraction conventions.

ML

• Deployed an updated cropping model with several improvements across document types:
  • Better alignment for pre-cropped images
  • Improvements for passports, foldable documents, and IDs in general
  • A slight improvement in barcode detection for US and Canadian documents
• Updated the face occlusion detection model to version 0.2 for web-based onboarding sessions, improving detection of partially obscured faces during identity verification.
• Update Improved MRZ parsing accuracy for Russian passports. The givenNameMrz and lastNameMrz fields now return only valid Latin alphabet characters, excluding numeric characters that were previously being included incorrectly.

Deepsight:

Deepsight requires additional licensing. Contact your Incode representative for more information.

• The Deepsight liveness service now returns an explanation object in API responses when an attack is detected. The object includes a human-readable description of the rejection reason and a keywords block containing the attack category (e.g., paper, replay, 2D mask, 3D mask, face swap, synthetic face, face animation), as well as indicators for flat depth and video corruption. This makes it easier to understand and act on liveness rejection results without additional interpretation.
• Improved the tamper-resistance of Deepsight liveness checks for web onboarding sessions. The backend now validates the Deepsight configuration against the flow settings at processing time, ensuring liveness checks cannot be bypassed through client-side modifications.

ID Templates

New supported templates

NEW CLASSIFICATION SUPPORT

Ethiopia

• Oromia
  • IdentificationCard / IDENTIFICATION_CARD / 2023

Indonesia

• IdentificationCard / IDENTIFICATION_CARD / 2021

Laos

• IdentificationCard / IDENTIFICATION_CARD / 2023

Nicaragua

• IdentificationCard / IDENTIFICATION_CARD / 2026

Peru

• DriversLicense / DRIVERS_LICENSE / 1882

South Sudan

• IdentificationCard / REFUGEE_IDENTIFICATION_CARD / 2023

United States of America

• Louisiana
  • IdentificationCard / IDENTIFICATION_CARD / 2001
• Tribal Indentification
  • TribalIdentification / TRIBAL_IDENTIFICATION_CARD_UNDER21 / 2020
  • TribalIdentification / TRIBAL_IDENTIFICATION_CARD_UNDER21 / 2024
  • TribalIdentification / TRIBAL_IDENTIFICATION_CARD / 1843

NEW ID SUPPORT

Liberia

• VoterIdentification / VOTER_IDENTIFICATION_CARD / 2020

Sudan

• DriversLicense / DRIVERS_LICENSE / 2022

Somalia

• Somaliland
  • VoterIdentification / VOTER_IDENTIFICATION_CARD / 2021

United States of America

• Montana
  • IdentificationCard / IDENTIFICATION_CARD_UNDER21 / 2025
• Wyoming
  • DriversLicense / DRIVERS_LICENSE / 2024
• Tribal Identification
  • TribalIdentification / TRIBAL_IDENTIFICATION_CARD / 1968

Changes to current templates

ID OCR EXTRACTION IMPROVEMENT

France

• Passport / NATIONAL_PASSPORT / 2008 r3 - Incode MRZ

Honduras

• IdentificationCard / IDENTIFICATION_CARD / 2020 r3

Hungary

• IdentificationCard / IDENTIFICATION_CARD_FOR_FOREIGNERS / 2016 r1
• IdentificationCard / IDENTIFICATION_CARD / 2012 r1
• IdentificationCard / IDENTIFICATION_CARD / 2016 r2
• IdentificationCard / IDENTIFICATION_CARD / 2022 r1

Mexico

• CDMX
  • DriversLicense / DIGITAL_DRIVER_LICENSE_APP / 2023 r1

Rwanda

• IdentificationCard / IDENTIFICATION_CARD / 2019 r1

United States of America

• Montana
  • DriversLicense / DRIVERS_LICENSE / 2025 r1

SENSITIVE PII REDACTION

United States of America

• Montana
  • IdentificationCard / IDENTIFICATION_CARD_UNDER21 / 2025 r1 - Age assurance

Demo: 16 March 2026 | Production: 23 March 2026

Release Highlights

Simplified Document Chooser

The Document Chooser in V2 has been updated to ensure a more consistent user experience and simpler customization.

• The screen shown during Onboarding always uses a compact card layout regardless of flow or document type. This removes variability and makes UI customization more predictable.
• The Show document chooser screen setting in the ID Capture module is the only control for when the screen is shown. Previously, the Document Chooser could be skipped regardless of this setting when flows were configured to expect only “ID” types.

The Document Chooser screen is shown in Onboarding by default. To intentionally skip this screen, navigate into your Flows or Workflows and disable the Show document chooser screen setting in the ID Capture module.

Dashboard

Enhancements

Escalations:

The Escalation Management System is not available by default. Contact your Incode Representative if you would to enable this feature for your organization.

• When creating an Escalation, the value selected in the Escalation Reason drop-down dynamically changes the options available in the Issue drop-down. Additionally, the Comment field is now required for most Escalation Reasons. These improvements provide a simpler experience while creating the escalation and more clarity in the escalation once it is submitted.
• There are two new options in the Escalation Reason drop-down when creating an escalation: Classification and ID Validation Crosscheck. These options populate several new options in the Issue drop-down as well:
  • Classification Issue possibilities: Unknown Classification, Incorrect Classification
  • ID Validation Crosscheck Issue possibilities: Document number crosscheck, Personal number crosscheck, Reference number crosscheck, Sex crosscheck, Full name crosscheck, Birth date crosscheck, Expiration date crosscheck
• When an escalation is first submitted, it now has the status of “Opened”. Previously, all escalations started as “In Progress”, which could be a misrepresentation of its actual status.

Workflows and Flows:

• Added tooltips to Deepsight settings in Workflows, Flows, and individual module configuration. This provides more context about the settings while you are viewing them, giving you more confidence in your configuration. Deepsight requires additional licensing. Contact your Incode Representative for more information.
• You can now configure Workflow conditions related to Claim matching result and Claims matching error type.
  • A Claim matching result condition can be configured with Pass or Fail.
  • A Claim matching error type condition can be configured with Claims not found for identity or Claims match failed.
• You can now configure Workflow conditions related to Id expiration offset days. This allows you to build on the Expiration tolerance setting from ID Validation to granularly decide how to handle expired IDs based on how close to the expiration date it is.
• When building a Workflow, Watchlist Business is now listed with the Modules rather than the Processes. When Watchlist Business is added without eKYB, the configuration options for Business Name and Business Country default to Input. In Onboarding, these fields accept user input rather than using the eKYB data. This update was made for Flows in the previous release.

Modules:

• Simplified the eKYC module configuration to hide redundant settings when Country is set to Global.

Helpdesk and Candidate Verification:

• Improved session search within Helpdesk and Candidate integrations so you can find all sessions associated with a given integration reference more reliably. This includes configurable fallback behavior based on your disableVerification setting.
• Enhanced the filters on the Candidate and Helpdesk Verification sessions lists. You can filter by Name, User Identifier, Last Update, Score, and Session Status.
• Update Switched the endpoints that are called from the Helpdesk and Candidate Verification pages:
  • GET v1/dashboard/validate-phone switched to POST /omni/applicant/validate-phone
  • POST /v1/workforce/employee/directory switched to POST /omni/employees/directory
  • POST /v1/workforce/candidate/directory switched to POST /omni/candidates/directory

Fixes

• Fixed an issue that was causing Sessions from other organizations to show in the Directory Information page.
• Fixed an issue where the image from Face Authentication was not cropped in the single session view when the session was run on desktop.
• Fixed an issue with Candidate Verification and Helpdesk Verification that was causing sessions to not be shown.
• Update Fixed an issue that caused the Onboarding app to initiate a redirect when OAuth2 Secured was enabled. Now, in this scenario, the Auth server handles all redirects as expected.

Web App (Onboarding)

Enhancements

• The taxID validation in US KYB now accepts more formats.
• Update Updated the Brazilian Portuguese translation on the Document Selector screen to more accurately represent the intended meaning.
• Update Added Netherlands as an option in the Country drop-down in KYB.

Fixes

• Fixed an issue with Car Invoice processing in the Document Capture module that caused the tutorial to not be shown and the request to capture a second page to be skipped.
• Phone numbers are now displayed correctly in the user profile and wallet, ensuring accurate area codes and full phone numbers are shown regardless of the user's location.

Server

Enhancements

• Updated the logic for the illiteracy check to correctly send users down the verification process that is most functional for them.
• The Advanced Phone Number Risk check now removes the 1 after the country code in a Mexican phone number (+52 1) prior to sending the KYXStart request. This ensures compatibility with updated formats. The system will continue to store and display the number with a 1.
• Introduced a new field on the template level to indicate whether the template has an NFC chip. This field has been applied to all relevant configurations and templates.
• Added an optional configuration to use DigiLocker with the ID Capture module. If enabled for your organization, there is a new setting in the module configuration called Enable Digi Locker. On the backend, a digiLocker property has been added to the GET omni/flow/<ID> API. Both are off/false by default. Contact your Incode representative if you are interested in this feature.
• The rate limit for /add/watchlist/single-record has been updated to reject requests with a 429 error if the rate limit is reached.
• There is a new optional configuration for Phone check shadow mode. When enabled, the 30-second cooldown for sending OTP is ignored. Contact your Incode representative if you are interested in this feature.
• Updated the logic behind the experience of capture attempts with an expired ID. Expiration information can be returned on add/front, add/back, add/barcode, process ID. At the first detection that the ID is expired, the user is presented with this information and redirected to try with a different ID. This prevents situations where the user runs out of capture attempts with an expired ID.
• Business customers integrating backend-to-backend with Omni onboarding can now retrieve session-related data using their server token (client credentials flow) when calling the omni/b2b/onboarding/request-new API. This enables secure access to required session data endpoints by ID for B2B integrations, reducing integration friction.
• Updated the NotificationService to support FIPS-compliant cryptography providers, improving security compliance for environments that require FIPS.
• Added new fields to Proof of Address processing for Mexican Tax Status documents, so legalName and streetType are now included in additionalDocumentAttempts for downstream use.
• Improved name matching for Brazil eKYC to better handle common Brazilian naming patterns. When the Tax ID match is exact, the system can now return “Approximate Match” in more cases (for example, abbreviated last names or partial names), which helps reduce false mismatches and improve conversion.
• Improved the Authentication flow so that returning users are recognized more reliably (including when disableVerifications=true), reducing cases where an existing user is treated as new.
• Added support for Ghana Card facial verification via Shrinq for eKYC.
• Update Added support for PAR authorization flow in Onboarding. This is implemented using a hidden parameter in the /omni/start endpoint.
• Update Names returned by RENAPER now go through the same special-character normalization as OCR-extracted names before matching, reducing false mismatches for identities with accented or otherwise non-ASCII characters.

Fixes

• Fixed an issue with /omni/workforce/workflows that caused the response to be an empty array instead of returning all workflows.
• Fixed an issue where Onboarding verification links created via request-new could expire too quickly when QR phishing protection was enabled. The link TTL is now aligned with the standard onboarding URL TTL for a more reliable start-to-finish verification experience.
• Update Fixed an issue that caused a failed claim matching to still result in a session pass. Now, when claim matching fails, the session is put into manual review as expected.
• Update Fixed an issue that caused a successful OAuth2 verification to throw an error rather than perform the configured redirect.

ML

Improvements for Mexican Constancia de Situación Fiscal documents:

• Fixed an issue with OCR extraction of the RFC (tax ID) on Mexican Constancia de Situación Fiscal documents. Previously, this field could be extracted incorrectly if OCR misread a character. This fix results in fewer false errors / rejections and more reliable data capture of the RFC field, reducing the need for manual review or customer resubmission.
• Added a new field, "Tipo de Vialidad", for OCR extraction from Mexican Constancia de Situación Fiscal.
• Added a new extracted field for “Denominación/Razón Social” (Legal Name) on Mexican Constancia de Situación Fiscal documents, so the full legal name is available in the structured output payload.

General:

• Added support for extracting fingerprint and printed signature images from Chile identity cards (2013 and 2024), and returning the new fingerprintImageID via the /omni/get/images and /omni/get/images/v2 endpoints for easier retrieval.
• Implemented server-side readability estimation in the ID Capture service to better detect low-quality document images and improve capture reliability.
• Update Added a video quality validation check for Selfie Video that reduces cases for video sessions falling back to single-frame checks. This change improves overall selfie capture stability by significantly reducing video discards and fallback behavior.

ID Templates

New supported templates

NEW CLASSIFICATION SUPPORT

Colombia

• Passport / NATIONAL_PASSPORT/ 2026

Dominican Republic

• Military / MILITARY_CARD / 2026

Federated States of Micronesia

• DriversLicense / DRIVERS_LICENSE / 2025

Guyana

• IdentificationCard / IDENTIFICATION_CARD / 2006

Jamaica

• VoterIdentification / VOTER_IDENTIFICATION_CARD / 2015

Kyrgyzstan

• IdentificationCard / IDENTIFICATION_CARD / 2025

Moldova

• DriversLicense / DRIVERS_LICENSE / 2023

Nigeria

• TaxIdentification / TAX_IDENTIFICATION / 2015

New Zealand

• DriversLicense / DRIVERS_LICENSE / 2025

United States of America

• TribalIdentification / TRIBAL_IDENTIFICATION_CARD / 1844

NEW ID SUPPORT

Angola

• TravelDocument / CONSULAR_CARD / 2022

Australia

• Capital Territory
  • IdentificationCard / AGE_CARD / 2014

Spain

• ResidenceDocument / ASYLUM_SEEKER_CARD / 2021

Estonia

• IdentificationCard / IDENTIFICATION_CARD / 2025

France

• Permit / PRIVATE_HIRE_DRIVERS_LICENSE / 2024

Grenada

• MedicalCard / SOCIAL_SECURITY_CARD / 2025

Liechtenstein

• Passport / NATIONAL_PASSPORT / 2026

Mexico

• Estado de Mexico
  • DriversLicense / DRIVERS_LICENSE / 2006
• Guerrero
  • DriversLicense / DRIVERS_LICENSE / 1955
• Quintana Roo
  • DriversLicense / DRIVERS_LICENSE / 1998

Netherlands

• Permit / PRIVATE_HIRE_DRIVERS_LICENSE / 2021

Pakistan

• IdentificationCard / IDENTIFICATION_CARD / 2025

Philippines

• MedicalCard / MEDICAL_CARD / 2008

El Salvador

• IdentificationCard / IDENTIFICATION_CARD / 2018

United Nations

• IdentificationCard / REFUGEE_IDENTIFICATION_CARD / 2019

United States of America

• California
  • Other / IDENTIFICATION_CARD / 2024
• New Jersey
  • Other / IDENTIFICATION_CARD / 2020
  • Other / IDENTIFICATION_CARD / 2021
• Tribal Identification
  • TribalIdentification / TRIBAL_IDENTIFICATION_CARD / 1901
  • TribalIdentification / TRIBAL_IDENTIFICATION_CARD / 1906
• West Virginia
  • Other / FIREARMS_LICENSE / 2020

Changes to current templates

FEATURE UPDATE

Chile

• IdentificationCard / IDENTIFICATION_CARD / 2013 r8 - Fingerprint
• IdentificationCard / IDENTIFICATION_CARD / 2024 r8 - Fingerprint

Hong Kong

• DriversLicense / DRIVERS_LICENSE / 2000 r2

Mexico

• Other / DIGITAL_CURP_CERTIFICATE_FOR_FOREGINERS_PDF / 2026 r1

ID CLASSIFICATION IMPROVEMENT

India

• Delhi
  • DriversLicense / DRIVERS_LICENSE / 2009 r1

Russia

• Passport / NATIONAL_PASSPORT / 2008 r4 - Enrolling back side

ID OCR EXTRACTION IMPROVEMENT

Argentina

• IdentificationCard / IDENTIFICATION_CARD / 2023 r3

Bolivia

• IdentificationCard / IDENTIFICATION_CARD / 2001 r5
• IdentificationCard / IDENTIFICATION_CARD / 2002 r5
• IdentificationCard / IDENTIFICATION_CARD / 2020 r6
• IdentificationCard / IDENTIFICATION_CARD / 2023 r5

Canada

• Ontario
  • MedicalCard / MEDICAL_CARD / 2020 r6

India

• Delhi
  • DriversLicense / DRIVERS_LICENSE / 2009 r1
• Telangana
  • DriversLicense / DRIVERS_LICENSE / 2014 r2

Russia

• Passport / NATIONAL_PASSPORT / 2008 r4 - Enrolling back side

El Salvador

• IdentificationCard / IDENTIFICATION_CARD / 2022 r7

SENSITIVE PII REDACTION

Germany

• ResidenceDocument / RESIDENCE_PERMIT / 2011 r3 - Redact
• ResidenceDocument / RESIDENCE_PERMIT / 2019 r2 - Redact

Demo: 2 March 2026 | Production: 9 March 2026

Release Highlights

Damaged ID Check

There is a new check when validating an ID that looks for physical damage to the document as part of the verification. Physical damage can include severe creases or fading, cuts, and tears.

This check is enabled by default in the ID Validation module in Workflows and Flows using the Damaged ID check setting.

The outcome of this check is displayed in the ID Quality Tests section of the single session view. The outcome of the check does not directly impact the overall score, but damage may prevent proper OCR or security feature validation. To reject or review sessions that fail the Damaged ID check, set up a rule via Verification Rules.

Dashboard

Enhancements

• The Escalations table has been reordered to display the most relevant information first. You can also now reorder the columns yourself to customize your view. Any changes you make are saved for your user and persist after a log out.
• Updated three-dot menus throughout Dashboard to align with the updated look and feel of other menus.
• Multiple accessibility improvements, including adding the proper heading role to headings and improving the contrast of colors on notification banners.
• Improved filtering capability for Identities and Authentications pages, making it easier to locate specific entries.
• In Configuration settings, added four new webhook events: session started, session failed, session succeeded, and session pending review. The payloads from these webhooks provide data about Sessions. They work for both Onboarding and Authentications Sessions.

Flows and Workflows:

• There is a new setting under Deepsight in Flow and Workflow settings to include trust checks in scoring. Trust checks include device trust, behavioral trust, and camera trust. When Deepsight is enabled for the Flow or Workflow, this setting is automatically enabled as well but can be turned off. This allows you more granularity and control of how Deepsight functions in the Flow or Workflow.

Modules:

• When building a Flow, Watchlist Business is no longer nested under the eKYB module and can now be used and configured separately. When Watchlist Business is added without eKYB, the configuration options for Business Name and Business Country default to Input. In Onboarding, these fields accept user input rather than using the eKYB data.
  This update will be made to Workflows in a future release.
• When the eKYC module is configured with the Enable Email Risk setting or if the Source is set to Email Risk 1, the Email field is required during the Onboarding journey. Otherwise, the field is optional.
• eKYC modules with the UK as the country have a new source option: UK Voter Register. This source focuses on address verification based on the user’s voter registration information.
• Updated the eKYC module configuration in Workflows and Flows so all fields are available and presented consistently. This aligns the experience and functionality across Workflows and Flows.
• Improved the experience for configuring eKYC modules in Flows and Workflows by moving Countries into a drop-down separate from Sources. With growing country and source support, this improved experience allows you to see countries and sources that can be configured together with more clarity.
• The eKYC module now supports auto-fill using data extracted from the ID. You can enable this in any or all of the eKYC module configuration field drop-downs by selecting Auto-fill from ID (OCR). This option enhances the user experience by allowing them to not have to manually re-enter data they already submitted via their ID.
• In the Face Capture module, you can now set Image Quality Severity to Ultra High. This highest level ensures image processing can produce the most accurate results because it requires exceptional image quality.
• The User Consent module has been deprecated. Depending on your configuration, it may no longer be visible in the modules list. Any existing uses of User Consent are marked with a deprecated tag to prevent further use. You should use the Data Sharing Consent module in any future Flows or Workflows, as well as to replace existing instances of User Consent.

Fixes

• Fixed an issue in the Workflow builder that did not allow nodes to be reconnected after a condition was deleted.
• Fixed an issue for accessibility where the focusable order of items inside the Workflow structure did not match the functional order.
• Fixed an issue that caused the Image Quality check to not display in the single session view when it was enabled. Now, the check is displayed on the Face Recognition tab.
• Fixed an issue that caused Video Selfie recordings of Front ID, Back ID, or Selfie to freeze or display a black screen at the end of the recordings when Deepsight is enabled on the Flow or Workflow.

Web App (Onboarding)

Enhancements

• For eKYC and eKYB modules with the UK as the country, the State field has been removed from the address collection screen in Onboarding, as the UK does not have states.
• For eKYB modules with Mexico as the country, the only available fields in Onboarding are Business Name, Postal Code, and Tax ID. All other fields have been removed from this screen for cross-platform consistency.

Accessibility:

• The entire Face Capture experience is usable and compatible with screen readers and keyboard navigation.
• Improved accessibility for ID Capture UXv2 in Web implementations.

Fixes

• Fixed an issue in OAuth2 Secured Onboarding Flows/Workflows where users could get stuck on the authorization page even after onboarding completed, and the resulting Session could show an UNKNOWN score. This fix ensures the authorization service polls /authorization/status until a final state before proceeding to verify authentication and redirect back with the result.
• Removed a confusing and incorrect error statement that appeared after a failed Passport scan.
• Fixed an issue where the Manual upload ID capture setting in the ID Capture module in a Workflow did not trigger the on-screen upload option for the Onboarding user.

Server

Enhancements

• Added a mitigation for observed fraudulent behavior using Mexico INE documents.
• Selfie verification is now available in Government Validation for Brazil and South Africa.
• Added a additionalAttrs field to the OCR response for Colombian Cédula de Extranjería to distinguish the following subtypes: RESIDENTE, MIGRANTE, TEMPORAL, and VISITANTE.
• occlusionSeverity is now returned in Flow and Workflow FETCH endpoints along with isOcclusionEnabled.
• isQualityCheckEnabled and qualityChecksSeverity are returned in Flow and Workflow FETCH endpoints based on the configuration of the Image Quality check in the module.
• Added optional configuration to set a reverification period. This period would define how long an Authentication is valid before requiring a new Onboarding session. Contact your Incode representative if you are interested in this configuration.
• Added optional configuration to not store PII data on unsuccessful 1:N Authentications. Contact your Incode representative if you are interested in this configuration.
• One-time password (OTP) cooldown time is now set to 30 seconds. This means the user must wait a minimum of 30 seconds before requesting a new OTP Authentication code.
• Updated SMS notification service to use the region code instead of the country code for rate limiting. This helps to better identify SMS messages from countries that use the same country code.
• Optionally, the Web SDK response can now include a new boolean field, id_quality_attempt_approved. This field gets its value from a backend readability score. When enabled, this value can be used to adjust how the SDK evaluates ID image quality. The readability score is only relevant for Mexican documents; for any other documents, the field is not returned.
• Implemented logic that prevents the first and last names extracted from the ID capture from being overwritten by custom fields.
• Added support for the IdentityAfrica provider for Kenya eKYB checks. This expands coverage for customers running Kenya business verification.
• Document multimodal interaction (MMI) is now included in the overall MMI score. This allows Deepsight to more accurately reflect both face and document integrity. If the document MMI is unknown, it is excluded from scoring. Deepsight requires additional licensing. Contact your Incode representative for more information.
• Update There is a new endpoint that returns only the date of birth from the OCR extraction. This is intended for use cases where the returned data needs to be explicitly limited. Other scoped data will be supported in the future. This feature is configuration-dependent. Contact your Incode representative for more information.

Workforce:

• Added support for OAuth 2.0 Client Credentials B2B integrations to enable the use of Omni Onboarding Flows.
• Transferred Workforce verification functionality to Omni.
• Transferred Workforce integration ID to the omni/start endpoint to enable claim matching and eventually determine webhook configuration.

Fixes

• Fixed an issue where the expiration threshold was not applied to secondary ID scans.
• Aligned the user experience between Flows and Workflows when using Deepsight.
• Fixed login issues for users with the Helpdesk or Recruiter role.
• Fixed an issue with bearer tokens being used after OAuth2 Secured verification.
• Update Fixed an issue with password reset when a user’s email was changed in the system.

ML

Improvements for region-based OCR:

• Improved OCR consistency for cases using region-based templates. This improvement provides more consistent and reliable extracted fields, reducing mismatches avoiding unexpected OCR differences across environments or processing paths.
• Region-template-based OCR can now return image-based outputs for supported document templates.

Update Introduced multiple improvements to models, including:

• Invalidated ID check: Now also rejects documents with a cut corner
• ID Alteration check: Accuracy improvement
• Fake ID check: New security features
• Deepsight for documents: Accuracy improvement
• Barcode: Fix for false rejections

ID Templates

New Document Support

New Classification:

Argentina

• DriversLicense / DRIVERS_LICENSE / 1959

New ID support:

Argentina

• DriversLicense / DRIVERS_LICENSE / 2022
• DriversLicense / DRIVERS_LICENSE / 2023
• Passport / NATIONAL_PASSPORT / 2026

Antigua and Barbuda

• MedicalCard / MEDICAL_BENEFITS_CARD / 2021

Burkina Faso

• TravelDocument / CONSULAR_CARD / 2022

Belize

• DriversLicense / DRIVERS_LICENSE / 2023

Colombia

• IdentificationCard / DIPLOMATIC_IDENTIFICATION_CARD / 2023

Ghana

• IdentificationCard / IDENTIFICATION_CARD / 2024

Guinea

• DriversLicense / DRIVERS_LICENSE / 2023

Mexico

• Military / MILITARY_CARD / 2023
• Guerrero:
  • DriversLicense / DRIVERS_LICENSE / 1954
• Sonora:
  • DriversLicense / DRIVERS_LICENSE / 2017

Nigeria

• IdentificationCard / IDENTIFICATION_CARD / 2012

Peru

• DriversLicense / DRIVERS_LICENSE / 2022

Sweden

• IdentificationCard / IDENTIFICATION_CARD / 2000

United States of America

• Montana:
  • DriversLicense / DRIVERS_LICENSE_UNDER21 / 2025
  • IdentificationCard / IDENTIFICATION_CARD / 2025
• North Carolina:
  • VoterIdentification / VOTER_IDENTIFICATION_CARD / 2023

Changes to Existing Templates

Feature update:

Colombia

• ResidenceDocument / IMMIGRATION_CARD / 2014 r5

• ResidenceDocument / IMMIGRATION_CARD / 2015 r2

ID Classification improvement:

Brazil

• FederalID / IDENTIFICATION_CARD / 2019 r8

ID OCR extraction improvement:

India

• Andhra Pradesh:
  • DriversLicense / DRIVERS_LICENSE / 2010 r1

Mexico

• Guerrero:
  • DriversLicense / DRIVERS_LICENSE / 19985 r1

Panama

• Passport / NATIONAL_PASSPORT / 2019 r2

United States of America

• Montana:
  • DriversLicense / DRIVERS_LICENSE_UNDER21 / 2025 r1 - Age Assurance

Sensitive PII redaction:

Germany

• IdentificationCard / IDENTIFICATION_CARD / 2021 r4 - Redact
• Passport / NATIONAL_PASSPORT / 2017 r5

China

• Hong Kong:
  • ResidenceDocument / PERMANENT_RESIDENT_IDENTITY / 2018 r3 - Redact

United States of America

• Montana:
  • DriversLicense / DRIVERS_LICENSE_UNDER21 / 2025 r1 - Age Assurance
  • IdentificationCard / IDENTIFICATION_CARD / 2025 r1 - Age Assurance

Demo: 12 February 2026 | Production: 23 February 2026

Dashboard

Enhancements

• Multiple accessibility enhancements, including improvements to the order of focusable items, drag-and-drop features, button and modal dialog labels, and removed alt text for images that are purely decorative but don’t enhance understanding.
• You can now export user information from Dashboard. Clicking Export to CSV on the Users page downloads a .csv file containing each user’s name, phone, type (role), email, and permissions (if available). This behavior also triggers an audit log entry called USERS_REPORT_GENERATED.
• In Dashboard Configuration, the Directory Settings tab has been renamed to Claims Settings.

Flows and Workflows:

• The legacy Workflows UI has been deprecated and removed from Dashboard. The new and improved UI is now the only option. Refer to the Workflows documentation if you need help navigating the new experience.

Modules:

• There is a new Advanced Phone Number Risk check that delivers enhanced risk signals for phone number-based verification.
  This check includes all capabilities of the existing Phone Number Risk module: global phone number support, active line validation, fraud activity signals, and a risk score based on observed activity. In addition, Advanced Phone Number Risk includes checks for recent porting activity, previous and current carrier information, timestamps for when the number was identified in data breaches and first seen in our data partner network, associated social media platforms, and an overall confidence score that reflects the trustworthiness of the phone number.
  When this check is run in a session, the single session view includes a section for Advanced Phone Number Risk to display results.
  This is currently configurable using the eKYC module in Flows, with Workflows planned for a later release.
• There is a new setting for Deepsight called Ignore missing metadata. When enabled, no metadata is included in the request, and it does not affect scores. This setting is intended for use with the API integration, not with Incode’s capture methods. You can enable this setting in the Face Capture, Face Authentication, and ID Capture modules. Deepsight requires additional licensing. Contact your Incode representative for more information.
• Aligned the design of configuration for the Forms and Data Entry module between Flows and Workflows to provide a consistent experience.

Workforce only:

• There is a new page in Dashboard called Directory Information. This page allows you to see all directories that are set up displayed in a table. You can click into each listed directory to view the directory profile.

Fixes

• Fixed an issue with Identities permissions that allowed users without the correct permissions to see the Identities tab.

Flows and Workflows:

• The Redirect Desktop attempts to Mobile setting is enabled by default when creating a new Flow or Workflow.
• Previously, saving a Workflow with the OAuth2 Secured (web only) setting enabled would reset the toggle to the off position. Now, this setting is preserved when enabled.
• The Allowed devices setting in Workflows is intentionally enabled without the ability to turn it off. This setting is required for the user to be able to go through the Workflow.
• UI fix: In Workflow settings, the Session timeout expiration unit of time (minutes) was not visible on the screen.
• UI fix: Added a tooltip to the OAuth2 Secured copy icon in Workflows.

Web App (Onboarding)

Enhancements

• Aligned the mandatory/optional status of address fields across configurations for the eKYB module for Brazil.
• When a user attempts ID capture with an unsupported document in UXv2, the error screen now displays a list of supported documents.
• The eKYB module has been migrated to UXv2.
• Update Added validation for a taxId field in the onboarding flow for US KYB Advanced and US KYB Advanced+. The submitted taxId must be 9 digits. Any other format triggers an on-screen error.

Fixes

• Fixed an issue where biometric consent was shown in the wrong order during Onboarding.
• Fixed an issue that caused verification to fail immediately after QR scan when Phishing resistance was enabled in the Workflow settings. This setting is now working as expected.
• Refined error handling for the Face Authentication module to be more specific.
• Fixed an issue with the ID capture UI on desktop.
• Aligned the mandatory/optional status of address fields across configurations for the eKYC module for USA.
• Update Fixed an issue that caused Video Selfie to get stuck on the processing screen if the face in the video didn’t match the face in previous onboarding steps. Now, the Video Selfie face capture can be tried again up to 3 attempts.
• Update Improved error handling for email OTP.
• Update Fixed an issue that caused the accepted document list for Serbia to display nothing.

Server

Highlights

SMS Attack Mitigation:

We have introduced a comprehensive set of security enhancements to strengthen protection against SMS-based attacks while maintaining reliable message delivery for legitimate users.

These improvements include:

• Pre-send phone number risk validation: Phone numbers are validated for risk before sending SMS or OTP messages, and rate limiting with configurable cooldown periods prevents automated attacks. These enhancements protect against abuse while maintaining reliable message delivery, ensuring a safer, more secure verification experience for legitimate users.
• Consistent rate limiting across all SMS-sending endpoints: Enhanced security across all SMS-sending endpoints by implementing consistent rate limiting and validation, helping protect against automated SMS-based attacks while ensuring reliable message delivery for legitimate use cases.
• Configurable cooldown periods between OTP requests: This feature introduces configurable delays between OTP requests to the same phone number, helping protect against SMS-based attacks while maintaining a smooth user experience.
• SMS-based desktop-to-mobile redirects disabled by default for new organizations: This enhances security for new organizations by disabling SMS-based desktop-to-mobile redirects by default to reduce exposure to SMS-related attacks. Controlled opt-in is available.

Together, these enhancements significantly reduce exposure to SMS abuse and automated attacks, while preserving a smooth and secure verification experience.

Enhancements

• Improved the visibility of watermarking on document images.
• Updated QR code parsers for Panama and Chile to better handle special characters in documentNumber response data.
• Improved barcode parsing for addresses from British Columbia documents. Now, the full address is returned from the front of the ID, while structured fields are parsed from the barcode and returned as separate address fields.
• The GET /omni/finish-status endpoint now includes a deprecation notice, signaling a transition to the POST /omni/finish-status method for data modification operations. This prepares integrations for upcoming changes that will enhance security and align with REST API best practices.
• Image quality checks now run consistently during both Face Capture and Face Authentication, providing real-time feedback and scoring aligned with other face attribute validations for a more reliable and seamless verification experience.
• Added support for Nigeria as a government validation provider, expanding identity verification options and enabling more comprehensive compliance capabilities for regulated workflows.
• Face Authentication now includes configurable scoring rules based on overall authentication confidence values, giving administrators enhanced control over verification thresholds and enabling more precise security policies tailored to their risk tolerance and use case requirements.
• Update Digital ID PDF upload is now supported for 2026 Mexico CURP Certificate for Foreigners.
• Update Enhanced the Watchlist feature with an optimized template management system that improves performance and scalability. This update enables faster processing of watchlist operations, providing a more responsive experience when managing and verifying users against your organization's watchlists.
• Update Strengthened the security of Onboarding Workflows to ensure that authentication tokens are properly scoped and isolated across tenants. This enhancement protects customer data by preventing unauthorized access to personally identifiable information (PII), giving you greater confidence in the privacy and security of your platform.

Fixes

• Fixed an issue with an invalid/unauthorized key that was causing /omni/incode-id/send-otp and /omni/send/sms-otp to fail to send the SMS with OTP to the user.
• Fixed an issue that caused document expiration tolerance to not be applied.
• Fixed an issue with ID Validation that caused Deepsight to not run with digital IDs. Deepsight requires additional licensing. Contact your Incode representative for more information.
• Fixed an issue that caused ID Verification checks to fail with digital IDs. This fix ensures accurate validation results and improved reliability for identity verification workflows.
• Addressed a vulnerability related to temporary password handling during account creation, ensuring sensitive credentials are better protected throughout the user provisioning process to enhance account security.
• Refined logic for taxID verification in US KYB sessions as well as error handling for when a session returns an unverified taxId.
• Update When a user is blocklisted in a custom watchlist based on multiple identifiers, the system now includes Face as one of the blocklist matching factors. This ensures more accurate custom watchlist scores.
• Update Fixed an issue that caused OCR values that were redacted from the document image to still be displayed in single session view.
• Update Fixed an issue that occurred on certain environments where the password setup email did not properly redirect to the necessary page.

Machine Learning

• Update Deployed several new models for Deepsight. These models introduce the following:
  • Reduced compute time
  • Improved results after applying postprocessing operations on images
  • Increased defense against internally-created synthetic images
  • Improved recall for both Corrupted and Good depth maps
  • Updated API Response that includes outputs from DepthQualityModel
• Update Updated SDK and API models for face processing. These models detect hyperrealistic 3D masks with more accuracy and have minor threshold adjustments.

ID Templates

New Document Support

Philippines

• IdentificationCard / SSS_ID_CARD / 2025

Changes to Existing Templates

The following document was updated for ID Classification improvement:

Sri Lanka

• DriversLicense / DRIVERS_LICENSE / 2011 R1

The following documents were updated for OCR extraction improvements:

Argentina

• IdentificationCard / IDENTIFICATION_CARD / 2023 r2

Brazil

• ResidenceDocument / MIGRATORY_REGISTER / 2012 r3

Panama

• IdentificationCard / IDENTIFICATION_CARD / 2010 r4
• ResidenceDocument / PERMANENT_RESIDENCE_CARD / 2015 r3

Saudi Arabia

• IdentificationCard / IDENTIFICATION_CARD / 2010 r2
• IdentificationCard / IDENTIFICATION_CARD / 2013 r1

United States of America

• Alaska
  • Other / IDENTIFICATION_CARD / 2023 r1
• Arizona
  • DriversLicense / LEARNERS_PERMIT / 2023 r1
• Pennsylvania
  • DriversLicense / DRIVERS_LICENSE_UNDER21 / 2017 r2
• Tribal Identification Cards
  • TribalIdentification / TRIBAL_IDENTIFICATION_CARD / 2006 r1

Originally titled2026 February 5

Demo: 29 January 2026 | Production: 9 February 2026

Dashboard

Enhancements

• Accessibility improvements, including accurate alt text for images and labeled modal dialogs.
• Update The Executive with Custom Permissions role now includes a permissions option for Escalations. This permission allows users to view the Escalations tab and its content. The separate Sessions permission is still needed to view any Sessions associated with an Escalation.

Workflow and Flow Configuration and Settings:

• In Flow settings, you can now granularly enable or disable Risk AI Agent for available countries. For Workflows, you can accomplish this by adding a condition to look for the country code on the ID. Currently, Risk AI Agent supports Colombia, Mexico, and the United States. Risk AI Agent requires additional licensing. Contact your Incode representative for more information.
• You can now configure conditions related to Deepsight after the Face Authentication module in a Workflow.

Fixes

• Fixed an issue that caused an error to display when a custom node was added to the canvas in the new Workflow builder.
• Fixed an issue where users who updated their email were unable to log in.
• Update Added and improved tooltips for the Document Capture module in Workflows.

Web App (Onboarding)

Enhancements

• Updated the design of the screen a user sees at the beginning of Onboarding.

Fixes

• Fixed a bug that caused a “Something went wrong” error screen to display even though the operation was successful.
• Fixed an issue where the customization was not working for some text on the Onboarding launch screen.
• Update Aligned the mandatory/optional status of address fields across configurations for the eKYB module for USA.

Server

Enhancements

• Improved matching for business names that contain characters with accents as well as entities such as additional spaces or dots in the eKYB module for Mexico.
• Added the left half as a new region of interest for the following templates:
  • NGA|ALL|TravelDocument|CONSULAR_CARD|2017
  • BGD|ALL|IdentificationCard|IDENTIFICATION_CARD|2006
• Update Historically, the system automatically added a 1 after the country code (+52) for Mexican phone numbers to ensure consistency with phone number formats. Starting with this release, if a Mexican phone number has a 1 after the country code (+52 1), the 1 is removed prior to sending the SMS to ensure compatibility with the SMS provider. The system will continue to store and display the number with a 1. This change affects the add/phone endpoint.
• Update SMS messages sent via API are now limited to 160 characters. Currently-effected endpoints include /omni/add/phone and /omni/organization/{{orgId1}}. Any messages sent with more than 160 characters will fail until the text is shortened.

Fixes

• Refined redaction and watermarking capabilities on Sessions with errors. When a document fails classification or is an unknown document type, the image is fully redacted. When classification is successful but some other error is returned, the image is redacted and watermarked according to the requirements of the document type. You can enable watermarking in the ID Capture module.

Machine Learning

This release introduces overall improvements across identity verification and fraud prevention, including higher accuracy in liveness checks, enhanced detection of fake and altered documents, better recognition of damaged IDs, expanded document coverage for key markets, and more advanced AI-driven risk assessment for improved decision-making.

ID Templates

New Document Support

Argentina

• DriversLicense / DRIVERS_LICENSE / 1960
• DriversLicense / DRIVERS_LICENSE / 1961
• DriversLicense / DRIVERS_LICENSE / 1963
• DriversLicense / DRIVERS_LICENSE / 2005
• DriversLicense / DRIVERS_LICENSE / 2020

India

• Chhattisgarh
  • DriversLicense / DRIVERS_LICENSE / 2023
• Nagaland
  • DriversLicense / DRIVERS_LICENSE / 2018
• IdentificationCard / DIPLOMATIC_IDENTIFICATION_CARD / 2023

Kazakhstan

• DriversLicense / DRIVERS_LICENSE / 2005

Mali

• Passport / NATIONAL_PASSPORT / 2025

Mexico

• Guerrero
  • DriversLicense / DRIVERS_LICENSE / 1985
• Military / MILITARY_CARD / 2018
• Other / DIGITAL_CURP_CERTIFICATE_FOR_FOREIGNERS_PDF / 2026

Nepal

• DriversLicense / DRIVERS_LICENSE / 2007

Peru

• DriversLicense / DRIVERS_LICENSE / 1889
• ResidenceDocument / RESIDENCE_PERMIT / 2000

Portugal

• ResidenceDocument / RESIDENCE_PERMIT / 2024

Seychelles

• DriversLicense / DRIVERS_LICENSE / 2016

Somalia

• IdentificationCard / IDENTIFICATION_CARD / 2016

South Sudan

• DriversLicense / DRIVERS_LICENSE / 2023
• IdentificationCard / IDENTIFICATION_CARD / 2024

Trinidad and Tobago

• Permit / WORK_PERMIT / 2024

United States of America

• TribalIdentification / TRIBAL_IDENTIFICATION_CARD / 1845
• TribalIdentification / TRIBAL_IDENTIFICATION_CARD / 1849
• TribalIdentification / TRIBAL_IDENTIFICATION_CARD / 1851

Vietnam

• DriversLicense / DRIVER_LICENSE / 2025

Changes to Existing Templates

Ecuador

• IdentificationCard / IDENTIFICATION_CARD / 2020 - Specific field improvements: documentNumber

Mexico

• Tlaxcala
  • DriversLicense / DRIVERS_LICENSE / 2022 - Template improved in general

Demo: 19 January 2026 | Production: 26 January 2026

Dashboard

Highlights

Updated Workflow Builder:

The Workflow builder has been updated with a new look and feel. Key changes include:

• Modules, processes, and conditions are always visibly accessible from the canvas
• All modules and processes can be previewed on hover
• Drag-and-drop functionality
• Ability to connect or disconnect nodes to adjust Workflow paths
• Root node flexibility
• Visual and design consistency with other aspects of Dashboard

The new UI is enabled by default. You can temporarily revert to the old UI by clicking Switch to Old UI on the Workflows page. This option will continue to be available for a few weeks to help with the transition to the new experience.

Enhancements

• Multiple accessibility improvements, including accurate alt text on images, labeling and formatting of screen elements, and increased contrast.

Single Session View:

• Submission Method:
  There is a new field called Submission Method in the ID OCR section of the single Session view. Values for this field can be Captured Document, Uploaded File, or Imported Credential.
• Added a column for Document Attributes to the CSV export from the single Session view. This is already in place in the CSV export from the Sessions list.

Workflow and Flow Settings and Module Configuration:

• In Workflow and Flow settings, radio buttons and checkboxes have been replaced with toggles. This aligns the visual and functional experience with other areas of Dashboard.
• Strict Video Checks:
  There is a new configuration option in Face Capture and Face Authentication modules called Strict Video Checks. This setting determines whether the system should perform a crosscheck comparing the face from the video and the selfie. The option is only available when Deepsight Multi-Modal Intelligence is set to Single frame + Depth + Video. Deepsight requires additional licensing. Contact your Incode representative for more information. This setting is available for both Workflows and Flows.
• OAuth2 Secured:
  There is a new setting in Workflows and Flows called OAuth2 Secured. This setting can strengthen the security of the user journey against replay attacks in webflows. When enabled, a redirect URL is required for the Workflow or Flow to save. The OAuth clientid is saved in the configuration settings for future reference.
• Enable SNA verification:
  There is a new configuration option in the Phone Number Input module called Enable SNA verification. This setting uses Silent Network Authentication (SNA) as an alternative to SMS OTP verification. Enabling SNA can improve security, reduce user friction, and lower operational costs associated with SMS delivery. This setting is available for both Workflows and Flows.
• Asynchronous Modules:
  Workflows now support asynchronous modules with improved clarity and control. When you add an async module to a Workflow, the system provides clear guidance and validation to ensure each async path includes the required Async Resolution step. This enables smoother background processing while end users complete their Onboarding journey. See also the Asynchronous Modules entry in Web App enhancements.
• Removed unused and deprecated modules from Flows, including Stadium Selector and Generate QR.

Fixes

• Added missing configuration options for face recognition checks such as mask, lenses, and hat validation to the Video Selfie module in Workflows.
• Updated the tooltip description for the ID Already Used check in single Session view to provide a clearer understanding of what the check looks for.
• Updated error messaging for mutually-exclusive settings in Workflow and Flow configuration.
• Update Fixed an issue with logins for Workforce Dashboard users.

Web App (Onboarding)

Enhancements

• Asynchronous Modules:
  Users can now complete the Onboarding flow without needing to wait for asynchronous module results. The system allows the user to move on to the next step in Onboarding while the previous step renders its result in the background. This reduces time spent on loading screens, increasing user satisfaction and Onboarding completion rates. See also the Asynchronous Modules entry in Dashboard enhancements.
• Added analytics tracking for the Digital ID PDF upload feature. These analytics help monitor user behavior, success rates, and potential issues.
• After the maximum capture attempts are met, a user can continue on to the next step in Onboarding rather than being presented with an error screen.
• Age Assurance is now available with Workflows using UXv2.
• During a selfie capture using the Face Capture module, when face occlusion checks are configured (lenses, mask, closed eyes) and the user is determined to have one of these elements, a specific error is shown directing them to uncover their face. Previously, a generic error was shown.
• End users now see an "All data is encrypted" message during the ID capture process.
• The ID Capture step in Onboarding now includes an updated Common Issues screen to help the user prevent problems like glare and blur in their capture.
• If you have configured a custom field with the "date" type, the web app user is provided a date picker component rather than a text field.
• Update The camera permission flow in Web has been redesigned to match the streamlined experience already available in our iOS and Android applications.

Fixes

• Previously, when a Workflow was configured with the ID Validation and CURP Validation modules, the CURP capture screen would always show during the Onboarding Workflow. Now, the CURP capture screen is only shown when the CURP cannot be obtained from the OCR data. This issue and fix are specific to UXv2.
• Previously, when using an iPad in landscape mode, the ID and Selfie Capture screens would remain white and not load. Now, iPads can load these screens regardless of device orientation.
• Update Fixed an issue where autocapture wasn’t working on iPads after rotating the device from portrait to landscape.

Server

Enhancements

• The system can now create rules using all address components. This allows for validation on the state from the address on the ID as well as the issuing state, which can differ.
• An Identity created with a Columbian document will have a national ID number. This 6-10 digit number can be used as a hint in the Face Authentication module.
• If a Workflow or Flow does not contain the Phone Number Input module, the user cannot use SMS or OTP and the phone number cannot be updated. This enhances SMS security and attack prevention. To allow for SMS or OTP in Onboarding, ensure the Phone Number Input module is added and configured to the relevant Workflows or Flows.
• If QR Onboarding is enabled, any Onboarding-related SMS will not be sent.
• When Age Assurance is enabled in Workflow or Flow settings, you cannot configure the Face Capture module with Enable face recording or the ID Capture module with Enable ID recording. Age Assurance also ensures any Deepsight recordings are deleted when the Session is complete. Deepsight requires additional licensing. Contact your Incode representative for more information.
• Previously, configured face attributes, image quality, and liveness were not present in the result if they were not executed and face matching was marked as failed. Now, when these elements are configured but not executed, they are marked as unknown.
• Enhanced the security and reliability of face login flows by adding support for liveness statistics endpoints in the Crypto service, ensuring seamless end-to-end encryption for biometric authentication processes.
• Dashboard users can now access comprehensive eKYC attempt data, including both Incode-processed responses and raw third-party provider information through newly structured API endpoints.
• Venezuelan ID expiration dates now correctly display the last day of the expiration month instead of the first day, accurately reflecting that documents remain valid throughout the entire month stated on the card.
• A new Risk AI Agent processing node is now available in Workflows, enabling holistic evaluation of all session signals to deliver more accurate and intelligent decision-making. This node is optimized for placement at the end of workflows after ID validation, providing enhanced fraud detection capabilities for U.S.-based onboarding flows.
• Video selfie scoring is now available and accurately evaluated at the time workflow conditions are processed. This enhancement ensures reliable video selfie validation and improves the accuracy of final workflow decisions, leading to more trustworthy identity verification outcomes.
• When a Flow does not include the Face Match module but does have the Face Capture module, the Age Estimation result is available in Face Attributes rather than Face Recognition. This only applies if your system is configured for age estimation.
• The system now allows duplicate email addresses in the same directory during synchronization while maintaining data integrity. When multiple records with identical email addresses exist in a directory, employee search operations will fail during claim matching, preventing ambiguous authentication scenarios and ensuring accurate identity verification. This enhancement is specific to Workforce implementations.
• City matching for Tel Aviv, Israel has been enhanced to deliver more accurate results. Companies registered in Tel Aviv now receive exact city matches even when the official city name includes additional district information, improving overall data quality and match rate performance.
• US KYB Sessions now clearly indicate the verification status of Ultimate Beneficial Owners (UBOs) with visual indicators, making it easier to identify valid ownership information at a glance.

Fixes

• The Government Validation module can use a selfie captured from the Face Authentication module. Previously, it would only use a selfie from the Face Capture module.
• Enhanced Custom Watchlist accuracy by correcting the device fingerprint logic, ensuring more reliable device matching and improved fraud detection across onboarding sessions.
• Removed the unused authentications/generateImageUrl endpoint due to a vulnerability.
• When a Session contains a selfie captured from a Face Authentication module and that Session or associated Identity is added to a custom watchlist, the watchlist record now contains the selfie image.
• Face occlusion check results are now included in the overall score for Face Authentication.
• Fixed an issue with full frame image rotation during ID preprocessing. This reduces potential errors and improves the overall quality of document capture.
• The Government Validation module returns clearer statuses for US states that are not supported by AAMVA.
• Update Fixed an issue so Sessions with Government Validation consistently return complete response data across all ID types. This improves data integrity and enables more accurate tracking and reporting for compliance workflows.
• Update Fixed a bug where some fields were not displaying in analytics.

ID Templates

New supported templates

Argentina

• DriversLicense / DRIVER_LICENSE / 1967
• DriversLicense / DRIVERS_LICENSE / 1968
• DriversLicense / DRIVERS_LICENSE / 1969

American Samoa

• VoterIdentification / VOTER_IDENTIFICATION_CARD / 2023

Australia

• Passport / EMERGENCY_PASSPORT / 2025
• Capital Territory / IdentificationCard / AGE_CARD / 2014 - Only config file created for Data Collection
• New South Wales / Other / FIREARMS_LICENSE / 2020 - Only config file created for Data Collection

Benin

• Passport / NATIONAL_PASSPORT / 2024
• TravelDocument / CONSULAR_CARD / 2022

Belize

• ResidenceDocument / PERMANENT_RESIDENCE_CARD / 2025 - Only config file created for Data Collection

Brazil

• FederalID / DIGITAL_IDENTIFICATION_CARD_PDF / 2024
• FederalID / DIGITAL_IDENTIFICATION_CARD_PDF / 2025
• FederalID / DOMESTIC_IDENTIFICATION_CARD / 1844
• FederalID / DOMESTIC_IDENTIFICATION_CARD / 1845

China

• Passport / DIPLOMATIC_PASSPORT / 2023

Ivory Coast

• IdentificationCard / REFUGEE_IDENTIFICATION_CARD / 2020 - Only config file created for Data Collection

Democratic Republic of the Congo

• DriversLicense / DRIVERS_LICENSE / 2018
• TravelDocument / CONSULAR_IDENTITY_CARD / 2021 - Only config file created for Data Collection
• TravelDocument / CONSULAR_IDENTITY_CARD / 2022

Comoros

• IdentificationCard / IDENTIFICATION_CARD / 2020
• ResidenceDocument / RESIDENCE_CARD / 2020 - Only config file created for Data Collection

Costa Rica

• Passport / NATIONAL_PASSPORT / 2019

Denmark

• DriversLicense / DRIVER_LICENSE / 2025
• Greenland / DriversLicense / DRIVERS_LICENSE / 2024

Dominican Republic

• TravelDocument / CONSULAR_CARD / 2022

East Timor

• Passport / NATIONAL_PASSPORT / 2020 - Only config file created for Data Collection

Egypt

• DriversLicense / INTERNATIONAL_DRIVING_PERMIT / 2021

Estonia

• IdentificationCard / DIPLOMATIC_IDENTIFICATION_CARD / 2022
• IdentificationCard / IDENTIFICATION_CARD / 2025 - Only config file created for Data Collection

Ethiopia

• DriversLicense / DRIVERS_LICENSE / 2023 - Only config file created for Data Collection

Gabon

• Visa / VISA / 2014

Georgia

• ResidenceDocument / TEMPORARY_RESIDENCE_CARD / 2025 - Only config file created for Data Collection

Gibraltar

• DriversLicense / DRIVERS_LICENSE / 2023

Guinea

• VoterIdentification / VOTER_IDENTIFICATION_CARD / 2020 - Only config file created for Data Collection

Gambia

• ResidenceDocument / RESIDENCE_PERMIT / 2015 - Only config file created for Data Collection

Greece

• IdentificationCard / POLICE_IDENTIFICATION_CARD / 2020 - Only config file created for Data Collection
• IdentificationCard / POLICE_IDENTIFICATION_CARD / 2025

Guyana

• DriversLicense / DRIVERS_LICENSE / 2020 - Only config file created for Data Collection

Honduras

• DriversLicense / DRIVERS_LICENSE / 2018 - Only config file created for Data Collection

Indonesia

• DriversLicense / DRIVER_LICENSE / 2024

India

• Arunachal Pradesh / DriversLicense / DRIVERS_LICENSE / 2023
• Nagaland/ DriversLicense / DRIVER_LICENSE / 2020
• Tamil Nadu / DriversLicense / DRIVERS_LICENSE / 2020

Interpol

• Passport / PASSPORT / 2015 - Only config file created for Data Collection

Jordan

• Military / MILITARY_CARD / 2022 - Only config file created for Data Collection

Japan

• ResidenceDocument / SPECIAL_PERMANENT_RESIDENT_CERTIFICATE / 2024
• Visa / VISA / 2024

Kosovo

• IdentificationCard / IDENTIFICATION_CARD / 2008 - Only config file created for Data Collection
• IdentificationCard / IDENTIFICATION_CARD / 2024
• Passport / NATIONAL_PASSPORT / 2020 - Only config file created for Data Collection
• ResidenceDocument / RESIDENCE_PERMIT / 2025

Kuwait

• DriversLicense / DRIVERS_LICENSE / 2015 - Only config file created for Data Collection

Kyrgyzstan

• DriversLicense / DRIVERS_LICENSE / 2020

Laos

• IdentificationCard / IDENTIFICATION_CARD / 2025 - Only config file created for Data Collection

Mexico

• DriversLicense / DIGITAL_FEDERAL_DRIVERS_LICENSE_PDF / 2025
• Campeche / DriversLicense / DRIVERS_LICENSE / 2020 - Only config file created for Data Collection
• CDMX / DriversLicense / DRIVER_LICENSE / 2025
• Guerrero
  • DriversLicense / DRIVERS_LICENSE / 1896
  • DriversLicense / DRIVERS_LICENSE / 1897
  • DriversLicense / DRIVERS_LICENSE / 1899 - Only config file created for Data Collection
  • DriversLicense / DRIVERS_LICENSE / 1911
  • DriversLicense / DRIVERS_LICENSE / 1950
• Quintana Roo / DriversLicense / DRIVERS_LICENSE / 2007
• San Luis Potosi / DriversLicense / DRIVERS_LICENSE / 2025

Mauritius

• IdentificationCard / IDENTIFICATION_CARD / 2025

Malaysia

• DriversLicense / DRIVER_LICENSE / 2025

Nigeria

• IdentificationCard / IDENTIFICATION_CARD / 1995
• IdentificationCard / REFUGEE_IDENTIFICATION_CARD / 2019
• TravelDocument / CONSULAR_CARD / 2017
• TravelDocument / CONSULAR_CARD / 2025

Nepal

• DriversLicense / DRIVERS_LICENSE / 2023

New Zealand

• Cook Islands / DriversLicense / DRIVERS_LICENSE / 2025 - Only config file created for Data Collection
• Niue/ DriversLicense / DRIVERS_LICENSE / 2020 - Only config file created for Data Collection

Pakistan

• Khyber Pakhtunkhwa / DriversLicense / DRIVERS_LICENSE / 2023

Peru

• DriversLicense / DRIVER_LICENSE / 1884
• DriversLicense / DRIVERS_LICENSE / 1885
• DriversLicense / DRIVERS_LICENSE / 2021
• DriversLicense / DRIVERS_LICENSE / 2025 - Only config file created for Data Collection
• Visa / VISA / 2024

Philippines

• IdentificationCard / SSS_ID_CARD / 2025 - Only config file created for Data Collection
• Military / MILITARY_CARD / 2020 - Only config file created for Data Collection
• Military / MILITARY_CARD / 2021 - Only config file created for Data Collection
• Other / GSIS_ECARD_PLUS / 2020

Puerto Rico

• Other / FIREARMS_LICENSE / 2020

Republic of Chad

• Military / MILITARY_CARD / 2020 - Only config file created for Data Collection

Romania

• IdentificationCard / DIPLOMATIC_IDENTIFICATION_CARD / 2025

Saint Kitts and Nevis

• IdentificationCard / IDENTIFICATION_CARD / 2015
• IdentificationCard / IDENTIFICATION_CARD / 2016 - Only config file created for Data Collection

Samoa

• DriversLicense / DRIVERS_LICENSE / 2023

Sierra Leone

• IdentificationCard / IDENTIFICATION_CARD / 2020 - Engineering fix: personal number MRZ parsing

Slovakia

• IdentificationCard / IDENTIFICATION_CARD / 2023

Somalia

• Somaliland / DriversLicense / DRIVERS_LICENSE / 2020 - Only config file created for Data Collection

South Sudan

• DriversLicense / DRIVERS_LICENSE / 2022 - Only config file created for Data Collection

Sudan

• Passport / DIPLOMATIC_PASSPORT / 2020

Sweden

• DriversLicense / DRIVERS_LICENSE / 2025

Thailand

• IdentificationCard / IDENTIFICATION_CARD_FOR_FOREIGNERS / 2025

Togo

• IdentificationCard / IDENTIFICATION_CARD / 2020
• Passport / NATIONAL_PASSPORT / 2015 - Only config file created for Data Collection
• ResidenceDocument / RESIDENCE_PERMIT / 2023 - Only config file created for Data Collection

Turkish Republic of Northern Cyprus

• DriversLicense / DRIVERS_LICENSE / 2015 - Only config file created for Data Collection

Turkmenistan

• Passport / NATIONAL_PASSPORT / 2025

Turks and Caicos Islands

• IdentificationCard / NATIONAL_STATUS_CARD / 2022

Ukraine

• IdentificationCard / DIPLOMATIC_IDENTIFICATION_CARD / 2020 - Only config file created for Data Collection

Uruguay

• DriversLicense / DRIVER_LICENSE / 2019

United Kingdom

• ResidenceDocument / RESIDENCE_PERMIT / 2010 - Only config file created for Data Collection

United States of America

• Other / BIRTH_CERTIFICATE / 2011
• DriversLicense / DRIVERS_LICENSE_UNDER21 / 2025
• **Arizona **
  • Other / BIRTH_CERTIFICATE / 2020 - Only config file created for Data Collection
• Colorado
  • DriversLicense / DRIVERS_LICENSE / 1994 - documentSeriesExpired enabled on template level
  • DriversLicense / DRIVERS_LICENSE_UNDER21 / 1994 - documentSeriesExpired enabled on template level
  • IdentificationCard / IDENTIFICATION_CARD_UNDER21 / 2014 - documentSeriesExpired enabled on template level
  • Other / BIRTH_CERTIFICATE / 2020 - Only config file created for Data Collection
  • Permit / DRIVER_INSTRUCTION_PERMIT_ALLAGES / 1994 - documentSeriesExpired enabled on template level
  • Permit / DRIVER_INSTRUCTION_PERMIT_UNDER18 / 1994 - documentSeriesExpired enabled on template level
  • Permit / DRIVER_INSTRUCTION_PERMIT_UNDER21 / 1994 - documentSeriesExpired enabled on template level
• Connecticut
  • Other / IDENTIFICATION_CARD / 2020
• Delaware
  • Other / BIRTH_CERTIFICATE / 2020
• Guam
  • DriversLicense / DRIVERS_LICENSE / 2011 - documentSeriesExpired enabled on template level
• Iowa
  • Other / BIRTH_CERTIFICATE / 2020 - Only config file created for Data Collection
• Kansas
  • DriversLicense / DRIVERS_LICENSE_UNDER21 / 2004 - documentSeriesExpired enabled on template level
  • DriversLicense / LEARNERS_PERMIT / 2013 - documentSeriesExpired enabled on template level
• Maryland
  • Other / BIRTH_CERTIFICATE / 2020 - Only config file created for Data Collection
• Massachusetts
  • Other / BIRTH_CERTIFICATE / 2020 - Only config file created for Data Collection
• Missouri
  • Other / BIRTH_CERTIFICATE / 2020 - Only config file created for Data Collection
• Montana
  • DriversLicense / DRIVERS_LICENSE / 2025
• New Jersey
  • Other / BIRTH_CERTIFICATE / 2020 - Only config file created for Data Collection
  • Other / IDENTIFICATION_CARD / 2019
• New York
  • Other / BIRTH_CERTIFICATE / 2020 - Only config file created for Data Collection
• North Carolina
  • DriversLicense / DRIVER_LICENSE_UNDER21 / 2004 - documentSeriesExpired enabled on template level
  • DriversLicense / DRIVERS_LICENSE / 2000 - documentSeriesExpired enabled on template level
• North Dakota
  • DriversLicense / LEARNERS_PERMIT / 2006 - documentSeriesExpired enabled on template level
  • DriversLicense / LEARNERS_PERMIT / 2023
• Ohio
  • DriversLicense / DRIVER_LICENSE_UNDER21 / 2009 - documentSeriesExpired enabled on template level
  • Other / BIRTH_CERTIFICATE / 2020 - Only config file created for Data Collection
• Oklahoma
  • IdentificationCard / IDENTIFICATION_CARD / 2023
• Pennsylvania
  • Other / BIRTH_CERTIFICATE / 2020
• South Carolina
  • DriversLicense / DRIVERS_LICENSE / 1994 - documentSeriesExpired enabled on template level
  • DriversLicense / DRIVERS_LICENSE_UNDER21 / 1994 - documentSeriesExpired enabled on template level
• Texas
  • Other / FIREARMS_LICENSE / 2024
• Tribal Identification
  • TRIBAL_IDENTIFICATION_CARD / 1852
  • TRIBAL_IDENTIFICATION_CARD / 1854
  • TRIBAL_IDENTIFICATION_CARD / 1856 - Only config file created for Data Collection
  • TRIBAL_IDENTIFICATION_CARD / 1857
  • TRIBAL_IDENTIFICATION_CARD / 1859 - Only config file created for Data Collection
  • TRIBAL_IDENTIFICATION_CARD / 1860 - Only config file created for Data Collection
  • TRIBAL_IDENTIFICATION_CARD / 1861 - Only config file created for Data Collection
  • TRIBAL_IDENTIFICATION_CARD / 1862 - Only config file created for Data Collection
  • TRIBAL_IDENTIFICATION_CARD / 1863 - Only config file created for Data Collection
  • TRIBAL_IDENTIFICATION_CARD / 1864 - Only config file created for Data Collection
  • TRIBAL_IDENTIFICATION_CARD / 1867
  • TRIBAL_IDENTIFICATION_CARD / 1868
  • TRIBAL_IDENTIFICATION_CARD / 1869
  • TRIBAL_IDENTIFICATION_CARD / 1900
  • TRIBAL_IDENTIFICATION_CARD / 1903
  • TRIBAL_IDENTIFICATION_CARD / 1908
  • TRIBAL_IDENTIFICATION_CARD / 1943
  • TRIBAL_IDENTIFICATION_CARD / 1961
• US Virgin Islands
  • VoterIdentification / VOTER_IDENTIFICATION_CARD / 2015 - Only config file created for Data Collection
• Virginia
  • Other / BIRTH_CERTIFICATE / 2020 - Only config file created for Data Collection
• Washington
  • DriversLicense / DRIVER_LICENSE_UNDER21 / 2007 - documentSeriesExpired enabled on template level
• West Virginia
  • DriversLicense / LEARNERS_PERMIT_UNDER21 / 2023
  • IdentificationCard / IDENTIFICATION_CARD_UNDER21 / 2023
• Wyoming
  • Other / FIREARMS_LICENSE / 2021 - Only config file created for Data Collection

Vietnam

• IdentificationCard / IDENTIFICATION_CARD / 2020

Yemen

• Passport / NATIONAL_PASSPORT / 2017

Zambia

• MedicalCard / MEDICAL_CARD / 2023
• TravelDocument / CONSULAR_CARD / 2024

Changes to current templates

Australia

• New South Wales / DriversLicense / HEAVY_VEHICLE_DRIVERS_LICENSE / 2015 - OCR provider switched to Incode
• Queensland / DriversLicense / HEAVY_VEHICLE_DRIVERS_LICENSE / 2020 - OCR provider switched to Incode
• South Australia / DriversLicense / DRIVERS_LICENSE / 2015 - OCR provider switched to Incode

Bangladesh

• IdentificationCard / IDENTIFICATION_CARD / 2006 - documentSeriesExpired enabled on template level

Bulgaria

• IdentificationCard / IDENTIFICATION_CARD / 2010 - Specific field improvements: nationality, birthPlace, issuingAuthority
• IdentificationCard / IDENTIFICATION_CARD / 2024 - Specific field improvements: nationality, birthPlace, issuingAuthority

Bahrain

• DriversLicense / DRIVERS_LICENSE / 2018 - Gender standardised to one letter values

Bosnia and Herzegovina

• Passport / NATIONAL_PASSPORT / 2015 - MRZ lines extracted by Incode OCR

Brazil

• FederalID / DOMESTIC_IDENTIFICATION_CARD / 2004 - Specific field improvements: name

Canada

• Other / FIREARMS_LICENSE / 2010 - Gender standardised to one letter values
• British Columbia
  • Other / Services Card / 2022 - OCR provider switched to Incode
• Ontario
  • MedicalCard / MEDICAL_CARD / 2020 - Template switched to entity_segmentation approach

Chile

• IdentificationCard / IDENTIFICATION_CARD / 2013 - New field image(s) extracted
• IdentificationCard / IDENTIFICATION_CARD / 2013 - Specific field improvements: PersonalNumber
• IdentificationCard / IDENTIFICATION_CARD / 2024 - New field image(s) extracted

Czech Republic

• IdentificationCard / IDENTIFICATION_CARD / 2012 - Template improved in general
• IdentificationCard / IDENTIFICATION_CARD / 2021 - Specific field improvements: personalNumber
• ResidenceDocument / RESIDENCE_PERMIT / 2013 - Template improved in general
• ResidenceDocument / RESIDENCE_PERMIT / 2020 - Template improved in general

El Salvador

• DriversLicense / DRIVER_LICENSE / 2000 - Gender standardised to one letter values
• Passport / NATIONAL_PASSPORT / 2024 - Template improved in general

Ghana

• TravelDocument / CONSULAR_CARD / 2023 - Gender standardised to one letter values

Hong Kong

• ResidenceDocument / PERMANENT_RESIDENT_IDENTITY / 2018 - Sensitive data redacted

Ireland

• Passport / NATIONAL_PASSPORT / 2006 - Template improved in general. New field added: issuingAuthority
• ResidenceDocument / RESIDENCE_PERMIT / 2020 - Template improved in general

Italy

• DriversLicense / DRIVER_LICENSE / 2013 - OCR provider switched to Incode OCR

Mexico

• **Nayarit **
  • DriversLicense / DRIVERS_LICENSE / 2019 - Gender standardised to one letter values
• **Quintana Roo **
  • DriversLicense / DRIVERS_LICENSE / 2002 - Gender standardised to one letter values

Mongolia

• IdentificationCard / IDENTIFICATION_CARD / 2013 - Gender standardised to one letter values

Mozambique

• DriversLicense / DRIVERS_LICENSE / 2021 - Gender standardised to one letter values

Nigeria

• Passport / NATIONAL_PASSPORT / 2019 - Template switched to entity_segmentation approach. Fallback approach added: regions
• Passport / NATIONAL_PASSPORT / 2020 - Template switched to entity_segmentation approach. Fallback approach added: regions

Netherlands

• Passport / NATIONAL_PASSPORT / 2024 - MRZ lines extracted by Incode OCR

Panama

• IdentificationCard / IDENTIFICATION_CARD / 2016 - OCR provider switched to Incode
• IdentificationCard / IDENTIFICATION_CARD / 2023 - OCR provider switched to Incode

Peru

• TravelDocument / CONSULAR_CARD / 2020 - Gender standardised to one letter values

Philippines

• IdentificationCard / POLICE_CLEARANCE_IDENTIFICATION_CARD / 2021 - Gender standardised to one letter values
• Passport / NATIONAL_PASSPORT / 2016 - OCR provider switched to Incode

Paraguay

• IdentificationCard / IDENTIFICATION_CARD / 2018 - OCR provider switched to Incode

Romania

• IdentificationCard / IDENTIFICATION_CARD / 2015 - MRZ lines extracted by Incode OCR
• IdentificationCard / IDENTIFICATION_CARD / 2022 - Document classification improved. Specific field improvements: issuingAuthority, issueDate
• Passport / NATIONAL_PASSPORT / 2019 - MRZ lines extracted by Incode OCR

Singapore

• Passport / NATIONAL_PASSPORT / 2017 - Sensitive data redacted
• ResidenceDocument / RESIDENCE_PERMIT / 2005 - Sensitive data redacted

Slovakia

• ResidenceDocument / RESIDENCE_PERMIT / 2019 - Template improved in general
• ResidenceDocument / RESIDENCE_PERMIT / 2020 - Template improved in general

Spain

• IdentificationCard / IDENTIFICATION_CARD / 2015 - Specific field improvement: name
• Passport / NATIONAL_PASSPORT / 2015 - Template switched to entity_segmentation approach

Taiwan

• DriversLicense / DRIVERS_LICENSE / 2015 - Template improved in general. tamperCheck disabled on template level. paperIdLiveness disabled on template level
• DriversLicense / DRIVERS_LICENSE / 2019 - Template improved in general. tamperCheck disabled on template level. paperIdLiveness disabled on template level

United States of America

• Arizona
  • DriversLicense / LEARNERS_PERMIT / 2023 - OCR provider switched to Incode
  • DriversLicense / LEARNERS_PERMIT_UNDER21 / 2023 - OCR provider switched to Incode
• Colorado
  • DriversLicense / DRIVERS_LICENSE_UNDER21 / 2020 - OCR provider switched to Incode
  • IdentificationCard / IDENTIFICATION_CARD_UNDER21 / 2022 - OCR provider switched to Incode
• District of Columbia
  • IdentificationCard / IDENTIFICATION_CARD_UNDER21 / 2023 - OCR provider switched to Incode
• Idaho
  • IdentificationCard / IDENTIFICATION_CARD_UNDER21 / 2023 - OCR provider switched to Incode
• Illinois
  • DriversLicense / DRIVERS_LICENSE / 2020 - OCR provider switched to Incode
  • IdentificationCard / IDENTIFICATION_CARD / 2020 - OCR provider switched to Incode
• Minnesota
  • DriversLicense / LEARNERS_PERMIT / 2018 - OCR provider switched to Incode
• Mississippi
  • DriversLicense / DRIVER_LICENSE_UNDER21 / 2024 - OCR provider switched to Incode
  • IdentificationCard / IDENTIFICATION_CARD_UNDER21 / 2024 - OCR provider switched to Incode
• Nebraska
  • DriversLicense / DRIVERS_LICENSE / 2017 - OCR provider switched to Incode
• New Hampshire
  • DriversLicense / DRIVERS_LICENSE / 2011 - documentSeriesExpired enabled on template level
  • IdentificationCard / IDENTIFICATION_CARD / 2017 - OCR provider switched to Incode
• New Jersey
  • Other / IDENTIFICATION_CARD / 2023 - Gender standardised to one letter values
• New York
  • DriversLicense / LEARNERS_PERMIT_UNDER21 / 2017 - OCR provider switched to Incode
• North Carolina
  • DriversLicense / DRIVER_LICENSE_UNDER21 / 2024 - Template improved in general
  • DriversLicense / DRIVERS_LICENSE / 2024 - OCR provider switched to Incode
• North Dakota
  • DriversLicense / DRIVER_LICENSE_UNDER21 / 2023 - OCR provider switched to Incode
• Oregon
  • IdentificationCard / IDENTIFICATION_CARD_UNDER21 / 2018 - OCR provider switched to Incode
• South Carolina
  • DriversLicense / LEARNERS_PERMIT / 2025 - Template improved in general
  • DriversLicense / LEARNERS_PERMIT_UNDER21 / 2025 - Template improved in general
  • IdentificationCard / IDENTIFICATION_CARD_UNDER21 / 2025 - Template improved in general
• Tennessee
  • DriversLicense / DRIVERS_LICENSE_UNDER21 / 2024 - OCR provider switched to Incode
  • DriversLicense / LEARNERS_PERMIT / 2024 - OCR provider switched to Incode
  • DriversLicense / TEMPORARY_DRIVERS_LICENSE / 2024 - OCR provider switched to Incode
  • IdentificationCard / IDENTIFICATION_CARD / 2015 - OCR provider switched to Incode
  • IdentificationCard / IDENTIFICATION_CARD_UNDER21 / 2024 - OCR provider switched to Incode
• Washington
  • DriversLicense / LEARNERS_PERMIT / 2018 - OCR provider switched to Incode
• West Virginia
  • DriversLicense / DRIVERS_LICENSE / 2023 - Template improved in general
  • IdentificationCard / IDENTIFICATION_CARD / 2023 - Template improved in general
• Wisconsin
  • DriversLicense / DRIVERS_LICENSE_UNDER21 / 2015 - Document classification improved
  • DriversLicense / LEARNERS_PERMIT_UNDER21 / 2023 - OCR provider switched to Incode

Yemen

• DriversLicense / DRIVERS_LICENSE / 2019 - Specific field improvements: expirationDate