ATLAS
← Back to News and Insights

RBI consolidates cyber directions for non-bank payment operators, small PSOs from 2028

5 min

Large and medium PSOs are covered on website placement; the directions require annual system audits and RBI cyber-incident reports within six hours.

LinkedIn Post
RBI consolidates cyber directions for non-bank payment operators, small PSOs from 2028
India · Photo: Previn Samuel / Unsplash

The Reserve Bank of India (RBI) issued its Master Directions on Cyber Resilience and Digital Payment Security Controls for non-bank Payment System Operators on 5 November 2026. The final directions consolidate the RBI’s December 2019 cyber controls for third-party ATM switch application service providers and its January 2020 instructions on the scope and coverage of payment-system audits. They were issued under sections 10(2) and 18 of the Payment and Settlement Systems Act 2007.

The directions apply to all authorised non-bank payment system operators (PSOs). Existing security and risk-mitigation instructions for card payments, prepaid payment instruments (PPIs) and mobile banking continue to apply. Where applicability differs, the consolidated directions prevail.

For compliance teams, this is a final control framework rather than a consultation. PSOs must align board oversight, cyber-risk measurement, technical safeguards, vendor arrangements, incident reporting, business continuity and system audits against one instrument. The directions also require PSOs to secure adherence by unregulated entities in their digital-payment ecosystems, including payment gateways, vendors and third-party ATM switch providers, subject to mutual agreement and a board-approved organisational policy.

Governance moves to the board

The board remains responsible for oversight of information-security, cyber-risk and cyber-resilience risks. It may delegate primary oversight to a board subcommittee headed by a member with information or cyber-security experience, but that subcommittee must meet at least quarterly.

Each PSO must maintain a board-approved information-security policy covering its payment-system applications and products, the roles of the board, senior management and key personnel, cyber-risk controls, resilience processes and training. The policy must be reviewed annually. A separate board-approved Cyber Crisis Management Plan must address detection, containment, response and recovery from cyber threats and attacks.

The PSO must assign implementation and accountability for the information-security policy and cyber-resilience framework to a senior executive with relevant expertise, such as a chief information security officer. It must define key risk indicators to identify possible risk events and key performance indicators to assess control effectiveness. The board subcommittee must monitor both continuously, and information-technology assessment reports must be placed before it at the meeting immediately after they become available.

Before launching a new product, service or technology, or making a major change to existing infrastructure or processes, the PSO must conduct a cyber-risk assessment. Resulting actions must be implemented under the oversight of the CISO or equivalent executive.

Atlas’s view is that the structural change is not merely a consolidation of technical checklists. By linking quarterly board oversight, measurable indicators, recurring assessments and third-party controls, the RBI has placed cyber resilience within the PSO’s formal governance architecture.

Technical controls and the six-hour clock

The directions require a complete inventory of information assets, critical functions, processes and third-party providers, supported by current network, dependency and data-flow diagrams. Asset records must include an identifier, network address, location, owner and end-of-life support status.

Among the baseline controls, PSOs must:

- use least-privilege access, multi-factor authentication for privileged accounts and remote access, and controls over removable media;
- operate a security operations centre with centralised log monitoring, incident detection and response tools, supported by mechanisms such as security information and event management;
- use network segmentation, anti-malware, multi-layered boundary defences and application whitelisting;
- adopt secure software development practices and obtain source code for critical applications procured from vendors, or maintain a source-code escrow arrangement where that is not possible;
- subject applications to rigorous security testing, such as source-code review, vulnerability assessment or penetration testing, through qualified professionals at least annually in authenticated mode;
- resolve security-testing deficiencies within a time-bound process, and audit critical services, applications and infrastructure before deployment or redeployment;
- obtain independent-auditor assurance of cyber-resilience capabilities from vendors involved in critical processes;
- protect data in transit and at rest, including personally identifiable information, and obtain PCI-DSS certification where card data is stored;
- test backed-up data at least every six months to confirm recovery without loss of transactions or audit trails; and
- preserve audit logs for at least five years.

Cloud users must maintain a board-approved cloud policy covering permitted activities, provider responsibilities, localisation, protection and recoverability. Cloud service providers must undergo an independent information and cyber-security audit at least annually, with the report and the provider’s performance reviewed by the board’s IT-oversight subcommittee.

Unusual incidents, including cyber-attacks, critical-system outages, 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 be reported to CERT-In.

Business-continuity plans must cover extreme but plausible cyber events, be reviewed annually and support recovery against defined recovery-time and recovery-point objectives. The RBI says PSOs should strive for near-zero recovery-point objectives. Disaster-recovery facilities must be in a different zone from the primary data centre, and disaster-recovery drills must take place at least half-yearly.

The payment-security provisions add operational requirements for customer and transaction protection. PSOs must provide authenticated facilities for customers to identify and report fraudulent transactions, support alerts for unusual activity, and ensure that online transactions and fund-transfer notifications identify the merchant or beneficiary appropriately. A change to a registered mobile number or email address triggers a minimum 12-hour cooling period before online payments are permitted through mobile-payment services.

Annual audit and remediation

Authorised PSOs must submit an annual System Audit Report prepared by a CERT-In-empanelled auditor, a CISA registered with ISACA or a DISA-qualified auditor. The report is due within two months of the financial year-end. Entities using an April-to-March year should submit it by 1 June; those using a calendar year are advised to submit it by 1 March of the following year.

The auditor must be independent: neither the audit firm nor a sister concern may have provided services to the PSO during the previous two financial years. Testing must cover both control design and operating effectiveness across governance, access, hardware, networks, data, business continuity, scalability, project management, vendors, incidents, changes, patches, logs, mobile services and security testing.

Previous open observations must be checked for sustained compliance. The report and compliance status must go to the board. Each open observation requires a specific corrective-action deadline of no more than three months, and an observation is closed only after the auditor accepts the remediation.

Official source: rbi.org.in
PaymentsPayment System OversightICT Cyber IncidentsOperational Resilience ICT

Permanent link to this Atlas analysis

Continue with coverage connected by market, topic and operating context.

Continue with Atlas

Move from this development into the relevant research, comparison and workflow.