Working table
| Evidence item | Minimum fields | Suggested label |
|---|---|---|
| Transaction | ID, amount, currency, method, request time | E01-transaction |
| Status history | Exact label and timestamp | E02-statuses |
| Cashier/terms | Route, timing, limits, capture date | E03-terms |
| Operator message | Date, channel, sender, full relevant text | E04-support |
| Bank/wallet record | Date, amount, masked destination, status | E05-receiving |
| Verification | Request, submission receipt, acknowledgement | E06-verification |
Start with a claim statement
Use four sentences: what happened, what should have happened under the cited term or process, what impact remains, and what remedy is requested. Separate facts from inference. “Status changed to processed at 14:02” is a fact; “the operator sent the transfer then” is an inference unless supported by a rail reference.
Use GBP amounts exactly as shown. If currency conversion occurred, record the original and converted amounts and who performed the conversion.
Build a chronology before adding attachments
Give each event a date and time zone, actor, event, source and evidence ID. Include the withdrawal request, every status change, document request, submission, acknowledgement, operator decision, payment reference and receiving-account posting. Note gaps instead of filling them with assumptions.
Keep the chronology stable. Corrections should be dated so an ADR reviewer can see what changed.
Preserve originals and share redacted copies
Keep original emails, PDFs and screenshots in a read-only archive if practical. Work from copies. Redact passwords, full card numbers, security codes, unrelated transactions and unnecessary identifiers, but leave enough context to authenticate the record. Do not alter the substance of a message or transaction.
File names should describe evidence rather than conclusions: E04-2026-11-10-support-chat.pdf is stronger than proof-they-lied.pdf.
Map every request to evidence
In a short index, list the issue, supporting evidence IDs and remedy. If the operator disputes a fact, place its contrary evidence alongside yours. An honest record that shows uncertainty is more credible than a file that hides inconvenient details.
Before ADR submission, check its current file formats, size limits, deadlines and remit. Keep the operator’s final response or deadlock letter as a separate indexed item.
A practical sequence
- Write the issue and requested remedy in plain language.
- Create a dated transaction and communication chronology.
- Assign stable evidence IDs to original and redacted copies.
- Link each factual claim to one or more evidence IDs.
- Export a clean pack and keep the working archive private.
Great Britain scope
This guide is for adults in England, Scotland and Wales dealing with businesses licensed by the UK Gambling Commission. It does not cover Northern Ireland. Payout Case is editorial and does not rank operators, publish offers, accept gambling accounts or receive referral payments.
Frequently asked questions
Should I send every chat transcript?
Send material that establishes the issue, response and unresolved points. Index full transcripts where relevant; avoid an unlabelled dump that makes the key evidence hard to find.
Can I redact a bank statement?
Often yes for unrelated data, but keep the account holder, relevant dates, transaction and identifying ending needed for the dispute. Ask the recipient what must remain visible.
What if I do not have a screenshot of an old status?
State that gap. Use transaction logs, emails or later acknowledgements, but do not recreate a screenshot or present memory as a contemporaneous record.
Related guides
Complaint process · Withdrawal statuses · Payment verification · Privacy notice
Sources
Sources reviewed 16 November 2026. Check the current regulator guidance and the business’s own terms and complaint procedure.


