RollbackTransaction

Request parameters of data:

• token — identifies a player
• transactionId — the id of transaction to rollback
• gameId — identifies game
• roundId - (OPTIONAL) game round Id for which 

Response parameters:

• result — request result (true if success and false if failed)
• err_desc — error description (if “result” is false)
• err_code — error code (if “result” is false)
• transactionId — unique key which identifies single financial transaction(RGS transaction ID)
• balance - player balance after transaction

Rollback Transaction request example:

Endpoint: https://staging.tomhorngames.com/api/TomHorn/RollbackTransaction

{
    "time": "04-02-2021 14:57:35",
    "hash": "300E010BFD0B0B19C07AC4F2007AB7EF",
    "data": {
        "token": "136275",
        "transactionId": "16928505367480413124",
        "gameId": "racingbet"
    }
}

Error codes

Rollbacks in rounds with multiple Withdraws

In case a game round had multiple Withdrawals:

• To cancel a withdrawal from a ground with multiple withdrawals, just sent one (1) Rollback request.
• To cancel all Withdraws in the game round, the game provider has to call a Rollback for each withdrawal transaction (in case of error/timeout: recall until successful or “Round closed” error). Multiple Withdrawals work in parity, so InAPI expects the same amount of Rollbacks for the same number of withdrawals.
  

Send the optional roundId parameter with the Rollback call to ensure rounds will be marked as closed on InAPI side.

If all withdrawals were rolled back, any deposit call will fail. A deposit call is only expected if only any of the withdrawals were rolled back and NOT all.