NPCI Makes UPI AutoPay Portable: 7 Big Changes to Know

India's digital payments system just took a major leap forward. The National Payments Corporation of India (NPCI) has upgraded UPI AutoPay. Standard UPI payments for shops have always worked across all apps. However, recurring AutoPay setups remained locked inside the specific app where you created them.

Imagine you use one UPI app to pay for your monthly Netflix subscription, life insurance premium, and mutual fund SIP. If you wanted to switch to a different UPI app, you faced a big problem. You had to manually cancel every single recurring payment in the old app. Then, you had to set them all up again in the new app.

UPI AutoPay Portability changes this completely. It separates your automatic payments from any single app. Now, recurring mandates are portable. You can view, manage, and move your active mandates across supported UPI apps. You do not have to cancel or restart them.

Important Note on Availability: While NPCI has announced this interoperability framework, it is not universally available right now. Technical implementation by participating banks and apps is ongoing. Not all apps support the migration feature yet. Not all mandate types are eligible today. Do not assume an official framework announcement means a completed rollout across every single app.

How to Move a UPI AutoPay Mandate to Another App

If your apps and bank support the new framework, moving a mandate is simple. Follow these verified steps to migrate an active recurring payment.

1. Open the Destination App: Launch the new UPI app where you want to move your payments.
2. Find the AutoPay Section: Navigate to the app's settings or profile area. Look for a section named "Manage AutoPay," "Recurring Payments," or "Mandates."
3. View Active Mandates: The new app will fetch a list of all your active mandates linked to your bank account. It does this by communicating directly with the central NPCI registry.
4. Select the Mandate to Move: Tap on the specific subscription or SIP you want to migrate.
5. Initiate the Transfer: Look for a button that says "Transfer to this App" or "Port Mandate."
6. Authenticate with UPI PIN: This is the crucial security step. You must enter your secret UPI PIN to authorize the move. This proves you are the account owner.
7. Confirm Migration: Once the PIN is verified, the mandate moves to the new app. Future debits will be managed from this interface.

Mandate Compatibility Matrix

Not all recurring payments are treated equally right now. Here is a breakdown of what you can generally expect to move, provided your app supports portability.

Troubleshooting Mandate Migration

Moving payments between apps might not always go smoothly. Here are common issues and how to resolve them.

• The Mandate Does Not Appear: If your new app does not show an active mandate, ensure your bank account is fully linked. The feature might also still be rolling out for your specific bank.
• Migration Fails After Entering PIN: This usually happens due to a timeout at the remitter bank. Wait a few hours and try again. Do not spam the transfer button.
• Old App Still Shows the Mandate: Sometimes, the old app's display cache does not update immediately. The source of truth is your bank account. Check the NPCI portal or wait 24 hours for the old app to sync.
• Hit the 90-Day Limit: You cannot port the same mandate multiple times in a short period. If you moved it recently, you must wait out the 90-day cooling-off period.

Security Guide: Safe Portability Practices

Fraudsters often use new features to trick users. You must know how to distinguish legitimate mandate approvals from fraudulent requests.

• You Initiate the Action: A legitimate mandate transfer is always started by you, inside the app settings.
• Beware of Links: Never click on SMS or WhatsApp links claiming to "upgrade" or "port" your AutoPay. These are scams.
• The Golden PIN Rule: You only enter your UPI PIN to approve a transfer or send money. You NEVER enter your PIN to receive money or cancel a service.
• Verify the Merchant: When the PIN screen appears, verify the merchant name and the maximum debit limit shown. They should match your original subscription exactly.

Problems With Older AutoPay Mandates

Why is this new portability feature so important? To understand this, we must look at the older system. The legacy framework created massive friction for users.

In the old system, setting up an AutoPay mandate locked your payment to that specific UPI app. It bound the payment to that app's specific payment handle and ID. This created three major headaches.

