Digital lending software for the loan after your app approves it
Lokta, the agentic loan servicing platform
You built the app your borrowers use. Keep it. Once a loan is approved, the loan record behind it sits on Lokta: the schedule, every repayment and bounced NACH debit, servicing requests, collections and the accounting entries each one creates.
Your app keeps the borrower. Your loan record sits on Lokta.
You've probably built the front end already: onboarding, KYC, the credit decision and the screens a borrower opens each month. The strain shows after approval. If your app, your servicing system and your finance ledger each hold their own version of a loan, someone in lending operations reconciles the differences by hand, and the more loans you book, the more of that work there is.
On Lokta the loan and its accounting entries sit on one record, so there's no second ledger to match at month end. It's built for the lender who wants to show RBI every receipt and approval from its own record.
Own the borrower experience.
Onboarding, KYC, the credit decision and every screen the borrower sees stay with you.
One record for the loan after approval.
Schedules, receipts, charges, servicing changes, DPD and GL entries sit on one record. Your app reads it through Lokta's published REST API.
Approve what changes the loan.
A proposed waiver, reschedule or foreclosure quote goes to an authorised approver, and the decision stays on the account.
What Lokta handles after your app approves a loan
Each stage ends on the loan's record. Most start in your app, which shows the borrower the result while Lokta keeps the history behind it.
Booking
- In your app
- The borrower sees the loan go live.
- On the record
- The approved loan arrives from your own origination system by API, and its schedule follows the product version it was booked under. Where a loan goes out in tranches, what the borrower owes is worked out again from the amounts and dates actually paid out.
Repayment
- In your app
- What's due and what's been paid.
- On the record
- Receipts apply under your allocation rule. When a NACH debit bounces, Lokta logs it as a payment exception. The instalment is still owed, and it counts toward DPD.
Servicing requests
- In your app
- The borrower asks for a statement or a foreclosure quote.
- On the record
- Statements, schedules and charges come from the same record your app reads. A foreclosure quote the agent drafts goes to an approver first. The servicing agent answers WhatsApp and SMS questions from the loan's record and approved knowledge.
Delinquency
- In your app
- Reminders the borrower can act on.
- On the record
- DPD is worked out from what's still due. For a standard instalment loan, more than 30 days overdue shows SMA-1 and more than 60 days shows SMA-2; borrower-level NPA rules apply separately. Before a collections message goes out, Lokta checks the contact hours and the borrower's consent. Collections on Lokta today means DPD and product queues, promises to pay, and WhatsApp and SMS messages. A dialer, a field app and agency workflows are on the roadmap, and there's no voice bot.
A worked example on an assumed loanTake an ordinary instalment loan with no other overdue amounts. The borrower's EMI is ₹5,400, due on the 5th of each month. The 5 April NACH debit bounces, Lokta records a payment exception, and the instalment stays due on the record. The 5 May debit bounces too. At the end of 6 May the April instalment has been overdue for more than 30 days, so the loan shows SMA-1 with ₹10,800 overdue, before any bounce or penal charge. On 8 May the borrower pays ₹10,800 through your app, the receipt posts under your allocation rule, and DPD is worked out again from whatever's still due. Your app can show the new balance.
Accounting
- In your app
- Nothing. This one's for your CFO and finance team.
- On the record
- Every financial event posts double-entry to your mapped GL heads, and reviewed journals sync to Tally on a schedule.
The RBI rules that follow a digital loan after disbursal
For NBFCs the digital lending rules sit in Chapter III, paragraphs 6 to 30, of the Reserve Bank of India's Credit Facilities Directions, 2025, as updated on 15 July 2026. Paragraph 6(7) keeps you fully responsible for what your lending service providers do. You'll need to produce the evidence yourself, and that's easier when it's already on your record. Four of those rules are below.
Repayments go straight into the NBFC's bank account, with no third-party pass-through or pool account (paragraph 10(2)). Three narrow exceptions are written in.
- What the record has to show
- Each receipt, the account it landed in and its date.
- Where Lokta stands
- Lokta matches bank statements and provider collection files to the ledger. Money it can't match waits in suspense, with an ageing view.
The Key Fact Statement and other signed documents go to the borrower's verified email or SMS automatically (paragraph 9(3)).
- What the record has to show
- Which KFS the loan was booked under, and when each document went out.
- Where Lokta stands
- Each product version carries its own terms, charges and KFS, and a loan stays tied to the version it was booked on. Ask us how send times are kept for your channels.
The borrower can leave during a cooling-off period of at least 1 day, paying principal and proportionate APR with no penalty (paragraph 11).
- What the record has to show
- The window's end date and the exit amount.
- Where Lokta stands
- Ask us how we'd handle the cooling-off window for your products. We'll answer it in the first conversation.
Recovery contact follows the Responsible Business Conduct Directions, which bar calls before 8 a.m. or after 7 p.m. (paragraph 100 there, applied through paragraph 6(5)).
- What the record has to show
- Each contact attempt and when it happened.
- Where Lokta stands
- Lokta's collections channels are WhatsApp and SMS, and contact hours and consent are checked before each message goes out.
Connect your app without rebuilding it
Your engineers build against an OpenAPI 3.1 specification generated from the code, covering 314 published REST endpoints. The version sits in the path (/v1, /v2), so a new version ships beside the old one. Your app doesn't break. Backend services sign in as OIDC service principals through Keycloak.
Included as standard: Cashfree for payments, Digio for KYC if you want it, Gupshup for SMS and WhatsApp, SMTP email, credit-bureau reporting and Tally. Bureau pulls and Account Aggregator get wired in after you've chosen providers. Each lender gets its own deployment on AWS, hosted in India for Indian lenders, or Docker images inside your own VPC on the Enterprise tier.
You get a demo built on your own use cases, and a sandbox to test against. Start with the developer documentation.
Three ways to hold the loan behind your app
Each path trades setup effort against how much of the record you hold yourself. If your platform holds loans for several lenders, see loan management for embedded finance.
Keep your current LMS behind the app.
There's no migration. That's the appeal. You'll want to check how it takes events from your app, and how often your team reconciles the two.
Hold the post-approval book on Lokta, with your app in front.
Your app stays yours, and repayments, servicing, collections and accounting share one record. You take on a migration, proven on a parallel run before you switch. The FAQ below covers how that works.
Build servicing in-house.
You'll control every line. You'll also own the ledger, the GL mapping and every RBI amendment for as long as the book is live.
Built by the team behind Apache Fineract, the open-source lending core at the Apache Software Foundation. Meet the team.
How to choose digital lending software for the loan after approval
A feature list for a digital lending platform doesn't show how the system behaves once loans are live. These seven checks do. Your team can run each one in a demo or the sandbox, and we'll run all seven on your own use cases.
- API
- Have your engineers call the sandbox for a loan's schedule, dues and receipts, and ask how a new API version ships without breaking the app.
- Failed debits
- Bounce a NACH debit in the demo and watch the record: the instalment stays due, DPD keeps counting, and your team sees the exception.
- Fund flow
- Upload a bank statement with one receipt that matches no loan. It should wait in suspense with an ageing view, not post to a loan.
- Product versions
- Change a charge on a live product and check that loans already booked keep the terms and KFS they were sold on.
- Collections contact
- Queue a collections message for outside your contact hours, and another for a borrower with no consent on file. Both should be held before they send.
- Approvals
- Propose a waiver and follow it: who approves it, what posts, and what the audit trail shows afterwards.
- Accounting
- Ask to see the journal entries behind one repayment and one bounce charge, mapped to your GL heads.
Frequently asked questions
- What is digital lending software?
- Software a lender uses to lend through an app or website. RBI calls that app a digital lending app (DLA). Origination software handles the application and the credit decision. Loan management and servicing software holds the loan after approval: the schedule, repayments, servicing requests, collections and the accounting entries behind each of them, for as long as the loan is live. Lokta covers the second part through Loan Management and AI Loan Servicing, and you keep the first.
- How does digital lending work?
- The borrower applies in your app or on your website. You run KYC and the credit decision, and the loan is disbursed. RBI treats this as digital lending: a remote, automated process that takes in customer acquisition, credit assessment, approval, disbursal, recovery and customer service. After disbursal, the borrower repays by NACH or another mandate, or through a payment gateway. Your team handles servicing requests such as statements and foreclosure quotes, follows up on overdue amounts, and keeps the accounts until the loan closes. Some RBI rules keep applying after disbursal: repayments, for example, go straight into the lender's bank account, with three narrow exceptions. Lokta holds the record from the day your app passes it the approved loan.
- Does Lokta include loan origination?
- No. Loan Origination is on the roadmap. No release date is published. Your app and your LOS keep the application and the credit decision, then pass approved loans to Lokta.
- Do we have to rebuild our app?
- You shouldn't have to. Your app connects to Lokta's published REST API for the loan's schedule and repayments, whether it's written in Kotlin, Swift or React Native. Your engineers map the app's calls to that API and test the borrower journeys in the sandbox first.
- Can the AI change a loan on its own?
- No. The agent proposes and an authorised user approves. Nothing the agent proposes runs until that approval, and the core posts it only after. Both steps stay on the audit trail, so you'll always know who signed off.
- Can we move a live book onto Lokta?
- Yes. Your book moves onto Lokta's ledgers, and for a while a test batch of loans lives on both platforms. Cutover waits until every balance matches, and your old system stays live until it does. Expect a migration assessment of 2 to 4 weeks, then 4 to 8 weeks to migrate and go live. We agree the parallel run timeframe with you. A new book with nothing to move typically goes live 4 to 6 weeks after signing, depending on the loan product category.
Bring the app you have and the book behind it
Tell us how loans reach your app or website, where they go once they're approved and where servicing takes your team the most time. We'll walk through how that book would sit on Lokta. The three pricing tiers are published.