What actually decides a dispute

Entry 01A dispute is decided on records, not on feelings

Every route in this desk — the card chargeback, the terms dispute, the conduct complaint — is decided on the records each side can produce. The network does not know whether a charge felt wrong; it knows the reason code you filed, the authorisation it can see, and the evidence the merchant filed in response. That does not make the system unfair, it makes it documentary: the side that kept the clearer, timestamped trail tends to win, and the side that relied on memory tends to lose. The practical consequence is that what you do before a dispute matters — keep confirmations, note the dates, screenshot the ledger — because that is the material you will file.

Entry 02The records the operator brings

An operator responding to a dispute usually files a set of core records. The transaction record shows the amount, the method, the timestamp and the reference. The authorisation and session data show that the payment was approved from a device and session linked to the account, which is what defeats a “it was not me” claim. The terms version accepted shows what the account agreed to, with a date. And the play history shows what the deposit bought — whether the balance was used, how, and what came of it, which is what defeats a “I got nothing for it” claim. Together they argue that the charge was authorised and the service delivered.

Entry 03The records you bring

Your side is the mirror. The transaction reference and the statement line establish the charge and its date. Your correspondence with the operator — ideally in writing and from the account email — establishes what you raised and when. Screenshots or exports of the account ledger establish what your balance actually showed. And the ground of your dispute establishes which of the operator’s records are even relevant: if you claim non-receipt, the play history is central; if you claim an unauthorised charge, the authorisation data is. The single most useful habit is to raise issues in a channel that leaves a record, because a phone call that resolved nothing leaves nothing to file.

• Keep the reference The transaction reference on the statement is what every decider works from.
• Write, don’t call A written trail from the account email is the version that can be filed.
• Export the ledger A dated balance history shows what the account actually displayed.
• Name the ground Your reason code decides which of the operator’s records are tested.

Entry 04The reason code frames which evidence matters

The ground you file under is not paperwork; it selects the test. A “fraudulent, not mine” dispute turns on the authorisation and device records — whoever the trail points to wins. A “service not received” dispute turns on whether the deposit bought anything usable, so the play history and any account restriction dominate. A “duplicate” or “amount different” dispute turns on the transaction and ledger entries. Because the code frames the evidence, choosing a code that does not match the facts is the fastest way to lose a dispute that had merit — the operator’s records will answer a question you did not ask, and the decider will rule on the question you framed.

Entry 05What carries weight, and what does not

Timestamped records carry weight; assertions do not. A log that shows an approval from your usual device at a plausible hour outweighs a later statement that you do not remember the payment. A dated ledger export outweighs a recollection of the balance. A written exchange outweighs a verbal one. And consistency carries weight: a claim that shifts as the evidence comes in reads as unreliable, while a stable, documented account reads as credible. None of this guarantees an outcome — the decider rules on the whole file — but it explains why the same dispute can be won by one cardholder and lost by another on the same facts but a thinner record.