• Strict App Lock-In: If you set up recurring debits on one app, you were stuck. Switching to a competing UPI application was very hard. You had to manually revoke every active mandate. Then, you had to log into individual merchant portals. Finally, you had to set up fresh authentications on the new app.
• The "Ghost Mandate" Problem: Users lacked a central console to see all their live recurring payments. Suppose you uninstalled an app without canceling the mandate inside it. The automated debits would still continue at your bank. This caused unexpected debits and failed transaction penalty charges.
• Merchant Gateway Dependence: For businesses, recurring mandates were tied to specific Payment Aggregators (PAs). If a business wanted to switch payment processors, it was a nightmare. They could not move the legacy mandates in the background. They had to ask every customer to re-authorize their payments.

How Cross-App Portability Works

The modernized framework fixes these older problems. It transforms the mandate from an app-specific permission into a portable asset. This asset is held centrally at your bank and the NPCI central switch.

The UPI app on your phone now acts merely as an interface. It is no longer the exclusive owner of your payment data. Your bank holds the actual instruction. Any approved app can now read that instruction.

Core Pillars of the Interoperability Framework

The updated mandate architecture establishes two functional pillars. These rules apply to Remitter Banks, Sponsor Banks, and Payment Service Providers.

Universal Viewability

Under portability guidelines, you must be able to see all your active mandates. This applies to any compliant UPI application registered with your verified mobile number. You can also view them on the central NPCI My Mandates portal.

When you link your bank account to a new UPI application, the app issues a secure request. It asks the NPCI switch for your data. The switch checks your bank's database. It returns a standardized list of every active standing instruction. This eliminates the "forgotten subscription" problem. It brings absolute transparency to your cash flows.

Also Read | Green Bonds in India: A Complete Guide to the Market and Regulations

Seamless Migration

Users possess the explicit right to migrate the management of an active mandate. You can move it from your Originating App to a Destination App. Once ported, everything changes to the new app. Future push notifications, pre-debit alerts, and pause commands will happen there.

Technical Execution Flow

The technical workflow for transferring a mandate relies on standardized API parameters. The UPI protocol suite manages these calls. The process is smooth for the user. However, it maintains bank-grade security on the backend.

1. Discovery Phase: The user opens the destination app. They navigate to the mandate section. The app fetches all active e-mandates via the NPCI switch.
2. Review Phase: The user selects a specific mandate. The app shows the immutable details. This includes the Unique Mandate Reference Number (UMRN), Merchant Name, and Debit Limit.
3. API Dispatch: The destination app sends a specific network request. It issues an `UPDATE` call to the NPCI switch.
4. Authentication Check: The NPCI switch prompts the user for their UPI PIN. This step ensures cryptographic proof of authorization. It prevents rogue apps from stealing your mandates.
5. Registry Update: Upon PIN validation, the bank updates its internal routing table. The NPCI switch binds the mandate to the new app.
6. Synchronized Handshake: The destination app shows a success message. An alert goes to the old app, forcing it to mark the mandate as "Ported Out."

Architectural Constants vs. Dynamic Variables

A critical security feature is strict data control. Some parameters remain fixed during a transfer. Other parameters change dynamically to allow the new routing.

What Does NOT Change (Immutable)

• The UMRN: The Unique Mandate Reference Number is permanent. NPCI generates this 18-digit identifier during setup. It anchors the mandate forever.
• The Funding Account: Your source of funds remains the same bank account. Porting changes the remote control, not the bank account itself.
• Financial Limits: You cannot increase the maximum per-debit limit during a port. Modifying limits requires an entirely separate, explicit approval process.
• Merchant Terms: The billing cycle and end date remain identical.
• Regulatory Alerts: The Reserve Bank of India (RBI) mandates a 24-hour pre-debit alert. Your bank must continue sending this via SMS or email.

What Changes (Mutable)

