BackVora
Project Overview

Vora

A conceptual KYC onboarding experience designed to reduce verification drop-off through clearer guidance, trust-driven interactions, and real-time feedback.

Year
2025
Role
UX & UI Design
Skills
UX Research  ·  KYC Flow  ·  UI Design  ·  Prototyping
Vora cover
About

Verification without the friction

Vora is a concept project exploring the KYC and onboarding experience in fintech which is the most critical and often most frustrating part of any financial product. The goal was to design a verification flow that feels guided and trustworthy, based on patterns observed working in compliance for three years.

Core Problem

Where users abandon

Users of fintech platforms frequently abandon identity verification mid-flow. The reasons are consistent: unclear requirements, no feedback after failed attempts, and anxiety around uploading sensitive personal data. For fintech products, this drop-off directly impacts activation and revenue.

Regulation requires the data. Good design determines whether users feel safe enough to share it.
Insights

Observed on the compliance side

Users frequently abandoned identity verification mid-flow, often without understanding why they were rejected or what was expected of them.

Without clear feedback or transparent communication, the experience felt opaque and anxiety-inducing, particularly around uploading sensitive personal data.

These frustrations revealed an opportunity to redesign verification as a guided, human experience rather than a regulatory formality.

Vora insights — user concerns around verification
Key Decisions

What we built, and why

Step-by-step structure

Breaking the flow into three clearly labelled steps reduced cognitive load and gave users a sense of progress and control throughout verification.

Real-time capture feedback

The scan frame shifts from neutral to amber to green as conditions improve, with automatic capture once ready and a manual option always visible.

Contextual trust signals

Encryption notices and plain-language explanations appear at the moment they are needed, not buried in a terms page.

Vora key decisions — document choice, scan capture, verified state
Outcomes & Learnings

Clarity is the product

Designing this flow with a compliance background meant understanding not just user frustration but the regulatory reasons behind each requirement. That dual perspective as both user advocate and compliance realist shaped every decision: what to ask for, when to ask for it, and how to explain it without creating alarm.

Understanding the regulation is what lets you design around it.

Full case study available upon request.