Assemble the file before you address anyone

What belongs in the file

Nine items. Not all of them apply to every dispute, but each one either proves a fact or rebuts a likely answer.

• Transaction identifiersThe operator, the payment provider and the dispute body all search by reference rather than by description. An amount and a date is an anecdote; a reference is a record.
• A dated copy of the terms in forceThe governing version, not the current pages. This is the single most decisive document in a terms dispute and the one most often missing.
• The bonus or promotion text as it stoodTerms on a promotion can change after the fact. A dated copy, showing the maximum bet, the weighting and the expiry as they were, settles the argument that the rule existed when you played.
• Full correspondence, in orderThe decision-maker reads what the operator already told you. A tidy message list shows both what was asked and what was avoided.
• Account statements and balance historyDeposits, withdrawals, bonus credits and adjustments, with dates. Shows the arithmetic and where the balance went.
• Screenshots with the URL and clock visibleA screenshot without a visible address and time cannot be placed. A full-window capture with both visible is self-authenticating enough to be considered.
• Round or game records, where the dispute is about a roundA game record is provable in a way that an impression of a game is not. Where a bet identifier or round hash is published, keep it.
• The licence details of the operatorWhich authority licenses it decides which complaint rules apply, whether an independent dispute body is mandatory, and which regulator can act.
• The remedy you are asking forOne sentence, with the amount and the transaction. Written down early so that the escalation does not drift into a different request.

Two of those are worth collecting even when nothing has gone wrong: the dated terms copy and the licence details. They take minutes to obtain while you are logged in and reading calmly, and they are the two items people most reliably cannot reconstruct once a dispute begins.

How to capture it so it counts

A capture is only useful if a stranger can tell what it is. Four habits do most of the work:

1. Show the address and the clock. A full-window screenshot that includes the page address and the system time places the evidence on a page at a moment. A cropped image does neither, and invites the reply that it shows something else.
2. Keep the original file, do not retype the numbers. Exports, downloads and saved pages carry as much as their contents. Retyping an identifier into a message introduces a chance of error and removes the original.
3. Record times as the platform shows them. Operator logs are usually kept in one time zone. If you convert, say so explicitly and note both, so a mismatch in timestamps is explainable rather than contradictory.
4. Number the pages of the file. A submission with a contents list — item, date, what it proves — reads as a file. A pile of attachments reads as an argument, which is a different thing.

Where a document only exists inside the account and cannot be downloaded, request it in writing. An operator that can produce a transaction log for its own investigators can produce it for you, and the refusal to do so is itself a recorded fact.

What is not evidence

Being clear about this saves effort. In a records-based process, the following carry close to no weight:

That second list is not a reason to give up. It is a reason to stop spending the complaint on arguments the process cannot answer, and to spend it instead on the three things it can: the term, the record and the clock.

A file you can hand over

When the file is assembled, the complaint itself becomes short. A working shape:

• One paragraph of facts, in date order, with identifiers.
• One paragraph of terms: the clause relied on, the clause misapplied, and the date of the version attached.
• One paragraph of remedy: the amount, the transaction, the action and the date asked for.
• A numbered attachment list: item, date, what it proves.
• Two requests: a final written response, and the name of the dispute body with its referral deadline.

That structure survives every rung above it unchanged — the same file is the referral submission and the exhibit list. Building it once is what makes escalation cheap.