3.B Application journey

Purpose

Take a qualified lead through a clean, friction-minimised application flow that captures every data point underwriting needs, with consent and audit trail intact, in 15 – 40 minutes for a typical SME borrower.

In-scope features

Borrower onboarding

Mobile-OTP entry.
PAN entry and validation.
Borrower-type capture — individual / proprietorship / partnership / LLP / private limited / public limited / HUF / trust.
GSTIN entry and validation (if applicable; some SMEs are below GST threshold).
Udyam registration number (if applicable).
Business name and trade name.
Date of incorporation / commencement.
Industry / NIC code.

Business profile

Business address(es) — registered, principal place, operational locations.
Business operations summary — nature of business, products / services, key customers, key suppliers.
Business vintage — years in operation.
Annual turnover (claimed; later cross-checked with GST and bank).
Number of employees.
Working capital cycle — typical receivable days, payable days, inventory days.
Banking relationships — primary bank, sponsor bank, all operating accounts.

Promoter / director / partner profile

For each natural person controlling or representing the entity:

Name, DoB, gender, nationality, mobile, email, PAN, Aadhaar reference.
Permanent and current address.
Photograph.
Educational / professional background (light, optional).
Shareholding / partnership stake in the business.
Other directorships (auto-populated from MCA where available).

Beneficial ownership

For entity borrowers, map every natural person owning >= 25% (companies) or >= 15% (partnerships, trusts) — directly or indirectly.
Layered ownership (holding companies, multi-tier) captured to ultimate BO.

Loan requirement capture

Loan amount sought.
Product preference — line of credit / term loan / invoice-backed / anchor-backed.
Purpose of loan — working capital / supplier payment / inventory build / expansion / receivable bridge / GST payment / salary cycle / equipment / specific invoice.
Tenure preference.
Repayment preference — bullet / EMI / structured.
Disbursement target — own account / vendor / specific account.

Existing debt capture

Existing loans with amount, lender, tenure, EMI, vintage, outstanding.
Existing credit card limits for proprietor.
Recent applications at other lenders (if borrower willing to share).

Bank account capture

Operating bank accounts — bank name, account number, IFSC, account type.
Primary collection account (NACH source).
Disbursement account.

Collateral details (only if secured product)

Property / asset details.
Valuation history.
Insurance.
Title chain.

Invoice / PO upload (only if invoice-backed product)

Invoice list with anchor, value, due date.
PO list.
E-invoice IRN cross-check.

Tally / accounting upload (optional but high value)

Tally backup / export.
Zoho Books export.
Manual P&L / balance sheet upload.

Document upload

All identity / KYC docs (subject to KYC module).
Bank statements (PDF or AA-fetched).
GST filings (auto-pulled or manually uploaded).
ITR / 26AS / AIS (if available).
Tally / accounting export.
Photographs of shop / office (geo-tagged).
Other supporting (specific to product).

Bureau pull consent (per CIC).
AA consent with vendor, scope, purpose, duration.
GST data consent.
DPDP consent — purpose-specific.
Marketing consent — opt-in for offers, communications.

Application status

Borrower-facing tracker — every stage with timestamp.
Save-and-resume — borrower can leave and return; data persisted.
Document-pending highlights — borrower sees what’s needed.
Decision SLAs displayed.
Reasons-for-delay messaging when SLA breached.

Out of scope

KYC service flows themselves — see 3.C.
Data ingestion automation (bank statement parsing, GST pull) — see 3.D.
Underwriting decisioning — see 3.E.
Document generation (sanction, agreement) — see 3.H.

Key entities

Application — central record, with status.
BusinessProfile.
Promoter / Director / Partner / Proprietor.
BeneficialOwner (graph for multi-tier).
LoanRequirement — within Application.
ExistingDebt — array.
BankAccount — for borrower; multiple per Application.
Collateral — if secured.
Consent — array, with type, scope, timestamp, version, IP, device.
Document — array of uploaded artefacts.

Key workflows

First-time application — full data collection over 5–7 screens with save-and-resume.
Repeat application — pre-filled, light deltas, accelerated flow.
Co-applicant / co-borrower — when more than one promoter signs.
Document deficiency — automated nudges, partial submissions, retry.
Consent re-capture — for expired consents or expanded scope.

Integrations

Read-mostly from external systems:

PAN verification API (NSDL, Karza, Perfios).
GSTIN verification + summary (GST APIs via GSP).
Udyam verification (Udyam portal direct).
MCA company / director lookup (MCA APIs via Karza / Signzy / Probe42 / Tofler).
CIN / LLPIN / DIN verification.
Bank account verification — penny drop (Razorpay / Cashfree / Setu / Decentro).
Digital identity — DigiLocker fetch for OVDs.

APIs (exposed to other modules)

POST /applications — start a new application from a lead.
GET /applications/{id} — read.
PUT /applications/{id} — update (save-and-resume).
POST /applications/{id}/submit — finalise.
POST /applications/{id}/documents — upload document.
POST /applications/{id}/consents — record consent.
POST /applications/{id}/withdraw — borrower withdraws.

Events emitted

application.created
application.section_completed (per section)
application.submitted
application.withdrawn
consent.captured / consent.revoked
document.uploaded / document.rejected
bo.added / bo.removed

Edge cases

Borrower abandons mid-application — save state, follow-up via SMS / RM.
PAN / GSTIN mismatch between application and verification — block submit; show clear reason.
Multiple promoters with conflicting data — UI to reconcile.
Borrower changes bank account between application and disbursement — re-do penny drop + NACH mandate.
GSTIN cancelled between application start and submit — block and decline.
Application restarted on a different channel — deduplicate; resume from saved state.
Consent revoked mid-application — application paused; borrower re-prompted.
Renewal application picks up stale data — refresh GST and bank automatically; bureau on a defined cadence.

Compliance touchpoints

Digital Lending Guidelines — vernacular language, KFS (deferred to documentation module but planned), borrower-data privacy, RE disclosed.
DPDP — every consent purpose-specific and revocable.
KYC MD — KYC method selected here; downstream module fulfils it.
Outsourcing — if a third-party form-builder / SDK is used in the journey, must be governed.
Beneficial ownership — captured per PMLA.

MVP vs production

Feature	MVP	Production
Vernacular toggle	English + 1 regional initially	All 11+ official languages
Save-and-resume	✓	✓
Multiple promoters / partners	✓	✓
Beneficial-owner graph	Simple (single-tier)	Full multi-tier
Co-applicant flow	(Phase 2)	✓
Tally / accounting upload	(Phase 2)	✓
In-app consent UX	✓	✓
Mobile-optimised flow	✓	✓
Branch / DSA-assisted mode	✓	✓
RM / DSA application creation on behalf	✓	✓
Hindi / Marathi / Tamil at MVP	English + 1	+ 5 languages

Related: 3.C KYC / KYB, 3.D Data ingestion, 3.O Admin for product / template configuration, 2.3 Digital Lending Guidelines, 13.4 Application backlog.