FinTech and BFSI – Sector-specific Guidance for DPDP Compliance

  • Blog|Company Law|
  • 14 Min Read

How the DPDP Act applies to banks, NBFCs, fintech companies, insurers and co-operative banks: lawful bases, the interaction with RBI, PMLA and CERT-In rules, KYC retention, payment data localisation, breach reporting and audit evidence.

  • By Taxmann
  • |
  • Last Updated on 16 November, 2026

DPDP Compliance for BFSI

The DPDP Act applies to banks, NBFCs, fintech companies, insurers and SEBI-regulated entities as it applies to any other Data Fiduciary: it is a horizontal statute, with no sector-specific chapters. What makes DPDP compliance for BFSI demanding is the interaction with sectoral law. A personal data breach at a bank can trigger three notifications, one of them a six-hour report to CERT-In. Payment system data must stay in India under the RBI’s storage circular, whatever section 16 of the Act permits. And the erasure duty in section 8(7) gives way to the retention requirements of the PMLA and the RBI’s KYC Direction. Taxmann’s Digital Personal Data Protection sets out the working rule: where the DPDP Act and a sectoral requirement address the same obligation, satisfy both by applying the more restrictive. The core obligations apply from 13 May 2027.

Table of Contents

  1. Why does the DPDP Act matter for the BFSI sector?
  2. On what grounds may a bank process customer data?
  3. How do the DPDP Act and the RBI, PMLA and CERT-In requirements fit together?
  4. How long can KYC records be kept, and when must they be erased?
  5. Can a bank store customer data outside India?
  6. What must a bank do after a personal data breach?
  7. What changes for NBFCs, digital lenders and fintech companies?
  8. How does the Act apply to insurers and SEBI-regulated entities?
  9. Where should co-operative banks and smaller institutions start?
  10. What will an auditor look for in a financial institution?
  11. Quick answers

1. Why does the DPDP Act matter for the BFSI sector?

Because financial institutions sit where several of its obligations meet. The DPDP Act is a horizontal statute: it applies to every sector within the territorial scope of section 3 and contains no sector-specific chapters or industry-specific obligations. Its practical impact still varies by sector, because each sector brings its own regulatory history, processing patterns, vendor architecture and pre-existing regulation. A provision that is straightforward for a software company may present a complex interaction for a bank that is also subject to the RBI’s data localisation directions (Chapter 13).

A commercial bank processes identity data for Know Your Customer compliance, transaction data for payment processing, credit data for lending decisions and communication data for service delivery, and each category engages different provisions of the Act (para 13.1). The sectoral rules do not fall away. Section 38(1) makes the Act additional to, and not in derogation of, any other law, and section 38(2) gives the Act precedence only to the extent of a conflict (para 12.3). Where the DPDP Act and a sectoral requirement address the same obligation, the compliance programme must satisfy both, applying the more restrictive (paras 13.1 and 13.7). The ethical side of handling customer data, beyond what the law requires, is discussed in data ethics in banking.

2. On what grounds may a bank process customer data?

On a ground the Act recognises, mapped activity by activity. The book identifies the provisions that each category of banking data engages:

Processing Provision What it means for the bank
Statutory reporting to the RBI and the Financial Intelligence Unit, including suspicious transaction reports Section 7(d) A legitimate use, so the processing involved in the disclosure needs no consent; it must follow the disclosure provisions of the relevant law (paras 3.3.4 and 13.1)
Employee data Section 7(i) Processing for purposes of employment needs no consent (para 13.1)
Data used for credit decisions Section 8(3) Data likely to be used for a decision affecting the Data Principal must be complete, accurate and consistent; a credit decision made on an incomplete income record is a decision made on incomplete data (paras 5.3 and 13.1)
Customer records once the purpose is served Section 8(7) Erasure must be reconciled with the retention requirements of the PMLA, the RBI’s Master Direction on KYC and the Banking Regulation Act (para 13.1)
Promotional campaigns Section 6 consent In the book’s illustrative register, marketing is a separate purpose, not inherent in the underlying transaction, so it needs specific consent with an easy way to withdraw (Figure 3.1)

Onboarding is the Act’s own illustration of the notice duty. Under the illustration to section 5(1), a customer opening an account through a bank’s app opts for a live, video-based customer identification process to complete KYC, and the bank must accompany or precede its request for her personal data with a notice describing the data and the purpose of processing (Appendix B).

