UPI MDR 2026: The 0.4% P2M Merchant Charge Effective 15 October — Full Rate Schedule, Sector Overrides, P2PM Exemption, and Merchant Reconciliation Playbook

Last verified: 17 September 2026 — UPI MDR 2026 flagship for the merchant-fees cluster; every 15-October assertion carries the pending Supreme Court PIL caveat. The Income-tax Act 2025 framework (payment codes 1001-1092 replacing legacy 194x sections) has been in force since 1 April 2026 and is referenced where relevant.

The 30-second answer

UPI MDR 2026 is 0.4% on Person-to-Merchant (P2M) UPI transactions above Rs 2,000, capped at Rs 300 per transaction at or above Rs 75,000, effective 15 October 2026. Transactions at or below Rs 2,000 remain zero-MDR — about 95% of P2M volume by count on NPCI’s own figure. Six essential-service sectors (railways, telecom, insurance, fuel, utility bill collection, education) pay a flat Rs 5 per transaction above Rs 2,000 instead of the 0.4%. Capital-markets flows (AMCs, SEBI-registered brokers, securities dealers) pay 0.02% capped Rs 300. UPI AutoPay and mandates are explicitly exempt (any ticket size). Small merchants receiving at or below Rs 1 lakh per month via UPI QR stay zero-MDR under the P2PM category — with a new 3-consecutive-month graduation rule that formally moves them into the chargeable P2M bucket once inward UPI credits cross Rs 1 lakh/month for three consecutive months. All P2P (person-to-person) transfers are free full-range. Consumer-side scanning is free. UPI apps are barred from charging consumers a platform fee. RuPay debit and RuPay-credit-on-UPI are explicitly out of scope of the new MDR and continue on their own separate schedules. The MDR is paid by the merchant, not the consumer — no surcharge to the customer is permitted. The notified framework is currently subject to a pending Supreme Court challenge (PIL filed 16 September 2026); if the Court stays or strikes it, the pre-15-October zero-MDR schedule remains in force.

Quick Reference

The rest of this article walks the schedule band by band, decomposes the numbers into a worked-example table using the FAQ’s own Q35 illustration, sets out the six-check reconciliation playbook that must run on every UPI-heavy settlement file from October onward, explains what the pending PIL means for a rate-card decision made in the first week of October, and closes with what changes for a UPI-heavy merchant on the operational side.

What changed on 15 October 2026, in one paragraph

Between 4 August 2026 (when the Finance Ministry introduced the Taxation and Other Laws (Amendment) Bill) and 15 September 2026 (when NPCI published the operative Frequently Asked Questions document), the six-year zero-MDR regime for Person-to-Merchant UPI transactions ended by law. Section 10A of the Payment and Settlement Systems Act 2007 — which had prohibited any bank or system provider from levying charges on prescribed electronic modes — was narrowed by the amendment to preserve the zero-MDR bar only on bank-account UPI P2M at or below Rs 2,000 and on RuPay debit across the full range. Above Rs 2,000 on bank-account UPI, a Ministry of Finance notification of 14 September 2026 and NPCI’s Frequently Asked Questions document dated 15 September 2026 (hosted on the Department of Financial Services site at financialservices.gov.in) crystallise the operative rate schedule effective 15 October 2026: 0.4% on transactions above Rs 2,000, capped at Rs 300 per transaction at or above Rs 75,000, with sector overrides and category exemptions detailed in the sections that follow. Every subsequent Q-number citation in this article (Q3, Q17, Q22, Q29, Q33, Q35, Q36, Q37, Q39-Q42) refers to the same NPCI FAQ document; the direct link above is the primary source, the parent DFS page is the durable one. The notified framework is currently subject to a pending Supreme Court challenge (PIL filed 16 September 2026); the “Current status” section below covers what that means for the 15 October date.

Who actually pays, and who does not

The FAQ dedicates an entire section (Q15-Q22) to the question of who bears the charge, and the answer is unambiguous: the merchant pays the MDR, the consumer does not, and the notification introduces no consumer-facing UPI charge. Five specific rules combine to produce that outcome.

Rule 1 — P2P is fully exempt (Q16, Q20). Person-to-person UPI transfers stay free across the full ticket range with no cap. There is no merchant in the loop, and the notification has nothing to say about them. A friend transferring rent to a flatmate on UPI, a parent sending pocket money to a child, a customer refunding a peer — all continue to work exactly as they did before 15 October 2026.

Rule 2 — P2M consumer-side scanning is free (Q19). When a consumer scans a merchant’s UPI QR or enters a merchant VPA, the consumer pays nothing on the UPI leg. The merchant receives the credit net of the notified MDR (and, if applicable, any contracted platform fee — see the network-MDR-vs-platform-fee section below), but the consumer’s outflow is exactly the amount they entered.

