Chargeback Received: A UK Merchant's Response Framework from First Notice to Final Appeal

A chargeback notice can arrive without warning, often during a busy trading period and frequently by email or through an acquirer portal rather than by post. It is easy to treat the notice as another customer complaint. That is a mistake. A chargeback is a formal dispute process governed by card scheme rules, and it runs to a clock. The merchant's objective in the first three working days is not to win the argument in principle, but to preserve the option to respond properly.

Why the first 72 hours matter

Most chargeback deadlines are measured from the date the notice is received or made available in the acquirer portal. The exact period depends on the card scheme, the reason code and the acquirer's own cut-off arrangements. A merchant that waits for a quiet afternoon before opening the notice may find that the evidence window has already narrowed.

A practical internal target is to complete the first three steps below within 72 hours: verify the notice, freeze the evidence and decide whether to represent or refund. That internal deadline leaves room for review before the scheme deadline, which may be shorter than expected. It also avoids two common errors: refunding the customer while a representment is still being prepared, and submitting a response without checking whether the transaction has already been credited.

Step 1: Verify the notice and the clock

Start with the acquirer portal or the email that carries the notice. Confirm the transaction date, amount, card last four digits, reason code and the date by which a response must be submitted. Check whether the notice is a chargeback or a retrieval request. A retrieval request asks for information; a chargeback moves funds and requires a formal response. They are not the same process.

Record the notice date and the stated deadline in a shared dispute log. If the deadline appears unusually short, ask the acquirer to confirm it in writing. Do not rely on memory, and do not assume that a public holiday extends the scheme deadline unless the acquirer confirms it. The merchant account provider is the correct first point of contact for procedural questions.

Step 2: Freeze evidence, not the customer relationship

Create a single dispute folder and place every relevant record in it. Depending on the reason code, this may include the order confirmation, terms and conditions accepted at checkout, delivery address, address verification result, card verification result, 3-D Secure outcome, IP or device data, dispatch confirmation, tracking history, proof of delivery, customer correspondence and the published refund or returns policy.

Preserve records in their original form. Do not crop screenshots or rewrite system notes. If a customer makes contact while the dispute is open, respond factually and avoid promising a refund before the commercial decision has been made. A merchant may still choose to refund because the relationship or the amount does not justify the administrative cost, but that decision should be recorded and should not be made in parallel with an active representment.

Step 3: Build a representment pack that answers the scheme question

The reason code should determine the evidence, not the other way round. For a fraud-related dispute, the strongest pack usually shows that the cardholder authorised the transaction and received the goods or services. That may include a 3-D Secure result, address verification, delivery to a verified address, prior transaction history and correspondence from the customer. For a goods not received dispute, tracked delivery to the stated address, carrier confirmation and any signature or safe-place record are central. For a not as described dispute, the product listing, images, terms, returns policy and customer communication matter more than a generic statement that the item was sent.

Include a short cover sheet that maps each piece of evidence to the reason code. Remove irrelevant personal data and do not include full card numbers. A focused pack is easier for an issuer to assess than a large file with no obvious structure.

Step 4: Write the response in plain, chronological English

The cover letter should summarise the transaction, state why the chargeback is considered invalid and list the evidence attached. Use short paragraphs and clear dates and amounts. Avoid emotional language, speculation and legalistic phrases that do not help the issuer understand the facts. Address the reason code directly.

If evidence is missing, say so and explain why. A carrier exception report or a system outage log is more credible than an unsupported claim that delivery definitely occurred. The response should read as a factual account that a busy reviewer can follow in a few minutes.

Step 5: Submit before the deadline and record the outcome

Submit through the acquirer portal or the channel specified in the notice, and keep the confirmation. Save a complete copy of the submitted pack. The issuer then has a period to review the response, and the scheme may allow a further stage if the chargeback is upheld. Monitor the dispute log rather than waiting for another email.

If the chargeback is lost, decide whether a final appeal is commercially justified. Pre-arbitration or arbitration stages can carry fees that exceed the transaction value, and they should be reserved for cases where the evidence is clear and the amount or principle warrants the cost. A final appeal is not a second opportunity to make a general complaint; it must address the specific reason code and the evidence already presented.

Step 6: Tighten records to reduce repeat disputes

Once the dispute is closed, review the cause rather than only the outcome. Late delivery, unclear billing descriptors, slow refunds, missing authentication and poor communication all generate avoidable chargebacks. Check that the descriptor on the customer's statement is recognisable, that dispatch emails are sent promptly and that delivery exceptions are followed up. Review dispute reasons monthly and look for patterns by product, channel or courier.

A 72-hour internal response routine will not eliminate chargebacks, but it gives UK merchants a disciplined way to protect their position while the scheme clock is running.