How Payment Reversals Work: A UK Guide for Businesses

Sooner or later, money you have already been paid gets pulled back out of your account. A customer changes their mind, a bank sides with a cardholder you have never heard from, a Direct Debit you collected last week reverses without warning. It is one of the least glamorous parts of running a business that takes payments, and one of the most expensive to get wrong.

The word “reversal” gets thrown around as if it meant one thing. It does not, and the vagueness is what costs money. A void, a refund and a chargeback are three separate mechanics with three very different price tags, and grabbing the wrong one, or moving too slowly to use the cheap one, is a mistake UK merchants make every single month. This guide untangles the whole family: what each type is, who sets it off, how long you get, and what it actually takes out of your pocket.

A note on terminology: some payment providers use “payment reversal” narrowly to mean cancelling an authorisation before settlement. This guide uses it as an umbrella for all six routes covered below. Where provider documentation uses different wording, we say so.

Payment Reversals at a Glance

Six mechanics shelter under the “reversal” umbrella. What separates them operationally is one thing: whether the money has actually moved yet, and who gets to make the call.

One pattern runs through the whole table, and it is worth committing to memory: the earlier in the process a reversal happens, the less it hurts. Cancel while the money is only on hold and it costs nothing. Let the same order settle and hand the money back as a refund, and you have paid the processing fee for the privilege. Leave it long enough to curdle into a chargeback, and you are out the fee, the stock and an afternoon of someone’s time. The merchant who ends up better off is not the one who fights reversals well. It is the one who catches them early.

What Counts as a Payment Reversal

A declined card at the checkout is not a reversal. No payment happened, so there is nothing to reverse. A reversal specifically unwinds a payment that was authorised, captured or completed, and pushes the money back towards the payer. That distinction matters the moment you start reconciling your books, because the two look nothing alike in your figures.

A refund is only one flavour of reversal, and the comfortable one: you decide to give the money back. The rest are less pleasant, because someone else decides for you and tells you afterwards. Chargebacks and indemnity claims are the ones worth understanding before they land rather than while you are staring at the notice, and that is exactly where most businesses first meet them.

Two questions sort out which reversal you are dealing with, and between them they settle everything that follows:

• Has the money settled yet? Before settlement you can usually cancel for nothing. After it, giving money back always carries a cost.
• Who is driving it? If it is you, you own the timing and the customer experience. If it is the customer or their bank, you are working to someone else’s deadline with the clock already running.

The Main Types of Payment Reversal

Authorisation Reversals and Voids

When a customer pays by card, two things happen that feel like a single event. The card is authorised first: the issuer confirms the money exists and quietly earmarks it, putting a hold on the customer’s account. Only later is the payment captured and settled, and that is the moment the money actually reaches you. The gap between those two steps is where the cheapest reversal in the entire system lives.

Cancel before capture and you void the authorisation. The hold lifts, the money never moves, and since nothing was captured there is no processing fee to lose. We checked Stripe’s own documentation on this, and it is blunt: voiding a held payment “avoids the need to process a refund or pay associated fees.” Whenever that option is still on the table, a void is the reversal you want.

If I were to leave a UK merchant with one instruction from this whole guide, it would be this. Build your cancellation flow so it catches orders before they settle. Everything else here is damage limitation, done well or badly; voiding early is the only move that costs you absolutely nothing, and most businesses never wire it in.

The window does not stay open forever. On most networks a card authorisation holds for roughly 7 days on an online payment and about 2 days in person, though extended authorisations can stretch that to 30 days depending on the network. Let it lapse without capturing and it voids itself: the hold drops, the customer is never charged, and you have quietly lost the sale you thought you had. Fine when you meant to cancel. A nuisance when you simply forgot to capture on dispatch.

Worth warning your customers about one wrinkle: even after you reverse an authorisation cleanly, some issuers take a few days to clear the “pending” line from the statement. That lag sits with the cardholder’s bank, not with you, but you are the one who fields the anxious email about it.

Refunds