One exemption is specific to lending. Section 17(1)(f) exempts processing to ascertain the financial information and assets and liabilities of a person who has defaulted in payment due on a loan or advance taken from a financial institution, provided the processing follows the disclosure provisions of other law; “default” and “financial institution” take their meanings from section 3 of the Insolvency and Bankruptcy Code, 2016 (para 11.1.6). The exemption removes notice, consent, data quality and the rights obligations, but not accountability under section 8(1) or the security safeguards under section 8(5), which the book treats as a floor below which no exemption may descend (para 11.1). The two grounds are compared in lawful processing and consent and legitimate uses under section 7.

3. How do the DPDP Act and the RBI, PMLA and CERT-In requirements fit together?

Obligation by obligation. The book’s first implementation point for every sector is that the interaction must be mapped at the level of individual obligations, not through general statements about regulatory overlap. For each DPDP obligation, the mapping identifies the corresponding sectoral requirement, the more restrictive of the two and the control that satisfies both (para 13.9). Its illustrative matrix for banking (Figure 13.1, para 13.9):

Obligation DPDP Act Sectoral requirement More restrictive Control
Breach notification Section 8(6) and Rule 7, with the detailed report to the Board within 72 hours Cyber incident reporting within 6 hours (CERT-In Direction, 2022) CERT-In A unified incident response, with a 6-hour initial report covering both
Data localisation Section 16, a permissive default Payment data stored only in India (RBI circular, 2018) RBI Payment data stored in India; other data under section 16
Retention and erasure Section 8(7): erase when the purpose is served KYC records kept for 5 years after the relationship ends (RBI KYC Direction) RBI, the longer retention Retain for 5 years after the relationship, then erase
Consent Section 6: free, specific, informed Explicit, revocable consent under the RBI Digital Lending Guidelines Both aligned; the DPDP Act adds the Rule 3 notice One consent mechanism that satisfies both section 6 and the Digital Lending Guidelines

The mapping sorts obligations into three groups: overlap, where a single control satisfies both regimes; additionality, where the DPDP Act goes further than the sectoral rule; and conflict, where section 38(2) gives the Act precedence. The result is a unified compliance matrix showing, for each obligation, the DPDP reference, the sectoral reference, the control and the evidence of compliance (para 12.3). Roles need the same granularity: whether an institution is a Data Fiduciary, a Data Processor or both is decided for each processing activity, not for the organisation as a whole (para 13.9), as explained in Data Fiduciary, Data Processor or both.

Taxmann.com | Research | Subscribe Now!

4. How long can KYC records be kept, and when must they be erased?

For as long as the applicable law requires, and no longer. Section 8(7) requires erasure once consent is withdrawn or the specified purpose is no longer served, unless retention is necessary for compliance with any law. Banking is where that exception does most work. The book lists the PMLA and the RBI’s KYC directions among the retention requirements that every Data Fiduciary must map, category by category, keeping data only for as long as the most demanding applicable requirement mandates (para 8.1).

The Act’s own illustration to section 8(7) is a bank. A customer closes her savings account; the illustration posits a banking law that requires identity records to be kept for ten years after closure, and because retention is necessary for compliance with law, the bank keeps her data for that period (para 8.1). The actual period comes from the sectoral law. The book’s banking matrix records the RBI KYC Direction as requiring retention for five years after the relationship ends, with the control set as retain for five years post-relationship, then erase (Figure 13.1). Its retention schedule template treats payment transaction data the same way: stored in India under the RBI’s requirement, five years under the PMLA and a one-year minimum for logs under Rule 8(3), giving an effective period of five years, after which the data is erased and the erasure confirmed (Figure 8.1, para 8.9.1).

Erasure requests follow the same logic. A customer who asks a bank to erase her data under section 12(3) while anti-money laundering law still requires the bank to keep her identity records should receive a response explaining that the data cannot be erased during the retention period, and the bank must document the legal basis for keeping it. The book recommends that the response identify the broad reason, the categories of data retained, the retention period or review point where known, and the grievance route, even though the Act does not expressly require a reasoned refusal in those terms (para 9.2). A nominee’s request to erase a deceased customer’s data is declined on the same footing, with documented justification, where banking law requires the records to be kept (para 9.4). See data retention and erasure and handling Data Principal rights requests.

5. Can a bank store customer data outside India?

Not payment system data. Section 16(1) is permissive: personal data may be transferred abroad unless the Central Government notifies a restriction for a country or territory, and as of Notification G.S.R. 843(E) no such notification had been issued (para 8.6). But section 16(2) preserves any law that provides a higher degree of protection for, or restriction on, transfer outside India. The RBI’s circular on Storage of Payment System Data, which requires the entire data relating to payment systems operated in India to be stored only in India, operates independently of the Act. A bank that stores payment data overseas in reliance on section 16(1) would breach the RBI’s direction, even if it does not breach the Act (para 13.1).

