Guide · Support
A stuck round is pending until someone proves otherwise
Players say the spin froze. Sometimes the credit is in flight.
7 min readUpdated By the Turnkeyxgaming team
Collect the id, then wait for the status
Sometimes the round is voided a minute later. Sometimes it is genuinely stuck. The wrong move is to credit them 'to be kind' before you know which.
Take the player id, the round id, the time and the game name. Look at the wallet. A debit with no credit is pending. Leave it pending and ask for status. If you credit a goodwill win and the studio then sends the real credit, you pay twice. If you refund and the studio sends a win, you pay the win and the refund. Goodwill, if you offer it, comes after the round is closed and is labelled as goodwill.
Escalations need the studio id as well as the round id. A queue that says 'slot frozen' will be routed badly. Include whether the player has already been told anything. When the status arrives, apply the rollback or the credit once, and write to the player in the same words the status uses.
Write the wait before escalation separately for slots, live and crash. They do not go quiet at the same speed. A single threshold either pages during a normal retry or leaves a live player on a frozen shoe. While you wait, leave the balance as the wallet has it. Goodwill, if your policy allows it, is a labelled credit after the round is closed, never a way to close the round.
What you may do to the balance while the round is open
Pending means the studio has not finished. An early payment assumes an outcome you do not have.
| Status you can prove | Balance action | What you tell the player |
|---|---|---|
| Debit taken, no credit yet | Leave it. Do not refund and do not pay a win. | The round is pending. You have asked for status. |
| Studio says void | Apply the rollback once, if the debit succeeded. | Void, in that word. Stake returned if it was taken. |
| Studio says settled, credit in hand | Acknowledge the credit once, on the original id. | Settled, and show the line. Do not add a second courtesy credit. |
| Round closed, and you still want to make a gesture | A separate goodwill credit, labelled as such. | Goodwill. Not a correction of the round, which is already finished. |
While the round is open
- 01
Do not pay early
Do not manual-credit a round that is still pending.
- 02
Full ids
Escalate with player, brand, studio, game and round id.
- 03
Same words
Tell the player the status you received: settled, void or still pending.
Kindness before the status pays the round twice
A manual win followed by the studio's real credit is two payments. A refund followed by that credit is a refund plus a win. Apply the one callback once the round is closed, and only then consider a labelled goodwill credit.
Worked example
A live round that never credits: the first ninety seconds
At 00:00 the debit for €25 lands and the player sees the bet accepted. At 00:05 the result screen does not appear. At 00:30 support opens the round and sees a debit with no credit, so it stays pending. At 00:75 the studio returns a void for that round id, and the wallet applies the rollback once. At 00:80 the player is told the round was void and the stake is back. No goodwill credit is paid while the round is open, because the status could still have been a win.
If the studio had returned a settled result instead, the credit would be applied once against the original transaction id and the player would be told the round settled. The timeline is the point: the action changes with the status, not with how long the player has been waiting or how upset they are. Set separate thresholds for slots, live and crash, because they go quiet at different speeds.
What happens while the round is pending
| Time | What is known | What the wallet does |
|---|---|---|
| 00:00 | Debit accepted | Nothing beyond the debit |
| 00:05 | No credit, no result | Leave the round pending; do not refund |
| 00:30 | Support has the round id | Ask the studio for status |
| 00:75 | Studio says void | Apply the rollback once |
| 00:80 | Player informed | Show the void and the returned stake |
FAQ
Questions operators ask
How long should a round stay pending before we escalate?
Long enough for a normal retry to land, and not so long that the player is ignored. Set that threshold in the support runbook for live, slots and crash separately. They do not fail at the same speed.
Can two agents both 'fix' the same pending round?
Not safely. One callback, applied once, is the settlement. A second agent who refunds while the first is still waiting will meet the studio credit later and pay both. The runbook should name a single owner for that round id.
What has to be on the escalation, besides 'the spin froze'?
Player, brand, studio, game and round id, plus the time and whether you have already promised the player anything. A queue line with only the symptom will be routed to the wrong studio, and a promise you forgot to mention will be paid again when the credit lands.
Can support refund the stake before the studio answers?
Not safely. If the studio later sends a win, the player has both the refund and the win. Wait for the status, apply one callback, and keep any goodwill credit separate and labelled.
Keep reading
Related pages
- 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
- Guide · WalletVoids and rollbacksWhen a studio voids a round, the rollback returns exactly the stake the debit took, keyed to the original transaction id.Read
- Guide · OperationsOne studio offlineIf one studio fails, mark that studio unavailable and leave every other studio launchable. A lobby-wide outage is a choice.Read
- Product · WalletWalletBalance, bet, win and rollback on one seamless wallet: idempotent transaction ids shared by casino games and sportsbook alike.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.