Payments Glossary · Risk & Compliance

Chargeback

Also called card dispute reversal

A forced reversal of a card sale, initiated by the issuing bank at the cardholder's request, that pulls funds back out of your account.

What it is

A chargeback is the mechanism by which a card issuer reverses a settled transaction and takes the money back from the acquirer, which takes it back from you. It exists because the card networks promise cardholders protection, and that promise is funded, ultimately, by merchants. The sequence is consistent across networks. The cardholder contacts their issuer. The issuer assigns a reason code and initiates the dispute. Your acquirer debits your account for the transaction amount plus a chargeback fee, commonly 15 to 40 dollars, which you pay whether you win or lose. You then have a short window, typically 7 to 30 calendar days depending on the network, reason code and your acquirer's internal deadline, to submit compelling evidence in a process called representment. If the issuer accepts it, the funds return. If not, the case can escalate to pre-arbitration and arbitration, where the losing party pays network fees that can exceed the transaction value. Two things surprise merchants. First, a refund does not prevent a chargeback: if you refund after the dispute is filed, you can lose both the refund and the disputed amount. Second, chargebacks count against monitoring program ratios even when you win them, because most programs count disputes filed, not disputes lost. Card-present transactions with EMV chip authentication generally carry liability protection against fraud-type chargebacks. Card-not-present transactions do not, which is why the entire risk architecture of payments changes the moment a merchant starts taking orders online or by phone.

Why it matters to your business

For a small business, chargebacks are three costs stacked: the lost sale, the fee that applies win or lose, and the ratio damage that can eventually cost you your merchant account entirely. The third is the one that ends businesses, and it is the one nobody quotes you at signing. The single highest-return action is boring: make your billing descriptor recognizable. A large share of disputes are filed because the cardholder did not recognize the name on the statement. Get your DBA and phone number in that descriptor and you will prevent disputes you would otherwise have to fight. This is education, not legal advice; your dispute rights and deadlines are governed by network rules and your merchant agreement.

Where it gets contested

The structural complaint from merchants is that chargebacks were designed for an era of mail-order fraud and are now the default consumer path for any disappointment, dispute or forgotten subscription. Issuers, competing on service, make filing a dispute a two-tap operation in a mobile app, while the merchant's rebuttal must be assembled by hand and read by someone with little incentive to reverse a customer-friendly decision. The networks have responded with tools rather than structural change: rapid dispute resolution, order insight and alert services from Ethoca and Verifi that let a merchant refund pre-emptively. Those tools reduce dollars lost, and under Visa's current monitoring math a resolved dispute may still leave the associated fraud report in the numerator, which merchants read as a rigged scoreboard. The live and unresolved question is whether tightening thresholds through 2031 will simply push card-not-present merchants out of the acceptance market, or force better dispute-prevention products. Nobody has answered that yet.

How to check it yourself

Run a one-dollar charge on your own card and look at how it appears in your banking app. If you cannot recognize your own business from that descriptor in under two seconds, neither can your customers, and you are manufacturing disputes.

Receipts

Claims above that are checkable, with where to check them. Published so you do not have to take anyone's word for it.