All the possible results of the request can be presented with the following codes:
| Code | Description |
|---|---|
| 0 | Success |
| 100 | Player account does not exist |
| 101 | Invalid currency |
| 102 | Player account blocked/inactive |
| 103 | Insufficient funds |
| 104 | Invalid player sessionToken |
| 105 | Invalid credentials |
| 106 | Duplicate transaction ID |
| 107 | Game round closed |
| 199 | Custom error |
| 501 | Retry/cancel triggered |
If the response code is not "0" (Success), the request is considered failed.
If the response code is "199" (Custom error), the request is considered failed. It will not be canceled/retried, the error dialog will be displayed. This error dialog will contain the text from the received "description" field as is (without translation).
If the response code is "501" (Retry / cancel triggered), the corresponding request is also considered failed but it will be retried (available for the Cancel and Credit requests only) or canceled (available for the Debit request only).
RubyPlay doesn't process responses depending on the error codes from the table above (the exception is 501 code and it suitable for the Debit, Cancel, Credit requests only). All these Codes and Descriptions must be provided by the Operator just to be able to resolve possible issue on both sides.