Casino Complaint Checklist: Dates, Hashes, Screenshots, and Round IDs

If you need to contact casino support about a missing payout, a failed deposit, a game result issue, or an account-related problem, the fastest way to reduce back-and-forth is to prepare your evidence before you submit the complaint.

This checklist focuses on the details support teams usually need to review a case: exact dates, timezone, screenshots, round IDs, transaction IDs, and account history. If you are still at the preparation stage, it can also help to review this broader guide to online casino complaints and fixing common issues before sending your final message.

Before you open a support ticket, collect the core facts in one place. A simple note, document, or spreadsheet is enough.

Use this complaint-prep checklist:

If more than one event happened, create a separate line for each one. That makes it much easier to explain what happened and when.

Support teams often compare your report against account logs, game logs, payment records, and provider records. If your date or time is vague, they may need to ask follow-up questions before they can even start reviewing the case.

To avoid that, record:

For example, writing “March 5 around lunchtime” is much less useful than “2025-03-05, 12:43 PM, GMT+7, taken from my account transaction history.”

Consistency matters too. If you use local time in one screenshot and platform time in another, note that clearly. A small timezone mismatch can create a lot of confusion in deposit, withdrawal, and gameplay complaints.

A transaction hash is a unique string that identifies a blockchain transaction. In plain language, it is like a tracking number for a crypto transfer.

This matters most when your complaint involves:

If crypto is involved, the transaction hash can help support or payment teams verify:

Not every casino complaint needs a hash. It is mainly relevant for blockchain-based deposits and withdrawals. For card payments, bank transfers, or e-wallets, the useful identifier may instead be a payment reference number, receipt number, or processor transaction ID.

A round ID is a reference tied to a specific game round or spin. Support teams and game providers may use it to locate the exact play event you are complaining about.

This is especially useful when the problem involves:

Not every interface shows round IDs in the same place, and some may not show them at all. When available, you may find them in game history, bet history, transaction detail views, or support-exported records.

If you cannot find the round ID, still record the game name, approximate time, stake amount, and balance change. That combination can still help support narrow the event.

Screenshots are most useful when they show the full context, not just one cropped detail.

Where possible, capture the full screen and make sure the image includes:

Best practices:

If support later replies with a case number or ticket number, add that to your evidence folder or notes right away.

Once you collect the raw evidence, put it into a simple timeline. This helps support understand the sequence quickly.

A practical order is:

A simple timeline might look like this:

This structure is much easier to review than a long unformatted message.

You do not need a long complaint. Clear and specific is better.

Use this simple structure:

Example:

Depending on the platform and payment method, useful identifiers may appear in different places. Common places to check include:

You may find:

These fields are not displayed the same way on every platform, so check a few sources and keep notes on where each detail came from.

Before contacting support, make sure you have:

The goal is not to overload support with random files. It is to send a clean, chronological complaint package with the identifiers they are most likely to need.

A round ID is a reference for a specific game round, spin, or hand. Support or the game provider may use it to find the exact event you are reporting.

No. A transaction hash is mainly relevant for crypto deposits and withdrawals. Other payment methods may use a receipt number, processor reference, or transaction ID instead.

They should show as much context as possible, including the game or payment page, timestamp if visible, balance, amount involved, status message, and any visible IDs.

They use the timing details to compare your complaint against internal logs, payment records, and game records. Including the timezone helps reduce confusion.

You may find it in cashier history, account transaction pages, email receipts, payment provider confirmations, wallet records, or blockchain explorer entries, depending on the payment method used.

Yes, you can still report the issue with the details you have. It helps to clearly label what is confirmed, what is approximate, and what evidence is missing so support can review the case more efficiently.