Unified Lending Interface: what ULI changes for lenders and for the people sourcing loans
The Unified Lending Interface is a Reserve Bank of India initiative that gives lenders consent-based, standardised API access to the data needed for a credit decision - land records, satellite and agri data, KYC, GST and account aggregator flows - through a single interface. Its purpose is to cut the data-collection portion of underwriting, particularly for MSME and agricultural credit where verification, not credit judgement, causes most of the delay.
For a farmer seeking a crop loan or a small trader seeking working capital, the slow part of borrowing has never been the credit decision. It is proving who you are, what you own and what you earn, in a form the lender's system will accept - land records from one state portal, a GST return from another, bank statements assembled by hand.
ULI is India's attempt to make that data layer standard rather than bespoke. The way to think about it is UPI's logic applied to credit information: one interface, consent-driven, with the plumbing hidden from both the lender and the borrower.
What ULI actually provides
ULI is not a lending platform and does not make credit decisions. It is a standardised, consent-governed pipe between lenders and the data sources that already exist but currently have to be integrated one by one.
- Standard APIs to state land records, which removes the largest single obstacle in agricultural and rural secured lending.
- Satellite and agronomic data for crop and yield assessment, useful where income cannot be documented conventionally.
- Identity and KYC verification services in a common format.
- GST and transaction data relevant to MSME cash-flow-based lending.
- Account Aggregator flows for bank statement data, with explicit borrower consent.
- A consent architecture, so the borrower authorises each data pull rather than signing a blanket permission.
ULI standardises the inputs to underwriting. It does not standardise the policy. Two lenders on ULI with the same borrower can and should reach different decisions - the difference is that both reach them in hours rather than weeks.
Where the time saving comes from
In a conventional MSME or agri file, the elapsed time is dominated by collection and verification. When those steps become API calls, the shape of the process changes rather than just its speed.
| Step | Conventional process | With ULI-style data access |
|---|---|---|
| Identity and address | Physical documents, manual verification | Verified digitally at sourcing |
| Land ownership | Visit to the revenue office, days to weeks | API pull against the state record |
| Income or yield assessment | Field estimate or informal documentation | Satellite and agronomic data, GST flows |
| Banking behaviour | Statements collected and keyed in | Account Aggregator with consent |
| Overall | Weeks for a rural secured file | Hours to a few days |
What a lender has to change internally
Access to faster data does not by itself produce a faster loan. Most lenders discover that their internal sequence, built around waiting for documents, does not compress just because the documents arrive instantly. The queues simply move.
- Rebuild the credit policy around verified digital attributes rather than around document checklists.
- Move eligibility and data pulls to the sourcing stage, so the field team sees the decision inputs before the customer stands up.
- Redesign approval routing - when data arrives in minutes, a deviation waiting a day for a human becomes the whole turnaround.
- Fix consent handling in the field app: the borrower must understand and authorise each pull, and that record must be retrievable.
- Retrain field staff away from document collection towards need assessment and relationship work, which is where their time now creates value.
What it means for field sourcing teams
The most underrated consequence of ULI-style infrastructure is what it does to the field visit. A rep who can verify land, identity and banking during the conversation is no longer a courier for paperwork; they can discuss an indicative amount on the spot and close the file in the same sitting.
That is only true if the mobile workflow supports it. If the rep still has to photograph documents and hand them to an operations desk, the lender has bought faster data and kept the old process around it.
Where Toolyt fits
Toolyt is the field layer that makes this usable: consent capture and digital verification at the customer's location, eligibility and obligation checks computed on the phone, deviation flags raised before login, and files that reach credit complete. Whatever the underlying data rails, the sourcing team works in one mobile journey rather than across a portal, a WhatsApp group and a document bag.
Frequently asked questions
- What is the Unified Lending Interface?
- ULI is a Reserve Bank of India initiative providing lenders with standardised, consent-based API access to the data required for credit decisions - including land records, KYC, GST, satellite and agronomic data, and Account Aggregator bank data - through a single interface rather than bespoke integrations with each source.
- How is ULI different from UPI?
- UPI standardised payments; ULI applies the same idea to lending data. UPI moves money between accounts, while ULI moves consented borrower information to lenders. Neither makes a decision - they are infrastructure that removes friction from the transaction around them.
- Who benefits most from ULI?
- Borrowers whose data is hardest to assemble: farmers needing land-record verification, and small businesses whose income sits in GST filings and bank flows rather than in audited statements. For lenders, the gain is largest in rural secured and MSME books where verification dominates turnaround.
- Does ULI replace a loan origination system?
- No. ULI supplies verified data; the loan origination system still runs the workflow, policy, deviations, approvals and disbursement. Lenders connect the two so that data arrives in the origination flow automatically rather than being collected and keyed in.
- Is borrower consent required for ULI data pulls?
- Yes. The architecture is consent-driven - each data request is authorised by the borrower, and the consent record must be maintained. This is a practical design requirement for any field or digital journey built on top of it.
Related to this
Want to see this running on your own data? Book the lending operations demo