The complaint packet
Make your casino complaint easy to investigate
The first paragraph should tell a reader what happened, what remains unresolved and what you want corrected. The attachments should let that reader check those statements without searching through your entire account history.
Keep a complete private record. Create a separate redacted version if you publish the complaint. These two copies serve different purposes: investigation needs usable references; a public account of the problem usually does not.
Put the disputed event on one page
Identify the casino and the affected transaction or account decision. Record the amount and currency, the relevant date with timezone, the current status and the last answer from support. Then state the requested correction: trace a missing transfer, review a rejected document, explain a deduction or restore an amount that the records show was removed in error.
Separate what you observed from what you suspect. 'The withdrawal screen says completed and my receiving account has no matching credit' gives an investigator two records to compare. 'The casino stole my money' does not identify the missing payment stage.
Do not delay this summary until the end of a long story. Details belong in the chronology and attachments, where they can support the claim.
A chronology records changes, including the gaps
| Event | What to write | Evidence to retain |
|---|---|---|
| Request or decision | Amount, currency, method, time and exact displayed status | The original account entry or notice |
| Requirement received | What the casino requested and whether it said the request blocks payment | The complete message and relevant term |
| Your response | What you sent, when and through which channel | Submission acknowledgement and submitted copy |
| Casino reply | The review outcome, explanation or promised next action | The written reply and ticket reference |
| Transfer or correction | What changed in the account and what arrived at the destination | The balance ledger and receiving-account entry |
Leave a missing event marked unknown. An upload acknowledgement cannot fill the review-outcome row, and a completed withdrawal label cannot fill the receiving-account row.
Attach proof for the actual dispute
| Disputed point | Useful records | Question they should answer |
|---|---|---|
| Withdrawal delayed | Request history, payment term and support replies | What is the last confirmed payment stage, and what remains outstanding? |
| Marked paid, not received | Completed entry, sending reference and destination history | Was a transfer sent to the correct destination, and was it credited? |
| Verification rejected | Document request, submitted copy, acknowledgement and rejection reason | Which requested field or format was not satisfied? |
| Bonus balance deducted | Accepted offer version, bonus ledger and relevant bets | Which clause and recorded action explain the deducted amount? |
| Account locked with a balance | Last balance, access error, restriction notice and support contact | What money remains, what restriction applies and how can it be reviewed? |
| Withdrawal cap changed | Earlier and later cap views, request history and the casino's explanation | Which condition governs the affected request, and what changed? |
Send the relevant slice of history, with enough context to make it intelligible. An unrelated deposit list or a cropped reply can make the decisive event harder to identify.
Keep originals private; prepare public copies deliberately
Preserve complete originals
Keep the original captures, downloaded statements and messages securely. Record when and where they were obtained. Work on copies when making annotations or redactions.
Remove account access details
Public copies should not expose email addresses, account names, passwords, login codes, recovery material or support links containing access tokens.
Remove financial identifiers
Hide bank and card details, wallet addresses, transaction hashes and account references from public attachments. Keep usable identifiers in the private investigation packet.
Protect identity documents
Do not post a passport, selfie, address document or full financial statement publicly. Explain which document was requested and what the rejection said without showing the document itself.
Inspect every public image
Open the exported copy at full size. Check chat headers, browser tabs, notification overlays and reflected details as well as the main content. Confirm the exported pixels actually hide the information.
Keep the event readable
After redaction, the public copy should still show the relevant status, amount or wording. If it no longer supports the statement, use a plain description and reserve the original for private review.
A blockchain receipt has a specific job
Write a request the recipient can answer
Start with the short dispute summary and the relevant reference. Point to the chronology and name the attachment that supports each disputed event. Ask for the specific review or correction, together with a written reason if it is refused.
For a missing payment, request the sending route, reference and time. For a deduction, request the applied clause, rule version, relevant bets and calculation. For rejected verification, request the remaining defect and accepted correction. Asking five unrelated questions at once makes a generic reply easier.
Retain the complaint acknowledgement and stated next step. If the reply overlooks a record, identify that record in your follow-up. If a promised update is missed, add the promise and missed update to the chronology rather than repeatedly opening a fresh chat.
Before handing the packet to someone else
Check that the recipient handles this casino and this kind of complaint, and read its submission rules. A public forum, a payment provider and a dispute service need different information and have different powers. A forum post cannot itself trace a bank transfer or order payment.
Use the complete private packet only through the recipient's intended secure channel. Publish the redacted summary separately if appropriate. Keep the same chronology in both versions so later corrections do not create contradictory accounts.
For a dispute involving a casino in another jurisdiction, use the cross-border complaint guide to identify the route before sending sensitive material. This evidence packet does not supply a universal complaint deadline or guarantee recovery.
Record the outcome precisely
Update the record when verification is accepted, access is restored, a deduction is corrected or a transfer arrives. These are separate outcomes. If only part of a withdrawal was received, record the amount received and the amount still outstanding.
A complaint marked closed can mean several things, including a withdrawal of the complaint. Preserve the reason for closure. Do not turn a green account status, a casino promise or a mediator's status label into a payment receipt.
Practical questions about complaint records
What if a live chat disappeared?
Record when the chat occurred, what you can still substantiate and that the transcript is missing. Request a copy through support. Do not recreate a quotation from memory and present it as an original message.
Should I send every screenshot I have?
Select records that support the disputed events, retaining the complete originals privately. A small indexed packet is easier to investigate than many unexplained images. Include surrounding context where a cropped view would change the meaning.
Can I remove a name from a verification document?
A public copy should protect identity information. For the private verification submission, ask which redactions the reviewer permits; removing a required holder field may make the document unusable. Keep those two copies separate.
What proves that a withdrawal was resolved?
For a payment dispute, retain the actual receiving-account credit and reconcile its amount with the outstanding request. If fees, conversions or instalments are involved, document them rather than assuming that one incoming entry resolves the full balance.
Continue with the question that matters
- Find the stalled withdrawal stage
Identify the missing handoff before writing the payment complaint.
- Reconstruct a bonus deduction
Connect the rule, relevant bets and removed amount.
- Read documented casino disputes
Check the evidence and outcome behind each case.
Last updated:Checked by: Karssen Avelar