LENDOS
Product Plan & Delivery Blueprint

One platform, two lending products — revised to start with the field.

A unified loan origination, management and collection platform for a field-sourced business loan and a digital salaried loan. Both are manually assessed for now, both start from an in-house onboarding app, and both share one back office, data model and collection rail — delivered module by module, priorities first.

Version 2.022 Oct 2026Updated after 2nd client callTwo products · One codebase
Overview

One software, two journeys

The business runs two lending products that share the same back office, data model and collection rails but follow different origination journeys. We build one platform with a product-type switch, not two separate systems. The first phase takes the Business Loan end-to-end — onboarding to disbursement — so operations move from instinct-based decisions to a systematic, auditable flow.

Phase 1 front door

In-house field onboarding

A staff app captures the customer in the field — data, live selfie + GPS, shop photos and documents — replacing the WhatsApp-group workflow.

Manual now · both

Manual credit decision

A credit officer decides on a single-page profile and enters the sanctioned amount. Even the "instant" salaried loan is manually reviewed (15–20 min TAT) for now.

Required

Automated collection

UPI AutoPay / eNACH mandates for recurring repayment — the one piece automated from day one for the Business Loan.

What changed since v1 (after the 2nd call):
  1. The digital salaried loan is a digital journey with manual back-office assessment — not an automated rule engine yet.
  2. The field-staff onboarding app is in-house and in Phase 1 — the front door for the Business Loan.
  3. Business Loan tenure is up to 100 days, with daily / weekly / fortnightly / monthly EMI frequencies.
  4. Added a field-verification flow: live selfie + GPS, Aadhaar address & face match, distance in km.
  5. Two guarantors (KYC + cheque + OTP) and two references are mandatory; customer cheque is captured.
  6. A manual document window for rent agreement, shop electricity bill and cheque photos.
  7. Company verification via MCA and official-email verification (next phase) for the salaried loan.
  8. Sales-agent tagging on every lead; reuse the client's existing DLT registration for OTP/SMS.
The Two Products

What we're building for

Same platform, two different borrower journeys. Both are manually assessed today; automation is added later as volume and confidence build.

PRODUCT 1 · field-sourced · Phase 1

Business Loan

Source
Field sales staff via in-house onboarding app
Borrower
Shop & business owners, and self-employed / salaried on daily repayment
Credit
Manual review on a single-page profile (maker-checker)
Disburse
Manual bank transfer; officer enters sanctioned amount
Tenure
Up to 100 days (e.g. 50 / 60 / 75 / 90)
EMI freq.
Daily · weekly · fortnightly · monthly
Security
2 guarantors (KYC + cheque + OTP) · 2 references · customer cheque
Collect
UPI AutoPay / eNACH mandate; split-sweep option
Data
PAN · Aadhaar · GST · bank (AA + manual) · rent agreement · electricity bill
PRODUCT 2 · digital journey · Phase 2

Instant Salaried Loan

Source
Digital self-service + in-house calling
Borrower
Salaried; employer verified via MCA
Credit
Manual officer review within a 15–20 min TAT (rule engine later)
Disburse
"Instant" — target ~30 min; officer enters sanctioned amount
Tenure
One-shot repayment on the salary cycle (~30–35 days)
Verify
eKYC + selfie · company (MCA) · official email (OTP/domain, next phase)
Collect
Customer-initiated (repeat / top-up); no binding mandate
Data
eKYC · employment · salary · PF/UAN · bank via AA
On naming. The daily-EMI loan can go to salaried borrowers too, so strictly it behaves like a personal loan. For the system this makes no difference — it stays the Business Loan product and we don't over-categorise. The separately-built digital product is the Salaried Loan; its automatic assessment is deferred, so it runs on the same manual decision path for now.
Architecture

One platform, three applications

A shared platform core serves a web back-office console, an in-house field-staff app, and (for the digital loan) a customer app — all wired to the same integrations.

Platform & channel map
Priority 1

Web Console

Back-office & credit team — onboarding review, decisioning, disbursement, LMS, collections, admin.

Priority 1 · in-house

Field Staff App

Staff onboard the customer from the field: data, live selfie + GPS, shop photos, document upload, sales tagging. (Full lead/beat CRM comes later.)

Phase 2

Customer App

For the digital Salaried Loan — self-service apply, eKYC + selfie, e-sign, status & repayment. KYC-compliant device permissions.

Journey · Product 1

Business Loan — field to automated collection

Field-captured lead → auto-fetched profile + manual documents → guarantors, references and field verification → manual credit decision → manual disbursement → automated recurring collection.

Business loan origination & collection flow
Design notes. Every data pull (PAN, Aadhaar, GST, bank via Account Aggregator) has a manual upload fallback, because not all banks/co-ops are integrated. A document window lets staff photograph and attach rent agreement, shop electricity bill and cheques. The credit decision and disbursement are manual — both carry maker-checker and a full audit trail. The officer sees a single-page profile and enters the amount to sanction.
Journey · Product 2

