Unformatted total transaction amount without any decimalization.

Example: 

$100.00 = 10000, $123.67 = 12367, $.99 = 99

Indicates the type of Authentication request.

01 - Payment transaction

02 - Recurring transaction

03 - Installment transaction

04 - Add card

05 - Maintain card

06 - Cardholder verification as part of EMV token ID&V

07-79 - Reserved for EMVCo future use (values invalid until defined by EMVCo)

80-99 - Reserved for DS use

A Boolean value that represents the ability of the cardholder browser to execute Java.

Value is returned from the navigator.javaEnabled property.

Possible Values:

True

False

BrowserJavascriptEnabled

NEW FIELD

A Boolean value that represents represents the ability of the cardholder browser to execute JavaScript.

Possible Values:

True

False

Mechanism used by the cardholder to authenticate to the 3DS requester.

Possible Values:

01 - No authentication occurred (e.g. Guest Checkout)

02 - Login to the cardholder account at the Merchant system using Merchant system credentials

03 - Login to the cardholder account at the Merchant system using a Federated ID

04 - Login to the cardholder account at the Merchant system using Issuer credentials

05 - Login to the cardholder account at the Merchant system using third-party authentication

06 - Login to the cardholder account at the Merchant system using FIDO Authenticator

07-79 - Reserved for EMVCo future use (values invalid until defined by EMVCo)

80-99 - Reserved for DS use

Possible Values:

01 - No preference

02 - No challenge requested

03 - Challenge requested (3DS Requestor Preference)

04 - Challenge requested (Mandate)

05-79 - Reserved for EMVCo future use (values invalid until defined by EMVCo)

80-99 - Reserved for DS use

05 - No challenge requested (transactional risk analysis is already performed)

06 - No challenge requested (Data share only)

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

08 - No challenge requested (utilise whitelist exemption if no challenge required)

09 - Challenge requested (whitelist prompt requested if challenge required)

NOTE: This is a 2.0 required field, Cardinal will default to 01 on Merchant Configuration - can be overridden by the merchant.  EMV® 3-D Secure version 2.1.0 supports values 01-04.  Version 2.2.0 supports values 01-09.

DecoupledMaxTime

NEW FIELD

Indicates the maximum amount of time that the 3DS Requestor will wait for an ACS to provide the results of a Decoupled Authentication transaction (in minutes).

Possible Values: 

Numeric values between 1 and 10080 accepted.

NOTE:  Decoupled authentication is not supported at this time.

DecoupledIndicator

NEW FIELD

Indicates whether the 3DS Requestor requests the ACS to utilise Decoupled Authentication and agrees to utilise Decoupled Authentication if the ACS confirms its use.

Possible Values: 

Y - Decoupled Authentication is supported and preferred if challenge is necessary

N - Do not use Decoupled Authentication

Default Value: N

NOTE: If the element is not provided, the expected action is for the ACS to interpret as N, DO NOT use Decoupled Authentication.  Decoupled authentication is not supported at this time.

Indicates the type of 3RI request.

Possible Values:

01 - Recurring transaction

02 - Installment transaction

03 - Add card

04 - Maintain card

05 - Account verification

06-79 - Reserved for EMVCo future use (values invalid until defined by EMVCo)

80-99 - Reserved for DS Use

06 - Split/delayed shipment

07 - Top-up

08 - Mail Order

09 - Telephone Order

10 - Whitelist status check

11 - Other payment

NOTE:  EMV® 3-D Secure version 2.1.0 supports values 01-05.  Version 2.2.0 supports values 01-11.

Amount

Unformatted total transaction amount without any decimalization.

Example: 

$100.00 = 10000, $123.67 = 12367, $.99 = 99

NOTE: Supports 3RI Device Channel in version 2.2.0

CurrencyCode

NEW FIELD

3 digit numeric ISO 4217 currency code for the sale amount.

NOTE: Supports 3RI Device Channel in version 2.2.0

PurchaseDate

NEW FIELD

Date of original purchase. 

Format:

YYYYMMDDHHMMSS

NOTE: If not passed, Cardinal will use current date. Required for recurring transactions. 

NOTE: Supports 3RI Device Channel in version 2.2.0

Installment

NEW FIELD

Indicates the maximum number of authorizations for installment payments.

An integer value greater than 1 indicating the maximum number of permitted authorizations for installment payments.

Example values accepted:
• 2
• 02
• 002

NOTE: Supports 3RI Device Channel in version 2.2.0

RecurringEnd

NEW FIELD

The date after which no further recurring authorizations should be performed.

Format:

YYYYMMDD

NOTE: Supports 3RI Device Channel in version 2.2.0

RecurringFrequency

NEW FIELD

Integer value indicating the minimum number of days between recurring authorizations. A frequency of monthly is indicated by the value 28. Multiple of 28 days will be used to indicate months.

Example:

6 months = 168

Example values accepted (31 days):
• 31
• 031
• 0031

NOTE: Supports 3RI Device Channel in version 2.2.0

ProductCode

