3.H Loan documentation

Purpose

Produce, execute, and archive every contractual artefact needed for a legally enforceable loan, with eSign / eStamp where appropriate, in a format that satisfies regulator audit and any future legal recovery.

In-scope features

Document set (per loan)

Sanction letter — formal communication of sanction with terms; pre-disbursement.
Key Fact Statement (KFS) — per RBI standardised format (Apr 2024) — see 2.4 LSP and KFS.
Loan agreement — main contract, vernacular + English, fully reflecting sanctioned terms.
Demand Promissory Note (DPN) — separately signed; payable on demand.
Personal guarantee — by promoter / director for entity borrowers.
Board resolution — for company borrowers, authorising borrowing and signatories.
Partnership authorisation — for LLP / partnership borrowers.
Hypothecation agreement — for secured loans with movable collateral.
Mortgage / MoDT — for property collateral.
NACH mandate — for repayment.
UPI AutoPay — alternate / additional mandate.
Security documents — collateral-specific.
Co-lending disclosure — names of all lenders, shares, single point of contact.
Borrower consent logs — every consent referenced with timestamp.
Privacy notice — per DPDP.
Terms and conditions — generic, versioned.

Document orchestration

Templates per product, per partner, per language; placeholder substitution.
Versioning — every template versioned; every issued document records template version.
Multi-language — at minimum English + Hindi; expand per state.

Execution rails

eSign — Aadhaar eSign (OTP / biometric where permitted) for legally valid digital signature.
eStamp — digital stamping via Stock Holding Corporation / SHCIL APIs through vendors.
Physical signing fallback — for borrowers who can’t / won’t eSign.
Witness flow — where required.
Co-applicant / co-borrower signing — multi-party sequence.

Vendor abstraction

Vendor routing — eSign / eStamp vendor selected per loan / borrower / state, with fallback.
Vendor cost optimisation.

Out of scope

KFS computation (APR formula) — in 3.E / KFS service.
Sanction itself — in 3.F.
Disbursement — see 3.I.

Key entities

Template — versioned per type / product / language / partner.
Document — issued instance; references template version.
EsignSession — per signer, per document.
EstampSession — per document.
MandateInstrument — NACH / UPI AutoPay.
EvidencePackage — bundle per loan.

Key workflows

Sanction issuance — sanction approved → KFS + sanction letter generated → borrower acknowledges KFS → sanction letter eSigned.
Agreement execution — loan agreement + DPN + PG generated → multi-signer eSign flow → eStamp → executed copy in DMS.
NACH mandate — generated → borrower authorises (paper / eNACH digital) → submitted to NPCI via sponsor bank → activated.
Co-lending docs — co-lending disclosure addendum added to all relevant docs.
Document re-issue — minor corrections → versioned re-issue with audit trail.
Evidence package on demand — for audit / legal / RBI inspection.

Integrations

eSign vendors — Leegality (leegality.com), Digio (digio.in), SignDesk (signdesk.com), NSDL.
eStamp — same vendors; SHCIL e-stamp paper APIs.
NACH / eNACH — Digio DigiCollect, NPCI BBPS / NACH via sponsor bank.
UPI AutoPay — NPCI via PSP partner.
PDF generation engine (server-side: wkhtmltopdf, Puppeteer, PDFKit; or a vendor SaaS).
DMS — internal or vendor (e.g., DocuSign Vault, AWS S3 with retention).

APIs

POST /documents/sanction/generate.
POST /documents/agreement/generate.
POST /esign/sessions — start eSign for a doc.
GET /esign/sessions/{id}.
POST /estamp/sessions.
POST /mandates/create.
GET /mandates/{id}/status.
GET /loans/{id}/evidence-package.

Events emitted

document.generated
kfs.acknowledged
esign.completed / esign.failed
estamp.completed
mandate.registered / mandate.active / mandate.failed
evidence_package.assembled

Edge cases

eSign fails repeatedly — fallback to alternate vendor / paper.
eStamp state-paper unavailable — vendor failover; some states issue intermittently.
Borrower’s Aadhaar OTP fails — alternate auth path.
Multi-signer flow stalls — automated nudges; expiry policy.
Document content edit after eSign — invalid; re-issue with new version.
NACH mandate rejected by sponsor bank — error code-specific remediation; bank account re-validation.
Co-applicant out of country — Aadhaar eSign unavailable; legal review of alternatives.
eStamp duty changes mid-flow — recompute and re-issue.

Compliance touchpoints

IT Act, 2000 — eSign legal validity; Aadhaar eSign and DSC are valid digital signatures.
Indian Stamp Act + State stamp laws — stamp duty applicable per state; eStamp accepted where notified.
RBI KFS standard — see 2.4.
RBI Digital Lending Guidelines — KFS prerequisite to disbursement.
NACH rules — NPCI procedural guidelines.
DPDP — retention and access controls.
Outsourcing MD — eSign / eStamp / DMS vendors governed.

MVP vs production

Feature	MVP	Production
Sanction letter + KFS + agreement + DPN + PG templates	✓ (English + Hindi)	All 11+ languages
eSign	✓ (single vendor)	Multi-vendor routing
eStamp	✓ (basic states)	All states
NACH	✓ (eNACH preferred)	+ UPI AutoPay
Co-lending disclosure addendum	✓	✓
Multi-signer flow	✓	✓
Evidence package	✓ (on-demand assembly)	✓ (pre-computed for active loans)
Document versioning	✓	✓
Searchable DMS	✓	Full-text + metadata
Hypothecation / mortgage docs	(Phase 4, only with secured products)	✓