Salaried Loan — digital journey, manual decision

Digital self-service → eKYC + selfie → employer and employment verification → bank via Account Aggregator → a single-page summary a credit officer approves within minutes → "instant" disbursal.

Digital salaried loan flow
Why the assessment stays manual. The client wants the officer to retain the credit call for now — the journey is fully digital up to a single-page summary, but a person reviews it inside a 15–20 min target and enters the sanctioned amount (not the requested one). Automatic assessment is a later phase, switched on once the manual decisions prove out. Repayment is one-shot on the salary cycle, so there is no binding mandate.
Field Verification

Live selfie, location & identity match

A verification step at the start of the field journey, built from a live selfie and a geo-tagged photo. Output is a verification score attached to the credit dashboard.

Field verification flow

Location → address

The geo-tagged photo is reverse-geocoded to a street address and compared with the Aadhaar address, reporting the distance in km.

Face match

The live selfie is matched against the Aadhaar photo, returning a match percentage and a liveness / anti-fake signal.

Build vs buy

Done in-house where possible, or via a verification API (Perfios-style) — the final call depends on per-check cost once the demo & proposal land.

Modules

Modules to be built

Each module carries a priority. P1 ships first to get the Business Loan running; later items follow as volume and integrations mature.

◆

1 · Customer Onboarding & KYC

P1
  • PAN → auto-fetch profile
  • Aadhaar OCR + API authentication
  • Live selfie + GPS capture at lead
  • Minimal-entry forms · consent · de-duplication
◆

2 · Document & Data Fetch Hub

P1
  • Bank statements via Account Aggregator + manual upload fallback
  • GST turnover & returns
  • Manual document window: rent agreement, shop electricity bill, cheques
  • Bank-statement analyser · per-API cost metering (wallet)
◆

3 · Field Verification & Liveness

New · P1
  • Selfie face-match vs Aadhaar photo (%)
  • Geo-tagged photo → address (reverse geocode)
  • Aadhaar-address comparison + distance (km)
  • Liveness / anti-fake + verification score
◆

4 · Guarantors & References

New · P1
  • 2 guarantors — name, relation, mobile
  • Guarantor OTP verification + KYC + cheque capture
  • 2 references — name, relation, mobile
  • Customer cheque captured & linked to file
◆

5 · Credit & Underwriting

P1 · manual (both)
  • Single-page consolidated applicant view
  • Manual sanction; officer enters sanctioned amount
  • 15–20 min TAT target (Salaried Loan) · maker-checker
  • Reason codes; rule engine added later
◆

6 · Loan Origination & Application

P1
  • Application capture with product-type switch
  • Sales-agent tagging on every lead
  • Status tracking & pipeline
  • One codebase, two journeys
◆

7 · Sanction & Disbursement

P1 · manual
  • Sanction letter & offer terms
  • e-Sign / e-Stamp agreement
  • Manual disbursement record + bank transfer
  • Auto-disbursement switch (enabled later)
◆

8 · Loan Management (LMS)

P1
  • EMI & interest engine — daily / weekly / fortnightly / monthly
  • Tenure up to 100 days · penal & PF config
  • Repayment schedule & booking
  • One-shot repayment + repeat / top-up (Salaried Loan)
◆

9 · Collections

P1
  • UPI AutoPay mandate (up to ~100-day term)
  • eNACH + re-presentation
  • Split / daily-sweep collection option
  • Bounce handling, reminders & dunning
◆

10 · Field Staff App

P1 · in-house
  • Staff onboards field customers (not full CRM yet)
  • Customer data, selfie + GPS, shop photos
  • Document upload from the field
  • Customer-facing app for digital loan comes later
◆

11 · Admin & Configuration

P1
  • Products, schemes, ROI, PF & penal config
  • Roles, permissions, branches · sales-team tagging
  • DLT / SMS template & provider config
  • Integration / API credentials · rule-engine config (later)
◆

12 · Dashboards, MIS & Reports

P1
  • Pipeline / funnel & TAT
  • Approval vs rejection analysis
  • Disbursed register & collection efficiency
  • Per-branch & per-sales-agent performance
Integrations

Third-party integrations & ownership

KYC-licensed APIs are taken under the client's NBFC; verification & rails are arranged by us. Final selection is made on cost and service after the client shares their shortlist and demo outcomes.

