Digital Lending Platform

Lending Infrastructure
That Survives the Audit.

One deployment. Multiple lender tenants. The full loan lifecycle for regulated NBFC-class lenders — Sharia-native by configuration, built for any market: jurisdiction is config, not a rewrite.

Origination  ·  Management  ·  Collections  ·  Conventional & Islamic finance

The Full Lifecycle

Seven Stages.
One Platform. No Handoffs.

Most lenders stitch origination, servicing, and collections from separate vendors — then reconcile the seams by hand. dhanavega runs the whole lifecycle in one deployment, each stage owned by a named domain module.

1

Configure

Admin-Config

Publish the product: pricing, charges, policy, Sharia toggle. Versioned and immutable.

2

Originate

LOS

Lead to application. Zero-Form IDP pre-fills fields straight from the borrower’s documents.

3

Underwrite

LOS

Rules decide. The score advises — with a SHAP snapshot filed for the regulator.

4

Disburse

LOS

Maker-checker approval, idempotent payout. A retry can never disburse twice.

5

Service

LMS

Schedules, repayments, restructures. Decimal money, Hijri-aware calendars.

6

Collect

LCS

DPD buckets, agent queues, settlements — every action hash-chained.

7

Close

LMS

Clean closure with the full trail intact, first click to last rupee.

Platform Capabilities

Built for Lenders Who
Answer to a Regulator.

Every capability below is engineered around one question: can you defend this decision, this payout, this record — two years from now, under oath?

The Config Plane

Config-Driven Product Builder

Publish a compliant lending product — pricing, charges, policy, Sharia toggle — from a 46-table config plane. Every publish is versioned and immutable. Every loan is stamped with its product_id and version_id, so the rules it was booked under are frozen forever. Launching in a new market or shipping a new product is a configuration change, not a fork.

46-Table Config PlaneVersioned PublishesRules Frozen Per LoanMarket as Config

Explainable Credit Scoring

Every score ships with an immutable SHAP snapshot. Rules decide; the model advises. When a regulator asks why, the answer is already on file.

Zero-Form Document Intelligence

IDP extracts fields from the documents borrowers already have, with confidence and provenance badges — gov-verified, extracted, or conflict. Nobody retypes their own payslip.

Fraud Signal Scoring

LOW, MED, HIGH risk bands computed independently of the credit decision. Fraud posture never contaminates creditworthiness — or vice versa.

Tamper-Evident Audit Log

A per-tenant SHA-256 hash chain, written by a database trigger the application role cannot touch. Every state change is chained to the one before it. Deleting a record breaks the chain — and the break is the evidence. Auditors get a trail that proves itself.

Maker-Checker Kernel

Dual approval on regulated writes, idempotency keys on every mutation, RFC 9457 problem-details errors. Operations are safe to retry and impossible to replay.

Multi-Tenant Isolation

Postgres row-level security as an enforced database floor — not an app-layer promise. Identity via Keycloak OIDC; the platform stores no passwords.

Sharia-Native Money Model

Murabaha, Ijarah, and Tawarruq as a per-product toggle, not a code fork. Hijri calendars and decimal Money primitives throughout — float never touches a rupee or a riyal. One platform serves conventional and Islamic books side by side.

Governed AI

AI a Regulator
Can Question.

Black-box scoring fails the first audit it meets. dhanavega treats every credit score as evidence: explainable at issue, immutable at rest, reproducible on demand.

Rules first, model second

Eligibility is decided by published policy rules. The ML score is advisory — it can inform an underwriter, never overrule the rulebook.

Deterministic by contract

Same inputs, same score, every time. An enforced additivity invariant makes the arithmetic checkable by anyone — including the regulator.

Explanations filed, not generated later

Every score is stored with an immutable SHAP snapshot at decision time. Two years on, the “why” is the original — not a reconstruction.

invariant: base + Σ shap == score  // enforced, not aspirational
Score explanation · APP-2041SHAP snapshot · immutable
Base score671
Salary stability+38
Tenure at employer+21
Recent enquiries−12
Utilization trend−6
Final score712
671 + 38 + 21 − 12 − 6= 712 ✓

Illustrative decision record. Factor weights vary by product version.

Architecture & Trust

The Boring Guarantees
That Win Due Diligence.

Five domain modules — Admin-Config, LOS, LMS, LCS, Customer — on a NestJS modular monolith, with a Python/FastAPI ML service and a jobs tier running a transactional outbox over Redis Streams. Designed to be inspected.

SHA-256

Hash-Chained Audit

Per-tenant hash chain written by a database trigger the application role cannot touch. The trail proves its own integrity.

Postgres RLS

Isolation at the Database Floor

Row-level security enforced by the database, not the app layer. Keycloak OIDC handles identity — no password store to breach.

RFC 9457

Maker-Checker Kernel

Dual approval on regulated writes. Idempotency keys on every mutation. Structured problem-details on every error.

K8s + Helm

Runs Where the Regulator Says

Cloud-portable and on-prem capable. OpenTelemetry traces and Prometheus metrics on every service, so operations are observable in either home.

CI Gate

Market-Pluggability, Enforced by the Build

A CI gate fails the build if a market literal — CIBIL, eNACH, SADAD, INR — leaks into shared runtime code. Jurisdiction stays in config because the pipeline refuses anything else.

118
Data entities
170
Screen specs
29
Locked architecture decisions
46
Tables in the config plane

PostgreSQL schema-per-module · KMS-encrypted object storage · retry, backoff, dead-letter and watchdog on the jobs tier · 12-sprint delivery plan

See It Running

Walk the Golden Path, End to End.

One demo, one loan: lead to KYC to score to sanction to disbursal to first repayment — with the SHAP explanation, the maker-checker approvals, and the hash chain behind every step. Bring your product sheet; we’ll show you how it becomes configuration.

Platform kernels live in production · First NBFC tenant (consumer brand PayDay+) in active build · New markets are config packs, not rewrites