Guide · Support
A dispute needs the round id, not a screenshot
Players describe rounds in studio names and feelings. Support can only search by id. The history view has to show the id, the game, the time, the stake, the credit and the status, in the currency of the session.
7 min readUpdated By the Turnkeyxgaming team
What 'I won and it disappeared' usually is
The common cases are a void, a credit that landed and was then wagered, a jackpot flag the player did not recognise as already included, and a bet on a different product entirely. None of those can be diagnosed from a cropped animation. Start from the wallet line. If the wallet shows a credit, walk the player through the balance after it. If the wallet shows a void, say void. If the wallet shows nothing, then escalate with the round id to the studio path.
Keep the history long enough for the complaint window you publish. A 24-hour history guarantees an argument with anyone who writes in on Monday about Saturday. You do not need to show every raw callback in the player UI. You do need them in the tool your agents use.
Give the player a short reference and the agent the full round id, the studio id and the brand. Search on the agent side should accept a paste of either id and land on one wallet line. If the search needs a date range before it will try, agents will guess the date from the player's memory and miss the line. Look up by id first. Use the time as a check, not as the key.
What the common complaint usually is
Start from the wallet line. The animation is a clue to which round they mean, not evidence of what was paid.
| What the player says | What the wallet line usually shows | What the agent says |
|---|---|---|
| The win vanished | A credit, then later stakes that spent it. | Walk the balance forward from that credit. Do not re-credit it. |
| The game took the stake and crashed | A void, with the stake returned. | Say void. Do not call it a loss of zero. |
| A jackpot never arrived | A flagged credit already included in the balance. | Point at the flag. The celebration and the line are the same prize. |
| Nothing was recorded | No debit and no credit for that round id. | Then escalate, with the id. Not before. |
The agent view
- 01
Id first
Put the round id on the agent view and let the player see a shorter reference.
- 02
Status words
Use settled, void and pending. Do not use a blank status.
- 03
Then escalate
Only send a round upstream when the wallet has no matching line.
Screenshots of the reels are not a ledger
A cropped animation cannot show a later stake, a void, or a credit that landed in the same second. Ask for the time and the game, find the id, and answer from the line. Request a replay only when that studio actually provides one.
A search box that said local and meant UTC
A player in Dhaka wrote in on a Wednesday about a hand played 'last night, about half eleven'. The agent typed Tuesday 23:30 into the search tool. The label on the field said local time, the column it queried was stored in UTC, and the two readings of the same round sat six hours apart. The search returned nothing, so the agent escalated to the studio path, which is where a diagnostic should only go when the wallet has no line at all.
The round existed. It had settled at 17:41 UTC, a 48 win on a 4 stake, and the balance had been spent at another table by 01:20 local. The escalation cost three days and a studio contact's afternoon, and the answer had been in a wallet row throughout. The player, meanwhile, was told twice that the case had been sent to the provider, which sounds like an admission that money is missing.
Test the search field against a round you already know, from a device set to a zone that is neither UTC nor the office's. Label the field with the zone it expects, or drop the label and treat the player's time as approximate. An agent needs a result from an id alone, from a player id across a wide window, and from whatever short reference you print. A date range should narrow a result, never gate it.
What a dispute ticket needs before it leaves the queue
Six fields. Missing any one of them is why a ticket goes around twice.
- Brand and player id together, since a player id alone can match a different brand on a shared wallet.
- The round id or the wallet transaction id. One of the two exists even when the studio offers no replay.
- The session currency, so the figures in the reply match the figures the player is looking at.
- The time in the zone the player used, converted once, with the conversion written on the ticket so the next agent does not redo it differently.
- The exact sentence the player has already been given, so a second reply does not contradict the first.
- What the wallet shows: debit only, debit and credit, or nothing at all. Only the third escalates on evidence.
FAQ
Questions operators ask
Can we replay the animation for the player?
Only if that studio provides a replay. Many do not. The wallet line is the source of payment truth either way.
Should the player-facing history show raw callback payloads?
No. Players need the game, a short reference, the time, the stake, the credit and a status word in the session currency. Raw callbacks stay in the agent tool, where the full round id and the studio id are searchable.
How far back does the agent tool have to reach?
At least as far as the complaint window you publish. If players may write in a week later, a tool that keeps a day will force every Monday ticket into an escalation that the wallet could have answered.
The player cannot find a round id and only remembers the game. What do we search on?
Player id across a window wide enough to include the session, then narrow by game id and stake. Ask for the balance before and after, which many players can read from a message or a screenshot of the chip. Treat every time they offer as approximate, and say so on the ticket so the next person does not trust it further.
Should the player see the studio's round id or only our reference?
Either works provided the agent tool accepts both and resolves them to a single wallet line. A short reference is easier to read out on a call; the long one is what an escalation needs. Do not print an id the studio will not recognise and then forward it to the studio as though it were theirs.
Keep reading
Related pages
- 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 · SupportStuck roundsLeave a frozen spin pending until you know whether the credit is in flight, voided or genuinely stuck, then escalate with the id.Read
- Product · WalletWalletBalance, bet, win and rollback on one seamless wallet: idempotent transaction ids shared by casino games and sportsbook alike.Read
- Guide · ArchitectureHow a casino API worksOne casino round traced end to end: catalogue, launch, wallet callbacks, settlement and the report line the next morning.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.