The following table lists all standardized response codes used in CloudAggregator transaction callbacks. Operators must return only these codes from their wallet endpoints.
Code | Status | Description |
|---|
200 | Success | The request was processed successfully. |
200 | Success - duplicate request | The request was already processed (idempotency). The original response is returned. |
1 | Technical Error | An internal server error occurred on the Operator's platform. |
102 | Wager Not Found | No wager matching the provided transaction_id was found (used in Rollback responses). |
110 | Operation Not Allowed | The requested operation is not permitted under current conditions (insufficient funds check already handled by 1006; this covers other business rule violations). |
400 | Transaction Parameter Mismatch | A duplicate transaction_id was received but essential fields differ from the original request. |
409 | Round Closed / Transaction ID Exists | The round has already been closed, or the transaction_id is already in use for a different operation. |
1000 | Not Logged On | The session is invalid or expired. NEVER return for Result or Rollback requests. |
1003 | Authentication Failed | The session_id or account_id could not be authenticated. |
1006 | Out of Money | The player has insufficient funds to cover the wager. |
1007 | Unknown Currency | The currency in the request is not registered for this Operator. |
1008 | Parameter Required | A mandatory request parameter is missing or malformed. |
1019 | Gaming Limit | A responsible gaming limit (wager, loss, session, deposit) would be exceeded. |
1035 | Account Blocked | The player account is suspended, self-excluded, or otherwise blocked. |