Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
Luxury hotel chains, airline OTAs, jewellery retailers, and premium ecommerce merchants absorb material leakage because the issuer interchange on premium, signature, and infinite credit cards is higher than the consumer credit interchange, and Indian gateways pass the differential to the merchant by either routing the entire premium card to the published 3 percent slab or applying a non-qualified surcharge above the contracted consumer rate. The merchant sees one blended MDR column and cannot separate premium from consumer billing without a per-transaction BIN-tier join. Auto-classification errors that route consumer-tier signature cards to the premium slab compound the leakage by 0.5 to 1 percentage point per affected transaction.
For every credit card transaction on the settlement file, derive the issuer product tier from the BIN against the acquirer schedule rather than from the gateway classification field alone. Compute expected fee as contracted slab for that BIN tier and network multiplied by gross. Compare to actual fee column, including any non-qualified surcharge line. Aggregate effective rate per network per card tier monthly. Flag consumer-tier transactions billed above the contracted consumer slab by more than a 5 basis point band, and flag premium-tier transactions billed at a slab the merchant agreement does not name. Cross-reference EMI-converted premium-card transactions for slab stacking.
Acquirer BIN-tier reference table refreshed quarterly, with first-six-digit ranges marked consumer-credit, premium-rewards (signature, infinite, world, world-elite), commercial, premium-corporate. Per-network contracted slab table for consumer, premium, commercial, EMI, international. BIN-tier rule in the MDR rule set per gateway and per network. Per-transaction expected-fee column versus actual-fee column including non-qualified surcharge. Monthly effective-rate-by-tier report by gateway. Slab-stacking detector for EMI-converted premium-card transactions. Recovery register feeding the merchant-fee leakage class for raising structured disputes against the gateway.
A monthly effective-rate matrix by network by card tier showing where the consumer tier is reading above contracted consumer slab and where the premium tier is reading above any contracted premium slab. A per-gateway BIN-classification variance log listing transactions where the gateway tier differs from the acquirer tier. A non-qualified surcharge audit log capturing every surcharge line above the rate column. A standing dispute register tracking BIN-tier claims filed and accepted, with recovery quantified at the monthly and annual run rate.
A luxury hotel chain operating six properties across India processes roughly ₹3.5 crore of monthly credit card volume at its booking engine and on-property card machines. The card mix breaks 18 percent premium and rewards cards (Visa Signature, Visa Infinite, Mastercard World, Mastercard World Elite — the issuer products marketed to high-spending corporate travellers and frequent flyers), 70 percent standard consumer credit, and 12 percent commercial and corporate cards on business-stay folios. The contracted slab in the merchant agreement names 2 percent for consumer credit, 3 percent for premium and commercial, and 3 percent for Amex and Diners. The controller pulls the gateway settlement file, computes the effective rate by tier, and reads something unexpected: 35 percent of card volume has been billed at the 3 percent slab. The premium and commercial mix together is 30 percent. Seventeen percentage-points of consumer-tier card volume has been classified premium and routed to the 3 percent slab.
That gap is the canonical premium-card MDR leakage signal in India. Premium and rewards cards do carry higher issuer interchange because the airport lounge access, accelerated reward points, complimentary insurance, and concierge programmes are funded from interchange revenue. Gateways legitimately pass the differential to the merchant. The leakage is not the existence of the premium slab — it is the auto-classifier routing consumer-tier signature and rewards cards to the premium slab without the BIN evidence to back it. This guide is the interchange-tier mechanics, the detection workflow, the reconciliation discipline, and the worked recoverable for a hospitality merchant carrying material premium-card volume.
Quick reference: premium credit card MDR map
| Aspect | Detail |
|---|---|
| Instrument | Credit card (Visa, Mastercard, RuPay credit, Amex, Diners) |
| Premium tier products | Visa Signature, Visa Infinite (Privilege and Reserve), Mastercard World, Mastercard World Elite, RuPay Select, RuPay Platinum |
| Consumer credit MDR (network) | 1.4% to 2.5% domestic, negotiated; published gateway rate around 2% |
| Premium credit MDR (network) | 1.8% to 3% domestic, often billed at the premium 3% slab |
| Amex / Diners MDR | 2.95% to 3% domestic, structurally at the premium slab |
| Commercial credit MDR | 2.5% to 3%, billed at the premium 3% slab across Razorpay, PayU, Cashfree |
| Regulatory cap | None — credit-card MDR is uncapped (RBI 2017 caps apply only to non-RuPay debit at 0.40% / 0.90%) |
| Tier carrier | BIN — first six to eight digits of the card number, joined to the acquirer BIN-tier schedule |
| Operative reference | Acquirer interchange schedule (HDFC Acquiring, Axis Acquiring, ICICI Acquiring, RBL Bank, Worldline); the gateway classification field is derivative |
| Common leakage mechanism | Auto-classification of consumer Visa or Mastercard BINs as Signature or World, then routed to the 3% premium slab |
| Alternative leakage mechanism | Non-qualified surcharge applied above the contracted consumer rate as a separate fee line |
| GST overlay | 18% on the MDR or platform fee only, separate line — never folded into the MDR percentage |
| TDS overlay | Income-tax Act 2025 §393(1) Sl. 8(v) payment code 1035 at 0.1% applies to e-commerce operator payouts where relevant; not to the MDR itself |
The carrier of the tier attribute is the BIN. The carrier of the billed rate is the settlement file column (plus any non-qualified surcharge line). The audit is the join between the two.
Why do premium and rewards cards cost the merchant more?
The interchange economics of a premium card are straightforward. A Visa Infinite cardholder pays no annual fee in exchange for a portfolio of benefits the issuer is contractually committed to deliver: complimentary airport lounge access (often unlimited and including a guest), accelerated reward points on hotels, airlines, and dining (typically 2x to 10x the standard consumer earn rate), travel insurance, lost-card liability cover, and a concierge desk. None of that is free for the issuer. The lounge access is paid per visit to Priority Pass or DragonPass at $25 to $35 a touch. The reward points are a hard liability on the issuer balance sheet at 0.5 to 1 paise per point depending on the redemption catalogue. The insurance carries a per-policy premium to the underwriter.
The issuer funds the benefits programme from one revenue line: interchange. Standard consumer credit interchange on Visa or Mastercard in India runs roughly 1.4 to 1.8 percent of transaction value as the issuer share. Premium-tier interchange runs roughly 2.0 to 2.5 percent on Signature and World products, and 2.3 to 2.8 percent on Infinite and World Elite. The differential is the budget for the benefits programme.
That interchange is paid by the merchant via the gateway. The gateway sees the issuer-product tier on the BIN, pays the issuer the elevated interchange, and either bakes the differential into a 3 percent slab on the merchant’s settlement file or applies a non-qualified surcharge above the contracted consumer rate. From the merchant’s perspective both mechanisms cost the same; what differs is the line presentation.
How does a non-qualified surcharge differ from being routed to the 3% slab?
Two mechanisms produce the same total fee with different line presentations on the settlement file. The clean mechanism is slab routing: the rate column on the settlement file reads 3 percent for the premium-card transaction, the fee column shows 3 percent of gross plus 18 percent GST on the fee, and the merchant can compute effective rate per tier directly from the rate column.
The opaque mechanism is the non-qualified surcharge. The rate column reads the contracted consumer slab — 2 percent — and the fee column shows 2 percent of gross. A separate fee line is added below labelled non-qualified surcharge, premium-card uplift, interchange differential, or simply IC differential. The surcharge line lands at 0.5 to 1 percent of the transaction value, which closes the gap to the premium slab. The blended fee on the period now reconciles to roughly 3 percent on the premium-card subset, but the rate column alone shows 2 percent.
The audit consequence is that the per-transaction effective-rate computation has to include any non-qualified surcharge line, not just the rate column. A controller running a clean rate-column audit on a settlement file that uses the non-qualified surcharge mechanism will conclude the file reads 2 percent across all card tiers and miss the premium-card leakage entirely. The non-qualified surcharge line has to be folded into the effective-rate computation per transaction.
Where does the leakage hide in the BIN-tier mapping?
The legitimate premium-card billing is the gateway recovering its interchange cost; the leakage is the gateway misclassifying a consumer card as premium and routing it to the 3 percent slab anyway. Three sub-patterns recur on real settlement files.
First, the auto-classifier overshoot. The gateway billing engine flags any BIN that matches a Visa Signature, Visa Infinite, Mastercard World, or Mastercard World Elite product code as premium and routes to the 3 percent slab. The BIN classifier is built on the network’s published product schedule, which the gateway refreshes monthly or quarterly. Where the network adds a new Signature BIN range and the gateway’s schedule has not yet refreshed, a Signature card may slip through at the consumer slab (under-recovery, gateway absorbs); where the network retires a Signature range and the gateway schedule still flags it, a consumer card slips into the premium slab (over-recovery, merchant absorbs). The merchant-side leakage is the second direction.
Second, the BIN-prefix ambiguity. Some issuer ranges contain a mix of consumer and premium products under the same first-six-digit prefix, with the disambiguation resting on the seventh and eighth digits. A gateway billing engine that classifies only on the first six digits and defaults the ambiguous range to premium routes a meaningful share of consumer cards to the 3 percent slab. The acquirer schedule, which classifies on the full BIN, is the binding reference.
Third, the cross-network application of a non-qualified surcharge. A merchant has contracted with the gateway for a 2 percent consumer credit slab and a 3 percent Amex and Diners slab — but has not separately contracted a premium-card slab for Visa Signature or Mastercard World. The gateway treats the absence of a contracted premium slab as an implicit authorisation to apply a non-qualified surcharge on those products. The merchant agreement is silent; the billing engine assumes consent. The remedy is contract discipline — every premium product tier the gateway recognises must have an explicit contracted slab in the merchant agreement, even if that slab equals the consumer slab (effectively waiving the differential).
What does the audit look like on a luxury hotel chain — worked example?
A luxury hotel chain operating six properties processes ₹3.5 crore of monthly credit card volume across the booking engine and on-property card machines. The BIN-tier join against the acquirer schedule shows a card mix of 18 percent premium (Visa Signature, Visa Infinite, Mastercard World, Mastercard World Elite), 70 percent standard consumer credit, and 12 percent commercial and corporate cards on business-stay folios. The contracted slabs in the merchant agreement read 2 percent for consumer credit, 3 percent for premium and commercial, and 3 percent for Amex and Diners.
The settlement file shows that the gateway has billed 35 percent of card volume at the 3 percent slab — 18 percent of premium plus 12 percent of commercial is 30 percent of contracted premium-or-commercial volume, but the actual 35 percent at premium means 5 additional percentage-points of consumer-tier cards have been routed to the premium slab. Re-running the BIN-tier join on the per-transaction file confirms it: 17 percentage-points of the 70 percent consumer volume have been classified premium by the gateway’s auto-classifier (the acquirer schedule classifies them as standard consumer Visa or Mastercard).
The arithmetic on the recoverable runs as follows. Total monthly card volume is ₹3.5 crore. The misrouted share is 17 percent of the total card volume, which is ₹59.5 lakh. The slab differential on the misrouted share is 1 percentage point (3 percent billed versus 2 percent contracted consumer). The monthly leakage is ₹59.5 lakh times 1 percent, which is ₹59,500 per month. Annualised the recoverable is ₹7.14 lakh.
The audit lift does not stop at the recoverable. Two structural flags arise from the same run. First, the 18 percent of correctly-classified premium-card volume — ₹63 lakh per month — is contractually priced at 3 percent, which is the network ceiling; an aggressive renegotiation can target 2.75 percent on a multi-year commit, taking ₹15,750 per month off the premium-card line. Second, the consumer slab itself at 2 percent is above the ₹3.5 crore-monthly negotiated achievable of roughly 1.6 percent on enterprise pricing; tightening the consumer slab on the next contract review takes a further ₹1.4 lakh per month off the consumer line. The ₹59,500 monthly auto-classifier recovery is the floor. The renegotiation upside is the lift.
What is the reconciliation discipline that catches this on day one?
Wire the BIN-tier check into the per-transaction settlement file ingestion at the point the file is parsed. For every card row, derive the issuer product tier from the acquirer BIN-tier table (not from the gateway classification field), compute the expected fee as the contracted slab for that tier times gross, sum the actual fee column with any non-qualified surcharge line, and log the variance with BIN, gateway tier, acquirer tier, contracted slab, billed slab, and surcharge line where present.
Surface three reports monthly. The effective-rate-by-tier matrix tells the controller where each network and tier is reading against the contracted slab on a per-tier basis. The BIN-classification variance log lists transactions where the gateway tier disagrees with the acquirer tier — these are the dispute candidates that go to the gateway with the BIN evidence attached. The non-qualified surcharge audit log captures every surcharge line above the rate column, with the BIN tier and contracted slab beside it, so a surcharge applied without contracted authorisation is surfaced rather than absorbed.
Refresh the acquirer BIN-tier table quarterly. The issuer banks open new premium-card ranges every month — HDFC Bank Infinia, Axis Magnus, ICICI Emeralde, SBI Aurum, IDFC FIRST Wealth — and the gateway billing engine lags the acquirer schedule by weeks. Stale BIN-tier tables generate false positives in one direction and miss real leakage in the other.
The Reserve Bank of India’s Payment Aggregator framework specifies the disclosure expectations on merchant statements that make the per-transaction BIN-tier audit feasible; the join between the settlement file and the acquirer schedule is the operative discipline that converts the disclosure expectation into a recoverable.
Quantify the premium-card auto-classification leakage on your settlement file
Enter your monthly card gross, your premium versus consumer split from the acquirer BIN-tier join, your contracted consumer and premium slabs, and the gateway’s billed effective rate per tier. The MDR Effective-Rate Calculator returns the per-tier expected fee, the actual fee with any non-qualified surcharge folded in, the misrouted share of consumer volume billed at premium, and the annualised recovery — the same arithmetic that converted ₹59,500 a month into a structured BIN-tier dispute on the luxury hotel chain worked above.
Open the MDR Effective-Rate Calculator →Continue reading in this cluster
This is the premium and rewards card tier of the merchant-fee leakage framework. Continue with the cornerstone reference for the full audit framework, then the adjacent leakage patterns:
- MDR fee reconciliation across networks and instruments — the cornerstone audit framework for the full eight-pattern set
- Commercial card billed at consumer rate: MDR audit path — the corporate-and-commercial tier of the same BIN-tier audit logic
- Premium card misrouting to the 3% slab: BIN-tier audit — the cornerstone BIN-tier audit reference for premium-card classification
- Cluster hub: Merchant fees and MDR reconciliation
- Money page: Payment gateway reconciliation