Identity Verification UX: Design the Retry Before You Design the Selfie

A founder on r/SaaS described adding identity verification for compliance and watching sign-up conversion fall from about 68% to 34% almost overnight. Compliance would not budge, so the growth team blamed the regulation. The thread that followed matches what we see in fintech, insurance, health, and marketplace audits: most of the loss happens at the first imperfect photo, the first vague error, and the first silent wait.

Our position is simple. Identity verification is a checkout flow with a legal requirement attached, and it deserves the same care your payment step gets. Teams that treat it as a vendor SDK they drop into a screen end up with a flow that works for the employee who tested it at a desk and fails for the customer holding a phone in a dim kitchen at 10pm.

Where verification actually loses people

We split every verification funnel into three moments before we touch a single screen.

Before the start. The customer sees "Verify your identity" with no warning, no time estimate, and no reason. They do not have their license nearby, or they feel ambushed, and they leave without trying.

During capture. The document photo has glare. The selfie times out. The camera permission prompt appears with no context and gets denied. The customer tries twice, sees the same vague error, and gives up.

After submission. The screen says "Processing" and nothing else. Behind the scenes the case sits in a manual review queue for hours. The customer hears nothing, assumes they were rejected, and signs up with a competitor that verified them in four minutes.

Each moment has a different fix. A team that measures only "verification completion rate" cannot tell which one is bleeding, so they redesign the wrong screen. The first deliverable in any verification audit we run is that three-way split, pulled from real event data.

Ask for verification at the moment it earns its keep

Regulation usually says you must verify before a customer can move money, receive a payout, or access a regulated feature. It rarely says you must verify before they can see the product. Where the rules allow it, we move the check to the first action that requires it: the first transfer, the first payout, the first claim.

By that point the customer has already invested. They have set up an account, connected something, or seen a quote they want. Verification now reads as the last step to something they chose, and completion goes up because the reason is obvious.

When the check must happen at sign-up, the screen before it does the heavy lifting. It names what they will need (a government ID and their face), how long it takes, why the law requires it, and what happens to the data. Twenty seconds of honest preview beats any amount of polish on the capture screen.

Design capture for the worst lighting your customers have

Vendor SDKs ship with sensible defaults and generic copy. Generic copy is where the losses hide. We review every capture state on a mid-range phone, at night, with a worn card, because that is the real test environment.

What good capture looks like:

• Live framing feedback that tells the customer what is wrong right now: too far, glare on the top corner, edges cut off.
• An auto-capture that waits for a sharp frame, plus a manual shutter for people whose card never triggers it.
• A fallback to file upload after two failed auto-captures, so a customer with a scanner or a stored photo can still finish.
• A camera permission request that appears after an explanation, with a recovery path if they tap "Don't allow."
• A desktop handoff that sends the capture step to their phone with a QR code and brings them back to the same place when it is done.

Liveness checks deserve their own pass. If the customer does not respond in time, retry once automatically with clearer instructions instead of failing the whole session.

Every rejection needs a reason and a next step

This is the part most teams skip, and it is where we start. Write the failure states first. List every outcome your vendor can return (blurry document, expired ID, name mismatch, unsupported document type, face mismatch, inconclusive) and decide what the customer sees for each one.

A customer told "Your ID photo was blurry. Retake it near a window or under a lamp" will usually try again. A customer told "We couldn't verify your identity" will usually leave. Move as much of the reason into plain language as your compliance team allows, and make "Try again" the primary action on the screen. Keep everything they already entered so a retry means retaking one photo and nothing more.

Name mismatches need special care. Married names, hyphenated names, transliterated names, and middle names on one document but not another trip up legitimate customers constantly. Give them a way to explain or add a second document before routing them to a dead end.

Treat manual review as a product surface

Some cases will always land in a human queue, and the customer should hear about it. A review state should tell the customer three things: we have your documents, this usually takes about this long, and we will notify you by email and text when it clears. Then actually send the notification, with a link that lands them back in the flow they were in.

If review needs more information, ask for it inside the product with the exact document needed. Sending them to a support inbox where they have to explain everything again is how you lose the customers you already paid to acquire.

Inside the company, review needs its own design work too. Reviewers should see the original capture, the vendor's reason codes, and the customer's history on one screen. Faster, clearer decisions shorten the wait the customer feels.

What we measure

We instrument verification like any other critical funnel:

• Start rate: of customers who reach the step, how many begin.
• Capture success on first attempt, split by document type and device.
• Retry rate after a specific error, and how many retries end in a pass.
• Share of sessions routed to manual review, and median time to decision.
• Return rate after a review notification.

Those numbers tell you which of the three moments to fix first. Pass rates around 85 to 90 percent are what operators in regulated fintech often report for well-run flows. If you are far below that, the gap is almost always in states someone never designed.

Our reject list

When we audit identity verification, these are the patterns we flag first:

• Verification forced at account creation when the regulation only requires it before money moves.
• A capture screen with vendor default copy that no one on the team has read.
• One generic error for every failure reason.
• A retry that clears the form and starts the whole flow over.
• "Processing" with no time estimate and no notification when it finishes.
• Camera permission requested with no explanation and no recovery path.
• Desktop users told to "use your phone" with no handoff.
• Name mismatch treated as fraud with no way to explain.
• Reviewers working across three tools to make one decision.

How we work on it

We build these fixes as working software in your product, with senior designers who have shipped regulated flows and AI-assisted execution that lets us cover every failure state in days instead of weeks. Your compliance team keeps the final say on what the customer can be told. We make sure every state they approve is clear, kind, and recoverable.

If your verification step is quietly eating half your sign-ups, start by scanning the page that leads into it with our free UX Scan. When you want the full flow audited and rebuilt, book a discovery call or email ash@uxsignalstudio.com.