Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
Indian-issued cards routinely show up in settlement files billed at 3%+ international MDR with a cross-border forex line layered on, when the issuer country derived from the BIN is India and the contracted domestic slab is around 2%. The over-charge is invisible in blended-rate dashboards and surfaces only at per-transaction grain. Every month the leakage compounds, with 18% GST on the inflated fee flowing through alongside.
Reconciliation extracts the first six digits of every settled card transaction, looks up the BIN against a current issuer-country registry, and compares the BIN-derived scope to the scope the acquirer applied. Any transaction with BIN-country IN that was charged at an international slab (above ~2.5 percent network MDR) or carries a non-zero forex line is flagged as a mis-classification. The over-charge is the actual MDR minus the contracted domestic rate, applied to the transaction value, with proportional GST.
BIN registry refreshed at gateway-cycle cadence, domestic-versus-international scope rule per network, contracted-rate matrix keyed by network and tier, forex-line presence check (must be zero for BIN-country IN), per-transaction settlement extract feed, monthly exception report with recoverable amount per transaction.
Per-transaction mis-classification report with recoverable over-charge by row, monthly aggregate of recoverable MDR and recoverable GST, fee-adjustment request letter ready for acquirer submission, and a trended BIN-classification dashboard that flags drift before it compounds across a quarter.
| Aspect | Detail |
|---|---|
| Instrument | Card (credit / debit, P2M) |
| Scope determinant | First six digits of card PAN — the BIN |
| Domestic MDR slab | ~1.4 to 2.5 percent (network-dependent, contracted) |
| International MDR slab | 2.69 to 3.5 percent (gateway pricing pages) |
| Forex line | Only valid where BIN-country is outside India |
| GST | 18 percent on the MDR line, separately invoiced |
| Detection grain | Per-transaction settlement file with BIN visible |
| Regulator / network rules | RBI (acquirer licensing); Visa, Mastercard, RuPay, Amex (BIN registries) |
A finance head at a D2C brand looks at the gateway’s monthly invoice and sees the card MDR line running a few basis points above what the contract should produce. Most teams shrug — promotional mix shift, end-of-month corporate-card spike, some plausible explanation. The leakage that hides best in that blended number is the mis-scoped transaction: an Indian-issued card billed at the international slab with a forex margin layered on. The over-charge per transaction is around 100 to 150 basis points; on the few percent of volume affected it adds up to small four-figure monthly losses, plus GST. It is the third of the eight standard leakage patterns in the merchant-fee stack and the easiest one to detect deterministically once you have per-transaction data — because the BIN itself decides the answer.
What does “domestic BIN billed at international rate” actually mean?
Every card carries a primary account number whose first six digits are the Bank Identification Number, registered by the network (Visa, Mastercard, RuPay, American Express, Diners) and mapped to an issuer institution and an issuer country. The card networks publish, and the acquirers consume, a BIN registry that determines the scope of each transaction.
When a card is presented at checkout, the acquirer reads the BIN, looks up the issuer country, and applies the MDR slab tied to that scope. A BIN whose registered issuer country is India is a domestic transaction and should be billed at the contracted domestic slab — typically 1.4 to 2.5 percent across Visa and Mastercard credit, lower on debit. A BIN whose registered issuer country is anywhere else is a cross-border transaction and is billed at the international slab — 2.69 to 3.5 percent on the published pricing of Razorpay, PayU and Cashfree, with a separate forex margin layered on the transaction value.
The mis-classification is when an Indian BIN — say, an HDFC, ICICI, SBI or Federal Bank issuer with the IN country code — is processed at the international slab. The settlement file then shows three things that should not co-occur: a domestic BIN, an international MDR rate, and a non-zero forex amount. Any one of them alone is normal in some context; all three on the same row is the leakage signature.
Why does this mis-classification happen in production?
Three structural reasons, in roughly descending order of frequency.
First, BIN-table staleness. Card networks issue new BIN ranges every quarter as banks expand their card programmes, fintechs co-brand with sponsor banks, and PSU and co-operative banks refresh their plastic. The acquirer is supposed to refresh its BIN-to-country registry on the network’s published cadence — typically monthly. In practice the refresh slips, and newer Indian BINs end up either unclassified (defaulting to international under fallback logic) or stale-classified. The smaller and newer the issuing bank, the higher the probability.
Second, fallback logic. When a transaction arrives with a missing, malformed, or unrecognised BIN, the acquirer’s processing rules need a default. The conservative default — both prudentially and commercially — is the international slab, because under-charging an international transaction as domestic leaves the acquirer carrying the interchange differential. From the merchant’s point of view this means a small but persistent tail of unrecognised BINs is billed at the higher slab even when most of them are perfectly ordinary Indian cards.
Third, dispute-cycle re-scoping. A transaction initially scoped as domestic may get re-scoped during a forex-fluctuation adjustment or a chargeback workflow. The re-scope writes a new MDR rate and a forex margin into the settlement file, and the merchant has no notification mechanism to confirm the original scope was correct. The line item changes silently between cycles.
The Reserve Bank of India supervises payment aggregators under the PA/PG Guidelines and licenses acquirers under the Payment and Settlement Systems Act, 2007. The licensing framework expects accurate scope classification; sustained mis-classification across a merchant’s settlement file is a contractual breach that the merchant can raise with the acquirer’s compliance team and, if unaddressed, with the gateway’s principal banker.
How does the leakage hide in the gateway report?
In a default gateway dashboard the merchant sees a single card-MDR figure, sometimes split by network and rarely split by scope. A blended monthly fee that should be 2.0 percent and is actually 2.05 percent looks like ordinary mix variance. It is not.
To make the leakage visible, the settlement file needs three columns the dashboard does not surface by default: the full card BIN (first six digits, or the first eight where the network has migrated to eight-digit BINs), the scope flag the acquirer assigned (domestic or international), and the forex amount per transaction. With those three columns, the per-row check is mechanical — BIN look-up to country, compare to assigned scope, flag the mismatch.
Most Indian payment aggregators will produce a per-transaction CSV on request, with a turnaround of one to three business days. The format varies across Razorpay, PayU, Cashfree and PhonePe but the essential fields are always available. If your current report does not contain BIN-level detail, that is the first thing to request — without it, no audit of this pattern is possible.
Worked example: D2C health-supplement brand finds the leak
A D2C health-supplement brand processes Rs 2 crore monthly in card GMV through its payment gateway. The contracted domestic card slab is 2 percent. The blended card MDR for the past quarter has been running at 2.03 to 2.04 percent — close enough to the contract that finance has not investigated.
The controller pulls a per-transaction settlement extract for the past month, filters card transactions where the assigned scope is “international,” and runs the BIN against a current issuer-country registry. The audit returns the following.
Of the Rs 2 crore monthly card GMV, 3.2 percent — Rs 6.4 lakh — was processed at the international slab of 3 percent. Cross-checking the BINs against the network registry, every one of those transactions had a BIN-country of IN. The cards were issued by Indian banks (a mix of HDFC, ICICI, Axis, Federal Bank, and several newer co-operative bank BINs), but the acquirer’s stale registry had not classified the newer BINs as domestic, and fallback logic pushed them to the international slab.
The over-charge calculation:
- Affected volume: Rs 6.4 lakh
- Applied rate (international): 3 percent
- Contracted rate (domestic): 2 percent
- Rate over-charge: 1 percentage point
- MDR over-charge per month: Rs 6.4 lakh times 1 percent = Rs 6,400
- MDR over-charge annualised: Rs 76,800
- GST at 18 percent on the over-charge: Rs 6,400 times 18 percent = Rs 1,152 per month, Rs 13,824 annualised
- Forex line erroneously applied: a small additional amount per transaction (typically 1 percent forex margin on a non-INR settlement, which on a domestic-BIN INR transaction is zero legitimate cost) — recoverable in full where present
The fee-adjustment request goes to the acquirer with the per-transaction exception list as the documented basis. The MDR over-charge is reversed via credit note; the GST on the over-charge is reversed via the corresponding GST adjustment in the supplier’s invoice; the forex line, where applied, is reversed in full.
The brand also asks the acquirer to refresh its BIN registry on the network’s published cadence and to acknowledge in writing the BIN-classification policy for unrecognised BINs. The structural fix — newer Indian BINs correctly classified at issuance — eliminates the leakage going forward.
The recovered amount on a single Rs 2 crore monthly book is modest in absolute terms, around Rs 90,000 a year including GST. The same audit on a Rs 20 crore monthly book recovers roughly Rs 9 lakh annually. Pattern #3 scales linearly with card volume.
Detection technique: the per-transaction BIN audit
The discipline that catches this pattern repeatably is a monthly per-transaction BIN audit fed by the settlement file extract.
Step one, extract per-transaction settlement data with the BIN field exposed. If the gateway’s standard report does not include BIN, request the per-transaction CSV. Every Indian PA can produce one.
Step two, maintain a current issuer-country registry. The networks publish BIN ranges with issuer and country; an internal table refreshed monthly from those publications is sufficient. For BINs not yet in the registry, mark them as “pending classification” rather than defaulting to international — this prevents the merchant from carrying the acquirer’s fallback cost as an audit miss.
Step three, run two deterministic checks on every row. Check one: where the BIN-country is IN, the applied MDR rate must equal the contracted domestic rate within a small tolerance, and the forex amount must be zero. Check two: where the BIN-country is not IN, the applied MDR rate may be the contracted international rate, and a forex line is permissible. Both checks fail loudly into an exception queue.
Step four, aggregate the exceptions monthly into a recoverable amount, raise the fee-adjustment request with the acquirer, and feed the recovered amount back to the books as a fee-line credit. Where the acquirer refuses, the merchant has documented per-transaction evidence — every individual row, the BIN, the assigned scope, the applied rate, the contracted rate, the over-charge — which makes the dispute auditable and the resolution faster than the gateway’s preferred opaque “we will review and revert” path.
The same per-transaction discipline catches the rest of the merchant-fee leakage stack: premium and commercial cards routed to the wrong slab, MDR not reversed on refunds, recurring add-on fees stacked on the base rate, and zero-MDR instruments billed at non-zero MDR. None of those are visible in a blended dashboard; all of them are deterministic at per-transaction grain.
How much are domestic-BIN mis-classifications costing your book?
Model your monthly card GMV, the share you suspect is being mis-scoped, your contracted domestic rate and the international slab being applied. The calculator returns the monthly and annual recoverable MDR, separates the GST line, and quantifies the forex over-charge alongside.
Open the MDR Effective-Rate Calculator →Continue reading in this cluster
- MDR fee reconciliation guide — cornerstone overview of verifying gateway charges against contracted rates by instrument and network
- RuPay debit vs Visa/Mastercard debit MDR — the network-routing lever that sits alongside BIN-tier audits in the merchant-fee playbook
- RBI 2017 debit-card MDR cap — the regulatory ceiling that anchors every debit MDR audit
- Cluster hub: Merchant fees and MDR leakage
- Money page: Payment gateway reconciliation