What shipping this changed
We designed the document pipeline before we designed the interface.
Documents encrypted before they are ever at rest
A PAN card or a bank statement is not a file, it is an identity theft kit. Uploads are encrypted on receipt, and the plaintext never touches disk on the way through — the failure mode we were designing against is a misconfigured storage bucket, which is how most Indian document leaks have actually happened.
Every document read is attributable
Encryption answers "could someone outside read this". Access logging answers "which of our own people did", which is the question a regulator or a customer actually asks after an incident. Both were built in, not retrofitted.
The approval flow is a state machine, not a status field
Loan origination is a sequence with money and obligations attached to each step. Modelling it as explicit states with explicit transitions means an application cannot end up half-approved because two operators clicked at the same moment — a race condition in a fintech flow is a financial event, not a bug report.
Retention decided at the start
Under the DPDP Act, holding KYC documents longer than the purpose requires is itself the violation. What gets deleted, and when, was agreed before the first document was accepted rather than discovered during an audit.
The stack, and why
A conventional, boring stack, chosen deliberately. Fintech is the wrong place to be the first person using something — well-understood components have well-understood failure modes, and known failure modes are the ones you can actually defend against.
Want the same, pointed at your product?
Free discovery call, then a fixed price in writing within 24 hours. No retainer, no surprises at the end.