For six years, accepting a UPI payment cost a merchant nothing. That era has ended in part. From 15 October 2026, a Merchant Discount Rate applies to selected UPI merchant payments, and the rollout is now live. These UPI Merchant Fees introduce new considerations for businesses handling digital transactions. If you run a payment app, an aggregator, a checkout stack or a business that takes UPI at scale, UPI MDR 2026 is no longer a policy debate. It is a product, engineering and finance backlog.

This guide explains what the new framework says, who is affected, and the specific changes that apps, aggregators and merchants need to make. It also covers how fintech app development in India is changing as teams rebuild fee engines, reconciliation and reporting around the new rules.

UPI MDR 2026 in 60 seconds

The government notified the zero-MDR threshold on 14 September 2026, and NPCI followed with an operational circular and FAQs on 15 September. The key points:

• Standard rate: 0.4% MDR on eligible person-to-merchant (P2M) UPI payments above ₹2,000.
• Cap: for payments of ₹75,000 and above, MDR is capped at ₹300 per transaction.
• Still free: all person-to-person (P2P) transfers, merchant payments up to ₹2,000, and UPI AutoPay or mandate-based recurring payments.
• Small-merchant protection: street vendors and small merchants under the P2PM category, receiving up to ₹1 lakh a month, stay at zero MDR.
• Flat ₹5 categories: for payments above ₹2,000 in categories such as railways, telecom, insurance, fuel and public utility bills, MDR is a flat ₹5 rather than 0.4%.
• Capital markets: mutual fund and securities payments follow a separate structure, reported at 0.02% with a ₹300 cap.
• No customer charges: UPI apps cannot levy platform fees or hidden charges, and merchants are not supposed to pass MDR on to buyers.
• Small-merchant fund: 5% of total MDR collections goes to a dedicated fund to support merchant onboarding and UPI adoption among small businesses.

In practice, a ₹3,000 eligible payment carries ₹12 of MDR, a ₹25,000 payment carries ₹100, and a ₹50,000 payment carries ₹200. The government’s own estimate is that only about 4% of merchant transactions will attract MDR, so most everyday small-ticket payments are untouched. The exposure sits in high-ticket categories: electronics, jewellery, furniture, education fees, travel bookings, B2B payments and event ticketing.

Note: figures above come from the government notification, the NPCI circular and press coverage as of early November 2026. Always confirm rates, category lists and effective dates against the latest NPCI circular before changing production systems.

Why this matters beyond the headline

Zero MDR made UPI the default way to pay in India, but it left everyone downstream with costs and no revenue. Banks, payment service providers (PSPs), third-party app providers and aggregators carried the infrastructure, fraud and support burden of a system processing hundreds of trillions of rupees a year, with little direct income from merchant payments.

The new framework is designed to share a modest fee across the chain. Reporting on the circular indicates that of the 0.4% standard MDR, about 0.28% goes to the customer’s issuing bank as interchange and about 0.08% goes to the UPI app provider through the payer-side PSP. The rest, along with the 5% small-merchant fund, is distributed among other participants as set by the UPI Steering Committee.

For product and engineering teams, the key shift is this: UPI is no longer a single, flat, free payment rail. It now has thresholds, categories, caps and exemptions that must be evaluated per transaction, in real time, and then reflected in settlement, invoicing and reporting.

What payment apps (TPAPs and PSP apps) must change

Apps that sit on the payer side feel the change differently from those on the merchant side. They are barred from charging users, but they are part of the MDR distribution chain, so their systems still need to handle the new classification logic.

1- Remove or audit every consumer-facing fee. The framework prohibits UPI apps from charging platform fees or similar charges. Review any convenience fee, “processing” fee or bundled surcharge in your UI and backend. Anything that looks like a fee on a UPI payment is now a compliance risk.

2- Make P2P vs P2M vs P2PM classification airtight. The whole regime hinges on correctly identifying whether a payment is a person-to-person transfer, a person-to-merchant payment or a P2PM payment to a small merchant. Misclassifying a P2P transfer as P2M, or a small-merchant payment as a standard merchant payment, creates both regulatory and trust problems. Review how your app reads merchant codes, QR payloads and VPA types.

3- Handle threshold and category logic. The ₹2,000 threshold, the ₹75,000 cap and the flat ₹5 categories all depend on transaction amount and merchant category. Your apps and APIs should pass the right metadata so downstream systems can price the transaction correctly.

4- Keep customer messaging clean. Users should see the price they were quoted and nothing more. Update receipts, payment confirmation screens and support scripts so customers are not confused about whether they were charged. If a merchant tries to add a surcharge, your support flow should know how to respond.

