LSP Evidence Locker
Collects proof that each lending partner follows the rules, as it happens, and shows which partner is missing what before the audit asks.
Every lending partner's evidence, counted against your own obligation list
A partner's report changed after it arrived: the mismatch is flagged and the original kept
One audit pack per partner and period, with a manifest that checks offline
A partner's feed stops: the gap is flagged on day two, not day seven
The whole demo as a video, with captions and chapters
Demo built on synthetic data.
1 of 5: The partners
The problem
Under RBI's Digital Lending Directions, the lender answers for what its lending service providers do. The evidence — consent records, key fact statements delivered, complaint response times, recovery call audits — sits with each partner, in each partner's format, until someone asks for it.
What it does
It receives evidence from each partner through an API or a file drop and fingerprints every file, so tampering shows.
It reads partner documents into evidence items against a list of obligations you can edit.
It shows each partner's coverage — which obligations have evidence behind them and which don't.
It exports an audit pack per partner.
Try to break it
On the call we'll trigger these, live:
- A partner's feed stops for a week. The gap is flagged on day two.
- A file changes after it was received. Its fingerprint no longer matches, and it's flagged.
- The same file arrives twice. It's stored once.
Where it runs
Your data centre or an India-hosted cloud account. Read the documents with a local model and partner data stays with you.
Who else does something like this
Finnulate offers compliance tooling for RBI's digital lending rules.
The Locker is self-hosted by the lender and organised around evidence from each partner.
The rules it respects
Built around RBI's Digital Lending Directions 2025 and the DPDP Act.
What our tests measured
How we testThese figures come from test runs on Google's Gemini (gemini-3.5-flash-lite), a hosted model, on synthetic data. We'll add runs on a local model.
- Run on 15 October 2026
- Model: gemini:gemini-3.5-flash-lite
- 230 examples
For your engineers
- Engines
- Reconciler, Extractor, Consent Spine, Proof Console
- Sealed mode
- Test passed: with sealed mode on, it refuses every outbound connection except to the model you've approved.
Data flow



