MDR fee reconciliation — verifying gateway charges against contracted rates

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. From 15 October 2026, a new class of MDR billing error becomes possible on the UPI bank-account cell (deducting the pre-15-October zero MDR above ₹2,000, or over-deducting versus the notified 0.4% / capped ₹300 schedule) and a new compliance-monitoring obligation appears for merchants near the P2PM small-merchant threshold. 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.

The UPI MDR Landscape from 15 October 2026: Band-Aware, Not Uniformly Zero

A critical distinction post-15-October 2026: UPI bank-account P2M is no longer uniformly zero-MDR. The Taxation and Other Laws (Amendment) Act 2026 (Presidential assent 17 August 2026) narrowed Section 10A of the Payment & Settlement Systems Act to preserve the zero-MDR bar only for transactions at or below ₹2,000; the Ministry of Finance notified the amendment on 14 September 2026, and NPCI’s FAQ dated 15 September 2026 crystallised the operative schedule.

On UPI bank-account P2M, the network MDR now runs in three bands:

• At or below ₹2,000: zero network MDR (unchanged; about 95% of P2M count on NPCI’s own figure).
• Above ₹2,000 and below ₹75,000: 0.4% flat MDR. Sector overrides apply — flat ₹5 per transaction for railways, telecom, insurance, fuel and utility bill collection (education: flat-fee-or-capped per Q42, figure unstated); 0.02% for capital-markets flows (AMCs, brokers, dealers).
• At or above ₹75,000: capped ₹300 per transaction (or ₹300 under the 0.02% capital-markets cap regime).

Adjacent instruments unchanged by the amendment:

• RuPay debit — remains zero MDR full-range.
• RuPay-credit-on-UPI — approximately 2% above ₹2,000, nil below (NPCI October 2022 circular). Explicitly excluded from the new MDR per FAQ Q36.
• PPI / wallet-on-UPI — 0.5% to 1.1% above ₹2,000, nil below (NPCI 24 March 2023 circular). Unaffected.
• UPI AutoPay — explicitly exempt (FAQ Q22).

On top of the network MDR, the gateway platform fee is unchanged in kind. Gateways are entitled to charge their own commercial fee for providing the technology layer, dashboard access, settlement processing, and API infrastructure — this fee remains contractually agreed with the merchant and is unaffected by the network-MDR change. This means a merchant processing ₹1 crore per month through UPI bank-account via a payment gateway now potentially pays two positive charges above ₹2,000: the notified network MDR (a fraction of the volume in the mid-band at 0.4%) and the contracted platform fee (unchanged). The reconciliation must verify both — the notified MDR against the schedule above, the platform fee against the contracted enterprise rate — and both attract 18% GST on the fee only, claimable as ITC.

Domestic card and net banking MDR typically ranges from 1.5% to 2.5% depending on card type and gateway contract. International card transactions carry significantly higher MDR — typically 3% to 4.3% — due to cross-border interchange fees and currency conversion charges. These are unaffected by the UPI MDR change.

Sixth Check: UPI Band-Aware MDR Verification + P2PM Graduation Monitor

The pre-15-October reconciliation workflow ran five checks (rate verification per instrument, GST on MDR, refund reversal, TDS overlay where applicable, contracted-rate variance). Post-15-October, a sixth check applies specifically to UPI bank-account cells, with a linked seventh compliance-monitoring obligation for merchants near the P2PM small-merchant threshold.

Check 6a — UPI bank-account MDR at or below ₹2,000: zero-tolerance. Expected network MDR is zero. Any positive deduction is a FEE_DEDUCTION_UPI_ZERO_BAND exception, recoverable in full against the gateway. Applies to both bank-account UPI at or below ₹2,000 and to RuPay debit across the full range (Section 10A of the PSS Act as amended still applies to RuPay debit full-range).

Check 6b — UPI bank-account MDR above ₹2,000 and below ₹75,000: notified 0.4% flat with sector-override lookup. Expected: 0.4% x transaction value for standard merchant categories; flat ₹5 per transaction for essential-services categories; 0.02% x transaction value for capital-markets categories. Any material variance is a FEE_DEDUCTION_UPI_MID_BAND exception. The variance class requires a merchant-category-code lookup to select the correct expected rate. UPI AutoPay transactions are explicitly exempt regardless of ticket size and must be filtered out of this check.

Check 6c — UPI bank-account MDR at or above ₹75,000: cap enforcement at ₹300 per transaction. Expected: at most ₹300 per transaction (regardless of raw 0.4% calculation, which would exceed ₹300 above the ₹75,000 threshold). Any deduction above ₹300 on a single transaction is a FEE_DEDUCTION_UPI_CAP_BREACH exception, recoverable per transaction. For a ₹2,00,000 transaction, a raw 0.4% would be ₹800; the cap enforces ₹300; the ₹500 gap is the per-transaction recoverable.

Check 7 — P2PM small-merchant graduation monitor. For merchants whose inward UPI QR receipts are at or below ₹1 lakh per month (the P2PM small-merchant category under FAQ Q23, Q24, Q28, Q29), the network MDR is zero regardless of ticket size. A merchant is formally moved into the P2M chargeable category after inward UPI credits exceed ₹1 lakh per month for three consecutive months. The reconciliation must therefore run a rolling monitor on aggregate inward UPI QR receipts:

• Track monthly UPI QR inward receipts against the ₹1 lakh/month threshold.
• Alert the finance team when the rolling 3-month average approaches the threshold (e.g., at ₹90,000/month).
• Formally trigger a re-baseline of the merchant’s MDR expected-rate table (from the P2PM zero schedule to the P2M three-band schedule above) when three consecutive months exceed ₹1 lakh, with the graduation date recorded in the audit log.
• This monitor did not exist before 15 September 2026 and is a new compliance-monitoring obligation for merchants in the P2PM band.

Both Checks 6 and 7 read against the NPCI FAQ dated 15 September 2026 as their operative reference. Any post-15-October settlement close should surface UPI-band exceptions as their own reporting class, separated from the general FEE_DEDUCTION variance that covers card-instrument mis-billings.

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

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.

For the definitive current-state UPI MDR schedule effective 15 October 2026 — the 0.4% P2M merchant charge, three-band structure, sector overrides, P2PM small-merchant exemption + graduation rule, and the six-check merchant reconciliation playbook restated for the split-band world — see the UPI MDR 2026 flagship reference. The notified framework is currently subject to a pending Supreme Court challenge (PIL filed 16 September 2026).

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.

Frequently Asked Questions