API security is now a board-level matter for India’s lenders. The Reserve Bank of India (RBI) has issued an advisory dated 16 November 2026, titled “Good Practices for API Governance and Security”, asking banks, small finance banks, payments banks, NBFCs and urban co-operative banks to tighten how they build, open up, watch and retire the application programming interfaces that link them to fintechs, payment firms and AI services.
The guidance, reported by CNBC-TV18 and BW Businessworld on 17 November, follows an RBI thematic review of API practices across regulated entities. It goes wider than the regulator’s earlier 3 November advisory on bank-NBFC fund-transfer APIs, covering every API across the full lifecycle and, for the first time, APIs used to reach AI and machine learning models.
What the RBI API security advisory asks for
The RBI has said the practices are illustrative and do not override existing legal or supervisory rules. Still, they set a clear benchmark for what supervisors will look for.
- A board-approved API policy: a documented API security framework covering internal APIs and those exposed to customers and partners.
- Three lines of defence: business and technology teams run controls, information security and risk oversee them, and internal audit gives independent assurance.
- Named owners for critical APIs: a business owner accountable for the need and risk, and a technology owner for build and operations.
- A central API inventory: covering partner-built, externally exposed and retired APIs, with each one classified by criticality and risk.
- Least-privilege partner access: formal security reviews of third-party integrations, with access recertified periodically.
Technical controls banks and NBFCs must look at
On the technical side, the advisory calls for multi-factor authentication where appropriate, approved API gateways for critical and externally exposed interfaces, and rate limits, quotas and throttling to curb misuse and denial-of-service attacks. Requests and responses should be validated, while credentials, keys and certificates must be stored securely, rotated and monitored.
Lenders are also expected to keep centralised API security logs with real-time monitoring for unusual access, data extraction and credential theft. Security testing should go beyond software flaws to check whether business logic, such as transaction approvals, can be abused through a legitimate API call.
AI model APIs come under the lens
A notable addition is guidance on APIs that connect lenders to AI and machine learning models. The RBI wants access controls matched to each model’s sensitivity, safeguards against prompt- or input-based misuse, and audit trails of model versions, administrative changes and relevant inputs and outputs. Data sent to outside model providers should be governed through data residency, minimisation, anonymisation or tokenisation, and retention rules, so that customer data is not exposed through third-party AI services.
Why the RBI is acting now
The advisory follows a run of attacks on lending and payment links. On 9 October, CERT-In issued a critical alert on campaigns that stole API credentials of payment aggregators, gateways and partner banks, then called disbursement APIs from whitelisted systems to bypass KYC, sanction and limit checks. On 4 November it named the threat actor “Crafty Falcon” and warned the campaign was escalating.
Smaller NBFCs have been hit hardest, with an estimated Rs 300 crore lost in two months. Two Mumbai-based NBFCs reportedly lost about USD 2 million through more than 700 unauthorised transfers after the API link used for loan-disbursement instructions was compromised. The regulator has also stepped up cyber checks on banks and has said technology resilience matters as much as credit risk.
What it means for Indian lenders
For CIOs and CISOs, the immediate task is visibility: a complete, risk-ranked list of every API and every partner connected to it. Institutions that rely heavily on fintech, co-lending and embedded finance partnerships will have the most work to do, and the AI provisions mean GenAI pilots now need the same governance as payment APIs.
Key takeaways
- The RBI’s 16 November 2026 advisory sets good practices for API governance and security at banks, NBFCs and UCBs.
- It covers board-approved policy, API inventories, partner access, gateways, rate limits, logging and business-logic testing.
- APIs that connect lenders to AI and ML models are covered for the first time.
Featured image: The Reserve Bank of India tower in Mumbai. Photo: KuwarOnline, Wikimedia Commons (CC BY-SA 3.0).