Rule 3 — UPI apps are barred from consumer platform fees (Q17). The FAQ explicitly prohibits UPI app providers — the consumer-facing apps that route the payment — from charging consumers any platform fee on UPI transactions. This is a consumer-protection rule distinct from the merchant-side aggregator/gateway platform fee that a merchant contracts separately with its payment aggregator, which is unchanged in kind by the regime change and continues to be paid by the merchant on its own account.

Rule 4 — Merchants cannot pass the MDR as a surcharge (Q34). A merchant is barred from adding an “MDR surcharge” or “UPI fee” line to the invoice to recover the notified MDR from the consumer. The MDR is the merchant’s cost of accepting the payment, not a customer-passable item. Attempting to pass it will read as a UPI-acceptance-mandate violation and put the merchant on the wrong side of the Section 269SU acceptance obligation.

Rule 5 — The MDR itself lands on the merchant (Q3, Q31, Q34 read together). The 0.4% (or the applicable sector override, or the Rs 300 cap) is deducted at the network level and does not reach the consumer’s account. On a Rs 3,000 UPI purchase, the consumer sees a Rs 3,000 debit; the merchant sees a credit of Rs 2,988 net of the Rs 12 MDR before any platform-fee or GST-on-fee lines are applied (which land as further deductions on the merchant’s side, not on the consumer’s).

The practical takeaway for a consumer-facing brand from 15 October onward is that the consumer experience of paying by UPI does not change. The finance-team experience of receiving a UPI credit does change, in the specific ways the next four sections detail.

The full rate schedule: three bands + FAQ Q35 worked-example math

The schedule is three-band on bank-account UPI, with a small number of overrides that displace the standard rate for specific merchant categories or specific instrument types. Here it is against the FAQ’s own Q35 worked-example table, extended with two additional ticket sizes to show the cap behaviour more clearly.

The three bands are:

• Zero band — at or below Rs 2,000. No MDR. About 95% of UPI P2M count sits here per NPCI’s own figure (though a materially smaller share by value, since the higher-ticket bands are a small share of count but a large share of rupees). The Section 10A statutory bar retained in the narrowed amendment applies to this band.
• Notified band — above Rs 2,000 and below Rs 75,000. 0.4% flat on the transaction amount. A Rs 5,000 transaction is Rs 20; a Rs 20,000 transaction is Rs 80; a Rs 60,000 transaction is Rs 240. The rate is a fixed percentage of the transaction value in this band — no cap yet clips in.
• Capped band — at or above Rs 75,000. Flat Rs 300 per transaction. At exactly Rs 75,000, raw 0.4% equals the cap (Rs 300). Above that, the cap holds and the effective rate declines with ticket size: 0.30% at Rs 1,00,000, 0.15% at Rs 2,00,000, 0.06% at Rs 5,00,000, and so on. There is no upper limit on ticket size in the cap band — an invoice paid on UPI at Rs 25,00,000 attracts the same Rs 300 as a Rs 75,000 purchase.

The important calibrator for a merchant’s cost model: the cap makes the arithmetic non-linear at the top end. A merchant modelling annual UPI cost by taking (annual UPI volume x 0.4%) as a shorthand will overstate cost on the large-ticket portion of the mix, sometimes materially. A cost model that captures the actual mix — how much volume sits at or below Rs 2,000 (zero), how much sits between Rs 2,000 and Rs 75,000 (raw 0.4%), how much sits at or above Rs 75,000 (each transaction capped at Rs 300) — is the only way to plan an FY27 payments-cost line with any accuracy. The worked-example section further on in this article walks through a specific merchant profile using this three-band decomposition.

The zero-band bar is statutory (narrowed Section 10A of the PSS Act). The notified-band and capped-band rates are the operative schedule per the NPCI FAQ dated 15 September 2026. The notified framework is subject to a pending Supreme Court challenge (PIL filed 16 September 2026).

Sector overrides: essential services + capital markets + agri-inputs footnote

The 0.4% headline rate does not apply to every merchant category above Rs 2,000. The FAQ names two override tiers, and press coverage of the underlying NPCI circular corroborates a third category (agricultural inputs) as also sitting in the essential-services override, though the FAQ PDF does not itself name it.

Essential-services override — flat Rs 5 per transaction above Rs 2,000 (Q33, Q39-Q42). Six sector families receive this override:

• Railways — booking on IRCTC or partner platforms.
• Telecom — mobile and broadband recharges and postpaid bill payments.
• Insurance — life, health, motor, and general insurance premium payments to IRDAI-regulated insurers.
• Fuel — petrol, diesel, and CNG purchases at pumps and dispensing stations.
• Utility bill collection — electricity, water, and piped gas payments to distribution licensees.
• Education — school and university fee payments to recognised educational institutions.

