NBFC software and digital lending platforms built around how you actually lend

Custom lending software for NBFCs, digital lenders and co-operative institutions - built to the RBI digital lending guidelines, CKYC integration, India-hosted data. Eight years, 730+ systems shipped.

  • KFS generated by the system to the RBI mandated format, before sanction, every time
  • Disbursement direct to the borrower's bank account, no LSP routing, enforced by the system
  • CKYC fetch, create and update - built as a named deliverable, not an assumption
  • Data in India, on infrastructure you control - the RBI digital lending guidelines require it
Book a call

30 minutes. Bring the compliance requirement that is currently a manual process.

Digital lending and loan processing context
730+ SYSTEMS SHIPPED
500+ CLIENTS WORLDWIDE
8 YEARS
25+ INDUSTRY VERTICALS
LENDING AUTOMATION

NBFC software is the operational system for a lending institution - loan origination, KYC, account management, EMI collection, portfolio reporting - built to the specific product types and regulatory requirements of the institution, not configured from a generic lending template.

The generic lending template works until your loan product is unusual - because your borrower profile is non-standard, your collection workflow is field-based, or your product combines elements the template did not anticipate. That is where compliance requirements become the hardest to meet from a system that was built for someone else.
CHALLENGES

What we keep hearing before the first call

Common bottlenecks and operational breakdowns we encounter before modernizing the workflow.

The RBI digital lending guidelines require a Key Fact Statement to be issued to the borrower before sanction, in the mandated format. The system does not generate it. Someone copies the loan terms into a template, checks it, prints it, gets it signed, and scans it. It is done correctly most of the time.
The guidelines are clear: the loan amount must disburse directly from the lender to the borrower, not through a Lending Service Provider's account. If it is going through a third party first, that is a compliance breach, and the first time the auditor finds it will not be the last.
The CKYC Integration is in the roadmap. Until it is built, someone fetches the record from the CKYC registry, checks it against the form, and enters the data. The margin for error is the margin between two humans comparing two documents.
COMPLIANCE

The RBI digital lending rules that change what your system has to do

The RBI Digital Lending Guidelines (Master Direction, September 2022) require that a Key Fact Statement be provided to the borrower before the execution of the loan agreement. The KFS has to include the Annual Percentage Rate (APR), the loan tenure, the EMI schedule, the fees and charges, the cooling-off period, the grievance mechanism, and the name of the Recovery Agent authorised by the lender. The format is mandated and it has to be in a language the borrower understands. The system generates the KFS from the loan terms at the sanction stage, prints it in the required format, and records the borrower's acknowledgement on the loan file.
The guidelines prohibit disbursement of loan funds through a Lending Service Provider's account. The disbursement instruction from the system must go directly from the lender's bank account to the borrower's bank account, with no intermediate routing. We build the disbursement module to generate the payment instruction to the lender's bank directly and to record the UTR number as confirmation. The cooling-off period window is enforced: the disbursement cannot be released until the window has elapsed and the borrower has not exercised the right to cancel.
The guidelines require that data relating to lending transactions be stored in India. This is an architecture decision that has to be made before the first line of code is written, not after. We build on Indian infrastructure - AWS Mumbai, Azure India or GCP Mumbai depending on your preference - and the hosting agreement is in writing before onboarding. There is no 'we will figure it out later' on data residency for a regulated institution.
The Central KYC Registry (CKYC) maintains a centralised KYC record for financial customers. NBFCs are required to upload KYC records for new borrowers and to fetch existing CKYC records before conducting KYC again. We build the CKYC integration as a named module: fetch by Aadhaar or PAN, create a new record for new borrowers, and update an existing record where the borrower's details have changed. The CKYC record is stored on the borrower profile and linked to the loan file.
Core Architecture

What goes into an NBFC platform we build

Loan origination and credit assessment

Application capture, document collection, credit bureau integration, internal scoring, credit committee workflow, sanction letter and KFS generation.

KYC, CKYC and AML

Aadhaar e-KYC, PAN verification, CKYC fetch and upload, AML screening against the specified lists. Borrower profile on the loan file.

