When users encounter identity verification failures during fintech onboarding, they often lack clear, actionable guidance on what went wrong and how to proceed — leading to abandonment, repeated failures, and erosion of trust before the relationship even begins.
The information gap between "something went wrong" and "here's exactly what to do next."
| Not This | Why |
|---|---|
| The verification decision itself | Decisions are correct and necessary |
| Speed of verification | May be constrained by regulation |
| Number of steps required | May be non-negotiable |
| The verification system being broken | System works as designed |
First-time applicants attempting to open a regulated financial account who have encountered at least one verification failure or retry scenario.
Characteristics:
- May have limited experience with digital banking onboarding
- May not understand why identity verification is complex
- Are in a high-stakes emotional state (money, identity, trust)
- Have no prior relationship with the institution to fall back on
Explicitly NOT:
- Existing customers with established trust
- Users who complete onboarding without friction
- Fraudulent actors (who are correctly rejected)
- Regulations (KYC/AML) mandate specific verification steps
- Explanations must not reveal fraud detection logic
- Legal language requirements may conflict with plain-language communication
- System knows why verification failed; user often does not
- Sharing too much detail creates security/fraud risk
- Sharing too little creates confusion and abandonment
- Users need trust to share sensitive documents
- Trust is lowest at the moment of failure
- Institution cannot "prove" trustworthiness — must demonstrate it
- Support teams are expensive and don't scale
- Automated responses often feel cold or unhelpful
- Edge cases are numerous
- Onboarding friction means user never becomes a customer
- Abandonment at this stage is often permanent
Patterns that would indicate this problem exists:
- High retry rates on specific verification steps
- Drop-off spikes after first failure
- Support ticket volume related to "what do I do now?"
- Time-on-screen increases after error states
- Users uploading the same document multiple times
Note: Actual data would be required to validate severity.