What does it mean if a payment is refused because of 3D Not Authenticated?

For 3D Secure 2 transactions that are refused because of 3D Not Authenticated (3d-secure 2: Authentication failed) you can find more insights about why the transactions failed with the threeDSRReqTransStatusReason, which can be found in the Customer Area under the 3DS tab: 
mceclip0.png
The threeDSRReqTransStatusReason can be used to determine if the root cause of the refusal might be an integration issue, in which case we recommend to replicate the issue and modify your integration, or a valid reason from the issuing bank, in which case the shopper can reach out to the bank or attempt the payment with a different payment method.

 

For 3D Secure 1, we don't have further insights in why transactions are refused because of 3D Not Authenticated (3d-secure: Authentication failed). When this error message is displayed, it most likely means the shopper failed the authentication (probably input the wrong password/code). 

In those cases, we can see in the Customer Area: 

mceclip0.png

- the Raw acquirer response is 3d-secure: Authentication failed

- 3D offered is Y - more information about the meaning can be found here

- 3D authenticated is - more information about the meaning can be found here

 

This transaction was refused but for future transactions, you can recommend the shopper to verify the password or code they input to complete the authentication. 

Was this article helpful?
14 out of 97 found this helpful