KYC is a product problem before it is a compliance problem
The rules say what to verify. Whether customers finish the journey depends on choices the rules never mention.
Amogh Suman
Most teams meet KYC as a checklist handed over by compliance. The regulation says what must be collected and verified, the vendor says what its service returns, and the product team is asked to fit both onto a screen. The result is a flow that satisfies the rule and loses the customer.
The customer experiences none of that structure. They experience a request for a document they may not have at hand, a selfie that fails in poor light, and a message saying something went wrong. Every one of those moments is a design decision, even when nobody made it deliberately.
Where onboarding breaks
Drop-offs gather in a few predictable places: the moment a document is requested, the moment a live check fails, and the wait for a manual review. Adding another verification vendor fixes none of them. What helps is deciding what to ask for first, what can wait, and what the customer sees while waiting.
The regulation tells you what to verify. It is silent on when, in what order, and how gracefully.
Three questions for the product team
- What is the least we must verify before the customer gets their first piece of value?
- Which checks can run in the background while the customer carries on?
- When a check fails, does the customer know exactly what to do next?
Compliance sets the floor. Product decides whether customers ever reach it.