June 26, 2026
9 min read
RBI Digital Lending Guidelines 2025: What NBFCs Must Implement for Credit Analysis Compliance
June 26, 2026
9 min read
The RBI’s Digital Lending Directions 2025 are the most comprehensive update to India’s digital credit regulatory framework since the original 2022 guidelines. For NBFCs using automated credit decisioning infrastructure — credit bureau analysis software, bank statement analysis, GST verification, Account Aggregator — the 2025 Directions impose specific technical, operational, and governance requirements that go beyond the 2022 framework’s general principles and mandate specific implementation standards.
This article covers the four compliance pillars of the 2025 Directions and their practical implications for credit analysis tools, data collection practices, and credit policy documentation. It is not a comprehensive legal analysis — NBFCs should engage qualified legal and compliance counsel for their specific implementation. It is a practical guide to the operational changes that credit operations teams need to understand and implement.
The 2022 Digital Lending Guidelines established the foundational framework: consent-based data access, prohibition of first-loss default guarantees in certain structures, disclosure requirements, and data localisation. The 2025 Directions build on this foundation with three material expansions:
The 2025 auditability requirement means: for every credit decision — automated or human — the NBFC must maintain a complete record that can be reconstructed for an RBI examiner. For automated credit decisions made using automated credit underwriting India systems, this means:
Systems that generate a credit score or verdict without maintaining an attributed signal log do not meet the 2025 auditability standard — regardless of how accurate their scoring may be.
The 2025 Directions tighten the consent requirements for each data type used in credit assessment. For Account Aggregator India integration, the AA consent artefact satisfies the consent requirement for bank statement data. For PDF-based data collection, the NBFC must maintain documented evidence of the borrower’s consent to provide the documents for credit assessment purposes — and that consent must specify the data types being collected and the purpose for which they will be used. For bureau data, the credit enquiry itself (initiated only upon loan application) serves as the consent mechanism under existing bureau terms. For GSTR data accessed through the GSTN API, the NBFC must maintain a record of the consent mechanism used.
The practical implication: NBFCs must audit their current consent collection process for each data type and ensure that consent documentation meets the specificity requirements of the 2025 Directions. Generic ‘I agree to data collection’ checkboxes during loan application are likely insufficient; data-type-specific consent with purpose specification is the 2025 standard.
This pillar directly affects the choice of credit analysis tools. The 2025 Directions require that automated credit decisions be explainable to the borrower if requested — and explainable to RBI examiners during examination. Black-box algorithmic scoring models that produce a credit score or verdict without an interpretable signal trail do not meet this standard. Credit analysis software for NBFCs must produce outputs where each flag or signal can be explained in terms of the data that generated it.
Rule-based, flag-attributed systems meet the explainability standard by design — each flag is generated from a specific data element against a specific threshold, and both the data element and the threshold can be stated plainly: ‘This application received a Warning flag because the borrower’s credit card utilisation rate is 87%, which exceeds our 80% Warning threshold under the Board-approved credit policy Section 4.2.’
Opaque ML scoring models — where the output is a number without an interpretable feature attribution — do not meet this standard unless they are paired with an explainability layer (SHAP values, LIME, or similar attribution methods) that can produce a human-readable explanation for each decision.
The 2025 Directions maintain the data localisation requirement from the 2022 framework — all borrower financial data must be stored on India-based servers — and clarify the offshore processing exception: any processing of Indian borrower financial data on offshore systems must be completed within 24 hours, with data restored to Indian-based systems and the offshore copy deleted within that window. For NBFCs using cloud-based credit analysis platforms, this affects architecture choices — particularly for platforms that route data through offshore processing nodes.
GSTN API-based verification data, AA-sourced bank data, and bureau report data must all meet these localisation requirements. NBFCs should request explicit data localisation confirmation from their credit analysis tool vendors, including the geographic location of data storage and processing infrastructure, before deploying new tools in their underwriting workflow.
Mapping the compliance requirements to tool categories:
FinEye’s credit bureau analysis platform is designed around RBI-standard NPA classification terminology and generates signal-attributed Risk Flags with timestamped, logged outputs — designed for compliance with the 2025 framework’s auditability and explainability requirements.
The 2025 Directions update and extend the 2022 Digital Lending Guidelines with three material additions: specific auditability requirements (timestamped, signal-attributed logs from automated systems), algorithmic explainability requirements (decisioning outputs must be explainable to borrowers and examiners), and expanded data source documentation requirements (each data source used in credit decisions must be documented in the credit file with consent and signal attribution).
Account Aggregator integration is not explicitly mandated for all loan types by the 2025 Directions. However, the framework’s consent specificity requirements, data integrity expectations, and fraud management provisions create strong regulatory incentives for AA adoption where available. NBFCs accepting PDF bank statements must maintain specific consent documentation and implement forensic fraud detection, which AA integration simplifies or eliminates.
Auditable credit decisioning means that for every credit decision, the NBFC can produce, upon RBI examination request: the specific data sources accessed (with timestamps and consent records), the specific signals or flags generated from each data source (with the data element and threshold that triggered each flag), the credit decision output (with the flag set and credit policy rules applied), and the retention of this complete record for the specified period.
Compliance documentation requirements: (1) Board-approved credit policy covering all loan products, data sources, consent mechanisms, and risk flag thresholds; (2) signed data processing agreements with all credit analysis tool vendors confirming data localisation compliance; (3) consent collection records for each data type for every credit application; (4) system audit logs from all automated analysis tools; (5) training records for credit staff on the credit policy and automated tool outputs; (6) quarterly internal audit verification of compliance with each 2025 Directions requirement.
FinEye’s credit bureau analysis platform is designed around the specific requirements of RBI-compliant credit analysis: RBI-standard NPA classification terminology in all outputs, signal-attributed Risk Flags with specific data element attribution, timestamped and logged outputs for every analysis run, and India-based data storage. NBFCs should engage their compliance team to review FinEye’s specific implementation against their own interpretation of the 2025 Directions.