Chargebacks for UK businesses: how to avoid them and how to win them

A chargeback is one of those things that does not feel real until the first one lands. The acquirer's email arrives with a transaction reference and a four-digit reason code, the funds are already out of your account, and you have somewhere between two and four weeks to put together a defence with evidence you may not have collected at the time of the sale. This guide is for the UK operator who has either taken their first chargeback and wants to handle it properly, or watched their dispute rate creep up and wants to understand where the leak is.

The mechanics of chargebacks have not changed much since the schemes (Visa and Mastercard) standardised them in the 1990s. What has changed is the operational discipline that wins them: the evidence pack the acquirer wants, the response windows set by Visa and Mastercard chargeback rules, and the small handful of operational changes that stop most disputes before they ever reach the bank.

For the wider payments view, our card processing fees explained and merchant statement walkthrough cover the cost-side numbers underneath this dispute-side piece.

How a chargeback actually works

Five steps, in order.

One. The cardholder calls or messages their issuing bank to dispute a charge. The reason can be anything from genuine fraud to "I do not recognise this descriptor". The issuer makes the first call on whether the dispute meets a valid reason code.

Two. The issuer logs the dispute under one of the scheme's reason codes (Visa codes 10.x for fraud, 11.x for authorisation, 12.x for processing errors, 13.x for "consumer disputes"; Mastercard runs an equivalent set). The reason code is the single most important piece of information in the case because it dictates which evidence wins.

Three. Your acquirer receives the chargeback notification from the scheme. The funds are pulled from your settlement account before you have said a word. Your acquirer notifies you and starts the response clock.

Four. You either accept the chargeback (the funds stay with the cardholder, the case closes) or defend it by submitting an evidence pack inside the scheme response window (commonly 30 days from notification). The pack goes through your acquirer to the issuer.

Five. The issuer reviews the evidence under the scheme rules and either reverses the chargeback or upholds it. This first defence stage is commonly called representment. Some cases can then move into pre-arbitration and, more rarely, arbitration, but many merchant disputes end earlier in the cycle.

Two important truths the messaging from acquirers does not always make explicit: the funds leave your account before you defend, and your acquirer is the messenger between you and the issuer, not the decision-maker. The scheme rules and the issuer make the call. Your acquirer's job is to package and deliver your evidence cleanly inside the window.

The evidence pack that wins

Every winning chargeback response has four parts.

One: the transaction record. The original authorisation, the date and time, the amount, the card last four digits, and any AVS or CVV check results captured at the moment of sale. This proves the transaction happened and was authorised by the issuer.

Two: proof the customer received what they paid for. For in-person sales this is the terminal receipt, transaction log, and any signed receipt where one exists. For online physical goods it is a tracked-delivery confirmation tied to the order. For services or digital goods it is a delivery log, an access log, or signed acknowledgement.

Three: the customer communications log. Every message between you and the customer, in date order, with timestamps. Email threads, text messages, WhatsApp logs. The pattern that wins is a clear customer story: they ordered the thing, they received the thing, they used the thing, then weeks later the dispute appeared.

Four: a one-page narrative. A short cover document that walks the issuer through the case in plain English: what was bought, when it was delivered, what the customer said and when, why the reason code does not apply. Acquirer staff who package representments in volume tell us the narrative is the difference between a win and a loss for borderline cases.

Submit the pack inside the response window. Late submissions are treated as no submission, regardless of how strong the evidence is.

Card-not-present is where most leaks live

A disproportionate share of SME chargebacks tend to sit in card-not-present transactions: ecommerce, phone orders, and manual key entry. That is a recurring pattern in payments operations work, even though the exact mix varies by sector and channel. The cardholder is not present, the card is not physically read, the signature is not captured, and the evidence required for the response is harder to assemble after the fact.

If your business takes meaningful card-not-present volume, the operational discipline is different from in-person sales. Capture AVS (address verification) and CVV checks on card-not-present transactions where the gateway supports them; both can help later in a dispute, but AVS is not universal across UK setups. Tag any first-time customer above a value threshold (set the threshold to whatever flagging volume you can review by hand) for a brief manual review before fulfilment. Record any phone or message conversation against the order ID, not in a separate inbox.

