Chargeback Operations: A Merchant's Workflow
Chargeback operations is the discipline of watching disputes, answering them on time, and fixing what causes them. Here is how Visa and Mastercard say to run it.
A chargeback lands on a Tuesday. Another one comes Friday. If each one gets handled as a surprise, the work never ends and the same problems keep coming back. Chargeback operations is the fix for that. It treats disputes as a steady workflow, not a string of emergencies. This page lays out that workflow, using what Visa and Mastercard say about it.
What chargeback operations covers
Chargeback operations covers four kinds of work. First, watching your dispute activity so nothing arrives as a surprise. Second, answering each dispute within the time your acquirer gives you. Third, tracking disputes by type and by channel so patterns show up. Fourth, fixing the root causes with your acquirer so the same disputes stop repeating.
It is not the same as chargeback management as a broad subject, though the two overlap. Management is the whole field. Operations is the day-to-day running of it: who checks the queue, who answers, and what gets fixed.
One reason the discipline matters is that you are not the only one watching. Acquirers are responsible for monitoring each of their merchants on an ongoing basis. Your bank is keeping score too. A shop that runs its own numbers first knows what its acquirer is seeing.
The core workflow: monitor, respond, resolve
The daily loop has three steps.
Monitor. Check your dispute queue on a set schedule, not when someone remembers. Watching dispute rates can help merchants find problem areas and improve how you prevent disputes. A dispute you find on day one is one you can still answer in time.
Respond. Each dispute needs an answer with evidence attached. Visa says a merchant may settle a dispute by giving its acquirer more details about the sale. That answer is called representment, and the full process of disputing a chargeback has its own page. The short version: send the proof that fits the claim, not everything you have.
Resolve. When the answer goes in, record the outcome. Won, lost, or settled, each result tells you something about the next fix. A stack of wins on the same claim type means the fix is working. A stack of losses means it is not.
Response timelines and why they vary by acquirer
Every merchant asks how long they have to answer. The honest answer is that it depends, and Visa says so plainly. Visa says the merchant's time to respond is the time on the acquirer's request, and it may vary by acquirer.
Trust the date on the request in front of you. Not the one another shop got from its bank. Not one from an old request. Open each request the day it lands and plan around that date.
The practical habit is simple. When a dispute request comes in, log the due date the same day. Build your answer schedule backward from it. If your acquirer gives you a portal or a contact for questions, use it when a date is unclear.
Measuring your dispute activity
You cannot run operations without a number to watch. Visa suggests merchants track dispute activity as a share of sales activity. That ratio, disputes over sales, is the one that shows whether things are getting better or worse over time.
Track it monthly, and track it in a way you can compare. A single month tells you little. A year of months shows a trend, and a trend is what you act on.
One split matters more than the rest. A merchant that sells both in person and online should track those disputes separately. The two channels produce different problems. Mixing the two muddies both numbers.
Tracking disputes by type and channel
Beyond the ratio, track what kind of dispute each one is. Track your disputes by type, since each type points to its own business problem and fix.
A fraud claim on online sales points at your checkout and your identity checks. A claim that goods never arrived points at your delivery records. A claim of a duplicate charge points at your billing system. A claim that the goods were not as described points at your product pages.
Each type gets its own count, and each count gets compared month to month. When one type jumps, that jump is your next project. The customer side of the same coin is the chargeback itself. Knowing how a cardholder files one shows where your own process leaks.
Root-cause fixes with your acquirer
Answering disputes well is defense. Fixing causes is offense. Visa advises merchants to work with their acquirer on a plan that finds the root cause of their disputes.
The reason is that many disputes come from avoidable mistakes in how a merchant processes a sale. A wrong amount keyed in. A subscription billed twice. These are not fraud. They are process errors, and process errors can be fixed.
Some fixes are cheap and quick. If a customer with a valid complaint contacts you, act promptly and issue a credit as appropriate. A refund given today costs less than a dispute fought next month. Proof of delivery or pickup lets you answer a dispute where the customer says the goods never came. Make that proof a standard part of your shipping routine.
Work with your acquirer on a plan that finds the root cause of your disputes and how to fix it.
When to accept a dispute rather than fight it
Not every dispute deserves a fight. Visa says accepting a dispute that cannot be fixed may save the time and cost of fighting it.
The math is blunt. Visa says a merchant can lose the sale amount and the goods, and also pay its own costs to respond. Fighting a weak case means spending hours and money on a claim you were going to lose anyway.
So build a rule into your operations. Accept a dispute when you have no evidence that answers the specific claim. Accept it when the cost of building an answer exceeds the amount in question. Fight when your records speak directly to the claim, like delivery proof against a "never arrived" case.
A cardholder who files a dispute with their bank may have a real complaint. See how that works from the cardholder side. Some of those complaints are best answered with a refund before the dispute ever forms.
What happens when chargeback rates climb too high
This is where operations stops being an internal matter. Mastercard designed the Excessive Chargeback Program so each acquirer closely watches chargebacks at the merchant level. The ECP lets Mastercard find out promptly when a merchant has gone over monthly ECP thresholds.
The measurement is monthly. Mastercard compares a merchant's chargebacks in a calendar month with its Mastercard transactions in the month before. A merchant can be an Excessive Chargeback Merchant (ECM) or, at a higher level, a High Excessive Chargeback Merchant (HECM).
The consequences reach beyond Mastercard. Excessive Chargebacks is one of the reasons a merchant can be listed in the MATCH Pro system.
One measurement is the VAMP ratio. The VAMP ratio adds the count of fraud and disputes, then divides by the count of settled transactions. It is a different formula from a simple dispute rate, because it counts fraud as well as disputes.
The lesson in all of it is the same. A merchant that watches its own numbers, answers on time, and fixes causes can see these thresholds coming.