3DS Response
3DS response fields and their values/meanings
This section provides an overview of the 3DS response fields and their associated values/meanings.
There is also a translation of the TxShield response to 3DS1 naming conventions (TxShield response matches naming conventions of 3DS2).
Example Response
transStatus
The values in the transStatus field along with the eci field indicate whether a liability shift has occurred. If the value is Y, U, A you can attempt the authorisation (payment) transaction. If the value is N, C, R we recommend not attempting the authorisation transaction, however, it is at the merchant's discretion if they wish to proceed.
Only a status of Y guarantees a full liability shift.
A transStatus of C should only be returned by the 3DS SDK if challenges are turned off. This turns the 3DS SDK into a frictionless workflow. If you receive a transStatus of C the frictionless transaction has not been authenticated. The ACS server (the card issuer) requested the Challenge workflow, and in a forced frictionless scenario this means the authentication has failed. You should not proceed to payment. The 3DS SDK returns the transStatus of C so that the merchant can keep statistics and track how many potential authentications failed because the ACS requested a challenge. You can use this information to make a more informed decision as to whether you turn challenges on, or keep them turned off.
transStatusReason
The values in the transStatusReason field can be mapped to the below meanings. The full text should already be in the msg field in the response data so you don't need to map this yourself.
TxShield (3DS2) fields to 3DS1 translation
Last updated