Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
Indian merchants treat UPI as a single zero-MDR rail and so do not reconcile interchange on its sub-rails. PPI/wallet-on-UPI carries 0.5%-1.1% interchange on tickets above ₹2,000 (NPCI circular 24 March 2023, effective 1 April 2023) yet the deduction lands under the generic UPI parent in the settlement file, hiding the cost. As wallet-on-UPI mix grows in D2C, food delivery, and OTT cohorts the unbilled-looking deduction accumulates materially.
Reconciliation splits the UPI parent bucket into three children — bank-account UPI (zero interchange), RuPay-credit-on-UPI (~2% above ₹2,000), and PPI/wallet-on-UPI (0.5%-1.1% above ₹2,000) — using the payment-instrument sub-type field exposed in the gateway settlement payload. Each child has its own expected interchange schedule keyed on ticket size and merchant category code; the engine recomputes the expected deduction per transaction and raises a variance when actual deviates from expected.
Rail-split rule on the UPI parent method using the instrument sub-type field; interchange-schedule table keyed on rail + merchant category code + ticket band (NIL ≤ ₹2,000, 0.5%-1.1% above ₹2,000); UPI_INTERCHANGE variance class with tolerance threshold; refund-interchange-retention flag to detect cases where wallet interchange was not reversed on a refunded transaction; monthly GST-invoice matcher to GSTR-2B for the 18% ITC line.
A per-transaction wallet-on-UPI interchange variance report with recoverable over-charges, a rail-mix dashboard tracking bank-account vs RuPay-credit vs PPI share month-on-month for CFO visibility, refund-interchange retention exceptions for gateway support tickets, and an ITC-claim schedule for the 18% GST on interchange.
A D2C personal-care brand running ₹6 crore monthly GMV at a 70% UPI mix typically sees wallet-on-UPI grow from low-single-digit share to nearly 10% over eighteen months as PhonePe wallet, Paytm wallet, MobiKwik, and Amazon Pay all push their loyalty and cashback features inside the UPI rail. The brand’s CFO sees a stable “UPI” deduction line on the gateway statement and concludes the rail is still zero-cost. The actual interchange leakage is on the order of ₹40,000 per month, growing — and it never appears as its own line in the gateway dashboard until somebody splits the UPI bucket by instrument sub-type.
This article walks through the rule, the worked numbers, and the reconciliation discipline that surfaces it.
Quick-Reference: PPI / Wallet-on-UPI Interchange
| Aspect | Detail |
|---|---|
| Instrument | Wallet / Prepaid Payment Instrument (PPI) on UPI, P2M |
| Interchange band — at or below ₹2,000 | NIL (0%) |
| Interchange band — above ₹2,000 | 0.5% to 1.1% (merchant-category dependent) |
| Effective date | 1 April 2023 |
| Source circular | NPCI wallet-interoperability circular dated 24 March 2023 |
| Wallet-loading fee | 15 bps (0.15%) above ₹2,000 — borne by PPI issuer, NOT merchant |
| Customer charge | None — customer pays no extra |
| GST on interchange | 18% on the fee only (not on transaction value); separate line |
| Where it lands in settlement | Under the parent “UPI” rail in most gateway files — needs sub-type split to surface |
| Regulator | NPCI under RBI’s PPI Master Direction framework |
What Exactly Did the 24 March 2023 Circular Change?
Until early 2023, PPIs (mobile wallets like Paytm, PhonePe wallet, MobiKwik, Amazon Pay, Freecharge) and bank-account UPI lived as two separate rails. A customer paying from a Paytm wallet to a merchant happened on the closed Paytm loop, and a customer paying from an ICICI bank account via UPI happened on the open NPCI rail. The wallet rail was not interoperable: a PhonePe wallet could not pay a merchant onboarded only on the Paytm acquiring side, and the merchant economics differed materially from UPI.
The NPCI circular dated 24 March 2023 changed two things effective 1 April 2023. First, it formally permitted PPIs to ride on the UPI rail in an interoperable fashion — meaning any UPI-accepting merchant could now receive a wallet payment from any wallet operator, all flowing through NPCI’s UPI switch. Second, because the PPI issuer now incurs real cost in this flow (it must fund the wallet from the customer’s bank account and bear the cost of holding float), the circular introduced an interchange fee on PPI merchant transactions above ₹2,000 ranging from 0.5% to 1.1% depending on the merchant category. Transactions at or below ₹2,000 carry NIL interchange.
The same circular separately introduced a 15 bps (0.15%) wallet-loading fee above ₹2,000, but this is paid by the PPI issuer to the customer’s bank when the wallet is loaded — it never touches the merchant. It is mentioned here only because it is the most common source of confusion in internal-audit notes.
Customer-side disclosure was unchanged: the consumer pays no additional fee at checkout and sees no charge on their statement.
Why Does It Not Show Up Clearly on the Gateway Settlement?
Most Indian gateway settlement files — Razorpay, PayU, Cashfree, PhonePe PG, Juspay, Paytm PG — use a two-level taxonomy for the payment method: a parent rail (UPI, Card, NetBanking, Wallet, EMI) and an instrument sub-type. For UPI, the parent stays “UPI” regardless of whether the funding source was a bank account, a RuPay credit card on UPI, or a PPI. The sub-type field — variously called wallet, provider, instrument_detail, vpa_handle, or bank — is what distinguishes the three.
If a reconciliation engine groups deductions by the parent rail only, all UPI deductions get bundled into one cell, and the visible MDR/interchange figure is a blended average that hides the wallet-on-UPI cost. The same issue affects the RuPay-credit-on-UPI deductions, which carry roughly 2% above ₹2,000 — see the dedicated RuPay-credit article in this cluster for that walkthrough.
The fix is structural: the rail-split rule on the UPI parent needs to fire on the sub-type field, producing three children — bank-account UPI, RuPay-credit-on-UPI, and PPI/wallet-on-UPI — each of which is reconciled against its own interchange schedule. This is straightforward in NPCI’s UPI 2.0+ payload schema, and every major Indian gateway exposes the sub-type field in either the settlement API response or the settlement webhook payload.
For context on how this fits into the broader gateway-fee verification routine, see the MDR fee reconciliation walkthrough — wallet-on-UPI interchange is a specialised variance class within that workflow.
How Big Does This Get for a Real D2C Brand?
Consider a personal-care D2C brand running ₹6 crore monthly GMV. UPI accounts for 70% of payment-method mix, which is consistent with what most apparel/beauty/personal-care D2C brands see post-2024 as cards have steadily lost share to UPI for sub-₹5,000 baskets.
Within UPI, the typical split for a growing 2026-cohort D2C brand is:
- Bank-account UPI: 88% of UPI volume — zero interchange
- Wallet-on-UPI (Paytm, PhonePe wallet, MobiKwik, Amazon Pay): 9% of UPI volume — interchange-bearing
- RuPay-credit-on-UPI: 3% of UPI volume — interchange-bearing at ~2% above ₹2,000
Working the wallet-on-UPI cost:
- Wallet-on-UPI monthly volume: ₹6 crore × 70% × 9% = ₹37.8 lakh
- Approximate share above ₹2,000 ticket: ~95% (D2C average order value typically ₹2,200-₹2,800)
- Interchange-bearing volume: ₹37.8 lakh × 95% = ₹35.91 lakh
- Interchange at 1.1%: ₹35.91 lakh × 1.1% = ₹39,501 per month
- Annual interchange cost: ₹39,501 × 12 = ₹4.74 lakh
To this add 18% GST as a separate line (recoverable as Input Tax Credit if the brand is GST-registered) and the same calculation for the RuPay-credit-on-UPI sub-rail, which compounds because RuPay-credit interchange runs ~2% above ₹2,000.
The ₹4.74 lakh annual figure is small relative to the brand’s revenue but material relative to its EBITDA margin. More importantly, it is invisible — the CFO sees “UPI” on the gateway statement and assumes zero cost. As the wallet-on-UPI mix grows (and it has grown in every D2C cohort tracked since Q3 2024), the unflagged deduction grows with it.
Calculate your effective rate per rail, including wallet-on-UPI
Enter your monthly GMV, UPI mix, and the wallet-on-UPI share — the calculator decomposes the blended UPI MDR into bank-account, RuPay-credit, and PPI sub-rails, applies the NPCI interchange schedule per band, and outputs the rupee-level fee you are paying on each. Useful for D2C, OTT, and food-delivery CFOs validating their gateway statements.
Open the MDR Effective-Rate Calculator →Detection Routine: How Do You Surface the Leakage?
The reconciliation discipline has four moving parts and can be implemented in any mature reconciliation tool or a well-structured spreadsheet. The objective is to produce a per-transaction expected interchange figure and a variance against the actual deduction.
Step 1 — Pull instrument sub-type into the reconciliation key. The settlement file must surface the sub-type, not only the parent rail. For Razorpay this is in the payment.method_details payload; for PayU it is the payment_source field; for Cashfree it is exposed in the settlement-webhook payment_method.instrument block; for PhonePe PG and Paytm PG it is in the paymentInstrument.type field. Build the recon key as (parent rail, sub-type, ticket band) — band being “at or below ₹2,000” vs “above ₹2,000”.
Step 2 — Maintain an interchange-schedule table. A small lookup keyed on (rail, sub-type, merchant-category, band) with the expected interchange rate. Sample rows: (UPI, bank-account, any, any) → 0%; (UPI, wallet-on-UPI, any, ≤ ₹2,000) → 0%; (UPI, wallet-on-UPI, retail-D2C, > ₹2,000) → 1.1%; (UPI, wallet-on-UPI, education, > ₹2,000) → 0.5%; (UPI, rupay-credit, any, > ₹2,000) → 2.0%. The merchant-category-specific rates are NPCI-defined; cross-reference your acquirer’s contract.
Step 3 — Raise a UPI_INTERCHANGE variance on mismatch. For every transaction, compute the expected interchange (expected_rate × transaction_value), compare to the actual deduction recorded in the settlement file, and raise a variance if the difference exceeds a small tolerance threshold (₹1 or 0.05%). Variances cluster into three patterns: (a) wallet-on-UPI billed at the wrong slab — likely a contracted-rate-mismatch ticket with the acquirer; (b) wallet-on-UPI interchange not reversed on a refunded transaction — see Step 4; (c) bank-account UPI showing a non-zero deduction, which is a clear billing error.
Step 4 — Flag refund-interchange retention. When a transaction is refunded, the interchange should typically be reversed alongside the principal. Some gateway settlement flows fail to reverse the interchange line, leaving the merchant with a permanent cost on a transaction that did not stick. The reconciliation should match every refund event against the original transaction’s interchange line and raise an exception when reversal is missing — these are recoverable through a dispute.
This discipline turns wallet-on-UPI interchange from an invisible blended cost into an itemised, defensible variance log that supports both internal CFO reporting and acquirer-side fee disputes.
What About the 15 bps Wallet-Loading Fee?
The 24 March 2023 circular also introduced a 15 bps (0.15%) wallet-loading fee on transactions above ₹2,000 — but this fee is borne by the PPI issuer (the wallet operator), not the merchant. Specifically, when a customer loads their PhonePe wallet from an ICICI bank account to make a ₹3,000 payment, PhonePe pays 0.15% of ₹3,000 = ₹4.50 to ICICI as a wallet-loading fee. The merchant never sees this line item.
This is worth being explicit about because internal-audit notes and merchant-side advisory documents occasionally cite the 15 bps as a merchant cost stacking on top of the 1.1% interchange. It does not. The two fees are economically distinct: interchange is paid by the merchant to fund the issuer-side cost of the consumer transaction; the wallet-loading fee is paid by the PPI issuer to the remitting bank to fund the float that backs the wallet balance. The aggregate cost to the merchant is the interchange line only — 0.5% to 1.1% above ₹2,000.
For full regulatory context on PPI economics, see the NPCI’s published circulars on UPI and wallet interoperability — they are the primary source for the rate schedule that gateways implement downstream.
Continue Reading in This Cluster
The wallet-on-UPI interchange article is one of a series on Indian payment-rail fee leakage. To go deeper:
- MDR fee reconciliation against contracted gateway rates — the parent workflow that splits every deduction in a gateway statement against the contracted rate schedule by instrument type. Wallet-on-UPI interchange is one variance class within this.
- UPI settlement reconciliation walkthrough — the broader UPI settlement reconciliation routine, including the sub-rail split and the credit-debit matching pattern for refunds.
- Cash-to-bank reconciliation across UPI and POS — how the UPI bucket reconciles back to the bank statement and how wallet-on-UPI interchange interacts with the credit-side principal.
For the cluster index covering every Indian merchant-fee leakage pattern — premium cards, Amex/Diners, EMI, international cards, RuPay-credit-on-UPI, refund retention, GST on MDR, and more — visit the merchant-fees insights hub. And for the operating money page describing the gateway-fee reconciliation workflow end-to-end, see payment gateway reconciliation.