Chargeback Prevention: Visa's New 2026 Threshold

A chargeback is what happens when a customer disputes a charge directly with their bank instead of contacting the store for a refund — and it’s expensive in a way a normal refund isn’t. A store on the losing end of a chargeback typically loses the product, the shipping cost already spent, and a separate dispute fee from the payment processor on top, usually somewhere between $15 and $25 per incident regardless of the original order size. A handful of chargebacks a month is a real, if manageable, cost of doing business. The bigger risk sits one level up.

Visa runs a chargeback monitoring program, and in 2026 it lowered the threshold that flags a merchant as high-risk from 2.2% of transactions down to 1.5%, across both North America and Europe. Nothing about how a store operates has to change for this to matter more than it did last year — the bar itself simply moved closer, and a store sitting comfortably under the old threshold might not be under the new one. Cross that 1.5% line and a merchant risks extra monitoring, higher processing fees, and in more serious or repeated cases, losing the ability to process card payments altogether — a genuinely business-ending outcome for a store that depends entirely on card checkout.

For most small stores, this isn’t a five-alarm emergency — the overwhelming majority sit well under 1%. It is, however, a good reason to actually know the number on purpose, rather than finding out about it for the first time in a stern email from a payment processor.

Where chargebacks actually come from, and why most of them aren’t fraud

It’s tempting to picture chargebacks as mostly fraud — stolen cards, bad actors — and treat prevention as purely a security problem. In practice, a large share of chargebacks at small stores come from something much more mundane: a customer genuinely forgets they made a purchase weeks earlier and disputes it as unrecognized, or a customer doesn’t know where their package is, gets frustrated, and disputes the charge instead of emailing support first because disputing feels faster and guaranteed. Both of these are addressable without touching fraud detection at all.

Clear, specific billing descriptors — the text that shows up on a customer’s bank statement — reduce the “I don’t recognize this charge” category directly, simply by making the charge recognizable at a glance instead of showing a cryptic processor name the customer has never seen before. Proactive order-status emails (confirmed, shipped, out for delivery, delivered) reduce the “where’s my package, I’m disputing this” category by giving an anxious customer an obvious next step — checking the email you already sent — before their next move becomes calling the bank.

Checking and tracking the number itself

Most payment processors show a chargeback rate directly in their dashboard, and most store owners have simply never looked. Check it this month as a first step, treat anything above roughly 1% as worth active attention, and anything above 1.5% as urgent rather than routine. From there, the useful habit is checking it monthly going forward rather than only when a processor flags a problem — a rate creeping upward over three months is much easier to fix quietly than a rate that’s already crossed the threshold and triggered a formal review.

If a genuine spike does show up, the fastest diagnostic is usually pulling the specific disputed orders and looking for a pattern: one product with a description mismatch, one shipping delay window, one specific customer segment. Chargeback spikes are rarely random — they usually trace back to one fixable thing once someone actually looks at the disputed orders side by side instead of just the aggregate percentage.

Two questions worth answering before this becomes urgent

Does a refund policy that’s too strict actually cause more chargebacks? Often, yes — a customer who feels a refund request will be denied or fought over is more likely to go straight to their bank instead of asking the store first, since a bank dispute feels like the guaranteed path. A visibly fair, easy-to-find refund policy quietly reduces chargebacks by giving frustrated customers a first option that isn’t the bank.

Is it worth disputing a chargeback once it happens, rather than accepting the loss? Usually only when there’s clear evidence the customer is wrong — a delivery confirmation with signature, a support conversation showing the issue was already resolved. Disputing a chargeback with weak evidence just spends more time for the same outcome; the better use of that time is almost always fixing whatever pattern caused it, so the next one doesn’t happen.

Getting real visibility into this number automatically, rather than checking it manually once a quarter, is part of the broader payment and carrier integration work — connecting the systems that would otherwise require someone to remember to go check a dashboard nobody has time to check often enough.