Error Handling
If a request to the SlimPay API fails or wasn’t accepted by the server, the type of error encountered will be indicated by an HTTP status code. This JSON-encoded message body also includes a human-readable message about what went wrong.
{
"code": XXX,
"message": "Some message to explain what our server thinks you did wrong."
}A 200 or 201 code indicates the request was successful and you can proceed with further API calls.
A 4xx code indicates there was a problem with the request that was sent, and should only happen during your development/testing phase. Common errors include 400 Bad Request, 401 Unauthorized, 403 Forbidden and 404 Not Found.
A 5xx code indicates an issue with the SlimPay server, such as 500 Internal Server Error and 503 Service Unavailable.
Please note: in the event of a 504 Gateway Timeout error, we advise you to verify the state of your payment using the API (get-payment) or the Dashboard before retrying the transaction. It's very likely the payment has actually been processed.
You can find a comprehensive list of all HTTP status codes here.
Different error codes are returned for different flow scenarios:
- Synchronous errors: returned by the API in response to an HTTP request which can't be fulfilled
- Order errors: a property of the order representation following a failed attempt during the Checkout
- Payment errors: a rejected, returned, reversed or refunded payment
Please note: the descriptions below don’t always match the specific error message of the response body.
Synchronous errors
| Code | Message |
|---|---|
| 100 | Internal error |
| 101 | Incomplete data |
| 102 | Request type missing |
| 103 | The merchant authentication has failed |
| 104 | Unknown merchant site |
| 105 | Incoherent timestamp |
| 108 | No customer |
| 109 | No login |
| 111 | Session timeout |
| 122 | Invalid honorificPrefix property |
| 123 | Invalid givenName property |
| 124 | Invalid familyName property |
| 125 | Invalid email property |
| 127 | Invalid telephone property |
| 128 | Invalid postalCode property |
| 129 | Invalid city property |
| 133 | Invalid bic property |
| 134 | Invalid iban property |
| 135 | Invalid rum property |
| 136 | Invalid debit amount |
| 137 | Invalid direct debit execution date |
| 138 | Invalid direct debit label |
| 139 | Invalid card amount |
| 140 | Invalid card operation type |
| 141 | Invalid subscriber reference property |
| 142 | Invalid companyName property |
| 143 | Invalid organizationId property |
| 144 | Invalid address1 property |
| 145 | Invalid address2 property |
| 146 | Invalid country property |
| 147 | Invalid transaction ID |
| 148 | Not SEPA account |
| 150 | The client has aborted or cancelled the order |
| 156 | Wrong OTP |
| 157 | Expired OTP key |
| 158 | Max OTP key try reached |
| 159 | Incoherent mandate reference |
| 160 | Max OTP key send reached |
| 161 | Invalid CSI |
| 162 | Invalid OTP channel type |
| 163 | Invalid sequence type |
| 167 | Invalid mandate signed date |
| 168 | Invalid mandate source |
| 177 | The bank account is not in the SEPA zone |
| 179 | Invalid creditor |
| 180 | Duplicate mandate reference |
| 181 | No documents to sign |
| 183 | Document already treated |
| 185 | Missing frequency |
| 186 | Forbidden IBAN |
| 187 | Document template not found |
| 188 | Invalid account owner |
| 191 | Invalid dateSigned property (must be present and in the past) |
| 193 | IP or IBAN or phone number is forbidden |
| 196 | No payment scheme in the request and SlimPay cannot compute the default one according to the client configuration |
| 198 | Duplicate subscriber reference |
| 199 | Debtor mandate not found |
| 200 | Debtor's data are unavailable |
| 201 | The mandate signature has failed |
| 202 | The code entered during the signature is invalid |
| 205 | Client data are inconsistent |
| 222 | Missing mandatory OTP channel type |
| 230 | The payment processor (sofort or ideal) does not support signature approval method (otp or checkbox). |
| 231 | The payment items are not valid. |
| 232 | The payment processor (mandate order item) and payment scheme (payment order item) are not consistent. |
| 233 | The sort code is not found |
| 234 | The sort code is invalid |
| 235 | The account number is invalid |
| 236 | The country code is invalid |
| 237 | Your bank does not accept SEPA payments |
| 238 | The sort code is not valid |
| 239 | Service Unavailable |
| 240 | The payment is not refundable |
| 241 | BIC not consistent with provided IBAN |
| 301 | The card operation has been refused by the operator |
| 401 | Card operation bank refusal |
| 402 | Card operation access failure |
| 403 | Invalid card number |
| 404 | Invalid card cvv |
| 405 | Invalid card expiration data |
| 406 | Invalid birth date |
| 407 | Card operation invalid transaction reference |
| 408 | Card lost |
| 409 | Card stolen |
| 410 | Card expired |
| 411 | Insufficient card funds |
| 412 | Card suspect |
| 413 | Card limit exceeded |
| 414 | Card in opposition |
| 415 | Connection to card operator failed |
| 416 | Card data missing |
| 417 | Card operation duplicate |
| 419 | Card cancelled |
| 420 | Card operator session expired |
| 421 | Existing card alias |
| 422 | Unknown card alias |
| 423 | Card operator internal error |
| 511 | Address not in SEPA country |
| 512 | Iban not in SEPA country |
| 522 | IP address or IBAN or phone number is in blacklist |
| 523 | Debtor IBAN is creditor IBAN |
| 524 | Maximum number of subscriptions for the same IBAN reached |
| 525 | Maximum number of phone numbers for the same IBAN reached |
| 529 | IBAN bank and branch code blacklisted |
| 555 | Anti-fraud rule violation |
| 602 | The card provider returned an error |
| 631 | This account does not exist |
| 632 | Contact your bank for authorisation |
| 633 | Operation cancellation unauthorised |
| 634 | Card expired |
| 635 | Card lost |
| 636 | Card stolen |
| 637 | Check your configuration |
| 638 | Conversion rate is not found |
| 639 | Duplicated transaction |
| 640 | The usage frequency is exceeded |
| 641 | There is an opposition on the account |
| 642 | The bank is unknown |
| 643 | Invalid Card |
| 644 | Invalid PIN |
| 645 | the transaction can't be processed. |
| 646 | Invalid birthdate |
| 647 | Invalid cvv3 |
| 648 | Invalid amount |
| 649 | The amount is exceeded |
| 650 | Security violation |
| 651 | Suspicious card |
| 652 | Transaction can not be found |
| 653 | Transaction refused by card scheme |
| 654 | Unauthorised transaction |
| 655 | Card not registered |
| 656 | Fraud detected |
| 657 | Refund period exceeded |
| 661 | Card not enrolled |
| 662 | Card not participating |
| 663 | Card authentication failed |
| 664 | Can not find verify Enrollment call for this card |
| 665 | Duplicated transaction |
| 666 | Invalid PARES |
| 667 | Enrollment verification failed |
| 668 | Authentication verification failed |
| 669 | Authentication verification failed |
| 681 | Max attempts exceeded |
| 682 | Moto Contract is not set for the merchant |
| 709 | Maximum number of references to the same subscriber reached |
| 901 | Duplicate order |
| 902 | The resource has not been found |
| 903 | Illegal state |
| 904 | Access denied |
| 905 | Unmapped error |
| 906 | Error |
| 907 | Bad Gateway : the remote server sent a wrong response |
| 908 | Currency mismatch between the request and the resource on the server |
| 909 | No payment scheme in the request and SlimPay cannot compute the default one according to the client configuration |
| 910 | The provided payment scheme is unsupported according to the client configuration |
| 911 | The amount is incorrect. |
| 912 | No mandate |
| 913 | The provided request is incompatible with the client configuration |
| 914 | The provided request is invalid |
| 915 | The payment is not cancellable |
| 916 | Cannot find origin bank account |
| 917 | Cannot find destination bank account |
| 918 | There are multiple possible origin and/or destination bank accounts. You must specify them. |
| 919 | Creditor is configured with entities but entityReference is not given |
| 920 | Creditor is not configured with entities but entityReference is given |
| 921 | Creditor entity not found |
| 922 | dateFrom and dateTo are not compatible |
| 923 | Creditor is configured with entities but entityReference is not given. |
| 924 | The binary content is unreadable |
| 925 | Checkout user approval error |
| 926 | Cannot find the refunded payment. |
| 927 | The order is not cancellable |
| 928 | The card transaction is not capturable |
| 929 | The total amount to reimburse cannot be higher than the original transaction. |
| 930 | The process of the recurrent card transaction has failed |
| 931 | You can not access to this resource |
| 1001 | Missing phone |
| 1002 | Phone number is not accessible |
| 1003 | Phone number not received |
| 1004 | Missing email |
| 1005 | Inaccessible email |
| 1008 | Email not received |
| 1009 | Code canceled |
| 1010 | Missing phone and email |
| 1011 | Code cancelled by client |
| 1020 | Order already used |
| 2000 | Forbidden access code reuse |
| 2001 | Forbidden access code override |
| 2002 | Order already in final state |
| 2003 | Registration max attempts |
| 2004 | Invalid Order. |
| 2005 | This functionality is not yet supported |
| 2008 | Order's validation failed. |
| 2011 | Order not found |
| 3000 | This is not a SlimCollect Pay transaction |
| 4000 | The email address or password entered is not valid. |
| 4001 | The account has been locked for security purpose. Try again in few minutes. |
| 4002 | The account has been locked for security purpose. Contact your account manager. |
| 4003 | The Dashboard account password has expired and must be updated. |
| 4004 | Missing multi-factor authentication Data. |
| 4005 | OTP code is not valid. |
| 4006 | Too many requests. |
| 4007 | OTP sms sending failed. |
| 4008 | The password entered is not valid. |
| 4009 | Multi-factor authentication has been locked for security purpose. Try again in few minutes. |
| 4010 | Multi-factor authentication has been locked for security purpose. Contact your account manager. |
| 4011 | QuickSight configuration error |
| 5000 | Failed to create a Slimcollect PIS Payment Link |
| 5100 | Failed to create a Slimcollect AIS Link |
| 5200 | Failed to connect to SlimpayWebhook |
| 5201 | The maximum number of webhook you can create is 16 |
| 5202 | Unrecognized eventType |
| 5203 | The title already exists |
| 5204 | Webhook with this UUID is not existing |
| 5205 | Webhook configuration can't be operated. Please verify your request |
| 10000 | IBAN is blacklisted |
| 10001 | IP is blacklisted |
| 10002 | Untrusted email |
| 10003 | Address is blacklisted |
| 10004 | Name is blacklisted |
| 10005 | IP country is in country list |
| 10006 | Emailage fraud detection |
| 10007 | Invalid IBAN structure |
| 10008 | Phone is blacklisted |
| 10009 | Model mandate check |
| 10010 | Schufa rule check |
| 10100 | Card 3DS evaluation |
Order errors
| Code | Message |
|---|---|
| 100 | Internal error |
| 101 | Incomplete request data |
| 105 | Incoherent timestamp |
| 108 | No customer |
| 120 | Session timeout |
| 123 | Invalid given name |
| 124 | Invalid family name |
| 125 | Invalid email |
| 127 | Invalid phone number |
| 128 | Invalid postal code |
| 129 | Invalid city |
| 133 | Invalid BIC |
| 134 | Invalid IBAN |
| 158 | Max OTP key try reached |
| 160 | Max OTP key send reached |
| 179 | Invalid creditor |
| 180 | Duplicate mandate reference |
| 181 | No documents to sign |
| 186 | Forbidden IBAN |
| 188 | Invalid account owner |
| 201 | Mandate signature failed |
| 202 | Invalid user approval (OTP) code |
| 205 | Inconsistent client data during signature |
| 222 | Missing mandatory OTP channel type |
| 901 | Duplicate order |
| 902 | Resource not found |
| 903 | Illegal state |
| 905 | Unmapped error |
| 931 | You cannot access to this resource : [reason] |
| 1001 | Missing phone |
| 1002 | Phone number is not accessible |
| 1003 | Phone number not received |
| 1004 | Missing email |
| 1005 | Inaccessible email |
| 1008 | Email not received |
| 1009 | Code cancelled |
| 2000 | Forbidden access code reuse |
| 2001 | Forbidden access code override |
| 2002 | Order already in a final status |
| 2003 | Order is disabled or expired |
| 2004 | Invalid order |
| 2005 | This functionality is not yet supported |
| 2008 | Order's validation failed |
Payment errors
In the event that a direct debit or credit transfer fail, an error code will be returned explaining the reason for the R-transaction.
For a complete list of error codes and the reasons for payment failure, please refer to the European Payment Council guide on R-transactions. A selection of common payment failure codes for direct debit are listed below, and are also included on our Help Center.
For information about managing payment failures, please refer to our payment issues section.
Direct debit error codes
| Code | Reason |
|---|---|
| AC01 | Account Identifier incorrect |
| AC04 | Account closed |
| AC06 | Account blocked |
| AC13 | Debtor account is a consumer account |
| AG01 | Direct Debit forbidden on this account for regulatory reasons |
| AG02 | Operation code/transaction code/sequence type incorrect, invalid file format |
| AM04 | Insufficient funds |
| AM05 | Duplicate collection |
| BE05 | Identifier of the Creditor Incorrect |
| CNOR | Creditor Bank is not registered under this BIC in the CSM |
| DNOR | Debtor Bank is not registered under this BIC in the CSM |
| FF01 | File format incomplete or invalid |
| FOCR | Following a cancellation request (by the creditor) |
| MD01 | No mandate or Unauthorised Transaction |
| MD02 | Mandate data missing or incorrect |
| MD06 | Disputed authorised transaction |
| MD07 | Debtor Deceased |
| MS02 | Refusal by the Debtor |
| MS03 | Reason not specified |
| RC01 | Bank Identifier (BIC) Incorrect |
| RR01 | Regulatory Reason |
| RR02 | Regulatory Reason |
| RR03 | Regulatory Reason |
| RR04 | Regulatory Reason |
| SL01 | Specific Service offered by the Debtor Bank |