For merchants in any of these six categories, a Rs 5,000 UPI transaction attracts Rs 5 flat, not the Rs 20 raw 0.4% (Rs 15 saving per transaction); a Rs 50,000 transaction attracts Rs 5 flat, not Rs 200 (Rs 195 saving per transaction). The FAQ’s own phrasing on the list is non-exhaustive (“such as … among others,” Q33) and refers to a “designated Industry program category” that it does not itself fully enumerate. Merchants in adjacent verticals (e.g., healthcare provider payments, certain government-fee collections) should verify their category classification with their payment aggregator and against the underlying NPCI circular before assuming the flat Rs 5 applies.

Capital-markets override — 0.02% capped Rs 300 (Q37, Q38). AMCs and mutual-fund houses, SEBI-registered brokers, and securities dealers sit in a distinct tier. A Rs 50,000 SIP contribution attracts Rs 10 (0.02% x Rs 50,000), not Rs 200 (0.4% x Rs 50,000); a Rs 5,00,000 stock-market settlement attracts Rs 100 (0.02% x Rs 5,00,000), not the Rs 300 standard cap; a Rs 20,00,000 settlement attracts the Rs 300 cap in this tier too, once the raw 0.02% calculation exceeds it. Combined with the UPI AutoPay exemption (see below), a routine SIP contribution running on UPI AutoPay carries no notified MDR at all — exempt on two grounds.

Agricultural-inputs footnote (press-corroborated, one tier below the FAQ-sourced facts). Agricultural inputs — fertilisers, pesticides, seed procurement flows through registered agri-input dealers — are corroborated across press coverage of the underlying NPCI circular (BusinessToday and Onmanorama, 15-16 September 2026) as sitting in the essential-services flat-Rs 5 override. The FAQ PDF itself does not name agri-inputs; the corroboration is via press coverage citing the underlying circular directly. Held to press-corroborated tier — worth verifying with the payment aggregator’s category mapping before assuming.

Materiality. The essential-services carve-out reported at about 17% of P2M UPI transactions by count and about 46% by value (BusinessToday, 15-16 September 2026) — i.e., a large minority of transaction value sits outside the 0.4% headline rate entirely. For a merchant whose category falls into the override, a UPI cost model built off the headline 0.4% would overstate cost by an order of magnitude on the affected volume. For an aggregator or payment-industry analyst modelling market-wide UPI MDR revenue, the same distortion cuts the other way.

Standard categories. Every merchant category not falling into the essential-services or capital-markets overrides pays the standard 0.4% (capped Rs 300 at or above Rs 75,000) schedule from 15 October 2026. E-commerce, food delivery, D2C retail, SaaS, hospitality, professional services, most healthcare cash payments — all standard-tier unless specifically classified into one of the override sectors.

The notified framework is subject to a pending Supreme Court challenge (PIL filed 16 September 2026).

P2PM small-merchant exemption + the new 3-consecutive-month graduation rule

The P2PM (Person-to-Peer-Merchant) category is a distinct classification the FAQ carves out for small merchants whose inward UPI QR receipts stay at or below Rs 1 lakh per month. Merchants in this bucket stay at zero MDR regardless of ticket size and regardless of merchant category (Q23, Q24, Q28). The eligibility test is monthly-collection threshold plus bank-account categorisation only — no GST registration is required to qualify. A small shopkeeper accepting UPI payments on a personal or business current account, with monthly aggregate inward UPI receipts staying at or below Rs 1 lakh, pays zero MDR on every UPI credit whether the ticket is Rs 100 or Rs 5,000 or Rs 20,000.

The new graduation rule (Q29) — this did not exist before 15 September 2026. A merchant is formally moved into the chargeable P2M category once inward UPI credits exceed Rs 1 lakh per month for three consecutive months. This creates a specific, previously-nonexistent compliance-monitoring obligation for merchants near the threshold: track monthly inward UPI receipts on a rolling basis; alert when the rolling window approaches Rs 1 lakh/month; formally re-baseline the rate-card expectation to the chargeable P2M three-band schedule once three consecutive months exceed the threshold; record the graduation date in the audit log.

The obligation runs on aggregate inward UPI QR receipts across all of a merchant’s UPI acceptance instruments — the merchant cannot split a single business across two UPI VPAs to keep each individually under the threshold; the aggregate is measured at the beneficial-owner level.

