Q-Cyber Magazine
RBI's 2026 digital payment security controls
A companion 31 July 2026 Reserve Bank direction requires commercial banks to maintain a Board-approved payments-security policy and sets control chapters for internet banking, mobile applications and card payments.

On the same day it issued a consolidated cybersecurity framework for commercial banks, the Reserve Bank issued a companion direction aimed only at digital payments. The two texts should be read together, but they are not the same rulebook.
A policy with a three-part test
The Board may delegate review to the IT Strategy Committee, but material amendments remain with the Board, and the policy must be reviewed at least annually. The required content is unusually specific. Beyond alignment with business strategy and risk, the policy must address Functionality, Security and Performance: confidentiality and integrity of customer data and processes; infrastructure and backup; secure build and testing; scalability; high availability with minimal technical declines; dispute resolution and grievance handling; and a review mechanism that leads to swift corrective action when any of those requirements is impaired.
The scope is also broader than "a payment app." It includes financial and specified non-financial transactions such as balance enquiry, PIN set or change, mobile-banking registration, OTP generation, mini-statements, transaction-status checks and the option to raise a dispute. Those journeys, and the systems behind them, are in scope whether the bank operates them itself or through an RBI or authorised PSO system.
Exhibit 1
Structure of the 2026 digital payment security controls for commercial banks
| Chapter | Focus |
|---|---|
| I. Preliminary | Title, immediate commencement, applicability to commercial banks (other than small finance banks, payments banks and local area banks in this text), and defined payment products and services |
| II. Role of the Board | Board-approved digital payment policy, at least annual review, Functionality-Security-Performance requirements |
| III. General controls | Governance of security risks, generic controls, application security life cycle, authentication framework, fraud risk management, reconciliation, customer protection and grievance redressal |
| IV. Internet banking | Specific security controls for internet banking |
| V. Mobile payments applications | Device policy, encryption, re-authentication, ban on storing credentials on the device, handling of unsecured networks, optional alternatives to SMS-based OTP |
| VI. Card payments | Card payment security, including PCI-HSM for cardholder-authentication processes such as key generation, key injection and PIN verification |
Source: Reserve Bank of India (Commercial Banks – Digital Payment Security Controls) Directions, 2026, official table of contents and operative chapters, issued 31 July 2026 and updated 1 October 2026.
Mobile and card controls worth a close reading
The mobile chapter is a useful illustration of the direction's tone. Applications may be installed only if device baseline requirements are met, including checks for vulnerable operating systems, malicious applications and insecure Wi-Fi. Device or application encryption is required to protect stored customer information. The application must re-authenticate after a period of non-use and each time it is launched, must not store user IDs, passwords, keys or hashes on the device, and must wipe sensitive information from memory on exit. Banks may implement alternatives to SMS-based OTP. Unsecured networks must trigger additional checks.
For cards, the directions point to PCI-HSM for securing cardholder-authentication applications and processes, including key generation, key injection, PIN verification and secure encryption. Transaction-control caps, reviewed under a Board-approved policy, sit alongside fraud-risk and reconciliation duties in the general chapter.
Parallel 2026 payment-security directions exist for other bank classes. A payments business should confirm which licence text applies, rather than assuming the commercial-bank document is universal.
Implications
- Write the FSP test into the product policy, and review it at least annually at Board or IT Strategy Committee level.
- Treat non-financial journeys as in scope where the direction lists them.
- Remove credentials from the device, and rehearse re-authentication and unsecured-network behaviour.
- Align card key management with PCI-HSM expectations where card authentication is offered.
What this means for fintech
Banks, and the fintech partners who build on their rails, now have a current, detailed security text for digital payments. The useful reading is practical: if a new product cannot satisfy Functionality, Security and Performance in a Board-approved policy, it is not ready to be launched.


