3DS Method FAQ

Owned by Chris Bohatka
Aug 07, 2020
2 min read

The 3DS Method is a URL associated with an Issuer’s BIN or BIN range. The 3DS Method facilitates gathering information about the context of a transaction and must be run prior to submitting the authentication request. Information identifying the device type and location will be shared with the Issuer for use in their risk decisioning. This data helps achieve frictionless authentications more frequently, as the Issuer risk model can accurately assess when the consumer is trusted based on the current transaction context. In the event that the Issuer requests a Challenge, this device data is also used to provide the consumer with an optimal user experience by tailoring the content to the device being used (screen size, resolution, color depth, etc).

Failure to run 3DS Method may result in higher step up rates, increase in failed frictionless authentications, or downgrades to 3DS 1.0.2.

 

In order to achieve the best results on your authentication request, be sure to complete your integration of Device Data Collection based on your integration method with Cardinal. This will facilitate the running of the 3DS Method URL and ensure you are positioned for successful authentication with EMV 3DS. It is also recommended to pass as many digits of the BIN/Card Number as possible. This will ensure an exact match with the Issuer’s 3DS Method URL. Per EMV® 3DS specification, the 3DS Method may take up to 10 seconds to complete (note: running of the 3DS Method is asynchronous and transparent to the consumer). Based on this, Cardinal recommends running this as early in the checkout process as possible. This provides the highest likelihood the issuer has received the information and completed their assessment prior to proceeding with the authentication request.

For more information on this, please refer to the documentation which corresponds to your integration method. For any questions you have, please reach out to your Implementation Manager.

Additional information on 3DS Method can be found in the EMVCo EMV® 3-D Secure Protocol and Core Functions Specification. In both guides (EMV 3DS 2.1.0 and EMV 3DS 2.2.0) refer to Section 5.8.1.

 

EMV® is a registered trademark in the U.S. and other countries and an unregistered trademark elsewhere. The EMV trademark is owned by EMVCo, LLC