Error codes
This is the complete list of client error codes with an explanation of each code. The error code is returned in the errorCode attribute of an error object. When you are building business logic to identify and handle errors, it should be based on the error code.
Client errors 1000–1999
The Troubleshooting column suggests how to solve the problem that caused the error.
| Code | Message | Troubleshooting |
|---|---|---|
| 1001 BAD_REQUEST | Missing required header | Include x-session-id and x-device-id in the request header. |
| 1002 BAD_REQUEST | Missing required parameter | Include the missing parameter(s). What parameter is missing depends on which endpoint you are calling. Create Session: Include header parameter bankId.Get Account by ID, Get Balances by ID, Get Transactions by ID: Include endpoint parameter id.Get Payments by ID, Complete Payment: Include endpoint parameter paymentId.Include endpoint parameter paymentProduct. |
| 1003 BAD_REQUEST | Invalid account id | Valid IBANs consist of two characters followed by 13 to 32 digits. The number of digits in Nordic accounts are as follows: Norway 13, Sweden 22, Finland 16 and Denmark 16. Valid BBANs only consist of digits, while the following number of digits apply to Nordic accounts: Norway 11, Sweden 20 and Denmark 14. Domestic Scheduled Payment: The debtorAccount and/or creditorAccount object does not contain a valid IBAN or BBAN.If accountScheme = BGNR or PGNR, the identifier must be between min 7 and max 8 digits long.SEPA Scheduled Payment: The debtorAccount object does not contain a valid IBAN or BBAN. |
| 1003 BAD_REQUEST | Invalid payment id | Get Payment by Id, Authorize Payment, Complete Payment: The wrong paymentId was supplied. |
| 1004 BAD_REQUEST | Invalid x-psu-ip address | The x-psu-ip-address you included is not in a valid IPV4 or IPV6 formator x-psu-ip-address is required by the bank, but not included in your call. |
| 1005 BAD_REQUEST | Invalid redirect URL | The URL given in x-redirect-url is not according to the proper URL syntaxor the URL given in x-redirect-url does not match any of the Redirect URLs registered for your application in the Dashboard. |
| 1006 BAD_REQUEST | Invalid PaymentProduct | Get Payment by Id, Authorize Payment, Complete Payment: The value of paymentProduct must correspond to the type of payment that was initiated, which is either domestic-transfer, domestic-scheduled-transfer, sepa-credit, or sepa-scheduled-credit. |
| 1007 BAD_REQUEST | Payment Id not associated with the current session | Get Payment by Id, Authorize Payment, Complete Payment: The endpoint parameter paymentIdwas not generated in the session identified by the x-session-id that you supplied in the request header. |
| 1007 BAD_REQUEST | Payment Id not associated with the current session. Payment Not Found on the Bank's side | Get Payment by Id: The endpoint parameter paymentIdwas edited/deleted by the end-user in their online banking. |
| 1008 BAD_REQUEST | Payment Id not associated with the current payment product | Get Payment by Id, Authorize Payment, Complete Payment: There is a mismatch between the endpoint parameters paymentId and paymentProduct. The paymentId was not generated for the given paymentProduct. |
| 1009 BAD_REQUEST | Payment Id in an invalid state | Complete payment: The paymentId represents a payment that is not yet authorized, so you have to run Authorize Payment first. |
| 1010 BAD_REQUEST | Unsupported payment Id for this operation | Authorize Payment: You are trying to authorize a payment that is exempt from SCA. |
| 1011 BAD_REQUEST | Remittance Information structured or unstructured needs to be provided | Either remittanceInformationStructured or remittanceInformationUnstructured is required in the request body for payment initiations. |
| 1012 BAD_REQUEST | Remittance Information structured needs to have reference | Include reference and referenceType in the remittanceInformationStructured object. |
| 1013 BAD_REQUEST | An unsupported operation for current resource | Payment initiation: The payment product you are trying to use is not supported by the bank. Get Consent: Your URL is invalid. Call Get Consent with the exact URL received as a part of the 1426 error response. The URL is the value of the href parameter in the link object, see the consent guide for more information. |
| 1014 BAD_REQUEST | Insufficient funds for the transaction | |
| 1015 BAD_REQUEST | Amount negative or not a valid number | The amount must be greater than 0. |
| 1016 BAD_REQUEST | Account is required | Include the account number in the payment request. |
| 1017 BAD_REQUEST | Invalid IBAN | The debtor account number is not valid. Domestic Scheduled Payment, Domestic Payment: Creditor and debtor account numbers are located in different countries, but they must be in the same country. |
| 1018 BAD_REQUEST | Invalid ISO 4217 currency code | Include a valid currency code. |
| 1019 BAD_REQUEST | The account id is not associated with this current confirm funds request | |
| 1020 BAD_REQUEST | There is no session available. Please check your session id and device id or create another session. | |
| 1021 BAD_REQUEST | Invalid resource id | Invalid bankId was given. |
| 1022 BAD_REQUEST | Invalid currency for requested account | Payment currency is different from debtor account currency. It must be the same. Also, note that SEPA payments must always be made in EUR. |
| 1023 BAD_REQUEST | Invalid values in payload. | The request body JSON for payment initiation has the wrong format. |
| 1023 BAD_REQUEST | Invalid values in payload. The payment amount exceeds period limit for this bank account. | The period limit is set by PSUs in their online bank. The period referred to is usually "monthly". |
| 1023BAD_REQUEST | Invalid values in payload. The payment amount exceeds payment amount limit for this bank account. | The period amount limit is set by the bank, and in some cases, PSUs can override the bank's limit in their online bank. |
| 1024 BAD_REQUEST | HTTP request method not supported | Make sure that the request method is according to the description in API References. |
| 1025 BAD_REQUEST | Invalid device id. Device id needs to be of proper RFC4112 Format | |
| 1026 BAD_REQUEST | Invalid end-to-end identifier. The end-to-end identifier should be between 1 and 35 characters | Correct the endToEndIdentification. |
| 1027 BAD_REQUEST | PSU Id header is missing even though it is required by the bank | Include x-psu-id in the request header (string that contains an encrypted end-user identifier). |
| 1028 BAD_REQUEST | No encryption key found for the given client id | This error is returned when an encryption key for the application has not been generated in the developer portal. Make sure to follow the guidelines given in Sensitive end-user data. |
| 1029 BAD_REQUEST | The date when the money should reach the recipient must be a banking day | Correct the requestedExecutionDate and make sure it’s a banking day in the country where the creditor and debtor account is located.Use for example information sources showing Nordic bank holidays or global holidays. |
| 1030 BAD_REQUEST | The execution date is in the past. Please specify a later date | Correct the requestedExecutionDate and make sure it’s a future date. |
| 1031 BAD_REQUEST | The execution date should be of date format: yyyy-mm-dd | Correct the date format so that it follows ISO-8601. |
| 1032 BAD_REQUEST | Wrong format of unstructured remittance information, maximum is 140 characters | Change the contents of remittanceInformationUnstructured and make sure it’s a maximum of 140 characters. |
| 1032 BAD_REQUEST | Wrong format of unstructured remittance information, maximum is 35 characters for Swedbank | Change the contents of remittanceInformationUnstructured and make sure it’s a maximum of 35 characters. |
| 1032 BAD_REQUEST | Wrong format of unstructured remittance information, maximum is 12 characters for Swedish banks | Change the contents of remittanceInformationUnstructured and make sure it’s a maximum of 12 characters. |
| 1032 BAD_REQUEST | Wrong format of unstructured remittance information, maximum is 40 characters for Danish banks | Change the contents of remittanceInformationUnstructured and make sure it’s a maximum of 40 characters. |
| 1032 BAD_REQUEST | Wrong format of unstructured remittance information, maximum is 66 characters for Danske NO | Change the contents of remittanceInformationUnstructured and make sure it’s a maximum of 66 characters. |
| 1032 BAD_REQUEST | Wrong format of unstructured remittance information, maximum is 30 characters for Bank Norwegian NO | Change the contents of remittanceInformationUnstructured and make sure it’s a maximum of 30 characters. |
| 1033 BAD_REQUEST | Debtor account is required. | Include a debtor account. |
| 1033 BAD_REQUEST | Debtor account is required. Invalid debtor account | Include a valid debtor account. |
| 1034 BAD_REQUEST | Creditor account is required. | Include a creditor account. |
| 1034 BAD_REQUEST | Creditor account is required. Invalid creditor account | Include a valid creditor account. |
| 1035 BAD_REQUEST | Invalid TPP id | |
| 1036 FATAL | The operation failed due to invalid/missing access rights | Payment initiation is not allowed for the given debtor account. |
| 1037 BAD_REQUEST | Country field inside the creditor address is mandatory | Include country inside the paymentMetadata object in the request body. |
| 1038 BAD_REQUEST | Missing required parameter: Creditor address | Include country inside the paymentMetadata object in the request body. |
| 1039 BAD_REQUEST | Missing required parameter : Creditor name | Include creditorName in the request body. |
| 1040 BAD_REQUEST | Missing required parameter : Debtor name | Include debtorName in the request body. |
| 1041 BAD_REQUEST | The reference number is not valid | Include a valid reference in the remittanceInformationStructured object in the request body. |
| 1042 BAD_REQUEST | The reference type is not valid | Include a valid referenceType in the remittanceInformationStructuredobject in the request body. |
| 1043 BAD_REQUEST | Missing reference number in structured remittance information | Include a valid reference in the remittanceInformationStructured object in the request body. |
| 1044 BAD_REQUEST | Reference field is not allowed for this payment type | Use remittanceInformationUnstructured instead of remittanceInformationStructured. |
| 1045 BAD_REQUEST | The creditor message length must be between 0 and 12 characters | Change the contents of remittanceInformationUnstructured and make sure it’s a maximum of 12 characters (10 for Swedbank). |
| 1046 BAD_REQUEST | Duplicate insert operation | |
| 1047 BAD_REQUEST | Invalid PSU Id. | Your x-psu-id is invalid. |
| 1047 BAD_REQUEST | Invalid PSU Id. Corporate accounts are not supported | You are trying to access a corporate account, which is not supported. |
| 1048 BAD_REQUEST | Invalid character(s) in name or address field | Only A-Å, a-å, 0-9, and space allowed. |
| 1426 CONSENT | This resource needs to initialize consent. Please use the URL provided to continue. The consent URL will provide the bank authentication URL. You can consume this resource after authenticating. | Call GET Consent. |
| 1428 CONSENT | This payment requires Strong Customer Authentication (SCA). Please use the authorization URL provided to continue, then complete the payment API after authorizing it. | Call GET Authorize Payment. |
Client errors 2000–2999
| Code | Message |
|---|---|
| 2001 AUTH | Invalid token |
| 2002 AUTH | Expired token |
| 2003 AUTH | Not authorized |
| 2004 AUTH | Forbidden |
| 2005 AUTH | Invalid client id/secret |
| 2006 AUTH | API Not found |
| 2007 AUTH | Multiple tokens found |
| 2008 AUTH | Invalid grant_type |
| 2009 AUTH | Refresh token expired |
Neonomics errors 3000–3999
These are internal errors in the Neonomics platform. For these errors, Neonomics clients can retry the request in case of NETWORK error.
| Code | Message |
|---|---|
| 3001 FATAL | Internal error. Please contact Neonomics support with complete error message. |
| 3002 FATAL | Internal error. Please contact Neonomics support with complete error message. |
| 3003 FATAL | Internal error. Please contact Neonomics support with complete error message. |
| 3004 FATAL | Internal error. Please contact Neonomics support with complete error message. |
| 3005 FATAL | Internal error. Please contact Neonomics support with complete error message. |
| 3006 FATAL | Internal error. Please contact Neonomics support with complete error message. |
| 3007 FATAL | Internal error. Please contact Neonomics support with complete error message. |
| 3008 FATAL | Internal error. Please contact Neonomics support with complete error message. |
| 3009 FATAL | Internal error. Please contact Neonomics support with complete error message. |
| 3010 CONSENT | Unable to keep session alive. Consent missing. |
| 3011 CONSENT | Session not found. Consent missing. |
| 3012 FATAL | Internal error. Please contact Neonomics support with complete error message. |
| 3013 FATAL | Internal error. Please contact Neonomics support with complete error message. |
| 3014 FATAL | Internal error. Please contact Neonomics support with complete error message. |
| 3015 FATAL | Internal error. Please contact Neonomics support with complete error message. |
| 3016 FATAL | Internal error. Please contact Neonomics support with complete error message. |
| 3017 FATAL | Internal error. Please contact Neonomics support with complete error message. |
| 3018 FATAL | Internal error. Please contact Neonomics support with complete error message. |
| 3019 BAD_REQUEST | Invalid encryption for personal identification |
| 3901 NETWORK | Network error occurred. Please retry. |
| 3902 FATAL | Internal error. Please contact Neonomics support with complete error message. |
| 3999 FATAL | Internal error. Please contact Neonomics support with complete error message. |
Bank errors 4000–5999
These are errors returned from the Bank. For these errors, Neonomics clients can retry the request in case of NETWORK error.
| Code | Message |
|---|---|
| 4903 FATAL | Network error |
| 4904 FATAL | Internal error. Please contact Neonomics support with complete error message. |
| 4905 FATAL | Internal error. Please contact Neonomics support with complete error message. |
| 4906 FATAL | Unauthorized operation |
| 4907 NETWORK | Network error |
| 4908 FATAL | Internal error. Please contact Neonomics support with complete error message. |
| 4909 FATAL | Internal error. Please contact Neonomics support with complete error message. |
| 4910 BAD_REQUEST | Invalid IBAN/BBAN/SORT_CODE_ACCOUNT_NUMBER provided |
| 4911 BAD_REQUEST | Access to account denied. Please verify that account number is correct. |
| 4912 FATAL | Payment rejected by the bank or failed at the bank's end |
| 4913 FATAL | Invalid header error |
| 4914 FATAL | Payment failed at bank's end |
| 4915 FATAL | Payment rejected by the bank |
| 4929 BAD_REQUEST | Daily request limit reached |
| 4930 FATAL | Internal bank error |
| 4997 CONSENT | The bank's consent request has expired |
| 4998 CONSENT | Unable to complete consent with provider |
| 4999 FATAL | Unknown error |
| 5000 BAD_REQUEST | Bank does not currently allow duplicate payments. Please change the ‘instrumentedAmount’. |
| 5001 BAD_REQUEST | PSU Id is required by the bank |
| 5002 NETWORK | Connection Closed from the bank |
| 5003 BAD_REQUEST | Missing IBAN and/or BBAN |
| 5004 BAD_REQUEST | Missing payment metadata |
| 5006 BAD_REQUEST | Missing references in structured remittance information |
Updated about 1 year ago