Worked example — when should the CFO’s dashboard alert. Consider a Tier-3-town retailer whose monthly UPI QR receipts have been running at Rs 65,000-Rs 75,000/month through the first half of the year, growing steadily. In July, receipts hit Rs 90,000 (crossing 90% of the threshold); in August, Rs 1,05,000 (first month above); in September, Rs 1,10,000 (second month above); in October, Rs 1,15,000 (third consecutive month above). The formal move into chargeable P2M is triggered on the October reading. The dashboard alert should ideally fire in July (approaching threshold), give the retailer time to plan for MDR liability, and update the rate-card expectation from October onward. Waiting until the graduation month itself surprises the retailer with a rate-card change that could have been anticipated and communicated three months earlier.

Sub-threshold merchants — what to do operationally. Even for a merchant well below Rs 1 lakh/month with no realistic chance of crossing the threshold in the current year, the operational discipline is worth establishing before it is needed. A simple monthly aggregation of inward UPI credits, plotted against the Rs 1 lakh line, is enough. The dashboard alert can fire at 75% of threshold (Rs 75,000/month) as a soft prompt to review the trajectory, and again at 90% (Rs 90,000/month) as a firm prompt. The point is to make the rate-card change a planned re-baseline, not a settlement-shock discovery.

Aggregator-provided monitoring. Some payment aggregators are expected to build P2PM threshold monitoring into their merchant dashboards as a compliance affordance from 15 October 2026 onward. Where a merchant’s aggregator provides this natively, the merchant should still cross-verify against their own bank statement aggregation — the aggregator sees only the volume that flows through their own switch, not necessarily every UPI credit the merchant receives across all VPAs. The definitive threshold measurement is the merchant’s own aggregate inward UPI receipts, not any single gateway’s slice of them.

Small-merchant support fund. The FAQ (Q8, Q9, Q27) references a dedicated support fund for Tier 3-6 centres and North-East states plus J&K and Ladakh, to be finalised in consultation with RBI within three months of the framework taking effect — i.e., roughly by mid-December 2026. Details of the fund’s operative structure are not in the FAQ document; the fund is a policy commitment rather than a live scheme as of 17 September 2026. Merchants in the covered geographies should watch for RBI and NPCI communications on this front through Q4 2026.

The notified framework is subject to a pending Supreme Court challenge (PIL filed 16 September 2026). If the framework is stayed or struck, the P2PM graduation obligation described here does not enter force and the pre-15-October zero-MDR schedule remains applicable across the full P2M range, obviating the need for the graduation monitor.

The legal chain: how six years of zero MDR ended in six weeks

The transition from the six-year zero-MDR regime to the notified three-band schedule ran through four dated steps in the six weeks between 4 August and 15 September 2026. Each step is verifiable against the primary source named alongside it.

4 August 2026 — the Finance Ministry introduces the Taxation and Other Laws (Amendment) Bill, 2026. The Bill amends Section 10A of the Payment and Settlement Systems Act 2007 — the exact statutory provision that had prohibited banks and system providers from levying charges on the prescribed electronic modes (bank-account UPI P2M and RuPay debit P2M) from 1 January 2020 onward. The Bill narrows the Section 10A protection to transactions at or below Rs 2,000 on bank-account UPI P2M and retains it in full on RuPay debit. Legislative history is tracked at PRS Legislative Research.

17 August 2026 — Presidential assent. The Bill receives Presidential assent, taking effect as the Taxation and Other Laws (Amendment) Act 2026. The statutory amendment is now on the books.

14 September 2026 — Ministry of Finance notification. The Ministry of Finance operationalises the amendment by notification, specifying that the narrowed Section 10A applies from the date fixed by NPCI in its operative circular. The notification does not itself set the rate; it delegates the operative rate-setting to NPCI’s UPI and Services Steering Committee.

15 September 2026 — NPCI publishes the operative FAQ. NPCI’s “UPI and Services Steering Committee” sets the operative 0.4% rate (capped Rs 300 at or above Rs 75,000) with the sector overrides, P2PM exemption, graduation rule, AutoPay exemption, RuPay-credit-on-UPI exclusion, no-surcharge rule, and consumer-side platform-fee bar, via the Frequently Asked Questions document referenced throughout this article and hosted on the Department of Financial Services site at financialservices.gov.in. The document sets 15 October 2026 as the effective date (Q5).

Historical framing. The regime that ended on 14 October 2026 had been continuously in force since 1 January 2020, when Section 10A of the PSS Act (introduced by the Finance (No. 2) Act 2019) combined with Section 269SU of the Income-tax Act (introduced by the same Finance Act 2019) and Rule 119AA of the Income-tax Rules to create the zero-MDR mandate on the prescribed e-modes. Section 269SU’s acceptance mandate — that businesses above Rs 50 crore turnover must offer UPI and RuPay debit as prescribed e-modes — was untouched by the 2026 amendment and continues to bind. Section 271DB’s Rs 5,000/day penalty for non-provision is also unchanged. The full historical/legal-basis reference is at UPI zero-MDR regime under Section 269SU and the PSS Act — that article carries the archival treatment of the regime that ended.

