Verifone · Schema
ThreedAuthentication
ThreedAuthentication from Verifone eCommerce API
PaymentsPOSTerminal ManagementeCommerceFinTechPayment ProcessingOmnichannel
Properties
| Name | Type | Description |
|---|---|---|
| eci_flag | string | Electronic Commerce Indicator (ECI). The ECI value is part of the 2 data elements that indicate the transaction was processed electronically.This should be passed on the authorization transaction to t |
| enrolled | string | The enrolment response status of Authentication eligibility from the Directory Server. Possible Values: * `Y` - Yes, Bank is participating in 3-D Secure protocol and will return the ACSUrl. * `N` - No |
| cavv | string | Cardholder Authentication Verification Value (CAVV). Base64-encoded values of 28 or 32 characters. Hex-encoded values of 40 or 48 characters. |
| cavv_algorithm | string | The algorithm used to generate the CAVV value. Supported for 3D Secure v1 only. |
| pares_status | string | Authentication response code. Possible Values: * `Y` - Successful Authentication. * `N` - Failed Authentication. * `U` - Unable to Complete Authentication * `A` - Successful Attempts Transaction. * `C |
| xid | string | The transaction identifier assigned by Directory Server. Supported for 3D Secure v1 only. |
| threeds_version | string | The 3DS version used to process the transaction. |
| ds_transaction_id | string | The unique transaction identifier assigned by the Directory Server. Supported for 3D Secure v2 only. |
JSON Schema
{
"$schema": "http://json-schema.org/draft-07/schema#",
"$id": "https://raw.githubusercontent.com/api-evangelist/verifone/refs/heads/main/json-schema/ecommerce-api-threedauthentication.json",
"title": "ThreedAuthentication",
"description": "ThreedAuthentication from Verifone eCommerce API",
"type": "object",
"properties": {
"eci_flag": {
"type": "string",
"description": "Electronic Commerce Indicator (ECI). The ECI value is part of the 2 data elements that indicate the transaction was processed electronically.This should be passed on the authorization transaction to the Gateway/Processor.Please refer to the integration guide for information on its usage.",
"enum": [
"05",
"06",
"07",
"02",
"01",
"00"
]
},
"enrolled": {
"type": "string",
"enum": [
"Y",
"N",
"U",
"B"
],
"description": "The enrolment response status of Authentication eligibility from the Directory Server.\n\nPossible Values:\n\n * `Y` - Yes, Bank is participating in 3-D Secure protocol and will return the ACSUrl.\n\n * `N` - No, Bank is not participating in 3-D Secure protocol.\n\n * `U` - Unavailable, the DS or ACS is not available for authentication at the time of the request.\n\n * `B` - Bypass, merchant authentication rule is triggered to bypass authentication in this use case.\n\nNOTE: If the Enrolled value is NOT Y, then the Consumer is NOT eligible for Authentication."
},
"cavv": {
"type": "string",
"minLength": 28,
"maxLength": 48,
"description": "Cardholder Authentication Verification Value (CAVV). Base64-encoded values of 28 or 32 characters. Hex-encoded values of 40 or 48 characters."
},
"cavv_algorithm": {
"type": "string",
"description": "The algorithm used to generate the CAVV value. Supported for 3D Secure v1 only."
},
"pares_status": {
"type": "string",
"enum": [
"Y",
"N",
"U",
"A",
"C",
"R"
],
"description": "Authentication response code.\n\nPossible Values:\n\n * `Y` - Successful Authentication.\n\n * `N` - Failed Authentication.\n\n * `U` - Unable to Complete Authentication\n\n * `A` - Successful Attempts Transaction.\n\n * `C` - Challenge Required for Authentication.\n\n * `R` - Authentication Rejected."
},
"xid": {
"type": "string",
"description": "The transaction identifier assigned by Directory Server. Supported for 3D Secure v1 only."
},
"threeds_version": {
"type": "string",
"enum": [
"1.0.2",
"2.1.0",
"2.2.0"
],
"description": "The 3DS version used to process the transaction."
},
"ds_transaction_id": {
"type": "string",
"description": "The unique transaction identifier assigned by the Directory Server. Supported for 3D Secure v2 only."
}
}
}