RuPay Debit MDR Reconciliation for Indian Merchants: Zero-MDR Audit Path

A finance head reading a payment-gateway settlement file in 2026 will see a debit MDR line and, in nine cases out of ten, will not interrogate the network split inside it. The split is the entire point. RuPay debit person-to-merchant MDR has been zero since 1 January 2020, by NPCI mandate flowing from Section 10A of the Payment and Settlement Systems Act, 2007 and Section 269SU of the Income-tax Act, 1961. Any positive network MDR billed on a RuPay debit transaction is, mechanically, leakage. And any RuPay-eligible debit card that is silently routed through the Visa or Mastercard rail costs the merchant cap-bound MDR (0.40% or 0.90%) on volume that should have settled at zero. The audit is per-transaction, the rule is binary, and the rupee impact is real and recoverable.

Why is RuPay debit P2M zero MDR while Visa and Mastercard debit are not?

The two debit regimes were set by different instruments and rest on different legal bases.

The general debit-card MDR cap dates to the RBI circular RBI/2017-18/105 (DPSS.CO.PD No.1633/02.14.003/2017-18), effective 1 January 2018. It tiered debit MDR at 0.40 percent (POS and online) and 0.30 percent (QR-code) for small merchants — annual turnover up to Rs 20 lakh — with a per-transaction cap of Rs 200; and at 0.90 percent (POS and online) and 0.80 percent (QR-code) for all other merchants, with a per-transaction cap of Rs 1,000. It also prohibits merchants from passing debit MDR to the customer through a surcharge. This cap remains current as of June 2026.

The zero-MDR mandate was a separate instrument set two years later. From 1 January 2020, Section 10A of the Payment and Settlement Systems Act, 2007, read with Section 269SU of the Income-tax Act, 1961 and Rule 119AA, prescribed UPI bank-account P2M and RuPay debit P2M as e-modes on which no network MDR may be charged. Businesses with turnover above Rs 50 crore must mandatorily offer these modes, on pain of a Rs 5,000 per day penalty under Income-tax Act Section 271DB. The mandate is funded through a Ministry of Finance incentive scheme to the acquiring banks; the FY27 Budget allocation is Rs 2,000 crore.

The practical effect is that the 2017 RBI cap now binds only non-RuPay debit. RuPay debit is mandated to zero; Visa and Mastercard debit are capped but non-zero. A merchant whose debit volume skews toward Visa and Mastercard pays cap-bound MDR on transactions that, had the same card been issued or routed on RuPay, would have cost nothing.

What does a leakage flag look like on a RuPay debit transaction?

The detection rule is one line: a positive network MDR amount on a transaction where the card network is RuPay and the instrument is debit is a leakage flag. There is no ticket-size carve-out, no turnover slab, no transitional clause. The mandate is absolute.

In settlement-file practice the audit is mechanical. Pull the settlement file with per-transaction detail. Confirm it carries a payment-instrument field and a card-network field — most Indian gateways expose both, the network derived from the card’s first six digits (the Bank Identification Number). Filter to instrument = debit and network = RuPay. Sum the MDR column for that slice. The expected value is zero. Any non-zero amount is a billing error.

Two distinctions matter. First, network MDR is not the same as the gateway’s platform or technology fee. Several aggregators bill a flat platform fee on all transactions including RuPay debit; that fee is a separately contracted commercial line and is not affected by the zero-MDR mandate. The reconciliation must keep network MDR and platform fee on different rows. Confusing the two is the most common reason a merchant raises a fee-recovery claim and is told, correctly, that the deduction was the platform fee, not MDR.

Second, GST at 18 percent is computed on the fee, not on the transaction value, and is itself a separate reconciliation line. A merchant whose RuPay debit MDR has been billed at non-zero will also have been billed GST on that fee; both are recoverable but must be reconciled and claimed as separate ledger entries.

How does BIN-tier routing optimisation reduce RuPay-eligible volume that ends up on Visa or Mastercard?

Many Indian issuer banks issue dual-badged debit cards — a single physical card that carries both a RuPay logo and a Visa or Mastercard logo, with two BINs encoded on the card. When the cardholder taps or swipes at checkout, the acquirer’s routing rules decide which network the transaction settles on. If the default routing is Visa or Mastercard, the merchant pays cap-bound MDR even though a zero-MDR rail was available on the same card.

BIN-tier routing optimisation is the practice of using the BIN to decide network. For dual-badged cards, the policy a cost-rational merchant wants is straightforward: prefer the RuPay rail wherever the issuer and acquirer both support it. The configuration is not at the merchant’s checkout — it is at the acquirer level. The merchant’s role is two-fold: request the policy change in writing at contract negotiation and renewal, and audit the per-network split each month to confirm the policy is being honoured.

Gateway and acquirer sales teams rarely volunteer this configuration. Routing co-badged volume to RuPay shifts MDR revenue from non-zero to zero, which is a margin line on their side. The merchant has to ask, has to cite the regulatory basis (PSS Act Sec 10A, Income-tax Act Sec 269SU, NPCI’s RuPay routing guidance), and has to verify on the settlement file.

A useful structural check, run quarterly, is the RuPay-eligible BIN audit. Pull the BIN of every Visa or Mastercard debit transaction in the period; cross-reference against the public RuPay BIN list (issuer banks disclose RuPay BIN ranges); compute the proportion of Visa and Mastercard volume that was on RuPay-eligible BINs. That proportion is the routing-shift opportunity. Multiplied by the contracted Visa/Mastercard MDR rate it gives the rupee value still on the table.

Worked example: quick-commerce merchant re-routing co-badged debit volume

