Outcome 01
Sub-200ms fraud verdicts via the API
Anomaly + fraud_detection + p2p_p2m_classifier run on the leg in flight; the verdict and its Courtroom bundle return in one response.
For partner banks
An intelligence layer your fraud SOC and your compliance team can both audit.
Real-time UPI fraud verdicts, document KYC at scale, transaction categorisation for downstream analytics — every output Courtroom-signed and replayable from the audit ledger.
Illustrative: a Tier-1 PSP's fraud SOC could review high-volume UPI legs with low-latency verdicts and a structured handover for the ambiguous ones once the fraud endpoint is wired.
Marketing claim
Sub-200ms fraud verdicts on the live API.
The three outcomes a partner buys
What you actually get.
- Outcome 02
KYC at the volume the bank actually sees
PAN, Aadhaar, salary slip, and address proof are ingested in any of 36 formats, OCR'd, tamper-flagged, and PII-redacted at the parquet boundary.
- Outcome 03
An audit chain the regulator can verify from outside
Every model call, every override, every alert — HMAC-chained, replayable years later, exportable on RBI request.
Integration · Day 1 → Day 90
Curl in five minutes.
- Day 101
Sandbox keys provisioned. The bank's risk team POSTs the first test bundle through the credit-risk endpoint and reads the feature-weight-attributed response.
- Day 702
Fraud verdicts wired against the live UPI webhook in shadow mode. The SOC sees the Mukodi verdict next to the bank's existing one — no enforcement yet.
- Day 3003
Shadow mode lifts on a single product line. Cost budget WARN + STOP gates are seeded; Slack alerts route to the on-call channel.
- Day 9004
Full production cutover. The bank's compliance team has replayed the chain three times for internal audit and once for the regulator.
Models powering this vertical
Specialised models, one envelope.
Compliance · for the regulator's question list
Written into the architecture.
- RBI · Outsourcing of IT Services
Retention windows and reporting cadence aligned with the RBI master direction on outsourcing of IT services for regulated entities. Vendor DPA on file per DPDP §8 fiduciary obligations.
- RBI · Account Aggregator
Mukodi is a Financial Information User where the bank is the Financial Information Provider; consent is brokered through the licensed AA — Mukodi never receives bank-portal credentials.
- DPDP §§11–14 · data-principal rights
Erasure, correction, and portability are wired self-serve on the consumer surface and as API endpoints on the partner surface.
- UIDAI · 8-digit Aadhaar masking
PII redaction enforced at the parquet boundary — partners never receive the unmasked Aadhaar artefact, and the original is deleted within the configured retention window.
A typical week
What the integration feels like once live.
Monday morning
Weekend transactions roll up; the SOC dashboard shows the new fleet-wide baseline and the four legs that crossed the anomaly threshold overnight.
Tuesday afternoon
A novel merchant cluster triggers a coverage gap in the categoriser. The feedback loop captures the correction and the model retrains on Wednesday's batch.
Thursday standup
Cost-budget WARN fires at 80% on the credit-risk meter. The Slack channel surfaces the call breakdown by product line; the team decides to raise the budget or throttle.
Friday closeout
Compliance pulls last week's audit ledger slice, verifies the HMAC chain end-to-end, and files the weekly attestation with their existing reporting tool.
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 · Banks
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.