The book’s method is a two-level assessment before any transfer. First, has a section 16(1) notification restricted transfer to the destination? Second, does any sectoral regulation, regulatory direction or statute restrict the transfer of that category of data? The transfer may proceed only if both are satisfied; relying on the first alone risks breaching both the sectoral rule and the accountability obligation in section 8(1) (para 8.8). The same question arises for insurers under the IRDAI’s data governance guidelines, to the extent they restrict cross-border transfer of policyholder data (para 8.8). A bank notified as a Significant Data Fiduciary may also have to keep personal data of categories specified by the Central Government, with the traffic data about its flow, within India under Rule 13(4) (para 8.7). See data localisation and cross-border transfers.

6. What must a bank do after a personal data breach?

Meet three clocks at once. A personal data breach at a bank may trigger three distinct notifications (para 13.1):

  1. the six-hour cyber incident report to CERT-In under the Information Technology Act, 2000;
  2. intimation to the Data Protection Board without delay, followed by the detailed report within seventy-two hours under Rule 7(2); and
  3. intimation to each affected Data Principal without delay under Rule 7(1).

The breach response workflow must accommodate all three, so detection, classification and notification have to work within the shortest applicable deadline (para 13.1). The CERT-In obligation operates independently of the DPDP Act’s breach notification requirements (para 12.3), and the seventy-two-hour clock runs from the moment the bank becomes aware of the breach, not from the end of its investigation (para 6.2). The book’s matrix resolves the overlap with a unified incident response that issues a six-hour initial report covering both regimes (Figure 13.1).

The Schedule sets the stakes: up to Rs. 250 crore for failing to take reasonable security safeguards under section 8(5), and up to Rs. 200 crore for failing to notify the Board or affected Data Principals under section 8(6) (para 14.5). The notification steps are set out in personal data breach intimation under Rule 7, and the response plan in the incident response plan.

7. What changes for NBFCs, digital lenders and fintech companies?

More obligations at once. The sector carries a concentration of DPDP obligations, reflecting its processing of financial data at scale, its reliance on digital channels to acquire and serve customers, and its position within the RBI’s oversight framework. Digital lending platforms process personal data across the whole customer lifecycle, and each stage engages different provisions of the Act (para 13.7):

  1. identity verification at onboarding;
  2. creditworthiness assessment during underwriting;
  3. transaction monitoring during the loan tenure; and
  4. collections processing in the event of default.

The RBI’s Digital Lending Guidelines restrict the collection of borrower data beyond what the lending purpose needs and require borrower consent to data collection. They operate alongside the consent framework in section 6 and the data minimisation built into section 6(1). Where both address the same obligation, such as informed consent to data collection, the programme must satisfy both and apply the more restrictive (para 13.7). In practice that means one consent mechanism built to meet both, with the Rule 3 notice that the DPDP Act adds (Figure 13.1). The consent records, notice versioning and withdrawal design that make consent provable are covered in lawful processing and consent.

The Consent Manager framework under section 6(7) to (9) and Rule 4 is of particular relevance to fintech, because of its structural similarity to the RBI’s Account Aggregator framework. Both interpose a registered intermediary between the individual and the data holder, both require the intermediary to act in a fiduciary capacity, and both prohibit it from reading the data that flows through its platform. Entities operating in both should assess how far their Account Aggregator infrastructure can be extended or adapted to support Consent Manager functions, and whether separate registration with the Data Protection Board under Rule 4 is required (para 13.7). See Consent Managers under the DPDP framework.

Taxmann's Digital Personal Data Protection Act 2023 with Rules – Bare Act with Section Notes

8. How does the Act apply to insurers and SEBI-regulated entities?

Insurers process some of the most sensitive data in commercial practice: health data for underwriting, financial data for premiums and claims, and identity data for verification. The Act creates no separate category of sensitive personal data, but that sensitivity is relevant when the Central Government assesses under section 10(1)(a) whether to designate an insurer as a Significant Data Fiduciary (para 13.2), with the additional obligations explained in Significant Data Fiduciary obligations.

The lawful basis changes with the stage of the policy. Policy issuance on a proposal the Data Principal voluntarily submits may fall within section 7(a). Claims processing may involve section 7(a), where the policyholder initiates the claim, and section 7(d), where the insurer is required by law to report claims data to the IRDAI. Fraud investigation may fall within section 17(1)(a), on enforcing legal rights, or section 17(1)(c), on investigating offences (para 13.2). Long policies raise the retention question: a life insurer that keeps a policyholder’s health data for the duration of a thirty-year term policy is retaining it for the specified purpose and is not in breach of section 8(7), provided retention is genuinely necessary for the policy or for compliance with insurance regulation (para 13.2).