A quick-commerce merchant processes Rs 15 lakh per month in debit-card GMV through its payment gateway. The current network mix is 32 percent RuPay, 68 percent Visa or Mastercard. The merchant is in the “other merchant” tier (annual turnover above Rs 20 lakh), so the applicable Visa/Mastercard debit cap is 0.90 percent; the gateway’s contracted rate is 0.85 percent. RuPay debit is zero by mandate.

Baseline monthly debit MDR:

• RuPay bucket: 32% of Rs 15,00,000 = Rs 4,80,000 at 0% = Rs 0
• Visa/Mastercard bucket: 68% of Rs 15,00,000 = Rs 10,20,000 at 0.85% = Rs 8,670
• Total monthly debit MDR: Rs 8,670

The merchant runs the quarterly RuPay-eligible BIN audit and finds that a material share of the Visa/Mastercard volume is on dual-badged BINs that could have settled on RuPay. The merchant raises this with the acquirer in writing, citing the routing-policy request, and works through three months to shift the configuration. The mix moves to 55 percent RuPay, 45 percent Visa or Mastercard. New monthly debit MDR:

• RuPay bucket: 55% of Rs 15,00,000 = Rs 8,25,000 at 0% = Rs 0
• Visa/Mastercard bucket: 45% of Rs 15,00,000 = Rs 6,75,000 at 0.85% = Rs 5,738
• Total monthly debit MDR: Rs 5,738

Monthly saving: Rs 8,670 minus Rs 5,738 = Rs 2,932. Annualised: Rs 35,184. GST at 18 percent rides on the MDR line as a separate reconciliation entry, so the GST cash-outflow drop is symmetric to the MDR drop — a smaller fee base means a smaller GST outflow even where the GST is claimable as input tax credit, because the working-capital drag between outflow and ITC realisation is itself smaller.

None of this requires the customer to do anything differently. The card the customer holds is unchanged; the checkout flow is unchanged; only the network the transaction settles on changes. Scaled linearly: a merchant doing Rs 1.5 crore monthly debit GMV with the same routing shift would recover roughly ten times the figures above, before any additional billing-error recovery on the RuPay bucket itself.

Reconciliation discipline: detect, recover, prevent recurrence

The discipline that converts a one-time routing optimisation into a durable reduction in debit MDR is monthly per-network reconciliation against the settlement file, fed by per-transaction data.

The minimum monthly check is three steps. First, group every debit transaction in the settlement file by card network. Second, compute the per-network effective rate as total MDR divided by network volume. The RuPay effective rate must be zero; the Visa and Mastercard effective rate must be at or below the contracted rate, with the per-transaction caps (Rs 200 small merchant, Rs 1,000 other) respected. Third, raise two exception lists: any non-zero MDR on RuPay debit (a billing error, recoverable from the gateway with the exception list as documented basis), and any per-network effective rate above the contracted rate on Visa or Mastercard debit (also a billing error, also recoverable).

The structural check, run quarterly, is the RuPay-eligible BIN audit described above. The two together — monthly per-network effective-rate audit and quarterly RuPay-eligible BIN audit — close the loop on both leakage modes. The monthly audit catches billing errors; the quarterly audit catches drift in the routing policy and quantifies the next-leg savings opportunity.

This is the same discipline that catches the rest of the merchant-fee leakage stack — Amex and Diners hidden inside a blended rate, commercial cards billed at the consumer slab, domestic BINs billed at international rates, MDR not reversed on refunds. The common methodological thread is per-transaction settlement data sliced by network and instrument, compared to a per-network rate matrix derived from contract and regulation. The reconciliation logic for MDR charged on zero-MDR UPI / RuPay debit is the closest sibling — same legal basis, same detection rule, two different instruments.

How does this interact with the Section 271DB mandatory-acceptance penalty?

Section 271DB of the Income-tax Act, 1961, requires businesses with turnover above Rs 50 crore to mandatorily offer the prescribed e-modes — UPI bank-account P2M and RuPay debit P2M — and imposes a Rs 5,000 per day penalty for non-provision. The interaction with the zero-MDR audit is direct. A large merchant is required by law to accept RuPay debit; the network MDR on those transactions is mandated at zero; and any positive MDR billed on those transactions is a billing error. The same regulatory architecture creates the obligation and zeroes the cost. The reconciliation discipline above is the audit trail that documents both — that the acceptance obligation is being met (RuPay debit volume is present in the settlement file each month) and that the cost obligation is being honoured by the gateway (RuPay debit MDR sums to zero).

What about the platform fee and GST on the same transaction?

A clean RuPay debit MDR audit should show three lines per transaction in the reconciliation, not one. The network MDR line is zero. The gateway platform or technology fee, if contracted, is a non-zero commercial line — typical values are quoted at the gateway level (Razorpay, PayU, Cashfree, PhonePe PG each publish their structure), and the merchant’s contracted rate may differ at enterprise scale. The GST line is 18 percent on the platform fee (since network MDR is zero, GST on MDR is zero too); it is computed on the fee, not on the transaction value, and is claimable as input tax credit against GSTR-3B subject to the usual ITC matching discipline. A merchant who reconciles all three lines separately can recover billing errors at each level without disputing whichever level is correctly charged.

Continue reading in this cluster

• RuPay debit vs Visa/Mastercard debit MDR — the network-split deep-dive with the same regulatory basis and the BIN-tier steering technique
• MDR charged on zero-MDR UPI / RuPay debit — the leakage-pattern sibling for both zero-MDR instruments together
• Section 271DB penalty for non-provision of UPI / RuPay — the acceptance-side regulatory obligation that pairs with the zero-MDR cost mandate
• Cluster hub: Merchant fees and MDR leakage
• Money page: Payment gateway reconciliation

Frequently Asked Questions