Result

Result Transaction

Overview

The Result method is called by the game provider to inform the casino that a game round has completed and to report the outcome. If the player wins, the Result transaction adds the winning amount to the player’s balance. If the player loses, a result value of 0 is sent, indicating no additional funds should be added to the player’s balance.

Flow Diagram

Casino Responsibilities

The casino platform must perform the following operations when processing a Result request:

1. Session Validation

   • Confirm the incoming game session ID is valid
   • Verify the session is associated with the provided account ID

2. Idempotency Check

   • Check if a request with the same transactionid has been processed before
   • If any essential fields mismatch (transactionid, accountid, or result), return “Transaction parameter mismatch”
   • If no mismatches, return the original response with status “200 Success - duplicate request”

3. Round Validation

   • Confirm that the incoming accountid and roundid match a previously placed wager
   • For FRB or tournament payouts, a Result may be received without a previous Wager

4. Session Expiry Handling

   • A Result must be accepted even if the game session has expired
   • Return code 1000 Not logged on is never a valid response to a Result call

5. Game Status Processing

   • If gamestatus is “completed”, mark the round as closed
   • If gamestatus is “pending”, the round remains open for additional Result transactions

Request Details

Endpoint

{casino_endpoint}?request=result&[parameters]

Request Parameters

Example Request

GET {casino_endpoint}?request=result&gamesessionid=123_jdhdujdk&accountid=111&device=desktop&gameid=80102&apiversion=1.2&result=10.0&roundid=nc8n4nd87&transactionid=trx_id&gamestatus=completed

Response Details

Response Parameters

Example Success Response

{
  "code": 200,
  "status": "Success",
  "walletTx": "de73550e-0612-4a1b-8a0d-a5a3745b",
  "balance": 100.00,
  "bonusWin": 0.00,
  "realMoneyWin": 10.00,
  "bonus_balance": 50.00,
  "real_balance": 50.00,
  "game_mode": 1,
  "order": "cash_money",
  "apiversion": "1.2"
}

Error Handling

Common Error Codes

Implementation Notes

1. Game Status Handling:

   • pending - Indicates that the round is still in progress and more Result transactions may follow
   • completed - Indicates the round is finished and should be closed
   • A round can have multiple pending Results but only one completed Result

2. Idempotency Handling:

   • Always store transaction IDs to identify duplicate requests
   • Return the original response for duplicate transactions with the same transaction ID
   • Only the balance fields may change in duplicate responses (as player balance may have changed due to other transactions)

3. Session Expiry:

   • Result transactions MUST be processed even if the player’s session has expired
   • This is crucial as Results may arrive significantly after the player has disconnected
   • Never return 1000 Not logged on for Result transactions

4. Free Round Bonus Results:

   • For FRB games, a Result may be received without a matching Wager
   • Include the frbid parameter to identify which bonus the Result belongs to

5. Multiple Results in a Round:

   • Some games (particularly live games) may send multiple Result transactions for a single round
   • Only the final Result with gamestatus=completed closes the round

Security

When Signature Validation is enabled:

1. Include the X-Groove-Signature header in your request
2. Calculate signature using query parameters (excluding request)
3. Include frbid parameter if present (for free round bonuses)
4. See Signature Validation for detailed implementation

Signature Example

For the request:

GET {casino_endpoint}?request=result&gamesessionid=123_jdhdujdk&accountid=111&device=desktop&gameid=80102&apiversion=1.2&result=10.0&roundid=nc8n4nd87&transactionid=trx_id

Query parameters for signature (alphabetically sorted):

• accountid: “111”
• apiversion: “1.2”
• device: “desktop”
• gameid: “80102”
• gamesessionid: “123_jdhdujdk”
• result: “10.0”
• roundid: “nc8n4nd87”
• transactionid: “trx_id”

Concatenated values: 1111.2desktop80102123_jdhdujdk10.0nc8n4nd87trx_id

With security key "test_key", the signature would be:

X-Groove-Signature: d9655083f60cfd490f0ad882cb01ca2f9af61e669601bbb1dcced8a5dca1820f

Related Endpoints

• Wager - Used before a Result to place a bet
• Wager and Result - Combined operation for immediate bet and win
• Rollback on Result - Used to reverse a Result transaction if needed