Define the complaint and requested outcome
A useful complaint states what happened, which term or transaction is disputed and what resolution is requested. Separate withdrawal delay, verification, bonus removal, account closure and game-result issues rather than combining them into one accusation.
Keep the language factual. Dates, references and copies of the relevant terms are more persuasive than repeated messages or threats. Do not include passwords, authentication codes or complete payment credentials.
Build the evidence file
Create one timeline from registration to the disputed event. Keep original files and note when each screenshot or message was created.
| Evidence | What it should show |
|---|---|
| Account and transaction details | Username, registered email, amount, method and transaction reference. |
| Applicable terms | The dated rule for the bonus, withdrawal, verification or account action. |
| Cashier records | Deposit, balance and withdrawal status with timestamps. |
| Verification records | Documents requested, upload confirmation and review responses. |
| Support messages | Ticket numbers, explanations and promised dates. |
| Payment-provider records | Receiving account statement or trace showing whether payment arrived. |
Use the operator’s formal process
Start with support for a simple operational issue, but move to the complaints address or form named in the terms when the normal window passes or the explanation is disputed. Mark the message as a formal complaint and request acknowledgement, a reference number and a final written response.
Ask the operator to cite the exact term and evidence behind any decision. If a document is missing, request its name and secure upload route. If a payment is marked sent, request the traceable reference and release date.
- Short summary of the disputed event
- Chronological list of material dates
- Transaction and support references
- Relevant term or promotion version
- Supporting screenshots or statements
- Specific outcome requested and reasonable response date
Escalate to the correct external route
The next route depends on the licence and contract. Verify the exact operator, domain and licence in the regulator’s own register. Follow any named dispute or regulator procedure and include the operator’s final response where required.
A UKGC or UK alternative dispute route should not be presented as available for an overseas casino unless the exact operator and domain are covered. Overseas regulators differ in whether they accept individual complaints and what remedies they can order.
Keep following the same reference instead of creating a new complaint for every reply. Record acknowledgement dates, deadlines and the name of the team handling the case. If the operator requests more time, ask what work remains and when the next written update will arrive. A status update is useful only when it identifies a real step, such as document review, transaction tracing or a final account decision.
Avoid complaint and recovery scams
Be cautious when an unknown service promises guaranteed recovery, asks for an upfront release fee or requests control of a bank account or crypto wallet. Never share a seed phrase, private key, password or one-time code. A regulator does not need remote access to the player’s device to review a written complaint.
Do not create altered screenshots, false documents or public accusations that cannot be supported. Preserve evidence and use the formal route. If personal or payment data may have been stolen, contact the relevant financial provider and local reporting service separately from the casino complaint.