Skip to main content
How-To · 11 min read

Net Banking MDR: Flat Fee vs Percentage for Indian Merchants

Indian finance teams routinely accept the gateway's default net banking line — flat ₹7-20 per transaction or 1.8% to 2% percentage — without checking which structure the merchant's own ticket distribution actually rewards. The break-even point between the two pricing models sits at roughly ₹500-700 per transaction. Above that, percentage wins decisively for high-ticket utility, B2B, and travel cohorts; below it, flat-fee wins decisively for D2C, food, and microtransaction cohorts. This article walks through the threshold logic, the worked numbers for a ₹50 crore monthly electricity utility, and the reconciliation discipline that keeps the contracted structure honest.

Terra Insight
Terra Insight Reconciliation Infrastructure

Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →

Published 23 June 2026
Domain expertise
TDS Reconciliation GST Input Credit Platform Settlements NACH Batch Matching Bank Reconciliation Form 26AS Matching ERP Integrations Enterprise Finance Ops
Knowledge Card
Problem

Indian finance teams accept the gateway's default net banking structure — flat ₹7-20 per transaction or 1.8% to 2% percentage — without computing the break-even ticket size against the merchant's own transaction distribution. A high-ticket utility, B2B, or travel merchant on a flat fee structure pays multiples of what percentage would cost on the same volume, and a low-ticket D2C or food merchant on a percentage structure pays multiples of what flat would cost. The structural choice is treated as a gateway default rather than a negotiation variable, and the leakage compounds month after month under a line item that finance teams glance past as 'net banking, ₹X lakh'.

How It's Resolved

Reconciliation computes the break-even ticket size between the flat fee F and the percentage P as F divided by P (for example, ₹12 divided by 1.8% equals ₹666.67), and segments the merchant's net banking transaction distribution into below-break-even and above-break-even buckets. Where the dominant bucket is above break-even (high-ticket cohorts), the expected-rate table favours percentage; where the dominant bucket is below break-even, the table favours flat. The engine then computes the actual deduction per transaction against the contracted structure and flags variances, separating contracted-structure deviation (gateway billing percentage on a flat contract or vice versa) from corridor-routing variance (mis-priced bank corridor) and from refund-non-reversal (MDR or flat fee retained on a refunded order).

Configuration

Net banking sub-method split on the gateway parent fee line; ticket-size bucketing rule at the contracted break-even (default ₹500-700 band, parametrised on flat-fee value and percentage value); bank corridor column on each net banking transaction; expected-rate table keyed on contracted structure (flat versus percentage), per-corridor rate where corridor-specific contracted; NETBANKING_STRUCTURE_VARIANCE class for contracted-structure deviation; NETBANKING_CORRIDOR_VARIANCE class for mis-priced corridor; refund-fee-retention check class; 18% GST line matcher to GSTR-2B for the Input Tax Credit claim.

Output

A per-transaction net banking variance report split by ticket band and bank corridor; a structure-choice analysis showing what the merchant's monthly net banking cost would be under each of flat-₹7, flat-₹12, flat-₹20, 1.8%, and 2% pricing on the actual transaction distribution; a corridor-mix dashboard for negotiating corridor-specific rates with the gateway; a refund-fee-retention exception list for gateway support; an Input Tax Credit claim schedule for the 18% GST on legitimate net banking fees.

A large electricity utility processes ₹50 crore in monthly net banking collections at an average ticket of ₹3,500. The gateway default is a flat ₹12 per transaction. The finance team sees a clean net banking line on the settlement file every month and assumes the per-transaction structure is cheaper because the headline percentage at the same gateway is 1.8% to 2%. The arithmetic disagrees. The utility is processing roughly 14.28 lakh net banking transactions a month, each carrying ₹12 of fee, which sums to ₹1.71 crore a month. The same volume at 1.8% percentage would have cost ₹90 lakh. The flat fee that looked cheap on the per-unit number is, in fact, almost double the percentage on the same gross.

This article walks through the break-even ticket logic, the worked numbers for the utility and three other persona cohorts, and the reconciliation discipline that catches the structure mismatch the month it starts.

Quick-Reference: Net Banking Pricing in India

