Fintech
DPDP compliance for fintech, lending and payments
Last reviewed 15 November 2026
Fintech companies sit on a concentrated pile of personal data: identity documents, bank details, transaction histories, credit scores and device signals. They are also among the most likely candidates for the stricter category of Significant Data Fiduciary. This page sets out what the DPDP Act and Rules mean for fintechs, lenders and payment companies and how to prepare.
A heavily regulated sector gets one more regulator
Fintechs already answer to the RBI, SEBI, IRDAI or other regulators depending on their business. The DPDP Act does not replace those; other laws continue to apply, and where retention or disclosure is required by another law, the Act respects that. What the DPDP Act adds is a horizontal set of duties on how you collect consent, protect data, handle breaches and treat customers’ rights, enforced by the Data Protection Board with penalties of up to ₹250 crore.
In practice, you need to reconcile obligations. A bank, for example, may need to keep customer identity records for years after an account closes because other law says so. The Act’s own example confirms that such retention is allowed. But you must be clear about which records you keep, why and for how long, and erase the rest.
Consent and purpose limitation in lending journeys
A loan application flow often collects far more than it needs, shares data with partners, and reuses it for cross-selling. Under the Act, consent must be specific to the purpose and limited to the data necessary for it. Asking for access to a customer’s contacts or photos to process a loan, when that is not necessary, is the kind of overreach the Act’s own illustration warns about. Marketing and data sharing with partners need separate, withdrawable consent.
The Act allows processing without consent for certain legitimate uses, such as complying with a legal obligation. It also exempts processing to ascertain the financial information, assets and liabilities of a person who has defaulted on a loan from a financial institution, subject to the provisions of other laws. Know which of your processing falls under which basis and document it.
Significant Data Fiduciary risk
The Central Government can notify a Data Fiduciary or class of Data Fiduciaries as Significant based on the volume and sensitivity of data, the risk to people’s rights and other factors. Large fintechs should plan as if they may be designated. Significant Data Fiduciaries must appoint an India-based Data Protection Officer who reports to the board, appoint an independent data auditor, and under Rule 13 undertake a Data Protection Impact Assessment and an audit every twelve months, sharing significant findings with the Board. They must also verify that algorithmic software is not likely to pose a risk to people’s rights, and may be required to keep certain specified data within India.
AI in credit decisions
Credit scoring, fraud detection and collections increasingly rely on models. The Act says that where personal data is likely to be used to decide something that affects the person, you must ensure its completeness, accuracy and consistency. Poor data feeding a credit model can therefore be a compliance failure as well as a fairness problem. Keep a register of AI systems that make or shape decisions, classify their risk, document human review and be ready to explain a decision to a customer who asks.
Vendors, KYC providers and collections agents
Fintech stacks are vendor-heavy: KYC and identity verification, payment gateways, credit bureaus, SMS and WhatsApp providers, cloud hosting, analytics and outsourced collections. You remain responsible for what they do with your customers’ data, and each must be engaged under a valid contract with security and breach-notification terms. A vendor register with risk scores and signed agreements is the minimum evidence you should be able to produce.
Breach reporting stacks up
A fintech breach may trigger several obligations at once. Under the DPDP Rules you must inform each affected person without delay and inform the Board without delay, with a detailed report within 72 hours. Sector regulators and CERT-In may have their own reporting timelines, which can be shorter. Your incident plan should list every recipient and deadline in one place, with owners and templates ready.
Cross-border data
The Act allows transfers of personal data outside India except to countries the Government restricts by notification, and Rule 15 says transfers are subject to requirements the Government may specify. Other sectoral rules, for instance on payment data storage, may be stricter and the Act expressly preserves laws that give a higher degree of protection. Map where your data and your processors’ data live.
How Complisarthi helps fintechs
- Compliance Audit scores readiness and prioritises gaps.
- Consent Manager records granular, purpose-level consent with a tamper-evident log and handles rights requests.
- Vendor Risk Tracker and DPA Generator cover KYC, payments and cloud vendors.
- AI Governance registers credit and fraud models, classifies impact and drafts transparency and explanation documents.
- Data Classification builds your record of processing and flags cross-border flows.
- Breach Response keeps the 72-hour and CERT-In clocks visible and drafts notices.
Find your fintech’s DPDP gaps
Start with the free compliance audit: about 10 minutes, no credit card, and a ranked list of what to fix first.
Check Your Compliance Score — Free