Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
Indian OTT, SaaS, D2C and other subscription merchants frequently treat the gateway settlement file's single "UPI" line as the zero-MDR rail mandated in January 2020. That assumption silently absorbs RuPay-credit-card-on-UPI volume which carries approximately 2% interchange above a ₹2,000 ticket — split roughly 1.5% to the issuing bank and 0.5% to the network and acquirer — under NPCI's October 2022 enablement. The customer pays nothing extra. The merchant pays the full cost. Without per-sub-instrument splitting at the gateway feed mapping stage, the leakage compounds every billing cycle and shows up as unexplained variance between contracted UPI economics and actual settlement net.
Pull settlement files at the lowest available sub-instrument granularity from every payment aggregator. Map UPI to two distinct sub-buckets: bank-account UPI (expected MDR 0%) and RuPay-credit-on-UPI (expected interchange 0% at or below ₹2,000, ~2% above ₹2,000). Compute effective rate by sub-instrument as fee divided by gross. Flag any non-zero MDR on the bank-account UPI bucket and any UPI line where the effective rate is consistent with a card-grade interchange. For above-₹2,000 RuPay-credit-on-UPI tickets, compute expected cost as gross × 2% and compare to actual fee column; surface deviation. Reconcile GST 18% as a separate line on the fee only.
MDR rule set per gateway and per sub-instrument with explicit RuPay-credit-on-UPI carve-out from the generic UPI bucket. Ticket-size threshold of ₹2,000 carried as a rule parameter for tier switching from 0% to ~2%. BIN-or-instrument-code mapping table that resolves the gateway feed's sub-instrument tag to (a) bank-account UPI, (b) RuPay credit on UPI, (c) PPI/wallet on UPI. GST-on-MDR retention flag enforcing 18% on fee only, never on transaction value. Reconciliation variance threshold at the sub-instrument level so a single "UPI" bucket cannot conceal mixed-MDR volume.
A monthly per-sub-instrument settlement report distinguishing zero-MDR bank-account UPI from chargeable RuPay-credit-on-UPI, with effective-rate, expected-cost, actual-cost and variance columns. A drill-down register of every above-₹2,000 RuPay-credit-on-UPI transaction with computed expected interchange. A GST-on-MDR audit trail with input-tax-credit alignment to the aggregator's monthly tax invoice. A reconciliation discipline note for the finance controller showing what percentage of the "UPI" line was actually zero-MDR and what percentage carried interchange — the basis for renegotiation and for accurate contribution-margin reporting.
A Bengaluru-based OTT video subscription business with 40,000 active subscribers on a ₹2,499 monthly plan reads its quarterly gateway dashboard. Total processed: ₹29.97 crore. The instrument-mix line says “UPI: 65%”. The finance controller assumes the zero-MDR rail covers that volume — the standard interpretation since the RBI/CBDT zero-MDR mandate took effect on 1 January 2020. The CFO assumes the same. The numbers in the monthly P&L assume the same.
The assumption is wrong. NPCI permitted RuPay credit cards to ride the UPI rail in an October 2022 circular. Above a ₹2,000 ticket the merchant pays approximately 2% interchange — split roughly 1.5% to the issuing bank and 0.5% to the network and acquirer. The customer is charged nothing extra. The gateway often labels the entire UPI line as just “UPI”. On a ₹2,499 ARPU subscription business with even a small RuPay-credit-on-UPI mix, the leakage compounds every billing cycle and never surfaces unless the settlement file is split by sub-instrument before the journal entries hit the GL.
This article walks the regulatory basis, the structural confusion, a worked OTT example, and the reconciliation discipline that prevents the silent margin drain.
Quick reference: RuPay-credit-on-UPI cost map
| Aspect | Detail |
|---|---|
| Instrument | RuPay credit card on UPI (P2M) |
| Sub-instrument code (typical) | CCoUPI / UPI-CC / RuPay-Credit-UPI |
| Interchange — at or below ₹2,000 | 0% |
| Interchange — above ₹2,000 | ~2% (~1.5% issuer + ~0.5% network/acquirer) |
| Who pays | Merchant (customer pays nothing extra) |
| Effective date | 1 October 2023 (NPCI circular Oct 2022 enabling; interchange schedule effective Oct 2023) |
| Regulator | NPCI / RBI |
| Comparator — bank-account UPI (P2M) | 0% network MDR (zero-MDR mandate since 1 Jan 2020) |
| Comparator — PPI/wallet-on-UPI | 0% at or below ₹2,000; 0.5%–1.1% above ₹2,000 |
| GST overlay | 18% on the MDR/platform fee only (never on transaction value) |
| TDS overlay (if e-commerce participant) | Section 393(1) Sl. 8(v) code 1035, 0.1% on gross |
| Legal basis (zero-MDR comparator) | Income-tax Act Section 269SU + PSS Act Section 10A |
What did NPCI’s October 2022 circular actually permit?
The October 2022 NPCI circular extended the UPI rail to RuPay credit cards. Until that point, UPI carried only bank-account-debit P2M flows and RuPay debit P2M flows — both within the zero-MDR prescription under Section 269SU of the Income-tax Act 1961 and Section 10A of the Payment & Settlement Systems Act 2007. The CBDT notification under Rule 119AA prescribed those two modes; zero-MDR on UPI P2M is current law as of June 2026 but under active review — the Parliamentary Standing Committee on Finance (report tabled 12 March 2026) and the Payments Council of India have proposed tiered/30 bps MDR for large merchants; no binding RBI/CBDT notification yet.
RuPay credit cards sit outside that zero-MDR prescription. NPCI’s enablement allowed a cardholder to link a RuPay credit card to a UPI handle and authorise UPI-shaped flows funded from the credit-card account. The user experience is indistinguishable from regular UPI — a QR scan, a UPI app authorisation, a clean acknowledgement. Underneath, the funding leg is a credit-card transaction. The interchange schedule that came with the enablement establishes the cost structure that matters for reconciliation: zero at or below ₹2,000, and approximately 2% above ₹2,000 — with the split allocating roughly 1.5% to the issuing bank and 0.5% to the network and acquirer.
There is no consumer surcharge. The cost falls entirely on the merchant. And in the gateway feed, the transaction often appears under a generic UPI bucket — sometimes with a sub-instrument code that distinguishes it (CCoUPI, UPI-CC, or a RuPay-credit tag), sometimes with the distinction collapsed at the dashboard level even when it exists in the raw file. That collapse is where the leakage lives.
Where does the leakage hide on a real settlement file?
Three structural places.
First, the dashboard view. Almost every Indian payment aggregator presents an instrument-mix donut on the merchant dashboard. UPI is a single slice. If the underlying API or raw CSV carries a sub-instrument column, the dashboard often does not surface it. The CFO sees “UPI: 65%” and treats it as zero-MDR. The raw file, queried at the lowest grain, shows the 65% decomposing into bank-account UPI and RuPay-credit-on-UPI in proportions the finance team has never quantified.
Second, the settlement journal mapping. Most ERP and accounting integrations map “UPI” to a single GL account. When the gateway reports a fee against UPI volume that should have been zero, the variance is closed as “gateway charge” or “settlement adjustment” and posted as expense without the sub-instrument provenance. The audit trail loses the information needed to renegotiate or to flag misclassification.
Third, the contracted rate sheet. Many merchant agreements still reflect the pre-October-2022 understanding that UPI is one instrument with one rate (zero). When the aggregator’s billing logic switches to apply the RuPay-credit-on-UPI interchange to volume the merchant believed was zero-MDR, there is no contract clause to point to in dispute. The agreement needs an explicit RuPay-credit-on-UPI sub-instrument carve-out with the ₹2,000 threshold and the ~2% above-threshold rate stated in writing.
The Razorpay published rate card, for instance, footnotes a 2.15% platform fee on RuPay-credit-on-UPI volume. PayU and Cashfree carry similar carve-outs. PhonePe PG publishes a single blended Standard Plan headline; the per-instrument rate has to be confirmed via the Business Dashboard quote. None of this is hidden in a contractual sense. It is hidden only in the operational sense — in the gap between what the merchant assumed “UPI” meant and what the gateway is actually billing.
How does the cost compare across UPI sub-instruments?
Three UPI sub-instruments, three cost profiles.
Bank-account UPI (P2M) carries zero network MDR. The merchant may still pay the gateway a platform fee — a Razorpay or PayU subscription-style fee, a Cashfree promotional rate, a PhonePe blended quote — but the network MDR component on a bank-account UPI P2M transaction is zero by mandate. Important to keep these straight in the chart of accounts: network MDR and gateway platform fee are economically distinct. The former is the regulated/contracted instrument cost. The latter is the gateway’s commercial charge for orchestration, settlement, dispute handling, and feature stack.
PPI or wallet-on-UPI carries no interchange at or below ₹2,000 and an NPCI-published interchange of 0.5%–1.1% above ₹2,000 (the wallet-interoperability circular of 24 March 2023). A 15-basis-point wallet-loading fee on volumes above ₹2,000 sits with the PPI issuer, not the merchant.
RuPay credit on UPI carries the ~2% above-₹2,000 interchange that this article is structured around. Below ₹2,000 it is zero. Above ₹2,000 it is roughly 2%, split issuer-network-acquirer as described.
For an OTT subscription business with a ₹2,499 ARPU plan, every transaction sits above the ₹2,000 threshold. The mix question — what share of the “UPI” line is bank-account versus RuPay-credit versus wallet — is therefore not a curiosity. It is a direct determinant of contribution margin.
Worked example: an OTT business with a ₹2,499 plan
A Bengaluru OTT video subscription business runs 40,000 active subscribers on a ₹2,499 monthly plan. Monthly gross merchandise value is ₹9.99 crore (40,000 × ₹2,499 = ₹9.996 crore, rounded ₹9.99 Cr). The instrument mix on the gateway dashboard reads as follows: UPI 65%, credit/debit cards 28%, net banking 5%, wallets 2%.
The 65% UPI line is what the finance team needs to decompose. Suppose the underlying raw settlement file, when queried at sub-instrument granularity, shows bank-account UPI at 95% of the UPI bucket and RuPay credit on UPI at 5%.
RuPay-credit-on-UPI volume: ₹9.99 Cr × 65% × 5% = ₹32.47 lakh.
Above ₹2,000 ticket: ~100% of this volume, because every subscription transaction is ₹2,499.
MDR at 2%: ₹32.47 lakh × 2% = ₹64,935 per month.
Annual: ₹64,935 × 12 = ₹7.79 lakh.
That is the cost the business is bearing — accurately — on RuPay-credit-on-UPI volume in a clean billing scenario.
Now the leakage layer. Suppose the gateway, on this account, bills the entire UPI line at a “UPI flat” 2.15% rate that the finance team never questioned because they assumed it applied only to a tiny sliver of non-zero-MDR sub-volume. In fact it applies to the entire RuPay-credit-on-UPI bucket at 2.15% rather than the 2% interchange basis: ₹32.47 lakh × 2.15% = ₹69,805 per month. The difference is ₹69,805 − ₹64,935 = ₹4,870 per month, or ₹58,440 annually. This is the additional leakage masquerading inside the UPI line. It is small per month and meaningful in aggregate. It compounds with any RuPay-credit-on-UPI mix growth and with any future change in the interchange split.
What the worked example illustrates is not a single magnitude. It is the structure of the question. The CFO needs to know three things every month: (1) what share of UPI volume was bank-account UPI (true zero-MDR), (2) what share was RuPay credit on UPI (zero at or below ₹2,000, ~2% above), (3) what the gateway billed on each share. Without that decomposition, the contribution-margin calculation on the subscription business is wrong by a structural amount.
Model your true UPI effective rate by sub-instrument
Drop your monthly GMV, UPI share, RuPay-credit-on-UPI mix, and ticket profile into the MDR Effective-Rate Calculator. It splits the UPI line by sub-instrument, applies the ₹2,000 threshold, computes expected interchange against the actual fee column, and surfaces the rupee leakage hiding inside your “UPI” bucket.
Open the MDR Effective-Rate Calculator →Reconciliation discipline: how do you split UPI by sub-instrument?
Five operational steps.
Step one — pull settlement files at the lowest available grain. Most aggregators expose a per-transaction CSV or API endpoint that carries the instrument and sub-instrument tag, the gross, the fee, the GST, the net, the bank reference and the timestamp. The dashboard view almost always collapses sub-instrument detail; the raw file usually does not. NPCI publishes circular and sub-instrument schemas at npci.org.in that define the canonical instrument codes — your engineering team should map the gateway’s sub-instrument tag to those canonical codes once and lock the mapping in a versioned table.
Step two — split the UPI bucket into three sub-buckets. Bank-account UPI (expected MDR 0%). RuPay credit on UPI (expected interchange 0% at or below ₹2,000; ~2% above). PPI/wallet on UPI (expected interchange 0% at or below ₹2,000; 0.5%–1.1% above). Every UPI transaction must resolve to exactly one of these three; if the sub-instrument tag is missing, flag the transaction for manual review rather than defaulting it to bank-account UPI.
Step three — compute expected interchange per transaction. For each above-₹2,000 RuPay-credit-on-UPI transaction, expected interchange equals gross × 2%. For each above-₹2,000 PPI/wallet transaction, expected interchange equals gross × the contracted PPI rate in the 0.5%–1.1% band. For bank-account UPI of any ticket size, expected interchange equals zero. The gateway’s platform fee — distinct from interchange — is a separate column carried alongside expected interchange, not folded into it.
Step four — compare to the actual fee column. Variance by sub-instrument and by day. Any non-zero MDR on bank-account UPI is the single most important flag — it indicates either misclassification at the gateway or a billing error at the aggregator. Any RuPay-credit-on-UPI fee that exceeds 2% of gross indicates a gateway platform-fee uplift that needs to be reconciled to contract. Any GST line that exceeds 18% of the fee component (not 18% of transaction value) indicates a posting error.
Step five — close the loop on contract. The merchant agreement needs an explicit RuPay-credit-on-UPI clause with the ₹2,000 threshold and the ~2% above-threshold rate stated. The aggregator’s monthly tax invoice needs to reconcile against the per-transaction GST totals so the input-tax-credit chain is intact under Rule 36(4). The chart of accounts needs three UPI sub-accounts so the GL itself preserves the distinction.
Done with discipline, this is what separates a finance team that knows its contribution margin from a finance team that thinks “UPI” is one thing.
How does TDS Section 393 sit on top of this?
Where the OTT business is selling through a third-party operator (an app-store, a streaming aggregator, a bundling distributor), the operator deducts TDS at 0.1% on gross under Section 393(1) Sl. 8(v) payment code 1035 of the Income-tax Act 2025. The rate was 1% under the pre-October-2024 Section 194O regime; it was reduced to 0.1% effective 1 October 2024 and migrated to the new section/code structure under the 2025 Act.
The 0.1% TDS is layered on top of, and entirely separate from, gateway MDR. GST 18% applies to the MDR/platform fee component only — never to the transaction value. So a ₹2,499 subscription transaction routed through an aggregator and funded from a RuPay credit card on UPI carries four distinct fee components on the settlement file: (a) RuPay-credit-on-UPI interchange at ~2% on gross (because ticket is above ₹2,000), (b) the gateway’s platform fee per the agreement, (c) GST at 18% applied to (a) + (b) — the fee components only, (d) TDS at 0.1% deducted by the operator under code 1035 and reconciling to Form 26AS at year end.
Folding any two of these into a single blended “settlement charge” line breaks one of the reconciliation paths — the ITC chain, the 26AS reconciliation, or the gateway dispute window. The discipline is to keep all four on separate columns from the moment the settlement file is ingested.
What does the ledger entry actually look like?
For a single ₹2,499 OTT subscription transaction funded from a RuPay credit card on UPI, the clean journal looks like this. Debit Bank (settlement account) ₹2,381.12. Debit MDR/Interchange — RuPay-credit-on-UPI ₹49.98 (₹2,499 × 2%). Debit GST Input — on MDR ₹8.997 (₹49.98 × 18%). Debit Gateway Platform Fee — RuPay-credit-on-UPI ₹0 in this scenario (folded into interchange for illustration; in practice the gateway’s commercial line sits on its own column). Debit TDS Receivable — Code 1035 ₹2.499 (₹2,499 × 0.1%, applicable only where an aggregator/operator deducts). Credit Subscription Revenue ₹2,499. Add GST output on revenue per the merchant’s GST structure. The point is that the entry resolves to five distinct columns, not one. A merchant that posts a single “Net settlement: ₹2,381.12” line to revenue contra is collapsing the entire reconciliation chain — there is no audit basis later for GST input-tax-credit on the MDR, no Form 26AS reconciliation on the TDS, no contract-dispute basis on the interchange, no margin variance analysis by sub-instrument.
For aggregated daily settlement reporting, the chart of accounts should carry at minimum: UPI bank-account (zero-MDR), UPI RuPay-credit ≤ ₹2,000, UPI RuPay-credit > ₹2,000 (the ~2% bucket), UPI PPI/wallet ≤ ₹2,000, UPI PPI/wallet > ₹2,000, and the corresponding MDR sub-accounts in expenses. This is not over-engineering. It is the granularity at which the leakage is observable and the policy at which the contract is renegotiable.
How do gateways differ on the RuPay-credit-on-UPI line?
Three operational variations the finance team should expect.
Razorpay’s published pricing footnotes a 2.15% platform fee on RuPay-credit-on-UPI volume — the 0.15-point uplift above the ~2% interchange is the gateway’s commercial margin. Enterprise contracts negotiated at ₹1 Cr-plus monthly GMV often reduce this to a tighter band; the contract must state the sub-instrument and the threshold explicitly.
PayU’s published 2% flat blends multiple instruments; the RuPay-credit-on-UPI line is typically billed at the premium-instrument 3% slab in the standard footnote unless the contract carves out a specific RuPay-credit-on-UPI rate. The merchant agreement must distinguish RuPay credit on UPI from generic premium credit-card volume.
Cashfree’s 10-year-anniversary promotional rate of 1.6% for new merchants signing between 18 September 2025 and 30 April 2026 — locked 12 months, up to ₹1 Cr monthly GTV — requires UPI to remain at least 40% of monthly GTV or the offer rescinds. The treatment of RuPay-credit-on-UPI within the “UPI” share for that 40% threshold is a contract-language question; the merchant should confirm in writing whether the promo’s UPI denominator includes or excludes RuPay-credit-on-UPI volume.
PhonePe PG publishes only a blended Standard Plan headline (currently struck-through “Free*” under a limited-time launch offer). The per-instrument rate is not publicly disclosed; the RuPay-credit-on-UPI rate must be confirmed via the Business Dashboard quote and read into the settlement reconciliation engine as a contracted rule.
In every case, the operational discipline is the same: contract-explicit, sub-instrument-tagged, threshold-aware. The gateway commercial differences are negotiable; the underlying NPCI interchange schedule is not.
What about the politics of the zero-MDR debate?
The current debate matters operationally because the worst-case planning scenario for an Indian subscription business is the introduction of a tiered MDR on bank-account UPI itself. If the bank-account UPI rail moves from 0% to even 30 basis points on merchants above ₹20 lakh annual turnover (the Payments Council of India’s proposed structure), an OTT business doing ₹100 crore annual GMV with 65% UPI mix sees an incremental cost in the ₹19-lakh-annual range from a single bps move.
That is not the current law. As of June 2026, bank-account UPI remains zero-MDR by mandate. The Parliamentary Standing Committee report (tabled 12 March 2026) and the PCI proposal are both recommendations, not binding. The FY27 Union Budget continues to allocate funds for the zero-MDR subsidy on RuPay debit and low-value BHIM-UPI. But the operational implication is clear: the finance team that has not built per-sub-instrument settlement reconciliation discipline today will not have the tooling to absorb a tiered-MDR transition cleanly. The RuPay-credit-on-UPI work is the rehearsal for the broader transition.
Continue reading in this cluster
- Platform fee leakage on Razorpay, PayU, Cashfree — the per-transaction fee-column audit playbook for D2C and subscription businesses.
- MDR fee reconciliation across instruments — the operative reconciliation logic for splitting MDR by instrument and surfacing variance against contract.
- Razorpay settlement reconciliation — the Razorpay-specific settlement file mapping and journal-entry discipline.
- Cluster hub: Merchant fees & MDR leakage
- Money page: Payment gateway reconciliation