Card input errors
| Result Code |
Result Message |
More information |
Test amount |
| 105101 |
Invalid card number |
The card number given doesn’t match the real number of the card |
333.14 |
| 105102 |
Invalid cardholder name |
The card holder name given doesn’t match the real owner of the card |
|
| 105103 |
Invalid PIN code |
The Personal Identification Number code is invalid. The user should check card information and retry. |
333.55 |
| 105104 |
Invalid PIN format |
The Personal Identification Number format is invalid. The user should check card information and retry |
|
SecureMode / 3DSecure errors
| Result Code |
Result Message |
More information |
| 101399 |
SecureMode: 3DSecure authentication is not available |
3DSecure is not available. Please contact our support to unblock the situation. |
| 101304 |
SecureMode: The 3DSecure authentication session has expired |
|
| 101303 |
SecureMode: The card is not compatible with 3DSecure |
|
| 101302 |
SecureMode: The card is not enrolled with 3DSecure |
|
| 101301 |
SecureMode: 3DSecure authentication has failed |
|
| 101305 |
SecureMode: Soft decline |
Strong customer authentication is required in order to be able to proceed to payment |
| 101306 |
SecureMode: 3DSecure authentication requested |
|
Tokenization / Card registration errors
| Result Code |
Result Message |
More information |
| 001599 |
Token processing error |
The token has not been created as there was a problem - check that you sent all the correct parameters. |
| 105299 |
Token input Error |
This is a generic error meaning that we got an error when submitting the token to the bank. It is usually returned because there was a too long time between the card registration request and the first action done with this card. Indeed, you have 20min maximum to create the first Pre-auth or Payin |
| 105202 |
Card number: invalid format |
This error is returned in case the card number formate is wrong (on card registration) |
| 105203 |
Expiry date: missing or invalid format |
This error is returned in case the expiry date is wrong (on card registration) |
| 105204 |
CVV: missing or invalid format |
This error is returned in case the CVV is wrong (on card registration) |
| 105205 |
Callback URL: Invalid format |
This error is returned in case the ReturnURL is wrong on CardRegistration process |
| 105206 |
Registration data : Invalid format |
This error is returned in case the data sent to the tokenization server is not the right. You can get this error when you are trying to edit the CardRegistration Object with the RegistrationData(got from the tokenization server) |
The following errors may be received by our PSP when POSTing the card data to the CardRegistrationURL
| Result Code |
Result Message |
More information |
Test amount |
| 02625 |
Invalid card number |
|
|
| 02626 |
Invalid date. Use MMYY format |
|
|
| 02627 |
Invalid CCV number |
|
|
| 02628 |
Transaction refused |
Invalid URL return field |
|
| 02101 |
Internal Error |
There is an issue on the tokenization server (PSP side). Please check the resolution on http://status.mangopay.com/ |
|
| 02632 |
Method GET is not allowed |
Your Payment form has to use POST method on Tokenization Server |
|
| 09101 |
Username/Password is incorrect |
Please ensure that you are sending the right registration data. |
|
| 09102 |
Account is locked or inactive |
|
|
| 01902 |
This card is not active |
|
333.12 |
| 02624 |
Card expired |
|
333.33 |
| 09104 |
Client certificate is disabled |
|
|
| 09201 |
You do not have permissions to make this API call |
|
|
| 02631 |
Delay exceeded |
Too much time taken from the creation of the CardRegistration object to the submission of the Card Details on the Tokenizer Server |
|
Specific JS Kit card registration errors
| Result Code |
Result Message |
More information |
Test amount |
| 009999 |
Browser does not support making cross-origin Ajax calls |
|
333.57 |
| 001596 |
An HTTP request was blocked by the User's antivirus |
Getting the token from Payline failed due to the HTTP call being blocked by an anti-virus/plugin/extension - for example, this is known to happen with Kaspersky if the "Safe Money" option is activated |
|
| 001597 |
An HTTP request failed |
|
|
| 001598 |
A cross-origin HTTP request failed |
|
|
| 001599 |
Token processing error |
Getting the token from Payline failed as no token data was received - most likely, the HTTP call failed for some reason - a timeout or anti-virus/plugin/extension may have blocked it |
|
| 101699 |
CardRegistration should return a valid JSON response |
Finishing card registration with MANGOPAY API failed as a valid JSON response wasn't received for some reason |
|
| 105204 |
CVV_FORMAT_ERROR |
The CVV is missing or not the required the length |
|
| 105203 |
PAST_EXPIRY_DATE_ERROR or EXPIRY_DATE_FORMAT_ERROR |
The expiry date is not in the future |
|
| 105202 |
CARD_NUMBER_FORMAT_ERROR |
The card number is not a valid format |
|
