Release 25.R4: July 2025

Changed Behavior

Here are some of the changes in behavior that you might want to be aware of.

Accessibility

As part of the accessibility issues that have been fixed in this release, the following changes in behavior will now be observed when signing a transaction:

• When you focus on an element in the Signer Experience, a box (border) will be displayed around the element.

• A checkmark will now be displayed next to the currently selected language within the Language menu.

• Hover colors within the Language menu have been updated from a shade of the primary color to a more neutral color.

• Hover color of buttons displayed in the primary color will now be a lighter shade of that color (example: the Download Individual Document buttons).

• Hover color of buttons displayed in dark grey will be a lighter shade of that color (example: the zoom in/zoom out buttons).

Updated Capture Signature Panel

The Capture Signature panel within the Sender UI has been updated to use the same panel as that displayed within the Signer Ceremony. Note the following: (refs PB-112574)

• The panel no longer opens as full screen. The user can still make it full screen, but it will not be the default.

• The screen size (regular vs full screen) will be remembered the next time the sender accesses the Capture Signature panel.

• The text “Draw signature” is now displayed under the signing line.

• Resizing the panel after drawing the signature will clear the signature.

Delegation Start Variable Added to Activation email:

The out of the box email.delegation.activate email template has been updated to include the delegation start date. (refs PB-116151)

The string "Your role as a delegate will expire on: $EXPIRY_DATE;." has changed to "Your role as a delegate will span from $DELEGATION_START_DATE; to $EXPIRY_DATE;."

No changes will be made to the email.delegation.activate email at the account level.

Additional Changes in Behavior

• The Password Rules on the Reset Password page will now show only the rules configured for an account. For example, if you don't have a minimum password length defined (set to 0), the Password Length will not show on the Reset Password page. (refs PB-110679)

• The date picker control within the sender UI has been slightly updated. You will now see the month and year appear to the top left of the date picker with a drop-down that allows changing the year, and the previous/next month buttons are now displayed in the top right corner of the date picker. (refs PB-112570)

• Using a browser’s auto-fill feature has been disabled in the Signer Experience. (refs PB-116262)

• The OneSpan Sign logo has been removed from the display when previewing the signing customization page. (refs PB-116237)

• The Arkhineo and SFTP connectors are now End of Life and no longer available.

Upcoming Changes

Here are some of the new features, changes and enhancements that we will be introducing in an upcoming release.

• Regrouping of Signature and Initial signature types: For clarity and ease of use we will be regrouping our signature fields that appear in the Signature Type drop-down list so that the Click to Initial signature type no longer appears with the other signature types (Click to Sign, Capture Signature, Mobile Capture). (refs PB-113072)

• Name change for SMS OTP in Evidence Summary: If you are an API integrated user you should be aware that we will be changing the name of the SMS OTP event that appears in the Audit Trail section of the Evidence Summary. (refs PB-113072)

Existing event name: Sent SMS

Upcoming event name: Sent SMS code

• Deprecation of IDV Workflow Configuration APIs: In an upcoming release, the following IDV Workflow Configuration APIs will be deprecated, and no longer available of use. (refs PB-116894)

  

What's New

Here are some of the new features and enhancements we have made for this release.

In App-Documentation

You can now access our documentation directly from the OneSpan Sign UI, with the added ability to view context relevant articles depending on where you are. (refs PB-101047)

This feature will be enabled by default for newly created accounts only. It can also be enabled or disabled using the Account Configuration page.

This feature is only displayed on viewports larger than 1024px.

Beta - SMS Notifications

In addition to receiving transaction notifications by email, transaction notifications can now be sent by SMS.

Note that this feature is currently in BETA and only available in Sandbox environments. To enable this feature please contact our Support Team. (refs PB-108033).

Enhanced File Upload Error Reporting for Integrators

Previously, when uploading multiple files using APIs if one or more files contained errors the REST response would not identify which of those files the errors pertained to.

