Redesigning KYC Flows Without Breaking Compliance

The Starting Point

The client's KYC form was a dense, 15-field monster. Regulators didn't require all 15—they required maybe 9. The extra 6 had accumulated over years of "it might be useful someday" thinking. The result: users abandoned mid-form because it felt endless.

Compliance is non-negotiable in fintech. But compliance doesn't mean "ask for everything, store everything." It means knowing exactly what the regulator requires, asking for that, and nothing more.

What RBI Actually Requires

We did a compliance audit first. Here's what KYC really needs under SEBI/RBI rules for a trading account:

• Name (exact match with ID)
• Date of birth
• PAN (primary KYC identifier)
• Address (proof required)
• Occupation/Income bracket
• Bank account for settlement
• ID proof (Aadhaar or Passport)

That's 7. The client was asking for 15: additional address fields, landline number, residential status, document type choices, emergency contact, etc. All optional for compliance. All taxing for users.

The Redesign

Step 1: Remove Redundancy

We removed fields that were either redundant (asking for city when pincode auto-fills it) or unused (the emergency contact field, data showed, was filled <3% of the time and never used). Dropped from 15 to 9 fields.

Step 2: Smarter Defaults and Auto-Fill

Pincode auto-populates city, state, and address type. If Aadhaar is linked, name and DOB come pre-filled. Banks show in a ranked list (by popularity) rather than alphabetical. These small changes cut interaction time by 2–3 minutes.

Step 3: Better Micro-Copy

Instead of "Residential Status," we wrote "Where do you live? (PAN address or current address)." Instead of vague "Proof of Address," we listed accepted documents. Users got clarity, abandon rates fell.

Step 4: Visual Progress

We added a progress bar: "Step 2 of 5." This is psychological. It signals the end is near. On long forms, it's essential for mobile users who lose patience.

Step 5: Progressive Disclosure

Not all users need all fields. If a user selects "Salaried," we show Income and Employer. If "Self-employed," we show Income range and GST. This shrinks perceived form length.

The Changes Visually

Before:

• 15 fields, all visible at once (mobile user horror)
• Generic labels ("Address," "City," "State," "Pincode"—all separate)
• No progress indicator
• Required/optional fields unmarked
• Submit button way at the bottom

After:

• 9 fields, shown in logical groups (2–3 per section)
• Clear, conversational labels
• Progress bar: "Step 3 of 5" (massive morale boost)
• Optional fields clearly marked (reduces anxiety)
• Submit button sticky at the bottom (always visible)

Results

Completion Rate

• Before: 71% completed KYC
• After: 84% completed KYC
• Improvement: +13 percentage points

Time to Complete

• Before: 8m 42s average
• After: 5m 18s average
• 38% faster

Validation Errors

• Before: 3.2 errors per user (city/state mismatches, format issues)
• After: 0.8 errors per user (auto-fill and better labels)
• 75% reduction in user friction

Compliance: Zero rejections for missing data. SEBI/RBI audits found no issues.

Key Principles

When redesigning a regulated flow:

1. Know your rules: Talk to legal/compliance. Distinguish "must-have" from "nice-to-have."
2. Every field must justify itself: If you don't know why a field exists, delete it.
3. Reduce redundancy: Don't ask for city if pincode gives it away.
4. Use progressive disclosure: Show fields conditionally, not all at once.
5. Copy is compliance: Clear labels reduce errors, re-work, and abandonment.
6. Progress indicators matter: On long forms, showing progress cuts abandonment 15–20%.

The Bottom Line

Compliance and good UX aren't opposites. They're allies. Clear, short forms have fewer errors and re-submissions. Users feel more confident. Regulators see clean data. Everyone wins. The 13% lift came from respecting users' time while respecting regulations' requirements.