The notified framework, effective 15 October 2026, is currently subject to a pending Supreme Court challenge (PIL filed 16 September 2026).

Network MDR vs payment gateway platform fee

Every UPI-heavy merchant using a payment aggregator (Razorpay, PayU, Cashfree, PhonePe PG, Paytm, BillDesk, Pine Labs, or another RBI-licensed aggregator) needs to hold two distinct cost lines apart from 15 October 2026 onward: the notified network MDR (set by regulation, band-aware, deterministic against the schedule) and the commercial platform fee (set by contract, unchanged in kind by the regime change). The cluster sibling UPI network MDR vs gateway platform fee walks through the split-line reconciliation and a D2C worked example in full detail. This flagship gives the essentials plus the confirmed-vs-unconfirmed sub-block on the gateway response.

Network MDR (post-15-October, notified schedule). The three-band schedule above — zero at or below Rs 2,000; 0.4% flat between Rs 2,000 and Rs 75,000; capped Rs 300 at or above Rs 75,000; with the essential-services and capital-markets overrides where applicable — is the notified merchant-side network cost on bank-account UPI. It is set by the DFS-hosted NPCI FAQ dated 15 September 2026, deducted at the network level, and is not a variable a merchant negotiates.

Payment aggregator platform fee (unchanged in kind). The platform fee is what the payment aggregator charges the merchant separately for its own services — routing the transaction through the appropriate switch, running real-time risk and fraud checks, delivering the merchant dashboard, generating reconciliation files, supporting customer refunds and disputes, complying with RBI’s payment-aggregator licensing and reporting requirements. It is a real service; a positive charge is legitimate; it is set by the master service agreement between the merchant and the aggregator; and it is unchanged in kind by the 15 October regime change. For a crore-scale UPI-heavy enterprise account, the contracted platform fee on UPI is typically a fraction of the card-grade percentage and is negotiated on the enterprise-tier account, not billed at the headline 1.95%-to-2% marketing rate designed for sub-Rs 5-lakh-monthly-volume small merchants.

Both lines are now positive on the same UPI transaction above Rs 2,000. Pre-15-October, the network MDR line was uniformly zero and the audit question was “is the deducted line a legitimate platform fee at the contracted rate?” Post-15-October, both lines are legitimate and both must be verified separately: the network MDR against the notified schedule (band-by-band), the platform fee against the contracted enterprise rate (per-network, per-master-service-agreement). Both attract 18% GST on the fee only, claimable as input tax credit.

Confirmed vs unconfirmed on the gateway response (as of 17 September 2026)

Confirmed:

• The notified network MDR on bank-account UPI above Rs 2,000 is 0.4% flat (capped Rs 300 above Rs 75,000, with sector overrides). This is the operative schedule from 15 October 2026 unless the Supreme Court PIL stays or modifies it.
• The gateway platform fee is a separate, commercial line set by the merchant’s contract with the aggregator, not by the notification. The notification does not change what any aggregator is entitled to charge as its own commercial fee.
• The gateway is entitled to bill both lines on the same settlement file (the notified network MDR at the correct band rate + the contracted platform fee), and the sum-of-fees-with-18%-GST is the merchant’s total deduction.

Unconfirmed:

• Whether any major Indian payment aggregator will announce a change to its UPI platform-fee schedule in response to the network-MDR change. No public announcement has been made as of 17 September 2026 by Razorpay, PayU, Cashfree, PhonePe PG, Paytm, BillDesk, Pine Labs, Mobikwik, or any other RBI-licensed aggregator that this article has located.
• Three plausible directions such a response could take (each is a hypothesis, not a prediction — do not represent any of these as expected):
  • No change. The platform fee is a commercial arrangement independent of the network MDR; the aggregator continues to bill the contracted rate. This is the simplest and, absent evidence to the contrary, the default assumption a controller should plan against.
  • Platform-fee reduction. If aggregators anticipate merchant pushback on total cost (network MDR + platform fee both being positive above Rs 2,000), some may reduce their UPI-specific platform-fee schedules to keep total merchant cost in a familiar band.
  • Platform-fee restructuring. Some aggregators may bundle the network MDR into their platform-fee line as a single “consolidated UPI fee” — technically a labelling change, but one that muddies the split-line reconciliation. Merchants should insist on a line-level split on their settlement files regardless of the aggregator’s marketing framing.

The gateway-response question is a specific line item in the FY27 payments-cost plan, not a general “market will figure it out” background item. Add a gateway-response monitor to the finance dashboard and re-baseline the contracted-rate reconciliation table when a change is confirmed for the merchant’s account. For the deeper walk-through of the split-line reconciliation and a D2C Rs 4 crore monthly worked example, see the cluster sibling UPI network MDR vs gateway platform fee.

