UPI Network MDR vs Gateway Platform Fee (Post-15-Oct-2026): The Two Separate Lines + The Open Question on Gateway Fees

Last updated: 17 September 2026 — Companion to Pattern #1 of the eight-pattern merchant-fee leakage taxonomy, restated for the 15 October 2026 UPI MDR regime change. Reflects the Income-tax Act 2025 framework live since 1 April 2026 (Section 393 sub-clauses and payment codes 1001-1092 replacing legacy 194x sections).

Quick Reference

A finance controller looking at a settlement file for a UPI-heavy merchant will see, from October 2026 onward, a line the gateway calls “MDR” or “TDR” or “gateway fee” deducted from the gross UPI credit. In the pre-15-October world, the instinct was to treat that as the cost of UPI — and on a card-grade 2% flat plan it read as 2% of UPI volume per month, with the statutory network-MDR component being zero and the rest being platform fee. In the post-15-October world, the deducted line is a sum of two positive charges above ₹2,000: a legitimate notified network MDR (0.4% flat between ₹2,000 and ₹75,000, capped ₹300 at or above ₹75,000) plus the legitimate platform fee (unchanged, contracted enterprise rate). The two lines still have different defensibility postures, still reconcile to different baselines, and still must be kept separate on the books — the audit discipline has become more important, not less, because both are now non-zero on the same transaction. This article restates the split for the post-15-October regime, walks through a D2C ₹4 crore monthly example, and carries the open question on gateway response as its own tracked section.

What is network MDR on bank-account UPI post-15-October 2026?

Network MDR is the regulated or notified instrument cost paid to the rail — for UPI, the cost the merchant owes by virtue of the payment being made over the UPI network. Historically (1 January 2020 through 14 October 2026), network MDR on bank-account UPI P2M was zero across the full ticket range under Section 10A of the Payment & Settlement Systems Act 2007 read with Section 269SU of the Income-tax Act and Rule 119AA. From 15 October 2026, that framework has changed:

• At or below ₹2,000 (about 95% of P2M count by NPCI’s own figure): network MDR remains zero. Section 10A of the PSS Act as amended by the Taxation and Other Laws (Amendment) Act 2026 (Presidential assent 17 August 2026) preserves the statutory bar in this band.
• Above ₹2,000 and below ₹75,000: the notified rate is 0.4% flat per the NPCI FAQ dated 15 September 2026, hosted on the Department of Financial Services site.
• At or above ₹75,000: the notified charge is capped at ₹300 per transaction — the effective rate declines from 0.4% at ₹75,000 to 0.15% at ₹2,00,000 and further with ticket size.
• Sector overrides: essential-services categories with a stated figure (railways, telecom, insurance, fuel, utility bill collection) pay a flat ₹5 per transaction above ₹2,000 rather than the 0.4% (FAQ Q33, Q39-Q41); education is flat-fee-or-capped per Q42 with no stated figure (Q42; agri-inputs additionally corroborated across press coverage). Capital-markets flows (AMCs, brokers, dealers) pay 0.02%, capped ₹300 (FAQ Q37, Q38).
• UPI AutoPay: explicitly exempt from the notified MDR (FAQ Q22) — automated recurring standing instructions do not carry the prescribed MDR transaction charges regardless of ticket size.

“Bank-account UPI” remains a narrower category than “UPI” as the term is colloquially used. It covers a UPI transaction where the payer’s bank account is debited directly and the merchant’s bank account is credited — no card, no wallet, no PPI, no credit line in the rail. Three other UPI variants exist and they follow their own separate schedules:

• RuPay debit P2M — remains zero MDR full-range under the retained Section 10A protection. Untouched by the 15 October amendment.
• RuPay credit card on UPI — zero interchange at or below ₹2,000 per transaction and approximately 2% above ₹2,000 (NPCI October 2022 circular). Explicitly out of scope of the new MDR per FAQ Q36 — the aggregate 2% continues to apply as before.
• PPI and wallet-on-UPI — interchange of 0.5% to 1.1% above ₹2,000 under the NPCI wallet-interoperability circular dated 24 March 2023. Unaffected by the new MDR.
• Credit-line-on-UPI — separate instrument with its own commercials; explicitly out of scope of the new MDR per FAQ Q36.

