A customer's card charged twice at the terminal
How a workshop stops double card charges at the counter, spots one before the customer leaves, and refunds it before it turns into a dispute.
By Achekam · · 5 min read · For Automotive businesses in South Africa, Nigeria, Kenya
The customer has collected the car, paid for the service by card, and driven off. Two days later they phone: their banking app shows the same amount twice. The service adviser is sure only one payment went through. The cashier remembers the terminal hanging and being restarted. Nobody kept the first slip.
A double charge is one of the most avoidable problems at a workshop counter, and one of the most damaging when it is handled slowly. The customer feels cheated over money they did not owe, and if they go to their bank before you put it right, a simple mistake becomes a formal card dispute. This article explains how double charges happen, how to catch them at the counter, and what to do when one slips through.
How a double charge happens
Most duplicates come from a handful of moments:
- The retry. The terminal seems to stall, so the cashier cancels and starts again. The first attempt had in fact been approved.
- The re-key. The amount is entered, the customer is slow with the PIN, the screen times out, and the cashier keys it again without checking the result of the first.
- Two slips, two entries. The terminal prints a merchant copy and a customer copy, and both are treated as separate payments when the day is reconciled.
- The second terminal. A busy workshop has two machines, and a payment is started on one and finished on the other.
Visa warns merchants about exactly these patterns. It says that entering the same transaction into a terminal more than once, depositing both the merchant and bank copies of a receipt, or depositing the same transaction with more than one merchant bank can all result in duplicate transaction disputes. Visa's dispute resolution guidance for businesses explains what disputes are, why cardholders raise them and how a business can prevent and answer them.
Why a duplicate turns into a dispute
Visa defines a dispute as the reversal of the value, or part of the value, of a transaction by the card issuer to the acquirer and, usually, by the merchant bank to the merchant. In plain terms: the customer's bank takes the money back, and your bank takes it from you.
The timing is what hurts. Stripe, describing how disputes work on its platform, states that while a dispute is open a business cannot issue a refund outside the dispute process, and that each dispute raises the business's dispute rate with that card network. Your own acquiring bank will have its own rules, so ask it how it handles a refund once a dispute is lodged. The lesson holds either way: the moment to fix a duplicate is before the customer calls their bank.
Checking before the customer leaves
The cheapest control is a quick look at the terminal before the customer walks away. If the terminal hesitated, misbehaved or was restarted at any point in the payment, check its last few transactions on screen or on a short report. If two approvals for the same amount appear close together, sort it out while the customer is still at the counter, with the customer watching.
At an Achekam till, a card payment is recorded by the cashier from the bank terminal's slip, because the till has no link to any card machine. That separation is useful here. The till holds one record per sale; the terminal holds one record per approval. When the two disagree, the difference is your duplicate.
Build that comparison into the day:
| When | Compare | Looking for |
|---|---|---|
| After any terminal hiccup | The terminal's recent approvals with the sale just rung up | Two approvals for one sale |
| Midday | The terminal's running total with the till's X report | Card totals that do not agree |
| Cash-up | The terminal's batch total with the Z report | A card total higher on the terminal than at the till |
A live X report of an open till and a Z report frozen at cash-up can both be opened as PDFs, so the comparison can be printed and initialled by whoever does it.
Refunding the extra charge
If the customer was charged twice and the till recorded the sale once, the till does not need to change: it already shows the correct position. The extra charge is reversed on the bank's terminal, using the terminal's refund or void function as your bank provides it. Stripe states that a business can issue more than one refund against a charge but cannot refund more than the original charge. The same common-sense limit applies at your terminal: refund exactly the duplicate amount, once, against the duplicate approval.
If the till also recorded the payment twice, for example because the sale was rung up again after the terminal stalled, correct the till too. In Achekam a supervisor or manager can refund all or part of a till sale, with a reason, as its own document linked to the original sale, and any goods are put back into stock. Use a reason that says what happened, such as "duplicate sale rung after terminal restart", so the refund makes sense when someone reviews it later.
Keep the terminal's refund slip with the original slips and a printout of any till refund, so the trail can be followed in either direction.
When the customer calls days later
If the duplicate is only discovered when the customer phones, act the same day:
- Ask for the date, the amount and the last four digits of the card.
- Pull that day's terminal batch report and Z report and look for two approvals.
- If the duplicate is confirmed, refund it on the terminal and tell the customer when they can expect to see it.
- Write a short note of the call, the evidence and the refund, and file it with the day's cash-up papers.
- If the customer says they have already disputed it with their bank, contact your acquiring bank before refunding, so you do not pay the money back twice.
A routine for the counter
The routine that prevents most duplicates is short: never re-key a payment until you have checked whether the first one went through; always look at the result on the terminal screen, not just whether a slip printed; keep one terminal per payment; and reconcile the terminal to the till at midday and at cash-up.
For the basics of recording terminal payments at the till, see recording card payments from the bank terminal. If a dispute does arrive, the chargeback dispute timeline explains how it unfolds.
A customer who sees a duplicate fixed at the counter rarely remembers it. A customer who has to chase it remembers the workshop for the wrong reason.
General guidance only, not advice on your own circumstances. Tax and payroll rules change: check the current position with the authority or your adviser.