Risk & disputes
Chargeback Management Guide
Chargeback management is the work of preventing disputes where you can, responding with evidence where you should, and keeping your dispute ratio below the levels the card networks monitor. A chargeback is a payment reversed by the cardholder’s bank; each one costs a fee, the sale and a mark against your account, so prevention is worth more than winning.
Summarize with
Key takeaways
- Most chargebacks fall into three groups: fraud, customer disputes and processing errors.
- A recognizable billing descriptor and an easy refund prevent a large share of them.
- Alerts let you refund a disputed sale before it becomes a chargeback.
- Fight the disputes you can document. Accept the ones you cannot.
- Your dispute ratio, not any single case, determines the health of your account.
What is chargeback management?
A chargeback is the card system’s protection for cardholders: someone who believes a charge is wrong can ask their bank to reverse it. Chargeback management is how a business limits how often that happens and handles each case when it does.
It has three parts. Prevention removes the reasons a customer would go to their bank, response is the handling of each case before its deadline, and monitoring is watching the totals. Done together, they let you see a pattern before a card network does.
How does a chargeback work?
- The cardholder contacts their bank, the issuer, and disputes a charge.
- The issuer assigns a reason code and, in most cases, credits the cardholder provisionally.
- The amount is pulled back from the merchant through the card network, and a chargeback fee is charged.
- The merchant may accept the chargeback or respond with evidence. This response is called representment.
- The issuer reviews the evidence and decides. Either side may be able to escalate to the card network for a final ruling.
Deadlines at each step are set by the card networks and are short. A response that arrives late loses by default.
Who is involved in a dispute?
Five parties touch every case. Knowing who decides what tells you where your effort counts.
| Party | Role | What they decide |
|---|---|---|
| Cardholder | Raises the dispute with their bank | Whether to dispute, and what reason to give |
| Issuer | The cardholder’s bank | Whether the dispute is valid and, after evidence, who is liable |
| Card network | Sets the rules, reason codes and deadlines | The final ruling if a case is escalated |
| Acquirer or processor | Passes the dispute and your response between you and the network | Whether your account needs closer monitoring |
| Merchant | Refunds, accepts or responds with evidence | Which cases to contest and how to prevent the next one |
You do not deal with the issuer or the network directly. Your processor or payments provider passes the case to you and your response back, and tells you the date by which it is due.
Why do chargebacks happen?
| Type | What happened | Typical prevention |
|---|---|---|
| True fraud | A stolen card was used | Address and security code checks, 3-D Secure, fraud screening |
| Customer dispute | The customer says they did not get what they paid for, or was not refunded | Clear terms, delivery evidence, fast refunds |
| Friendly fraud | The customer made the purchase but did not recognize or remember it | A recognizable descriptor, receipts, renewal reminders |
| Processing error | A duplicate charge, wrong amount or late presentment | Clean checkout logic and daily settlement |
How do you prevent chargebacks?
- Descriptor. Make the name on the statement the name the customer knows you by, with a phone number or site if possible.
- Communication. Send a receipt at once, a reminder before each recurring charge, and a clear way to reach you.
- Refunds. State the policy plainly and honor it quickly. A refund issued today cannot become a dispute next month.
- Authentication. Use address and security code checks for card-not-present sales, and stronger authentication on higher-risk orders.
- Records. Keep signed agreements, delivery confirmations and customer messages where you can find them.
What are chargeback alerts?
Alert programs notify a merchant that a cardholder has raised a dispute, before it is filed as a chargeback. You then have a short window to refund the sale. If you do, the dispute is resolved without a chargeback being recorded.
You still lose the sale, and alerts carry a fee. The benefit is to your ratio: fewer recorded chargebacks, and less exposure to monitoring programs. Lumino’s risk and disputes tools include chargeback alerts.
When should you fight a chargeback?
Fight when you can prove the cardholder authorized the purchase and received what was sold. Useful evidence includes:
- The signed agreement or accepted terms, with date and IP address.
- Proof of delivery or of use: tracking, logins, attendance, downloads.
- Correspondence showing the customer was satisfied or did not ask for a refund.
- Matching details between this purchase and earlier undisputed ones.
Accept the chargeback when you cannot document the sale, when a refund was genuinely due, or when the amount is smaller than the cost of your time. A weak response rarely succeeds.
What should a dispute response contain?
Your processor will show you the reason code and the date a response is due. Work back from that date and follow the same order every time.
- Read the reason code. It tells you what the cardholder claimed and therefore what you need to show.
- Check whether a refund has already been issued. If it has, say so and attach the proof.
- Gather only the evidence that answers the claim.
- Write a short cover note that states the facts in order and refers to each attachment.
- Submit through your processor’s dispute tool before the date, and keep a copy.
- Record the outcome and the reason, so that repeated causes can be fixed.
The response is read at the issuer by someone with many cases to get through. Short, relevant and clearly labeled serves you better than long. Even a well-documented case can be decided for the cardholder.
A worked example: how would an online store handle a disputed order?
It starts with a notification. An online store that sells office furniture learns that a customer has disputed a $600 order with their bank, saying they do not recognize the charge.
The store learns of it through an alert, before a chargeback is filed. It has a choice: refund now, which loses the sale but keeps the dispute off its record, or let the case proceed and answer it. The owner opens the order and finds that the delivery was signed for at the billing address and that the customer later emailed about assembly.
With that evidence she decides to contest, knowing that the chargeback will be recorded whatever the outcome. When it arrives, her processor shows the reason code and the response date. She submits the order confirmation, the signed delivery record and the email thread with a short note, and the issuer makes its decision.
Whatever the result, she asks why a real customer did not recognize the charge. The card statement showed the name of her holding company, not the store. She asks her provider to change the descriptor, which deals with the cause and not only the single case.
Illustrative
This store is hypothetical. The issuing bank decides the outcome of a dispute, and strong evidence does not ensure a decision in the merchant’s favor.
What mistakes should you avoid?
- Sending everything. A pile of unlabeled screenshots hides the one document that answers the claim.
- Refunding after the chargeback is filed. A separate refund on a sale that has already been pulled back can leave you paying twice, so check the status of the case first.
- Arguing in the response. The reader is the issuer, and tone does not substitute for proof.
- Treating each case as a one-off. The same reason code appearing again and again is a process problem, not bad luck.
- Leaving disputes to whoever is free. Without a named owner, cases wait until the date has passed.
- Tightening fraud rules without reviewing them. Filters that are too strict trade disputes for declined good customers, so check what they block.
Which ratios should you watch?
Card networks measure disputes and reported fraud against your transaction count. Visa’s program is VAMP; Mastercard runs its own. Merchants above a program’s threshold face fees, remediation plans and, if nothing improves, the loss of card acceptance.
Check your ratio every month and look at the trend, not the single figure. The VAMP compliance guide explains how the Visa program counts.
What should a monthly dispute review cover?
A ratio tells you that something changed, not what. A short review each month turns the figure into a decision.
- Count the disputes and fraud reports received and compare them with your transaction count.
- Group them by reason code and by product or offer.
- Check how many complaints were resolved by an alert or a refund before a dispute was filed.
- Review the cases you contested and what decided them.
- Pick one cause to fix before the next review, and name who owns it.
Keep the notes from each review. Over several months they show whether a fix worked, which a single month cannot.
How Lumino helps
How does Lumino help you manage chargebacks?
Risk & Disputes
Risk & Disputes notifies you when a dispute is raised and tracks deadlines, evidence and outcomes case by case, in the same dashboard as your payments. The merchant supplies the evidence and the issuer decides.
Card-on-File
With card-on-file, the customer’s authorization is captured with the first payment and every later charge sends a receipt, which gives you the consent record a dispute response needs.
Reporting & Analytics
Reporting & Analytics shows the status, refunds and disputes for each payment across your channels and merchant accounts, so a monthly review starts from one report and not from several exports.
About this guide
This guide is general information, not legal, tax or financial advice. Card network rules and state laws change, and they differ by business type. Check the current rules with your processor or counsel before changing how you price or accept payments.
FAQ
Common questions
What is the difference between a refund and a chargeback?
A refund is issued by the merchant. A chargeback is forced by the cardholder’s bank. A refund costs you the sale; a chargeback costs the sale, a fee and a mark against your dispute ratio.
What is the difference between a dispute and a chargeback?
The two words are often used for the same thing. Strictly, a dispute is the cardholder’s challenge to a charge, and a chargeback is the reversal of funds that follows when the issuer files it through the card network. An alert can let you resolve a dispute before it becomes a chargeback, where the networks support it. See risk and disputes.
What is a chargeback reason code?
A reason code is the label an issuer attaches to a dispute to say why the cardholder is contesting the charge. Each card network keeps its own list, grouped broadly into fraud, authorization, processing errors and consumer disputes. The code tells you which evidence is relevant, so read it before you write a response. See the chargeback glossary entry.
How much does a chargeback cost?
It costs the sale, a chargeback fee set by your provider, the time spent on the case and anything already delivered. The fee varies by provider and plan and is usually charged whether or not you win, so check your processing agreement for the amount that applies to you. See chargeback protection.
How long does a customer have to file a chargeback?
Time limits are set by each card network and depend on the reason for the dispute. They are commonly measured in months from the transaction or expected delivery date, which is why records need to be kept well beyond the sale.
Can chargebacks be eliminated entirely?
No. Any business that accepts cards will see some. The aim is to keep the ratio low and stable, and to resolve as many disputes as possible before they are filed.
What is a good chargeback ratio?
There is no single figure to aim for beyond staying well below the levels the card networks monitor. Those levels are set by each network, differ between programs and change, so we do not quote them here. Ask your processor for the thresholds that apply to your account and track your own trend. See the VAMP glossary entry.
Does a chargeback I win still count against my ratio?
In general, yes. Monitoring programs typically count disputes when they are filed, not when they are decided, so a case you win can still appear in the ratio. The counting rules belong to each card network and change, so ask your processor how your own figure is calculated. The VAMP compliance guide outlines Visa’s approach.
Does Lumino fight chargebacks for me?
Lumino provides monitoring, alerts and a workflow for responding, and our team will explain what evidence a case needs. The merchant supplies the evidence, and the issuing bank makes the decision.
Summarize with
Go through your disputes with our team.
Bring your recent chargebacks and we’ll look at the reasons, the deadlines and what could be caught earlier.