RBI's new security rules for non-bank payment operators, and what they mean for your payment app
On 5 November 2026 the Reserve Bank of India consolidated its cyber security and digital payment rules for authorised non-bank payment system operators, the companies behind wallets, payment gateways and other non-bank payment systems. Large and medium operators are covered from day one, small operators from 1 April 2028. What the rules require, and what to do in the first minutes of a payment scam.
Most people will never read an RBI Master Direction, and they should not have to. But the one issued on 5 November 2026 is unusually easy to translate into everyday terms, because several of its controls are things you can actually see and feel in a payment app: a forced logout, a blocked login after wrong PINs, a waiting period after you change your phone number. The document, "Master Directions on Cyber Resilience and Digital Payment Security Controls for non-bank Payment System Operators", pulls older circulars into one rulebook for the non-bank companies RBI authorises to run payment systems.
Who the rules actually cover
The directions apply to authorised non-bank payment system operators, often shortened to non-bank PSOs. That is the layer of companies that run payment systems without being banks: wallet and prepaid instrument issuers, payment aggregators and similar operators that hold an RBI authorisation. Two qualifications matter before anything else. First, banks are not the subject of this document; RBI notes that the existing instructions for cards, prepaid instruments and mobile banking continue as before. Second, the timelines differ by operator size: for large and medium non-bank PSOs the directions took effect the day they were published, while small non-bank PSOs have until 1 April 2028. So "RBI now requires X" does not mean every payment app on every phone shows every control today.
Protections you will be able to see
Several required controls map directly to moments a user notices:
Remote-access blocking. Operators must put in place a mechanism to identify remote access applications, to the extent possible, and prohibit access to the mobile payment application while the remote access is live. This targets the most damaging current scam pattern, where a fraudster convinces someone to install a screen-sharing app and then watches them type PINs.
A 12-hour cooling period. Whenever the registered mobile number or email ID linked to a payment instrument changes, there must be a cooling period of at least 12 hours before any payment transaction is allowed through online channels. A hijacked SIM swap or changed contact detail can no longer be followed instantly by a emptied account.
Device and SIM binding. Mobile payment applications must be bound to the device and SIM, and if the app sits unused beyond a period the operator sets, binding has to be performed again. Combined with automatic session termination after inactivity and a cap on failed login attempts, with immediate notification to the customer, the app becomes much harder to operate from someone else's phone.
Multi-factor authentication. Electronic debits, whether from bank accounts, cards or prepaid instruments, must be validated through multi-factor authentication except where explicitly relaxed.
Protections that work in the background
Operators must run real-time or near real-time fraud monitoring that generates alerts on suspicious behaviour, and facilitate online alerts based on parameters like transaction velocity, unusual geo-location or IP origin, and transfers to wallets, mobile numbers or VPAs on which vishing or other fraud is already registered. Transaction alerts must mask account and card numbers, must name the actual merchant or beneficiary rather than a gateway, and where an OTP is involved it must sit at the end of the message with a reference to the specific transaction. Operators must also subscribe to anti-phishing and anti-rogue-app services to identify and take down fake websites and applications impersonating them, and they must keep audit logs for at least five years.
If a scam still gets through
No rulebook stops every fraud, which is why the directions also mandate the response side. Each operator must run a staffed facility, 24 hours a day, every day of the year, for swift resolution of unauthorised or fraudulent transactions reported by customers. And each must provide a facility in its app or on its website that lets a customer, after authentication, identify and mark a fraudulent transaction for seamless and immediate notification to the issuer of the payment instrument. Alongside the operator's own channel, the government runs two citizen routes verified for this article: the national helpline 1930, which the Indian Cyber Crime Coordination Centre says runs in all states and union territories and connects to a system linking banks, payment intermediaries and wallets for quick action on financial cyber fraud, and the National Cybercrime Reporting Portal at cybercrime.gov.in, where all types of cybercrime can be reported.
Call 1930 first, and immediately. The national helpline runs in every state and union territory and exists to act fast on financial cyber fraud; do not wait to gather proof, and do not wait to find the right button inside the app. Filing at cybercrime.gov.in is equally direct. Everything else happens in parallel or right after, as available:
1. Call 1930 now, or file at cybercrime.gov.in. Neither requires any prior step.
2. Mark the transaction as fraud inside the payment app or on the operator's website; the directions require operators to offer this with immediate notification to the issuer of the payment instrument. Contact the operator's 24x7 reporting desk as well.
3. Keep whatever evidence you can: screenshots, SMS alerts, call records and the transaction reference.
Acting quickly improves the chance that the money trail is frozen in time, but no route can promise recovery.
The honest version
These directions raise the floor for the non-bank payment companies RBI authorises, and several controls directly attack the scams that currently do the most damage. They are not a guarantee. Coverage depends on the operator's size category, small operators have until April 2028, banks follow their own existing instructions, and no control replaces the basic habit of never sharing an OTP or installing an app because a caller asked you to. What has changed is that the protections now have names, timelines and a regulator behind them, and the reporting routes are concrete: the app's fraud desk, 1930, and cybercrime.gov.in.
Sources: Reserve Bank of India, "Master Directions on Cyber Resilience and Digital Payment Security Controls for non-bank Payment System Operators", 5 November 2026 (scope, effective dates and all quoted controls); Indian Cyber Crime Coordination Centre, i4c.mha.gov.in/ncrp.aspx (helpline 1930 and the citizen financial cyber fraud reporting system); National Cybercrime Reporting Portal, cybercrime.gov.in.
Frequently asked questions
Does this cover my bank's own app?
Not directly. The directions apply to authorised non-bank payment system operators. RBI states that the existing instructions on security and risk mitigation for cards, prepaid payment instruments and mobile banking continue to apply as before, and where there is any discrepancy in applicability, this Master Direction prevails for the entities it covers.
Does every payment app have to show all of this today?
No. The directions took effect on publication for large and medium non-bank PSOs, while small non-bank PSOs have until 1 April 2028. The document does not define a single visible deadline by which a particular feature appears in a particular app, so treat the list as what operators are required to build, not proof of what is already live.
What is the fastest thing to do after a fraudulent payment?
Call the national helpline 1930 immediately, or file at cybercrime.gov.in; neither waits on anything else. In parallel, mark the transaction as fraud in the app or on the operator's website, which the directions require operators to support with immediate notification to the issuer, and keep your evidence.