Documents & KYCRetail + B2Bpilot· marketing-claim · pii-redaction-frame-ocr

Documents & KYC.

Add a PAN, Aadhaar, passport, salary slip or bank statement — Mukodi extracts the fields.

Built by Filer →
The problem

Why this exists.

Document upload as a feature has been built ten thousand times in India and broken almost as often. Most apps either OCR poorly or just keep the file.

We want a single pipeline that accepts every document type a household actually owns and extracts the structured fields downstream features need.

How it works · 3 steps

From input to outcome.

  1. Step 01

    Step 1

    Add a PAN, Aadhaar, passport, salary slip, or bank statement from the Add tab.

  2. Step 02

    Step 2

    A vision-language model extracts the structured fields under a UIDAI 8-digit-mask gate.

  3. Step 03

    Step 3

    Forgery detection runs alongside extraction; mismatches surface for human review.

Under the hood

The models and routes behind it.

API routes
  • POST /api/v1/documents
  • POST /api/v1/b2b/document-verify
Compliance posture
  • UIDAI mandate — first 8 digits of any Aadhaar number are masked at the parquet write boundary.
  • DPDP §12 — extracted fields are erasable with the source document.
  • Forgery flags are advisory; final decision is the partner's.
What it's not

Document extraction is structured-field capture, not legal verification. Statutory KYC under PMLA still runs through your bank.

← Back to all features