Launching a Digital Lending Platform in India: RBI Rules, Costs and a Realistic Timeline
RBI rules decide how your lending stack handles money flows, disclosures and data. Here's what the directions require of the software, what a platform buy typically costs, and why most regulated launches take six to nine months.
Who the RBI Digital Lending Directions Cover and What They Change in Your Stack
If you're an NBFC, a bank or a lending service provider (LSP) planning a digital lending platform in India, settle first which of your systems the regulator treats as in scope. It's usually more than teams expect. The RBI's digital lending framework began as guidelines in September 2022, added default loss guarantee rules in June 2023, and was later consolidated into the Reserve Bank of India (Digital Lending) Directions, 2025. It applies to banks, NBFCs (housing finance companies included) and other regulated lenders, and it reaches every LSP and digital lending app (DLA) those regulated entities (REs) work with.
The core principle: the RE stays responsible for everything, even when a partner runs the app, onboarding or collections. Your loan origination system (LOS), loan management system (LMS), mobile app and partner APIs must all produce evidence the RE can show an inspector. That's a different job from building a slick onboarding flow, which is why a compliance-first requirements document should come before any vendor demo.
Foreign fintechs and global vendors hit this wall sooner than in most markets. Rules on data location, money flows and app permissions are strict enough that a platform built for the UK, the EU or Southeast Asia generally needs India-specific configuration, and sometimes a separate deployment.
Turning Each Rule Into a System Requirement
The rules are written in legal language, but most map directly onto product features. The table below is the checklist we'd put in an RFP. The right-hand column is what a weak implementation looks like. Rule details change through RBI circulars, so check each row against the current text with counsel.
| RBI requirement | What the platform must do | Red flag in a demo |
|---|---|---|
| Direct disbursal and repayment | Move funds directly between the borrower's bank account and the RE's account. LSP pool or pass-through accounts aren't allowed, apart from narrow exceptions such as certain co-lending flows or disbursal to a named end-use account | Disbursal routed through the LSP's nodal or escrow account "for reconciliation" |
| Key Fact Statement (KFS) | Generate a standardized KFS showing all-in APR, fees and cooling-off terms before the borrower signs, and log the acknowledgment | APR worked out in a spreadsheet outside the system, or fees missing from the KFS |
| Cooling-off (look-up) period | Let the borrower exit by repaying principal plus proportionate APR with no penalty. The minimum period is short and depends on loan tenor, so make it configurable by product | The exit flow needs a call to customer support |
| Data storage in India | Keep borrower data on servers located in India, and restrict any processing abroad to what the directions and your counsel confirm is permitted | Analytics, OCR or fraud scoring sent to an offshore SaaS endpoint |
| Need-based data collection with consent | Use explicit, purpose-specific consent with an audit trail. No access to contacts, call logs, files or media. Camera, microphone or location access only for onboarding or KYC | An SDK in the app that requests contacts or storage permissions |
| Grievance redressal | Name a grievance officer, track complaints with ticket IDs, and escalate unresolved cases to the RBI Integrated Ombudsman within the prescribed timelines | Complaints handled over email with no ticket IDs |
| Credit reporting and limits | Report every loan, short-tenor and BNPL-style products included, to credit bureaus. Never raise a credit limit without explicit borrower consent | Auto-enhancement switched on by default |
Two points catch teams out. First, the KFS must come from the same pricing engine that books the loan. Otherwise the disclosed APR and the charged APR will eventually differ, and that's a conduct problem, not a bug. Second, LSPs are limited in what personal data they may store, so the architecture should keep the system of record on the RE's side.
Separately, India's Digital Personal Data Protection Act and its Rules are being phased in over a transition period. Build consent and deletion workflows that satisfy both regimes now rather than refactoring later, and get qualified Indian regulatory counsel to confirm how they overlap in your setup.
Default Loss Guarantees, Multi-Lender Marketplaces and Account Aggregator Integration
Most LSP partnerships run into the default loss guarantee (DLG) rules. A DLG, sometimes called FLDG, is capped at 5% of the loan portfolio it covers. It can be provided only as a cash deposit, a fixed deposit with a lien in the RE's favor, or a bank guarantee. The RE must invoke it within 120 days of a loan becoming overdue unless the borrower pays first. The provider has to be a company incorporated under the Companies Act, and the arrangement must be disclosed. Asset classification and provisioning stay with the RE regardless of what the DLG covers.
For the tech stack, that means a DLG ledger: a portfolio-level cap tracker, invocation triggers tied to days past due, and reporting that ties out to the partner agreement. Many NBFC loan origination products treat this as a custom report. Push vendors to show it as a configured module.
If an LSP works with several lenders, the directions expect it to present the borrower with matching offers fairly, naming each lender and its key terms, without dark patterns that steer the choice. Run a marketplace and your offer-display logic and audit logs will be inspected. REs must also report their DLAs to the RBI, which maintains a public directory, so keep your app inventory accurate.
Account aggregator integration is optional in law but close to essential commercially. As a financial information user (FIU), you fetch consented bank statements and other financial data through RBI-licensed account aggregators such as Finvu, OneMoney, CAMSfinserv or Anumati, usually via a technology service provider. Budget for consent-artefact handling, parsing of the fetched data, and a PDF statement upload fallback for borrowers whose bank isn't live on the network.
What a Platform Buy Costs in 2026
Treat these as typical 2026 market ranges. They vary by contract terms, loan volumes and modules, and Indian-headquartered vendors, who usually price in rupees, are often cheaper than global vendors for similar scope. Confirm every figure with the vendor.
| Cost line | Typical range (USD) | Main driver |
|---|---|---|
| LOS + LMS implementation (one-time) | $60,000 to $400,000 | Number of products, integrations, co-lending and DLG modules |
| Annual subscription or license | $50,000 to $300,000+ | Active loans, users, modules; some vendors add per-loan fees |
| Mobile app and borrower journey | $40,000 to $150,000 | White-label vs. custom build, languages, accessibility |
| Third-party APIs (per loan) | About $0.50 to $4 | eKYC/CKYC, video KYC, bureau pulls, AA fetches, e-sign, e-mandate |
| India-region cloud hosting, DR and security tooling | $30,000 to $120,000 per year | Environments, disaster recovery, SIEM, WAF |
| Audits and assurance | $15,000 to $60,000 per year | VAPT by a CERT-In-empanelled auditor, IS audit, app reviews |
Hypothetical example: say a mid-size NBFC launches personal and MSME loans through its own app plus two LSP partners and expects about 15,000 disbursals a month. A plausible first-year budget runs $350,000 to $700,000 all-in, and third-party API spend likely becomes the largest variable cost by year two. Mambu, Nucleus Software, Newgen, Lentra and Pennant are among the vendors buyers commonly shortlist. Ask each for India-specific reference deployments, not global case studies.
A Realistic Six-to-Nine-Month Launch Plan
Some vendors quote 12 weeks. That may be achievable for a sandbox go-live. It isn't realistic for a regulated launch that can survive an inspection. Most delays come from partner integrations and compliance sign-off, not configuration.
| Phase | Months | Key outputs |
|---|---|---|
| Requirements, vendor selection, contract | 0 to 2 | Compliance-mapped RFP, data-residency clauses, exit and source-code escrow terms |
| Core configuration | 2 to 4 | Products, pricing and APR engine, KFS templates, cooling-off workflow, DLG ledger |
| Integrations | 3 to 6 | KYC, bureaus, account aggregator, e-sign, e-mandate, bank disbursal APIs, LSP APIs |
| Testing and assurance | 5 to 7 | UAT, VAPT, IS audit, board approval of policies, DLA reporting |
| Pilot and scale | 6 to 9 | Limited-cohort launch, reconciliation checks, grievance metrics, partner rollout |
Banks should plan for the upper end because of internal IT risk committees and core banking integration. A lean NBFC with one product and no LSP partners can sometimes finish in about six months.
Red Flags and a Decision Rule for Choosing a Vendor
- The vendor can't name its India hosting region or disaster-recovery site.
- KFS and APR are calculated outside the core loan engine.
- The disbursal design depends on a partner-controlled account.
- Mobile SDKs request permissions the directions prohibit.
- DLG, co-lending and multi-lender offer display are "on the roadmap."
- Contracts don't give the RE audit rights over the vendor and its subprocessors.
The decision rule: score every shortlisted vendor against the requirements table above before you look at price. Eliminate any vendor that fails direct disbursal, data residency or KFS generation, then negotiate cost among those left. Have qualified Indian counsel review the final architecture and partner contracts before launch.
Questions buyers ask
Can a lending service provider collect repayments into its own account and pass them to the lender?
Generally, no. The directions require disbursals and repayments to move directly between the borrower's bank account and the regulated entity's account, with no LSP pool or pass-through account. Narrow exceptions exist, such as certain co-lending flows and disbursals to a specified end-use account, so have counsel review any unusual money flow before you build it.
Do we need account aggregator integration to comply with the RBI digital lending directions?
It isn't mandatory, but most lenders adopt it because consented bank-statement data is faster and more reliable than PDF uploads, and it creates a clean consent trail. Coverage depends on the borrower's bank, so you still need a fallback upload and parsing flow.
Can we use a global cloud or SaaS vendor for our digital lending platform in India?
Yes, provided borrower data is stored on servers in India and any offshore processing is permitted under the directions. Most major cloud providers have Indian regions. The usual risk is subprocessors such as analytics, OCR or fraud tools that send data abroad. Ask for a full subprocessor list and data-flow diagram before you sign, and have counsel confirm the position.
Written by the Apex Hub Pulse editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.