What does the pending Supreme Court PIL mean for your rate-card work?

Last verified: 17 September 2026. A Supreme Court PIL was filed on 16 September 2026 by advocate Anjan Datta challenging the 14 September Ministry of Finance notification and the 15 September NPCI circular that together produce the notified framework taking effect on 15 October 2026. The petition alleges the levy was introduced without adequate statutory safeguards, transparency, or public consultation, and seeks quashing or suspension of the framework before 15 October. Outcome is unknown as of the last-verified date on this section. This is a live procedural challenge to a live notification and it may or may not succeed; the Court has not yet ruled on interim relief.

What the PIL does not do. It does not, by its filing alone, stay the 15 October effective date. The notification remains operative unless and until the Court grants a stay or strikes the framework. Aggregators, banks, and NPCI’s own switches will process transactions on 15 October under the notified schedule unless a Court order intervenes before then.

What the PIL could do. Three broad outcomes are possible: (a) the Court dismisses the petition or declines to grant interim relief and the framework takes effect and stays in force as notified; (b) the Court stays the notification pending fuller hearing, in which case the effective date is pushed out and the pre-15-October zero-MDR schedule stays in force during the stay period; (c) the Court quashes or modifies the notification on procedural or substantive grounds, in which case the notified framework is either replaced by a different framework or reverts to the pre-15-October zero-MDR baseline. Each outcome has distinct implications for FY27 payments-cost planning.

Graceful-degradation language for FY27 rate-card work. The safest posture for a finance-team rate-card decision made in the first week of October is to plan for outcome (a) as the base case — the notified schedule takes effect on 15 October — while carrying a documented degradation clause for outcomes (b) and (c). Practically: build the FY27 UPI cost model on the notified three-band schedule; keep the pre-15-October zero-MDR model in the working file as the reversion baseline; flag any aggregator or banking-partner communications on Court-ordered changes as they land; be prepared to re-baseline the rate-card expectation within a settlement cycle if the framework is stayed or struck. If the Court stays or strikes the framework, revert to the pre-15-October zero-MDR schedule. This graceful-degradation clause should sit in the FY27 payments-cost plan as a specific line item, not as an assumed background.

Communications discipline. For a merchant that has already begun customer or partner communications about the 15 October change, keep the messaging conditional — “the notified MDR takes effect on 15 October 2026 unless the pending Supreme Court challenge produces a different outcome” — rather than declaratory. A definitive “here is what UPI will cost you from 15 October” reads as reliable only until the Court rules; a conditional framing survives both a ruling in favour and a ruling against the notification.

This section will be updated when the Court rules on interim relief or on the substantive petition. The “last verified” date at the top of this section is the definitive signal of how current the treatment is — if the Court has ruled after the date shown and this section has not been updated, treat the section as informational rather than operative and verify against the current Court and NPCI positions directly.

Merchant reconciliation playbook: six checks that must run on every UPI-heavy settlement file from October onward

The pre-15-October MDR reconciliation workflow ran a set of standard checks against a uniform zero-MDR expectation on bank-account UPI. Post-15-October, the check surface expands to six specific checks that must run on every UPI-heavy settlement file. The cluster sibling MDR fee reconciliation treats the full six-check operational hub; here is the flagship-level summary that a controller can act on directly.

Check 1 — Zero-band verification (at or below Rs 2,000 on bank-account UPI + all RuPay debit + all RuPay-credit-on-UPI). Expected network MDR is zero. Any positive deduction on any of these three cells is a hard exception, recoverable in full against the aggregator. This is the classical Pattern #1 leakage check restricted post-15-October to the bands where it remains illegitimate. On bank-account UPI at or below Rs 2,000, the narrowed Section 10A of the PSS Act still applies. On RuPay debit, the full Section 10A protection is retained. On RuPay-credit-on-UPI, FAQ Q36 explicitly excludes the instrument from the new MDR and it follows its own separate schedule.

Check 2 — Notified-band verification (above Rs 2,000 and below Rs 75,000 on bank-account UPI). Expected: 0.4% flat x transaction value for standard merchant categories; flat Rs 5 per transaction for essential-services categories; 0.02% x transaction value for capital-markets categories. Any material variance is a 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 3 — Cap-band verification (at or above Rs 75,000 on bank-account UPI). Expected: at most Rs 300 per transaction (regardless of raw 0.4% calculation, which would exceed Rs 300 above the Rs 75,000 threshold). Any deduction above Rs 300 on a single transaction is a cap-breach exception, recoverable per transaction. For a Rs 2,00,000 transaction, a raw 0.4% would be Rs 800; the cap enforces Rs 300; the Rs 500 gap is the per-transaction recoverable. Combined with Check 2, this covers the notified-schedule verification on the full bank-account UPI ticket range.

