PayU MDR Reconciliation: Standard 2% + Premium Slab Handling for Indian Merchants

Every PayU settlement credit a finance team sees in its nodal-bank statement is the net of a mixed basket — domestic Credit Card, Debit Card, NetBanking, UPI, Wallet, and the premium-slab basket of American Express, Diners Club, commercial cards, international cards and EMI. The published price card is two lines: 2% + GST on the domestic basket, 3% + GST on the premium basket. The actual reconciliation surface is considerably wider, because PayU’s settlement file segregates Card Type and Card BIN columns that determine which slab each transaction was billed at — and it is the silent re-classification of a transaction from one bucket to the other that quietly drives merchant cost above the headline rate.

This article is written for the Indian D2C, subscription, OTT, SaaS and travel merchant moving from sub-Rs 10 lakh published pricing to negotiated custom rates above the Rs 10 lakh per month threshold. The reconciliation discipline it describes is for finance controllers, payment-ops owners and internal audit teams who treat the gateway settlement file as a primary cost-of-revenue source and want every basis point of fee leakage isolated against an explicit contract.

Quick-Reference Table

What Does PayU’s Settlement File Actually Contain?

The PayU Biz dashboard exports a settlement report that finance teams can pull by date range. Each row of the report corresponds to a single captured transaction; the rows are batched into a settlement_id that maps one-to-one with a NEFT credit on the merchant’s nodal bank statement. The columns that matter for MDR reconciliation are the ones that determine which slab each transaction was billed against — Payment Mode (Card, NetBanking, UPI, Wallet, EMI), Card Type (Credit, Debit, Prepaid, Commercial), Card BIN (the first six digits of the issuer’s card range, which the network classifies as consumer or commercial and as domestic or international), Issuer Country, Gross Amount, MDR Amount, GST on MDR, and Net Settlement.

The reconciliation join from this file to the merchant’s books has two halves. The outer join is settlement_id against settlement UTR — confirming that the batch of transactions in the report adds up to the NEFT credit in the bank statement. The inner join is the per-transaction reconciliation: each transaction’s Gross Amount minus its MDR Amount minus its GST on MDR should equal its Net Settlement, and the MDR Amount should equal the Gross Amount multiplied by the expected rate for that Payment Mode, Card Type and Card BIN. A variance on either half is a reconciliation exception that needs to be classified.

The published column structure is consistent across PayU Biz settlement exports, but the field names occasionally vary by merchant onboarding template. The discipline is to bind the reconciliation tool to the column structure once at onboarding and verify each new export matches the contracted schema — a new column or a renamed column is the most common cause of a silent ingest failure that surfaces months later as an unreconciled balance.

Where Does PayU Hide Premium-Card MDR?

The single largest leakage cell on a PayU settlement file is American Express and Diners Club volume folded into a blended-rate calculation that the merchant did against the 2% headline. The published price card lists these networks at 3% + GST in the premium-slab footnote, and the settlement file does bill them correctly at 3% — but the reconciliation exception arises when the finance team computes its effective rate as total MDR divided by total GMV, lands at something like 2.05% or 2.08%, and concludes the cost is “roughly the headline.” The 0.05 to 0.08 points of headroom above the 2% is not noise — it is the 1 percentage point of premium cost on the 5 to 7 percent of GMV that came from Amex, Diners, commercial cards and international cards.

The discipline is to compute the effective rate per network, not as a single blended figure. The PayU settlement file flags Payment Mode and Card Type explicitly, and the Card BIN identifies the network. Isolate every transaction whose BIN matches the American Express range (typically 34 and 37) and every transaction whose BIN matches the Diners Club range (typically 36, 30 and the Discover-acquired ranges). Compute the MDR Amount divided by Gross Amount for that isolated set. The result should land at 3% — confirming the slab is correct — and the volume should be a separately stated line in the management report rather than dissolved into the blended figure.

