Business Narrative
We are acting as the Lead Architect for SwiftCred, an exploding FINTECH startup operating as a Lending Service Provider (LSP). SwiftCred does not lend its own money; it partners with a Regulated Entity (an NBFC) to provide instant ₹20,000 personal loans to college students.
Despite a massive influx of users driven by an advanced AI underwriting algorithm, the operational backend of SwiftCred is currently trapped in a manual nightmare.
The CEO demands an entirely automated, API-driven solution to solve two massive bottlenecks:
- The Disbursal Bottleneck (Pay-Outs): When the AI approves a loan, SwiftCred compiles a CSV file and emails it to the NBFC at 5:00 PM. The NBFC manually uploads the CSV to their corporate banking portal. The student receives their money the next morning. It is too slow to compete in an "Instant Loan" market.
- The Collection Nightmare (Pay-Ins): To collect EMIs, SwiftCred texts students a static, generic UPI QR code. The student scans it and types in "₹2,000". SwiftCred receives thousands of unidentifiable ₹2,000 NEFT/UPI deposits a day. The finance team spends 80 hours a week staring at bank statements, manually trying to trace UTR numbers to figure out which specific student paid their EMI.
The Trap: The Digital Lending Guidelines (DLG)
A Junior Developer might suggest building a generic API integration where SwiftCred's corporate account automatically transfers the money out, and collects the money back in.
This architecture creates direct supervisory, partner, and business-continuity risk.
Modality 1: The Fund Routing Modality. Under the RBI's stringent Digital Lending Guidelines (DLG), an LSP (SwiftCred) cannot touch the principal loan amount. The physical Flow of Funds must be direct:
- Pay-Out: Must travel directly from the NBFC's bank account to the Borrower's bank account.
- Pay-In: Must travel directly from the Borrower's bank account to the NBFC's bank account.
If the principal loan capital ever pools or passes through SwiftCred’s corporate checking account, it creates prohibited co-mingling and shadow-lending risk.
We must build an automated, real-time, Two-Sided API Ledger without the LSP ever physically touching the capital.