IntegrationPurposeProvided byNotes
eKYC / AadhaarIdentity verification, Aadhaar e-signClient (NBFC)Licensed; client applying
PAN verificationProfile fetch & validationWe arrange—
Account AggregatorBank statement fetch (consent)Client — Perfios / DigitDemo scheduled; new NBFC onboarding rules — timeline risk; manual upload fallback
Field verification APIGeo photo → address, Aadhaar address & face match, distanceVendor (Perfios-style) or in-houseNew · decided on per-check cost
MCA company lookupEmployer verification (Pvt Ltd)We arrangeNew · partnerships not covered; new companies may be absent
Official-email verificationConfirm employer email (OTP or domain check)We arrangeNew · next phase
GSTTurnover & returnsWe arrangeBusiness Loan applicants
Credit bureau (CIBIL)Score, overdue & obligationsClient (NBFC)Consent-based
PF / EPFO (UAN)Employment & salary verificationWe arrangeConfirm API availability
UPI AutoPayRecurring auto-collectionWe arrangeVia payment aggregator
eNACHRecurring debit mandateWe arrangeSupports re-presentation
e-Sign / e-StampLoan agreement executionWe arrangeAadhaar e-sign
SMS / OTP (DLT)OTP & notificationsClient DLT + we arrange SMSReuse existing DLT registration; templates approved; buy SMS credits
WhatsApp / EmailApply-now links, remindersWe arrange—
Collections

How repayment is collected

Collection is the one flow that must be automated from day one for the Business Loan — across whichever EMI frequency the loan uses.

UPI AutoPay mandate

EMI pulled automatically on its schedule — daily, weekly, fortnightly or monthly — over a term of up to ~100 days. Primary rail for the Business Loan.

Split / daily sweep

A share of every UPI inflow is deducted at source until the period's EMI is met — suited to high digital-collection merchants.

eNACH

Recurring-debit mandate with re-presentation when a debit fails. Backed by the customer and guarantor cheques on file.

Reality check on "non-cancellable" mandates. By regulation, UPI AutoPay and eNACH mandates can be paused or revoked by the customer and require a pre-debit notification — a mandate cannot be made truly un-stoppable. The platform therefore treats bounces as normal: it re-presents (eNACH), retries, and runs reminder / dunning workflows, with customer and guarantor cheques as the fallback. We will confirm exact behaviour with the chosen payment aggregator.
Roadmap

Phased delivery

Phase 1 takes the Business Loan end-to-end so operations can start; integration-dependent and automation pieces follow as APIs and confidence land.

1
NOW · get the Business Loan running

Field onboarding → manual decision → automated collection

  • Field staff app (in-house) + web console + onboarding & KYC with live selfie + GPS
  • Data & doc hub: PAN, Aadhaar, GST; bank (manual + AA where available); document window (rent agreement, electricity bill, cheques)
  • Field verification · guarantors (KYC + cheque + OTP) & references
  • Single-page credit dashboard (manual) + manual disbursement with maker-checker
  • LMS / EMI engine (daily–monthly, up to 100 days) + Collections (UPI AutoPay / eNACH) + sales tagging & MIS
2
NEXT · digital salaried loan

Digital journey, manual assessment

  • Customer self-service apply + eKYC + selfie
  • Employer via MCA; employment, salary, PF/UAN
  • Single-page officer review (15–20 min TAT) → sanctioned amount → e-sign
  • "Instant" (~30 min) disbursal · one-shot repayment · repeat / top-up
3
AS APIs LAND · deepen verification & automation

Integrations & automation

  • Account Aggregator full coverage; GST & bureau live; official-email verification
  • Full field-verification API; split / daily-sweep collection & eNACH depth
  • Rule engine + auto-disbursement switch enabled once manual decisions prove out
4
LATER · scale

Full field CRM, customer app & multi-branch

  • Field CRM: lead & beat management, visit tracking, follow-ups
  • Customer-facing onboarding app for the Business Loan
  • Multi-branch rollout; feature parity benchmarked against market apps
Compliance & Controls

Built-in safeguards

Added to the plan as recommendations — especially important for the digital product and for the new field-verification data.

Regulatory

  • RBI Digital Lending Guidelines: Key Fact Statement, cooling-off period, direct disbursal to borrower account (no pass-through), regulated-entity branding, grievance redressal, FLDG if applicable.
  • DPDP Act 2023: explicit, auditable consent per data pull — including selfie, GPS and field-verification photos; purpose limitation; retention policy.
  • SMS / DLT: commercial SMS sent only on approved DLT templates under the registered sender; reuse the client's existing registration.
  • App permissions: only KYC-compliant permissions; no access to contacts/media; banned foreground permissions avoided.

Operational controls

  • Maker-checker on manual credit decisions and manual disbursement.
  • Full audit trail — who/what/when on every decision and money movement.
  • Consent artifacts & OTP stored for guarantors, references, AA, bureau pull and the loan agreement.
  • Field anti-fraud: liveness / AI-image detection, face match, geo + time stamps, address-distance checks.
Open Items

What we need to proceed