Step 01
Step 1
Forward a bank or card SMS to the Add tab.
Documents & KYCRetail
SMS forward parser.
Forward bank and card SMS alerts — Mukodi parses them into transactions.
The problem
Why this exists.
Not every Indian bank lives on the Account Aggregator framework yet, and not every household uses cards that integrate cleanly.
Almost every bank still sends an SMS for every debit and credit; that SMS is the fallback signal we can always rely on.
How it works · 3 steps
From input to outcome.
- Step 02
Step 2
Mukodi parses the amount, merchant, balance, and direction with a 20-bank dictionary.
- Step 03
Step 3
Ambiguous strings fall back to the LLM extractor with a confirmation card before they land.
Under the hood
The models and routes behind it.
Models called
API routes
Internal-only — no public route handler.
Compliance posture
- SMS text is processed server-side; the raw message is erasable under DPDP §12.
- Bank dictionary is open and auditable; new bank patterns ship with a parity test.
- Confirmation card on ambiguous parses ensures we never silently add a wrong row.
What it's not
SMS forwarding is a fallback when AA or a file upload is not available. It is not a substitute for a verified account-aggregator connection.
Related · features & stories