3D Secure 2.0 status codes provide the results from the 3D Secure authenticated transactions. You can use 3D Secure 2.0 to increase your confidence in your online processing.
How do I find my 3D Secure 2.0 transaction report?
1. Log in to the Portal. Navigate to Reporting/Analysis > Transaction Report. You can review how to review the Transaction Details here.
3D Secure 2.0 responses will return one of the following status codes to indicate if 3DS authentication was successful.
|
Status |
Description |
Merchant Recommended Action |
Liability Shift |
Authentication Required: False |
Authentication Required: True |
|
Success |
Authentication was successful |
Continue with transaction processing |
Yes |
Transaction Processes |
Transaction Processes |
|
Attempted |
Authentication was attempted but could not be completed |
Continue with transaction processing |
Yes |
Transaction Processes |
Transaction Processes |
|
Rejected |
Rejected by issuing bank |
Do not proceed with the transaction. Notify the card holder to contact their card issuer. |
No |
Transaction declined message 311 |
Transaction declined message 311 |
|
Failed |
Failed to authenticate card holder |
Do not proceed with the transaction. Notify the card holder to contact their card issuer. |
No |
Transaction declined message 311 |
Transaction declined message 311 |
|
Unavailable |
The 3DS service is available due to technical issues |
If you continue with the transaction there will be no liability shift and there will be risk of chargeback. |
No |
Transaction Processes |
Transaction declined message 311 |
|
Error |
Authentication failed due to an internal error |
If you continue with the transaction there will be no liability shift and there will be risk of chargeback. |
No |
Transaction Processes |
Transaction declined message 311 |
2. There is a new optional parameter '3DsecureAuthRequired' which defaults to false. If 3DsecureAuthRequired is set to true, the transaction will not continue processing unless 3DS authentication is successful.
Good to know:
- Depending on your integration method, you may need to pass in new parameters related to the client browser.
- In the case of a challenge flow, the naming of the parameters in the redirection will be changing, but their contents and usage will remain the same.