OneSpan Identity Verification Release Notes

The detail verification report received a couple of enhancements:

• Details about the issuing country and the issuing state (province) of the verification document, which are submitted via the UI, are now included in the report.
• The person alive score value included in the report now uses a (more user-friendly) decimal number format instead of a scientific format. (exponential notation), e.g. 0.0001 instead of 1e-4.

• The zones for extracted document information are now always in the following order, independent of the used provider:

  • Visual inspection zone (VIZ)
  • Machine readable zone (MRZ)
  • Barcode
  • Merged zones

  The MRZ and barcode values are not always included in the response.

• Browser and device information (including operating system and IP address) is now extracted and included in the report.
• You now receive a specific error message, which indicates that the verification failed because the document is unsupported or could not be processed.

The Veridas Document SDK and Selfie SDK have been updated to the latest version.

• Barcode scanning for Canadian and US identity document cards has been introduced by Mitek to improve the accuracy of the verification process. Previous versions only supported barcode scanning for Canadian and US driver's licenses.
• Improvements have been made to the user guidance during a document capture.
• Camera fix and Mitek SDK enhancement for iPhone 15 and iOS 17.x.

Description: It is possible to pass the camera check when using the Chrome mobile emulator on a desktop, even though the emulator does not have a front and back camera.

Status: This issue has been fixed.

Description: End users can now download all images for verification if an unsupported document was used.

Description: On iOS 17.x, an issue suppresses the camera permission dialog and directly shows an error that no camera was found.

Status: This issue has been fixed.

Status: This issue has been fixed for the detail verification report (DVR) and the OneSpan Sign evidence summary.

Status: This feature has been reverted.

Description: End users cannot tap the Continue button at the Review Image screen after taking a picture of the ID document on iPhone iOS 17.x devices.

Status: This issue has been fixed.

New OCR enhancements have been implemented by Veridas to improve the data extraction accuracy.

Veridas document and face capture SDKs have been updated to the latest version. The new versions include the following changes and improvements:

• Removed countdown 321 before capturing.
• Removed manual capture button and user clicks on the screen when prompted.
• Showed correct orientation screen between guidance and during capturing process.
• Added review image screen for document capturing.
• Enabled guidance for selfie capturing.

OneSpan has been working with Veridas—our Identity Verification Partner—to improve the overall user experience and acceptance rates with OneSpan Identity Verification. Veridas recently released an improved version that significantly increases the antispoofing performance in the passive and active liveness detection solution by increasing security for the same conversion rates.. The updated engine also yields a higher true acceptance rate.

In detail the update includes the following changes:

• Achieve a similar security level in the 0.77 Lifeproof score threshold compared to the previous one achieved with 0.95 threshold in 2021.
• A higher true acceptance rate in the antispoofing stage, going from 86% (for 0.95 threshold in the release 2023.6) to a 90% (for 0.77 threshold in the new release).
• With the new 0.77 threshold, there is a 1% of maximum attack percentage classification error across different attack species, including screens and print attacks.

OneSpan will be adjusting the person alive thresholds( i.e. Veridas Lifeproof score threshold) on production environment to 0.77 in this release of OneSpan Identity Verification.

The Detailed Verification Report API has been enhanced to include the download URLs of the selfie image and the image from the ID document. The images can be downloaded and used for manual verification if the end user verification fails for different reasons, for example because the user has submitted an unsupported ID document.

Several workflows now support barcode scanning for driver's licenses that were issued in Canada and the United States. The extraction of data from the barcode improves the accuracy of the verification process.

The following enhancements have been implemented in the default workflows of the integration with OneSpan Sign:

• Additional languages supported. The following languages are now also supported:

  • Bulgarian
  • Norwegian

• The providers' document and face capture SDKs have been upgraded to the latest versions. The new versions include enhancements for user experience and several technical improvements.

The following enhancements have been implemented in the default workflows of the integration with OneSpan Sign:

