Skip to main content
Migo Docs

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)​

CodeReal scenario
000Unhandled exception (handler catch-all). Not recorded as a business error.
2000Transaction not found or in an invalid state for the operation
2001Client or bank config not found; transaction not found (cancel/void)
2002Bank config or account not found (in authorize/capture)
2003Invalid amount / amount validation / invalid processorAmount / bank with no response
2004Blocked user; invalid OTP (in transaction authorization)
5000Internal error; the bank does not support affiliation
5001Invalid affiliation status received from the bank (webhook)
6000Account error; missing parameters (account/OTP); account validations
6001User not found / missing userUID parameter
6002Insufficient credit/balance (credit user validation)
6003Account not found
6005Account in arrears / default
6010Missing user / affiliation / pre-qualified data, or create/update error
6011Invalid email format (affiliation)
6012Invalid primary phone format (affiliation)
6013Invalid secondary phone format (affiliation)
6014Invalid birth or document expiration date
6015Invalid 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.