StructureTypical rangeBreak-even ticketWins forLoses for
Flat fee₹7 to ₹20 per transaction₹389 (at ₹7 / 1.8%) to ₹1,111 (at ₹20 / 1.8%)Above ₹500-700 ticket: high-ticket utility, B2B, travel, EMI, NBFCBelow ₹500-700 ticket: D2C, food, quick commerce, microtransactions
Percentage1.8% to 2% of grossSame break-even, mirror sideBelow ₹500-700 ticketAbove ₹500-700 ticket
Negotiated enterpriseFlat as low as ₹5-7 at high volume; percentage as low as 1.2-1.5%Shifts with the negotiated valuesVolume above ~₹1 crore/monthSub-scale merchants
GST treatment18% on the fee only, never on transaction valuen/aAlways a separate linen/a
RegulatorNot capped by RBI (unlike debit / UPI)Bilateral merchant ↔ gateway contractn/an/a

Net banking MDR is not regulated under the RBI 2017 debit-card MDR cap or the zero-MDR mandate of January 2020 — both of those touch debit and UPI bank-account P2M only. Net banking is a bilaterally negotiated rate and structure between the merchant and the payment aggregator.

Why Does Net Banking Sit Outside the RBI MDR Cap?

The 2017 RBI circular on debit card MDR capped non-RuPay debit at 0.40% for small merchants and 0.90% for other merchants, with per-transaction caps of ₹200 and ₹1,000. The zero-MDR mandate of January 2020 covered UPI bank-account P2M and RuPay debit, under Income-tax Act §269SU read with Section 10A of the Payment and Settlement Systems Act 2007. Net banking has not been brought under either regime. Credit card MDR is similarly uncapped and bilaterally negotiated; net banking sits in the same negotiated band.

The practical consequence for a controller is that the headline 1.8% to 2% percentage or the headline ₹7 to ₹20 flat fee on a gateway’s published rate card is the starting position of a negotiation, not the rate the merchant must accept. Volume above roughly ₹1 crore a month, a willingness to consolidate gateways, or a stable bank corridor mix all create room to negotiate below the headline. A merchant whose net banking line is being billed at the published structure without ever having negotiated has accepted the gateway’s default, not the gateway’s best price.

How Do You Compute the Break-Even Ticket Size?

The break-even ticket size between a flat fee F and a percentage P is F divided by P. For ₹12 flat at 1.8%, break-even is ₹12 / 0.018, which equals ₹666.67. Below that ticket size, percentage is cheaper; above it, flat is cheaper.

The full break-even grid for the negotiation range in 2026 reads:

Flat feeAt 1.8% percentageAt 2% percentage
₹7Break-even ₹388.89Break-even ₹350.00
₹10Break-even ₹555.56Break-even ₹500.00
₹12Break-even ₹666.67Break-even ₹600.00
₹15Break-even ₹833.33Break-even ₹750.00
₹20Break-even ₹1,111.11Break-even ₹1,000.00

The practical range to remember is ₹500 to ₹700 for typical contracted values. Most Indian merchant ticket distributions fall on one side of that band clearly enough to make the choice obvious once it is computed. A utility, a hotel chain, an NBFC EMI collection, a B2B SaaS billing at a four-digit ticket sits well above the break-even and the percentage structure is decisively cheaper. A D2C brand at a ₹650 ticket, a quick-commerce platform at ₹350, a content unlock at ₹49 sits well below and the flat fee is decisively cheaper.

What Does the Worked Example Look Like for an Electricity Utility?

Consider a state electricity board’s billing arm processing ₹50 crore of monthly net banking collections at an average ticket of ₹3,500.

The transaction count is ₹50 crore divided by ₹3,500, which equals 14,28,571 transactions in the month.

Under the gateway default of ₹12 flat per transaction, the monthly fee is 14,28,571 × ₹12 = ₹1.71 crore. GST at 18% adds ₹30.86 lakh, for a gross monthly cost of ₹2.02 crore.

Under a 1.8% percentage structure on the same volume, the monthly fee is ₹50 crore × 1.8% = ₹90 lakh. GST at 18% adds ₹16.20 lakh, for a gross monthly cost of ₹1.06 crore.

The percentage structure is cheaper by ₹81 lakh per month at the flat ₹12 default, or ₹9.72 crore a year — entirely a function of the average ticket sitting well above the ₹666.67 break-even.

