July 2, 2026 · Fintech · 9 min read
In India's lending market, NBFCs possess deep customer acquisition networks but face high capital costs, while nationalized banks hold huge low-cost deposits but lack digital onboarding channels. The RBI co-lending framework resolves this balance. Under the guidelines, banks and NBFCs co-lend to retail borrowers, sharing the capital risk. The bank provides the bulk of the loan (up to 80%), while the originating NBFC contributes the remaining 20%.
To scale these co-lending portfolios, platforms must automate credit scoring, escrow splits, and collections in real-time, replacing manual banking spreadsheets.
Managing split collections is the primary technical challenge in co-lending. When a borrower pays their EMI through UPI or Net Banking, the payment must be divided between the bank and the NBFC according to the co-lending split ratio (typically 80:20). Developers set up joint escrow accounts at partner banks.
Automated split billing sweeps route 80% of incoming EMI principal and interest payments directly to the bank's account, sweeps the 20% balance to the NBFC's ledger. This automated division prevents funds from mixing, satisfying banking guidelines.
With thousands of active loans running split EMIs, ledger mismatches easily crop up due to bank gateway drops or early repayments. Co-lending engines run automated, daily ledger reconciliation scripts. These scripts pull transaction reports from the bank's database using APIs, comparing them with internal borrower ledgers.
If a ledger mismatch is identified, the engine flags the record, alerting operations teams before billing runs. Running these daily checks prevents accounting discrepancies, keeping the co-lending book ready for RBI audits.
To execute split interest sweeps programmatically, developers schedule payment checks. Below is an example JSON payload indicating the structure of a split payment command, mapping incoming EMI values, joint escrow accounts, and the 80:20 split sweeps:
{
"escrow_sweep_id": "sweep_colend_882937402",
"incoming_emi_amount": 5000.00,
"split_ratio": {
"partner_bank_percentage": 80.0,
"nbfc_percentage": 20.0
},
"sweeps": [
{ "account": "sbi_credit_pool", "amount_inr": 4000.00 },
{ "account": "nbfc_reserve_ledger", "amount_inr": 1000.00 }
],
"reconciliation_status": "COMPLETED"
}By structuring these splits directly inside the API command payload, developers automate the interest divisions, preventing co-mingling of capital.
To clear loans instantly, the originating NBFC must align its digital underwriting rules with the partner bank's credit policies. Developers build unified credit scorecard modules. When a borrower applies, the system pulls credit logs via the Account Aggregator network, evaluating data against the joint credit criteria.
If the applicant passes the checks, the system approves the loan automatically, requesting the 80% capital pool from the bank's API. This instant workflow clears loans in minutes, improving the checkout experience.
Both co-lending partners must file regular credit audits with regulatory bodies. Platforms build automated report engines that output credit telemetry in XBRL (eXtensible Business Reporting Language) formats. These files log loan performance data, defaults, and interest splits.
Saving these reporting structures in secure cloud databases ensures compliance with central bank disclosure rules. Certified access controls shield borrower data, protecting user privacy during compliance audits.
Join 2,300+ product leaders getting one actionable growth breakdown every day — across 12 industries. No fluff, just hard product reviews and India benchmarks.
Deploying these compliance pipelines requires close collaboration between engineering leads, product managers, and security auditors. Operations teams should establish automated metrics dashboards to monitor payment gateway success rates, transaction times, and database write queues continuously. Running regular simulated tests and mock compliance audits helps platforms identify integration bottlenecks early, ensuring system databases remain secure, compliant, and ready for regulatory inspections under standard Indian frameworks (such as RBI, SEBI, or DPDP Act guidance). By reviewing transaction telemetry logs and scheduling vulnerability scans every 6 months, teams protect client information and maintain operational standards.