Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
Streaming subscription checkouts frequently display a 'Pay via UPI' tile that in practice routes premium credit cards through UPI-on-cards rails at 1.5% to 2.4% MDR plus 18% GST. Finance teams that reconcile MDR by tile label — assuming 'UPI = zero' — under-book gateway cost, under-recover input tax credit, and produce fee schedule mismatches that auditors flag against the 30/12/2019 Zero MDR notification.
Fee extraction reads the network field, card type field, and BIN prefix from every settlement line, not the checkout tile label. A rules table maps each combination — UPI plus VPA is zero MDR; RuPay Debit is zero MDR; RuPay Credit routed through UPI is 1.5% to 2.4%; American Express, Visa premium, or Mastercard premium is the corresponding published card schedule — to the expected MDR band. Each line's computed MDR is compared to the actual fee deducted in settlement, and variances beyond a tolerance are opened as exceptions with the specific rule that failed.
Settlement network dictionary (UPI, RuPay Debit, RuPay Credit, Visa Debit, Visa Credit including Signature and Infinite, Mastercard Debit, Mastercard Credit including World and World Elite, American Express, Diners), UPI-on-cards routing flag, MDR schedule table per network per MCC per card tier, GST rate 18% for aggregator services, and the merchant's tax invoice from GSTR-2B matched by GSTIN and invoice number.
Fee reconciliation register keyed by transaction with expected MDR versus actual MDR versus GST versus ITC-claimable amount; variance report grouped by network and card tier; input tax credit schedule for GSTR-3B; and an audit-ready trail showing the Zero MDR notification is honoured on UPI and RuPay Debit rails, with the priced rails booked at their contractually agreed schedules.
A streaming service in India can display any checkout label it wants — “Pay via UPI” is the most common tile because customers recognise it and complete the flow with fewer drop-offs. But the tile label is a customer experience surface, not a rail definition. When a premium credit card is linked to a UPI app under NPCI’s UPI-on-cards circular, a transaction that opens on a “UPI” tile can settle on a credit card rail at 1.5% to 2.4% MDR plus 18% GST. Fee reconciliation that groups settlement lines by tile label — instead of extracting network, card type, and BIN from the settlement file — treats zero-MDR and priced rails as one bucket and hides the merchant’s real gateway cost.
The reconciliation in one paragraph
For every settlement line, extract the actual rail — network (UPI, RuPay Credit, Visa, Mastercard, American Express, Diners), card type (credit or debit), and where available BIN prefix — and compare the deducted MDR against the schedule that applies to that rail for the merchant category. UPI and RuPay Debit must reconcile to zero MDR under the 30/12/2019 notification. Every other rail reconciles to its contractual schedule with 18% GST on the fee. Input tax credit on the GST is matched to the aggregator’s tax invoice from GSTR-2B and reported in GSTR-3B. Variance beyond a set tolerance opens as an exception with the identified rule failure.
What the scenario looks like in India — safe illustrative streaming brands
Consider a subscription checkout for an OTT platform — imagine Netflix India, Amazon Prime Video India, Sony LIV, ZEE5, ALT Balaji, MX Player, Aha Video, Sun NXT, Voot Select, or the audio platform JioSaavn. The subscription is priced at ₹1,999 per year including 18% GST on the taxable supply of the streaming service.
The customer opens the checkout and sees a tile grid — Cards, UPI, Wallets, Net Banking, EMI. Under the UPI tile they type a VPA or scan a QR. The transaction completes. To the customer the experience was UPI.
At settlement the next day, in the Razorpay, PayU, Cashfree, Bill Desk, or CCAvenue file, that line appears with fields that describe what actually happened. If the payment was a genuine VPA-to-VPA UPI transfer, the file shows Network = UPI, Card Type blank, MDR 0.00, GST 0.00. If the payment was on a RuPay Credit card the customer had linked to their UPI app, the file shows Network = RUPAY, Card Type = CC, MDR at the credit card schedule, GST at 18%. If a premium network card — where NPCI has permitted UPI-on-cards for that category and program — was linked, the file shows the same shape with the appropriate network.
The tile the customer saw was UPI. The fee-bearing rail was a credit card. The reconciliation must read the file, not the tile.
For an ad-supported streaming platform mixing subscription and one-time purchases, or a hybrid OTT product with a live cricket pay-per-view surge, the fee mix looks even less like the tile mix. During a launch window, premium credit card usage often spikes because subscribers running large monthly credit card bills consolidate their entertainment spend on rewards-earning cards. A recon that assumes “UPI = zero” during that spike materially under-books gateway cost.
The regulatory and PG-rules overlay
Three regulatory documents govern how this reconciliation must be constructed.
The Ministry of Finance notification dated 30 December 2019, effective 1 January 2020, made under Section 269SU of the Income-tax Act read with Section 10A of the Payment and Settlement Systems Act, 2007, prescribes Zero MDR on UPI and RuPay Debit transactions for merchants specified under Section 269SU. The notification is unambiguous — no charge whatsoever, including MDR, is to be imposed on the customer or on the merchant for these two rails. Any settlement line where Network = UPI and the payment method was a genuine UPI transfer, or where Network = RUPAY and Card Type = DR (debit), must carry MDR of zero.
The NPCI circulars on UPI-on-cards created the routing overlay that produces this reconciliation problem. UPI-on-cards allows a permitted credit card to be linked to a UPI app and used at merchant checkouts through the UPI interface. The rail underneath the customer experience is still the credit card network. The MDR schedule of the credit card applies. NPCI’s own communications and the RBI’s payment system guidance emphasise that the Zero MDR mandate applies to UPI and RuPay Debit, not to credit cards routed through UPI. The circulars started with RuPay Credit and have been extended by NPCI to selected permitted networks in specified merchant categories over time.
The RBI Guidelines on Regulation of Payment Aggregators and Payment Gateways, dated 17 March 2020 as amended, govern the settlement files this reconciliation reads from. A licensed Payment Aggregator (PA) must deliver settlement to merchants under the PA framework, and the format and content of the settlement file typically expose network, card type, and (with masking) BIN prefix. Merchants have a right, under the PA agreement, to a settlement file complete enough to allow this reconciliation. Where a gateway’s file collapses UPI-on-cards transactions into a “UPI” bucket without a network breakdown, the merchant should escalate — the RBI framework contemplates transparent settlement reporting.
The GST layer adds 18% Central and State GST on the aggregator’s service fee. The aggregator raises a tax invoice for the fee plus GST, and this invoice appears in the merchant’s GSTR-2B. The merchant claims the GST as input tax credit in GSTR-3B where the fee is attributable to taxable outward supplies, which includes the streaming subscription revenue.
The CGST Section 52 TCS at 0.5% for e-commerce operators applies to certain aggregator relationships and requires its own reconciliation stream — for MDR fee extraction on subscription checkouts, the operating rule is that the fee is a service consumed by the merchant, the merchant pays MDR + GST, and the GST portion is ITC-recoverable.
A worked example — illustrative numbers
An OTT platform sells a ₹1,999 annual subscription — priced at ₹1,694.07 taxable supply plus ₹305.03 GST at 18%, rounded to ₹1,999 gross. The subscriber checks out.
Scenario A — the subscriber types a VPA on the UPI tile. The bank account behind the VPA is debited ₹1,999. In the settlement file, Network = UPI, Card Type = blank, MDR = 0.00, GST on MDR = 0.00. Zero MDR notification honoured. Merchant net settlement = ₹1,999. Nothing to reconcile except the UPI settlement lifecycle itself.
Scenario B — the subscriber has linked an American Express Platinum Reserve or an HDFC Infinia to their UPI app (in a category and program where UPI-on-cards is permitted), and pays through the same “Pay via UPI” tile. The settlement file line shows Network = AMEX or Network = VISA (depending on the card program routing), Card Type = CC, MDR = 2.00% (illustrative — the actual schedule sits in the merchant’s PA agreement), Fee = ₹39.98, GST on fee at 18% = ₹7.20, Total deduction = ₹47.18. Merchant net settlement = ₹1,999 – ₹47.18 = ₹1,951.82.
Scenario C — the subscriber has linked an Amazon Pay ICICI credit card to their UPI app and pays. The settlement line shows Network = RUPAY, Card Type = CC (if the card was tokenised on the RuPay Credit UPI route) or the Visa/Mastercard co-badged network otherwise, MDR at the applicable credit card schedule for that MCC, GST at 18%.
Now consider a fee reconciliation that groups by tile label. It sees three “UPI” transactions and expects ₹0 MDR on all three. The gateway has actually deducted ₹0 on Scenario A and roughly ₹47 each on Scenarios B and C. The variance report will show two “unexpected MDR on UPI” exceptions. If those exceptions are dispositioned as “gateway error, dispute the deduction”, the merchant chases a dispute that the gateway will reject on first review because the deduction is correct per the UPI-on-cards rail. If the exceptions are dismissed as “small variance, ignore”, the merchant under-books ₹47.18 of gross gateway cost per premium-card-on-UPI transaction and under-claims ₹7.20 of GST ITC per line.
Across a subscriber base with even 5% penetration of UPI-on-cards among premium subscribers, at an annual ARPU of ₹1,999 and a subscriber count in the hundreds of thousands, the under-booked cost and lost ITC compounds into material misstatement in the annual accounts.
Common reconciliation breakages
The recurring failure modes cluster into six patterns.
First, grouping settlement lines by checkout tile label instead of by settlement Network + Card Type. This is the root cause of every other pattern.
Second, treating Network = RUPAY as uniformly zero MDR. RuPay Debit is zero MDR under the 30/12/2019 notification. RuPay Credit is not. The Card Type field must separate them; where Card Type is absent from the settlement file, escalate to the aggregator for a fuller file.
Third, missing the BIN dimension. A single merchant category can carry three different MDR bands depending on card tier — for example, the same MCC settling a Visa Classic Credit, a Visa Signature, and a Visa Infinite may face three different schedules. The reconciliation rule table needs a card-tier axis, keyed off BIN where the aggregator exposes it.
Fourth, treating 18% GST on MDR as a lost cost. It is not — it is input tax credit under GST where the fee attaches to taxable supplies. The GST portion must be matched to the aggregator’s tax invoice from GSTR-2B and posted to input credit in GSTR-3B.
Fifth, letting UPI-on-cards transactions fall between reconciliation streams. The gateway file line is “UPI-ish” enough that a “UPI settlement” recon team may ignore it, and “credit-card-ish” enough that a “card settlement” recon team may also ignore it. A single fee reconciliation pass across all networks eliminates this gap.
Sixth, dispositioning legitimate premium-card-on-UPI deductions as gateway errors. This wastes cycles on dispute submission and burns goodwill with the aggregator. The correct disposition is that the deduction is per contract; the checkout tile label was misleading to internal finance; the fix is upstream — either update the reconciliation rules or the checkout experience.
The refund flow amplifies this problem. When a premium-card-on-UPI subscription is refunded, the credit note under Section 34 of the CGST Act and the ITC reversal in GSTR-3B Table 4B(2) must reverse the specific fee-bearing rail, not the “UPI” tile label. See the refund reconciliation payment gateway guide for the credit note and ITC reversal mechanics, and see the MDR fee reconciliation article for the full multi-network MDR schedule matching pattern.
Sibling scenarios in this streaming and OTT wave 1 series cover the refund-after-settlement reconciliation, the chargeback dispute won recovery flow, the weekend and holiday settlement stretch, split settlement with two bank credits, mid-month MDR rate renegotiation, test transaction ghost 98-paise lines, and the subscription versus ad revenue multi-stream reconciliation.
How a reconciliation platform handles this
A reconciliation platform tuned to India payment gateway settlement files treats the tile label as metadata and the settlement fields as truth.
Every settlement line is parsed for Network, Card Type, and BIN where available. A rules table — configured once by the finance team from the aggregator’s PA agreement — maps each combination to the expected MDR schedule. UPI + VPA and RuPay Debit route to zero. Every other combination routes to its contractual band. The expected MDR is computed per line and compared against the actual fee deducted, with a small tolerance for rounding.
Variances above tolerance surface as exceptions. Each exception carries the specific rule failure — for example, “Line shows Network = UPI but MDR of ₹47.18 was deducted; the settlement metadata reveals the actual rail was AMEX credit; the deduction is contractually correct; the checkout tile-to-rail label mismatch should be raised with product”. The disposition path is clear and does not waste cycles on false dispute submission.
The GST leg is handled in the same pass. The aggregator’s tax invoice for the aggregate fee — the fee across all merchant transactions in the invoicing period — is matched from GSTR-2B by GSTIN and invoice number. Each transaction-level fee line contributes to the aggregate ITC claim in GSTR-3B, and the platform emits a schedule showing which invoice from GSTR-2B backs which portion of the ITC.
The output — a fee reconciliation register per transaction, a variance report per network and card tier, a GST ITC schedule for GSTR-3B, and an audit trail — closes the loop between the Zero MDR notification, the UPI-on-cards routing overlay, and the merchant’s monthly accounts.
Structured payment gateway reconciliation covers this pattern across every network the merchant accepts. Broader reconciliation software India capability extends the same discipline to bank statements, GSTR-2B matching, TDS reconciliation, and platform settlement variances, so the fee-and-tax accuracy on subscription revenue reconciles cleanly through to the annual return.
NPCI publishes the UPI circulars that define which credit card networks are permitted to route through UPI-on-cards and under which merchant categories, and the Ministry of Finance Zero MDR notification of 30 December 2019 remains the governing document for UPI and RuPay Debit merchant-fee treatment.
The five FAQs above address the tile-versus-rail distinction, the network and card-type fields to trust, and the GST ITC recovery on MDR that most finance teams either mis-book or forget entirely.
Frequently Asked Questions
Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
- ▸ Ministry of Finance — Notification dated 30 December 2019 (effective 1 January 2020) prescribing Zero MDR on UPI and RuPay Debit transactions under Section 269SU of the Income-tax Act read with Section 10A of the Payment and Settlement Systems Act, 2007.
- ▸ Reserve Bank of India — Guidelines on Regulation of Payment Aggregators and Payment Gateways (17 March 2020, as amended) establishing PA licensing, settlement timelines, and merchant reporting obligations that govern the settlement files this reconciliation reads from.
- ▸ National Payments Corporation of India — UPI Circulars enabling UPI-on-cards, including linking of RuPay Credit and other permitted credit card networks to UPI apps for merchant payments in specified MCC categories, with the underlying MDR schedule of the card retained.
- ▸ Central Board of Indirect Taxes and Customs (GST Council) — GST at 18% on payment gateway service fees including MDR, invoiced by the aggregator to the merchant; input tax credit claimable in GSTR-3B where the fee is attributable to taxable supplies.