Loan account management

Account creation on sanction, disbursement instruction with direct fund flow, EMI schedule, interest accrual, pre-payment and foreclosure.

Collections and field recovery

Demand notice generation, payment recording, overdue escalation workflow, field collection mobile app, recovery agent allocation.

Portfolio reporting and regulatory submissions

Portfolio at risk, collection efficiency, borrower-level outstanding. Data in the format required for RBI reporting submissions.

Grievance redressal mechanism

Borrower complaint registration, tracking through resolution, escalation to designated officers. The mandated mechanism, built into the system.

Lending institutions we have built for

Sellon Finserv and AMC Bank are names we can use. A third client, a co-operative institution, has asked not to be named.

Across eight years: 730+ systems, 500+ clients worldwide, 25+ industry verticals. Fintech and lending is a sector where we have gone deep on the compliance requirements, not just the feature set.

730+ Systems deployed
500+ Clients worldwide
8 yrs In production
25+ Industry verticals
Sellon Finserv

Sellon Finserv

India

AMC Bank

AMC Bank

India

Process

How the engagement works

1

A 30-minute call

You bring the compliance requirement or the product type that does not fit the template. We tell you whether it is ready.

2

Discovery, then a fixed-scope proposal

We map your loan products, your compliance requirements, your integrations. Fixed scope, fixed price.

3

Build, with weekly demos on your data

You see the KFS generated to the mandated format, the disbursement flow enforced by the system.

4

Implementation and go-live

Data migration, parallel running, staff training, RBI submission testing.

FAQs

Questions we get asked

NBFC software covers the operational systems an NBFC needs to run lending: loan origination and credit assessment, loan account management, EMI schedules and collections, KYC and CKYC integration, portfolio reporting, and the RBI digital lending compliance requirements. The difference between NBFC software and a spreadsheet is that the NBFC software enforces the rules consistently - the KFS is generated to the mandated format, the fund flow goes direct to the borrower, the CKYC record is fetched and stored - rather than relying on a process that a person runs correctly every time.

The RBI Digital Lending Guidelines (September 2022, updated 2023) require: a Key Fact Statement issued to the borrower before sanction, fund disbursement directly to the borrower's bank account with no LSP routing, a cooling-off period, a clear grievance redressal mechanism, and data stored in India. We build each of these as a named system feature rather than a process the team has to remember. The KFS is generated from the loan terms by the system. The disbursement instruction goes directly to the bank integration. The cooling-off window is enforced by the system before the disbursement can be released.

Yes. CKYC integration - fetching an existing CKYC record, creating a new one, updating a record - is a buildable named module. We scope it explicitly and include it in the proposal as a line item, not as assumed to be included.

Yes, though the specific compliance requirements for district co-operative banks, urban co-operative banks and multi-state co-operatives differ, and the applicable regulator (RBI, NABARD, state registrar) depends on the type and size of the institution. We scope the regulatory compliance scope during discovery based on what your institution actually requires.

In India, on infrastructure you control. The RBI digital lending guidelines require that data be stored in India. We build on Indian infrastructure - AWS Mumbai, Azure India, or GCP Mumbai depending on the client's preference - and the hosting agreement is in writing before onboarding.

Yes. Different loan products - personal loan, business loan, vehicle loan, gold loan, micro-credit - carry different origination flows, different KYC requirements, different EMI structures and different collection processes. We build the product configurator so that new products can be added without a code change for the common cases, and with a defined change process for the unusual ones.

The system tracks EMI due dates, generates the demand notice at the configured lead time, records payments when they come in, and escalates overdue accounts through the defined collection workflow. Field collection can be captured via a mobile app. The collector's record and the system record match without a manual reconciliation.

You do. Repository access, documentation and a full handover are in every contract from day one.

Ready to talk about your lending platform?

Book a 30-minute call. Bring the compliance requirement that is currently a manual process, or the loan product that does not fit your current system. We will tell you honestly whether we are the right team.

Book a call

Working from Pune with NBFCs, digital lenders and co-operative institutions across India.

Chat With Us