A bank's vendor review checks your SaaS against two rulebooks at once: the DPDP Act and the RBI's directions on outsourcing and cyber security. Under DPDP the bank is the Data Fiduciary and stays responsible for what you do with its customers' data. Under RBI rules it must also check your security, audit rights, data location, incident reporting and exit. Expect one questionnaire that covers both, and have evidence ready for each answer.
This post sets out which RBI directions are likely to apply, how they combine with DPDP, the question groups you will see, and the evidence for each. It builds on our post on DPDP for SaaS companies acting as Data Processors, which covers the DPDP side in more detail.
Why a bank's review goes further than DPDP
If your product handles a bank's customer data on its behalf, you are usually its Data Processor. The DPDP Act keeps the bank responsible for your processing (Section 8(1)), requires a valid contract with you (Section 8(2)), and requires its security safeguards to cover your work (Section 8(5)). Those duties start on 13 May 2027.
A bank is also regulated by the RBI, and RBI rules on outsourcing and technology risk already apply. They say similar things in different words, and some go further: inspection rights for the RBI itself, data stored in India where rules require it, and a six-hour incident clock. A bank's vendor team usually runs one review for both. The DPDP questions get added to a process that already exists. Our page on DPDP for banks and NBFCs covers what changes inside the bank.
The RBI directions a SaaS vendor meets

The RBI consolidated many of its instructions in late 2025 and 2026, so older vendor templates may still cite the earlier circulars. For scheduled commercial banks, the main ones as of November 2026 are:
| Direction | Reference | What it means for a SaaS vendor |
|---|---|---|
| Reserve Bank of India (Commercial Banks: Managing Risks in Outsourcing) Directions, 2025 | Reference: RBI/DOR/2025-26/171, 28 November 2025 | What it means for a SaaS vendor: Chapter IV covers material outsourcing of IT services, including cloud computing services and application service providers. It sets due diligence, contract terms, audit and RBI inspection rights, incident reporting, cloud controls and exit. It consolidates earlier outsourcing instructions, including those on IT outsourcing. Existing IT outsourcing agreements had to comply at renewal or by 10 April 2026, whichever was earlier |
| Reserve Bank of India (Commercial Banks: Cybersecurity, Technology: Risk, Resilience and Assurance Framework) Directions, 2026 | Reference: RBI/DoS/2026-27/410, 31 July 2026 | What it means for a SaaS vendor: Vendor risk assessment, due diligence and agreements for IT and cyber third parties outside the outsourcing directions. Data leak prevention at vendor-managed facilities. The bank stays responsible for customer data held by vendors. Banks report cyber incidents to the RBI within six hours of detection |
| Storage of Payment System Data | Reference: DPSS.CO.OD No.2785/06.08.005/2017-18, 6 April 2018, with FAQs | What it means for a SaaS vendor: Only if you handle payment data. The entire payment data must be stored in systems located only in India. It applies to third-party vendors engaged by payment system providers. Processing abroad is allowed if the data comes back to India within one business day or 24 hours, whichever is earlier |
| CERT-In Directions under the IT Act | Reference: 28 April 2022 | What it means for a SaaS vendor: Cyber incidents must be reported to CERT-In within 6 hours of noticing them. This applies to you as well as to the bank |
The RBI issued separate versions of the outsourcing directions for other kinds of regulated entity, such as payments banks and credit information companies, and the cyber security directions exclude small finance banks and payments banks. If you sell to an NBFC, a cooperative bank or a small finance bank, ask which direction it applies to you.
Is your SaaS "material outsourcing"?
The outsourcing directions apply their IT chapter to material outsourcing of IT services. That means a service that, if disrupted or compromised, could significantly affect the bank's business operations, or that could have a material impact on the bank's customers if there is unauthorised access, loss or theft of data (paragraph 53(2)). The directions name Software as a Service as a cloud service model (paragraph 91). They also exclude some purchases, such as off-the-shelf products like anti-virus and email solutions, and SMS gateways (paragraph 5(2)).
The bank decides how your product is classified, not you. If it is outside the outsourcing directions, the 2026 cyber security directions still expect a vendor risk assessment and an agreement in proportion to the risk (paragraphs 126 to 135). Either way, the DPDP questions apply whenever you process the bank's customer data.
How DPDP and RBI rules combine in one review
On most topics the two rulebooks ask for the same evidence. Where they differ, the bank will usually ask for the stricter of the two:
- Security. DPDP Rule 6 sets minimum safeguards: encryption or masking, access control, logs and monitoring, backups, one-year log retention and security terms in the contract. The RBI directions add items such as multi-factor authentication for cloud access and encryption keys under the bank's control for some cloud set-ups (paragraph 92).
- Incidents. DPDP Rule 7 asks the bank to tell affected people and the Board without delay, with a detailed report within 72 hours. The outsourcing directions ask you to report cyber incidents to the bank without undue delay, so that the bank can report to the RBI within six hours of detection by you (paragraph 56). That six-hour clock starts on your side.
- Sub-contractors. DPDP has no sub-processor rule, but the bank is responsible for the whole chain. The outsourcing directions require the bank's prior approval before you engage a subcontractor (paragraphs 34(iv) and 69), and make you liable for your subcontractors (paragraph 69(xiii)).
- Data location. DPDP allows transfers abroad unless the Government restricts a country (Section 16), and stricter sector rules still apply. The outsourcing directions ask for storage of data only in India "as applicable" under existing rules (paragraph 69(vi)). For payment data, the 2018 circular is explicit.
- Deletion and exit. DPDP requires the bank to make you erase its data when the purpose ends (Section 8(7)), after keeping data and logs for at least a year (Rule 8(3)). The outsourcing directions add a managed exit: return of data, help to a new provider, no changes to data during the transition, then removal or destruction (paragraphs 82, 83 and 92(xvi)).
- Audit. DPDP does not give the bank a right to audit you. The outsourcing directions require the contract to give the bank audit rights and the RBI inspection rights over you and your subcontractors (paragraphs 34 and 69).
The questions you'll get, and the evidence to have ready

