Small businesses reviewing UPI merchant charges in 2026 should separate three things: the customer’s payment, the merchant’s classification and the amount finally settled into the business account. A forwarded fee chart cannot tell you whether your own settlement is correct.
This guide explains the Ministry of Finance clarification dated 15 September 2026 and offers a bookkeeping workflow for checking deductions. Research was checked on 30 October 2026. Confirm the current rules and your classification with your bank or payment provider before making a business decision.
What the September clarification says
The official clarification says person-to-person UPI transfers remain free regardless of amount. Merchant payments up to ₹2,000 remain free of MDR, as do payments covered by the small-merchant zero-MDR framework. It identifies small merchants receiving up to ₹1 lakh monthly through the P2PM category as protected by that framework.
For specified merchant transactions above ₹2,000, the release describes an MDR framework with category-specific treatment. It states that customers do not pay MDR and that merchants should not pass it on to them. It also distinguishes security-related transaction limits from charging thresholds. Read the full release for the applicable rates and exceptions rather than treating every business payment identically. Source: Ministry of Finance clarification, 15 September 2026.
These are statements from the release, not an assessment of your account. The practical next step is to obtain the classification and settlement explanation for the business actually receiving the payment.
Ask the provider four precise questions
“Why was money deducted?” is understandable, but a more structured request is easier to resolve. Ask the bank or provider to identify the merchant category assigned to your account, the applicable current schedule, the transaction to which a deduction relates and where that deduction appears in the statement.
Do not guess your category from the size of the shop or the colour of a QR code. Keep the provider’s written answer with your business records. If the explanation refers to a notification, ask for the current official document and its effective date.
Also separate payment-processing treatment from other products you may have contracted for. A device subscription or a separately agreed business service should not disappear into a generic “UPI fee” label in your own accounts. Ask what each line item pays for and which agreement authorizes it.
Our suggested request is: “Please confirm our merchant classification, identify the transaction references behind these deductions, and provide the current schedule and effective date. Please distinguish processing deductions from other contracted services.” This is an enquiry template, not a legal notice or an allegation of wrongdoing.
Build a settlement ledger that answers one question
The main question is whether each successful customer payment can be traced to a settlement or a documented exception. A simple ledger is often more useful than a screenshot folder with no transaction references.
Record the transaction date, business receipt number, payment reference, gross amount, settlement reference, settled amount and any separately explained deduction. Add a status field such as matched, pending, refunded or disputed. Keep access limited to people who need the records.
For a hypothetical café, a customer’s ₹850 payment may be recorded on Monday and appear within a later settlement batch. Matching only the daily bank total can make that look missing when it is merely grouped differently. The ledger should preserve the connection between the individual payment and its batch.
This example does not establish a settlement timeline. Use the provider’s actual schedule. The point is to avoid treating a timing difference as a charge or treating an unexplained difference as normal simply because the daily total is close.
Reconcile in a repeatable order
- Begin with successful transactions shown in the official merchant record, not just a customer’s screenshot.
- Match those references to receipts or invoices in your own system.
- Match the transactions to the provider’s settlement report and then to the bank credit.
- List exceptions separately: timing differences, refunds, failed payments and unexplained deductions.
- Request an explanation for exceptions with the relevant references and amounts.
- Mark an item resolved only when you have evidence of the settlement, refund or valid adjustment.
Do this at a frequency appropriate to the business’s volume. A quiet shop and a high-volume seller need different routines. What matters is that the same person can follow the chain without relying on memory.
Retain the original reports rather than editing them to make totals agree. Use your ledger to explain adjustments. If a customer refund is involved, follow the provider’s process and your accounting procedure; do not make a second payment merely because an unfamiliar caller says the first one failed.
Train staff to describe the issue accurately
Front-desk staff should not have to interpret financial policy during a queue. Give them a short procedure for confirming a payment in the merchant system and escalating a mismatch. Avoid instructing them to add an improvised surcharge to cover an unexplained deduction.
A clear customer message might be: “We are checking the transaction reference in our merchant records.” That is more accurate than declaring the bank has charged the customer or that the payment has vanished before the records are reviewed.
When escalating internally, include only the information needed to resolve the payment. Full bank statements, customer identity documents and unrelated transactions should not be sent through an informal group chat as a default.
Keep the public-facing payment process understandable. If your business uses several QR codes or providers, label them clearly for staff. The reconciliation problem often starts when nobody can tell which account received a particular transaction.
Review the economics without blaming the payment method
Once deductions are understood, evaluate payment costs alongside the rest of the business. A meaningful review considers transaction mix, operational effort and separately contracted services. Do not compare two providers using one unexplained settlement as if it represented the whole month.
Create a short monthly note: which exceptions repeated, which took longest to resolve, whether staff needed extra training and whether the provider’s statements were clear. This turns a confusing deduction into an operational improvement rather than a recurring argument.
For broader planning, explore Business coverage and our Finance & Stock Market explainers. To suggest a correction to this guide, contact BuzzyBanana with the relevant official source.
Questions business owners often ask
Does the clarification say every UPI payment attracts MDR?
No. It distinguishes person-to-person transfers, merchant thresholds, protected small-merchant payments and specified chargeable categories. Read the full current rules and confirm your classification.
Is a transaction limit the same as a charging threshold?
No. The release expressly separates security and risk-management limits from charging thresholds. A limit shown in an app does not by itself explain a settlement deduction.
What should I do with a deduction I cannot explain?
Keep the original records, identify the affected references and request the applicable basis in writing. If the answer is incomplete, follow the bank or provider’s published escalation process rather than inventing an explanation in your accounts.
Source and scope
The ledger structure, examples and staff procedure are BuzzyBanana’s original operational suggestions. This article does not determine an individual merchant’s eligibility or provide accounting or legal advice.