A refund hands money back on a payment that has already settled. It is entirely your call, which makes it the tool you reach for when a customer cancels late, returns goods, or raises a complaint you would rather settle directly than watch escalate.

The sting is the fee. When you refund, the processing fee from the original sale stays gone. We checked this across the three providers most UK small businesses actually use, and none of them break ranks:

• Stripe puts it plainly: “Stripe’s processing fees from the original transaction aren’t returned.”
• Square confirms that when you refund a payment, “the processing fees for the payment aren’t refunded back to you.” Flag this one if you remember Square differently, because it used to hand fees back on refunds and quietly stopped.
• PayPal charges nothing to make the refund itself, but the fees you paid to take the payment in the first place do not come home.

So a refunded £200 order does not cost you £200. It costs you £200 plus the £3 or £4 in processing fees you already handed over and will never see again. Refund one order and that is noise. Refund 5% of a £50,000 month and the leakage becomes a line your finance lead will circle in red. The answer is not to refund less; it is to catch cancellations before settlement wherever the workflow allows, so a free void does the job a paid refund would have.

Customers feel the timing too. Stripe tells cardholders a refund lands “approximately 5 to 10 business days later, depending upon the bank.” Say so at the point you issue it, because the customer who waits a week, sees nothing, and cannot get you on the phone is the customer who rings their bank instead. And that turns a £3 fee into the next item on this list.

Chargebacks

The chargeback is the involuntary one. A cardholder disputes a settled payment with their own bank, the bank drags the money back out of your account under the card scheme rules, and you hear about it after the fact. The applicable deadline depends on the card scheme, the dispute reason and the date from which the period is measured; many card disputes work to a window of around 120 days from the transaction date, though that figure is not universal and some delayed-performance or ongoing-service cases can run considerably longer.

It is the most expensive routine reversal a card business faces, because it arrives with a dispute fee stapled to it and a real chance you lose the goods on top of the sale. Chargebacks also carry their own lifecycle, reason codes, evidence rules and monitoring thresholds that can drag your account into penalty programmes if the ratio climbs.

That is more than this page should try to swallow. We take the mechanics, the reason codes, the fees by provider and how to actually win a dispute apart in a dedicated guide: How Chargebacks Work. For the family picture, hold on to one line: a chargeback is what a refund turns into when you are too slow, too hard to reach, or dealing with someone who never intended to pay. Almost everything that reduces chargebacks comes down to fixing the problem before the bank ever gets the call.

Chargeback Reversal After Successful Defence

Win a chargeback dispute and the money does not simply appear back in your account. The card scheme routes the outcome through the issuer, and the disputed funds are restored to you, in practice within a few working days in most cases, though you should not count on a precise date. The process of submitting your defence is called representment; the chargeback reversal is what a successful outcome looks like on the other end.

Two things are worth knowing before you start counting that money as recovered. First, some provider fees survive the win. Stripe, for example, does not return its dispute fee even on a successful defence, so a £20 charge sits permanently in the cost column regardless of how the decision goes. If you also counter the dispute manually, Stripe charges a further £20 for that step. Neither comes back. Second, a first-round decision is not always the last word. In some cases the issuer can push the dispute to pre-arbitration, and from there to the card scheme itself. A win at representment is good; it does not automatically close the file.

Read the outcome notice carefully, reconcile the restored amount against the original transaction before you close the record, and keep your evidence file until you are certain no further escalation is coming. If the provider dashboard shows the chargeback as resolved, verify the credited amount matches what you expected before assuming it is done.

Direct Debit Indemnity Claims

Cards are only half the story. If you collect by Direct Debit through Bacs, the matching reversal is the indemnity claim, and it gives you even less room to argue than a chargeback does.

Every Direct Debit you take is wrapped in the Direct Debit Guarantee, the wording your customer sees and which every bank and building society in the scheme stands behind. Its heart is one promise: “If an error is made in the payment of your Direct Debit, by the organisation or your bank or building society, you are entitled to a full and immediate refund.” The customer never comes to you. They tell their own bank, the bank refunds them on the spot, and then it reclaims the money from your bank through an indemnity claim. You carry the full amount, and there is no neat “dispute fee” line because the whole payment simply unwinds.