Now, should this situation occur the REST response will include the following information: (refs PB-113308)

• The document that failed to load.

  This is only the case for file validation errors, NOT for errors originating from the platform. Platform related errors will be displayed as a generic message.

• A specific error message explaining why the document failed to load.

  Only the first document that fails to load will receive an error, as the upload will stop once an error occurs

Delegation for Integrators

You can now use APIs and Java SDKs to create a delegation session, using oAuth2.0 authentication. (refs PB-115754)

This means that you can now:

• Create an oAuth2.0 authentication token on behalf of another sender (by passing a sender Id to the token generation request)

• Create an oAuth2.0 authentication token as a delegate (by passing a sender Id and delegator Id to the token generation request)

• Perform API calls (to manage transactions, create authentication tokens, etc.) using this token

This feature is not supported when using Roles and Permissions. Additional technologies (such as .NET SDK) will be available in a future release.

User Interface Improvements

As we continue to modernize our Sender interface we are gradually rolling out new icons, tool tips, error and information messages, and more! (refs PB-116198).

In addition, for OneSpan Identity Verification transactions we have updated some of our notifications for clarity and better understanding. For example: (refs SAA-23306)

Bug Fixes

The following issues were resolved in this release:

Accessibility

• We have fixed an issue where the Language option in the More Actions menu was not tagged as a heading. (refs PB-112761)

• The focus state contrast in UI elements of the Signer Experience now meets WCAG Accessibility standards. (refs PB-115641)

• To meet WCAG Accessibility standards, we have updated certain elements in the Signer Experience so that color is no longer the only indicator of a focus state. (refs PB-115643)

• The hover contrast in UI elements of the Signer Experience now meets WCAG Accessibility standards. (refs PB-115644)

• The Enable Accessibility Mode button now has the proper role information attached to it. (refs PB-115984)

Admins

• When an individual signer is also an Ad Hoc Group member and a signing order is set, on accepting the eConsent as the first role, only one approval is now tracked in the Evidence Summary. (refs PB-115370)

• When an account is deleted some transactions belonging to that account were getting deleted, even though they were still within the defined grace period during which these transactions should have still been available. Now, upon account cancellation transactions are no longer marked as deleted and will not be purged until the grace period after the cancellation date has been reached. (refs PB-117091).

Integrators

• When rejecting an attachment using an API, the Name, Description, and Required properties are ignored. This makes the API behavior consistent with the Sender UI behavior. (refs PB-116353).

Senders

• When using the same layout on multiple documents, moving a signature on the first document would sometimes move the signature on the second document as well. This no longer happens. (refs PB-112756)

• Email validation is now performed as part of the pre-processing when adding multiple members to an ad hoc group (Groups call). As such if an error occurs with one entry, the saved members will not be removed. (refs PB-113748)

• Rapidly double-clicking the Save button when adding an attachment would sometimes results in an error message, as the system believed that two attachments with the same name were being uploaded. The Save button is now unavailable once it has been clicked once. (refs PB-114230).

• Members of an ad hoc group that were replaced using the Recipient Settings modal no longer appear within the Recipients section of the Transaction Edit. You do not have to refresh the page to make them disappear. (refs PB-114660)

• The Signing Order is now updated correctly when replacing an Ad Hoc Group with a different recipient. (refs PB-114670)

• The Template Designer is now available for users who do not have the Transaction permission. (refs PB-116136)

Signer Experience

• We have fixed the misalignment between the Ad Hoc Group/Member recipient row and their respective More Actions button on smaller screens. (refs PB-113539)

• The Authentication page of the Signer Experience did not appear in the Signer’s preferred language if that Signer was also had a OneSpan Sign Sender account, and if the preferred language was updated after the transaction had been sent. The preferred languages now appear as they should. (refs PB-115683)

• The signature stamp from the account profile now automatically uploads when the signer is added as a group in the transaction. (refs PB-117016)

Vulnerabilities

• This release also includes important security and vulnerability fixes.