These four adjacent rails frequently masquerade as “UPI” on the settlement file — that masquerade is the subject of a separate article in the cluster. The discipline for this article is to restrict the term “UPI” strictly to bank-account UPI P2M, where the network MDR is now band-aware. RuPay debit is included in the split-line reconciliation as its own row (unchanged, still zero).

What is the gateway platform fee, and why is it positive?

The gateway platform fee is the payment aggregator’s contractually agreed charge to the merchant for its services. The aggregator does real work that the merchant could not do alone — routing the transaction through the appropriate switch, running real-time risk and fraud checks, delivering a merchant dashboard, generating reconciliation files, supporting customer refunds and disputes, complying with RBI’s payment-aggregator licensing and reporting requirements. The platform fee is the price of that bundle.

For a small merchant on a headline plan the platform fee is a blended flat percentage — Razorpay and PayU publish 2%, Cashfree publishes 1.95% with a limited 1.6% promotional rate, PhonePe PG publishes 1.95% struck through with a limited “Free” promotional offer. These headline rates are designed for sub-₹5-lakh-monthly volume merchants and are not the right baseline for an enterprise account. A crore-scale UPI-heavy merchant negotiates an enterprise rate that is typically a fraction of the headline percentage on UPI bank-account volume and that may differ materially across cards, UPI, and net banking. The contracted rate per network is the reconciliation baseline; the published rate is a marketing reference.

The gateway is entitled to its contracted platform fee on every UPI bank-account transaction. What it is not entitled to is to call that fee “network MDR” on the settlement file, or to bill it at the card-grade flat percentage when the contract specifies a lower UPI-specific rate, or to apply a positive network-MDR component in addition to the platform fee. Those three are the leakage cells.

Why is conflation the leakage flag?

Three reasons.

First, the law is symmetric on the network-MDR cell. A controller defending a positive network-MDR line on bank-account UPI to an auditor has nothing to point to — Section 10A and Section 269SU are unambiguous and continuous since January 2020. A controller defending a positive platform-fee line on bank-account UPI has the master service agreement, an RBI-licensed payment-aggregator counterparty, and a legitimate service delivered. The two lines have entirely different defensibility postures, and folding them on the books erases the asymmetry.

Second, the right reconciliation baseline differs. Network MDR reconciles against the statutory zero — any positive value is a deterministic flag. Platform fee reconciles against the contracted enterprise rate per network — a per-network audit against the master service agreement. Carrying both as a single percentage line forces a single, blended reconciliation that is wrong on both ends: it concedes a positive network MDR on a zero-MDR instrument, and it benchmarks the platform fee against the wrong reference. Splitting the line restores the right baseline for each.

Third, the GST treatment differs. GST at 18% applies on the gateway’s charge to the merchant — the platform fee. It does not apply on the gross transaction value of the UPI debit. When the file carries the platform fee folded into a line called “MDR”, the GST calculation is forced onto an ambiguous base — usually the same blended line, sometimes (incorrectly) onto the gross transaction value. Splitting the platform fee onto its own line, with 18% GST on the fee as a separate line, restores the right base for the GST calculation and protects the merchant’s input-tax-credit position.

What is the right four-line structure on the books?

For one UPI bank-account transaction of gross value X processed through a payment aggregator at a contracted enterprise platform-fee rate of p percent on UPI bank-account volume, the right line structure on the books is:

The merchant’s net credit is X minus (X × p%) minus the GST on the platform fee. Where the merchant sells through a third-party e-commerce operator that deducts TDS, a fifth line captures the operator-deducted amount under the Income-tax Act 2025 framework — Section 393(1) Sl. 8(v) using payment code 1035 at 0.1% (legacy 194O at the same 0.1% rate effective from 1 October 2024 carries forward; the older 1% rate was pre-October 2024 and should not appear in any current reconciliation). The 5% rate under the PAN/Aadhaar default applies under the legacy 206AA equivalent. The TDS line is reconciled to Form 26AS rather than to the gateway settlement file.

On a direct-checkout UPI sale (the merchant’s own storefront, no marketplace operator), lines 1 to 4 are the full set and the operator-deducted line is absent.