The most preventable trigger by a distance is advance notice. Any change to the amount, date or frequency of a Direct Debit has to be flagged to the payer beforehand, normally 10 working days. Collect a changed amount without giving that notice and the payer is entitled to the full-and-immediate refund almost on the nod, and you will struggle to defend it. You can challenge an indemnity claim, but only with clean paperwork behind you: a valid mandate, proof you gave advance notice, and a tidy cancellation history. Thin records, and the claim stands.

Unlike a card chargeback, the Guarantee’s refund right is not neatly time-boxed, so treat a valid mandate and an orderly advance-notice trail as the thing standing between you and an easy clawback. (Selling into the US as well? The rough ACH equivalent is a “return”, tagged with NACHA R-codes, where an unauthorised consumer debit can be sent back for up to 60 days. Different scheme, familiar exposure.)

Bank Transfer Returns and Recalls

The last member of the family is the one everyone assumes is bulletproof: the plain bank transfer. Faster Payments feel final, and for day-to-day trade they usually are. But “the money is in my account” and “the money is mine for good” are not the same sentence.

Once a Faster Payment reaches the central system, nobody can simply yank it back. Recovery runs forwards, not backwards: if a payer reports a mistaken or fraudulent payment, their bank asks yours to send the funds back as a fresh return payment. That recovery request is separate from the original transfer: the original stays completed, and only a new return payment can undo the effect. Cooperative enough, on paper. Fraud is where it turns sharp.

Since 7 October 2024, the Payment Systems Regulator’s mandatory reimbursement rules have required banks to refund victims of authorised push payment (APP) scams made over Faster Payments, up to £85,000 per claim (a ceiling settled after an earlier £415,000 proposal was pulled back). The important part for you is who pays: the cost is split 50/50 between the sending bank and the receiving bank, with the receiving side reimbursing its half within 5 working days. That receiving side could be yours, if scam money ever lands in your account.

For an honest business the consequence is blunt. Because banks now shoulder half the bill on money their customer received, they have grown far quicker to freeze and claw back inbound transfers they suspect are scam proceeds. A large, unexpected payment from a brand-new customer is not a reason to panic, but it is a reason not to treat inbound bank transfers as untouchable the second they arrive. This regime lives with the PSR and Pay.UK, not the card schemes, so there is no chargeback to fight here. The money can still walk.

How the Payment Reversal Process Works

Strip the labels away and every reversal turns on a single hinge: settlement. Which side of it you are standing on decides whether a reversal is a free cancellation or a genuine loss.

Reversals Before Settlement

Before a payment settles, the money has not really gone anywhere; it is only reserved. Cancel at this stage, by voiding the authorisation, and it unwinds without a trace. No funds change hands, no fee is charged, and the customer is often none the wiser. This is the stage to build your workflows around. On any card setup that keeps authorisation and capture as separate steps, the ideal cancellation path reads: authorise on order, capture on dispatch, void if it falls over before dispatch. Every order you void instead of refund is a processing fee you get to keep.

Reversals After Settlement

Once a payment has settled, the money is sitting with you, and getting it back to the payer always costs something. Give it back voluntarily and it is a refund, and you swallow the original fee. Have it taken involuntarily, as a chargeback or an indemnity claim, and the full amount goes plus, on cards, a dispute fee. The thread tying them together is that the free option has gone. Speed is your only remaining lever now: the faster you settle a genuine problem with a refund, the less chance it hardens into a forced reversal that costs you more.

How Long Funds Take to Be Returned

Timing shifts by rail, and it matters because a customer waiting on money is a customer deciding whether to escalate:

