What Happens When You Shorten the First-Deposit Path

The Original Flow

Step 1: Choose amount (₹1000, ₹5000, ₹10000, or custom)

Step 2: Select bank account (dropdown with 20+ options)

Step 3: Choose payment mode (UPI, NEFT, IMPS)

Step 4: Review transaction details

Step 5: Enter OTP

Step 6: Confirmation screen ("Your transaction is processing")

Step 7: Receipt and success page

Each step was a new screen. On mobile, it felt endless. Users dropped off most at steps 2 (bank selection confusion) and 4 (review screen paralysis).

The Problem We Identified

1. Too Many Choices Too Soon

New users don't have a mental model for NEFT vs. IMPS vs. UPI. Showing all three options made them hesitant. They'd go back, research, or just abandon.

2. Redundant Review Screen

Step 4 was a review screen showing the amount, bank, and mode again. Users had just entered this. Why re-show it? Studies show review screens actually increase abandonment (users second-guess themselves).

3. Confirmation Theater

Step 6 was just a loading screen saying "Processing..." Users didn't need to see this. The receipt (step 7) was enough.

What We Changed

Step 1: Amount + Default Bank

We combined amount selection with bank pre-selection. If the user had one bank linked, we defaulted to it. If multiple, we showed the top 2 in a small list (most-used first). This cut the step from two screens to one.

Step 2: Smart Payment Mode

Instead of asking users to choose between NEFT/IMPS/UPI, we chose for them based on:

• Amount: UPI for <₹100k (fast, familiar), NEFT for higher amounts (safer perception)
• Time of day: UPI during business hours, NEFT after 5pm (when most UPI has higher limits)
• User's past behavior: If they'd used NEFT before, default to it

We still let them manually override ("Use a different payment mode?") but 91% accepted our default. This eliminated a choice.

Step 3: OTP + Submit

We combined the final submission with OTP entry. Instead of "Confirm" then "Enter OTP," it was one screen: "Enter the OTP we just sent. We'll process your ₹[amount] deposit now." Both actions felt like one.

We removed steps 4 (review), 6 (confirmation loading). Straight to the receipt (step 7) once OTP was verified.

The New Flow (3 Steps)

Step 1: "How much?" (amount input) + bank selector below (smart default shown)

Step 2: "We'll use UPI for speed." (payment mode is pre-selected, but editable) + confirm button

Step 3: "Enter OTP + submit" (final step, OTP entry + submit button = one action)

Results

Completion Rate

• Before: 58% of activated users made a first deposit
• After: 74% made a first deposit
• Improvement: +16 percentage points

Time to Deposit

• Before: 4m 28s average (with hesitation, re-reading screens)
• After: 1m 52s average
• 58% faster

Drop-Off Points

• Before: 12% dropped at bank selection, 11% at review screen
• After: 3% dropped at bank selection (smart default), review screen gone

Fraud & Risk

• Fraud rate stayed at 0.04% (no increase, as feared)
• Default payment modes actually reduced risky behavior (no more manual experimenting)
• Compliance: Zero issues flagged by RBI audits

Why This Works

1. Smart Defaults Over Choices

Don't ask users to choose between technical options they don't understand. Choose for them intelligently. Users will override if they want to; most won't.

2. Combine Psychological Moments

OTP entry and submission are both "commitment moments." Combine them. Separate, they feel like two hurdles. Together, they feel like one.

3. Remove Redundancy

Review screens are theater. If you've shown users the info already, don't show it again. It slows down momentum and invites second-guessing.

The Risk Question

The obvious concern: Doesn't removing review screens increase fraud?

Answer: No, if you've collected good data up front. By the time users get to deposit, they've already verified their identity (KYC). You know who they are. Showing a review screen doesn't catch fraud—it just slows down legitimate users. What prevents fraud is strong identity verification, not making the deposit flow longer.

Implementation

This required:

• Backend logic for smart defaults (1–2 days)
• Frontend UI consolidation (2–3 days)
• Compliance review (1 day)
• QA testing (2–3 days)
• Total: ~2 weeks

Worth it: The 16% lift in deposits translates to massive revenue impact at scale.

Takeaway

Shorter isn't always safer. It's only safer if the steps you remove were redundant. Here, we didn't remove friction; we removed waste. Every step in the new flow served a purpose. The old flow had theater and choice paralysis. The new one has momentum.