Ch 19 (08/22/2019 Update): Added Visa Delegated Authentication narrative and fields to Lookup Request Response

***Changes made on 08/22/2019 are delineated below in Red.***

Added Visa Delegated Authentication narrative and fields

Visa Delegated Authentication - Request - Conditionally Required

The PSD2 regulation allows an Issuer to ‘delegate authority’ for authentication to a third-party (e.g. wallet provider, merchant). The Visa Delegated Authentication (VDA) program enables clients and third-parties to choose to allow Visa to manage this delegation process.  CardinalCommerce fully endorses participation in the VDA program but only supports the 2.2 protocol. Merchants must be eligible to participate in Visa Delegated Authentication program rules, so please be sure to consult your Cardinal Activation Manager. Minimum requirements will require a Visa Merchant Id provisioned by Visa in order to participate.

Field Name
Description
Required
Condition
Field Definition
ChallengeIndicator

Indicates whether a challenge is requested for this transaction.

Possible Values:

07 - No challenge requested (strong consumer authentication is already performed)

CRequired for Visa Delegated Authentication N(2)
AlternateAuthenticationData

Data that documents and supports a specific authentication process.

Possible Values:

  • 01 = Static passcode
  • 02 = SMS OTP
  • 03 = Key fob or EMV card reader OTP
  • 04 = App OTP
  • 05 = OTP other
  • 06 = KBA
  • 07 = OOB biometrics
  • 08 = OOB login
  • 09 = OOB other
  • 10 = Other
  • 11 = Push confirmation
CRequired for Visa Delegated AuthenticationAN(2048)
AlternateAuthenticationMethod

Mechanism used by the cardholder to authenticate to the 3DS Requestor

Possible Values:

• 01 = No 3DS Requestor authentication occurred (i.e. cardholder “logged in” as guest)
• 02 = Login to the cardholder account at the 3DS Requestor system using 3DS Requestor’s own credentials
• 03 = Login to the cardholder account at the 3DS Requestor system using federated ID
• 04 = Login to the cardholder account at the 3DS Requestor system using Issuer credentials
• 05 = Login to the cardholder account at the 3DS Requestor system using third-party authentication
• 06 = Login to the cardholder account at the 3DS Requestor system using FIDO Authenticator
• 07 = Login to the cardholder account at the 3DS Requestor system using FIDO Authenticator (FIDO assurance data signed)
• 08 = Assurance data

CRequired for Visa Delegated AuthenticationN(2)

AlternateAuthenticationDate

Date and time in UTC of the customer authenticationCRequired for Visa Delegated AuthenticationN(12)