MDR Not Reversed on Refunds and Chargebacks: The Compounding Cost

Terra Insight Reconciliation Infrastructure

Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →

Published 23 June 2026

Domain expertise

TDS Reconciliation GST Input Credit Platform Settlements NACH Batch Matching Bank Reconciliation Form 26AS Matching ERP Integrations Enterprise Finance Ops

Reviewed by

Navin Krishnan

Managing Director & Founder — Terra Insight

Ex Amazon India · Intuit QuickBooks · Tata nexarc

ISO 27001:2022 Patent Pending Incorporated 2024

Knowledge Card

Problem

Indian merchants book gross GMV at the point of sale and lose MDR on every transaction; when the customer is refunded or charges back, the original MDR stays with the gateway and the loss is silent. Most ERP and finance stacks do not surface this as a discrete line — refunds reverse the sale and the MDR loss vanishes into general gateway expense, while chargebacks add a dispute fee that is usually netted off in the settlement without a contractual cross-check. For a subscription business with monthly cancellations the cost compounds across the subscriber lifetime.

How It's Resolved

Refund-MDR reconciliation joins each refund event in the settlement file to the originating sale's MDR line and computes the retained MDR (full original MDR minus any partial rebate per the merchant's contract). Chargeback reconciliation matches each dispute event against the contracted per-dispute fee schedule keyed on network and scope (domestic / international), and separately tracks the transaction-value debit. A monthly aggregation surfaces the three variance classes (REFUND_MDR_LOSS, CHARGEBACK_DISPUTE_FEE, CHARGEBACK_TXN_LOSS) by gateway, network and SKU.

Configuration

Refund-MDR retention flag per gateway rule (default: retain 100 percent; enterprise contracts may carry a partial rebate); per-dispute fee schedule per network and scope; chargeback variance classes (REFUND_MDR_LOSS, CHARGEBACK_DISPUTE_FEE, CHARGEBACK_TXN_LOSS); monthly aggregation report by SKU / subscription-tier for subscription businesses; GST-on-fee retention line for the 18 percent component that does not reverse with the sale.

Output

A monthly refund-and-dispute cost dashboard with three discrete variance lines, a per-SKU and per-subscription-tier ranking of refund-MDR loss for the marketing and product teams, a chargeback dispute-fee reconciliation against the contracted rate card with overcharge flags, and an audit-ready trail of the retained MDR and the GST that did not reverse with the underlying sale.

A D2C cosmetics subscription brand sells a ₹999 monthly skincare kit, processes ₹2.5 crore of monthly GMV across credit and debit cards, and posts a steady 6 percent monthly refund rate plus a 0.4 percent chargeback rate. The finance team reconciles the gateway settlement file every morning. The MDR line for the month nets to roughly ₹50 lakh and matches the contracted blended rate. The refund file matches the customer credits to the original sales. The chargeback file matches the disputed transactions to the debit notes. Every individual reconciliation closes clean, and the CFO signs off the gross-to-net margin reconciliation at the monthly close.

The cost that is not reconciled is the MDR retained on the refunded and charged-back transactions. It is real, it is recurring, and on a subscription business with monthly cancellations it compounds across the subscriber lifetime. This article walks through how the cost arises, how it is detected, and how to instrument the reconciliation discipline that converts an invisible drag into a tracked KPI.

Quick-Reference: How MDR Behaves on Refunds and Chargebacks in India

Aspect	Detail
Industry default on refund	MDR on the original transaction is non-refundable
Industry default on chargeback	MDR retained, plus a per-dispute fee, plus transaction-value debit if lost
Per-dispute fee range (domestic)	₹200 to ₹750 across major Indian gateways
International card chargeback fee	Typically at the upper end of the domestic range or higher
GST on the MDR	18 percent; does not reverse when the MDR is retained
Regulatory framework on disputes	RBI Harmonisation of TAT circular (20 September 2019) — governs credit timelines, not MDR reversal
Reconciliation owner	Merchant — gateway does not surface retained-MDR as a discrete line
Compounding profile	Linear on one-off refunds; subscription-multiplied on recurring-billing businesses

