Skip to content
All writing

RBI's API advisory: the controls banks need by December 3

RBI has reportedly told banks to tighten API-based payments as AI-assisted attacks were reported: a full API client inventory, audits of API clients, payout safeguards and transaction limits, with key deadlines on December 3, 2026. What each control means in the systems.

Banking & payments2 min read

RBI issued a confidential advisory to banks dated November 3, 2026 on API-based payments, according to reports by Head and Tale and MediaNama. The advisory has not been published, so the details below are as reported. It asks banks to know every client calling their payment APIs, audit those clients, add safeguards on payouts and set limits, with technical changes due by December 3, 2026. A day after the advisory, the Indian Cyber Crime Coordination Centre warned banks, NBFCs and fintechs about AI-assisted attacks.

Know every API client

Banks are reported to need a full API client inventory. We would record each client's business profile, services used, integration details, limits and security contacts. In many banks this information sits in onboarding files, gateway configurations and relationship managers' email. Building it means reconciling the gateway's list of active credentials with the commercial records, and closing credentials nobody can account for.

Audit the clients

NBFC API clients reportedly need a CERT-In audit before onboarding, with existing clients given until February 3, 2027. Audits repeat at least once a year and after any material cyber incident. Other API clients, such as business correspondents, payment aggregators and fintechs, need a periodic audit within three months. Banks need a register that tracks each client's audit status and blocks or limits a client whose audit lapses.

Safeguard every payout

The reported requirement is at least one of two safeguards on API-based fund transfers. The first is beneficiary whitelisting, where only pre-registered accounts can receive payouts. The second is maker-checker with out-of-band confirmation of debit requests. New integrations need this before go-live; existing ones by December 3, 2026.

Limits and monitoring

Per-transaction and daily limits are reported as effective immediately, with intra-day velocity limits within one month. Banks are also asked to watch for changes in user-agent, app version, operating system and network attributes. Those changes are the signals an automated attack leaves.

The monitoring part is a fraud scoring problem. We would score each API transaction against that client's usual pattern. When we put real-time scoring and alerts inside a major financial institution's banking systems, fraudulent transactions fell by 25%.

What to do this month

Reconcile the API client list, put limits on every client, and choose whitelisting or maker-checker per integration. Then start the audit schedule and per-client monitoring, which take longer to run well.

Questions

What did RBI's November 2026 API advisory require?
As reported, a full API client inventory, CERT-In audits for NBFC API clients, periodic audits for other API clients, beneficiary whitelisting or maker-checker with out-of-band confirmation on payouts, transaction and velocity limits, and monitoring of client app and network changes.
What is the deadline for existing API integrations?
Existing API-based fund transfer integrations reportedly need a payout safeguard by December 3, 2026. Existing NBFC API clients reportedly have until February 3, 2027 for CERT-In audits.
What is beneficiary whitelisting for API payouts?
Only pre-registered accounts can receive payouts through a client's API integration.

Tell us which system the AI has to run inside

If that system is not ready for AI yet, tell us that too. An engineer will reply and say plainly whether we are the right firm for it.