Your Wallet App Now Has a Legal Clock Ticking on Every Cyberattack — RBI’s New Rules Give Payment Companies Just Six Hours to Report One
If you’ve ever changed your registered mobile number on a UPI app and then tried, within minutes, to send money — and found yourself briefly, inexplicably blocked — that friction is about to become a formal, nationwide rule rather than an inconsistent app-by-app quirk. On 5 November 2026, the Reserve Bank of India issued a consolidated set of Master Directions on Cyber Resilience and Digital Payment Security Controls for non-bank Payment System Operators (PSOs) — repealing and folding together six earlier, scattered circulars into one rulebook that now governs everything from UPI-linked wallets to card networks to cross-border money-transfer operators.
RBI CYBER RESILIENCE DIRECTIONS — KEY POINTS
Six-hour cyberattack reporting clock; twelve-hour cooling-off after a mobile/email change
RBI Master Directions on Cyber Resilience & Digital Payment Security Controls for non-bank PSOs — issued 5 November 2026
Large/medium PSOs comply immediately • small PSOs by 1 April 2028 • six earlier circulars repealed and consolidated
Two numbers sit at the heart of it. First: six hours. Any unusual incident — a cyberattack, a critical system outage, suspected internal fraud, a settlement delay — must be reported to the RBI, in a prescribed format, within six hours of detection; genuine cybersecurity incidents must separately go to CERT-In as well. Second: twelve hours. After a customer changes their registered mobile number or email ID, a mandatory cooling-off period of at least twelve hours must pass before that account can be used for an online payment — precisely the friction described above, now made uniform and compulsory rather than left to each operator’s own risk appetite.
Sidebar: prepaid instrument (PPI) issuers get a parallel, separately-worded cooling-off requirement for fund transfers and cash withdrawals after an electronic reload — the Directions don’t pin a specific number of hours to that one (Para 35 leaves it to the issuer to set a “suitable” period), which is worth flagging to any PPI-issuer client who assumes the same twelve-hour figure applies there by default.
The Directions sort payment operators into three tiers, and the tiering does real work. “Large” PSOs — the National Payments Corporation of India (NPCI) and its subsidiaries, card networks, non-bank ATM networks, white-label ATM operators, large PPI issuers, TReDS platforms, Bharat Bill Payment Operating Units and payment aggregators — along with “medium” PSOs (inbound cross-border money-transfer operators under MTSS, and medium-sized PPI issuers) must comply immediately, from the date the Directions were placed on the RBI’s website — no transition window at all. “Small” PSOs — small PPI issuers and instant money-transfer operators — get until 1 April 2028. A PPI issuer that gets reclassified upward into a bigger tier mid-stream must fall in line within one year of that reclassification, which creates a real planning wrinkle: an issuer reclassified late in 2027 could, on paper, land a compliance date later than 1 April 2028 even though it is now meant to be held to a higher standard sooner — something any issuer approaching a tier threshold should flag for RBI clarification rather than assume works in their favour.
Governance gets tightened too. Every covered PSO’s Board must now own information-security and cyber-resilience risk directly — it may delegate day-to-day oversight to a sub-committee, but that sub-committee must be headed by a member with genuine information-security or cyber-security background and must meet at least quarterly. The Board itself must approve both an Information Security policy (reviewed annually) and a separate Cyber Crisis Management Plan, and a named senior executive — typically a Chief Information Security Officer — must be personally accountable for making it all actually happen, with system-audit and VA/PT (vulnerability-assessment/penetration-testing) reports routed to that sub-committee at its next scheduled meeting rather than sitting in a drawer.
Why It Matters
This single rulebook now touches an enormous slice of how ordinary Indians move money day to day — UPI-linked wallets, prepaid cards, bill-payment apps, ATM networks that aren’t bank-owned, and the payment aggregators sitting behind a huge share of e-commerce checkout pages. For the fintech and payments industry specifically, the six-hour reporting clock and the governance mandates (named CISO, Board-approved Crisis Management Plan, quarterly sub-committee reviews) convert what used to be good-practice guidance, scattered across six separate circulars, into one unified, strictly timed compliance obligation with real supervisory teeth — and, for large and medium players, one with no grace period at all.
Key Takeaways
- RBI’s new Master Directions on Cyber Resilience and Digital Payment Security Controls for non-bank PSOs (issued 5 Nov 2026) repeal and consolidate six earlier circulars into one rulebook.
- Unusual incidents (cyberattacks, critical outages, suspected fraud, settlement delays) must be reported to the RBI within six hours of detection; cyber incidents go to CERT-In too.
- A twelve-hour cooling-off period now applies after any change to a customer’s registered mobile number or email, before that account can be used for an online payment.
- Large and medium PSOs (NPCI, card networks, large PPI issuers, payment aggregators, TReDS, BBPOUs, cross-border MTSS operators, medium PPI issuers) must comply immediately, from the date the Directions went live on RBI’s website — no transition window.
- Small PSOs (small PPI issuers, instant money-transfer operators) have until 1 April 2028; a PPI issuer reclassified into a higher tier must comply within one year of reclassification.
- The Board must directly own cyber-resilience risk, approve an annually-reviewed Information Security policy and a separate Cyber Crisis Management Plan, and designate an accountable senior executive (typically a CISO).
Practical Implications
For any client operating, or planning to operate, as a payment aggregator, PPI issuer, or bill-payment operator, this is not a “read when convenient” circular — large and medium-tier obligations are already in force with zero lead time. Boards of such entities should be told plainly that the governance requirements (a named CISO, an approved Crisis Management Plan, a quarterly-meeting sub-committee) are not optional best practice anymore but a direct Master Direction requirement, and that a six-hour incident-reporting clock starts running the moment an incident is detected, not when it’s confirmed or resolved. Clients building or auditing onboarding/KYC-update flows should specifically check whether their systems actually enforce the twelve-hour cooling-off window after a mobile/email change — a UX team that “fixes” this friction without knowing it’s now a regulatory floor could inadvertently create a compliance gap.
Action Checklist
- For payment-aggregator, PPI-issuer, TReDS, BBPOU or cross-border-MTSS clients: confirm immediate compliance readiness — there is no transition window for large/medium PSOs under this Direction.
- Verify the client’s incident-response playbook can actually meet the six-hour RBI reporting clock (and the separate CERT-In reporting obligation for cyber incidents specifically) from the moment of detection.
- Check that onboarding/account-update systems technically enforce the twelve-hour cooling-off period after a registered mobile number or email change, before permitting an online payment.
- For Boards of covered entities: confirm a named CISO (or equivalent accountable executive), a Board-approved Information Security policy (with an annual review cycle already scheduled), and a separate Cyber Crisis Management Plan are formally in place — not merely informally practised.
- For PPI issuers nearing a size/category threshold: flag the one-year-from-reclassification compliance rule to management now, given the identified gap where a late-2027 reclassification could nominally land a later deadline than small PSOs’ own 1 April 2028 date — and consider seeking RBI clarification rather than assuming the ambiguity resolves favourably.
Relevant Sections & Notifications
Section 10(2) read with Section 18, Payment and Settlement Systems Act, 2007 (enabling basis cited for the Directions per secondary legal analysis — see Disclaimer). Context: RBI Master Directions on Cyber Resilience and Digital Payment Security Controls for non-bank Payment System Operators, issued 5 November 2026, repealing six earlier circulars.
FAQs
Does the six-hour reporting clock apply to every payment company, or only the big ones? It applies across all three tiers — large, medium and small PSOs are all subject to the incident-reporting timeline. The tiering affects when an operator must have its broader governance and security controls in place, not the six-hour reporting obligation itself.
My PPI app doesn’t currently block a payment for twelve hours after I update my phone number — is that a problem? For large and medium PPI issuers, yes, in principle — this control is now a Master Direction requirement with no transition window, not a feature left to the operator’s discretion. Small PPI issuers have until 1 April 2028 to build this in.
Is this the same thing as the RBI’s general IT/cybersecurity guidelines for banks? No — this specific set of Directions applies to non-bank Payment System Operators (payment aggregators, PPI issuers, card networks, TReDS platforms, BBPOUs, cross-border money-transfer operators, non-bank ATM networks), not to banks themselves, which are separately regulated.
This article is intended for general informational purposes only and does not constitute financial, tax, legal or investment advice. This session could not directly retrieve the RBI’s own Master Directions text (or a specific circular/notification number for it); the headline facts — the 5 Nov 2026 issue date, the six-hour incident-reporting window, the twelve-hour cooling-off period, the three-tier classification and the 1 April 2028 small-PSO deadline — are corroborated across multiple independent outlets (including Vinod Kothari & Co.’s legal analysis and Outlook Money), and the specific enabling statutory provision (Section 10(2)/18, Payment and Settlement Systems Act, 2007) is cited per that secondary legal analysis rather than confirmed against the primary RBI text. Readers requiring the exact text should verify against rbi.org.in directly. Prepared by Finoscape Editorial Team — hello@finoscape.com.