• Voids: the hold releases at once, though the pending line may hang around on the customer’s statement for a few days at their bank’s pace.
• Card refunds: roughly 5 to 10 business days to reach the cardholder.
• Chargeback disputes: an initial debit can happen quickly; full resolution may take weeks; a restored amount after a successful defence takes further time beyond that.
• Direct Debit indemnity refunds: immediate to the payer, because their own bank fronts the money before reclaiming it from you.
• Bank transfer returns: as quick as the two banks care to be, but a disputed or fraud-flagged case can sit frozen for a good deal longer.

Tell the customer the date the reversal or refund was submitted, not the date it will appear in their account. That is the only date you actually control, and it is the one that matters if the customer later escalates.

What Payment Reversals Cost Your Business

Lost Revenue and Returned Funds

The obvious cost is the money itself. On a refund or a void you are simply handing back what you took, which at least lines up with a real cancellation or return. On a chargeback or an indemnity claim the sting is sharper: you can lose the sale and whatever you have already shipped against it. A £200 order lost to a chargeback after the goods have gone out of the door is closer to a £200-plus-stock-plus-postage event, and the reversal returns none of it.

Chargeback and Processing Fees

Fees are where the reversal types part company hardest, and where picking the right mechanic quietly pays for itself. We checked the current UK positions:

Read that table as a cost ladder. A void costs nothing. A refund costs the processing fee. A chargeback on Stripe costs £20 when it lands, and a further £20 if you contest it, neither of which comes back even when you win. That last detail draws a hard economic line under what is worth fighting: contesting a £30 Stripe chargeback costs you £40 before you factor in staff time. That is a point of principle, not a business decision. Know the number before you decide.

Administrative and Cash-Flow Costs

The line-item cost is only half the damage. Every involuntary reversal also burns staff time, because someone has to read the notice, dig out the evidence and decide whether to fight, and it lands whenever it pleases, which is the part that quietly wrecks a cash-flow forecast. A chargeback on a January sale can surface in your account in June. An indemnity claim can arrive whenever the payer’s bank gets round to raising it. You cannot forecast money that another party can pull back on their own timetable, so a business with a steady trickle of reversals is carrying a permanent low hum of uncertainty in its numbers that a clean prevention habit would simply switch off.

What to Do When a Payment Is Reversed

When a reversal lands, the first hour usually decides whether it stays a small cost or becomes a lost dispute. A calm, consistent routine beats a scramble every time.

Work through these steps in order:

1. Confirm the exact transaction status. Check your processor dashboard. Is the payment still authorised, has it settled, is it already in dispute, or has it already been partially refunded? The answer tells you which options are still open.
2. Check for any active dispute before touching the transaction. This is where the double-refund trap lives. If a chargeback is already in progress, do not also issue a manual refund without understanding how your processor handles both running at once.
3. Identify who initiated it. Did your processor flag it, did the customer contact you, or did a reversal notice arrive from your bank? The initiator determines your response route and the deadline you are working to.
4. Preserve the evidence immediately. Pull together: the transaction reference, order confirmation, delivery proof, customer communications, and the terms accepted at checkout. For a Direct Debit claim: the mandate, advance-notice records, and cancellation history. Do this before the clock runs on your response window, not after.
5. Respond before the provider deadline. For card chargebacks, the deadline shown in your acquirer’s dispute dashboard is what governs you; acquirers often set shorter internal windows than the card scheme’s outer limit. Do not use a generic industry figure. Read the actual notice.
6. Reconcile the payment and fees in your records. Record the reversal type, original settlement amount, the amount reversed, any fees charged, fulfilment cost, date submitted, and the final outcome. See the reconciliation checklist below.
7. Contact the customer where it helps. A short, clear message (“we have processed your refund; expect it in 5 to 10 working days”) removes the most common reason a refund escalates into a chargeback. For chargebacks you intend to contest, check with your acquirer before making contact, because unsolicited communication can sometimes complicate a defence.

Reconciling a Reversed Payment

Finance teams often get the reversal notice after the fact. A clean record makes the cost visible and gives you the evidence you need if the same transaction is ever questioned again. For each reversal, record:

