Our New Signer Experience

Welcome! 

Welcome to our New Signer ExperienceThe experience of an end-user as they review, accept, sign, and potentially download documents. — i.e., the part of the New User Experience intended for signers. This feature was introduced when OneSpan Sign 11.30 was released in September 2019.

The New Signer Experience improves the reviewing and signing of documents in many ways, including the following:

  • It has a new intuitive interface that accelerates the e-signing process.
  • Responsive Web Design: The source content is reused across all devices (desktops, laptops, tablets, mobile phones), responding to the user’s behavior and environment based on screen size, platform and orientation. Elements like layout, text size, navigation, and images automatically adjust to fit the user's device.
  • Customization! You can now personalize your signing interface with your own corporate brand. Use your own localized logo, your own colors, and your own text strings. Account Admins can customize the logo and colors directly from the New User Experience's sender interface.

Note that it's completely up to you whether you try the New Signer Experience. If you're not yet ready, don't worry. We won't implement this feature on your system until you ask us to do so.

When you're ready to move to the New Signer Experience from the Classic Signing Ceremony, you will need to submit Migration forms to our Support Team. These forms will help that team customize your New Signer Experience just the way you want it (with your preferred branding, enabled features, etc.). To access those forms, click here.

Deprecation of Classic Signing in 11.42: The Classic Signing Ceremony — i.e., the part of the Classic User Experience for Signers — will be deprecated in OneSpan Sign 11.42. The part of the Classic User Experience for Senders and Admins was deprecated in OneSpan Sign 11.35. Thus once OneSpan Sign 11.42 is released: (1) no part of the Classic User Experience. will be supported; (2) all accounts will be moved to the New User Experience.

The rest of this page discusses:

Feature Availability

The features available in the New Signer Experience are of two types:

Classic Signing Ceremony Features

As of OneSpan Sign 11.40, the New Signer Experience has all the features that the Classic Signing Ceremony has. Thus all of the following Classic Signing Ceremony features are now available in the New Signer Experience:

Feature Description For more information see...
Accept Only The Accept Only option opens the Acceptors for <Document> dialog box, which enables you to specify recipients who must "accept" this document during the Signing Ceremony. Configuring a document as Accept Only removes all the Signature Fields it contains. Accept Only
Attachments

Enables a signer to upload additional, supporting documents during the Signing Ceremony.

Note that:

  • By default, the following file types are supported: PDF, DOC, DOCX, RTF, ODT, JPG, JPEG, PNG, BMP, TXT, TIFF, TIF, GIF, XLS, XLSX
  • Account owners can define a whitelist of file types that may be uploaded as transaction attachments by signers on the account. This list cannot include file types on the global blacklist (see the next bullet).
  • To prevent signers from uploading malicious code, the following file types cannot be uploaded as attachments to a transaction: EXE, DLL, MSI, DMG, SO. This blacklist supersedes all account-level whitelists.
Uploading Attachments
Authentication (SMS, Q&A, KBA)

To add an extra layer of security to your online transactions, OneSpan Sign offers robust and flexible recipient-authentication options. Specifically, you can select various ways of validating the identity of the recipient of an invitation to a transaction before they are permitted to access the transaction's documents.

Configuring Recipient Authentication
Auto/Form Fields

When senders create transactions or templates, they can add Form Fields to documents. Form Fields enable the placement of additional data in a document at the time of signing. Like Signature Fields, non-signature fields can be placed anywhere inside a document.

Adding Fields to a Document
Capture Signature + Mobile Signature + Optional Signature Enables the use of Capture Signature, Mobile Signature and Optional Signature in the New Signer Experience. Adding Fields to a Document
Certificate Signing Enables users to sign with a digital certificate that resides on a Smart Card or hardware token. Personal Certificate Client
Change Signer Enables a signer to reassign their signing responsibilities to another signer. For example, suppose a man receives a document to sign, but then discovers that the signer should be his wife. With this feature, he can reassign all his signatures to his wife. Changing Signers
Click-to-Sign / Click-to-Initial Enables users to stamp their name or initials on a Signature Field by clicking it. Signature Fields
Decline

Enables an authenticated recipient to decline to sign a transaction.

The reasons for declining presented to signers can be displayed in a specified language for a given account (this feature is not available at the transaction level). To configure this feature, Admins should contact our Support Team.

Declining to Sign

Delegate Signing Enables a user to delegate access to their OneSpan Sign transactions to one or more other users on their account. For example, if an employee is away on vacation, they can ask other team members to manage and sign their transactions while they're away. Delegating Access
Document Download For their own personal records, recipients can download a transaction's signed documents.

Downloading Signed Documents

Documents/Recipients Signing Order

