Bank-linking UX: penny-drop, OTP and retry design

Linking a bank account is where many FinTech journeys either take off or stall. Users expect it to take seconds. Behind the screen, it involves banks, payment rails and verification partners that do not always respond on time.

A robust bank-linking flow is mostly about handling the moments when things are slow, uncertain or wrong. Here is how to design for them.

Choose the right verification method

Penny-drop: you send a small credit, often ₹1, to the account and match the name returned by the bank against your records.
Reverse penny-drop: the user pays a small amount from their own account, usually over UPI, which proves they control it. You refund it afterwards.
Account Aggregator: with the user's consent, you fetch verified account details through the RBI-regulated Account Aggregator framework.
Document upload: a cancelled cheque or bank statement, kept as a fallback when other methods fail.

Many teams offer reverse penny-drop first for speed, with penny-drop or document upload as fallbacks.

Hand holding a phone showing a payment QR code

Design for asynchronous results

Verification does not always come back instantly. Treat every attempt as having clear states: started, pending, verified, failed and expired. Show the user which state they are in and what happens next, instead of a spinner with no end.

Retries without double charges

Give every verification request an idempotency key, so a retry never triggers a second debit or credit.
Set sensible timeouts per partner and retry with back-off.
Fall back to a second provider when the first is degraded.
Never ask the user to repeat a payment until you know the first one failed.

Handle names and IFSC codes carefully

Bank records often format names differently from PAN or KYC data. Match with care, allow for initials and ordering, and route close mismatches to review instead of rejecting them outright.

Validate IFSC codes as users type. A valid code has 11 characters: four letters for the bank, a zero, and six characters for the branch. Show the bank and branch name back to the user to confirm.

Make status impossible to misread

Tell users exactly what was debited or credited and whether it will be refunded.
Send a confirmation by email or SMS when verification completes.
Offer a clear way to retry or switch method after a failure.

Observe everything, expose nothing

Log each partner's response codes and timings so you can spot degradation early. Mask account numbers in logs and keep them out of analytics entirely; bank details are among the most sensitive data you hold.

Final thoughts

Bank linking is plumbing, but users feel every leak. When verification is fast, retries are safe and every status is crystal clear, people barely notice the step at all. That is exactly the goal.

Want a second pair of eyes on your funnel? Our FinTech team maps every step from ad click to funded account and prices each leak. Get your FinTech growth audit.

Bank-linking flows that don't break: Penny-drop, OTP and retry design