Worked example — D2C brand, ₹4 crore monthly UPI bank-account volume, post-15-October

A direct-to-consumer brand on its own Shopify storefront processes ₹4 crore monthly UPI bank-account volume through Razorpay. Net banking, cards, and wallets are on the same gateway but are not in scope for this example. Ticket-mix representative of a D2C brand with a self-serve subscription and a larger high-ticket bundle:

• At or below ₹2,000: ₹60 lakh (15% of volume, ~85% of transaction count)
• ₹2,000 to ₹75,000: ₹3.20 crore (80% of volume)
• At or above ₹75,000: ₹20 lakh (5% of volume, 25 transactions averaging ₹80,000)

The contracted enterprise plan with Razorpay specifies a 1.5% platform fee on UPI bank-account volume (illustrative — the actual contracted rate varies by merchant; for the worked example we use a rate consistent with published enterprise-tier negotiated baselines). The correct post-15-October split-line settlement file shows:

This is the correct post-15-October structure. Both the notified network MDR (₹1,35,500) and the contractual platform fee (₹6,00,000) are legitimate charges — one is the notified schedule per the 15 September 2026 NPCI FAQ, the other is what the merchant owes per the master service agreement with Razorpay. Neither is leakage.

The leakage version of the same month, on a card-grade 2% flat plan that does not separate UPI bank-account from cards and does not enforce the notified schedule, would read:

The leakage in this version is the difference between what the aggregated 2% deducts (₹8,00,000) and what the correct notified network MDR (₹1,35,500) plus contracted platform fee (₹6,00,000) should sum to (₹7,35,500) — a ₹64,500 pre-GST monthly overrun, ₹76,110 with GST factored, ₹9,13,320 annualised at constant volume. The dispute language must be split-line, not single-line:

1. Network MDR line: the aggregated deducted line is not the correctly-computed notified MDR. Reclassify per the NPCI FAQ dated 15 September 2026: ₹0 on the at-or-below ₹2,000 band, 0.4% on the ₹2,000-₹75,000 band, capped ₹300 per transaction on the at-or-above ₹75,000 band.
2. Platform fee line: the contracted enterprise platform-fee rate on UPI bank-account under the master service agreement is 1.5%, not the card-grade 2% flat. Reclassify at 1.5% x total UPI volume.
3. GST line: 18% on the sum of the corrected network MDR and the corrected platform fee, not on the ambiguous aggregated line.

The gateway re-cuts the settlement at the corrected split lines, refunds the difference for the audit period, and updates the rate card on the account. All three lines are legitimate when correctly categorised; conflating them is what produces the leakage, and the leakage is now larger, not smaller, because the correct structure has more moving parts and there are more ways a single-line billing can go wrong.

What is unresolved: will your gateway platform fee change too?

This is the single most practically urgent open question a merchant using Razorpay, PayU, Cashfree, PhonePe PG, Paytm, BillDesk, Pine Labs, or any other Indian payment aggregator will have after 15 October 2026. It is deliberately called out here because the FAQ dated 15 September 2026 addresses only the network-level MDR — it says nothing about the separate, commercial, gateway-side platform fee that this article’s split-line reconciliation depends on.

What is confirmed as of 17 September 2026:

• The notified network MDR on bank-account UPI above ₹2,000 is 0.4% flat (capped ₹300 above ₹75,000, with sector overrides). This is the operative schedule from 15 October 2026 unless the Supreme Court PIL (filed 16 September 2026) 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 gateway 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.

Update, 27 September 2026 — what the gateways have said so far. Two of the large aggregators have published their position, and neither announces a platform-fee reduction:

• Razorpay (blog post dated 22 September 2026) presents its 2% + GST platform fee as current pricing, with no change stated for 15 October, and says the NPCI MDR will appear as a separate line in settlement files. In other words, the 0.4% is passed through on top of the platform fee, not absorbed into it.
• PayU (blog post dated 21 September 2026) explains the new MDR and advises merchants to ask their gateway how it will be reflected in settlement reports, but does not state any change to PayU’s own platform fee.
• We have not located a published position from Cashfree, PhonePe PG, Paytm, BillDesk, Pine Labs or Mobikwik as of 27 September 2026.