Bank questionnaires differ in length and format, but the questions typically fall into these groups:
| Question group | Typical questions | What it rests on | Evidence to have ready |
|---|---|---|---|
| Data and purpose | Typical questions: What customer data do you receive? Do you use it for anything other than our service? | What it rests on: DPDP Sections 8(1), 8(2) | Evidence to have ready: A data map for the bank's data, and a written statement of the purposes you process it for |
| Data location | Typical questions: Where is our data stored and processed? Is any of it accessed from outside India? | What it rests on: Outsourcing para 69(vi); payment data circular; DPDP Section 16 | Evidence to have ready: Cloud regions for each system, backup locations, and a list of any support access from abroad |
| Sub-contractors | Typical questions: Who are your sub-processors? Will you seek our approval before adding one? | What it rests on: Outsourcing paras 34(iv), 69(xiii); DPDP Section 8(1) | Evidence to have ready: A sub-processor register with data sent, country and contract date, and your change-notice process |
| Security controls | Typical questions: How do you encrypt, control access, log and monitor? Who holds the keys? | What it rests on: DPDP Rule 6; outsourcing paras 66, 92; cyber directions | Evidence to have ready: Encryption and key management settings, SSO and MFA settings, a role and access matrix, dated access reviews, log sources and alert rules |
| Tenant isolation | Typical questions: How is our data kept separate from other customers? | What it rests on: Outsourcing para 66 (ability to identify and segregate the bank's data) | Evidence to have ready: An isolation design and the tests that check it |
| Assurance | Typical questions: Share your latest security audit and penetration test. Do you hold ISO 27001 or SOC 2? | What it rests on: Outsourcing due diligence; cyber directions | Evidence to have ready: Current reports, and records of findings fixed |
| Incident and breach reporting | Typical questions: How fast will you tell us about a cyber incident or personal data breach? What will you send? | What it rests on: Outsourcing para 56; DPDP Section 8(6), Rule 7; CERT-In Directions | Evidence to have ready: One runbook covering the bank notice, CERT-In's 6-hour report and the DPDP contents, with a notice template and a dated drill |
| Logs and retention | Typical questions: How long do you keep logs and our data? Can you give us logs for an investigation? | What it rests on: DPDP Rules 6(1)(c), 6(1)(e), 8(3); outsourcing para 69(ii) | Evidence to have ready: Retention settings per log and data store, a log store the logged systems cannot edit, and a log export procedure |
| Rights requests and withdrawal | Typical questions: Can you find, correct, erase or stop processing one customer's data on our instruction? | What it rests on: DPDP Sections 6(6), 8(7), 11 to 13 | Evidence to have ready: An API or admin action for each, with a log of every request handled |
| Deletion and exit | Typical questions: How do you return and delete our data when the contract ends? How do you prove it? | What it rests on: DPDP Section 8(7); outsourcing paras 82, 92(xvi) | Evidence to have ready: An exit plan with turnaround times, deletion jobs and logs, and a note on how long backups keep data |
| Business continuity | Typical questions: What happens if your service or cloud region fails? | What it rests on: DPDP Rule 6(1)(d); outsourcing directions on business continuity | Evidence to have ready: Backup schedule, dated restore tests, a recovery plan and test results |
| Audit and inspection | Typical questions: Will you allow audits by us and inspection by the RBI? | What it rests on: Outsourcing paras 34, 69, 76 | Evidence to have ready: Contract terms reviewed by your lawyers, and a named owner who handles audits |
| People | Typical questions: Are staff with access background-checked and bound by confidentiality? | What it rests on: Outsourcing para 69(xix); cyber directions para 135 | Evidence to have ready: Screening policy, NDAs and training records |
Most of this evidence answers DPDP questions from any customer. Build it once and reuse it. The vendor evidence pack page lists what goes in, and our Rule 6 checklist breaks the security rows into checks.
The bank DPDP addendum
Many banks already have an outsourcing agreement or IT services contract with you. For DPDP they may add an addendum. It typically covers:
- Processing only for the bank's purposes and on its instructions.
- Reasonable security safeguards, often mapped to Rule 6.
- A breach notice period in hours, with the contents the bank needs for its own reports.
- Stopping processing on withdrawal, erasure at the end of the purpose, and the one-year minimum for data and logs.
- Help with rights requests and grievances within set times.
- Sub-processor approval and flow-down of the same terms.
- Data location, and no transfer abroad without consent.
- Indemnities and liability for breaches caused by you.
Read each clause with an engineer before you sign. A notice period your on-call team cannot meet, or a deletion promise your backups cannot keep, is a gap you have agreed to. Wording, liability and indemnities are legal questions. Our partner law firm reviews them.
Three clocks that start at once
An incident at a SaaS vendor that involves a bank's customer data can start several reporting duties together:
- Your notice to the bank: the period in your contract. The outsourcing directions ask for it without undue delay, so that the bank can meet its six-hour RBI deadline, counted from your detection.
- CERT-In: 6 hours from noticing a reportable cyber incident, for you and for the bank.
- DPDP: the bank tells affected people and the Board without delay, then sends the Board a detailed report within 72 hours of becoming aware.
Write one runbook that covers all three, with templates the bank can use directly. Then run a drill and keep the record. The drill record is often the piece of evidence vendors don't have.
Getting ready
- Ask early which RBI direction the bank applies to you, and whether it treats your service as material outsourcing.
- Check whether you touch payment data. If you do, storage in India is a hard requirement.
- Build the data map and sub-processor register for the bank's data first. Most answers depend on them.
- Set one-year retention for logs and data now, because the record takes a year to build.
- Write the three-clock runbook and run a drill.
- Write an exit plan with turnaround times, and test deletion on a copy.
- Send the addendum and audit terms to your lawyers before you sign.
A DPDP gap assessment shows which answers you can back with evidence today and which you can't. We then build the fixes as DPDP implementation work. Our post on what a DPDP technical audit delivers shows the format. If the bank also sends an AI or security questionnaire, see our work on security questionnaires. New to the law? Start with the DPDP Act explained, or see everything we do for DPDP compliance.
This article is general information, not legal advice. Which RBI directions apply to your service, and what your contract must say, are questions for the bank and your lawyers.
Sources: Digital Personal Data Protection Act, 2023, Sections 6(6), 8, 11 to 13 and 16. Digital Personal Data Protection Rules, 2025, Rules 6, 7 and 8 (G.S.R. 846(E), Gazette of India, 13 November 2025). Reserve Bank of India (Commercial Banks: Managing Risks in Outsourcing) Directions, 2025 (RBI/DOR/2025-26/171, 28 November 2025). Reserve Bank of India (Commercial Banks: Cybersecurity, Technology: Risk, Resilience and Assurance Framework) Directions, 2026 (RBI/DoS/2026-27/410, 31 July 2026). RBI circular on Storage of Payment System Data (6 April 2018) and its FAQs. CERT-In Directions, 28 April 2022. Last reviewed 18 November 2026.
FAQ
What do banks ask SaaS vendors about DPDP?
Where their customers' data is stored and who can access it, how it is secured, which sub-processors receive it, how fast you will report a breach, and how you stop processing and delete it. Banks also ask RBI questions in the same review, such as audit and inspection rights, data location and exit plans. Expect to back each answer with evidence.
Which RBI rules apply to a SaaS vendor of a bank?
For scheduled commercial banks, mainly the Managing Risks in Outsourcing Directions, 2025, if the bank treats your service as material outsourcing of IT services, and the Cybersecurity, Technology: Risk, Resilience and Assurance Framework Directions, 2026. If you handle payment data, the 2018 circular on storage of payment system data also applies. The bank decides how your service is classified.
Does a SaaS vendor have to store bank data in India?
Payment data must be stored only in India under the RBI's 2018 circular, with limited processing abroad. For other data, the outsourcing directions ask for storage only in India where existing rules require it, and DPDP allows transfers unless the Government restricts a country. Banks often ask for India hosting in the contract anyway.
What is a bank DPDP addendum?
A set of data protection terms a bank adds to its contract with a vendor that processes its customers' data. It usually covers processing only on the bank's instructions, security safeguards, a breach notice period, deletion, help with rights requests and sub-processor approval. Check each clause with an engineer and a lawyer before signing.
How fast must a SaaS vendor report an incident to a bank?
The DPDP Act sets no deadline for vendors. The RBI outsourcing directions ask vendors to report cyber incidents to the bank without undue delay, so the bank can report to the RBI within six hours of the vendor's detection. CERT-In's 6-hour rule may apply to you directly, and the contract usually sets the exact period.