The handful of operators we work with whose dispute rate sits in clean territory all do the same boring thing: they treat every card-not-present sale as a small evidence-collection exercise from the moment the order lands. By the time a chargeback arrives, the pack is half-built already.

How to stop the next one

Three operational changes that reduce chargeback rates in our experience without burning customer goodwill.

One: clearer billing descriptor. A surprising share of disputes are honest customers who do not recognise the charge on their statement. The descriptor that lands on the cardholder's statement is set by you (with your acquirer's help) and should be the trading name customers use, not a parent company or legal entity name. Adding a town or short product hint can help (MICHO TURKISH NOTTM, BRIDLEWAYS GUEST HOUSE, that sort of pattern).

Two: refund first when the customer is in the right. A clean refund costs you the original sale; a lost chargeback costs you the sale plus the chargeback fee plus operational time. If the customer has a fair complaint, refund quickly and move on. The economics favour the fast refund over the slow defence.

Three: tighten card-not-present onboarding. The high-risk patterns are well known: shipping address that does not match billing address, an unusually large first order, multiple cards attempted from the same device or session, an email domain that does not match the customer's name. None of these on their own is a fraud signal. Two or three together is worth a manual review before fulfilment.

If the dispute rate is rising, treat it as an operational warning sign well before you get anywhere near a scheme monitoring programme. In our work, some operators use tighter internal trigger points for in-person and ecommerce channels, but there is no single universal percentage that applies across every business. The schemes (Visa and Mastercard) run their own monitoring programmes and will flag the acquirer if a merchant's ratio crosses their published lines, so the practical aim is to spot the trend long before that conversation.

The bit acquirers do not explain clearly

A chargeback fee is the small charge your acquirer levies to cover the operational cost of processing the dispute through the scheme. Many acquirers charge the fee whether you win or lose the case, because the scheme work happens either way. The fee is set by your acquirer, not by Visa or Mastercard, and varies between providers; check your own contract for the exact treatment.

Two important nuances. First, a chargeback fee and the disputed transaction amount are separate. If you lose the case, you lose the transaction value AND pay the fee. If you win, you get the transaction value back but the fee usually still stands. Second, "won" disputes can sometimes be re-disputed by the issuer (pre-arbitration), so a representment win is not always final. The scheme rules around this are tightening; the practical advice is to keep the evidence pack on file for at least six months after the case closes.

Dojo, the acquirer Reeve Consult partners with, says in its public materials that it notifies merchants about disputes, sets out the evidence needed, and submits the response on the merchant's behalf. Different acquirers package dispute handling differently, so it is worth checking your own contract and portal deadlines.

A five-question diagnostic

If your dispute rate has been creeping up, work through these five questions before doing anything else.

One. Do you know your dispute rate as a percentage of transaction count for the last three months, or are you guessing?

Two. When you look at the disputes you have taken in the last six months, do they cluster around a single product, a single sales channel, or a single staff handover?

Three. Is your billing descriptor the trading name your customers actually recognise, or is it a parent company name, an old brand, or a payments processor's default?

Four. Do you have a written response template for chargebacks, or is the response built from scratch each time?

Five. Are you capturing AVS and CVV results on every card-not-present transaction where the gateway supports it, or only on some?

If two or more of those questions made you pause, the AI Opportunity Audit is a free 30-minute call. We will help you map where the disputes are coming from and what the operational fix is. The fix is rarely the card machine itself; it is usually the workflow around it.

If the diagnostic raised a flag

If the questions above were not easy to answer, the issue is usually not "are we using the wrong card-payments provider?" It is "do we know what is causing the disputes, and is the response routine fast enough to win the ones we should be winning?"

If you want a 30-minute conversation about that in your own business, book a free audit. We will look at the dispute pattern and the operational handovers, and tell you whether the first move is a billing descriptor change, a response-template build, a card-not-present rule tighten, or something else entirely.