Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
An enterprise processing ₹5 crore per month through a payment gateway at an average 1.8% MDR pays approximately ₹9 lakh per month in fees. A 0.2% billing error — applying the credit card rate to a debit card transaction — costs ₹1 lakh per month. MDR reconciliation is not a compliance exercise. It is a cost verification exercise, and the cost of not doing it accumulates silently in every settlement cycle.
What MDR Fee Reconciliation Is
MDR (Merchant Discount Rate) is the fee that a payment gateway charges the merchant for each processed transaction. The rate is not flat across all transactions — it varies by payment instrument (credit card, debit card, UPI, net banking, international card), by card network (Visa, Mastercard, RuPay), and sometimes by transaction size. Each merchant has a contracted MDR schedule with their gateway, which specifies the applicable rate for each instrument category.
MDR fee reconciliation is the process of verifying that every MDR deduction in the settlement report corresponds to the correct rate for the specific transaction type. Where the actual deduction exceeds the expected deduction — a variance classified as FEE_DEDUCTION — the excess represents a billing error that can be recovered through a formal adjustment request to the gateway.
GST at 18% is applied on MDR, making the full reconciliation scope: contracted rate × transaction amount = expected MDR; expected MDR × 1.18 = expected total deduction including GST. The 18% GST component is separately recoverable as ITC.
How MDR Fee Reconciliation Works
Step 1: Reconstruct Expected MDR Per Transaction
For each transaction in the settlement report, the reconciliation calculates the expected MDR based on three inputs: the transaction amount, the payment instrument type, and the contracted rate for that instrument. Instrument type is typically available in the settlement data as a payment method field (for example: CREDIT_CARD, DEBIT_CARD, UPI, NETBANKING, INTERNATIONAL_CARD).
Where instrument-level detail is not available in the settlement file, it must be sourced from the gateway’s transaction report and joined to the settlement file on payment_id. Without instrument-level detail, it is impossible to verify MDR accuracy — all transactions would appear to be billed at a single undifferentiated rate.
Step 2: Compare Actual MDR to Expected MDR
The actual MDR deducted is available in the settlement report either per transaction (detailed settlement) or as an aggregated fee at the end of the settlement period (summary settlement). Detailed per-transaction MDR is preferable for reconciliation — it allows line-level comparison. Summary settlement MDR requires back-calculation from total fees divided by total volume, which can only catch systematic rate errors, not individual transaction mis-billings.
Each transaction where actual MDR differs from expected MDR is flagged as a FEE_DEDUCTION exception. The exception record carries: transaction ID, transaction amount, instrument type, expected rate, applied rate, and variance amount.
Step 3: Verify GST on MDR and Claim ITC
The gateway deducts GST on MDR at 18%. This GST component is claimable as ITC by GST-registered merchants, provided the gateway issues a valid GST tax document (tax invoice or statement of charges) for the MDR. The reconciliation verifies that the GST amount deducted on MDR matches the expected 18% of the MDR charged, and that the supporting tax document is available for ITC claims in GSTR-3B.
MDR Rate Reference by Instrument
| Instrument | Approx MDR | GST on MDR | ITC eligible | Reconciliation key field |
|---|---|---|---|---|
| Domestic debit card | Varies by plan (0% for eligible small merchants per RBI) | 18% on applicable MDR | Yes — if MDR > 0 | Card type + merchant tier |
| Credit card (domestic) | 1.5%–2.5% depending on card category | 18% | Yes | Card network + card type |
| UPI (P2M up to ₹2,000) | 0% | Not applicable | Not applicable | Transaction amount + method |
| Net banking | Flat ₹10–₹25 per transaction | 18% | Yes | Payment method = NETBANKING |
| International card | 2.5%–3.5% | 18% | Yes | Card country code or network flag |
India-Specific Compliance Context
RBI has issued specific guidance on MDR for debit card transactions and UPI payments. The removal of MDR on debit card transactions for qualifying small merchants was a regulatory intervention to encourage digital payments. Merchants who qualify for zero-MDR treatment on debit cards but are being billed at a standard rate have a clear, RBI-supported basis for a fee adjustment claim.
GST on MDR creates a second reconciliation dimension. The gateway’s tax document must match the MDR amounts in the settlement report for ITC claims to hold at audit. A scenario where the settlement shows ₹90,000 in MDR deductions but the gateway’s GST invoice shows ₹85,000 produces an ITC discrepancy — the merchant can only claim ITC on the invoiced amount, regardless of actual deductions.
For merchants who moved from one gateway pricing plan to another mid-year, the contracted rate may have changed for a subset of transactions. MDR reconciliation must apply the correct rate schedule to the correct date range — pre-change transactions at the old rate, post-change transactions at the new rate — or it will generate systematic false FEE_DEDUCTION exceptions.
Full payment gateway reconciliation includes MDR verification as a standard exception category. Reconciliation software India applies the correct contracted rate schedule to each transaction and raises FEE_DEDUCTION exceptions automatically, enabling finance teams to pursue gateway adjustments with a documented exception log.
The Reserve Bank of India publishes circulars on MDR rates and payment system fee structures, which serve as the regulatory reference for zero-MDR eligibility and instrument-specific rate limits.
The five FAQs below address the calculation, ITC treatment, UPI zero-MDR rules, and common exception types encountered in MDR reconciliation.