Application Error Codes
Any HTTP response with a status code of 400 or greater will contain an array of one or more errors that cause the request to fail.
[
{
"code": "USR007",
"description": "Incorrect code",
"severity": "LOW",
"type": "BUSINESS",
“traceId”: “hchuewhuiehdiwhei”
}
]
Error codes are of the format AAANNN where AAA is a code in A-Z describing the error category and NNN is a numeric providing a more specific error within the category.
The following table contains the descriptions of the possible error codes that may be returned
Code | Description |
---|---|
Description | Entity Not Found. Typically accompanied with an http status code 404. Indicates that the resource being referred to could not be found. |
RLT001 | The request is rejected due to a Rate Limit being hit. Try again later when the next rate limit window opens |
DAE001 | A Web Application Exception was reported from a downstream integration below Eclipse. The exact reason is not known but the description may contain more details |
UNK001 | An Unknown error has occurred. The exact reason is not known but the description may contain more details |
NUR001 | Something during request processing expected a single result for something but instead got more than one |
PNF001 | A configuration property is missing. The property is required to process the request. Contact Eclipse support to understand what configuration is needed. |
VAL001 | A data constraint violation has occurred. |
JPE001 | An error occurred parsing the JSON provided in the request |
SEC001 | A security exception has occurred. The request does not have the required rights/access to do what it is trying to do or authentication data is invalid |
NFE001 | A parameter provided in the request is invalid in the context of the request. The description will explain what parameter is invalid. This is alerted to the Eclipse operations team automatically. |
IAE002 | A parameter provided in the request is invalid in the context of the request. The description will explain what parameter is invalid. These are typically from fields provided by the end user and are not alerted to the Eclipse operations team. |
ISE001 | The request could not be processed as something is not in a state that allows the changes that are being requested. |
OLE001 | An optimistic lock exception has occurred. Typically caused by a request to update something which has been updated by another request since the data was last read. |
SQL001 | An error was reported by a database trying to persist the data of the request |
IOE001 | An I/O Exception occurred either accessing data over the network or a file system |
WAL001 | The request could not be processed as a wallet involved in the request did not have sufficient balance to allow the transfer/charge. |
USR010 | Incorrect challenge response |
USR004 | Password is too weak |
USR006 | Password change code is incorrect |
USR011 | Too many authentication requests. Reuse bearer tokens until they expire. Do not get a new token for every API call. The limit is 40 successful authentication requests per hour for user identity. |
USR015 | Incorrect device fingerprint - device fingerprint is required for login but the one provided does not match what is on record. One must do a login with OTP to use the new device fingerprint. |
USR016 | Invalid device fingerprint - Device fingerprint is required but was not provided. |
USR072 | User already exists with that national identity number |
PAY002 | Invalid data in a payment request caused the payment to fail |
PAY005 | An unknown error prevented the payment from being processed within Eclipse |
UOE001 | An unsupported operation has been attempted. E.g. trying to do something on a gateway that does not support that functionality. |
LIM001 | The transaction is denied as it would exceed maxCreditsPerDay. Description would be along the lines of “Total daily credits to wallet would be exceeded. Max allowed is XXX and this transaction would make the total YYY for today” |
LIM002 | The transaction is denied as it would exceed maxCreditsPerMonth. Description would be along the lines of “Total monthly credits to wallet would be exceeded. Max allowed is XXX and this transaction would make the total YYY for this month” |
LIM003 | The transaction is denied as it would exceed maxDebitsPerDay. Description would be along the lines of “Total daily debits to wallet would be exceeded. Max allowed is XXX and this transaction would make the total YYY for today” |
LIM004 | The transaction is denied as it would exceed maxDebitsPerMonth. Description would be along the lines of “Total monthly debits to wallet would be exceeded. Max allowed is XXX and this transaction would make the total YYY for this month” |
LIM005 | Per transaction debit to wallet would be exceeded (see maxDebitPerTransaction on wallet type) |
LIM006 | Per transaction credit to wallet would be exceeded (see maxCreditPerTransaction on wallet type) |
LIM007 | Per days debits/credits credit on wallet would be exceeded (see maxTransactionTotalPerDay on wallet type) |
LIM008 | Total daily credits to organisation would be exceeded (see maxCreditsPerDayForOrg on wallet type) |
LIM009 | Total balance across users wallets would be exceeded (see maxTotalCurrentBalanceForUser on wallet type) |
LIM010 | Total monthly credits to user would be exceeded (see maxCreditsPerDayForUser on wallet type) |
LIM011 | Total monthly credits to organisation would be exceeded (see maxCreditsPerMonthForOrg on wallet type) |
LIM012 | Total monthly debits from organisation would be exceeded (see maxDebitsPerMonthForOrg on wallet type) |
LIM013 | Total daily debits from user would be exceeded (see maxDebitsPerDayForUser on wallet type) |
LIM014 | Total daily debits from organisation would be exceeded (see maxDebitsPerDayForOrg on wallet type) |
LIM015 | Total monthly debits from user would be exceeded (see maxDebitsPerMonthForUser on wallet type) |
LIM016 | Total daily credits to user would be exceeded (see maxCreditsPerDayForUser on wallet type) |
LIM017 | Total daily transactions to and from user would be exceeded (see maxTransactionTotalPerDayForUser on wallet type) |
LIM018 | Total daily transactions to and from organisation would be exceeded (see maxTransactionTotalPerDayForOrg on wallet type) |
LIM019 | Total balance across organisation wallets would be exceeded (see maxTotalCurrentBalanceForOrganisation on wallet type) |
PAY006 | Unknown external wallet type |
ARCH014 | JWT has expired |
ARCH010 | JWT is not renewable |
Updated 2 months ago