SEBI-regulated entities, such as stock brokers, depositories, mutual fund houses, portfolio managers and investment advisers, process investor data for account opening, transaction execution, regulatory reporting and grievance handling. Regulatory reporting rests on section 7(d). SEBI’s own cybersecurity framework overlaps with the security safeguards in Rule 6(1) and the breach notification requirements in Rule 7, so these entities should map their existing controls against the Act, use them where they align and build additional controls where they do not (para 13.7).

9. Where should co-operative banks and smaller institutions start?

With the foundations. Urban co-operative banks, district central co-operative banks and regional rural banks often run on vendor-hosted core banking platforms, with small internal technology teams and heavy reliance on external providers for security operations and system administration. For them, DPDP compliance will often depend as much on the strength of Data Processor contracts as on internal controls, which gives section 8(2) and Rule 6(1)(f) particular importance (para 13.8). Vendor contracts should clearly address (para 13.8):

  1. security safeguards;
  2. breach notification obligations;
  3. assistance with Data Principal rights requests;
  4. log retention responsibilities; and
  5. deletion of personal data when the services end.

The book points to the RBI’s Comprehensive Cyber Security Framework for Urban Co-operative Banks of December 2019, which scales expectations to an institution’s digital footprint and complexity, and recommends a similar risk-based approach for DPDP. Smaller institutions should first put in place the minimum safeguards under Rule 6(1), compliant Data Processor agreements, a lawful basis register and a grievance redressal mechanism, and then add more advanced privacy governance as their capability matures (para 13.8). The contract terms are covered in the data processing agreement.

10. What will an auditor look for in a financial institution?

Whether the DPDP Act has been read with the sectoral rules, not in isolation. The auditor will test whether a regulatory interaction matrix maps DPDP obligations against sectoral requirements, whether the more restrictive requirement is applied where both frameworks address the same obligation, and whether sector-specific evidence is kept. For banking, that evidence is the reconciliation of DPDP retention periods with KYC retention periods (para 13.10), which the book expects a bank to be able to produce promptly when the Board or an auditor asks (para 13.9).

The two findings that recur in this area are DPDP compliance treated in isolation from sectoral requirements, with no interaction mapping at all, and conflicting retention periods between the DPDP Act and sectoral regulation applied inconsistently (para 13.10). How the audit itself is run is covered in how a DPDP compliance audit is conducted.

11. Quick answers

Why is the DPDP Act important for the BFSI sector?

Because banks, NBFCs, fintech companies and insurers process identity, transaction, credit and health data at scale, and each category engages different provisions of the Act. The Act applies alongside RBI, PMLA, CERT-In, IRDAI and SEBI requirements, so the work lies in mapping each obligation against the sectoral rule and applying the more restrictive of the two.

Does the DPDP Act apply to banks and NBFCs?

Yes. It is a horizontal statute with no sector-specific chapters, so banks, NBFCs and fintech companies are Data Fiduciaries like any other. Their sectoral regulation continues to apply: section 38(1) makes the Act additional to other laws, and section 38(2) gives the Act precedence only where there is a conflict.

How long can a bank keep KYC records under the DPDP Act?

For as long as the applicable law requires, after which they must be erased. Section 8(7) allows retention that is necessary for compliance with law. The book’s banking matrix records the RBI KYC Direction as requiring five years after the relationship ends, followed by erasure. An erasure request made during that period is declined, with the legal basis documented.

Can a bank store payment data outside India under the DPDP Act?

No. Section 16 permits transfers unless a country or territory is notified, but section 16(2) preserves stricter laws, and the RBI’s circular on Storage of Payment System Data requires payment system data to be stored only in India. A bank that relied on section 16 alone would breach the RBI’s direction.

What are the breach reporting timelines for banks under the DPDP Act?

Three run together: a report to CERT-In within six hours, intimation to the Data Protection Board without delay followed by a detailed report within seventy-two hours under Rule 7(2), and intimation to affected Data Principals without delay under Rule 7(1). The response workflow has to work within the shortest of these deadlines.

Is an Account Aggregator a Consent Manager under the DPDP Act?

They are separate frameworks with a similar structure: both place a registered intermediary between the individual and the data holder, require it to act in a fiduciary capacity, and bar it from reading the data. The book advises entities in both to assess whether their Account Aggregator infrastructure can support Consent Manager functions and whether separate registration with the Board under Rule 4 is required.

