Release notes
August 2021
This release supports the following features:
3D Secure 2 now available also for merchants who do not process their payment with Elavon
Even merchants who do not process their payment with Elavon can also use the 3D Secure 2 solution by Elavon now. Such merchants will be registered as service provider merchants. After the registration is complete, they can use the 3D Secure solution just like merchants who process their payments with Elavon.
Message extension elements for the travel industry
Partners and merchants who operate in the travel industry can send travel-related data such as air, car rental, hotel, and travelers to the issuer (ACS) in the
/authenticaterequest. The issuer uses this data in risk-decisioning and determining the appropriate authentication response that it will send to the merchant.Token expiry timestamp
The
/tokenresponse returns a new field:validTo. This field value indicates the exact time of token expiry in the UTC format. Review the authentication page for more details.Web SDK
Install the latest version of Web SDK.
New features in the Web SDK version 1.0.5
- Supports the ‘service provider fields’ in the authenticate request for merchants who do not process their payment with Elavon. For details on these fields, see the 3D Secure 2 authenticate sample request in either the all-in-one workflow or the toolkit workflow
- Supports travel industry data in the
messageExtensionelement of the/authenticaterequest. - Error messages return all fields that were wrong in the corresponding request message.
- Accepts
acctInfoobject and its fields in the authenticate request
Bug fixes in the Web SDK
threeDSServerTransIDis now an optional field to send an authenticate request.
Web SDK demo application
The Web SDK demo application helps you to test all the functionalities that the Web SDK supports. You can now download the Web SDK demo application from the developer portal. Use the demo credentials listed on Web SDK demo app page to send requests and responses in a test environment.
June 2021 (Documentation update only)
To receive authentication credentials that you would need to test the different integration options in the sandbox environment, fill in the information requested in this form.
3D Secure 2 test credentials request formopen_in_newLink opens new window
We will send you the credentials by the next business day. We will also send contact details to whom you can reach out for any assistance required during the integration and testing process.
February 2021
The first release of the 3D Secure 2.0 solution by Elavon. This release supports the following features:
Available integration options
Two integration options are supported in this release: integrate directly to the 3DS Server or use the Web SDK for integration to the 3DS Server.
Auto-fallback to 3D Secure 1
When the issuer or the card used for the transaction does not support 3D Secure 2, the transaction falls back to 3D Secure 1. Review the Fallback to 3DS 1 page to understand when a transaction will fall back to 3DS 1 and the integration steps.
Test environment to test different authentication scenarios
Use the test environment to test the authentication scenarios supported by 3D Secure 2. Use the test card numbers to test these scenarios. To test the Web SDK, use the test card numbers to generate different authentication scenarios.
Elavon’s 3D Secure 2 solution supports 3D Secure 2.1 authentication for Mastercard, Visa, American Express, and Diners card schemes. Review the Getting started page for a brief overview of 3D Secure 2.1 and the different authentication flows supported.