Your chargeback case begins before the bank’s email

There are two days left to answer a dispute. The folder contains a receipt, tracking number and forty pages of correspondence. What is missing is evidence that answers the customer’s actual claim. Shipping records do not address a cancelled subscription. A screenshot of today’s terms does not establish what applied six months ago. A large archive can still make a weak case.

Chargeback preparation starts when the order is placed and fulfilled. The aim is not to collect more information about the customer. Preserve a small, connected and permissible chain of facts explaining what happened in this particular transaction.

Define the disputed question first

Different dispute reasons require different evidence. Adyen’s requirements depend on the reason and payment scheme, and meeting them does not guarantee a win. See Adyen’s dispute reasons and defence requirements. A universal PDF containing everything found about the customer is therefore a poor operating standard.

For goods allegedly not received, investigate fulfilment of that order. For duplicate charging, establish how separate financial transactions relate to separate obligations. For a cancelled subscription, consent, cancellation time, paid period and subsequent collection activity become relevant. These illustrate the direction of an investigation, not a promise that the listed records satisfy every case.

The proposed evidence card records five things: the fact supported, source, time, link to the order and limits of interpretation. Email sent may establish dispatch but not necessarily that it was read. Delivery evidence requires checking its address and connection to the order rather than merely finding a familiar tracking number.

Terms change; the purchase history must survive

Imagine an online course sold with monthly access. The team changes its refund policy after purchase. Saving only the current web page during a dispute does not establish which terms the buyer encountered when ordering. A workable design versions the terms and links the applicable version to the purchase record.

Retain the agreed mechanism for recording consent and appropriate evidence of the promised service and fulfilment. Do not manufacture historical acknowledgements after the fact. Do not treat any account login as proof that the disputed service was consumed. Select information that genuinely addresses the claim while respecting retention and minimisation requirements.

Evidence retention should not follow a longer-is-always-better rule. Applicable obligations, contracts and potential proceedings affect the period. The team needs to know which records remain necessary, who may access them and when retention ends. Convenience in a possible future dispute does not justify uncontrolled accumulation of identity documents.

Edit the response instead of archiving everything

First state the position in one sentence: which claim is contested, and which fact supports that position? Build a concise chronology and arrange evidence to support it. If a crucial date appears on page 37 without explanation, the reviewer may not understand its significance.

Stripe requires evidence through its dispute-response process and limits changes after submission. See Stripe’s response procedure. Follow your provider’s requirements on deadlines, formats and final submission. Take the deadline from the actual case rather than an old guide promising one universal number of days.

Before submission, a second employee checks four things: the payment is correct, the response addresses the stated reason, dates and amounts agree, and the package does not expose unrelated information. That review is more useful than another paragraph asserting the company’s good intentions. Exclude claims the team cannot substantiate and distinguish a contemporaneous record from a later explanation.

Some disputes should be accepted

If the company failed to deliver its promise, replacing the complaint with procedural arguments does not fix the underlying problem. Separate accepting responsibility from defending a supported position. Set decision authority and an economic assessment for uncertain cases: amount, preparation cost, evidence quality and applicable consequences.

Winning is not the only measure of performance. Track missed deadlines, missing evidence, recurring causes and cases that appropriate customer service could have resolved earlier. Win rates without case mix are misleading. A team accepting clearly justified complaints changes the population of disputes it chooses to defend.

Measure where the file became weak. Was the applicable policy missing? Was fulfilment never linked to the payment? Did a cancellation sit unanswered in support? These findings point to different product fixes. Another response template will not repair a missing historical record or an unreliable cancellation process.

Rehearse with one order

At a cadence chosen by the team, take a synthetic or appropriately de-identified case and assemble the package without help from the order’s original owner. How long does it take to find the applicable terms? Do support and payment timestamps agree? Can fulfilment be understood without guessing?

Repair the gaps in the product: preserve the relevant terms version, link the order to fulfilment, and make cancellation understandable. The next dispute email can then trigger a bounded factual review rather than an urgent reconstruction of a vanished history.