A negotiated reduction in the flat fee from ₹12 to ₹7 closes a meaningful share of the gap. At ₹7 flat: 14,28,571 × ₹7 = ₹1 crore per month, plus 18% GST of ₹18 lakh, for ₹1.18 crore monthly. That is still ₹12 lakh more expensive than the 1.8% percentage at gross — but the negotiation has reduced the leakage from ₹81 lakh a month to ₹10 lakh a month. The full negotiated saving — flat ₹7 from flat ₹12 — is ₹71 lakh a month, or ₹8.52 crore a year, without changing the pricing structure.

The right move for the utility is therefore a two-step renegotiation: first, move from flat ₹12 to either flat ₹7 or 1.8% percentage; second, structure-switch to percentage if the gateway will not cross the flat ₹7 threshold. Either lands inside the ₹1.06-1.18 crore monthly band; the prior contract was sitting at ₹2.02 crore.

Interactive Tool

MDR Effective Rate Calculator

Enter your monthly net banking gross, your average ticket, and the flat fee and percentage on offer. The calculator computes the break-even ticket size, projects the monthly fee under each structure, and shows the negotiated-rate sensitivity so the structure decision sits on the merchant’s own numbers, not the gateway’s default.

Open the tool →

How Does the Same Logic Play Out for a Low-Ticket D2C Brand?

The mirror image of the utility is a D2C consumables brand selling at an average ticket of ₹650. Monthly net banking gross of ₹2 crore implies 30,769 transactions.

Under flat ₹12 per transaction, monthly fee is 30,769 × ₹12 = ₹3.69 lakh, plus 18% GST of ₹66,500, for ₹4.36 lakh monthly.

Under 1.8% percentage, monthly fee is ₹2 crore × 1.8% = ₹3.60 lakh, plus 18% GST of ₹64,800, for ₹4.25 lakh monthly.

The two structures sit within roughly two percent of each other at the ₹650 ticket — the merchant is on the break-even line for a ₹12 / 1.8% structure (break-even ₹666.67, ticket ₹650). The choice is essentially indifferent. A small move in the negotiated values — ₹15 flat or 2% percentage — would tilt the answer decisively.

For a quick-commerce platform at a ₹350 ticket, the same ₹2 crore monthly volume implies 57,143 transactions. Flat ₹12 produces ₹6.86 lakh monthly fee; 1.8% produces ₹3.60 lakh. The flat structure is nearly double the percentage — the ticket sits well below the ₹666.67 break-even and the percentage is decisively cheaper.

The structural rule for low-ticket cohorts is the inverse of the utility rule: percentage wins, often by a wide margin, and any gateway default of a flat fee at this ticket band should be challenged in the next contract review.

What Is the Reconciliation Discipline Around the Contracted Structure?

The discipline is four variance classes, all running off the contracted rate card.

The first is the structure-variance class. The expected fee on every net banking transaction is the contracted flat fee or the contracted percentage. Any deduction that does not match — a percentage charge on a flat contract, or a flat charge on a percentage contract — is a NETBANKING_STRUCTURE_VARIANCE flag. A merchant on flat ₹12 who sees a ₹150 deduction on a ₹7,500 transaction is being billed 2% under what looks like a flat-fee contract; the variance is ₹150 minus ₹12 = ₹138 recoverable, and the next ten transactions in the same corridor will reveal whether the entire corridor has flipped or whether the variance is sporadic.

The second is the corridor-variance class. Where the merchant has negotiated corridor-specific rates (a cheaper rate on a public-sector bank corridor or on a particular mid-sized private bank that dominates the customer mix), the expected-rate table is keyed on the bank corridor. Any transaction billed at the headline rate where a corridor-specific rate was contracted raises a NETBANKING_CORRIDOR_VARIANCE flag. This is the variance class most likely to be missed if the engine treats net banking as a single line; the corridor column is the difference between catching this and not.

The third is the refund-fee-retention class. Net banking fees, whether flat or percentage, are industry-wide non-refundable. A refunded ₹7,500 transaction retains its ₹12 flat fee (or its ₹135 percentage fee at 1.8%); the merchant’s books should reflect the cost separately rather than expecting a netting against a future settlement. A high-refund cohort — quick commerce, ticketing, fast fashion — compounds this every cycle.

The fourth is the platform-fee versus MDR separation. Net banking, like UPI bank-account P2M, can carry a separate gateway platform fee in addition to the MDR-equivalent fee. The reconciliation engine should hold platform fee and MDR/flat fee as separate columns rather than fold them into one rate, since they have different contractual basis and different sensitivity to renegotiation.

