Wager

Wager Transaction

Overview

The Wager method represents a player placing a bet in a game. When a player initiates a betting action, the game provider sends a Wager request to the Tech Fusion platform, which then forwards it to the casino operator. The casino processes the request by validating the player’s session, checking available funds, and updating the player’s balance accordingly.

Flow Diagram

Casino Responsibilities

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

1. Session Validation

   • Confirm the incoming game session ID is valid
   • Verify the session is associated with the provided account ID
   • Reject the wager if validation fails

2. Transaction Validation

   • Verify sufficient funds are available
   • 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 (transactionid, accountid, or betamount), return “Transaction parameter mismatch”
   • If no mismatches, return the original response with status “200 Success - duplicate request”

4. Transaction Storage

   • Store transaction details to handle future Result and Rollback calls
   • Important fields to store: gamesessionid, accountid, roundid, transactionid, and betamount

Request Details

Endpoint

{casino_endpoint}?request=wager&[parameters]

Request Parameters

Example Request

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

Response Details

Response Parameters

Example Success Response

{
  "code": 200,
  "status": "Success",
  "accounttransactionid": "aaaaaaa",
  "balance": 100.00,
  "bonusmoneybet": 0.00,
  "realmoneybet": 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. 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)

2. Transaction Storage:

   • Store wager details to validate future Result and Rollback calls
   • Key data includes: session ID, account ID, round ID, transaction ID, and bet amount

3. Error Handling:

   • Return appropriate error codes based on validation results
   • Include detailed error messages for troubleshooting

4. Free Round Bonuses:

   • If the wager is part of a Free Round Bonus, include the frbid parameter
   • For FRB wagers, the bet amount is typically 0 in real money mode

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=wager&gamesessionid=123_jdhdujdk&accountid=111&device=desktop&gameid=80102&apiversion=1.2&betamount=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”
• roundid: “nc8n4nd87”
• transactionid: “trx_id”

Concatenated values: 1111.210.0desktop80102123_jdhdujdknc8n4nd87trx_id

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

X-Groove-Signature: f6d980dfe7866b6676e6565ccca239f527979d702106233bb6f72a654931b3bc

Related Endpoints

• Result - Used after a wager to add winnings to the player’s balance
• Wager and Result - Combined operation for immediate bet and win
• Rollback - Used to reverse a wager transaction if needed