Chargebacks for Indian Sellers: A Working Guide

Chargebacks are the one payment loss that compounds. A refund ends a problem. A chargeback ends a problem, takes a fee, and adds a mark to a ratio that can eventually cost you the ability to accept cards at all.

Chargeback, refund, RTO: three different losses

A refund is merchant-initiated. You control the timing, the amount and the record. It is the cheapest of the three because it closes the matter permanently.

An RTO is a delivery failure. The parcel comes back. On COD no payment ever settled; on prepaid you refund. You lose forward freight, reverse freight and handling. There is no payment dispute and no scheme consequence.

A chargeback is a forced reversal. The cardholder raises it with their issuing bank, the issuer pushes it through network rails, and the money leaves your settlement whether you agree or not. You lose the goods, the payment, the original processing fee, and a dispute fee that commonly runs Rs 500 to Rs 1,500 at Indian aggregators. You also add one to a monitored ratio.

Only the third carries scheme risk. Track all three in separate buckets, or you will keep solving the wrong problem with the wrong team.

Why disputes happen here specifically

India mandates additional factor authentication on most card transactions. Because 3DS and OTP are standard, the classic unauthorised-use dispute is far weaker here than in markets without AFA, and liability commonly sits with the issuer rather than with you. That single regulatory fact reshapes the entire local mix.

What Indian sellers actually face is goods not received, goods not as described, a cancelled recurring payment still charged, credit not processed after a promised refund, and duplicate or incorrect amounts. Every one of those is won or lost on delivery evidence and communication records, not on fraud tooling. If you are buying a fraud stack to fix an Indian dispute problem, check the reason code split first.

Two timing facts to hold. Customers typically have up to 120 days from the transaction or expected delivery date to raise a dispute, which means an order shipped in March can reverse in July. And RuPay reason code 1065, account debited but confirmation not received at the merchant, carries a mandatory T+5 calendar day resolution window, far tighter than the 30 to 45 day windows typical on Visa and Mastercard. Separately, failed transactions sit under the RBI harmonised turnaround time framework, with compensation payable to the customer for delayed reversal.

The evidence pack that wins

• Authentication proof. The 3DS or AFA result, authorisation code, ARN, and the exact transaction timestamp.
• Order record. IP address, device details, email and phone captured at checkout, and whether the delivery address matches earlier orders on the same account.
• Delivery proof. Carrier tracking events with timestamps, the proof of delivery, and the delivery OTP or signature. For any not-received claim this is the decisive document. If your 3PL does not surface delivery OTPs into a report you can pull yourself, fix that before you fix anything else.
• Policy proof. A dated capture of the refund, shipping and cancellation policy exactly as displayed at checkout on the order date, plus the terms acceptance record.
• Communication log. Every ticket, email and WhatsApp thread with the customer, in sequence, with timestamps. Silence on your side reads as fault.
• Relationship history. Prior orders from the same customer, delivered and undisputed. This quietly resolves a large share of first-party claims.

Submit it as one PDF in that order, opening with a one-page cover that names the reason code, states your counter-fact in two sentences, and lists the exhibits. Whoever reviews it at the issuer gives it minutes, not hours. Structure is worth as much as substance.

Deadlines lose more cases than weak evidence does. The network window may be 30 to 45 days, but your aggregator passes down a much shorter one, often 7 to 10 days and sometimes 72 hours. A lapsed dispute is lost no matter how good the pack was. Route dispute notifications to a shared inbox with a named owner and a daily check, not to the founder address that opened the account three years ago.

Keeping the ratio low

Know the thresholds you are measured against. Mastercard’s Excessive Chargeback Merchant tier triggers at 100 chargebacks and a 1.5 per cent monthly ratio together. Visa consolidated its dispute and fraud monitoring programmes into VAMP in 2025, with the excessive threshold ratcheting toward 0.9 per cent from April 2026 alongside minimum count floors. Breaching means fines first, then higher reserves and slower settlement, then termination and a MATCH listing that makes replacement acquiring genuinely hard to obtain.

The levers that move the number, in order of effect:

• Billing descriptor. If the bank statement shows a legal entity name no customer recognises, you are manufacturing disputes. Use the brand name they see, with a contact number if the field allows it.
• Refund inside 48 hours. A refund costs you the goods. A chargeback costs the goods plus the fee plus the ratio. When a case is ambiguous, refund and move on.
• Delivery communication. Dispatch alert, out-for-delivery alert, and a delivered confirmation with a working tracking link. Most not-received disputes come from customers who cannot locate a parcel, not from fraud.
• Subscription hygiene. Pre-debit notification at least 24 hours ahead, one-click cancellation, and the renewal date printed on every confirmation. Cancelled-recurring is among the easiest codes to lose.
• Support responsiveness. Publish a first-response time and hit it. Customers escalate to their bank when a brand goes quiet, and the bank has a faster process than you do.

Review three numbers every month: disputes as a share of card transactions, win rate by reason code, and median days from dispute notification to evidence submitted. The third one predicts the other two, which is why it is the one to put on a dashboard.