• Managing Routing: Future execution payloads and notifications route through the new app.
• User Control Console: Pausing or revoking the mandate now happens in the new app's interface.
• Dispute Resolution: If a double-debit occurs, you initiate the UPI Help module within the newly selected app.

Regulatory Guardrails and Protections

To maintain system stability, the framework introduces strict regulatory guardrails. These prevent abusive commercial practices.

The 90-Day Rolling Window Rule

You can port a single e-mandate only once every 90 days. This prevents automated switching that could crash bank servers. It stops users from constantly jumping between apps just to test the feature. The NPCI switch tracks this timer centrally. If you try to port a mandate too soon, the system will block it with an error code.

Also Read | Bank of Baroda Launches UPI Global QR Payments

Strict Anti-Solicitation Framework

NPCI enforces a strict policy against aggressive marketing. Apps cannot offer you cashbacks, scratch cards, or rewards to port your AutoPay mandates. Furthermore, apps cannot send targeted push notifications begging you to transfer your mandates. The porting action must be purely organic. The user must initiate it without bribes.

Merchant-Side Portability and Backend Decoupling

App portability is only half the story. The framework also creates massive changes for businesses and merchants.

Historically, a merchant's UPI AutoPay mandates were bound to their chosen Payment Aggregator. If a merchant wanted to switch aggregators due to high fees or server downtime, it was a disaster. They could not move the legacy mandates. They had to ask every single customer to re-authenticate their subscriptions.

The new framework fixes this with structural updates. Legacy mandates used Purpose Code 14. Interoperable mandates use Purpose Code AZ. This new code tells the bank that the mandate is not tied to one processor.

Furthermore, merchants now use a Corporate PAN-Based Merchant Identifier Code (MIC). This binds the merchant identity to their tax PAN, not their aggregator. A merchant can now seamlessly migrate thousands of active mandates from one aggregator to another. The consumers do not have to re-authenticate anything. This ensures subscription continuity and automated gateway failovers during server crashes.

Strategic Impact on the Indian Fintech Ecosystem

This transition reshapes the competitive landscape for payment apps in India.

Before portability, a few top players controlled most of the market. Recurring mandate lock-in passively reinforced this monopoly. Users stayed with clunky apps just because moving their SIPs was too much work. By freeing mandates, challenger apps can now compete fairly. They can win users by offering better speed, superior security, and cleaner interfaces.

Consumers also gain a massive advantage. You get a single dashboard to manage your financial life. You can easily audit all recurring obligations. You can execute quick revocations. If you cancel a service in your app, the termination is immediate. It stops the merchant from debating your bank account entirely.

Enterprises benefit from higher execution success rates. Interoperability reduces payment failures caused by old UPI IDs or dormant apps. Because mandates are anchored at the remitter bank, high-value transactions succeed more often.

Implementation Boundaries and Scope

While the rules are clear, ecosystem adoption takes time. Full interoperability requires your bank, the merchant's bank, and the apps to be certified for Purpose Code AZ. If your bank is slow to update, your mandates might temporarily show as ineligible for transfer.

What Cannot Be Ported

It is crucial to know the limits of this framework. It applies only to e-mandates registered directly on the UPI AutoPay rail. You cannot use this to port other types of recurring payments.

• Card-Billed Subscriptions: Payments tied directly to your credit or debit card numbers cannot be moved via UPI.
• NACH Mandates: Electronic mandates using IFSC and Account numbers fall outside this system.
• App Store Billing: Subscriptions managed via the Apple App Store or Google Play Store billing engines remain locked there.
• Wallet Auto-Reloads: Proprietary wallet top-up instructions cannot be ported.

UPI AutoPay Portability is a massive win for Open Banking in India. It ensures your financial data belongs to you, not the app you use. As banks finish upgrading their systems, the friction of switching financial providers will disappear. This paves the way for a truly competitive and transparent digital economy.

Also Read | UPI Privacy Rules Are Changing: What Happens to Your Mobile Number After September 4?