LarkMoney

Loan Against Mutual Funds,
simulated end to end

A working model of the LarkMoney journey: CAS pull through MF Central, lien marking split across CAMS and KFIN, agreement, disbursal and everything after sanction. Runs locally, no backend, no real data.

App journey
LarkMoney on a phone

Login through disbursal, then servicing: draw, repay, watch NAVs move, cure a margin call.

Web journey
LarkMoney in a browser

Same graph, same screens, starting from a client already tracking investments on the web app.

What MF Central and the RTAs publish
MF Central — CAS pull consent
  1. 1.Investor identified by PAN and mobile → CAS consent
  2. 2.Redirected to MF Central's own portal → MF Central portal
  3. 3.Consent given, scope shown before signing → MF Central portal
  4. 4.Redirected back with a request ID → Portfolio pulled
  5. 5.Portfolio fetched by request ID → Portfolio pulled
MF Central — lien marking (CAMS / KFIN)
  1. 1.Request validated per registrar, folios matched → Choose what to pledge
  2. 2.Request grouped by RTA, one leg per registrar → Split by registrar
  3. 3.OTP to registered mobile, and email for CAMS → MF Central OTP
  4. 4.Investor consent submitted, lien sub-reference issued → MF Central OTP
  5. 5.RTA confirms to the lender asynchronously → Confirming with your RTA
Illustrative

A fictional client, a fictional portfolio, and lender terms awaiting compliance sign-off. No data is collected and nothing here is a real application.