The payment gateway supports the transmission of authentication fields for the following cardholder authentication programs:
Merchants using a third party cardholder authentication solution can submit the following authentication values with Visa and/or MasterCard transactions.
Note: The cardholder authentication fields are currently supported only through the Chase Paymentech, FDMS Nashville, Global Payments and TSYS processors for Visa and MasterCard transactions. If cardholder authentication information is submitted for transactions processed through any other processor, it will be ignored.
Fields are name/value pairs with the syntax of:
x_name_of_field = value of the field&.
|
FIELD NAME |
REQUIRED? |
VALUE |
FORMAT |
NOTES |
|
x_authentication_ indicator |
Optional |
The electronic commerce indicator (ECI) value for a Visa transaction; or the universal cardholder authentication field indicator (UCAF) for a MasterCard transaction obtained by the merchant after the authentication process. |
Please note that special characters included in this value must be URL encoded. |
Required only for AUTH_ONLY and AUTH_CAPTURE transactions processed through cardholder authentication programs. When submitted with other transaction types, this value is ignored.
This field is currently supported through Chase Paymentech, FDMS Nashville, Global Payments and TSYS. |
|
x_cardholder_ authentication_value |
Optional |
The cardholder authentication verification value (CAVV) for a Visa transaction; or accountholder authentication value (AVV)/ universal cardholder authentication field (UCAF) for a MasterCard transaction obtained by the merchant after the authentication process. |
Please note that special characters included in this value must be URL encoded. |
Required only for AUTH_ONLY and AUTH_CAPTURE transactions processed through cardholder authentication programs. When submitted with other transaction types, this value is ignored.
This field is currently supported through Chase Paymentech, FDMS Nashville, Global Payments and TSYS. |
Please note that invalid combinations of the x_authentication_indicator and x_cardholder_authentication_value fields will cause the transaction to error.
Valid value combinations for these fields are as follows:
Visa
|
AUTHENTICATION INDICATOR |
CARDHOLDER AUTHENTICATION VALUE |
|
5 |
Not null |
|
6 |
Not null |
|
6 |
Null/Blank |
|
7 |
Null/Blank |
|
7 |
Not null (some international issuers may provide a CAVV value when ECI is 7) |
|
Null/Blank |
Null/Blank |
MasterCard
|
AUTHENTICATION INDICATOR |
CARDHOLDER AUTHENTICATION VALUE |
|
0 |
Blank /Null |
|
2 |
Not null |
|
1 |
Null |
|
Null |
Null |
For example, when the MasterCard value for x_authentication_indicator is “1,” the value for x_cardholder_authentication_value must be null. In this scenario, if a value is submitted for x_cardholder_authentication_value, the transaction fails validation and is rejected.
The authentication verification value returned by Visa or MasterCard is included in the transaction response from the payment gateway and is also included on the Transaction Detail page for the transaction in the Merchant Interface.