Module 5 Lesson 1: Failed verification states

Course 1 › Module 5: Error & edge states › Lesson 5.1

Failed verification states

Six failure types, emotional arc, state machine, and 22-point checklist — 34 min · 6 sections

Section 1 of 617% complete

Section 1

Audio ready

OpeningThe most underdesigned moment in fintech~2 min

Here's a statistic that should change how you think about verification design.

Between 20% and 40% of first document submissions in KYC flows fail automated checks. That's not a fringe case. In a product with ten thousand daily onboardings, it's two to four thousand failure states every day. And most of them are designed as afterthoughts.

The happy path gets the design attention. The pending screen gets a spinner. The failure states get "please try again." And then someone wonders why conversion through KYC is so much lower than it should be.

Failure states are where the relationship with the product is made or broken. A user who fails verification and receives clear, specific, non-accusatory guidance will retry and usually succeed. A user who fails verification and sees "verification failed — please try again" will often abandon — and tell others. The design of failure states is not a detail. It's a retention strategy.

This lesson maps six types of verification failure, the emotional arc a user travels through them, the specific design requirements of each state, a copy audit exercise, and a 22-point pre-handoff checklist.

Let's start with understanding what actually causes verification to fail — because the design response depends entirely on the cause.

Section 1 of 6