Wager And Result

Wager And Result Transaction

Overview

The Wager And Result method is an optimization that allows game providers to perform both a wager and a result operation in a single transaction. This is particularly useful for instant games where the outcome is determined immediately after the player places a bet, such as scratch cards or simple slot spins.

By combining these operations, the game can reduce latency and network traffic, resulting in a smoother player experience. Like individual Wager and Result transactions, Wager And Result implements idempotency controls to prevent duplicate processing.

Flow Diagram

Casino Responsibilities

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

1. Session Validation

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

2. Transaction Validation

   • Verify sufficient funds are available for the wager
   • Check that the player is within responsible gaming limits
   • Determine if the transaction has already been processed

3. Idempotency Check

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

4. Transaction Processing

   • Process the wager (deduct the bet amount from player balance)
   • Process the result (add the win amount to player balance)
   • Calculate the final player balance

Request Details

Endpoint

?request=wagerAndResult&[parameters]

Request Parameters

Example Request

GET {casino_endpoint}?request=wagerAndResult&gamesessionid=123_jdhdujdk&accountid=111&device=desktop&gameid=80102&apiversion=1.2&result=10.0&betamount=5.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": 105.00,
  "bonusWin": 0.00,
  "realMoneyWin": 10.00,
  "bonusmoneybet": 0.00,
  "realmoneybet": 5.00,
  "bonus_balance": 50.00,
  "real_balance": 55.00,
  "game_mode": 1,
  "order": "cash_money",
  "apiversion": "1.2"
}

Error Handling

Common Error Codes

The error codes for Wager And Result are the same as those used in the individual Wager and Result transactions.

Implementation Notes

1. Use Cases:

   • Instant win games (scratch cards, simple slots)
   • Games where the outcome is determined immediately after the bet
   • Optimizations to reduce latency and improve player experience

2. Idempotency Handling:

   • 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

3. Balance Calculation:

   • The final balance should reflect both the wager deduction and result addition
   • Example: Initial balance 100.00, bet 5.00, win 10.00, final balance 105.00

4. Game Status:

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

5. Free Round Bonus:

   • For FRB games, the betamount is typically 0
   • Include the frbid parameter to identify which bonus is being used

Advantages Over Separate Calls

1. Reduced Latency: Single network round-trip instead of two
2. Simplified Error Handling: One transaction to track and manage
3. Atomic Operation: Either both wager and result succeed, or neither does
4. Improved Player Experience: Faster game play with immediate results

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=wagerAndResult&gamesessionid=123_jdhdujdk&accountid=111&device=desktop&gameid=80102&apiversion=1.2&betamount=10.0&result=10.0&roundid=nc8n4nd87&transactionid=trx_id

Query parameters for signature (alphabetically sorted):

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

Concatenated values: 1111.210.0desktop80102123_jdhdujdk10.0nc8n4nd87trx_id

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

X-Groove-Signature: bba4df598cf50ec69ebe144c696c0305e32f1eef76eb32091585f056fafd9079

Related Endpoints

• Wager - Separate endpoint for placing a bet
• Result - Separate endpoint for reporting game outcome
• Rollback - Used to reverse a transaction if needed