February 2020 (Version 3.4)

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.