• Additional languages supported. The following languages are now also supported:

  • English (UK)
  • Polish
  • Spanish (Spain)
• Partial name matching has been enabled.
• Migration to new user interface framework. A number of default workflows have been migrated to the OneSpan UX framework (React).

• OneSpan will be deploying IDV 2023 R2.1 in UAT to enable the validation of additional use cases.

  This release will have no impact on any existing clients or configurations.

The Detailed Verification Report API has been enhanced to include the following new items in the verification result:

• The provisional driver's license matcher details.
• Further personal information and document key data.

• The provider's document and face capture SDKs have been upgraded to the latest versions.

IDV has been enhanced to provide guidance when users are capturing an image of their ID document or their selfie. This new feature enhances the user experience and helps to improve the quality of the captured images.

Known issue: Document analysis and data extraction with IDV may intermittently fail on iPhone 12 Pro and Pro Max, iPhone 13 Pro and Pro Max, and iPhone 14 Pro and Pro Max, if running iOS 16.

Users may experience issues when trying to capture their ID documents on iPhone 14 Pro Max.

Status: This issue has been fixed.

• General updates for operating system and third-party library dependencies have been implemented.

The Detailed Verification Report API enhances the user experience and improves the IDV integration capabilities to retrieve the verification results for a transaction. The returned information includes a picture of the document, as well as the score and the threshold that are associated with the verification.

In this product release, the API focuses on personal information and the legal name.

• The provider's document capture SDK has been upgraded to the latest version.

Document verification fails if the transaction participant is underage.

Status: This issue has been fixed. The age of the transaction participant is no longer taken into consideration during the document verification process.

The audit trail document contains the IP address of the signer's device. In addition to the correct IP information, the audit trail document also contains a row with an unknown IP address.

Status: This issue has been fixed.

• The provider's document capture SDK has been upgraded. The new version includes several technical improvements.

• A new API for audit trail generation has been added (generate-audit-trail). With this API, you can generate the audit trail document at any time during an active workflow.
• The following information has been added to the audit trail:

  • The IP address of the signer's device.

    In addition to the correct IP information, the audit trail document will also contain a row with an unknown IP address. You can ignore this row.

  • The signer's email address.
  • The signer's phone number.

• Some of the internal OneSpan Identity Verification libraries have been upgraded to the latest versions to remove vulnerabilities that were present in older versions.
• The provider's document capture SDK has been upgraded. The new version includes a fix for canvas detection sizes for all devices, as well as several other bug fixes and improvements.

• iPhone SE (2nd generation)
• iPhone 12 Pro
• Samsung Galaxy S20 (SM-G981W)
• Huawei P30 Pro
• Redmi Note 9
• Google Pixel 4a

• Samsung Galaxy Tab S7

The Veridas DVF workflow has been enhanced to accommodate the following:

• Support of the following languages:

  • Chinese Simplified
  • Chinese Traditional
  • Danish
  • Dutch
  • English
  • French
  • German
  • Greek
  • Italian
  • Japanese
  • Korean
  • Portuguese
  • Russian
  • Spanish
• Support of notifications: Users will receive a notification at each step of the workflow.

• Only phone numbers that are supported by Twillio are accepted. The phone number format is:

  "+" followed by 5 to 15 digits

• This version of OneSpan Identity Verification includes a number of general bug fixes and product improvements.
• Some of the internal OneSpan Identity Verification libraries have been upgraded to the latest versions to remove vulnerabilities that were present in older versions.

Issues with face capture

Face capture did not work because iOS 15 does not support the provider SDK.

Status: This issue has been fixed. The corresponding provider SDK has been upgraded and correctly linked in OneSpan Identity Verification.

• Workflows can now be shared between tenants.
• A Veridas DVF sharable workflow has been created.

Configurable auto-redirect has been implemented. It redirects directly to the client website instead of displaying a page where the user needs to click a button to be redirected.