5- Plan for the new revenue line. If your app receives a share of MDR as the app provider, finance and data teams need visibility into accrual, settlement cycles and dispute treatment. This revenue needs its own reporting, not a spreadsheet workaround.

What payment aggregators and gateways must change

Aggregators carry the heaviest operational load, because they sit between merchants, acquiring banks and NPCI rails, and they are the ones who will actually bill merchants.

1- Build a real-time MDR calculation engine. Pricing can no longer be one flat rate for UPI. The engine needs to evaluate amount, merchant category, merchant tier (including P2PM exemptions), and special categories like capital markets, then return the correct fee and the split between participants.

2- Update merchant onboarding and contracts. Merchants now need to be classified at onboarding, and their pricing plans, caps and exemptions need to be reflected in agreements and dashboards. Merchants who were told “UPI is free” need clear communication on what changes and when.

3- Rework settlement and reconciliation. Net settlement amounts will now differ from gross payment amounts for eligible transactions. Reconciliation must match the gross payment, the MDR deducted, the GST on that MDR, and the net credit, per transaction and in aggregate. Failed, reversed and partially refunded payments need clear rules on whether MDR is reversed.

4- Fix invoicing and GST handling. MDR is a service charge, and GST applies on it. Merchants will expect monthly tax invoices that let them claim input credit where eligible. Your billing system should generate clean invoices and align with GSTR filings. Merchants should confirm treatment with their chartered accountant.

5- Prepare for the small-merchant fund. The fund is intended to support acquiring banks and aggregators in onboarding small merchants. Aggregators should track eligible merchants and volumes so they can claim support correctly if and when the mechanism is operational.

6- Stress-test performance and observability. Fee logic adds computation to the payment path. Load test it at peak festival volumes, add monitoring on fee mismatches, and keep an audit trail for every pricing decision.

What merchants must change

Most small merchants will see no difference. Mid-size and large businesses with high-ticket sales need to act now.

1- Model the real cost. Take your last three months of UPI sales, filter payments above ₹2,000, and apply 0.4% (or the flat or capped rate for your category). That is your new monthly cost. For some businesses it will be small; for high-ticket retailers and B2B sellers it can be material.

2- Do not surcharge customers. The framework says merchants cannot pass MDR on to buyers, and apps are barred from adding fees. Raise prices through normal pricing strategy if you must, but do not add a UPI line item.

3- Update your accounting. Record MDR as an operating expense, track GST on the MDR for input credit where eligible, and make sure your books reflect net settlement, not gross sales, in your bank statements.

4- Renegotiate and compare. Pricing, settlement speed, refund treatment and support quality will vary across aggregators now that UPI has a price. Compare quotes rather than assuming every provider charges the same.

5- Consider your payment mix. Cards, wallets, net banking and UPI now have different cost profiles. Credit card MDR typically runs higher than UPI, so UPI still looks competitive for many categories, but the gap has narrowed. Smart checkout design can offer the best option for each basket size without hurting conversion.

6- Check your systems. If you run your own billing, ERP or point-of-sale software, confirm it can record gross amount, MDR, GST and net settlement as separate fields. Many legacy systems record only one number.

The technology gap: why custom builds are back on the roadmap

Off-the-shelf checkout tools will add basic support, but businesses with complex needs are finding gaps. Multi-category catalogues, marketplace payouts, split settlements, B2B invoicing and subscription models do not fit neatly into a single flat-fee assumption.

This is where specialist fintech app development in India teams are being pulled in. The work typically includes:

• Fee and rules engines that classify transactions and calculate MDR in real time, with rules that can be updated without a full release.
• Reconciliation and settlement modules that match gross, fee, tax and net amounts across gateways, banks and ledgers.
• Merchant dashboards that show exactly what was charged, why, and what the GST impact is.
• Admin and compliance panels with audit trails, configurable limits and exportable reports.
• Payment gateway and bank API integrations that pass the right metadata for classification.
• Fraud and risk monitoring, since higher-value payments are exactly where fraud controls matter most.

Algosoft’s fintech app development company in India page outlines the building blocks, from payments and wallets to KYC, compliance workflows and bank connectivity. If your payment product needs a fresh architecture rather than a patch, a focused custom software development engagement is usually faster than stretching a legacy stack.

Industry-specific impact

E-commerce and marketplaces. High-ticket categories and split payouts to sellers need MDR-aware settlement. A purpose-built e-commerce marketplace platform can bake fee calculation, seller payouts and reporting into the core flow instead of bolting them on.

