Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
A single flat headline MDR percentage on a payment-gateway plan conceals an order-of-magnitude variance across instruments and networks — bank-account UPI is zero, RuPay debit is zero, non-RuPay debit is capped under 1%, credit cards run 1.4% to 2.5%, and Amex/Diners sit at 2.95% to 3.5%. For a UPI-heavy OTT or subscription merchant the flat rate is a multiple of the method-mix-weighted true cost; the apparent over-recovery is a mix of platform-fee renegotiation opportunity and Pattern #1 network-MDR leakage on zero-MDR cells.
Build a method-mix-weighted expected-cost model from the gateway's settlement file: split volume by instrument and network, multiply each cell's share of total volume by its contracted or regulated rate, sum to a weighted expected percentage, and compare to the flat rate actually billed. The gap times monthly volume is the apparent over-recovery. Parse the gap between the platform-fee portion (renegotiable to a sub-cell rate card) and the network-MDR portion that is legally zero on UPI bank-account and RuPay debit.
Per-gateway, per-network MDR rule set with the regulated zero-MDR cells (bank-account UPI, RuPay debit) hard-coded; method-mix decomposition by instrument and network with RuPay-credit-on-UPI and PPI-on-UPI separated from bank-account UPI; contracted-rate table per network separate from published-rate baseline; flat-rate-vs-weighted comparator that flags any gap above 0.15 percentage points; GST line isolator at 18% on the fee only.
A method-mix-weighted expected-cost report (per-network shares, per-cell rates, weighted expected percentage) reconciled to the flat rate billed, with the apparent over-recovery quantified in rupees and parsed between renegotiation opportunity and Pattern #1 leakage. The output is the dispute pack and the rate-card renegotiation brief the CFO or controller takes to the gateway's relationship leadership.
Last updated: 23 June 2026 — Pattern #6 of the eight-pattern merchant-fee leakage taxonomy. Reflects the Income-tax Act 2025 framework live since 1 April 2026 (Section 393 sub-clauses and payment codes 1001-1092 replacing the legacy 194x sections). All references to network MDR caps and zero-MDR mandates current as of this date.
Quick Reference
| Aspect | Detail |
|---|---|
| Pattern position | #6 of 8 in the merchant-fee leakage taxonomy |
| Flat-rate billing | Single headline percentage (commonly 1.95% to 2%) applied across every instrument and network |
| Network MDR on bank-account UPI | 0% (mandate since 1 January 2020) |
| Network MDR on RuPay debit | 0% (mandate since 1 January 2020) |
| Network MDR on Visa/Mastercard debit | RBI 2017 cap: 0.40% small merchant / 0.90% large merchant |
| Network MDR on Visa/Mastercard credit | 1.4% to 2.5% negotiated (no regulatory cap) |
| Network MDR on Amex/Diners | 2.95% to 3.5% (premium slab across gateways) |
| Detection mechanic | Method-mix-weighted expected-cost model vs flat rate billed |
| Typical leakage in UPI-heavy OTT mix | Effective rate 3x to 4x the method-mix-weighted expected cost |
| Legal basis (zero-MDR cells) | Payment & Settlement Systems Act Section 10A; Income-tax Act Section 269SU read with Rule 119AA |
A CFO at an OTT subscription business reviewing a monthly settlement on a flat 2% gateway plan reads the line item as a single number and treats it as a single cost. The reality on the settlement file is that the same line is being computed against a method mix where two-thirds of the volume carries zero network MDR by statute, a small slice carries the RBI-capped non-RuPay debit rate, and a single-digit-percentage slice is Amex or Diners at 3%. The headline 2% is the structural average of a flat-rate architecture; the method-mix-weighted true cost is much lower. Pattern #6 of the eight-pattern merchant-fee leakage taxonomy is the architectural one — not a billing error, not a contract breach, but the wrong pricing shape for a method mix that has shifted decisively toward UPI since 2020 and especially since 2023.
What does flat-rate MDR actually mean?
Flat-rate MDR is the simplest payment-gateway commercial structure: every successful transaction is charged the same percentage regardless of instrument, network, ticket size, or whether the underlying network MDR is regulated, capped, or zero. Razorpay’s published Standard Plan is 2% domestic blended; PayU’s published rate is 2% domestic blended; Cashfree publishes 1.95% standard (with a limited-time 1.6% promo for new merchants signing up between September 2025 and April 2026, conditional on UPI being at least 40% of monthly GTV); PhonePe Payment Gateway publishes 1.95% Standard Plan headline currently struck-through with a limited-time launch offer. These published cards are designed as a single number a small merchant can quote in five seconds.
Behind the single number there are at least seven distinct cost cells with materially different economics. Bank-account UPI carries zero network MDR by Section 10A of the Payment & Settlement Systems Act read with Section 269SU of the Income-tax Act and Rule 119AA — the regime is operative since 1 January 2020 and Budget 2026-27 has continued to fund the incentive scheme. RuPay debit carries zero network MDR by the same mandate. Non-RuPay debit (Visa and Mastercard) is capped at 0.40% for small merchants (annual turnover up to Rs 20 lakh) and 0.90% for larger merchants under the RBI 2017 circular, with a per-transaction cap of Rs 200 and Rs 1,000 respectively. Visa and Mastercard credit are uncapped and negotiated, commonly 1.4% to 2.5% for crore-scale merchants. Amex and Diners are billed at the premium 2.95% to 3.5% slab across every major gateway. Commercial and corporate cards are routed to the same 3% premium slab. RuPay credit card on UPI is approximately 2% above Rs 2,000 per transaction with zero interchange at or below. PPI and wallet-on-UPI sit at 0.5% to 1.1% above Rs 2,000.
The flat-rate architecture treats all of this variance as one number. The method-mix-weighted reconciliation is the discipline of treating each cell separately.
How does this leakage hide on a settlement file?
The settlement file looks innocuous. Every transaction has the same MDR percentage line. The line totals reconcile to the monthly invoice. The GST at 18% on the fee is calculated correctly. There is no missing transaction and no mathematical error.
What the settlement file does not show is the counter-factual. If the same volume mix had been priced at each instrument’s contracted or regulated rate — bank-account UPI at the contracted UPI-specific platform fee (which is typically far below the card-grade rate), RuPay debit at zero, non-RuPay debit at the RBI-capped rate, Visa/Mastercard credit at the contracted enterprise rate, Amex/Diners separately at the premium slab — the total fee would be materially smaller. The leakage is the gap between the flat-rate billed and the weighted expected cost; it does not appear as an error on any line because the flat-rate architecture by design averages across cells.
The method-mix-weighted reconciliation surfaces the gap by reconstructing the counter-factual. It does not impugn the gateway’s billing accuracy; it impugns the gateway’s pricing shape against the merchant’s actual method mix. The remediation is not a refund dispute (the gateway has billed exactly what the flat rate says it should bill); it is a contract renegotiation to a per-network rate card or an interchange-plus structure, with one carve-out — the bank-account UPI and RuPay debit cells where the network MDR is zero by statute and any positive line under an “MDR” column on those cells is also a Pattern #1 dispute the merchant can recover on past periods.
Worked example: OTT video subscription, Rs 15 crore monthly GMV
An OTT video subscription business processing Rs 15 crore in monthly GMV is on a payment gateway’s Standard Plan at a flat 2% rate. The settlement file is clean — every transaction is billed at 2%, the line totals reconcile to a monthly fee of Rs 30 lakh, GST at 18% on the fee is Rs 5.4 lakh as a separate line.
The CFO runs a method-mix-weighted reconciliation. The mix from the settlement file is as follows:
- 68% on bank-account UPI (P2M, customer’s bank account to merchant’s bank account)
- 7% on RuPay credit card on UPI
- 5% on PPI / wallet on UPI
- 12% on Visa/Mastercard credit (consumer cards, domestic)
- 5% on Visa/Mastercard debit (non-RuPay, domestic)
- 3% on Amex and Diners (combined, domestic)
The per-cell contracted or regulated rate used for the expected-cost model is:
- Bank-account UPI: 0% (network MDR is zero by statute; platform fee modelled at 0% for the regulated-cell baseline)
- RuPay credit on UPI: 2% (NPCI rate above Rs 2,000 per transaction)
- PPI/wallet on UPI: 1.1% (NPCI interchange above Rs 2,000)
- Visa/Mastercard credit: 1.9% (contracted enterprise rate proxy)
- Visa/Mastercard debit: 0.4% (RBI cap for relevant tier)
- Amex/Diners: 3% (premium slab)
The method-mix-weighted expected cost is:
0% x 68% + 2% x 7% + 1.1% x 5% + 1.9% x 12% + 0.4% x 5% + 3% x 3% = 0 + 0.14 + 0.055 + 0.228 + 0.020 + 0.090 = 0.533%
The flat 2% billed on Rs 15 crore is Rs 30,00,000 per month. The method-mix-weighted expected cost at 0.533% on the same volume is Rs 7,99,500 — round to Rs 8 lakh per month. The apparent over-recovery is Rs 22,00,500 per month, round to Rs 22 lakh per month, or roughly Rs 2.64 crore annualised.
An important parse: the apparent over-recovery is not pure leakage and is not pure renegotiation opportunity — it is a mix of both, and the reconciliation must separate the two. The Rs 22 lakh per month decomposes into (a) the gateway platform fee on bank-account UPI, RuPay credit on UPI, PPI on UPI, debit, and credit cards, which the merchant legitimately owes for routing, dashboard, settlement, and risk services, and (b) the network MDR component, which is zero on the bank-account UPI and RuPay debit cells by statute and is capped/negotiated on the rest. The portion that maps to bank-account UPI volume billed under a line called “MDR” is Pattern #1 leakage (Rs 10.2 crore monthly bank-account UPI volume times the implicit MDR component of the flat 2% line is the upper bound of the recoverable Pattern #1 leakage on past periods). The remainder is a renegotiation opportunity — the contract architecture is wrong for the method mix and a per-network rate card resolves it forward-looking. Audit details and the per-transaction parse between the two are what the dispute pack must carry to the gateway relationship leadership.
Build your own method-mix-weighted expected-cost model
Paste your monthly bank-account UPI, RuPay-credit-on-UPI, PPI-on-UPI, debit, credit, and Amex/Diners volumes with the flat rate you are billed, and the MDR Effective-Rate Calculator builds the weighted expected cost per network, compares it to the flat rate, and quantifies the apparent over-recovery. No upload, no signup.
Open the MDR Effective-Rate Calculator →Reconciliation discipline: the method-mix-weighted expected-cost model
The reconciliation discipline runs in six steps. It is independent of gateway and independent of business model; the inputs differ but the mechanic is identical.
Step 1 — Decompose volume by instrument and network. Take the settlement file for one calendar month. Split every transaction into instrument (UPI, card, net banking, wallet, EMI) and network (bank-account UPI, RuPay credit on UPI, PPI on UPI, RuPay debit, Visa/Mastercard debit, Visa/Mastercard credit consumer, Visa/Mastercard credit commercial, Amex, Diners, international card). UPI must be decomposed into the three UPI sub-networks using the RRN, UMN, and instrument metadata on the settlement file — a UPI line that is not sub-classified is the most common upstream defect and will distort the rest of the model.
Step 2 — Compute each cell’s share of total volume. Express each cell as a percentage of total successful-transaction volume. The sum across cells equals 100%. For an OTT subscription business this is overwhelmingly UPI-family rails; for a high-ticket D2C it skews toward cards; for an international travel OTA it skews toward cross-border Visa/Mastercard and Amex. The method mix is the merchant’s signature.
Step 3 — Apply contracted or regulated rate per cell. For each cell apply the rate that should be the reconciliation baseline. For bank-account UPI and RuPay debit the rate is zero (network MDR mandate). For non-RuPay debit the rate is the RBI 2017 cap (0.40% small / 0.90% large; 0.30% / 0.80% QR; per-transaction caps Rs 200 / Rs 1,000). For Visa/Mastercard credit the rate is the contracted enterprise rate from the merchant’s master service agreement — not the headline 2%. For Amex and Diners the rate is the premium slab from the gateway’s published or contracted pricing (2.95% to 3% typical). For RuPay credit on UPI the rate is approximately 2% above Rs 2,000 per transaction (with zero at or below); for PPI on UPI 0.5% to 1.1% above Rs 2,000.
Step 4 — Sum the dot product. Each cell’s percentage share multiplied by its rate, summed across cells, equals the method-mix-weighted expected cost. This is a single number expressed in basis points or percentage. For an OTT mix it sits well below 1%; for a card-heavy mix it sits closer to 1.5% to 1.7%.
Step 5 — Compare to the flat rate billed. The flat rate is the headline gateway percentage on the settlement file. The gap (flat rate minus weighted expected cost) times the monthly volume is the apparent over-recovery. Annualise to the contract review trigger.
Step 6 — Parse the gap. The gap is not one thing. The bank-account UPI and RuPay debit cells contribute pure Pattern #1 leakage on past periods (zero network MDR by statute; any positive percentage on those cells is recoverable). The non-zero cells contribute a renegotiation opportunity (the platform fee on each cell should be priced separately, not bundled into a card-grade flat). The dispute pack delivered to the gateway must carry both — past-period recovery on the zero-MDR cells per Pattern #1, and a forward-looking renegotiation to a per-network rate card or interchange-plus structure for the remainder.
NPCI’s public position on the zero-MDR regime is the primary external citation for the regulatory cells in steps 3 and 6. See the NPCI domain referenced in the external authority block below for the operative public position on UPI bank-account and RuPay debit zero-MDR.
How does this interact with GST and TDS?
Three reconciliation lines per transaction, kept strictly separate.
Network MDR plus platform fee with 18% GST. The combined fee line carries GST at 18% on the fee only — not on the transaction value. The corrected fee after the method-mix-weighted reconciliation has a corrected GST line as a consequence. ITC is claimable on the corrected line per the standard GST treatment for payment-aggregator services.
TDS where applicable. Under the Income-tax Act 2025 framework live since 1 April 2026, where the OTT subscription business sells through a third-party e-commerce operator or aggregator the operator deducts under Section 393(1) Sl. 8(v) using payment code 1035 at 0.1% on gross transaction value (this is the legacy 194O rate carried forward from October 2024; the older 1% rate is pre-October 2024 and should not appear in current reconciliations). 5% applies under the PAN/Aadhaar default rule. For an OTT business selling subscriptions directly through its own checkout to its own customers the operator scenario typically does not bite; for an OTT business distributed through a third-party app store or aggregator it does. None of this changes the method-mix-weighted MDR analysis — it is a separate line on the gross side, not on the fee side.
Net settlement credit. The bank-credited amount equals gross transaction value minus the combined fee minus GST on the fee minus any TDS deducted by an operator where applicable. The CFO’s monthly reconciliation reconciles each of the three lines to its statutory artefact: settlement file to gateway invoice and rate card for fee and GST, Form 26AS for any TDS deducted under code 1035, and bank-statement credit for the net.
What does “good” look like after remediation?
A controller running the method-mix-weighted expected-cost model one billing cycle after remediation should see:
- Per-network rate card (or interchange-plus structure) live on the account, with each cell priced separately and the flat rate retired.
- Bank-account UPI and RuPay debit cells billed at the contracted UPI-specific and RuPay-specific platform fee respectively, with the network MDR column reading zero on those cells (Pattern #1 hygiene).
- Non-RuPay debit billed within the RBI 2017 cap (0.40% small / 0.90% large; 0.30% / 0.80% QR; per-transaction caps Rs 200 / Rs 1,000).
- Visa/Mastercard credit consumer cells at the contracted enterprise rate (typically 1.4% to 1.6% for crore-scale monthly volume); Amex, Diners, premium/rewards cards, commercial/corporate cards, and international cards isolated and priced separately at their respective slabs.
- Method-mix-weighted expected cost recomputed monthly on the new rate card; effective rate (total fees divided by total volume) within 0.15 percentage points of the weighted expected cost; any excursion above that threshold triggers the per-network audit.
- GST at 18% on the fee as a separate line; no GST on transaction value.
- TDS under code 1035 at 0.1% where applicable as a separate line, reconciled to Form 26AS.
The forward-looking discipline is monthly. The method-mix-weighted reconciliation takes one analyst-day per month once the data pipeline is in place; for a UPI-heavy OTT or subscription business the recovery in the first cycle alone usually exceeds the cost of the discipline for the full year.
Continue reading in this cluster
- MDR charged on zero-MDR UPI / RuPay debit (Pattern #1) — cornerstone of the merchant-fees cluster
- Premium card misrouting to the 3% slab (Pattern #2) — sibling
- Domestic BIN charged at the international rate (Pattern #4) — sibling
- Merchant-fee leakage cluster hub — all eight patterns
- Payment gateway reconciliation — money page