search

🔄Rollback

circle-exclamation

For security purposes, you must whitelist only our server IPs to access your Seamless callback endpoint. We will not be responsible if your system receives transaction requests from unauthenticated sources. Ensure you record the IP address of every incoming request to your Callback URL.

Within the Single Wallet Integration framework, the "Rollback" function is an essential safeguard mechanism designed to ensure the integrity of player transactions. In scenarios where a player has successfully placed a bet in a game but the Customer's system either fails to respond, takes longer than the 3-second response window, or if the Game Provider experiences an internal system failure, our system will promptly initiate a "Rollback". This action ensures the immediate cancellation of the debit transaction, protecting the player from any system-induced discrepancies.

circle-info

Endpoint: /api/rollback Request Type: POST Content-Type: application/json

hashtag
Example rollback for Deduct balance

In case player not have enought balance, We must decrease player balance for negative

{
  "operatorToken": "<operatorToken>",
  "seamlessKey": "<seamlessKey>",
  "agentUsername": "<agentUsername>",
  "playerUsername": "<playerUsername>",
  "currencyCode": "<currencyCode>",
  "productName": "SA Gaming",
  "productId": 1,
  "productCode": "SA",
  "categoryId": 2,
  "categoryName": "Live Casino",
  "gameName": "Live Baccarat",
  "gameCode": "sa-baccarat-eu",
  "txnId": "eb54307d-7033-4a82-aa20-3cb42a7ea79a",
  "rollbackTxnId": "eb54307d-7033-4a82-aa20-3cb42a7ea79a",
  "roundId": "19e739a8-3855-4d88-bf19-e2094717ba2b",
  "eventType": 4,
  "eventName": "rollback",
  "txnRemark": "<txnRemark>",
  "amount": -1000,
  "requestUid": "<requestUid>",
  "requestTime": "<requestTime>",
  "timestamp": "<timestamp>"
}

hashtag
Example rollback for Increase balance

hashtag
Response example

Response Code:

🖥️Response Codechevron-right

Data Response Timing and Bet Outcomes:

Response Duration: For the "Debit" function to work seamlessly, it's imperative for the Customer's system to provide a timely response. Specifically, the Game Provider expects a data response from the Customer's system within a tight window of 3 seconds.

Implications of Delayed Response: Bet Cancellation: If the response isn't received within the stipulated 3-second timeframe, the bet in question will automatically be cancelled. This ensures that no bets hang in an indeterminate state due to system latency or communication delays.

Bet Rejection by Game Provider: In addition to bet cancellation, a delay beyond the 3-second window will result in the bet being outright rejected by the Game Provider. Players will be informed that their bet was not accepted due to a system delay.

Recommendations for Customers: Customers should optimize their systems to ensure prompt responses to any requests made by the Game Provider. This is essential to guarantee a smooth and enjoyable player experience.

Regular system checks and performance monitoring are advised to maintain consistent responsiveness and prevent unnecessary bet rejections.

In the rare event of recurring delays or issues, customers are encouraged to get in touch with the technical support team for diagnostics and potential solutions.

This description highlights the importance of a timely response and clearly outlines the consequences of delays, ensuring clarity for all stakeholders. Adjust as needed to fit your specific context or requirements.

PreviousCreditNextReward