Every 3-D Secure integration returns the same authentication result, which follows the EMVCo ARes transaction status (TransStatus). This page is the canonical reference for those values.
Property names
The same value surfaces under a different property name depending on the integration path. They all hold the EMVCo transaction status.
| Property | Where it appears |
|---|
transaction_status | The Secure Fields 3-D Secure finish callback authentication object. |
transactionStatus | The native iOS and Android SDK tokenization result authentication object. |
authentication_response | The transaction object (three_d_secure.response_data.authentication_response) and the API. |
Transaction status values
These are the values you can receive. They are identical across every integration path, because all paths follow the same EMV 3DS specification.
| Value | Meaning |
|---|
"Y" | Authentication was successful. |
"A" | Not authenticated, but a proof of authentication attempt was generated. |
"N" | Not authenticated; the transaction was denied. |
"R" | Authentication was rejected by the issuer, which requests that authorization not be attempted. |
"U" | Authentication could not be performed because of a technical or other problem. |
null | No authentication status could be determined. This is typically only returned when an error occurred during authentication. |
"U" and null are distinct. "U" is an explicit status from the issuer or directory server indicating that authentication could not be performed, whereas null means no status value was determined at all, typically when an error occurred during authentication. A successful frictionless authentication returns "Y", not null.
C (a challenge is required), and, from version 2.2.0, D (decoupled authentication) and I (informational only). These represent in-progress states that are resolved before a final result is returned, so they aren’t surfaced as a final transaction status. 
