Visa Delegated Authentication Conditional Lookup Fields

Owned by Chris Bohatka
Last updated: Jun 29, 2022 by Suyash Somani
2 min read

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

Condition

Field Definition

Field Name

Description

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)

Required for Visa Delegated Authentication 

N(2)

AlternateAuthenticationData

Data that documents and supports a specific authentication process that was sent in the AlternateAuthenticationMethod field.

For example, if the 3DS Requestor Authentication Method is:

  • 03, then this element can carry information about the provider of the federated ID and related information.

  • 06, then this element can carry the FIDO attestation data (including the signature).

  • 07, then this element can carry FIDO Attestation data with the FIDO assurance data signed.

  • 08, then this element can carry the SRC assurance data.

Required for Visa Delegated Authentication

AN(20000)

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

Required for Visa Delegated Authentication

N(2)

AlternateAuthenticationDate

Date and time in UTC of the customer authentication

Required for Visa Delegated Authentication

N(12)