In FlexiLoans' digital lending journey, document upload was the single biggest drop-off point. Many customers were not tech-savvy, and even when they did upload, the photo was often not legible.
What I built
A CKYC service that removed the step. The customer enters date of birth and PAN; the journey publishes an event to Amazon SNS; the CKYC service consumes it, calls the central KYC registry, and brings the customer's details and stored documents back into the journey prefilled.
Pipeline: from PAN to prefilled documents
Alongside it, services for Experian credit workflows and NSDL PAN verification, part of moving onboarding toward an event-driven microservices architecture.
Details that made it hold up in production
Idempotent consumption, keyed on loan id plus the customer's mobile number, because loan id alone missed duplicate cases.
Search before fetch: the registry has a search API and a fetch API. The service searches first, compares the record's last update with what is already stored, and fetches only when it has changed. Fewer provider calls, lower cost.
A business-outcome monitor, not only a system-health one: a daily count of documents per onboarded customer. During the staged rollout to 25% of customers it caught a message-encoding bug that uptime dashboards would have shown as green.
Production details and results
Results
Customer onboarding time reduced by 60%.
CKYC records resolved for about 80% of customers; the rest kept the manual path.
I wrote the CKYC service as a senior engineer and became Engineering Lead about nine months in.
Like this project
Posted Sep 21, 2026
An event-driven CKYC service for a digital lender that pulled customers' registry documents into onboarding automatically, removing the journey's biggest drop-off point.