Error catalog
All errors follow the universal envelope with an error: { code, name, description, message } object. The code comes from the catalog (MongoDB); the message is the specific detail added by the service.
Code catalog (code)
| Code | Real scenario |
|---|---|
000 | Unhandled exception (handler catch-all). Not recorded as a business error. |
2000 | Transaction not found or in an invalid state for the operation |
2001 | Client or bank config not found; transaction not found (cancel/void) |
2002 | Bank config or account not found (in authorize/capture) |
2003 | Invalid amount / amount validation / invalid processorAmount / bank with no response |
2004 | Blocked user; invalid OTP (in transaction authorization) |
5000 | Internal error; the bank does not support affiliation |
5001 | Invalid affiliation status received from the bank (webhook) |
6000 | Account error; missing parameters (account/OTP); account validations |
6001 | User not found / missing userUID parameter |
6002 | Insufficient credit/balance (credit user validation) |
6003 | Account not found |
6005 | Account in arrears / default |
6010 | Missing user / affiliation / pre-qualified data, or create/update error |
6011 | Invalid email format (affiliation) |
6012 | Invalid primary phone format (affiliation) |
6013 | Invalid secondary phone format (affiliation) |
6014 | Invalid birth or document expiration date |
6015 | Invalid gender (must be male or female) |
Retry strategy
When to retry
On 5000 or 000, retry with exponential backoff (1s, 2s, 4s) up to 3 times. The 2xxx / 6xxx codes are business errors and must not be retried without correcting the input.
For the per-endpoint detail of which codes each operation can return, browse the Credit Core interactive reference.