B2B and distribution. Dealer and distributor orders often exceed ₹2,000 by a wide margin. A dealer ordering platform that records MDR, GST and net settlement per order keeps finance teams out of spreadsheets.

Food delivery and local services. Most baskets fall below the threshold, but group orders, catering and premium services can cross it. A food delivery app or a handyman booking system should handle both cases cleanly.

Events and ticketing. Bulk and premium tickets frequently cross ₹2,000. An event ticketing and venue booking platform needs fee-aware checkout and refunds.

SaaS and subscriptions. Recurring payments through UPI AutoPay stay outside MDR, which makes mandate-based billing attractive. Teams building SaaS products should review whether their billing flow can use mandates where it fits.

How AI and data can help

The new rules create data problems that automation handles well.

• Machine learning solutions can flag unusual high-value payments, detect misclassified merchants and predict monthly MDR cost by merchant segment.
• Data engineering and AI pipelines keep gateway, bank and ledger data clean enough for automated reconciliation.
• AI chatbots and virtual assistants can answer merchant questions such as “why was this settlement lower?” without raising a support ticket.
• Generative AI development can turn dense circulars into plain-language merchant communications and internal runbooks.

AI should support, not replace, deterministic fee logic. The calculation of MDR must be rule-based and auditable. Use AI around it for detection, explanation and forecasting.

A 30-60-90 day action plan

First 30 days: understand and map.

• Read the NPCI circular and FAQs line by line.
• Map every UPI flow in your product: P2P, P2M, P2PM, mandates and refunds.
• Pull three months of data to quantify how much volume crosses ₹2,000 and which categories it falls in.
• Audit consumer-facing screens for any fee language.

Days 31 to 60: build and test.

• Implement the fee engine with thresholds, caps, flat categories and exemptions.
• Update settlement, reconciliation and invoice generation.
• Create test cases for edge cases: exactly ₹2,000, exactly ₹75,000, partial refunds, failed payments and category changes.
• Update merchant agreements, dashboards and support scripts.

Days 61 to 90: launch and monitor.

• Roll out in stages, starting with a pilot merchant group.
• Monitor fee mismatches, settlement disputes and support tickets daily.
• Review pricing and mix with finance, and refine communication with merchants.
• Prepare for further circular updates, since category lists and operational details may be refined.

Common mistakes to avoid

1. Treating MDR as a flat 0.4%. The threshold, cap, flat categories and exemptions all matter.
2. Hardcoding rates. Rules will evolve. Use configurable rule tables, not constants buried in code.
3. Ignoring refunds. Decide and document how MDR behaves on full and partial refunds.
4. Forgetting GST. Fee invoices and tax credit are where finance teams feel the most pain.
5. Surcharging customers. It is prohibited and will damage trust quickly.
6. Leaving merchants in the dark. Silence creates disputes. Communicate early, with worked examples.

Frequently asked questions

Is UPI MDR applicable from October 2026? 

Yes. The framework took effect on 15 October 2026 for selected P2M transactions above ₹2,000.

Do customers pay anything extra? 

No. MDR is a merchant-side charge. UPI apps cannot add platform fees, and merchants are not supposed to pass the fee on to customers.

Are P2P UPI transfers still free? Yes, regardless of amount.

Is UPI AutoPay charged MDR? 

No. Mandate-based recurring payments remain outside MDR under the framework.

What is the maximum MDR on a single UPI payment? 

For payments of ₹75,000 and above, MDR is capped at ₹300 per transaction under the standard structure. Capital-market payments have their own cap.

How much of UPI will actually be charged? 

Government estimates suggest around 4% of merchant transactions will attract MDR, so the large majority of everyday payments remain free.

Should we build custom software or use our existing gateway? 

If your payments are simple, your gateway may be enough. If you run marketplaces, split payouts, B2B invoicing or multi-category pricing, a custom or hybrid build usually pays off.

Conclusion: UPI is still the best rail, but it now needs better software

UPI MDR 2026 does not end the UPI story. It matures it. Most users and small merchants are protected, and a modest fee on higher-value merchant payments is meant to make the system sustainable for the banks, PSPs and apps that run it. But the transition moves complexity into software: classification, pricing, settlement, tax and communication.

Teams that treat this as a checkbox will spend the next year patching support tickets. Teams that treat it as a product opportunity will ship cleaner checkouts, clearer merchant dashboards and smarter payment routing.

If you are planning payment features, a new wallet, an aggregator platform or a merchant-facing dashboard, talk to a team that builds regulated payment products every day. Explore Algosoft’s fintech app development services, browse case studies, hire dedicated developers, or book a free consultation to scope your UPI MDR readiness plan. For more practical guides, visit the Algosoft blog.