Financial services · NBFCs & wealth
Consent that respects how lending and wealth actually run
Kavach is the shared notice and consent layer across LOS, core/LMS, CRM, bureau, KYC, collections, and wealth rails — APIs and webhooks for systems that can integrate, optional browser assist where legacy web UIs stay.
- Lending + wealth journeys
- Inside + outside the perimeter
- Not owned by one LOS vendor
Touchpoints
Where client data shows up (grouped)
For workshops with risk and compliance — not legal advice; your counsel sets lawful bases.
| Area | Typical activity | Notice / consent themes |
|---|---|---|
| Acquisition & onboarding | Leads, apps, KYC / CKYC, video PD, calculators, WhatsApp journeys. | Service vs marketing; channel opt-in; identity and KUA / CKYCR purpose. |
| Credit & sanction | Bureau pulls, bank analytics, underwriting, sanction packs, e-sign. | Explicit consent for bureau / alt data; contract vs optional cross-sell; joint applicants. |
| Disbursement & servicing | Tranches, mandates, EMI changes, prepayment, NOC, limit changes. | Servicing comms; channel preferences; material change documentation. |
| Collections & restructuring | Dialler, field, settlements, legal notices, restructure schemes. | Agency scope; fair practices; recordings; hardship data sensitivity. |
| Wealth: suitability & execution | Risk profiling, mandates, product selection, MF / broking / DP flows. | Advisory vs execution-only; product disclosures; suitability artefacts linked to orders. |
| Partners, contact centre, compliance | DSAs, BCs, AA journeys, CRM; AML, fraud, regulatory returns, grievance. | Partner purpose and retention; segregate regulatory vs optional uses; DPDP grievance evidence. |
At a glance
Client journeys and where Kavach sits
Two diagrams for decks: lending vs wealth rhythms, and how Kavach connects in-house systems with infrastructure and partners outside your perimeter.
1 · Lending and wealth journeys (simplified)
Each hand-off is a natural place to attach notice version and purpose in Kavach — and to fire webhooks so the next system does not improvise.
2 · Kavach inside the organisation and beyond
Calls that cross the perimeter leave with purpose and notice context attached; responses and webhooks land back in your core systems and client portal.
Purposes
What usually spans lending and wealth
- Contract & service — running the loan or advisory agreement.
- Regulatory & legal — AML, returns, court orders — logged apart from marketing.
- Optional growth — cross-sell, events — granular and withdrawable.
- Analytics — beyond servicing, disclose as counsel advises.
Kavach shows which story applied at each event — not one checkbox for everything.
Beyond marketing consent
Regulatory, fraud, and legal-process data
Much processing is not “fresh marketing consent.” Kavach helps you segregate those trails from optional uses so logs and portals stay intelligible to examiners and clients.
- Which notice was active for bureau / CKYC / RTA calls?
- Are marketing and regulatory bases separated in exports?
- On withdrawal of optional consent, which systems actually stop?
Not legal advice. Confirm grounds for your licence mix with qualified counsel.
Client portal
One timeline for borrower or investor
Aligned with what risk and audit export — important when grievances hit the nodal desk or social channels.
