The Evidence Window: Assembling a Chargeback File Before the Deadline

A chargeback can arrive with the ordinary look of an accounts query: a payment reversed, a notification from the acquiring bank, a request for information. By then, the useful work has usually already been done or left undone. Card schemes give a firm a fixed window in which to respond, and the quality of the response depends less on the strength of the argument than on the records that existed before the customer ever picked up the phone.

For a UK SME, the practical question is not whether chargebacks can be prevented altogether. They cannot. The practical question is whether the business can produce a coherent file quickly enough, and whether that file tells a consistent story about what was sold, what was agreed and what was delivered.

The clock starts before the dispute

Chargeback rules are set by the card schemes and administered through the acquiring bank. The precise timetable depends on the reason code and the scheme, but many disputes allow roughly 120 days from the transaction or the expected delivery date; some categories allow longer. The firm does not usually control when the clock starts. It controls what is available when the clock is running.

That distinction matters because a late response is often treated as no response. A well-argued case submitted after the deadline may not be considered on its merits. The objective, therefore, is not to write a persuasive letter at speed. It is to maintain a dispute file that can be assembled from existing records within a day or two.

Record the sale as an agreement, not a transaction

A card payment receipt proves that money moved. It does not prove what the customer bought, what terms applied, or what the customer was told. Those points are the substance of many disputes, particularly for card-not-present sales and for services with a delivery period.

At the point of sale, a UK SME should be able to show:

• the customer's name, billing address and, where relevant, delivery address;
• a description of the goods or services sufficient to identify the supply;
• the amount charged and the date of the charge;
• the terms accepted at checkout or in the signed order, including cancellation and returns provisions;
• for online sales, records of authentication checks such as address verification, card verification and, where used, strong customer authentication;
• any correspondence in which the customer confirmed the order or asked for a variation.

This is not an argument for collecting more data than the business needs. It is an argument for keeping the data that already passes through the sale in a form that can be retrieved. A confirmation email that restates the order, the price and the delivery expectation is more useful than a payment reference alone.

Capture fulfilment while it is still ordinary

Many disputes turn on whether the goods arrived or the service was performed. The evidence here is often created by operational staff who have no reason to think about chargebacks. A dispatch note, a courier tracking record, a proof-of-delivery image, a signed delivery sheet or a dated installation report can each answer a question that a bank will later ask.

For physical goods, the firm should retain the dispatch date, the carrier, the tracking number and the delivery confirmation. Where a signature or photograph is available, it should be stored with the order record rather than left in a separate courier portal that may expire. For services, the equivalent is a dated record of performance: a site visit note, a completed works sheet, a training attendance record or a system log showing access or completion.

Correspondence matters as much as delivery. If the customer reported a problem, asked for a delay, confirmed receipt or agreed a substitute, that exchange should sit with the order. A chargeback file that contains only internal records and no customer communication can look one-sided even when the firm is right.

Keep refund and returns history in the same place

A customer may dispute a payment after a refund was promised, partially processed or refused. The firm should be able to show its returns policy, the customer's request, the firm's response and any refund transaction reference. If a refund was issued, the acquirer will want to see it. If it was refused, the reason should be documented at the time, not reconstructed later.

This is also where a simple ledger helps. A monthly reconciliation that links orders, refunds and credits to the same customer reference reduces the risk of a dispute file containing contradictory dates or amounts.

Build the dispute file before it is needed

A dispute file is not a separate bureaucracy. It is a folder convention and a short checklist. For each order above a sensible threshold, the business can keep a single reference that links the order confirmation, the terms accepted, the payment record, the fulfilment evidence and the correspondence.

The checklist need not be elaborate:

1. Order and customer details.
2. Terms accepted at the time of sale.
3. Payment authentication and authorisation records.
4. Dispatch or performance evidence.
5. Delivery or completion confirmation.
6. Customer correspondence and refund history.
7. A short timeline of what happened, in date order.

When a chargeback notification arrives, the first task is to identify the reason code and the response deadline. The second is to assign one person to assemble the file. The third is to check that the story is consistent: the order date, the delivery date, the amount and the customer's complaint should not contradict one another. A concise cover note that maps each item of evidence to the reason code is more useful than a long narrative.

Make the routine proportionate

Not every sale needs a bespoke file. A small firm can apply the routine to higher-value orders, customised goods, delayed deliveries and customers with a prior dispute. A quarterly sample audit of ten orders will usually reveal whether the evidence is being captured or merely assumed.

At Galico, the practical test is simple: if a chargeback arrived tomorrow, could the business produce the order, the terms, the delivery proof and the correspondence before the response deadline? If the answer is no, the gap is worth fixing now, while the transaction is still ordinary and the clock has not started.