Appendix - Transaction Response Status Codes

This section contains reference information for response codes used throughout the Transaction API.

Success Codes

Code Status Description
200 Success Transaction processed successfully
200 Success - duplicate request Request with same transaction ID was already processed

Error Codes

Code Status Description Applicable Endpoints
1 Technical error Generic technical error All
102 Wager not found Wager with given transactionId not found Rollback
110 Operation not allowed Operation cannot be performed due to business rules Wager, Result, Rollback
400 Transaction parameter mismatch Essential fields mismatch (transactionid, accountid, betamount) Wager, Result, Rollback
409 Round closed or transaction ID exists Round already closed or transaction ID already used Wager, Result
443 Wrong Game ID Game ID is not valid FRB Create/Assign
444 Wrong Player Id Player ID is not valid FRB Assign
449 Invalid Parameters Request parameters are invalid FRB Create/Assign
500 Internal Error Internal server error FRB Create/Assign
1000 Not logged on Session invalid or expired GetAccount, GetBalance, Wager
1003 Authentication failed Authentication failed GetAccount
1006 Out of money Insufficient funds Wager
1019 Gaming limit Loss limit exceeded or Overall bet limit exceeded Wager
1035 Account blocked Player account is blocked Wager

Operation Not Allowed Details

Code 110 (Operation not allowed) can occur for various reasons:

For Wager:

  • The wager amount is less than 0
  • A user with the specified accountId cannot be found
  • The accountId is not identical to the sessionId that was created

For Result:

  • The result amount is less than 0
  • A user with the specified accountId cannot be found
  • The accountId is not identical to the sessionId that was created
  • Game status is not pending or completed

For Rollback:

  • A win request was already received for the given wager

Important Notes

  1. Success - duplicate request: When a request with the same transaction ID is received again, the original response should be returned with status 200. Balance-related parameters may differ as the player’s balance may have changed.

  2. Session Expiry: Result and Rollback requests must be accepted even if the game session has expired. Return code 1000 (Not logged on) is never a valid response to result or rollback calls.

  3. Idempotency: All transaction endpoints must provide idempotency to ensure duplicate requests are handled properly.