Our New Signer Experience
We are proud to introduce our New Signer ExperienceThe experience of an end-user as they review, accept, sign, and potentially download documents., which became available in September 2019 with the release of OneSpan Sign 11.30.
Note that the option to use the New Signer Experience is completely up to you. Should you decide that you are not yet ready to try our New Signer Experience don't worry — until you contact our Support Team, no changes will be made to your account. We will not implement this feature on your system until you tell us to do so.
The New Signer Experience offers signers the following advantages when they review and sign documents:
- 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.
The rest of this guide discusses:
- Feature Availability
- What if a Transaction Includes Features not yet Available?
- How Can I Access the New Signer Experience?
- Important Changes That May Affect You
The New Signer Experience brings many improvements to the User Experience. Moreover, future releases will continue to introduce new features to meet the evolving expectations of signers.
However, certain features currently available in the Classic Signing Experience are not available in this release of the New Signer Experience. While we’ve tried to include the features used by most of our users, some features critical to your account may not be included in the New Signer Experience just yet. Don’t worry — we plan to gradually deploy these features over the next few months.
The following table should help you to decide if and when you should implement the New Signer Experience:
The above table lists:
- Available New Features — These are features available in this release of the New Signer Experience that are not in the Classic User Experience.
- Available Existing Features — These are features available in this release of the New Signer Experience that also exist in the Classic User Experience. The next section, Existing Features in This Release, describes most of these features.
- What's Not Available — These are features in the Classic User Experience that will be coming soon to the New Signer Experience.
- Planned For New Features — These features are not in the Classic User Experience, and thus will be completely new when they become available in the New Signer Experience.
The following Classic User Experience features are among those available in this release of the New Signer Experience:
|Feature||Description||For more information see...|
|Attachments||Allows you to upload additional, supporting documents during the Signing Ceremony.||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|
|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|
|Signature Fields||You can now use Capture Signature and Optional Signatures in the New Signer Experience.||Adding Fields to a Document|
|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|
|Decline||This feature enables an authenticated recipient to decline to sign a transaction.|
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|
|Document Download||For their own personal records, recipients can download a transaction's signed documents.|
iFrames can be used to integrate our New Signer Experience into a third-party application.
|iFrame Best Practices|
|Fast Track||This feature 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|
|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|
|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).||Handover URLS|
|Mobile Capture||Allows you to capture a signature using a mobile device.||Capturing Signatures on Mobile Devices|
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|
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 only exception to this statement is e-Witness, which simply does not work when the New Signer Experience is on.
Remember too that you can deactivate the New Signer Experience at any time, simply by contacting our Support Team.
To access the New Signer Experience:
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:
- Account name
- Account email address
- The environment and environment URL where your account resides
- 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)
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 the New 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 Are the Supported Browsers and Devices?
The following browsers can be used with 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.|
|iOS||The latest version, plus the two previous versions.|
|Android||The latest version, plus the two previous versions.|
- 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.
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, nor is there any impact on your iFrame configurations.
|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.|
For instructions on using the New Signer Experience, click here.