This feature can be used, for example, on Thank you or Verification failed pages.

• The database connection is now atomic, which helps to prevent transactions from being blocked in the middle of a process.
• The AmazonMQ policy has been updated to increase the number of retries. This improves the reliability of internal component communication.
• The signature size has been optimized to be around 50 KB instead of 150 KB.

• Support for ID cards from Colombia has been added.
• The tampered document check has been improved.

An alert is now sent to OneSpan Customer Support when a transaction is blocked in the middle of the process.

Orchestrator operations are now atomic and resilient to concurrency.

• OneSpan Identity Verification has been upgraded to the latest provider SDKs.
• Support for ID cards that do not expire has been added.
• The format of the verification response has been updated as part of advanced name matching.

Some of the internal OneSpan Identity Verification libraries have been upgraded to the latest versions to remove vulnerabilities that were present in older versions.

• The following additional languages are now supported:

  • Danish
  • Dutch
  • German
  • Italian
  • Portuguese
  • Russian
  • Spanish
• English is the default language.
• SMS content can be localized.

• Guidelines have been added to the capture view to improve the user experience when an image of the passport is captured.
• The name matching algorithm has been improved to be more accurate and to reduce the false positive rate.

• Transactions can now be deleted automatically after they pass the configurable data retention period.
• Two different retention periods have been added for completed and incomplete transactions.

• A database check has been implemented to check the API health. The system will trigger a notification whenever there is an issue with the database connection.

• The database connection has been improved.

• Four IDV workflows have been added, and more countries and phone numbers are now supported.

• Users can now choose between document and face verification, or document verification only.

• The IDV workflows' look and feel has been adapted to match the OneSpan Sign look and feel.

• The IDV workflow events have been added to the OneSpan Sign audit trail document.

• The IDV workflow now supports mobile-only scenarios where no SMS is needed.

• The IDV workflows are also available in French.

With this feature customers can:

• Provide a parametrized Handover (redirect) URL per transaction.
• Provide a different Handover URL per page.

A new API has been added for transaction deletion. Users can now request to delete one or more transactions.

This feature facilitates the data controller's improved control over their transactions.

• Users no longer need to rotate the mobile device to capture an image of a document.
• The camera view is launched in full-screen mode.
• Android 11 and Chrome 89 are now supported.

• Reporting: Duplicate events are removed from reporting. Report generation is now semi-automated.
• An issue with double notifications for document verification has been fixed.
• The API response contained an incorrect error message when an invalid identity document was provided. This issue has been fixed.
• The lifetime of the tenant token has been limited to 5 years.

• Upon successful authentication via SecureKey, Secure Agreement Automation receives the required user data.
• Secure Agreement Automation matches the received/extracted data with the data provided by the client.
• Secure Agreement Automation calculates the verification results and sets the verification status to indicate either Success or Failure.

• The available document type is now filtered based on the selected country.
• The select document type and country page and the select country/state page are now ADA-compliant.
• The country code no longer needs to be provided when initiating a transaction, and the address field is now optional.
• The issuing state has been added to the verification hub AT document.

• The evidence pack issue where the contract image is missing from the screenshot has been fixed.
• There was a limitation of 1 MB for configuration, which limited the number of tenants that could be configured on the system. This limitation has been removed.

• The current workaround whereby the end user's address country must be submitted to the provider has been removed. This may not be the same country as indicated in their identity document.
• The end user's identity document type and country are now identified, for submission of this information to the provider to optimize the verification.
• The end user's identity document state and province are now identified. This data is required e.g. with US, Canadian, and Australian driver's licenses.

• The transaction ID and user role are now passed in the call-back URL to the tenant.
• The Role Handover feature can be used without document signing in the workflow.
• Multiple browser windows and tabs can now run at the same time.
• The limit of supported phone number formats has been increased from 64 to 200.

