Guide · Wallet
A void returns the stake that was actually taken
Studios void rounds when a shoe breaks, a stream dies, or a game client fails before a result exists. The wallet's job is to put back the stake it took. It is not to decide the result the studio refused to issue.
7 min readUpdated By the Turnkeyxgaming team
Do not invent a settlement
A rollback names the debit it reverses. Apply it once. If the debit never succeeded, the rollback is a no-op that you still acknowledge, so the studio stops retrying. If you already credited a win, you are in an exception: the void arrived after settlement, and a human should see it. Do not silently claw back a paid win without a rule you can show the player.
The player-facing history should say voided, not lost. A stake that comes back is not a win and it is not GGR. Leave it out of the gaming-revenue total. Finance disputes start when a voided round stays inside stake and the studio's invoice has already removed it.
Acknowledge a rollback even when the debit never landed. The studio retries until it receives success. A not-found response looks like a failure, so the same reversal keeps arriving overnight and the on-call treats a no-op as an outage. Persist the acknowledgement against the named debit id, including the explicit case that nothing was refunded because nothing was taken.
How a void should read in history and in revenue
One callback has two readers. The player needs a status word. The revenue job needs the stake kept out of the total it will later be asked to defend.
| What had already happened | History row | Revenue treatment |
|---|---|---|
| Debit succeeded, no win posted yet | Stake back, status void. Not a zero loss. | Drop the stake from GGR. |
| Debit never succeeded | No balance movement. Keep the rollback receipt so the retry stops. | Nothing entered the total, so nothing leaves it. |
| A win was already credited, then the void arrived | Leave the paid win until someone applies the rule you can show the player. | Park the credit on an exception line. Do not reverse it inside the export. |
| The same rollback is delivered again | Second delivery changes nothing on the balance. | Exclude the stake once, not once per delivery. |
Void handling
- 01
Status word
Show 'void' in history. Do not show a loss of zero that looks like a bug.
- 02
GGR
Exclude the voided stake and any reversed win from the revenue line.
- 03
Late void
Queue a void that arrives after a credit for someone to check. Do not auto-debit the player.
Do not award a result the studio withheld
A shoe that stops with cards face up is still unfinished. Paying the 'obvious' hand because the last video frame looked clear will not match the studio's void, and the player will quote your balance against a history row that says the hand never completed.
A shoe that stopped at 22:07
Speed blackjack, 42 players at the table, stakes totalling €3,180 across the hands in play. At 22:07 the dealer's stream drops and does not recover, and the studio voids every open hand. Rollbacks start at 22:08:14, one per staked hand, each naming the debit it reverses. Three of them reach a wallet whose debits had not yet committed, because those players staked in the last second of the betting window.
The wallet handles all three shapes without relying on a later retry. A committed debit is refunded and acknowledged. A rollback that names a debit still in flight writes an atomic cancellation record against that id in the same transaction as the acknowledgement; when that debit later arrives at commit, it reads the record and refuses to settle, so the money never moves twice. A debit that genuinely failed takes the rollback as a no-op, records the receipt against the named id and returns success, so the studio stops sending it. By 22:09:40 all 42 hands are closed and the shoe's stake total is zero.
That race is a test, not a hope. Pause a debit between validation and commit, deliver the rollback while it is paused, then release the debit and assert that exactly one of the two outcomes happened: the debit never committed, or it committed and was reversed inside the same atomic step. If the only thing that reverses an in-flight debit is a retry arriving after the acknowledgement, a lost retry leaves a stake behind that nobody is looking for.
The failure that followed was not in the wallet but in the wagering ledger. Those 42 rounds had counted towards a bonus requirement as they settled, at the table's game-type weight, and the void did not remove them. A player cleared part of a requirement on hands that never happened. A void has to reverse the contribution with the stake, from the same callback, rather than through a nightly recalculation that never runs.
The sequence, and the record each step leaves
| Moment | What arrives | What the wallet stores |
|---|---|---|
| T+0 | Debit for €75 with a transaction id | The id, the amount, the decision and the balance after it |
| T+67s | Studio voids the hand: rollback naming that debit id | The refund or cancellation record, the acknowledgement, and the link from rollback to debit |
| T+68s | The paused debit reaches commit | It reads the cancellation record and refuses to settle, so there is nothing to reverse later |
| T+69s | The same rollback again, because the first ack was lost | No second movement; the repeat delivery returns the stored success |
| T+90s | A rollback for a debit that never committed | An explicit no-op receipt, so the retry loop ends |
| T+1 day | Player asks why a hand is missing from history | Void status, stake returned, and no win attached to the round |
FAQ
Questions operators ask
Does the player need a new round id after a void?
No. The void closes the original round. The next hand or spin is a new round with a new id.
Should a returned stake still count as a loss on the reality check?
No. Session net uses the same wallet lines as history. A voided stake is not a loss and not a win. Leaving it inside the net figure shows the player a deficit the cashier has already undone.
Who writes the void sentence the player sees?
The studio owns the outcome. You map it onto a short list of words your history already uses. Do not print the studio's internal code, and do not add a cause the callback did not carry.
Does a voided hand still count towards bonus wagering?
It should not, and the place to fix that is the callback that returns the stake. If the contribution is reversed only by an overnight job, a player who moves to another game carries a requirement they have met on paper and not in fact, and support is left explaining the gap.
What if a rollback arrives while the debit is still in flight?
Record an atomic cancellation against the transaction id in the same commit that acknowledges the rollback. When the debit arrives, it must read that record and refuse to settle. Do not depend on a later retry to reverse it, because a lost retry leaves the stake behind with a success already sent to the studio. Test it by pausing the debit, delivering the rollback, then releasing the debit and asserting that only one balance movement survives.
What if a void arrives after the studio has paid a win?
That is an exception for a person, not an automatic debit. Reversing a paid win can leave a balance negative through no action of the player. Park the amount, keep the round visible with both events on it, and apply a rule you can show the player before anything is taken back.
Keep reading
Related pages
- Product · WalletWalletBalance, bet, win and rollback on one seamless wallet: idempotent transaction ids shared by casino games and sportsbook alike.Read
- Product · Live dealerLive casinoRoulette, blackjack, baccarat, game shows, teen patti and andar bahar on one dealer-table wallet and one GGR report, per licensed market.Read
- Guide · WalletCallback timeoutsA wallet timeout is a missing answer, not a refusal: a late debit gets voided and a late credit gets retried by the studio.Read
- Guide · SupportRound historySupport can search a disputed round by id, stake, credit and status. A player's screenshot is not a lookup key; the round id is.Read
Get a written quote and sandbox access
Tell us your licence, target markets and products. You get the GGR rate in writing, the studio list for your markets and sandbox credentials.