Chargebacks Explained: How They Work and How to Protect Your Business.
Most owners first learn what a chargeback is the hard way — money that was in their account is suddenly clawed back out, along with a fee, weeks after a sale they thought was final. If you accept cards, you need to understand this process before it happens to you, not after.
A chargeback is not a refund. A refund is you returning money to a customer directly. A chargeback is your customer disputing the charge with the bank that issued their card, and that bank forcibly reversing the payment — pulling the funds back out of your account, whether or not you agree. You’re not in the room when the decision starts. The customer calls their bank, says something went wrong, and the machinery begins on their side.
Here’s the sequence. The cardholder disputes a charge with their issuing bank. The bank provisionally takes the money back from you and assigns a reason code — fraud, “item not received,” “not as described,” duplicate charge, and so on. You then have a limited window to fight it, a process called representment, where you submit evidence that the charge was valid. The issuer weighs it and decides. If the amount is large enough and both sides dig in, it can escalate to arbitration through the card network, which gets expensive fast. Throughout, the clock is short and unforgiving.
Now the part owners underestimate: the true cost. When you lose a chargeback, you lose the sale amount, you’ve often already shipped the product or delivered the service (so you lose that too), and you pay a chargeback fee on top — frequently in the range of fifteen to a hundred dollars per dispute. But the real danger is your chargeback ratio. Card networks watch the percentage of your transactions that turn into disputes, and if it climbs past their thresholds, you can be hit with monitoring programs, fines, higher reserves, or — worst case — termination of your ability to accept cards at all, which can land you on an industry blacklist known as the MATCH list that makes getting a new processor very hard. A chargeback problem isn’t just lost sales. It’s an existential risk to your ability to take payments.
A growing share of the problem is “friendly fraud” — a customer who genuinely received what they ordered but disputes the charge anyway, sometimes forgetting the purchase, sometimes gaming the system. It’s maddening because you did nothing wrong, and it’s exactly why documentation matters so much.
Here’s how I’d think about protecting yourself, and it’s the same way I approached evidence as a litigator: assume you’ll have to prove your case to someone who wasn’t there. Make your billing descriptor clear, so the charge on a customer’s statement obviously matches your business — a huge share of “I don’t recognize this charge” disputes come from a confusing descriptor. Keep records: order details, delivery confirmation, signed receipts, communications, your refund policy displayed at the point of sale. Use the fraud tools your processor offers — address verification, card security codes, and for online sales, additional verification layers. Answer customer complaints fast and well, because a customer who can reach you doesn’t need to call their bank. And when a dispute does come, respond to it with organized evidence inside the window, every time. Merchants who simply ignore chargebacks lose by default.
The businesses that handle disputes well aren’t the ones who never get them. They’re the ones who built the habit of documentation before they needed it. Set that up now, while it’s calm.
Want help setting up fraud tools and a chargeback response process that actually holds up?
Comments