The commercial-card cell behaves differently. A commercial or corporate-issued BIN is auto-flagged by PayU into the 3% premium slab even when the merchant has not explicitly contracted to accept commercial cards at that rate. The leakage here is operational rather than billing: a merchant who has not modelled a commercial-card cohort in the revenue plan suddenly sees the 3% slab volume creep up over consecutive months because a B2B customer or distributor cohort has begun paying with corporate cards. The fix is to track commercial-card volume share month over month and renegotiate the slab if the cohort is material.

How Does the Rs 10 Lakh Custom-Rate Threshold Work?

PayU’s pricing page indicates that custom negotiated rates are available above approximately Rs 10 lakh per month in gross merchandise value. Below this threshold, the published 2% domestic and 3% premium rates are the contract; above it, the merchant moves to a custom-rate slab that is documented in the signed Merchant Service Agreement. The crossover is not automatic — the merchant initiates the renegotiation through the PayU sales team, and the new slab takes effect from the agreed effective date on the amended MSA.

Two reconciliation behaviours change at the crossover. First, the expected-rate baseline that the reconciliation tool uses must switch from the published 2% to the contracted custom rate on the effective date. Second, the premium-slab basket may or may not move — many custom-rate contracts negotiate the domestic blended rate down from 2% to 1.6 to 1.8 percent while leaving the Amex, Diners, international and EMI premium slabs at the published 3%. A merchant who assumes the custom rate applies to all volume will under-reserve cost; a merchant who reconciles cleanly will isolate the premium-slab basket as a separate line throughout the contract period.

The renegotiation cadence matters. Custom-rate contracts at the Rs 10 lakh threshold typically have a defined review window — six months, twelve months — at which the rate is revisited. The reconciliation discipline is to begin tracking the merchant’s effective rate against the contracted rate from the first month of the new slab, accumulate the variance, and walk into the renegotiation with a documented variance file rather than a blended estimate.

Which Leakage Cells Are Specific to PayU?

Three leakage cells recur across PayU reconciliations and are worth flagging at the platform level. The first is the international-acceptance forex-line gap. International acceptance on PayU requires a separate banking-partner approval, and the resulting fee structure has two layers — the 3% MDR on the card and a forex conversion line on non-INR settlement. The forex line is sometimes invoiced cleanly on the settlement file; in other cases the conversion happens at a rate set by the underlying banking partner and the merchant sees only a net INR credit. The reconciliation discipline is to identify every cross-border transaction by issuer country, expect the 3% MDR, and reconcile the forex line either as a separately stated charge or as the implied difference between the card-currency gross and the INR settled amount.

The second is the EMI billing-tier cell. EMI on PayU — debit-card EMI, credit-card EMI, cardless EMI — bills into the 3% premium slab on the published price card. The leakage here is when a merchant runs an EMI offer through PayU as a promotional product, treats it in their internal commercials as a 2% line, and only discovers in the next quarter that EMI volume is costing 3%. The discipline is to either negotiate a specific EMI slab in the custom-rate contract, or model EMI explicitly at 3% in the financial plan and the reconciliation rules.

The third is the commercial-card auto-flag. As covered above, commercial-card BINs auto-flag to the 3% slab without merchant confirmation. The leakage is the absence of a control gate — a merchant who does not run a commercial-card variance report will see commercial-card volume grow silently as B2B customers shift payment methods, and will absorb the 1 percentage point delta as a quiet cost-of-revenue increase. The reconciliation rule is a commercial-card BIN tracker that flags any transaction with a commercial-flagged BIN and either re-prices it to the contracted commercial rate or surfaces it for renegotiation.

What Is the Per-Instrument MDR Table for PayU?

The published rate card on PayU compresses to a two-tier table. The reconciliation discipline is to load this table as the expected-rate baseline below Rs 10 lakh per month and overlay the contracted custom rate above it.