All four classes share the same GST-on-fee discipline: 18% on the fee only, claimed as Input Tax Credit in GSTR-3B against GSTR-2B presence, never folded into the unit-cost percentage.

How Does Net Banking Compare to the Adjacent Rails for the Same Merchant?

The structural choice on net banking is best made in the context of the merchant’s full payment mix. For the electricity utility’s ₹50 crore monthly collections, the rail-mix likely looks like:

RailShare of monthly grossTypical contracted rateNotes
Bank-account UPI (P2M)35-45%Zero network MDROnly platform fee, if any, is contracted
Net banking25-35%Flat ₹7-12 or 1.8% percentageThis article’s subject
Visa/Mastercard credit8-12%1.4-2.5% negotiatedCard type drives the band
Visa/Mastercard debit5-10%Capped 0.40%/0.90% by RBIPer-transaction cap ₹200/₹1,000
RuPay debit5-10%Zero MDRMandated zero since January 2020
Amex / Diners1-3%2.95% to 3.5% premium slabPremium-slab leakage hot-cell
Wallets / PPI on UPI1-3%NIL at or below ₹2,000; 0.5%-1.1% aboveNPCI 24 March 2023

The 1.71 crore monthly flat-fee net banking line on the utility is, in this context, the single largest controllable spend in the rail mix. A move to percentage or to negotiated flat ₹7 saves more rupees than any optimisation on the smaller card rails. The same arithmetic does not hold for the D2C brand on a ₹650 ticket, where Amex/Diners share and chargeback exposure dominate the leakage map.

What Triggers a Re-Baseline of the Net Banking Structure?

Three events should force a re-baseline of the contracted structure.

First, a meaningful shift in the merchant’s own average ticket. A B2B SaaS that adds an SMB tier at a ₹999 cycle, an OTT that moves from ₹499 monthly to ₹2,499 annual, a hotel chain that adds a wellness brand at a different ADR — each of these crosses or shifts the break-even threshold and the structure that was correct at the prior ticket may not be correct at the new ticket. The reconciliation engine should run a quarterly check of the merchant’s average net banking ticket against the contracted break-even and flag any cohort whose average has crossed it.

Second, a volume-driven negotiation right. Crossing ₹1 crore a month in net banking gross typically opens a renegotiation conversation, and the new floor on the contracted structure should be tested at that threshold rather than at contract anniversary.

Third, a gateway-side rate-card change. A gateway moving its headline from 1.95% to 1.6% on a promotional window (Cashfree’s 10-year promotional structure expires 30 April 2026 for new sign-ups, locked 12 months) or from a flat fee to a percentage default for new merchants is a market signal — existing merchants on the old structure can usually anchor a renegotiation against the new market headline.

Continue Reading in the Merchant-Fees Cluster

  • Razorpay MDR reconciliation — gateway-specific rate card walkthrough, including the 2% domestic and 3% premium slab, the 0.99% subscription add-on, and the 2.15% RuPay credit-on-UPI platform fee.
  • PayU MDR reconciliation — PayU’s flat 2% domestic structure and 3% Amex/Diners/international slab, including the custom-rate threshold above roughly ₹10 lakh a month.
  • Flat-rate MDR concealing per-network cost differences — the cornerstone leakage pattern where a single blended rate hides UPI at zero and Amex at 3.5%; this article’s net banking structure choice is one face of the same problem.
  • Cashfree MDR reconciliation — Cashfree’s 1.95% standard, 1.6% promotional structure, and the UPI-share-mix condition that rescinds the promo if UPI falls below 40% of monthly GTV.
  • BillDesk MDR reconciliation — net banking-heavy gateway with a long history in utility and government billing corridors, where corridor-specific rates are the norm.
  • Merchant-fee leakage hub — every leakage pattern in the cluster, with the deterministic detection rules.
  • Payment gateway reconciliation money page — the operational reconciliation page for finance teams running gateway settlement files at scale.

For the regulatory framework that distinguishes net banking (uncapped, negotiated) from debit card MDR (capped under the 2017 circular) and UPI/RuPay debit (zero-MDR mandated since January 2020), see the Reserve Bank of India Payment and Settlement Systems portal.