NEW FIELD

Merchant product code.

Possible Values:

PHY - Goods/Service Purchase

CHA - Check Acceptance

ACF - Account Funding

QCT - Quasi-Cash Transaction 

PAL - Prepaid Activation and Load

NOTE:  Supports 3RI Device Channel in version 2.2.0

WhiteListStatus

NEW FIELD

Enables the communication of trusted beneficiary/whitelist status between the ACS, the DS and the 3DS Requestor.

Possible Values: 

Y - 3DS Requestor is whitelisted by cardholder

N - 3DS Requestor is not whitelisted by cardholder

Indicates the maximum number of authorizations for installment payments.

An integer value greater than 1 indicating the maximum number of permitted authorizations for installment payments.

Example values accepted:
• 2
• 02
• 002

Integer value indicating the minimum number of days between recurring authorizations. A frequency of monthly is indicated by the value 28. Multiple of 28 days will be used to indicate months.

Example:

6 months = 168

Example values accepted (31 days):
• 31
• 031
• 0031

This field contains the 3DS version that was used to process the transaction.

Possible Values:

1.0.2

2.1.0

2.2.0

NOTE: Required for Mastercard Identity Check transactions in Authorization

Transactions status result identifier.

Possible Values:

Y - Successful Authentication

N - Failed Authentication / Account Not Verified / Transaction Denied

U - Unable to Complete Authentication 

A - Successful Attempts Transaction 

C - Challenge Required for Authentication

R - Authentication Rejected (Merchant must not submit for authorization)

D - Challenge Required; Decoupled Authentication confirmed.

NOTE: Statuses of C and R only apply to Consumer Authentication 2.0.  Decoupled authentication is not supported at this time.

DecoupledIndicator

NEW FIELD

Indicates whether the ACS confirms utilisation of Decoupled Authentication and agrees to utilise Decoupled Authentication to authenticate the Cardholder.

Possible Values:

Y - Confirms Decoupled Authentication will be utilised

N - Decoupled Authentication will not be utilised

NOTE: 

If 3DS Requestor Decoupled Request Indicator = N, a value of Y cannot be returned in the ACS Decoupled Confirmation Indicator.

If Transaction Status = D, a value of N is not valid.  Decoupled authentication is not supported at this time.

WhiteListStatus

NEW FIELD

Enables the communication of trusted beneficiary/whitelist status between the ACS, the DS and the 3DS Requestor.

Possible Values: 

Y - 3DS Requestor is whitelisted by cardholder

N - 3DS Requestor is not whitelisted by cardholder

E - Not eligible as determined by issuer

P - Pending confirmation by cardholder

R - Cardholder rejected

U - Whitelist status unknown, unavailable, or does not apply

WhiteListStatusSource

NEW FIELD

This data element will be populated by the system setting Whitelist Status.

Possible Values:

01 - 3DS Server

02 - DS

03 - ACS

N(2)

Additional text provided by the Issuing Bank to the Cardholder during a Frictionless transaction and was not authenticated by the ACS.  The Issuing Bank can optionally support this value. 

Text provided by the ACS/Issuer to Cardholder during a Frictionless or Decoupled transaction.

The Issuer can provide information to Cardholder. For example, “Additional authentication is needed for this transaction, please contact (Issuer Name) at xxx-xxx-xxxx.”. 

The Issuing Bank can optionally support this value. 

NOTE:  Supports 3RI Device Channel in version 2.2.0.  Decoupled authentication is not supported at this time.

3DS 2.0

Required if ACS Decoupled Confirmation Indicator = Y Otherwise, Optional for the ACS.

Identifies the UI Type the ACS will use to complete the challenge. 

NOTE: Only available for App transactions using the Cardinal Mobile SDK and is optional for an Issuer to return.

Merchant Configuration ON & App

Indicates the type of authentication that will be used to challenge the card holder. 

Possible Values:

01 - Static

02 - Dynamic 

03 - OOB (Out of Band)

04-79 - Reserved for EMVCo future use (values invalid until defined by EMVCo

80-99 - Reserved for DS use

04 - Decoupled

NOTE:  EMV® 3-D Secure version 2.1.0 supports values 01-03.  Version 2.2.0 supports values 01-04.  Decoupled authentication is not supported at this time.

Merchant Configuration ON

Required in the ARes message if the Transaction Status = C or D in the ARes message.

Indicates whether a challenge is required to complete authentication. For example, regional mandates.

Possible Values:

Y - Challenge Required

N - Challenge Not Required

NOTE:  Supports 3RI Device Channel in version 2.2.0.  Decoupled authentication is not supported at this time.

Merchant Configuration ON

Required if Transaction Status = C or D.

Provides additional information as to why the PAResStatus has the specific value. 

NOTE: Required for Payment (e.g. Authentication Indicator equals 01 on Lookup Request) transactions when PAResStatus is equal to N, U, or R in the Lookup Response.  Please refer to "EMV 3-D Secure Protocol and Core Functions Specification v2.2.0" for a list of Reason Codes.