101301
Error message | SecureMode: 3DSecure authentication has failed |
---|---|
Description | The 3DSecure authentication has failed. |
Categories | 3DSecure Pay-in Card |
Causes
This error may occur when:
- Disruptions on the ACS servers (strong authentication servers of the card issuing bank) are encountered.
- The end user is blocked by the bank after several failed strong authentication attempts.
- The end user leaves the 3DS page (which, as a result, expires).
- The end user clicks on a “cancel” button.
- The bank blocks the payment.
- The end user fails to strongly authenticate with their bank application.
What to do
In such cases, end users can:
- Contact their bank to have more information.
- Try again later and/or with another payment method.
Example
Please find below an example of direct card pay-in which has failed due to disruptions on the ACS server.
API Response
Testing
To reproduce this error, you can:
-
Register one of our testing cards (challenge flow) available in our testing payments documentation.
-
Make a direct card pay-in with this card (using POST Create a Direct Card PayIn).
Request example
- Upon clicking on the
SecureModeRedirectURL
, you’re redirected to a page providing multiple scenarios for 3DS authentication. Select No, Rejected, or Unavailable for the pay-in to fail with the 101301 error.
Upon viewing your pay-in (GET View a PayIn (Direct Card) endpoint), you will see that the error 101301 is returned in the ResultCode
parameter.
Response example
Was this page helpful?