Outcome 01
Underwriting cycle from 3 days to 30 minutes
AA discovery + documents-KYC + credit-risk + default-prediction run in one orchestrated flow; the feature-weight bundle and the Courtroom signature return in the same response.
For NBFCs and bank lenders
Compress underwriting from three days to thirty minutes — without losing the audit trail.
Credit risk with feature-weight attribution, alternative-data scoring for thin-file applicants, document verification at scale, and a Courtroom-signed bundle on every decision your risk team can replay years later.
A mid-size NBFC underwrites 5,000 personal-loan applications a day with a 30-minute median cycle and a feature-weight attribution on every decline.
Marketing claim
Credit-risk scores with SHAP-level explainability and Courtroom signatures.Note ·The borrower receives a plain-language explanation of any decision (supporting the DPDP §11 access right); SHAP attributions are operator-facing and are translated into plain-language reasons in the borrower-facing portal.
The three outcomes a partner buys
What you actually get.
- Outcome 02
Explainable decline that holds up to a DPDP §11 access request
Explainable feature weights are operator-facing and are translated into plain-language reasons in the borrower-facing portal — the regulator-mandated explanation is written, not vague.
- Outcome 03
Thin-file scoring on alternative data
Gig-worker payouts, fuel spend, AA-discovered cash flow, rent receipts — every signal carries its provenance and is replayable from the audit ledger.
Integration · Day 1 → Day 90
Curl in five minutes.
- Day 101
Sandbox keys provisioned. The lender's risk team POSTs the first test application through the credit-risk endpoint and reads the feature-weight response.
- Day 702
Documents-KYC wired against the lender's existing intake. PAN and Aadhaar bundles flow through with the UIDAI 8-digit mask applied.
- Day 3003
Shadow scoring goes live alongside the existing model. Both scores arrive on the underwriter's screen; overrides are captured and routed back to the feedback loop.
- Day 9004
Production cutover on the first product line. The risk committee has replayed every override pattern and signed off on the feature-weight-to-plain-language template.
Models powering this vertical
Specialised models, one envelope.
Compliance · for the regulator's question list
Written into the architecture.
- RBI · Digital Lending Guidelines
Decision reasoning surfaced in the borrower-facing channel; no dark-pattern nudges, no streak guilt-trip — explicit alignment with the September 2022 digital-lending guidelines.
- DPDP §11 · access & explanation
Every decline carries a plain-language reason set translated from the feature-weight attribution; the borrower receives the explanation — supporting the DPDP §11 access right.
- RBI · Account Aggregator
AA-driven discovery is mediated by a licensed AA; Mukodi is the FIU, the bank is the FIP. The consent bundle is captured alongside the score for replay.
- RBI · Outsourcing of IT Services
Retention windows and incident reporting cadence aligned with the RBI master direction. Vendor DPA on file; sub-processor list on the security page.
A typical week
What the integration feels like once live.
Monday morning
Weekend applications roll in; the override report names the ten cases where the underwriter went against the model and the four patterns that emerged.
Tuesday afternoon
A drift signal on the default-prediction band fires through the self-healing observatory. The proposed retrain lands in the risk team's review queue.
Thursday standup
Cost-budget WARN fires at 80% on the credit-risk meter. Slack surfaces the call breakdown; the team raises the budget for the seasonal peak.
Friday closeout
Compliance pulls the week's audit slice and replays every decline that was appealed. The chain verifies end-to-end; the attestation files itself.
See it as a story
Related user journeys.
Partner FAQ
The straight answers.
How long does an integration take?
Most partners go from sandbox keys to a shadow-mode production wire in seven days. Full cutover lands by Day 30–90 depending on which product lines you light up and how many sit on your side of the integration.
What does pricing look like?
Per-call usage on the live endpoints, with a transparent cost-budget meter and WARN + STOP thresholds you control. The /developers page has the public price card; volume discussions happen on the partnerships call.
How is the audit trail structured?
Every model output, every override, every webhook delivery — HMAC-chained and signed. Each row links to the prior HMAC, so a tampered row breaks the chain at verification time. The chain is exportable on request.
Who handles compliance with our regulator?
You do — Mukodi is your data processor under DPDP §8 and your IT-outsourcing vendor under the RBI master direction. We furnish the artefacts (DPA, audit chain, retention attestation) that satisfy your filings.
What happens if a model drifts or misbehaves?
Drift fires through the self-healing observatory and a retrain proposal lands in your review queue. Production rollout is gated behind your TOTP approval; rollbacks are one click and a 6-hour cooldown.
Can we keep our own model in the loop?
Yes. The Mukodi verdict can run in shadow alongside your model, with both scores delivered to your underwriter or SOC operator. Overrides flow back into the feedback loop and ship as labels to the next training cycle.
Hire the house · Lenders
Ready to talk?
Sandbox keys are free. The integration call is a single thirty- minute slot. Production cutover lands by Day 30–90 depending on which product lines you light up.