Blog posts are not contract terms. The rate in your own agreement, and any written notice your gateway sends you, is what governs your account. The notified framework, effective 15 October 2026, is currently subject to a pending Supreme Court challenge (PIL filed 16 September 2026). Last verified 27 September 2026.

What is unresolved:

• Whether any major Indian payment aggregator will change its UPI platform-fee schedule in response to the network-MDR change. As of 27 September 2026, the published positions above point to the “no change, MDR passed through as a separate line” scenario for the gateways that have spoken; the rest have not published a position.
• The 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 ₹2,000), some may reduce their UPI-specific platform-fee schedules to keep total merchant cost in a familiar band. The industry has historically absorbed regulatory changes through commercial repricing rather than passing them through cleanly.
  • 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 this article recommends. Merchants should insist on a line-level split on their settlement files, regardless of the gateway’s marketing framing.
• Whether the small-merchant P2PM segment (at or below ₹1 lakh/month inward UPI QR receipts) will see gateway-side platform-fee adjustments to preserve accessibility, given that the notified network MDR is already zero in that segment.

What to do about the unresolved question:

• Add the gateway-response monitor to the finance dashboard. Track each gateway’s public rate-card page and account-management communications for any UPI platform-fee change from 15 October 2026 onward. Log the date and specifics of any change; re-baseline the contracted-rate reconciliation table when a change is confirmed for the merchant’s account.
• Do not renegotiate the contracted rate on speculation. Wait for the gateway’s own announcement before opening a rate-card negotiation on the platform-fee line specifically. Any renegotiation opened now, on speculation, is likely to net worse than a negotiation opened after the gateway’s own position is public.
• Reconcile against the current contracted rate. Until a change is announced and confirmed for the merchant’s account, the contracted platform-fee rate in the master service agreement remains the reconciliation baseline. Do not adjust the reconciliation expected-rate table on speculation.
• Reserve for the worst case. In the finance-plan cost-of-payments model, reserve for a scenario where the gateway does not adjust its platform-fee schedule and the total UPI merchant cost above ₹2,000 rises by the full 0.4% (plus 18% GST on the incremental MDR). This is the current default; a downward adjustment would be an upside to the plan.

This section will be updated as gateway responses are published. Merchants running settlement volumes at multi-crore monthly scale should treat the gateway-response question as a specific line item in the FY27 payments-cost plan, not as a general “market will figure it out” background item.

Detection discipline — separate the two lines on every settlement

The detection methodology has four steps and runs once per settlement cycle.

Step 1 — Reclassify the deducted line. On the settlement file, identify the column the gateway uses for the deducted percentage — often labelled “MDR”, “TDR”, “Convenience fee”, or “Gateway fee”. For UPI bank-account rows, this line is the platform fee, not the network MDR. Re-label the column in the merchant’s working file to “platform fee” so the downstream reconciliation does not inherit the historical convention.