Primary reference: Reserve Bank of India — RBI sets the regulatory framework for digital payment instruments under the Payment and Settlement Systems Act 2007. While debit card MDR is capped (0.40% small merchants / 0.90% large merchants under RBI circular DPSS.CO.PD No.1633/02.14.003/2017-18) and UPI bank-account P2M and RuPay debit are at zero MDR, net banking MDR is uncapped and bilaterally negotiated between the merchant and the payment aggregator, which is why flat-fee versus percentage structure is a negotiation variable rather than a regulated cell..

Frequently Asked Questions

Is net banking MDR regulated in India?
No. Net banking MDR is not subject to a regulatory cap. The Reserve Bank of India's 2017 circular DPSS.CO.PD No.1633/02.14.003/2017-18 capped non-RuPay debit card MDR at 0.40% for small merchants (turnover up to ₹20 lakh) and 0.90% for other merchants, with per-transaction caps of ₹200 and ₹1,000 respectively. The zero-MDR mandate of January 2020 (under Income-tax Act §269SU read with Section 10A of the Payment and Settlement Systems Act 2007) covers UPI bank-account P2M and RuPay debit. Neither regime touches net banking. The fee that lands on a merchant's net banking line is therefore the bilaterally contracted rate between the merchant and the payment aggregator, and the choice between a flat fee and a percentage is itself a negotiation variable. A controller pricing net banking should treat the published 1.95% to 2% headline as the starting position, not the floor.
Where is the break-even between a flat fee and a percentage for net banking?
The break-even ticket size is the point at which the flat fee per transaction equals the percentage applied to that ticket. For a ₹12 flat fee at 1.8%, the break-even is ₹12 divided by 0.018, which is ₹666.67. Below that ticket size, the percentage produces a smaller per-transaction cost; above it, the flat fee does. For ₹10 flat at 2%, the break-even is ₹500; for ₹20 flat at 2%, it is ₹1,000; for ₹7 flat at 1.8%, it is ₹388.89. The practical range to remember for negotiated net banking in 2026 is ₹500 to ₹700 — most merchant ticket distributions fall on one side of that band clearly enough that the dominant structure is obvious once it is computed.
How is GST applied on net banking MDR in India?
GST at 18% applies on the MDR or platform fee itself, never on the transaction value. The gateway issues a consolidated monthly tax invoice that totals MDR, platform fees, and any subscription or AutoPay add-ons, and applies one 18% GST line on the sum. A merchant whose net banking line is ₹1 crore in a month pays ₹18 lakh as GST on that line, claimed back as Input Tax Credit in GSTR-3B against GSTR-2B presence in the same period. The reconciliation engine should never fold the 18% into the per-transaction percentage or the flat fee — the 18% is recoverable and folding it into the unit cost overstates the cost of payments by roughly one-fifth. GST law on payment fees is unchanged; only the underlying MDR structure is negotiable.
What does flat-fee net banking look like in a settlement file versus percentage net banking?
A flat-fee net banking line shows the same rupee deduction per transaction regardless of ticket — every transaction in a given bank corridor reads ₹12 or ₹15 against the gross. A percentage line shows a deduction that scales linearly with the gross, with the same percentage applied per transaction in that corridor. The two are easy to distinguish on a sample of ten transactions of widely different ticket sizes. The leakage flag in either structure is the same: any deduction that does not match the contracted line. A merchant on a flat ₹12 net banking contract who sees a ₹150 deduction on a ₹7,500 transaction is paying 2% under what looks like flat-fee pricing — the gateway has billed percentage where flat was contracted, and that is recoverable. The reverse — flat where percentage was contracted, on a low-ticket cohort — is over-recovery for the merchant and under-recovery for the gateway, and is usually corrected in the gateway's favour at the next reconciliation cycle.
Does the choice of bank corridor affect net banking MDR?
It can. The acquirer-side cost of net banking varies modestly by bank — public-sector bank corridors and some mid-sized private bank corridors are routinely cheaper to acquire than the largest private bank corridors, and the gateway's blended net banking rate is a weighted average of those corridor costs. A merchant whose customer base is heavily concentrated in one or two bank corridors can therefore negotiate a corridor-specific rate that is materially better than the gateway's headline blended net banking rate. The reconciliation engine should carry the bank corridor as a column on every net banking transaction and the expected-rate table should be keyed on the corridor where corridor-specific rates have been contracted, so that mis-routing between corridors at the gateway end can be detected at variance.

See how TransactIG handles reconciliation for your industry

Configuration takes 2–4 weeks. No code development required. ISO 27001:2022 certified.