Refusal related to authentication
The red exclamation mark to the left of the 3D Secure tab indicates that the reason for rejection is related to cardholder authentication.
Only the buyer's browser interacts with the banks' authentication servers.
Example
- Error details: 39: 3D Secure refused for the transaction.
You can click on “Reason for refusal: Authentication” for more details on the refusal reason via the 3D Secure tab.
Here is a list of reasons and a description of the most frequently occurring codes.
| Value | Description |
|---|---|
| 39 | 3D Secure refused for the transaction This code corresponds to an incorrectly specified authentication code. |
| 149 | The payment session has expired Here are some of the possible causes:
|
| 205 | 3D Secure - cannot reach DS or ACS. The authentication servers (DS/ACS) are unavailable and the buyer is unable to authenticate. |
| 206 | 3D Secure - A technical error occurred during the process. This type of error can occur when the buyer performs the transaction using a cell phone with insufficient memory. The transaction fails during the authentication phase and the ACS shows an error message visible via the 3D Secure tab, in the authentication details. Example: “Error received from the ACS: TRANSACTION_DATA_NOT_VALID”
|
| 207 | Refusal of the authentication by the issuer (Transaction not allowed for this cardholder) This error appears when the authentication servers (ACS) reject the authentication.The buyer must ask their bank if the card used for the payment allows payments with 3DS2 authentication and/or payments via an e-commerce website. Status reason: “12-Transaction not allowed for this cardholder”
|
For more details on authentication results, see the guide dedicated to transaction management.
Remember to make sure that the buyer has not made another successful payment attempt with another payment method. Simply check the Multiple attempts tab.