Getting Started with ADX
Get an overview of ADX or check out the specifications.
Overview
The Authentication Data Exchange (ADX) API is used to send the authentication result of a transaction from Visa Consumer Authentication Service (VCAS) to a 3rd party; i.e. an issuer or processor. This authentication result can be used (but is not limited to) to help authorization decisioning, for case management systems, or for additional data for risk modeling.
There are two main calls in ADX, SendAuthenticationResult or SendAuthenticationResultDetail:
NOTE: When transaction data for specific fields is not available, those fields will not be present in the ADX response. The Authentication Responses table below outlines the available authentication response values resulting from the VCAS ADX request.
Data Validation
Cardinal strives to continually add new data points to the ADX specification to fit the needs of our customers. With that in mind, we ask that any fields not in use are ignored and not validated. This will allow flexibility in adding data points in the future and will help our customers to integrate those new data points when they are ready.
Risk Indicator Values
The RiskIndicator value is set during risk or challenge flows to indicate the risk level or challenge type. The value is then used in the construction of certain Authentication Values (AV). For example, CAVV Usage 3 Version 0 & CAVV Usage 3 Version 7 allows for this value to be passed within the AV value that is sent to the network’s Directory Server (DS).
Authentication Responses
3DS Version | SendADXOnAnyStatus | transStatus in RReq |
---|---|---|
EMV 3DS 2.x.x | True | Y, N, U, R, I |
EMV 3DS 2.x.x | False | Y |
Note:
Contact your client or integration manager to enable this feature.
Updated 6 months ago