Why a pack rather than a story

Complaints handlers and adjudicators work from documents. A narrative describes what you believe happened; a pack shows what happened and when. The same six items satisfy the operator’s complaints team, the ADR provider and, if needed, a regulatory report.

Assembling them once also stops the story drifting. Every stage of the route reads the previous one, and the fastest way to weaken a strong case is to tell it slightly differently three times.

Most of the pack is material you already have or can capture in ten minutes. The expensive part is the dated copy of the terms, and that is only expensive if you did not save it when you deposited.

Item one: the terms you accepted

The version that governs a dispute is the version in force when you accepted it. A live page is evidence of current policy and nothing more, and operators edit pages in place without leaving a trace of the previous wording.

Save the general terms, the withdrawal section and the specific bonus terms as dated PDFs or full-page captures. If you did not, say so plainly rather than quoting today’s page as if it were the old one; an honest gap is better than an argument built on the wrong document.

Where the operator quotes a clause, compare it word for word with your copy. A difference in wording is the strongest single point available to a customer, because it is documentary rather than argumentative.

ItemWhat it provesHow to capture it
Dated termsWhat you actually agreed toPDF or full-page capture on the day
Cashier recordThe status and the amountsScreenshot with the status wording visible
Request-and-supply listWhether requirements closedTwo columns with dates
Correspondence threadWhat was promised and whenOne email chain, or transcripts
Payment recordThat money moved, and howBank or wallet entry with reference
ChronologyThe shape of the caseOne page, dated, in order

Item two: the cashier record

Screenshot the cashier with the status wording visible, including the request date, the amount, the method and the reference if one is shown. Capture it at each change of state rather than only at the end.

Copy the wording exactly into your notes as well. Pending, processing, under review, approved, declined and failed are different states in an operator’s own systems, and paraphrasing them loses the only clue about where the matter sits.

If the account is later closed or restricted, these screenshots become the only record of what the account showed. Capture them while you can still log in.

Item three: the request-and-supply list

Two columns: what the operator asked for and when, and what you supplied and when. Nothing else. This is the single most useful document in a verification or withdrawal dispute because it shows whether the requirement set closed or multiplied.

A list that shortens round by round describes a functioning process, even a slow one. A list that grows after each submission describes a holding pattern, and that distinction is exactly what an adjudicator is assessing.

Include the channel and the file names you sent. Operators do lose attachments, and a documented upload is the answer to a later claim that nothing was received.

  • One row per request: item, date asked, date supplied, channel.
  • Record file names and the portal or address used.
  • Note any item requested twice and whether a defect was stated.
  • Note each quoted timescale and whether it was met.
  • Keep it factual: no commentary in the list itself.

Items four and five: correspondence and payments

Keep correspondence as one thread wherever possible. A single email chain is self-dating, shows the order of exchanges and needs no explanation. Where chat was used, obtain the transcript at the time or make a dated copy before closing the window.

The payment record is the bank, card or wallet entry that shows the money moving, with the reference intact. For wallet routes the wallet entry is the relevant one; the bank only saw the wallet being funded.

Redact balances and unrelated transactions when sending a statement extract, and leave the relevant entry, its reference and its date untouched. Removing the reference is the most common way a customer makes their own trace impossible.

Item six: the one-page chronology

Write the case as a dated list of events on a single page: deposit, bonus opt-in if any, play, withdrawal request, each status change, each request for information, each response, the decision. No adjectives.

Put the requested remedy at the bottom in one sentence: release the payment, reinstate the balance, correct the status, provide the clause relied on. A remedy that can be granted is more likely to be granted than a complaint about treatment.

Reuse this page unchanged at every stage. It is the index to the pack, and consistency across stages is worth more than any individual document.

What to leave out

Leave out everything that does not decide the question. Forty screenshots of a game lobby, a forty-minute transcript, your account history in full and your feelings about the operator all add volume and subtract clarity.

Leave out personal data the purpose does not need. Full identity documents, unredacted statements and anything containing card numbers should not circulate; send only what was asked for, through the channel that was named.

And leave out threats. They change nothing about the merits and occasionally close the channel the case depends on.

  1. Save the terms, dated, the day you deposit.
  2. Screenshot the cashier at every status change.
  3. Keep the request-and-supply list as you go.
  4. Keep one correspondence thread; get chat transcripts at the time.
  5. Write the one-page chronology and reuse it unchanged.

Keeping the pack safe

Store it outside the operator’s systems — your own files, not the account. Accounts get closed, restricted and emptied of history during disputes, and material you can only see while logged in is material you may lose.

Name the files so that the dates are visible without opening them. An adjudicator reading a bundle of clearly named, dated files forms a very different impression from one unpacking a folder called screenshots.

FAQ

What if I did not save the terms?

Say so, and work from what you have. Do not quote today’s page as the version you accepted; an honest gap is stronger than an argument built on the wrong document.

How much should I send?

Enough to decide the question and no more. The six items are the pack; the archive stays in reserve in case something is challenged.

Should I send a full bank statement?

Only if asked, and redact unrelated entries and balances while leaving the relevant transaction and its reference intact.

Is a screenshot good enough?

Yes, if it shows the status wording, the amount, the date and the account. Capture it at the time rather than reconstructing later.

Where should the pack live?

In your own files. Accounts are closed and histories disappear during disputes, so anything only visible when logged in should be saved first.

Next pages

Sources

Sources reviewed 18 November 2026. Check the current regulator page, operator terms and logged-in cashier before relying on a process.