What Exactly Happens to the MDR When a Refund Is Processed?

The merchant agreement governs the answer, and the published agreements of every major Indian payment aggregator carry the same clause: MDR is earned on authorisation of the underlying sale and is non-refundable on subsequent reversal. The economic chain explains it. When a card sale is authorised, the interchange (typically the largest sub-component of MDR, around 1.5 percent on a domestic Visa or Mastercard consumer credit card) is paid to the issuer bank. The scheme fee is paid to the network. The acquirer margin is paid to the acquiring bank. The gateway’s own margin sits on top. When the sale is refunded, the network does not reverse the interchange; the issuer keeps it. The acquirer does not reverse the acquirer margin. The gateway therefore cannot reverse the merchant-facing MDR without absorbing the loss itself.

The Reserve Bank of India’s framework on payment disputes (most relevantly the Harmonisation of Turn Around Time circular of 20 September 2019) governs the timelines for crediting failed and disputed transactions back to the customer, but does not require the gateway to reverse the MDR on a refunded transaction. That is a contractual matter between the merchant and the gateway, and the standard contract is zero reversal.

Some enterprise contracts now carry a partial refund-MDR rebate (commonly 25 to 50 percent of the original MDR, recovered from the gateway’s own margin after deducting interchange and scheme fees). The default published agreement does not.

What Does a Chargeback Actually Cost Beyond the Lost MDR?

A chargeback is a customer-initiated dispute filed with the issuer bank. The merchant absorbs three discrete costs on the same transaction:

The original MDR is retained by the gateway, identical to a refund.
A per-dispute fee is levied by the gateway regardless of whether the merchant wins or loses the dispute. Published rates across major Indian gateways sit in the ₹200 to ₹750 band; international card chargebacks (Visa, Mastercard, Amex international BINs) are at the upper end.
If the merchant loses the dispute — either by not contesting it within the issuer’s representment window or by losing on the merits — the full transaction value is debited from the next settlement on top of the fee.

The dispute fee is the predictable recurring leakage line. The transaction loss is event-driven and depends on the chargeback-defence workflow. For reconciliation purposes the dispute fee should be tracked as its own variance class against the contracted rate card, so that the merchant can catch the case where the gateway has billed at a higher per-dispute rate than the contract specifies.

Where Does Subscription Business Compounding Hide the Cost?

A subscription business does not pay MDR once and refund once; it pays MDR on every billing cycle and refunds whichever cycles the customer disputes. The economic profile is fundamentally different from a one-off retail sale.

Consider a steady-state subscriber base on a ₹999 monthly plan with 6 percent monthly churn-with-refund. Every month, MDR is deducted on the full subscriber base. Every month, 6 percent of those subscribers refund their most recent cycle. The merchant therefore pays MDR on roughly 6 percent of GMV that yielded zero realised revenue, every month, indefinitely. On a base of ₹2.5 crore monthly GMV, that is ₹15 lakh of GMV per month producing zero revenue but full MDR — and the MDR on that ₹15 lakh is retained by the gateway.

The annualised drag is meaningfully larger than a one-time refund analysis suggests. A retail business with the same 6 percent refund rate on a single-purchase customer base would experience the loss only once per customer lifetime; a subscription business experiences it every cycle the customer remains on the plan, and then again on the refunded cycle when the customer churns.

The same compounding logic applies to chargeback dispute fees on a recurring-billing business where the chargeback rate is steady and the customer base is large.

What Does This Look Like on a Real Settlement File? A Worked Example

A D2C cosmetics subscription brand with the following profile:

Monthly GMV: ₹2.5 crore (cards-only for simplicity — the brand routes recurring billing through credit and debit cards)
Blended MDR contracted at: 2 percent (consumer credit, domestic standard slab)
Refund rate: 6 percent of GMV
Chargeback rate: 0.4 percent of GMV
Per-dispute fee: ₹500 (mid-band domestic rate)

