The panel is empty. You would be the first on it.
No lender is empanelled with Ojas Loans today. What exists is the origination side: a ten-family shelf, structured product criteria, per-entity-type document checklists, an application pipeline and a consultant desk — ready for a first lender to point them at. You would be the lender of record, keep the whole credit decision, and shape the products from the start.
- You keep the decision
- You define the products
- Ojas never lends or books a loan
- No borrower data before an agreement
- No lender is empanelled yet, so you would be first
- You keep the underwriting decision, always
- You define the products and the criteria
- No borrower data moves before an agreement is signed
- You are the lender of record — money moves borrower ↔ you
Why talk to us now
What is on offer is a built origination side and first say over what it routes — there is no volume to show you yet.
You write the box
An empty panel means no incumbent has already set the shelf's shape. The first lender defines which families it lends to, the criteria that qualify a borrower, and the commercials — rather than fitting into a structure built around somebody else's appetite.
A built origination side
The intake is not a wish: a ten-family catalogue, per-entity-type document checklists (proprietorship, partnership, private limited, LLP), plain-English eligibility on every product, an application pipeline with a real status model, and structural KYC capture that never stores a raw Aadhaar number.
Structured criteria, not free text
Eligible stages, a business-vintage floor, a monthly-revenue floor, entity and venture type are typed fields on each product, and a gate evaluates a borrower against them on the server. The homepage runs those criteria as a figure on numbers a visitor sets; the public shelf itself applies them to nobody, and no screen edits the criteria yet — they are set through the API.
One backend under the borrower
A borrower already running its orders, settlements and books on Ojas has an operating history a consultant can assemble into a file — real records rather than a shoebox of statements. It is manual work today, and computed lender scoring is not built.
Define the product once
The product record carries the amount, rate, tenure and fee bands, the collateral flag, the government-scheme tag, the per-entity-type document checklist, and structured eligibility criteria — venture stage, business vintage, monthly revenue and entity type. A gate evaluates a borrower against those criteria and returns a plain-English reason when one is not met; the homepage shows it running on numbers a visitor sets. Today an operator enters the product record for you in the console, the criteria go in through the API, and the public shelf applies the gate to nobody.
See how it worksThe criteria you set
- Venture stage
- Business vintage
- Monthly revenue
- Entity type
- Venture type
- Amount, rate & tenure bands
- Collateral flag
- Government-scheme tag
Honest scope — bands on the shelf are illustrative merchandising; every file stays subject to your underwriting, and a product appearing to a borrower is never an offer of credit.
How empanelment works
A deliberately human process — a conversation, an agreement, and a configuration. No self-serve signup, and no borrower data moves before the agreement is signed.
- 1
Introduce
Tell us who you are and the segments you lend to. We meet you to understand your credit appetite — no obligation, no data exchange yet.
- 2
Align
We agree the products, the borrower criteria that fit your box, and the commercials — the disclosed sourcing fee and the settlement cycle — in a signed panel agreement.
- 3
Configure
Your products are listed with their bands and the structured criteria that qualify a borrower for them; an operator enters them on the shelf.
- 4
Receive files
Files reach you through your partnerships contact and our consultants — relationship-led, not automated — and none has been routed to a lender before. You underwrite, sanction and disburse; money moves borrower ↔ you directly, and the sourcing fee follows disbursal.
Lender questions, answered straight
How many lenders are on the panel today?
None. No bank, NBFC, small finance bank or microfinance institution is empanelled with Ojas Loans, and no loan has been sourced through it. The borrower-facing site says so on its home page and its lender page.
Does Ojas lend or take credit risk?
No. You are the RBI-regulated lender of record — you underwrite, sanction, disburse, price the loan, and carry the risk. Ojas Loans is a Lending Service Provider and Loan Origination System: it advises and assembles the file, and never books a loan, holds a pool account, or touches loan corpus. Loan money moves borrower ↔ you directly; the Ojas ledger only ever carries Ojas's own sourcing revenue.
How would files be pre-advised?
By the two things that already exist: borrower self-qualification against the shelf, and a consultant who works the case against a document checklist keyed to the borrower's entity type — proprietorship, partnership, private limited or LLP. Your structured criteria are evaluated by the gate on the server. Since no file has yet been routed to a lender, treat that as the designed intake rather than a measured funnel.
How would you get paid?
A lender-paid sourcing fee, disclosed and agreed in the panel agreement, triggered on disbursal — never on application, and never charged to the borrower. Stated as intent, because it is: no sourcing fee has been agreed or paid, and the automated commission posting that would make each payout an auditable double-entry journal is not built in this product yet. The platform Ojas runs on does keep balanced double-entry journals for its other settlement rails, which is the mechanism this would use — but reading that as a shipped loans feature would be wrong.
Do you share borrower data?
None of it moves today, because there is nobody to move it to and no agreement to move it under. Under an agreement it would be consent-based: a borrower's documents and operating history shared through their own consent flow, never without it. Two limits worth stating now — a raw Aadhaar number is never stored, only a masked form; and Account Aggregator data pulls are a structural registry only, because a live AA integration needs FIU registration with a sanctioned operator that Ojas does not hold.
Honest scope — empanelment and file exchange are relationship-led today: your partnerships contact and consultants carry it. A self-serve lender portal, structured programmatic file-submission APIs, and webhook callbacks are not built.
Shape the panel instead of joining one
Tell us what you lend against and we will tell you exactly what exists, what does not, and what it would take. You keep full credit authority and remain the lender of record; Ojas never lends, never books a loan, and never holds a pool account.
Talk to partnershipsSee the borrower side