PocketEdge
← All news

Desk note · industry · Banking / cyber regulation

RBI told banks to tighten controls on APIs after lending cyber raids

A Reserve Bank of India advisory dated 16 November 2026 lays out API inventories, owner accountability and stricter authentication for banks and NBFCs, following CERT-In alerts on attacks that exploited loan-disbursement interfaces.

17 Nov 2026 · 2 min read

Key takeaways

  • •The Good Practices for API Governance and Security applies to commercial banks, small finance banks, payments banks, NBFCs and urban co-operative banks.
  • •Regulators want a live register of APIs, risk-tiered reviews, named business and technology owners for critical interfaces, and periodic permission audits for fintech partners.
  • •Separate guidance covers AI and machine learning APIs, including data minimisation and monitoring of prompts sent to external model providers.

What's going on here?

Banks no longer serve customers only through branches. Most account opening, loan sanction and payment triggers run through application programming interfaces that connect core banking systems to fintech lenders, aggregators and merchant platforms. When those pipes leak credentials, attackers can move money without breaking into the main data centre. On 16 November 2026 the Reserve Bank of India issued an advisory titled Good Practices for API Governance and Security after a thematic review of how regulated entities manage these connections. The paper covers the full lifecycle from design to retirement. It asks for board-approved policies, split accountability between business, technology, risk and audit teams, and inventories that include third-party and discontinued interfaces. Critical APIs need named owners on both the business and tech side. The RBI also nudges multi-factor authentication, rate limits, gateway controls and continuous logging because Indian Computer Emergency Response Team alerts in October and November 2026 described NBFCs and payment firms losing money through compromised disbursement APIs, sometimes on weekends when monitoring thins out.

What does this mean?

Compliance cost rises for lenders that grew quickly by plugging dozens of fintech partners into the same API layer. Incumbent banks must map which external apps can originate loans or pull customer data, then prove access matches current contracts. Fintech partners face more frequent permission reviews and may see slower sandbox approvals until gateways catch up. For borrowers the near-term product set should look unchanged, but fraud response teams should expect more step-up checks on large transfers routed through partner apps. The AI section matters as banks trial external large language models for credit memos or customer chat: data leaving the firewall through an API must be scoped, logged and sometimes tokenised.

Why should I care?

If you use a digital lender or payments app, expect occasional friction as banks tighten API limits after patching holes. NBFC and bank technology vendors should budget for quarterly access reviews and penetration tests that mimic authorised API abuse, not only external hackers. Investors should read cyber disclosures in the next quarterly risk sections of private banks and large NBFCs. Watch follow-on RBI circulars that turn the advisory into binding directions, CERT-In updates on the CRAFTY FALCON campaign, and whether smaller urban co-operative banks receive delayed compliance timelines.

More desk notes

Disclaimer

For informational purposes only. Not investment advice. Verify with filings and a licensed adviser.