Refund-MDR leakage in a month:

Refunded GMV: ₹2.5 crore × 6% = ₹15 lakh
MDR retained on the refunded GMV: ₹15 lakh × 2% = ₹30,000 per month
Annualised refund-MDR leakage: ₹30,000 × 12 = ₹3.6 lakh per year

Chargeback impact in a month:

Charged-back GMV: ₹2.5 crore × 0.4% = ₹10 lakh
Number of chargebacks at a ₹2,000 average ticket size: roughly 500 disputes per month
Per-dispute fees: 500 × ₹500 = ₹2,50,000 per month in direct fees
MDR retained on charged-back GMV: ₹10 lakh × 2% = ₹2 lakh per month
Total monthly chargeback cost (before transaction-value losses on lost disputes): ₹2,50,000 + ₹2,00,000 = ₹4,50,000
Annualised chargeback impact: ₹4,50,000 × 12 = ₹54 lakh per year

The combined refund-and-chargeback drag is ₹57.6 lakh annually before the merchant has considered the transaction-value losses on chargebacks it fails to defend or the 18 percent GST that does not reverse on the retained MDR. None of these lines appears as a discrete cost in a standard ERP. The CFO sees the MDR expense line and the chargeback debit notes, but not the structural cost of MDR retained on every cycle the subscription was eventually refunded.

For a brand with a 12-month subscriber LTV target, this leakage is comparable in magnitude to the discount margin the brand is willing to give up for retention promotions — but it is invisible in the cohort economics because it is buried inside the monthly MDR expense aggregate.

Reconciliation Discipline: Turning Retained MDR into a Tracked KPI

The reconciliation discipline has three components and one settlement-file requirement.

Settlement-file requirement. The gateway settlement file must include, per transaction, the original sale identifier on every refund and chargeback event. Most gateways provide this as original_payment_id or equivalent; the file must carry it through to the merchant’s data warehouse. Without the original sale linkage, the retained-MDR reconciliation cannot be computed deterministically.

Component 1: REFUND_MDR_LOSS variance. For every refund event, join to the originating sale and compute retained MDR = original MDR minus any contractual rebate. Aggregate monthly by gateway, network, instrument and SKU. For a subscription business, also aggregate by subscription tier and cohort vintage.

Component 2: CHARGEBACK_DISPUTE_FEE variance. For every chargeback event, match the per-dispute fee deducted in the settlement against the contracted rate card (domestic / international, network-specific). Raise a variance when the actual fee exceeds the contracted fee.

Component 3: CHARGEBACK_TXN_LOSS variance. For every chargeback event the merchant loses on the merits or fails to contest, the transaction value is debited from the next settlement. Track this as its own variance line; it is distinct from the dispute fee and depends on the chargeback-defence workflow rather than the gateway rate card.

The three lines together produce the audit-ready refund-and-dispute cost dashboard that the CFO can table at the monthly close. The dashboard is the right surface to compare cohorts, instrument mixes, and gateway routing decisions on a like-for-like basis.

Interactive Tool

Model the refund-and-chargeback drag on your subscription book

Plug in your monthly GMV, blended MDR, refund rate and chargeback rate to see the effective payment cost — including retained MDR on refunded cycles and per-dispute fees on chargebacks — and the annualised drag the standard MDR expense line does not surface.

Open the MDR Effective-Rate Calculator →

What Should Be on the CFO’s Monthly Cover Sheet?

Three numbers, every month, on the gateway-cost cover sheet:

Retained MDR on refunds — gross amount and as a percentage of refunded GMV. Trended against the contracted MDR rate so the CFO can see whether the gateway is honouring any enterprise refund-MDR rebate.
Chargeback dispute-fee leakage — gross amount, number of disputes, and the per-dispute fee delta against the contracted rate card.
Chargeback transaction-value losses — gross amount of disputes lost on the merits or uncontested, broken out from the dispute fee.

