Skip to main content

SCA Using 3-D Secure

3-D Secure can be used to provide the necessary Strong Customer Authentication. You have a choice of how and when to use 3-D Secure to satisfy SCA:

Authentication Before Authorisation​

You submit payments using 3-D Secure for authentication up front so that the authorisation will be submitted to the Acquirer with the appropriate authentication data showing that SCA was sought. You may pass an exemption indicator[1] causing the Gateway to automatically request a frictionless flow[2].

Authentication After Authorisation, when requested by the Issuer (Bypass)​

You submit payments without 3-D Secure authentication but with an exemption indicator[1], if required, and the authorisation will be submitted to the Acquirer with no authentication data. If the Issuer approves the authorisation, then no further additional authentication is needed. However, if the Issuer refuses the authorisation due to SCA being required[3] then transaction can be repeated but this time using 3-D Secure[4] and no exception indicator.

The Gateway can support both choices and in the case of the second choice it can automatically perform the repeat the transaction on your behalf.

The choice of how and when authentication is performed is indicating by select a 3-D Secure Policy in the Merchant Management System or by sending the threeDSPolicy field in the request.

The policies available are:

  1. Authenticate Before Authorisation or When Issuer Requests [All Regions] (Default)
  2. Authenticate Before Authorisation Only [All Regions]
  3. Authenticate When Issuer Requests Only [All Regions] (Bypass)
  4. Authenticate Before Authorisation or When Issuer Requests [PSD2]
  5. Authenticate Before Authorisation Only [PSD2]
  6. Authenticate When Issuer Requests Only [PSD2] (Bypass)
  7. Authenticate Before Authorisation [PSD2] or When Issuer Requests [All Regions]

The [All Region] policies will perform 3-D Secure authentication regardless of the transaction’s jurisdiction.

The [PSD2] policies will perform 3-D Secure authentication only if the transaction falls within the jurisdiction of the European Union's Payment Services Directive 2, otherwise it will behave as if 3 D Secure had not been required.

[1] An exemption can be explicitly requested using the scaExemption field, refer to the Exemptions to Strong Customer Authentication section.

[2] The Gateway will use the correct ‘requestorChallengeIndicator’ unless overridden by any value passed in the request.

[3] The issuer will soft decline the transaction indicating SCA is required, refer to the SCA Soft-Declines section.

[4] You are advised to send a threeDSOptions ‘requestorChallengeIndicator’ value of 4 to mandate a challenge.

Footnotes​

  1. An exemption can be explicitly requested using the scaExemption field, refer to the Exemptions to Strong Customer Authentication section. ↩ ↩2

  2. The Gateway will use the correct ‘requestorChallengeIndicator’ unless overridden by any value passed in the request_._ ↩

  3. The issuer will soft decline the transaction indicating SCA is required, refer to the SCA Soft-Declines section. ↩

  4. You are advised to send a threeDSOptions ‘requestorChallengeIndicator’ value of 4 to mandate a challenge. ↩