Step 2 — Capture network MDR as an explicit zero line. Add a column for network MDR with the value zero on all UPI bank-account rows. This is not cosmetic — it documents the statutory position in the audit trail and creates the deterministic flag (any positive value here is Pattern #1, a hard dispute item).

Step 3 — Compute effective platform-fee rate per network. Sum the platform fee across UPI bank-account rows and divide by the UPI bank-account volume. The result is the effective platform-fee rate on UPI for the cycle. Compare it to the contracted enterprise rate per the master service agreement. The gap times the volume is the leakage for the cycle.

Step 4 — Reconcile GST on its own line. Sum the GST line across UPI bank-account rows and confirm it equals 18% of the platform fee (not 18% of the gross UPI volume). Any deviation is a GST-base error layered on top of the platform-fee question and must be corrected before the input-tax-credit claim is filed.

For a merchant with a multi-gateway footprint, the same four-step discipline applies per gateway and the per-network effective rates are compared across gateways. A consistently lower effective platform-fee rate on UPI bank-account at gateway A versus gateway B for the same merchant size and method mix is a signal to renegotiate gateway B at the next contract cycle. The audit itself is the renegotiation evidence pack.

Recovery playbook when the lines have been conflated

Where the audit reveals that the deducted line has been carried as a single percentage against UPI bank-account volume at a card-grade flat rate, the recovery playbook has three steps.

Step A — Open the dispute as a reclassification, not a refund. The framing is critical. The merchant is not arguing that the gateway’s charge should be zero; the merchant is arguing that the charge is a platform fee, not network MDR, and that the platform fee should be billed at the contracted enterprise rate per the master service agreement rather than at the card-grade flat. This framing prevents the gateway from booking a “goodwill credit” line that leaves the underlying misclassification in place.

Step B — Present the transaction-level exception list. A summary at the network level invites negotiation. A per-transaction list with the UPI reference, the gross value, the deducted line, the contracted rate, and the corrected platform fee leaves no negotiation room — the file is the claim. Pair this with the regulatory citations (Section 10A of the Payment & Settlement Systems Act, Section 269SU of the Income-tax Act, and the NPCI public position on zero-MDR for UPI bank-account) so the account manager can route the dispute internally without re-arguing the law.

Step C — Update the rate card on the account. The dispute settlement covers the audit period. The forward-looking remediation is the corrected rate card on the account — UPI bank-account billed at the contracted enterprise platform-fee rate (typed as a platform fee, not as MDR), with the network-MDR column explicitly at zero. Confirm in writing (an account-management email is sufficient) that the corrected card is live on the account from a specified settlement period, and re-run the per-network effective-rate audit on the first settlement after the corrected card to verify.

The discipline thereafter is monthly. The per-network audit takes one analyst-day per month once the data pipeline is in place, and the recovery on a UPI-heavy merchant in the first cycle of audit usually pays for the discipline several times over. For a deeper walk-through of the same Pattern #1 case with a SaaS persona and the gateway-dispute pack template, see the cluster sibling MDR charged on zero-MDR UPI / RuPay debit. For the Razorpay-specific settlement file layout and the platform-fee column conventions across instruments, see Razorpay MDR reconciliation. For the statutory anchor itself, see the UPI zero-MDR regime under Section 269SU and the PSS Act.

What does “good” look like after remediation?

A controller running the four-line decomposition one settlement period after remediation should see:

• A column called “Network MDR” carrying zero on every UPI bank-account row, explicitly captured.
• A column called “Platform fee” carrying the contracted enterprise rate per network — UPI bank-account at the negotiated UPI-specific rate, cards at the negotiated card rate, with Amex/Diners and international cards in their own separately priced cells rather than in the standard cell.
• A column called “GST” carrying 18% of the platform fee, not 18% of the gross transaction value, and tying back to the master service agreement schedule.
• Where applicable, a column called “TDS by operator” carrying 0.1% under Section 393(1) Sl. 8(v) code 1035 (Income-tax Act 2025 framework live since 1 April 2026), reconciled to Form 26AS rather than to the gateway settlement file.
• Refund credits on the disputed audit period explicitly tied to UPI bank-account volume reclassified to the contracted rate, not to a goodwill credit line.

The forward-looking baseline is the corrected rate card on the account and the monthly per-network audit. The conflation that produced the leakage is gone because the line structure no longer permits it — network MDR is its own line at zero, platform fee is its own line at the contracted rate, GST is its own line at 18% of the fee, and any future deviation surfaces on the first cycle in which it occurs.

Continue reading in this cluster

• UPI MDR 2026: the definitive current-state flagship — the 0.4% P2M merchant charge effective 15 October 2026, full band schedule, sector overrides, P2PM small-merchant exemption + graduation rule, and the six-check merchant reconciliation playbook. Currently subject to pending Supreme Court challenge (PIL filed 16 September 2026).
• MDR charged on zero-MDR UPI / RuPay debit — Pattern #1 — the cornerstone leakage class
• Razorpay MDR reconciliation — settlement file layout and platform-fee column conventions
• UPI zero-MDR regime under Section 269SU and the PSS Act — the statutory anchor
• Platform fee leakage on Razorpay and PayU — published vs negotiated rate decomposition
• Merchant-fee leakage cluster hub — all eight patterns
• Payment gateway reconciliation — money page