Refund vs Reversal vs Dispute vs Chargeback
Refunds, reversals, disputes and chargebacks all describe money moving back from a business to a customer, but they follow very different processes and have very different consequences. Knowing which one applies helps you respond correctly and avoid unnecessary costs.
The simplest way to think about it: a refund is voluntary, a reversal undoes a payment before or shortly after it completes, a dispute is a formal complaint, and a chargeback is a forced return of funds decided through the customer's bank or card scheme.
What is the difference at a glance?
| Refund | Reversal | Dispute | Chargeback | |
|---|---|---|---|---|
| Who initiates it | The business | The business or the bank | The customer | The customer, via their issuing bank |
| When it happens | After a payment settles | Before settlement, or shortly after processing | Any time within the allowed dispute window | Within scheme-defined timeframes |
| Who decides the outcome | The business | Largely automatic | The bank, based on rules and evidence | The card scheme process |
| Typical cost to the business | The refunded amount | Usually minimal | The disputed amount, plus admin effort | The amount, fees, and impact on chargeback ratios |
What is a refund?
A refund is a voluntary return of funds that the business initiates, usually because goods were returned, a service was cancelled, or an error was made. Refunds are processed through the same payment method as the original transaction where possible.
Refunds are the cheapest way to resolve a problem. A customer who receives a prompt refund has no reason to raise a dispute or chargeback, both of which cost the business more. See card refunds, reversals and voids for how this works on card payments specifically.
What is a reversal?
A reversal undoes a payment before it fully completes, or corrects it shortly afterwards. Common examples include:
- Voiding a card authorisation before it is captured
- An automatic reversal when a transaction times out or fails mid-processing
- A bank reversing a recent unauthorised debit order at the account holder's request
Reversals are usually faster than refunds because the funds have not yet settled to the business, or the correction happens within the banking system itself.
What is a dispute?
A dispute is a formal complaint by a customer that a payment was wrong, unauthorised or not what they agreed to. The dispute process depends on the payment method:
- Debit orders are disputed through the customer's bank, with the mandate deciding the outcome. See debit order disputes.
- Card payments are disputed through the issuing bank and may escalate into a chargeback. See card chargebacks.
A dispute does not always mean the customer wins. If the business can show valid authorisation — a signed mandate, a 3D Secure result or proof of delivery — the dispute may be rejected.
What is a chargeback?
A chargeback is the card-scheme version of a dispute: the issuing bank forcibly returns the funds to the cardholder, and the business must either accept the loss or fight it with evidence through a process called representment.
Chargebacks are the most expensive outcome for a business because they involve:
- Loss of the transaction amount
- Chargeback fees
- Administrative effort to gather evidence
- Damage to the business's chargeback ratio, which schemes and acquirers monitor
Which one should you use to fix a problem?
- If the customer is right, refund them promptly. A refund closes the matter; a chargeback keeps it open and costs more.
- If a payment was duplicated or failed mid-flight, ask your payment provider about a reversal before refunding.
- If a customer threatens a dispute, resolve it directly first. Banks and schemes generally expect customers to approach the business before escalating.
- Never refund a transaction that already has an open chargeback — you risk paying twice.
Related topics
Disputes and Compliance
Refunds, chargebacks, debit order disputes, payment fraud, PCI DSS Level 1, KYC, AML and POPIA explained, plus how to respond to payment incidents.
PCI DSS
What the PCI DSS standard requires, which merchants and providers must comply, and how hosted checkouts and tokenisation reduce your PCI scope.