A consistent reconciliation note: the 2% headline on UPI and on RuPay debit is the PayU platform fee, not the network MDR. The network MDR on UPI bank-account P2M and on RuPay debit P2M is zero by the regulatory mandate. This distinction matters when the merchant computes its true network cost — for an internal cost-of-revenue report it is legitimate to attribute the 2% to PayU as a platform fee; for a regulatory or category-level cost study it should be classified as gateway fee rather than network MDR.

Worked Example: D2C Beauty Brand Crossing the Rs 10 Lakh Threshold

Consider a D2C beauty brand running checkout on PayU at Rs 85 lakh per month in GMV across Card, NetBanking and UPI. The current basket mix is 48% UPI bank-account P2M, 35% domestic consumer credit card, 7% domestic commercial card, 5% Amex and Diners, 5% other (a blend of NetBanking, Wallet and RuPay debit). The brand is presently above the Rs 10 lakh threshold and below it on the published pricing — currently transitioning into a custom-rate contract.

Under the published 2% blended on the domestic basket and 3% on the premium basket, the expected monthly MDR works out as follows. Of the Rs 85 lakh GMV, 48% (Rs 40.8 lakh) at 2% on UPI is Rs 81,600; 35% (Rs 29.75 lakh) at 2% on consumer credit card is Rs 59,500; 7% (Rs 5.95 lakh) at 3% on commercial card is Rs 17,850; 5% (Rs 4.25 lakh) at 3% on Amex and Diners is Rs 12,750; 5% (Rs 4.25 lakh) at 2% on the other basket is Rs 8,500. Total expected published-rate MDR: approximately Rs 1.8 lakh per month before GST, or roughly 2.12% effective blended rate. The merchant’s books would commonly round this to “about 2%” — and miss the 0.12 percentage points of premium-slab cost.

After crossing the Rs 10 lakh threshold and negotiating a custom domestic rate of 1.7% blended on Card, NetBanking and UPI, the expected MDR shifts. On the same basket mix, the 48% UPI volume now bills at 1.7% — Rs 69,360; the 35% consumer credit card at 1.7% — Rs 50,575; the 5% other basket at 1.7% — Rs 7,225. The commercial card and Amex/Diners volume remain on the premium 3% slab — Rs 17,850 and Rs 12,750 respectively — because the custom-rate negotiation typically does not move the premium basket. Total expected custom-rate MDR: approximately Rs 1.58 lakh per month before GST, a saving of approximately Rs 25,000 per month or Rs 3 lakh per year against the published-rate baseline. Importantly, the brand’s reconciliation file must separately verify that the Amex and Diners volume continues to bill at the contracted premium 3% — Rs 12,750 in this example — and not drift higher.

The reconciliation discipline that surfaces this saving is the per-network effective-rate model. Without it, the brand would compute total fee divided by total GMV, land at a blended 1.86% or so, and have no way to attribute the gap between the 1.86% computed and the 1.7% contracted — the gap is the premium-slab volume sitting underneath. With the per-network model, the variance is decomposed into known contracted slabs, and the reconciliation closes cleanly each month rather than carrying a quiet residual.

What Does an Automated Reconciliation Tool Check for PayU?

A reconciliation tool configured for PayU performs five deterministic checks on every settlement file. The first is the outer join: each settlement_id must match a single NEFT credit on the nodal bank statement on UTR, date and net amount; any orphaned settlement_id or orphaned credit is flagged as a date-boundary exception. The second is the per-transaction MDR equation: Gross Amount minus MDR Amount minus GST on MDR must equal Net Settlement; sub-rupee differences are rounding exceptions, larger differences are fee-deduction exceptions. The third is the per-network expected-rate check: every transaction’s MDR Amount divided by Gross Amount must equal the contracted rate for that Payment Mode, Card Type and Card BIN within a defined tolerance; transactions outside tolerance are billing exceptions.

