Say a customer writes in claiming their order never showed up. It was $80. You could refund it this afternoon, or you could sit tight and let them take it up with their bank. Most teams don’t think twice about it. They should.
On paper both routes end the same way, with the money back in the buyer’s account. Your acquirer sees it differently, though, and so do the card networks. With chargeback fraud getting more common every year, the difference between a refund and a chargeback has turned into a real cost center that a lot of merchants still don’t track.
The refund side is pretty boring (that’s good)
When you refund, you’re in charge. You set the amount and you decide when it goes out.
What you lose is the sale itself plus, in many cases, the processing fee, since plenty of acquirers keep that fee even after the money goes back. So the $80 refund might really cost you $82 or $83.
And that’s about all. Nobody reviews the case, and your merchant account doesn’t take a hit.
Chargebacks cost more than the money
A chargeback works differently because the cardholder’s issuing bank pulls the funds back on its own. You find out later.
First the disputed amount disappears from your settlement. Then there’s a dispute fee on top, usually somewhere in the $15 to $100 range depending on your acquirer and region, and you pay it whether you win or not. Then someone has to dig up tracking numbers and old support emails before the response window closes.
The part people forget is the ratio. Card networks keep an eye on how many disputes you get compared to your total transactions, and if you creep up toward roughly 1%, you can get pulled into a monitoring program. That means fines, bigger reserves and awkward pricing talks with your acquirer. A spike in chargeback fraud can push you there even if every single order you shipped was legitimate.
| Refund | Chargeback | |
| Started by | You | The cardholder’s bank |
| Extra fees | Processing fee often kept | Dispute fee, win or lose |
| Hits your dispute ratio? | No | Yes |
| Who controls timing | You | The bank’s deadline |
| Can you get the money back? | Not relevant | Only if your evidence holds up |
| Work involved | A few minutes | Often a few hours |
Friendly fraud makes this messier
Some disputes aren’t honest. Chargeback fraud (people often call it friendly fraud) is when a customer gets exactly what they ordered and then tells their bank they never authorized it, or that it never arrived. Not all of it is deliberate, to be fair. A weird billing descriptor on a statement confuses a surprising number of people.
So “just refund everyone” isn’t a great policy. If you refund someone who’s gaming you, they learn it works, and there’s no dispute record to flag them next time. Contesting everything is just as bad, because you end up fighting customers who had a real complaint.
This guide to chargeback fraud goes deeper into the warning signs and how merchants catch repeat offenders early.
So when should you refund first?
A decent rule of thumb is this. If you’d probably lose the dispute, refund before it turns into one.
That usually covers customers who came to you directly before going to their bank, since that says a lot about intent. It covers orders where you can’t actually prove delivery, or the item showed up broken. It covers small orders where the dispute fee plus your team’s time would cost more than the sale. And it covers long-standing customers with no history of problems.
But if the order has obvious fraud signals, or you’ve got signed proof of delivery, or this same account has filed disputes before, it’s worth holding off and preparing to fight it. Watching chargeback fraud at the customer level rather than order by order is what lets you make that call with confidence.
Timing matters a lot here.
If you refund after the bank has already opened a case, the chargeback can still go through, and then you’ve paid that customer twice.
You need the data in one place
None of this works well if your information is scattered. Merchants running more than one payment processor often have dispute alerts in one tool, refund records in another and customer history in a third. Payment orchestration platforms, including open-source ones like Hyperswitch, bring those feeds together. Your refund rules then apply evenly across processors, and chargeback fraud starts to look like a pattern you can act on.
Conclusion
A refund costs you the sale and maybe a fee. A chargeback costs you that, plus a penalty, plus a little damage to how your acquirer sees you. Use refunds early when you know you’d lose anyway, keep genuine complaints separate from fraud in your reporting, and save the fight for disputes you have the evidence to win.