A fourth, optional, but useful for subscription businesses: retained-MDR drag per active subscriber, expressed as a rupee figure per subscriber per month. This converts an aggregate cost into a cohort-economics input the product and marketing teams can use when modelling LTV and retention promotions.

Continue Reading in This Cluster

This is pattern 7 of 8 in the merchant-fees leakage series. The other patterns and the cluster hub:

MDR fee reconciliation against contracted gateway rates — the cornerstone reconciliation discipline
Premium card misrouting to the 3% slab — BIN-tier audit — a sibling leakage pattern
MDR charged on zero-MDR UPI and RuPay debit — the highest-confidence deterministic leakage check
Merchant fees cluster hub — the full leakage taxonomy
Payment gateway reconciliation money page — TransactIG’s settlement-reconciliation surface

Primary reference: Reserve Bank of India — RBI's chargeback and dispute-management framework (Harmonisation of Turn Around Time circular, 20 September 2019) governs credit timelines for failed and disputed transactions, but does not require the gateway to reverse the original MDR on a refunded transaction — that is a contractual matter between the merchant and the gateway..

Frequently Asked Questions

Why don't payment gateways reverse the original MDR when a transaction is refunded?

The published merchant agreements of Razorpay, PayU, Cashfree, PhonePe, Paytm and BillDesk all carry the same clause: MDR is earned on authorisation of the transaction and is non-refundable on subsequent reversal. The economic basis is that the interchange the gateway pays to the issuer bank (the largest sub-component of MDR) is itself not reversed by the network on a refund — the issuer keeps the interchange, the network keeps the scheme fee, the acquirer keeps the acquirer margin, and the gateway therefore cannot reverse the merchant-facing MDR without absorbing the loss itself. Some gateways now offer a partial refund-MDR rebate on enterprise contracts, but the default is zero reversal.

Is the dispute fee on a chargeback separate from the lost MDR, and how large is it?

Yes — they are two separate losses on the same transaction. (1) The MDR on the original sale stays with the gateway. (2) A chargeback dispute fee is levied per dispute regardless of whether the merchant wins or loses the dispute; published rates across major Indian gateways sit in the ₹200 to ₹750 band, with international card chargebacks at the upper end. (3) If the merchant loses the chargeback, the transaction value is debited from the next settlement on top. The dispute fee is the predictable, recurring leakage line; the transaction loss is event-driven.

Does GST get refunded on the MDR component when a transaction is refunded?

The GST follows the underlying fee. Because the MDR is not reversed, the 18 percent GST on that MDR is also not reversed — the gateway has already paid the GST to the exchequer and the merchant has already claimed ITC against it. On the refunded order the merchant has lost the MDR and absorbed the GST as a sunk cost, even though the original sale itself is reversed and the merchant must refund the GST collected from the customer separately. This GST-on-fee asymmetry is a meaningful component of the leakage on a high-refund-rate business and is rarely modelled.

For a subscription business with a 6 percent monthly refund rate, how does the cost compound?

Each refunded month carries the original MDR loss. A subscriber who joins, pays four monthly cycles, and refunds the fifth has had MDR deducted on all five charges; the refund reverses only the fifth charge to the customer but leaves the merchant with the fifth-month MDR loss on a transaction that yielded zero revenue. On a steady-state subscriber base with 6 percent monthly churn-with-refund, the merchant pays MDR on roughly 6 percent of GMV that produced no realised revenue every month, indefinitely. The annualised drag is meaningfully larger than a one-time refund analysis suggests.

How is this reconciled inside TransactIG's settlement workflow?

A refund-MDR retention flag is enabled at the gateway-rule level so every refund event is reconciled against the originating sale's MDR line. The reconciliation produces a monthly REFUND_MDR_LOSS variance that aggregates by gateway, network, instrument and SKU. Chargebacks are reconciled separately: a CHARGEBACK_DISPUTE_FEE variance tracks the per-dispute fee against the contracted rate card, and a CHARGEBACK_TXN_LOSS variance tracks the debited transaction value. The three lines together produce the audit-ready refund-and-dispute cost dashboard the CFO can table at the monthly close.