​RBI Tightens API Security Rules for Banks and NBFCs Amid Cyberattack Risks

Rajesh Rai
5 Min Read


Follow us on Google News


Follow The420.in on Google News

New Delhi: Facing a rising threat of cyberattacks on financial institutions and unauthorized fund diversions through banking channels, the Reserve Bank of India (RBI) has directed banks, small finance banks, and non-banking financial companies (NBFCs) to tighten their digital security frameworks. The central bank has placed particular emphasis on imposing stricter controls over fund transfers conducted through Application Programming Interfaces (APIs), securing third-party connected systems, and enhancing transaction monitoring.

​On November 16, the RBI issued an advisory addressing API security and operational controls, with specific focus on API-based fund transfers. The regulator has also been communicating its supervisory expectations through regular engagements with banks and other regulated financial entities, expanding the scope of these discussions to include NBFCs. According to senior banking officials, the central bank is urging financial institutions not merely to react after an incident occurs, but to proactively identify vulnerabilities that criminals could exploit to access customer and institutional funds.

​Third-Party Vulnerabilities Threaten Banking Networks

​A primary concern for the RBI involves the exploitation of security weaknesses in third-party technical systems linked to banks and NBFCs. In several incidents, cybercriminals breached the systems of a financial institution or its external partner to divert money into fraudulent accounts through standard banking channels. Some cases involved altering beneficiary bank account details within loan disbursement systems, causing loan proceeds to be routed directly into accounts controlled by perpetrators.

​Such intrusions are known as supply chain attacks, where a vulnerability in a single partner or service provider compromises the broader network of connected institutions. The challenge for banking entities is to avoid approving transactions solely on the basis of trust in a partner’s security infrastructure. Under the RBI’s advisory, every transaction request received via an API must undergo independent verification. Banks must confirm that the payment instruction is genuine, initiated by an authorized entity, and contains accurate beneficiary details, rather than assuming a request is valid simply because it originates from a partner system.

​Transaction Velocity Checks and Account Verification

​Recommended security measures include transaction velocity checks, limits on API request volumes, whitelisting, and strong data encryption. The regulator has also stressed advance verification of beneficiary accounts and regular reconciliation of transactions. Financial institutions have been advised to periodically rotate security keys used for API authentication and conduct heightened scrutiny whenever unusual activity is detected.

​Through transaction velocity checks, institutions monitor the frequency and speed of transactions within a defined timeframe. If an API suddenly generates an abnormally high volume of payment requests, a bank can investigate the anomaly or temporarily restrict request limits. Rate limiting and throttling mechanisms further prevent any connected system from pushing through large batches of payment instructions within a short window. Banks are also required to periodically audit the security standards of their technology partners and review caps on the number and total value of API transfers permitted over fixed intervals.

​Six-Hour Cyber Incident Reporting Mandate

​Beyond API controls, the RBI aims to strengthen third-party risk management, data protection, and overall cyber incident preparedness. Financial institutions are expected to assess cyber risks in advance rather than limiting their response to post-incident reporting. Regulated entities are required to report specific categories of cyber incidents to the RBI within six hours of detection.

​Institutions must also reinforce senior management oversight, root-cause analysis, corrective measures, and forensic investigations where necessary. Restoring systems and resuming normal operations quickly after a cyberattack form a critical part of resilience planning. The central bank’s push comes as a growing share of banking operations relies on APIs and external technology partners, making the security of every link essential to protecting customer interests and maintaining uninterrupted financial services.