Player game bench
A frozen reel, closed live table or dropped connection does not by itself show whether a wager failed. The useful question is whether the server accepted and settled a specific round. Game history, balance history and a round identifier let support find that event without relying on memory or a screenshot of the final animation.
Open the current casino accountOpen game history and account transaction history before starting another round. Record the title, provider, stake, currency and approximate time. Look for a completed, cancelled, refunded or still-open entry. A changed balance is a clue, but the ledger state is the stronger record because a delayed animation can differ from server settlement.
The label may be Round ID, Game Number, Bet ID, Play Session ID or Transaction ID. It can sit behind a clock icon, game menu, bet archive or expanded transaction row. Copy the full value rather than typing it from memory. Also retain the account-side transaction reference when it differs from the provider round number.
Keep the identifier, UTC or local timestamp with timezone, stake, displayed outcome and before/after balance. Add one uncropped screenshot of the game-history row and one of the account ledger. Never include a password, one-time code, full payment number, wallet seed phrase or private key; none is needed to locate a casino round.
State whether the round is missing, marked complete with the wrong credit, or shown twice. Ask for the settlement state and provider reference, not a general promise that the game is fair. If the first reply discusses another event, answer with the same round ID and request escalation against that exact record.
Not automatically. Check whether the server accepted and settled the round in game and account history.
Look in game history, a clock or menu icon, the bet archive, or an expanded transaction record.
No. A round case needs identifiers and non-sensitive transaction facts, never passwords or security codes.
Last reviewed: 30 July 2026