If a transaction contains multiple documents, each recipient must sign the documents in the order in which they appear in the Documents list.

By default, a transaction's recipients can sign in any order. If it is important that signatures be obtained in a specific order, a Signer Workflow can be defined. When such a workflow is defined, signatures are obtained from recipients in the order in which the recipients appear in the Signers list.

Specifying the Signing Order

Adding Documents to a Transaction

Evidence Summary

For every signed transaction, OneSpan Sign captures an extensive Evidence Summary and Audit Trail. This Evidence Summary can be downloaded and viewed at any time. It is available to all transaction owners, both as an individual download and as part of the completed transaction.

Evidence Summary & Audit Trail
External Signer Verification

When a signer is trying to confirm their approval of a document, this feature enables OneSpan Sign to verify the signer's identity via their credentials with an external organization (e.g., DIGIPASS).

External Signer Verification
Fast Track Enables the rapid distribution of transactions for signing, automates the e-signature process, and eliminates the need to send individual transactions to your recipients. With Fast Track, you can associate a template with a single URL that links to your documents, and distribute it instantly to a large number of recipients. Fast Track
Fields font size Enables choosing the font size that will be used for a field's text when the field's parent document is printed. Creating a Transaction
Group Signing Enables a set of OneSpan Sign users to act as a single signer from the point of view of a transaction's creator. Groups
Handover URL

A Handover URL enables you to customize what happens after a recipient interacts with a transaction. For example, if a recipient declines to sign a transaction, a Handover URL is automatically triggered, and the application closes. If the recipient signs the transaction, you can either have them stay within the application itself, or direct them to a different URL (for example, a Signing Complete page).

Admins can specify different Handover URLs for different languages (this feature is available at the account level, not at the transaction level). To configure this feature, Admins should contact our Support Team.

Handover URLs
iFrame Support

iFrames can be used to integrate our New Signer Experience into a third-party application.

iFrame Best Practices
In-Person Signing

Enables a transaction to be signed in person by all signers on the same device.

Transaction Settings
Notarized Signing Enables a notary and other signers to sign and thus notarize electronic documents. e-Notary
OFAC Support The Office of Foreign Assets Control (OFAC) prohibits US citizens, businesses, and financial institutions from engaging in business or financial transactions with persons or entities in certain foreign countries. When the OFAC Support feature is enabled, we screen the IP addresses of users who connect to OneSpan Sign to ensure that our customers comply with OFAC's sanctions. U.S. Department of the Treasury
Optional Signatures Enables a signer to complete a transaction without signing all of their signatures inside the transaction's documents. Any of their signatures can be flagged as "optional". Optional signatures
Stylus Pens

Signers can use stylus pens on touchscreen devices to complete all actions in the Signing Ceremony (including Capture Signature and Mobile Signature).

Capture Signature & Mobile Signature

New Features

The New Signer Experience has improved the User Experience in many ways. The following table lists features available in the New Signer Experience that were never available in the Classic Signing Ceremony:

Feature When Introduced
Branding – Localized Logo & Strings

Release 11.31

Conditional Fields

Release 11.32

Guest Authentication pages redesign Release 11.37
Localized Decline reasons Release 11.35
Localized Handover URL Release 11.35
Remove iFrame from New Sender UI Release 11.39
Responsive design Release 11.30
Self-Branding – Colors Release 11.31
Session expiry warning Release 11.36
Signature Navigator Release 11.32
Signing Complete page (complete redesign) Release 11.30
Undo Signature Release 11.33
Webview support Release 11.40
Welcome/Overview page Release 11.38

Future releases will continue to introduce new features to meet the evolving expectations of signers.

What if a Transaction Includes Features not yet Available?

After you activate the New Signer Experience, if a transaction uses a feature that has not yet been implemented, signers will automatically be directed to our Classic Signing Ceremony.

The New Signer Experience will not support e-Witness (the OneSpan Sign component that stores viewed web pages and workflow-based actions taken by signers during the signing/delivery process). Note that this exclusion does not impact the document-based Audit Trails or Evidence Summary that accompany completed transactions; the New Signer Experience will continue to support them.

Remember too that you can deactivate the New Signer Experience at any time, simply by contacting our Support Team.

How Can I Access the New Signer Experience?

To access the New Signer Experience:

Click here to access our Migration Forms. These forms will help our Support Team get you up and running as quickly as possible.

Don't worry about finishing these forms all at once. You can always leave and go back to them, and your progress will be saved. HOWEVER, if you decide to complete these forms at a later time, you MUST click the Go To Documents link in the Branding Request email that you will receive. Do not try to return to your browser page directly.

