Error Codes
All wallet endpoints return error codes in a consistent format using the errorCode and errorText fields.
This section defines all error codes that can be returned by Wallet APIs.
Error Codes Table
| Error Code | Error Text | Triggers Cancel Debit | Cancel Retryable |
|---|---|---|---|
| 0 | Success | No | No |
| 1001 | Invalid timestamp | Yes | Yes |
| 1002 | Invalid hash | Yes | Yes |
| 1003 | Invalid token | No | Yes |
| 1004 | Invalid currency | Yes | Yes |
| 1005 | Insufficient balance | No | Yes |
| 1006 | Player not found | Yes | Yes |
| 1007 | Nothing to cancel | Yes | No |
| 1008 | Cancel not allowed | Yes | No |
| 1009 | Credit not allowed | Yes | No |
| 1100 | General error | Yes | Yes |
| 1101 | Validation error | Yes | Yes |
| 1102 | Game not found | Yes | Yes |
| 1103 | Bet already exists | Yes | Yes |
| 1104 | Transaction already exists with different parameters | Yes | Yes |
| 1105 | Invalid bet limit | Yes | Yes |
| 1106 | Transaction not found | Yes | No |
| 1107 | Non retryable error | No | No |
Error Handling Behavior
-
If Triggers Cancel Debit = Yes, a failed
debitrequest will result in acancelDebitrequest. -
If Triggers Cancel Debit = No, no cancel request will be triggered.
-
If Cancel Retryable = Yes, the system will retry the
cancelDebitrequest. -
If Cancel Retryable = No, the system will stop retrying the
cancelDebitrequest.