Does the DPDP Act exempt credit scoring or loan recovery?

Creditworthiness assessment during underwriting is processing that engages the Act, and data used for credit decisions must be complete, accurate and consistent under section 8(3). The exemption that touches lending is section 17(1)(f), for ascertaining the financial information and assets and liabilities of a person who has defaulted on a loan or advance from a financial institution, subject to the disclosure provisions of other law. Accountability and security safeguards still apply.

What should a co-operative bank do first under the DPDP Act?

Put the foundations in place: the minimum security safeguards under Rule 6(1), compliant agreements with its Data Processors, including the vendor hosting its core banking platform, a lawful basis register and a grievance redressal mechanism. More advanced privacy governance can follow as capability grows.

When do the DPDP Act’s obligations apply to banks and fintech companies?

From 13 May 2027, when Notification G.S.R. 843(E) brings the substantive obligations into force, including sections 3 to 17 other than section 6(9), and Rules 3 and 5 to 16. The registration of Consent Managers under section 6(9) and Rule 4 has applied since 13 November 2026.


This article draws on Chapter 13 of Taxmann’s Digital Personal Data Protection – An Essential Guide to India’s DPDP Law by CA Narasimhan Elangovan (2026 Edition), which examines banking and financial services, insurance, non-banking financial companies and fintech, and co-operative banks, regional rural banks and smaller institutions, together with the regulatory interaction matrix for banking and the sector-specific audit considerations. It also draws on Chapter 1 on commencement, Chapter 3 on the grounds for processing, Chapter 5 on data quality, Chapter 6 on breach intimation, Chapter 8 on retention and cross-border transfer, Chapter 9 on the erasure right, Chapter 11 on exemptions, Chapter 12 on the interaction with existing regulatory obligations, Chapter 14 on penalties, and Appendix B, which sets out the Act with section notes. Law stated as updated till 15 September 2026.

The DPDP Act, 2023, the DPDP Rules, 2025 and the notifications of 13 November 2025 are available on Taxmann.com | Research under Indian Acts and Rules.

Related reading: overview of the DPDP Act · scope and key definitions · rights of Data Principals · lawful processing and consent · obligations of Data Fiduciaries · cross-border data transfers · breach, enforcement and penalties · the DPDP Act compliance checklist for businesses · the DPDP Act and the IT Act · the DPDP Act and the EU GDPR · startups and SMEs · healthcare and HealthTech.

More in this series: the SPDI Rules and the DPDP Act · the Record of Processing Activities (ROPA) · the incident response plan · data retention and erasure · the privacy notice under Rule 3 · the data processing agreement · data localisation and cross-border transfers · employee data and workplace monitoring · exemptions under the DPDP Act · legitimate uses under section 7 · the Data Protection Board of India · how a DPDP compliance audit is conducted · Significant Data Fiduciary obligations · Consent Managers under the DPDP framework · personal data breach intimation under Rule 7 · handling Data Principal rights requests · Data Fiduciary, Data Processor or both · children’s data and verifiable parental consent.

Disclaimer: The content/information published on the website is only for general information of the user and shall not be construed as legal advice. While the Taxmann has exercised reasonable efforts to ensure the veracity of information/content published, Taxmann shall be under no liability in any manner whatsoever for incorrect information, if any.

Leave a Reply

Your email address will not be published. Required fields are marked *

Everything on Tax and Corporate Laws of India

To subscribe to our weekly newsletter please log in/register on Taxmann.com

Author: Taxmann

Taxmann Publications has a dedicated in-house Research & Editorial Team. This team consists of a team of Chartered Accountants, Company Secretaries, and Lawyers. This team works under the guidance and supervision of editor-in-chief Mr Rakesh Bhargava.

The Research and Editorial Team is responsible for developing reliable and accurate content for the readers. The team follows the six-sigma approach to achieve the benchmark of zero error in its publications and research platforms. The team ensures that the following publication guidelines are thoroughly followed while developing the content:

  • The statutory material is obtained only from the authorized and reliable sources
  • All the latest developments in the judicial and legislative fields are covered
  • Prepare the analytical write-ups on current, controversial, and important issues to help the readers to understand the concept and its implications
  • Every content published by Taxmann is complete, accurate and lucid
  • All evidence-based statements are supported with proper reference to Section, Circular No., Notification No. or citations
  • The golden rules of grammar, style and consistency are thoroughly followed
  • Font and size that's easy to read and remain consistent across all imprint and digital publications are applied