To complete these forms, you will need the following:

  • Your Account and Contact information:
  • The image you would like to use in your New Signer Experience. This is the image that will appear as a header during the New Signer Experience. It will be visible to all signers. Your image should:
    • Be no larger than (258 pixels in width x 40 pixels in height)

    • Be a JPEG, PNG, GIF, or BMP file
    • Have a transparent background (preferable)
    • Account Admins can select this image directly from the New User Experience's sender interface.

    • You have the option of using an existing image. For example, you may have already provided a logo for the Classic Signing Ceremony, and may want to use the same logo for theNew Signer Experience.

  • The strings to be used when declining to sign. Specify these strings if you would like to customize the list of reasons from which your signers can select when they decline to sign a transaction.
  • Some specification of how you want the Thank You Summary to look:
    • Whether the transaction owner's name will appear
    • Whether the signer's name will appear
    • Any custom messages you would like to display

The New Signer Experience can be localized in many different languages. However, you will need to do this separately for each language. Once you have finished filling out the forms for one language, you will then be given the option to continue customizing the New Signer Experience in another language.

If you want more testing flexibility, ask our Support Team to create a separate Sandbox account that will be dedicated to the New Signer Experience.

What Environments Are Supported?

What follows is a list of the environments supported by the New Signer Experience.

Operating Systems

  • Microsoft Windows 7, 8, 8.1, 10
  • Mac OS X

Browsers

  • Edge (the latest version, plus the two previous versions)
  • Starting with OneSpan Sign 11.39, Edge in IE mode is no longer supported by the New User Experience, including the New Signer Experience.

  • Chrome (the latest version, plus the two previous versions)
  • Firefox (the latest version, plus the two previous versions)
  • Safari (the latest version, plus the two previous versions)

For all browsers, cookies must be enabled.

Mobile Devices

  • iOS
  • Android

Device recommendations:

  • For the best experience on an Apple device, we recommend using an iPhone 6S or higher, or an iPad Air 2 or higher.
  • On a touch-screen device, a minimum of 2 GB of RAM is recommended. However, the more RAM you have, the better the performance will be.

Important Changes That May Affect You

Our New Signer Experience introduces some important changes that you should bear in mind when you do your tests. These changes might require you to adjust some of your settings.

Should you be concerned about any of these changes, please note that you can always revert back to your existing Signing Ceremony settings by contacting our Support Team. Also note that any API integrations you may have done will NOT be affected by moving to the New Signer Experience, though your iFrame configurations may be impacted.

Change Description
Hosting an in-person transaction

This change impacts customers who use a Signer Authentication Token to start an in-person signing session. In the New Signer Experience: (1) the transaction owner can always start an in-person transaction; (2) a signer who is an account sender can also start an in-person transaction, but only if the feature “Allow In Person for Account Senders” is enabled for the account. By contrast, the Classic Signing Ceremony permits any signer to start an in-person transaction. Thus to get a Signer Authentication Token that can be used to start an in-person transaction, you may need to update your integration to use the ID either of the transaction owner or of a signer who is also an account sender. Note: The person who starts an in-person transaction can run it, in the sense that they can switch from one signer to another during the signing session.

Mobile Signing Ceremony vs Responsive Design

Our new responsive design permits only one application to be used on desktops, laptops and mobile devices. This means that the Mobile Signing Ceremony will no longer exist after you move to the New Signer Experience.

Deprecation of the Opt-out Menu

To streamline the signing experience, we are deprecating the option to Opt-Out of a signing experience. However, signers can still use the Decline option. If you still need content that appeared in your Opt-out menu, you can add it to the Decline menu with help from our Support Team. If you are currently using only the Decline option, your configurations (e.g., your reasons for declining) will remain the same.

E-Consent The Accept button will still appear at the bottom of the page. However, you can request to have a new checkbox appear at top of the page that will enable signers to accept the E-Consent document by selecting that box. This will save signers from having to scroll all the way to the bottom of the page.
Email information will be removed from the Handover URL Currently, a signer's email information is passed to and shown in the Handover URL. With the New Signer Experience, this email information will be replaced by the Signer ID parameter.
Branding Bar The Branding Bar will no longer be supported.
Using URLs to define an account logo You can no longer use a URL to link to an account logo.
Document Descriptions Document descriptions will no longer appear in the New Signer Experience.
iFrame ‘scrolling’ attribute This change impacts customers who have iFrame configurations. For scrolling to work in the New Signer Experience, iFrame configurations require that the scrolling attribute be removed. By contrast, scrolling worked in the Classic Signing Ceremony if the scrolling attribute was set to false. Thus you may need to remove the scrolling attribute.

For instructions on using the New Signer Experience, click here.

Was this information helpful?
X