Urgent.News

What's breaking now, across hundreds of outlets.

Tech

Building UPI Payments Into Your App in 2026: What Razorpay, Cashfree, PayU and Autopay Actually Cost You

If you're wiring UPI into an Indian app right now, the engineering decisions you make this month will hit your margins differently after October 15, 2026, when NPCI's new 0.4% MDR on UPI P2M transactions above ₹2,000 kicks in. Here's the developer-level version of what changed and what it means for how you build. The gateway layer itself hasn't changed much — Razorpay, Cashfree and PayU all still…

If you are integrating UPI into an Indian app right now, engineering decisions made this month will affect your margins after October 15, 2026, when NPCI's new 0.4% MDR on UPI P2M transactions above ₹2,000 comes into effect. Razorpay, Cashfree and PayU's gateway layer remains largely unchanged - they all still charge roughly 2% plus GST for card transactions, have zero setup fees and zero MDR on UPI.

However, there's a new factor to consider on the backend: which MDR bucket each transaction falls into. The options are standard P2M with a 0.4% fee (capped at ₹300 on high-value tickets), sector flat fees for certain industries, capital markets transactions (0.02%), or small merchants exempt from MDR (such as static QR codes with monthly volumes under ₹1 lakh).

This requires updating your transaction schema to include a category field. For recurring billing, the real engineering challenge isn't the MDR change itself - it's implementing UPI Autopay (UPI 2.0), NPCI's e-mandate framework. This involves creating mandate flows, handling pre-debit notifications, implementing retry logic for failed executions due to insufficient balance, and managing mandate revoke/pause states.

These functionalities are priced separately from one-time Collect or Intent transactions (Cashfree quotes roughly ₹7.50 per mandate creation and ₹5-15 per execution depending on ticket size). The integration effort breaks down into three tiers: a basic single-gateway UPI Collect/Intent checkout can be built in 1-2 weeks; adding a second PSP for failover and Autopay mandates takes 3-5 weeks; going full Payment Aggregator with direct bank certification and multi-bank switch failover requires 2-4 months.

The actual timeline depends on your existing backend, team size and how much automation you implement in reconciliation. For a detailed cost breakdown with INR figures and a decision framework to determine which tier best fits your app's transaction profile, refer to "UPI Payment Gateway Integration Cost for Indian Apps in 2026".

Rewritten by urgent.news; may contain errors — check the original.

Source: dev.to

Read the original at dev.to →

Report a problem with this story

More in Tech

Frappe / ERPNext v16.50: The Future of Desktop Icons and Desk Navigation

What “retiring” really means, what changed in v16.50, and how custom apps should prepare By Mohamed Hamed ( @m7amedenho ) Published: October 2026 Frappe Framework and ERPNext v16.50 introduce a…

  • Frappe Framework and ERPNext v16.50 introduces new navigation model for Desk.
  • Existing sites will continue using Desktop Icon grid temporarily during migration.

More from Thursday 8 October →