DPDPA Compliance for Banks, NBFCs and Fintechs in India
Map DPDP duties against your RBI controls
Yes, the DPDP Act applies to every bank, NBFC, insurer, broker and fintech in India that handles customer data in digital form. It works alongside RBI, SEBI and IRDAI rules, not instead of them. OrbCyber maps where the Act adds new work, builds consent and security controls, and keeps the evidence ready before 13 May 2027.
Does the DPDP Act Apply to Banks and NBFCs?
Yes. The DPDP Act 2023 applies to every entity in India that processes personal data in digital form. This includes scheduled commercial banks, small finance banks, NBFCs, housing finance companies, insurers, insurance brokers, stock brokers, AMCs, payment firms, account aggregators, credit bureaus and fintechs. It applies on top of RBI, SEBI and IRDAI rules, not instead of them.
Why Banking Needs Specialised DPDPA Readiness
KYC Data and Consent Overlap
Banks collect vast personal data during KYC: Aadhaar, PAN, biometrics, financial history. KYC itself is a legal duty and needs no consent (Section 7), but marketing, cross-selling and analytics on the same data do need separate, granular consent.
Working with RBI, SEBI and IRDAI Rules
Financial institutions answer to RBI, SEBI, IRDAI and now the Data Protection Board. Aligning DPDPA obligations with existing regulatory frameworks without duplication requires a single control matrix. See the comparison table below.
Fintech, UPI and Account Aggregator Data Flows
Account aggregators, UPI, lending APIs and neo-banking platforms move personal data across dozens of entities. Each party in the chain is a Data Fiduciary or Processor and needs a compliant consent architecture.
Cross-Border Transfers and Payment Data Localisation
Payment system data must be stored only in India under RBI rules. For other data, the DPDP Act (Section 16) allows transfers abroad unless the government restricts a country. Stricter sector rules stay in force under Section 16(2). Map which data falls under RBI localisation and protect the rest with contracts and security controls.
DPDP Act vs RBI, SEBI and IRDAI Rules
| Area | DPDP Act | Sector Rule | What to Do |
|---|---|---|---|
| Consent | Itemised notice, granular opt-in, easy withdrawal (Sec. 5–6) | RBI KYC: consent for KYC is implied by law; SEBI: client consent for trading | Separate marketing/analytics consent from KYC consent |
| Retention | Erase when purpose ends, unless another law requires retention (Sec. 8(7)) | PMLA: 5 years after relationship; RBI KYC: 5 years; SEBI: 5–8 years | Retention schedule per data type reconciling both |
| Breach reporting | Board + affected persons, detailed report within 72 hours (Rule 7) | CERT-In: 6 hours; RBI CSITE: immediate to RBI; SEBI: 6 hours | One playbook meeting all three timelines |
| Cross-border | Allowed unless country restricted (Sec. 16); stricter sector rules survive (Sec. 16(2)) | RBI: payment system data stored in India only | Map which data is RBI-localised; contract + controls for the rest |
| Security | Reasonable security safeguards (Sec. 8(5)); penalty up to ₹250 Cr | RBI IT Governance; CSITE framework; SEBI CSCRF | Gap map: DPDP adds breach evidence, consent logs, deletion proof |
| Vendors | Fiduciary responsible for Processors (Sec. 8(2)) | RBI outsourcing guidelines; IRDAI TPP rules | DPA + security checks + deletion clause for each processor |
Key DPDPA Obligations for Financial Institutions
Consent for Marketing, Cross-Sell and Analytics
Processing needed to comply with a law (KYC, regulatory reporting) does not need consent under Section 7. Marketing, cross-selling, analytics and sharing with partners for their own use do need clear, itemised consent the customer can withdraw as easily as they gave it.
KYC Retention vs Customer Erasure Requests
A customer can request deletion, but PMLA and RBI KYC rules require keeping records for at least five years after the relationship ends. Section 8(7) allows this. Banks should erase data no law requires, and tell the customer why the rest is kept.
Breach Reporting to the Board, CERT-In and RBI
Tell the Data Protection Board and each affected customer without delay; send a detailed report within 72 hours (Rule 7). CERT-In requires notification within 6 hours, and RBI has its own incident reporting. One tested playbook should meet all three timelines.
Customer Rights Requests
Customers can ask what data you hold and how it is used, correct it, request erasure where no law requires retention, raise a grievance, and nominate someone to act for them. Banks need a simple intake process, tracking system and defined SLAs.
DPDPA by Financial Sub-Sector
Banks and Small Finance Banks
Multiple core banking systems, large branch networks, millions of accounts and deep RBI oversight. Likely candidates for Significant Data Fiduciary notification with extra DPO, DPIA and audit duties.
NBFCs and Digital Lenders
Lending apps must give itemised notices, collect only needed data and let borrowers withdraw consent. RBI digital lending rules already limit access to phone contacts; the DPDP Act adds penalties and customer rights on top.
Insurers and Insurance Brokers
Claims data, health records for health insurance, and third-party processor networks. IRDAI rules and DPDP obligations must be reconciled, especially around health data retention and cross-selling consent.
Fintech, Payments and Account Aggregators
Digital-first data collection, cross-border cloud hosting and multi-party consent chains. Each party in an AA or UPI chain is a Fiduciary or Processor. Consent withdrawal must be as easy as sign-up.
Stock Brokers and AMCs
Client KYC, transaction data, nominee details and portfolio information under SEBI oversight. SEBI CSCRF and DPDP security requirements need one control set, not two parallel programmes.
Are Banks Significant Data Fiduciaries?
Only if the government notifies them. The government looks at the volume and sensitivity of data processed, and the potential impact on the public. Large banks and payment firms are likely candidates. A Significant Data Fiduciary must appoint a Data Protection Officer based in India, conduct yearly Data Protection Impact Assessments, and get an independent data audit.
How We Implement DPDPA Readiness for Banks and NBFCs
- STEP 01
Map Your Financial Data Landscape
Inventory every system that touches customer data: core banking, loan origination, card management, CRM, payment gateways and third-party integrations.
2–4 weeks
- STEP 02
Align RBI and DPDPA Obligations
Build a single control matrix covering DPDP Act, RBI Master Directions, CERT-In, SEBI CSCRF and IRDAI rules. Identify gaps where DPDP adds new work.
3–5 weeks
- STEP 03
Build Consent and Security Controls
Separate KYC consent from marketing consent. Implement access controls, encryption, audit logging and VAPT across core systems.
6–12 weeks
- STEP 04
Monitor and Report
Quarterly posture reviews, board-level data protection reporting, staff refresher training and breach drill exercises.
Ongoing
What Our BFSI DPDP Service Includes
Scope of Work
- Financial data inventory: KYC, transaction, credit, insurance, investment
- Consent architecture for account opening, lending, insurance and investment
- RBI Master Direction alignment with DPDPA consent and retention requirements
- Data Processing Agreements for payment gateways, credit bureaus, and fintechs
- Cross-border data transfer assessment against the government’s restricted-country list (Sec. 16)
- Breach notification playbook aligned to DPDPA, CERT-In (6 hours) and RBI CSITE timelines
- Data Principal rights fulfilment: access, correction, erasure, and nomination
- Board-level Data Protection governance framework
Deliverables You Receive
- DPDPA Readiness Assessment Report
- Financial Consent Management Framework
- RBI–DPDPA Regulatory Crosswalk
- Data Processing Agreement Library
- Cross-border Transfer Impact Assessment
- Breach Response & Notification Playbook
- Board Governance Charter for Data Protection
- Quarterly Compliance Review Roadmap
DPDPA Penalties for Banks and NBFCs
| Maximum | Offence | Section |
|---|---|---|
| ₹250 Cr | Failure to take reasonable security safeguards | Sec. 8(5) |
| ₹200 Cr | Failure to notify the Board and affected persons of a breach | Sec. 8(6) |
| ₹200 Cr | Breach of children’s data obligations | Sec. 9 |
| ₹150 Cr | Breach of Significant Data Fiduciary obligations | Sec. 10 |
| ₹50 Cr | Any other breach of the Act or Rules | Schedule |
Figures are maximums per instance set out in the Schedule to the DPDP Act, 2023. This page is general information and not legal advice.
Common DPDPA Mistakes in BFSI
RBI compliance does not cover DPDP
RBI IT governance and cyber security controls help with security safeguards, but they do not cover notices, consent records, customer rights or Board breach reporting.
Consent cannot override KYC retention
A customer can withdraw consent for marketing, but PMLA and RBI KYC rules still require keeping records. Section 8(7) protects banks that follow those rules.
A cookie banner is not consent for lending apps
Website banners cover website visitors only. Lending apps, core banking, CRM and payment systems each need their own notice and consent architecture.
DPDPA Banking and Finance FAQs
Does the DPDP Act apply to banks and NBFCs?
Yes. Every bank, NBFC, insurer, broker, payment firm and fintech in India that handles customer data in digital form must follow the DPDP Act. It applies on top of RBI, SEBI and IRDAI rules, not instead of them. Large institutions may also be notified as Significant Data Fiduciaries with extra duties.
Does RBI compliance cover DPDP obligations?
Only in part. RBI cyber security and IT governance controls help with the Act’s security safeguards. But RBI rules do not cover everything the Act asks for, such as itemised notices, consent records, easy withdrawal, customer rights requests and reporting breaches to the Data Protection Board. A gap map shows what is new.
How does the DPDP Act work with RBI’s data rules?
The DPDP Act applies in addition to other laws. Where RBI, PMLA or another law requires a bank to keep or handle data in a certain way, the bank follows that law. Stricter sector rules on sending data abroad also stay in force. One control matrix covering both avoids duplicate work.
Can a customer ask a bank to delete KYC data?
A customer can ask, but the bank must keep KYC records for as long as PMLA and RBI KYC rules require, usually at least five years after the relationship ends. The DPDP Act allows this. The bank should erase data that no law requires, and tell the customer why the rest is kept.
Do banks need consent to process customer data?
Not always. Processing needed to comply with a law, such as KYC checks or reporting to regulators, does not need consent under Section 7. Marketing, cross-selling, analytics and sharing with partners for their own use do need clear, itemised consent that the customer can withdraw as easily as they gave it.
What must a bank do after a data breach?
Tell the Data Protection Board and each affected customer without delay, and send a detailed report to the Board within 72 hours. CERT-In must be told within 6 hours, and RBI has its own incident reporting. Banks should run one tested playbook that meets all three timelines.
Does DPDPA affect account aggregator and UPI integrations?
Yes. Each party in an account aggregator or UPI chain is a Data Fiduciary or a Data Processor. Consent artefacts, data minimisation and retention limits need to be built into each integration. Keep logs that show what data was shared, under which consent, and when it was deleted.
Does banking data have to stay in India?
Payment system data must be stored only in India under RBI rules. For other data, the DPDP Act allows transfers abroad unless the government restricts a country, and stricter sector rules still apply. Map which data falls under RBI localisation and protect the rest with contracts and security controls.
How does the DPDP Act affect digital lending apps?
Digital lenders and their apps must give itemised notices, collect only needed data, record consent, and let borrowers withdraw consent and request deletion. RBI’s digital lending rules already limit access to phone contacts and media. The DPDP Act adds penalties and customer rights on top of those limits.
Are banks Significant Data Fiduciaries under the DPDP Act?
Only if the government notifies them. It looks at the volume and risk of data, and the impact on the public. Large banks and payment firms are likely candidates. A Significant Data Fiduciary must appoint a Data Protection Officer in India, run yearly impact assessments and get an independent data audit.
Are collection agencies, call centres and KYC vendors our responsibility?
Yes. The bank or NBFC is the Data Fiduciary and stays responsible for data it shares with processors. These include collection agencies, call centres, DSAs, KYC providers and cloud core banking vendors. You need contracts, security checks, breach reporting duties and deletion at the end of the work.
What are the DPDPA penalties for banks and NBFCs?
Penalties go up to ₹250 crore for failing to take reasonable security safeguards, and up to ₹200 crore each for not reporting a breach or breaking children’s data rules. Significant Data Fiduciary failures can draw up to ₹150 crore. These are maximums per instance, set by the Data Protection Board.
When must banks be ready for the DPDP Act?
The DPDP Rules were notified on 13 November 2025 and apply in phases. Most duties, such as notices, consent, security safeguards, breach reporting and customer rights, apply from 13 May 2027. Banks should start now, because mapping core banking, loan, card and vendor systems takes months.
Who helps banks and NBFCs with DPDP compliance in India?
Financial firms usually work with law firms for legal advice, software firms for consent tools, and security firms for controls and evidence. OrbCyber combines DPDP consulting, security engineering and a consent management platform, and maps DPDP duties against existing RBI controls so teams reuse what they already have.
Reviewed by the OrbCyber Advisory Team | Last reviewed: October 2026 | Sources: Digital Personal Data Protection Act, 2023 (Gazette of India); DPDP Rules, 2025 (MeitY notification dated 13 November 2025); RBI Master Direction on IT Governance, Risk Management and Controls; CERT-In Directions, April 2022. This page is general information and not legal advice.
DPDPA for Other Industries
Ready to strengthen your security posture?
Book a free 30-minute consultation. No slides, just a working conversation about your gaps and roadmap.