Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
A finance team reviewing last week’s Razorpay settlement report finds three deductions that do not match any authorised refund. Two are chargebacks from card issuers — one from a transaction three months ago. Without order-level reconciliation, both would have been booked as unexplained deductions and written off. Chargeback reconciliation in India is the process of identifying those deductions, linking each one to the original order, and managing the dispute or representment within the window available.
What Chargeback Reconciliation Is
A chargeback is a transaction reversal initiated by the cardholder’s issuing bank on behalf of the cardholder — not by the merchant. Under RBI guidelines on failed and disputed transactions, the acquiring bank debits the merchant’s settlement account and notifies the merchant through the payment gateway. The deduction appears in the settlement report as a negative line item, typically without the original order reference that a standard refund would carry.
Chargeback reconciliation is the process of identifying each such deduction, classifying it correctly (chargeback versus refund versus MDR adjustment), linking it back to the original order in the ERP or order management system, and then either accepting the loss or submitting representment evidence within the allowed window.
In India, the 120-day window under Visa and Mastercard rules means a single settlement report may contain chargebacks from transactions that are three or four months old — outside the short-term memory of most manual reconciliation processes.
How Chargeback Reconciliation Works
Step 1: Classify Each Deduction in the Settlement Report
The first task is separating chargeback deductions from refund deductions and MDR fee deductions. All three appear as negative amounts in the same settlement file. The classification depends on the transaction type field or the deduction description provided by the gateway. Chargebacks typically carry a reason code from the card network (for example, “cardholder disputes” or “fraudulent transaction”). Refunds carry the original payment_id. MDR deductions are aggregated or per-transaction fee lines.
This step eliminates the error of booking a chargeback as a refund — which understates the dispute liability and overstates the refund volume in monthly reports.
Step 2: Match the Chargeback to the Original Order
Once classified, each chargeback deduction must be linked to its source transaction. The matching fields available are typically: the masked card number, the transaction amount, and the approximate transaction date (within the 120-day window). In high-volume environments where identical amounts repeat daily — for example, a subscription platform with thousands of ₹499 charges — amount-plus-date matching alone is insufficient. The card-number fragment becomes the primary identifier.
Where the original order is found, the chargeback record is linked to the order line in the ERP. Where no match is found, the deduction is flagged as unresolved and escalated to the finance team.
Step 3: Track the Dispute Window and Representment Outcome
After matching, each chargeback enters a dispute tracking workflow. The gateway-imposed response window is typically 5–10 business days. If the merchant elects to dispute, representment evidence — delivery proof, signed acknowledgement, IP logs for digital goods — is submitted through the gateway portal. The outcome is one of three:
- Representment accepted: Amount re-credited in a subsequent settlement cycle.
- Representment rejected: Amount is permanently lost; the deduction is written off.
- No dispute filed: Amount is treated as a loss at window expiry.
The reconciliation record must capture the outcome, the date of resolution, and the accounting treatment applied.
Chargeback vs Refund vs MDR Adjustment
| Type | Trigger | Appears in settlement as | Resolution path | ITC impact |
|---|---|---|---|---|
| Chargeback | Cardholder dispute via issuing bank | Negative deduction, chargeback reason code | Representment within gateway window (5–10 business days) | Credit note only if supply was reversed |
| Refund | Merchant-initiated return | Negative deduction linked to payment_id or order_id | Match to original order and credit note | Credit note required; ITC reversal in GSTR-3B |
| MDR adjustment | Gateway fee for processing | Per-transaction or aggregated fee deduction | Verify against contracted MDR rate | GST on MDR recoverable as ITC (18% GST) |
| Chargeback reversal (representment) | Successful merchant dispute | Positive re-credit in subsequent settlement | Match to original chargeback record | No additional GST impact |
India-Specific Compliance Context
RBI’s guidelines on failed and disputed transactions establish the framework within which acquiring banks and payment gateways operate the chargeback process in India. Visa and Mastercard impose the 120-day window at the card network level — this window applies regardless of which Indian gateway processed the transaction.
From an accounting and GST standpoint, chargebacks that involve the actual return or non-delivery of goods require a credit note under Section 34 of the CGST Act. Where the chargeback represents a fraudulent claim against a transaction that did occur and the goods were delivered, no credit note is issued. Finance teams must apply this classification at the time of dispute resolution, not at the time the chargeback first appears in the settlement.
For merchants selling across multiple gateways, each gateway maintains its own chargeback queue. A consolidated chargeback reconciliation view — aggregating deductions from Razorpay, PayU, Cashfree, and others — requires mapping gateway-specific reason codes to a common classification taxonomy before matching can begin.
Systematic payment gateway reconciliation reduces the risk of undetected chargeback deductions being written off without dispute. Organisations scaling beyond manual processes use reconciliation software India to automate the matching of settlement deductions against order records across multiple gateways simultaneously.
The Reserve Bank of India’s guidelines on disputed transactions provide the regulatory basis for the chargeback framework that acquiring banks and gateways implement in India.
The five FAQs below address the specific timelines, classification decisions, and multi-gateway scenarios that arise in practice.