Check 4 — Sector-override verification. For merchants classified in essential-services categories, the expected rate is flat Rs 5 per transaction above Rs 2,000, not 0.4%. For merchants classified in capital-markets categories, the expected rate is 0.02% capped Rs 300. Any settlement file that bills the standard 0.4% on essential-services or capital-markets volume above Rs 2,000 is a category-classification error, resolvable at the aggregator’s merchant-category-code table. Merchants should verify their MCC classification against the aggregator’s category list before disputing a specific deduction.

Check 5 — P2PM graduation monitor. For merchants whose inward UPI QR receipts are at or below Rs 1 lakh per month (the P2PM small-merchant category), the network MDR is zero regardless of ticket size. Run a rolling monitor on aggregate inward UPI QR receipts: track monthly against the Rs 1 lakh threshold, alert at 75% and 90%, formally re-baseline the rate-card expectation from the P2PM zero schedule to the P2M three-band schedule when three consecutive months exceed Rs 1 lakh (per FAQ Q29). Record the graduation date in the audit log. This check did not exist before 15 September 2026.

Check 6 — Split-line integrity (network MDR vs platform fee). On every settlement cycle, verify that the settlement file carries the network MDR and the platform fee as separate line items, not aggregated into a single “MDR” or “gateway fee” column. Reconcile the network MDR against the notified schedule and the platform fee against the contracted enterprise rate per the master service agreement. GST at 18% attaches to the sum of the two fee lines, not to gross transaction value. Any aggregation of the two into a single line is a split-line integrity exception that must be raised with the aggregator’s account-management team before the underlying deductions can be verified.

For a merchant that wants to walk through the arithmetic on their own file before opening the aggregator conversation, two tools published on the site handle the core computations:

• MDR effective-rate calculator — paste monthly UPI, RuPay debit, card, and other-instrument volumes at their headline billed rate and the contracted enterprise rate. The tool decomposes cost per network and quantifies leakage against the contracted rate. No upload, no signup.
• MDR leakage flag checker — paste a single settlement file’s totals and the tool surfaces which reconciliation exceptions raise for that cycle. Useful as a first-cut audit before a full check pass.

Both tools run entirely client-side and are calibrated against the post-15-October notified schedule. On bank-account UPI, the tools apply an approximate blended expected rate (~0.30%) weighted for a typical mix in which about three-quarters of monthly UPI-bank value sits in the Rs 2,000-Rs 75,000 band at 0.4% — the aggregate-volume input surface these tools present cannot band-split by ticket size, so their bank-account UPI output is a directional triage, not a per-band precision audit. For per-band precision, verify UPI network-MDR math manually against the notified schedule in Checks 1, 2, and 3 of the reconciliation playbook above. On RuPay debit, RuPay-credit-on-UPI, and PPI-on-UPI, the tools apply the notified rates directly; the sector overrides (essential-services flat Rs 5, capital-markets 0.02%), the UPI AutoPay exemption, and the P2PM small-merchant exemption are documented in the tools’ reference notes but must be applied manually — a merchant in an override category should adjust the expected rate accordingly. The tools’ outputs are illustrative and should be verified against the underlying settlement file’s transaction-level detail before a formal dispute is opened with the aggregator. The notified framework remains subject to the pending Supreme Court challenge (PIL filed 16 September 2026); a stay or strike reverts the reconciliation expectation to the pre-15-October zero-MDR baseline across the full bank-account UPI ticket range.

The notified framework is subject to a pending Supreme Court challenge (PIL filed 16 September 2026); the reconciliation checks in this section assume the notified schedule remains in force. If the framework is stayed or struck, Checks 2, 3, 4, and 5 revert to the pre-15-October zero-MDR expectation across the full bank-account UPI ticket range.

What does TransactIG change for a UPI-heavy merchant handling the transition?

For a finance controller running the six-check playbook above on every settlement cycle from 15 October onward, the operational burden depends on how band-aware the reconciliation pipeline is. A spreadsheet-based process that ran adequately against a uniform zero-MDR expectation before 15 October now needs to hold six band-and-category-aware exception classes, run a rolling P2PM graduation monitor, and cross-verify a split-line integrity check on every cycle. At single-gateway sub-Rs 50-lakh monthly UPI volume, the spreadsheet can be extended to cover the new checks. Above that, and certainly across a multi-gateway multi-crore-monthly UPI footprint, a purpose-built reconciliation platform is the difference between catching exceptions in the same cycle they occur and letting them annualise silently.

