Hub Help

2025.04.10 Release Notes

Summary

This release introduces new features, improvements, and fixes bugs. Importantly, we have now added the ability to mask Personally Identifiable Information (PII). See Customer PII Results for details.

New features

Data management

  • Customer PII results.

    Customers can now work with Intellicheck to specify which personally identifiable information will be displayed when the “Display PII” switch is turned on. This applies to both the transaction history page and Portal results page. Contact your CSM for help getting started.

Improvements

Core API improvements

This functionality is part of the core cloud API, so all access methods – Portal, Capture, Desktop – will see these improvements.

  • Image cropping.

    To make it easier to see if an image is clear and improve the quality of the OCR process, Capture now crops images before processing them. Specifically, after a customer captures a picture of an ID, we now automatically crop the image before it is displayed for approval – keeping only the part of the imagine inside the ID box on the screen. This makes the OCR process more forgiving of blurring and other image issues.

Capture improvements

  • Simplified document capture instructions.

    In order to reduce the number of ID photos customers must re-capture, we have updated text on the review image page in Capture. The text now reads, "Ensure your photo is clear, with no glare or blur, to avoid verification delays. Retake it if needed before submitting."

Hub improvements

  • Added barcode column.

    We added Barcode as a column selection on the Transactions page. See Transactions.

  • Improved risk alerts and messages.

    We changed how risk alerts and messages are presented.

    • On the Transactions page, we show a red Fail message in the Risk Alert column only if OCR matching failed.

    • On the Results page, in the Auth Session Results panel, we changed the label from the word Warning to the word Alert.

    • For an OCR-Barcode Match or OCR-MRZ Match, an Alert now means that one or more important mismatches were found.

    • On the result boxes, we updated several messages, such as Barcode passed/expired, Barcode failed, and Front matches barcode with warnings.

    See Investigate Transactions and Cardholder Information Warnings and Messages.

Bug fixes

Capture bug fixes

  • Jira NP-857 - Refresh does not work

    In Capture, refreshing the final completed page now works as expected.

Hub bug fixes

  • Jira NP-855 - User changes are not saved

    Changes made on the edit user page are correctly saved when Department is blank.

  • Jira NP-869 - Result value is not correctly copied

    On the transaction details page, data copied to the clipbord now includes the correct Result value.

  • Jira NP-891 - Page should not reload

    When the user navigates away from Hub to a new browser tab, and then navigates back to Hub, the page stays where the user left it. The page does not reload.

  • Jira NP-904 - New user password error message not shown For a new user, when the passwords in New Password and Confirm Password do not match, an error message now appears.

  • Jira NP-1000 - Horizontal scroll bar is cut off

    On certain pages, when the browser was in full screen mode, the lower horizontal scroll bar was missing. It now correctly appears at the bottom of the page.

  • Jira NP-1115 - Company and customer not found in search

    On the Create User page, searching the Company and Customer list correctly shows expanded results when company and customer share the same name.

  • Jira NP-1157 - Change password error message not shown For a password reset, when passwords in Old Password, New Password, and Confirm Password are the same, an error message now appears.

Portal bug fixes

  • Jira NP-1028 - Front and back images are stretched

    On the Portal v1 results page, an image of the ID document maintains the proportional size of the original.

  • Jira NP-1137 - Portal results not displayed

    On the Portal results page, transaction data is correctly displayed.

Known issues

No known issues in this release.

30 May 2025