The Reserve Bank of India (RBI) issued consolidated Master Directions on Cyber Resilience and Digital Payment Security Controls for non-bank payment system operators (PSOs) on 5 November 2026. The new text replaces the version of 30 July 2024 and absorbs two older circulars: the December 2019 cyber security controls for third-party ATM switch application service providers and the January 2020 review of system audit scope for payment systems. Six circulars dating back to December 2009 are repealed. For large and medium operators the directions apply from the day they were placed on the RBI website, while small operators have until 1 April 2028. In RegMemo’s analysis, the main effect of the consolidation is that system audit timetables and ATM switch vendor controls now sit in the same enforceable direction as board governance and incident reporting, which makes them harder to treat as secondary.
Who is covered and from when
The RBI sorts operators into three tiers in footnotes to the direction. Large non-bank PSOs are the National Payments Corporation of India (NPCI), NPCI Bharat BillPay, card payment networks, non-bank ATM networks, white label ATM operators (WLAOs), large prepaid payment instrument (PPI) issuers, Trade Receivables Discounting System operators, Bharat Bill Payment Operating Units and payment aggregators. Medium PSOs are inbound cross-border money transfer operators under the Money Transfer Service Scheme and medium PPI issuers. Small PSOs are small PPI issuers and instant money transfer operators.
The direction is issued under section 10(2) read with section 18 of the Payment and Settlement Systems Act, 2007. Operators must also seek adherence from unregulated entities in their payment chain, such as payment gateways, technology vendors and ATM switch providers, “subject to mutual agreement”, under a board-approved policy.
Governance and incident reporting
The board is responsible for oversight of information security and cyber risk. It may delegate primary oversight to a board sub-committee headed by a member with information or cyber security experience, and that sub-committee must meet at least once a quarter. Each operator needs a board-approved information security policy reviewed every year, a separate cyber crisis management plan and a senior executive, such as a chief information security officer, accountable for the cyber resilience framework. Risk and performance indicators for security controls go to the sub-committee for continuous monitoring, and audit and vulnerability reports go to the next sub-committee meeting after they are ready.
Unusual incidents, including cyber attacks, outages of critical systems, internal fraud and settlement delays, must be reported to the RBI in the prescribed format within six hours of detection. Cyber security incidents must also go to CERT-In, the national computer emergency response team. The six-hour clock is looser than the one-hour notification that the Monetary Authority of Singapore requires of financial institutions under its technology risk notices, and it sits between that and the European Union’s Digital Operational Resilience Act, under which an initial report on a major incident is due within four hours of classification and no later than 24 hours after the firm becomes aware of it.
Controls that touch customer journeys
Several baseline controls show up directly in product design. All electronic payment transactions that debit an account, including cash withdrawals, must be authenticated by multi-factor authentication unless the RBI has explicitly relaxed the requirement. A change of registered mobile number or email address linked to a payment instrument triggers a cooling period of at least 12 hours before online payments can resume. Card terminals installed at merchants must be validated against the PCI point-to-point encryption programme, and PPI issuers must apply a cooling period on transfers and cash withdrawals after funds are loaded electronically.
Operators that use cloud services need a cloud operation policy within the information security policy, covering which activities may sit in the cloud, data localisation and recoverability. Cloud service providers must undergo independent security audits at least once a year, and the board sub-committee reviews those reports annually. API security must cover authentication, confidentiality, integrity and availability.
System audits and ATM switch providers
The absorbed 2020 circular now sits in Section V. Each authorised operator must file a system audit report every year, prepared by a CERT-In empanelled auditor or a qualified CISA or DISA holder, within two months of the close of its financial year. Firms with an April to March year file by 1 June; firms with a calendar year file by 1 March. Audit observations are closed only after the auditor accepts the closure, and the audit firm must have no conflict of interest.
Section VI carries over the 2019 controls for ATM switch providers. WLAOs that rely on shared third-party switch services must write the controls into their contracts and must give the RBI access to the provider for on-site and off-site supervision. Providers must comply with PCI-DSS and PA-DSS where applicable. The obligation runs through the WLAO contract, which leaves the WLAO answerable to the RBI for a vendor it does not own.
What to watch
- 5 November 2026: directions effective for large and medium non-bank PSOs on publication
- 1 June 2027: next system audit report deadline for operators with an April to March financial year
- 1 April 2028: directions take effect for small PPI issuers and instant money transfer operators
- Contract amendments between WLAOs and ATM switch providers to add the Section VI controls and RBI access rights
Primary sources
- RBI, Master Directions on Cyber Resilience and Digital Payment Security Controls for non-bank Payment System Operators, 5 November 2026
Related: RBI sets April 2027 start for Basel III operational risk capital at commercial banks
Photo (cropped): Sailko, CC BY 3.0 via Wikimedia Commons