• Original transaction reference and settlement date
• Reversal type (void / refund / chargeback / chargeback reversal / indemnity claim)
• Original gross amount and processing fee paid
• Amount reversed and any additional dispute or counter-dispute fee
• Fulfilment cost (goods, delivery, packaging) where applicable
• Date submitted by you and date the reversal appeared in the customer’s account
• Dispute outcome if contested, and the amount actually restored
• Final net loss to the business after fees and fulfilment

The gap between the date you submitted the reversal and the date it posted is the one customers ask about most. Keep both columns, and you can answer that question in under a minute rather than hunting through bank statements.

How to Reduce Payment Reversals

Prevention is the only part of this that compounds. Every reversal you head off is the fee, the admin and the cash-flow wobble avoided in a single move. Four habits do most of the heavy lifting.

Prevent Duplicate and Incorrect Transactions

A surprising share of refunds and disputes are simply your own slip-ups coming home: the same order charged twice, the wrong amount taken, a subscription billed after someone cancelled. Reconcile before you re-attempt a failed charge, and make sure a cancellation in your system genuinely stops the next collection. These reversals are avoidable to the last one, and every single one is a fee you paid to fix a mistake you made.

Use Clear Billing Descriptors

The most common honest dispute is “I don’t recognise this charge.” A customer buys from your shop, then spots an unfamiliar processor name or legal entity on their statement weeks later, and disputes it in perfectly good faith. The fix costs next to nothing: set your billing descriptor to your trading name, the name the customer actually knows, and check what shows up on a real transaction before you lean on it. This one change clears a meaningful slice of chargebacks that were never really disputes at all, and businesses pay for it month after month simply because nobody got round to changing a setting.

Keep Payment and Delivery Evidence

You cannot defend a reversal with evidence you never kept. For cards, hold on to authentication results and delivery confirmation. For Direct Debits, keep the signed mandate, a record of every advance notice sent, and the cancellation trail. Turning on 3D Secure 2 for card payments earns its keep twice over here: a successfully authenticated transaction shifts liability for fraud-related chargebacks off you and onto the card issuer, so that dispute stops being your problem. It will not cover “goods not as described” complaints, but for outright fraud it is the strongest card in your hand.

Make Refunds Easy to Request

This is the counter-intuitive one, and the most reliable of the lot. A customer who can get a fast, no-argument refund almost never bothers with a chargeback, because there is nothing in it for them. A customer who cannot cancel without a phone call and a three-step confirmation flow rings their bank instead, and the bank’s reversal costs you far more than the refund ever would have. A hard-to-cancel subscription does not protect your revenue. It quietly moves it from “subscriber” to “chargeback” on the same statement line, and UK regulatory direction under the FCA’s Consumer Duty is leaning firmly against it. Make leaving as easy as joining, and you manufacture fewer reversals in the first place.

Frequently Asked Questions

What is the difference between a refund and a reversal?

A refund is one type of reversal, the voluntary kind, where you give money back on a payment that has already settled and you swallow the original processing fee. “Reversal” is the wider family, and its other members are less comfortable: a void cancels a payment before it settles for nothing, while a chargeback or a Direct Debit indemnity claim takes money back without your say-so. The distinction that matters is control. With a refund you decide; with the involuntary reversals, someone else decides and you find out afterwards.

Do I get my processing fee back when I refund a customer?

No, and it catches out a lot of businesses. Stripe, Square and PayPal all keep the fee you paid to take the original payment, even as you hand the money back. PayPal charges nothing extra to make the refund, but the original fees still stay gone. Square used to return fees and quietly stopped, so check your provider’s current policy rather than your memory of it. The practical takeaway is to cancel before settlement with a void wherever you can, because a void carries no fee at all.

What is a chargeback reversal?

A chargeback reversal is the outcome when a merchant successfully disputes a chargeback. The card scheme routes the decision through the issuer and the disputed funds are restored to the merchant. Some provider fees survive the win: Stripe’s dispute fee is not returned regardless of outcome, so a chargeback reversal recovers the transaction value but not necessarily every cost the dispute created. In some cases the issuer can still push the dispute to a further stage, so hold the evidence file until the case is definitively closed.