TransactIG is Terra Insight’s payment gateway reconciliation platform, designed for exactly this shape of Indian merchant-side settlement work. The GA capabilities that map to the UPI MDR 2026 transition are:

• Multi-pass matching engine with tolerance bands. Reconciles settlement-file lines against expected schedules across instruments (bank-account UPI, RuPay debit, RuPay-credit-on-UPI, PPI-on-UPI, cards, net banking), configurable for the post-15-October three-band UPI MDR structure and the essential-services and capital-markets overrides. On live customer data across TDS, GST, settlement, and batch reconciliation domains, the engine has taken automated match rates from 51% (spreadsheet or legacy tooling baseline) to 88% — the improvement is what the exception-review team spends its time on instead of the base match work.
• Variance taxonomy with provenance. Every difference between the deducted line and the expected schedule is classified into a named variance class — zero-band violation, mid-band variance, cap-breach, sector-override mismatch, split-line integrity break, P2PM graduation-trigger event — never left as “miscellaneous.” The taxonomy is the subject of a patent filing at the Indian patent office. In practice, the taxonomy is what makes the dispute pack against an aggregator specific to a named exception rather than a general “your MDR looks high” negotiation.
• Twenty-four-plus industry presets. The rate-card engine covers the merchant categories most affected by the 15 October change — retail/D2C, e-commerce, SaaS, hospitality, healthcare cash payments, professional services — through its 24+ industry presets. The post-15-October three-band schedule, the six essential-services categories that get the flat Rs 5 override, and the capital-markets AMC/broker/dealer tier at 0.02% capped Rs 300 are configuration entries — added in config, not code — with tolerances and slab boundaries edited the same way any rate-card change lands. A new preset for a merchant category the shipped set does not cover is a config-only addition.
• Two-to-four-week configuration deployment. A merchant onboarding for the first time — with settlement-file feeds from one or more of Razorpay, PayU, Cashfree, PhonePe PG, Paytm, BillDesk, Pine Labs, or another RBI-licensed aggregator, plus the merchant’s own bank statement and books — is typically live on the reconciliation surface in two to four weeks of config work, without customer engineering time. The 15 October deadline is inside that window for a merchant that starts now.
• Deployment options. SaaS on Terra Insight’s AWS Mumbai infrastructure, or a dedicated private-cloud VPC — both fully Terra Insight-managed with India data residency. ISO 27001:2022 certified; DPDP Act 2023 aligned; RBI IT-governance aligned. Customers do not run the software on their own infrastructure.
• Security posture and compliance. ISO 27001:2022 certification, AWS Mumbai residency, DPDP Act 2023 alignment, and RBI IT-governance alignment — the standard trust posture Indian enterprise finance and internal-audit teams require before onboarding a reconciliation platform on production settlement data.

For a UPI-heavy merchant with a multi-gateway footprint approaching the 15 October transition, the practical starting point is a diagnostic pass on the most recent monthly settlement file across one or two aggregators to identify which of the six checks would raise exceptions if the notified schedule had already been in force. The diagnostic itself typically surfaces the highest-recovery exception classes for the specific merchant and is the input to the configuration decision for the ongoing reconciliation surface. Terra Insight is also the publisher of the broader reconciliation software India capability set that TransactIG sits inside; for merchants whose reconciliation surface extends beyond payment-gateway settlements into TDS, GSTR-1/3B outward filings, and NACH domains, the same platform handles the full surface with domain-specific presets. GST inward reconciliation (GSTR-2A/2B, ITC, IMS) and intercompany reconciliation are on the roadmap.

The notified framework is subject to a pending Supreme Court challenge (PIL filed 16 September 2026). If the framework is stayed or struck, the reconciliation configuration reverts to the pre-15-October zero-MDR expectation across the full bank-account UPI ticket range — a rate-card change managed as a configuration update rather than a re-platforming effort.

Continue reading in this cluster

• UPI zero-MDR regime under Section 269SU and the PSS Act — the historical and legal-basis reference for the regime that ran from 1 January 2020 through 14 October 2026
• MDR charged on zero-MDR UPI / RuPay debit — split-band reconciliation playbook — Pattern #1 restated for the 2026 regime change, with band-aware detection logic and the residual-leakage playbook
• UPI bank-account MDR by ticket size — three-band schedule — the ticket-size decomposition with worked-example math on each band
• UPI network MDR vs gateway platform fee — split-line reconciliation — the split-line reconciliation with a D2C Rs 4 crore monthly worked example and the open gateway-response question
• MDR fee reconciliation — six-check operational hub — the full six-check operational hub with the P2PM graduation-monitor logic
• Merchant-fee leakage cluster hub — all eight patterns and cluster navigation
• Payment gateway reconciliation — money page