The short version of how to handle chargebacks in customer service is that most of the work happens before the dispute is filed. A clear billing descriptor, a refund policy the customer can find, order and shipping notifications with tracking, and a support reply inside four hours prevent the majority of first-party disputes. Once the dispute lands, response windows are tight (30 days for Visa, 45 for Mastercard, 20 for Amex), and evidence must address the exact reason code. Prevention pays. Representment pays sometimes.
What is a chargeback and why does it matter now?
A chargeback is a payment reversal initiated by the cardholder through their bank rather than through the merchant. The bank pulls the funds from your account, holds them, and asks you to prove the transaction was valid. If you do not respond, or your evidence does not address the specific dispute reason, the customer keeps the goods and the money and you pay a fee on top.
The scale matters. U.S. chargeback volume is estimated to reach 146 million disputes valued at $15.3 billion in 2026. Globally, volumes are estimated at 261 million disputes worth $33.8 billion in 2025. Chargebacks911 puts total merchant cost above $100 billion in 2025 once direct losses, processing fees and operational overhead are counted. The average dispute costs merchants $74 per Mastercard data.
For a small store, a single chargeback is annoying. A pattern of them is dangerous. Payment networks watch merchant dispute ratios. Visa's dispute monitoring standard threshold was a 0.9% dispute ratio and at least 100 total disputes; the excessive threshold was 1.8% and 1,000 disputes. From April 2025 Visa consolidated the fraud and dispute programmes into the Visa Acquirer Monitoring Program (VAMP) with a single rate. Crossing a threshold means fines, mandatory remediation, and in extreme cases termination of your merchant account. Prevention is not optional above a certain volume.
What causes most chargebacks at a small store?
Three things, in roughly this order.
Friendly fraud, also called first-party misuse. The customer received the order but disputes the charge with their bank rather than asking for a refund from you. Sometimes deliberate, sometimes because a family member made the purchase and they did not recognise the descriptor, sometimes because a refund from you would take longer than a chargeback. Industry estimates put friendly fraud at 60% to 80% of digital-commerce disputes. Visa puts it at around 20% of all fraudulent disputes globally, up to 30% for high-volume online merchants. It is growing.
Customer confusion. The customer honestly does not recognise the charge on their statement. A billing descriptor that reads "PMT*STORE7742" is a chargeback magnet. Chargeback-management analysis attributes about 22% of friendly-fraud claims to customer confusion of this kind.
Genuine fraud. A stolen card was used. Rarer than the first two on most small stores, but the one where prevention hurts the least because the customer has a legitimate claim.
The reason-code distribution matters because prevention tactics differ by reason. There is no single "reduce chargebacks" button; there are several small levers that each move one reason code.
What actually prevents chargebacks?
The lever list, in order of return on effort.
Fix the billing descriptor. It should read as your public store name plus a short reference, ideally with a phone number the customer can call. Card networks give you the length. Use it. This one change usually cuts "unrecognised charge" disputes measurably.
Answer refund requests inside four hours during business hours. A customer who gets a friendly reply and a refund path in four hours does not walk to their bank. A customer who waits two days does. The refund is cheaper than the chargeback.
Publish the refund policy where the customer looks for it. Above the fold on the product page, in the checkout, in the order confirmation, in the shipping confirmation. Not buried in a footer link. Transparency reduces confusion, which reduces disputes.
Send order confirmations, shipping notifications, and delivery confirmations with tracking numbers. A customer who can see where their order is does not open a "did not receive" dispute out of anxiety. A signed delivery on high-value orders removes the strongest not-received defence a friendly-fraud claimant has.
Add a "contact us before disputing" line. Put it on the order confirmation, the shipping email, and next to the billing descriptor guidance on your site. A visible route to a refund persuades a share of would-be disputers to write in instead. It costs nothing.
Use AVS, CVV and 3D Secure. Address Verification System and card verification checks catch a share of stolen-card fraud at authorisation. 3D Secure shifts liability for the dispute to the issuer in most schemes. Talk to your payment provider about turning them on.
Send a proactive update when something goes wrong. A late shipment, a partial ship, an out-of-stock, a customs delay. The email you did not send because you were embarrassed is the email that generates the chargeback.
How to respond to a chargeback that lands
Time is tight. Missing the response window forfeits the case regardless of evidence.
- Visa: 30 days from the notification.
- Mastercard: 45 days.
- American Express: 20 days.
Step 1: read the reason code. Every network has a short list. The reason code determines what evidence wins. "Product not received" is not the same fight as "product not as described" is not the same fight as "credit not processed".
Step 2: decide whether to accept or represent. Accept if the customer is right, or if the amount is small and the evidence is weak. The industry math is stark: the average merchant wins roughly 45% of the chargebacks they challenge through representment, and the net recovery across all issued chargebacks is closer to 20%. Do not represent low-probability cases; the fee and the time are wasted.
Step 3: gather compelling evidence tailored to the reason code. Categories that reliably help:
- Order receipt with billing address and items.
- AVS and CVV response codes at authorisation.
- Delivery confirmation, and a signature where the value warranted one.
- IP address, device fingerprint and login history for the account.
- Prior successful transactions with the same card.
- The full support conversation with the customer before the dispute.
- Timestamps of every touchpoint on the order.
Step 4: write a short cover narrative that ties the evidence to the reason code. Do not send a document dump. Explain, in a paragraph, what happened, when, and which pieces of evidence prove it. Reference the timestamps.
Step 5: file inside the window. Log the outcome for the pattern analysis in the next section.
What the chargeback data tells you about the store
Every dispute is a data point. Log the reason code, the amount, the outcome, and the time from purchase to dispute. Read the pattern monthly.
If most of your disputes are "unrecognised charge", the descriptor needs work. If most are "not received", tracking and delivery-confirmation practice needs work. If most are "not as described", the product page and photo need to match reality. If most are "credit not processed", your refund workflow is too slow. If you see the same customer email twice, block or manually review that account.
The metric that matters here is the chargeback ratio, calculated as chargebacks divided by total transactions in the same period. Below 0.5% is comfortable. 0.5% to 0.9% is worth attention. 0.9% and above is where payment networks start to notice.
How Keloa approaches chargeback support
Keloa's AI agents answer refund and where-is-my-order questions from live order data through the integrations layer, so the customer who was thinking about disputing gets a real answer inside a minute. The unified inbox keeps the full conversation history, timestamped, so when a dispute lands the support conversation is one export away.
Disputes and cancellations always route to a human, never to the bot. Our companion piece on when not to use AI for customer service covers the escalation rule set. For the wider ecommerce support picture see the ecommerce solutions page.
Frequently asked questions
Is a refund always better than a chargeback for the merchant? Almost always yes. A refund costs the transaction fee. A chargeback costs the transaction, the fee, a chargeback fee (typically $15 to $25), and a hit on your dispute ratio. If the customer is going to get their money back either way, do it as a refund. Fast.
How long do we have to respond to a chargeback? 30 days for Visa, 45 for Mastercard, 20 for American Express. Missing the window forfeits the case. Set a shared calendar reminder the day the notification lands.
What is a "compelling evidence" package? Evidence that directly addresses the specific dispute reason code, not a generic document dump. For a not-received dispute, tracking and delivery confirmation. For a not-as-described dispute, the product page, photos, and any pre-purchase communication. For an unrecognised-charge dispute, the AVS and CVV response, IP and device match, and prior order history.
Should a small store use a chargeback-management vendor? Below about 20 disputes a month, do it in-house. Above that, the volume usually justifies a specialist that plugs into your payment provider, files representments automatically, and shares a cut of the recovered funds. Talk to two or three before signing.
Can AI decide whether to represent a chargeback? It can score the likelihood of winning based on reason code and evidence completeness. The decision to represent should stay with a human, because the cost of wrongly conceding is small and the cost of wrongly representing is a wasted fee plus a bumped dispute ratio.
What is the acceptable chargeback ratio? Under 0.5% is comfortable. 0.5% to 0.9% is worth attention. From 0.9% onwards you risk entering a payment-network monitoring programme, with fines and remediation obligations attached. Track it monthly.
Want to reduce disputes at your own store? Book a demo and we will look at your refund policy visibility, your descriptor, and where the AI can answer refund questions inside the four-hour window that matters.