Can a customer receive both a refund and a chargeback?

Yes, and this is a real trap. If a customer contacts you directly and you issue a manual refund while they have already raised a chargeback through their bank, both processes can run in parallel. You hand back the money voluntarily while the bank simultaneously removes it through the dispute process, and you lose both. Always check your payment dashboard for an active dispute before refunding any transaction a customer has flagged as a problem.

Can a bank transfer be reversed?

Once a Faster Payment has landed it cannot be unilaterally recalled, but the receiving bank can send the funds back as a return payment if the payer reports a mistake or fraud. The recovery request is separate from the original transfer: it does not cancel the original payment, it initiates a new one. Since October 2024, banks must also reimburse victims of authorised push payment scams up to £85,000, with the receiving bank carrying half the cost. Money in your account is not guaranteed to stay there if it turns out to be scam proceeds.

What is a Direct Debit indemnity claim?

It is the Direct Debit equivalent of a chargeback, raised under the Direct Debit Guarantee. If your customer believes an error was made, they claim through their own bank, which refunds them at once and then reclaims the full amount from your bank. You carry the whole sum, and the most common trigger is collecting a changed amount without giving the required advance notice, normally 10 working days. Keeping a valid mandate and proof of every advance notice is what lets you challenge a claim you think is wrong.

How can I reduce chargebacks and reversals?

Catch cancellations before settlement so a free void does the work of a refund; set your billing descriptor to your trading name so customers recognise the charge; keep authentication and delivery evidence for cards, and mandate and advance-notice records for Direct Debits; and make refunds genuinely easy to request, since a customer who gets their money back quickly rarely bothers their bank. For the card-specific detail on fighting and preventing disputes, see our full guide to how chargebacks work.

Sources and Methodology

We verified the data on this page in August 2026. The sources used are listed below. Where a provider does not publish a figure, we say so rather than leaving a gap or extrapolating from a related rate.

• Provider fee schedules (August 2026): Stripe UK (dispute fees, including the counter-dispute charge introduced in its updated terms); Square UK (refund and dispute fees); PayPal UK business fee schedule.
• Bacs / Pay.UK operating rules: Direct Debit Guarantee wording, payer entitlement to an immediate refund, and the advance-notice requirement (10 working days by default) as published at directdebit.co.uk.
• Visa dispute framework: Published reason codes, chargeback timeframes, and the representment (second presentment) process. Mastercard operates equivalent rules; timeframes differ by reason code.
• Payment Systems Regulator — PS24/7: Authorised push payment reimbursement rules in force from 7 October 2024: mandatory reimbursement up to £85,000, costs split 50/50 between sending and receiving banks.
• NACHA ACH return codes: Referenced for international context on bank transfer returns (R-codes). UK Faster Payments operate under different rules; the PSR APP framework governs scam recovery.

Chargeback timeframes vary by card scheme, reason code, and the date from which the period is measured. Fees and deadlines change; the figures above reflect published rates at verification date. Confirm anything you are about to act on against the provider’s current terms before relying on it.

Editorial independence. BusinessExpert is an independent publication. Providers listed on this page have not paid to appear, and our assessments are based on publicly available information. Where we have affiliate arrangements with providers linked from this page, we disclose this in our advertising notice at the top of the page.

Related Guides

• How Chargebacks Work — the full mechanics of raising, defending, and preventing a card dispute, with reason codes and timelines.
• Payment Gateway Fees Explained — the three-layer fee structure behind every transaction, and what happens to those fees when a payment is reversed.
• Recurring Payments — how UK businesses collect regular card and bank payments, with failure rates and the Direct Debit indemnity risk compared.
• Direct Debit Providers for UK Businesses — GoCardless, Stripe Billing, and alternatives reviewed, including how each handles indemnity claims.
• How to Take Card Payments — setup, equipment, and contract terms that affect your chargeback exposure before the first transaction.