The fourth is the premium-slab isolation: every Amex BIN, Diners BIN, commercial-flagged BIN and international-issuer BIN must be tracked as a separately reported volume line, with its effective rate verified against the contracted premium slab. The fifth is the refund and chargeback MDR retention check: refunded transactions retain the original MDR on the industry standard, so the reconciliation tool tracks the cumulative MDR retained on refunds as a separately stated cost of refund — a number that is rarely surfaced in management reports but materially affects net merchant economics for a subscription business with high cancellation rates.

Two further checks overlay the regulatory dimension. The TDS check matches the operator’s Section 393(1) Sl. 8(v) deduction at 0.1% (payment code 1035) against the merchant’s Form 26AS — every transaction credited or paid by PayU as an e-commerce operator carries the 0.1% deduction, and the merchant claims credit in its income-tax return. The GST check matches PayU’s tax invoice for the GST on MDR against the merchant’s GSTR-2B; the 18% GST on the MDR fee is recoverable as input tax credit for registered businesses, but only if the invoice flow reconciles cleanly. These two checks turn the gateway settlement file from a payment-ops artefact into a regulatory artefact that ties into the merchant’s broader compliance posture.

Where Does the PayU Reconciliation Connect to Wave 1 Leakage Patterns?

The PayU per-instrument reconciliation maps directly to several Wave 1 leakage patterns that operate across gateways. The premium-slab isolation discipline is the same pattern documented in Amex and Diners hidden in blended MDR — the blended-rate calculation conceals 3% volume inside a 2% headline, and the fix is the per-network effective-rate model rather than a single weighted average. The commercial-card auto-flag exposure is the pattern in commercial cards billed at consumer or premium rate — the BIN routing is deterministic, but the merchant control gate that catches an unexpected commercial-card cohort is operational and easy to skip.

The international-acceptance forex-line gap shares structure with domestic BINs charged at international rates, which is the inverse symptom of the same BIN-classification mechanism — the leakage is symmetric, in one direction the domestic BIN is charged at the international rate, in the other direction the international volume lacks a cleanly invoiced forex line. The PayU custom-rate transition pattern is an instance of flat-rate MDR concealing per-network cost differences — the published 2% obscures that the underlying basket is 48% UPI at the zero-network-MDR rail and 5% Amex at the 3% premium slab, and the negotiation only fully captures value if the merchant decomposes the basket before signing.

The refund and chargeback discipline maps to MDR not reversed on refunds — PayU follows the industry-standard non-reversal practice, so the leakage is structural and the merchant should model the refund-MDR cost explicitly rather than discover it as a residual after each quarter. The settlement-level join between PayU’s nodal NEFT credit and the per-transaction report is the same matching surface covered in PayU settlement reconciliation: matching nodal credits to orders, which carries the operational detail on settlement_id, settlement cycles and LazyPay BNPL.

Continue Reading in This Cluster

The merchant-fees cluster on Terra Insight covers the per-gateway reconciliation surface and the platform-level leakage patterns that operate across them. Adjacent to this article: PayU settlement reconciliation for the nodal-credit join detail; Amex and Diners hidden in a blended MDR rate for the per-network effective-rate discipline; commercial cards billed at consumer or premium rate for the BIN auto-flag exposure; domestic BINs charged at international rates for the BIN-classification symmetry; flat-rate MDR concealing per-network cost differences for the blended-rate trap; and MDR not reversed on refunds for the refund-cost structural pattern.

For the broader category, the merchant-fees cluster hub collects every per-gateway and per-leakage-pattern article into a single index. For the money page that anchors the topic, payment-gateway reconciliation covers the platform-level reconciliation product surface that ingests PayU, Razorpay, Cashfree, PhonePe and the other Indian gateways into a single cost-of-revenue view. For the broader buying decision, reconciliation software India anchors the comparison frame.

The published rate card referenced throughout this article is the public PayU pricing page; the regulatory caps on debit-card MDR that bind the non-RuPay debit lines are set by the Reserve Bank of India under the 2017 rationalisation circular. For the authoritative source on the regulatory framework that governs PayU as a payment aggregator, see the Reserve Bank of India.