The situation
The application flow was clean until the KYC step, where it asked for photographs of identity documents. Analytics showed the sharpest drop of the entire funnel at exactly that screen, and a significant share of those users never returned.
The team had already iterated on the screen's design twice. Neither attempt moved the number meaningfully, which was the clue that the problem wasn't presentation.
What changed
Verification was restructured around typed identifiers resolved against source records, with consent captured in the same request. The user enters numbers they either know or can retrieve from their phone, and the result returns while they are still on the screen.
Checks were also tiered. A light verification opens an account with conservative limits. A deeper one runs when the customer requests a higher limit — at which point they are asking for something, and an extra step reads as reasonable rather than intrusive.
A side effect worth noting
Removing document uploads removed an entire category of obligation. The platform no longer stores identity document images, which simplified its retention policy, its access controls, and the conversation with its security reviewers.
Where it landed
Verification stopped being the funnel's worst step. Applicants who start the process now generally finish it in the same session, and support tickets about stuck or failed verifications dropped sharply — partly because there are fewer failures, and partly because the ones that remain explain themselves.
A composite account drawn from typical engagements. Details have been generalised to illustrate the integration pattern.