Making duplicate-account recovery feel clear and safe

Maya duplicate account recovery screens
TIMELINE

2020

ROLE

Product design contributor

TEAM

Maya

TL;DR

This concept helps customers understand and safely resolve a duplicate-account situation, turning a potentially alarming interruption into a guided recovery experience.

Disclaimer: This case study is a high-level overview — some specifics are covered by NDA. Happy to walk through the details in a call.

CONTEXT

Account issues carry a trust cost, not only a support cost.

For a consumer financial app, discovering an existing account can be confusing and stressful. Users need to understand what is happening, verify that the account is theirs, and feel confident about what will happen to their money and data.

APPROACH

Reduce uncertainty at every decision point.

The work focused on the questions a customer is likely to ask in the moment: Is this really my account? What happens if I reclaim it? What happens to my existing balance, history, and access?

RECOGNIZE

Show enough account information for a customer to confirm it without exposing unnecessary detail.

EXPLAIN

Use plain language to clarify the recovery path and its consequences.

REASSURE

Make preserved balances, data, and next steps visible before asking for consent.

DESIGN DECISIONS

A recovery flow designed for confidence.

REFLECTION

In fintech, reassurance is part of the interaction.

The strongest design move is often not adding more UI—it is making the right information available at the exact moment trust is at risk. This project reinforced how carefully designed language, consent, and recovery paths can shape a customer’s confidence.

Back to Oboda AI ERP →