Introduction

In response to a payment or authorization request, the issuer returns a 3DS authentication result, and if applicable the relevant 3DS challenge or exemption with its reason.

The threeD Class

The paymentOption.card.threeD class contains the 3D-Secure response parameters returned from the issuer at different stages of the 3D-Secure payment flow and the 3D-Secure authorization flow (which is not necessarily followed by a payment transaction).

The threeD class contains a different parameter set depending on the stage in the flow:

• First Call – 3D-Secure Response Parameters:
  This threeD class is included in the response to the following requests:
  • For REST:
    In the response to the first /payment (or /authorize3d) request requiring a challenge.
  • For Web SDK and Simply Connect:
    In the response to the /openOrder API request, which is used to authenticate your Nuvei merchant credentials.
  For more details see the First Call 3D-Secure Response Parameters section under the threeD Output Class topic.
• Final Call – 3D-Secure Response Parameters:
  This threeD class is included in the response to the following requests:
  • After a successful frictionless /payment request (either first or second).
  • After the challenge, in the response to the final /payment request.
  For more details see the Final Call 3D-Secure Response Parameters section under the threeD Output Class topic.

3DS Response

In response to a payment or authorization request, the issuer returns a 3DS authentication result, and if applicable the relevant 3DS challenge or exemption with its reason.

• Challenge / Exemption Reasons

  Follow the link (above) for a description of the challengePreferenceReason…

• Failed 3DS Authorization Reason

  If the 3DS authentication failed then the threeDReasonId and threeDReason parameters are returned by the issuer, which describes the reason for a failure:

  threeDReasonId	threeDReason
  01	Card Authentication Failed
  02	Unknown Device
  03	Unsupported Device
  04	Exceeds authentication Frequency Limit
  05	Expired Card
  06	Invalid Card Number
  07	Invalid Transaction
  08	No Card Record
  09	Security Failure
  10	Stolen Card
  11	Suspected Fraud
  12	Transaction Not Permitted to Cardholder
  13	Cardholder not enrolled in service
  14	Transaction timed out at the ACS
  15	Low confidence
  16	Medium Confidence
  17	High Confidence
  18	Very High Confidence
  19	ACS Maximum Challenges
  20	Non-Payment transactions not Supported
  21	3RI transaction not supported Effective 1 September 2019, Reason Code not Allowed
  22	ACS technical issue
  23	Decoupled Authentication Required by ACS but not requested by 3DS Requestor
  24	3DS Requestor Decoupled Max Expiry Time Exceeded
  25	Decoupled Authentication was provided insufficient time to authenticate cardholder.
  26	Authentication attempted but not performed by the cardholder
  81	MC – Exemption request accepted | VISA – ACS Timed Out
  82	VISA – Invalid Response from ACS
  83	VISA – System Error Response from ACS
  84	VISA – Internal Error While Generating CAVV
  85	VISA – VMID not eligible for requested program
  86	VISA – Protocol Version Not Supported by ACS
  87	VISA – Transaction is excluded from Attempts Processing (includes non-reloadable pre-paid cards)
  88	VISA – Requested program not supported by the ACS