What Indian lenders Will Ask Their Fintech Partners Under DPDP

India’s new data protection regime leaves banks, NBFCs and payment firms responsible for what their technology partners do with customer data. A cybersecurity specialist argues that lenders will respond by putting much tougher questions to those partners well before the main duties start in May 2027.

Rahul Verma is a Cybersecurity Sales Specialist at Singahi, which helps growing companies prove security to customers, investors and regulators. In this contributed piece he sets out his own view of what lenders and payment firms will ask their fintech partners under India’s Digital Personal Data Protection Act. The views are his own.

Most of India’s Digital Personal Data Protection Act, 2023 applies from 13 May 2027. For banks, NBFCs and payment companies, the visible work is plain enough: consent notices, customer rights and breach reporting. Less visible, but just as demanding, is the job of checking every partner that handles customer data on their behalf.

That list runs long. A single lender might rely on one firm for video KYC, another for collection calls and a third for credit decisioning, alongside a cloud host, an SMS gateway and an outsourced support desk. Under the Act, each of those partners is a Data Processor. The lender is the Data Fiduciary, and section 8(1) keeps it responsible for what its processors do, “irrespective of any agreement to the contrary”.

“An indemnity clause doesn’t move that duty,” says Verma. Lenders cannot contract their way out of the liability, so they will do the next best thing and ask far harder questions before they sign or renew. He expects those questions to fall into six areas, each traceable to the Act or the DPDP Rules, 2025.

A contract that says the right things

Section 8(2) allows a Data Fiduciary to use a processor only under a valid contract, and Rule 6(1)(f) requires that contract to provide for reasonable security safeguards. Fintechs should expect a DPDP schedule at renewal, often placed beside the terms already written for RBI’s outsourcing rules. A partner that has never had to describe its security in contract language will now have to.

Breach notice measured in hours

Under Rule 7, the lender must tell the Board and every affected customer without delay once it becomes aware of a breach, with a fuller report to the Board within 72 hours. Banks also owe CERT-In a report within six hours for some incidents, and RBI has its own six-hour rule. A partner that sits on an incident for two days causes the lender to miss every one of those deadlines.

Verma expects the schedule to ask for a notice period in hours, and the lender’s security team to check the partner’s incident procedure against it. Where the contract says 24 hours and the procedure says 72, someone will ask which one is true.

A year of logs

Rule 6(1)(e) and Rule 8(3) call for personal data and processing logs to be retained for a year, and that covers work done by a Data Processor too. The Rules even give the example of a company whose customer records sit with a cloud provider. Partners should be ready for the lender to ask what their retention settings actually are.

Acting on withdrawn consent

This is the question most easily missed. Under section 6(6), once a customer withdraws consent the lender has a reasonable time to stop processing, and it must make its processors stop as well, except where a law requires or allows the processing to continue.

Take a marketing partner holding a few lakh customer records for a lender. One customer withdraws consent. Can the partner stop using that single record, and tell the lender the date it stopped? Section 8(7) works the same way for erasure once the purpose has been served, and at the end of a contract lenders will want the deletion confirmed in writing.

Naming the sub-processors

Lenders will want to know which sub-processors touch the data and where each one operates. A fintech running on three cloud services and an outsourced support team should be able to name them without a week of digging.

Supporting the lender’s audit

A lender notified as a Significant Data Fiduciary needs an independent data auditor, along with a yearly impact assessment and audit, under section 10(2) and Rule 13(1). Auditors follow the data, so they will want evidence from the partners that hold it, and the contract will give the lender the right to collect it.

Why the pressure will be real

The fines land on the lender. Failing to take reasonable security safeguards, including over what its processors do, can cost up to ₹250 crore. Failing to report a breach can cost up to ₹200 crore. Exposure on that scale travels down the supply chain through contract terms and questionnaires.

None of it requires a certificate. Nothing in the Act or the Rules makes ISO/IEC 27701, or any other standard, compulsory for processors. In Verma’s view, most of the answers already exist somewhere in a fintech’s contracts, cloud consoles and incident runbooks. The task is to gather them before a lender’s questionnaire arrives in, say, April 2027, a few weeks before the main duties begin.

The post What Indian lenders Will Ask Their Fintech Partners Under DPDP appeared first on The Fintech Times.

Read More

Leave a Reply

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