Quick answer: when a casino round looks wrong or disappears, do not rely on the animation or the balance alone. Record the exact game label, date and time zone, stake, displayed result, round or session ID, wallet transaction ID, and the balance before and after the event. Compare the game-history record with the account transaction before you contact support.
This casino round ID dispute checklist is platform-neutral. It does not identify a SuperAce88 provider, game-history menu, result, licence, refund rule or support outcome. Menu names and identifiers vary by operator and provider, so copy every label exactly as it appears on the account you are reviewing.
Make one decision before you do anything else
Your first task is not to prove that a round was unfair. It is to determine which record is missing or inconsistent. A disputed event usually falls into one of three evidence states:
- No game record: the screen showed activity, but the round does not appear in the available game history.
- No wallet record: the game history shows a round, but there is no matching debit, credit, refund or adjustment in the account history.
- Records disagree: both records exist, but the amount, status, result, timestamp or identifier does not align.
Pause further play while you capture the evidence. New rounds can add more entries and make a simple one-round question harder to explain. If the screen froze, showed an error or displayed a rollback label, use the separate interrupted-round workflow rather than assuming the round won, lost or failed.
Build the one-round evidence map
Start with the game record and work outward. Some operator help pages show that different providers use labels such as round ID, game number, play session ID or transaction ID. Those examples demonstrate variation; they do not prove where any identifier appears on SuperAce88.
| Evidence field | Where to look | What to save exactly | Why it matters |
|---|---|---|---|
| Game identity | Lobby tile, game information panel or history row | Displayed title, provider label and any game ID | Separates similarly named games and prevents a support search against the wrong record |
| Round identity | Game history, result details or replay panel | Round, hand, game, spin or session ID with its label | Lets the operator or provider locate one event instead of searching a whole session |
| Time | Game record, device clock and account history | Date, exact time, displayed time zone and capture time | Explains apparent ordering differences and narrows the transaction search |
| Wager and result | Accepted round details | Stake, currency, selections or actions, displayed result and payout | Defines what was accepted and what the interface later reported |
| Wallet movement | Account statement or transaction history | Transaction ID, debit, credit, refund or adjustment, status and balance | Connects the game event to the account-side money record |
Save a full-screen screenshot showing the source and timestamp, then make a cropped copy for sharing. Keep the original privately. A crop should not remove the identifier or context needed to understand the row.
Do not treat every identifier as the same thing
A session can contain many rounds, and an account transaction can represent a stake, result, refund, reversal or transfer. A round ID may identify one game cycle, while a session ID groups activity and a wallet transaction ID identifies an account entry. Preserve the labels instead of renaming everything “transaction number.”
DraftKings, for example, describes a first-party route from an account transaction to hand or spin details and a transaction ID. Cloudbet provides provider-specific examples of where a round identifier may appear. These are useful examples of record structure, not universal menu instructions.
Create a timeline that separates facts from assumptions
Write the sequence in the order observed. Use one row per event, including reconnects and later status changes. Do not write “win removed” when the evidence only shows that an animation appeared and the next balance was lower.
| Time and zone | Source | Identifier | Observed fact | Question still open |
|---|---|---|---|---|
| 14:03:11 PHT | Game screen | Round R-001 | Stake displayed as 20.00; result animation appeared | Was the displayed result committed to the server record? |
| 14:03:18 PHT | Game history | Round R-001 | Status shown as completed; payout field shown as 0.00 | Does the provider record contain more detail? |
| 14:03:20 PHT | Wallet history | Transaction T-002 | One 20.00 debit shown; no separate credit visible | Is T-002 linked to R-001? |
The identifiers and amounts above are hypothetical. They show how to write a neutral chronology, not how any real platform records a round.
Use the mismatch matrix before escalating
| Mismatch | What the records establish | What they do not establish | Next safe action |
|---|---|---|---|
| No round in game history | The available history does not show the event in the checked range | That no wager reached the server | Save the range, filters, screen, balance entry and exact time |
| Round exists; wallet entry missing | A game record exists | That money was lost, paid or refunded | Check time zone, account range and pending/adjustment entries |
| Same amount appears twice | Two rows share an amount | That both are duplicate debits | Compare IDs, type, status and any reversal link |
| Animation and record disagree | The visual and recorded result differ | Which one is authoritative or why they differ | Preserve both and request a round-level review |
Prepare a privacy-safe support request
Once the packet is complete, open a route you verified independently. The support and transaction-record guide explains how to preserve the case ID, transcript and promised next step. The account-security guide covers route verification and phishing stops.
Please review round [exact ID] for [displayed game title]. The event time was [date, time and zone]. Game history shows [exact status and result], while account transaction [exact ID] shows [debit, credit or status]. I have attached redacted screenshots that preserve the labels and timeline. Please confirm which records were linked, the recorded round outcome, and the next case reference.
Never send a password, PIN, OTP, recovery code, seed phrase, private key, full card number or remote-access permission. Redact unrelated transactions and identity data when the verified request permits it.
Set a responsible-entertainment stop condition
Do not place more wagers to “test” whether the balance corrects itself, and do not chase a disputed amount. Pause until the records are understood. If the dispute or loss is creating pressure to deposit again, borrow, recover losses immediately or continue beyond your limit, stop play and use the options in the responsible gaming and self-exclusion guide.
Frequently asked questions
What if no round ID is visible?
Save the exact game title, displayed provider label, date, time zone, stake, result, balance movement and the history range you checked. Ask verified support which identifier it needs. Do not invent an ID or borrow one from a nearby round.
Does a win animation prove the official result?
No. It proves what the client displayed. Compare it with the game-history result and wallet record, then ask for a round-level review if they disagree.
Which timestamp should I record?
Record every displayed timestamp with its time zone, plus the device capture time. Account history and game history may use different zones or posting times.
Can one wallet entry cover several game events?
It can depend on the account design. Do not assume a one-to-one match. Preserve round, session and transaction labels so support can explain the relationship.
Does this checklist guarantee a correction or refund?
No. It produces a clearer evidence packet. The applicable rules, server records and reviewed account entries determine the outcome.
Primary reference sources
- Cloudbet Help Center: How to check whether a round completed and find its ID
- DraftKings Help Center: Viewing casino hand or spin results
- UK Gambling Commission RTS 1: Customer account information
Source boundary: Cloudbet and DraftKings describe their own interfaces. UK Gambling Commission standards apply in their stated jurisdiction. These references do not establish SuperAce88 provider relationships, menus, licence status, round results or refund rules.