• The issue with duplicate OTP failure in Audit Logger has been fixed.
• Upgrade to Angular 10.

• Handle French maiden name.
• Handle truncation of the name on the machine-readable zone (MRZ).
• Handle special case characters:
  • Spaces
  • Accents
  • Hyphens
  • Apostrophes
  • Commas

• The face verification event has been added to the reporting in the Audit Logger service.
• The face verification feature can now trigger a notification.
• The face verification event is part of the single evidence pack.

• Face capture verification is now available.
• The new MiSnap SDK enables auto document capture and increases the quality of the captured image.

• Integration of Secure Agreement Automation with URL shortener. The SMS sent to the mobile phone to proceed with document verification is now using the URL shortener.

• The communication with the provider has been changed to be asynchronous. With this change, the application will not time out if the verification process takes a longer time.

• Logs have been enhanced for all the Secure Agreement Automation microservices (except for the Puppeteer microservice).
• Request traceability has been improved by enabling logging of all outgoing responses with an actual response status.
• Logging has been added to decision points of the state machine (guards).
• Logging has been added to the shutdown cycles of the state machine.
• Logging notification types are now sent to the client (Notification Service Server).
• Logging has been improved to facilitate transaction tracing among the platform’s microservices.
• Further logging enhancements have been implemented in various Secure Agreement Automation components.

• It is now possible to apply the signature to the agreement at any place in the workflow (prior to this, it was applied at the final confirmation page only).
• The box size and location of the signature have been aligned between the UX and the PDF.
• The transaction ID is added to the Audit Logger service.
• Support for Base64 PDF to initiate a transaction.

• Integration. Integration for document verification, face verification, and liveness check.
• Multi-device support. The ability to start the process on a desktop and receive an SMS to continue the face verification process on a mobile phone.
• Reporting. Differentiate in the reporting between document verification failed and face verification failed.

• Verified supported documents.

  The following subset of documents and countries is now supported in this release:

  • Spain (Driver's License – Supported; National Identity Card – Supported; Passport – Supported)
  • France (Driver's License – Supported; National Identity Card - Not completely supported; Passport – Supported)
  • USA (Driver's License - Not supported by Secure Agreement Automation, collection of issuing state is not part of Secure Agreement Automation ATM; National Identity Card - N/A; Passport – Supported)
  • Canada (Driver's License - Not supported by Secure Agreement Automation, collection of issuing province is not part of Secure Agreement Automation; National Identity Card - N/A; Passport – Supported)
  • United Kingdom (Driver's License – Supported; National Identity Card - N/A; Passport – Supported)

• The evidence pack no longer displays "null" if the user does not provide an address.
• The Puppeteer service is now asynchronous to make the evidence pack generation more reliable and stable.
• Modify the Puppeteer service to obtain its version from a single place to avoid misconfiguration during deployment.

• Ensure the branding is consistent between what is provided in the initiate transaction JSON and what is used in the URL so that the correct branding is displayed to the customer.
• Tenants have separate queuing mechanisms for their requests.
• Container hardening policies of OneSpan are now applied to Secure Agreement Automation microservices.
• The Secure Agreement Automation OTP account is now linked to OneSpan instead of the Dealflo account.

• Notifications can be sent to multiple endpoints per workflow and per tenant (originally Secure Agreement Automation 3.4.1).
• The transaction ID and the notification type are now added to logs in order to simplify debugging.
• All Secure Agreement Automation notifications include milliseconds in their timestamp.

• In the case of document verification for a driver's license check, the second image (taken in color) is sent to the provider and saved in the audit trail document in greyscale. This does not impact the verification process.
• The generation of AT is slower than in previous versions due to recent modifications: 650 per hour instead of 1100+ per hour. This does not impact Ford which expects 50 transactions per peak hour.
• Face verification is not ADA-compliant due to an issue with the SDK for face capture.
• The Get Transaction Verification API returns a 404 error sporadically. On further retries, it responds successfully.