Redesigning international money transfers
A cross-border transfer flow people abandoned halfway through. I led the redesign — research, IA, interface, and the front-end details that made a 17-field form feel like a calm, guided path.
- Role
- Senior Product Designer · research → IA → UI → front-end collaboration
- Status
- Client work · production · UI shown with permission
The problem
People dropped out of the international-transfer flow at the points where it asked the most and explained the least: beneficiary bank details, the SWIFT/BIC code, confirmation, and the fee step. Field fatigue, errors with no real-time feedback, fee descriptions in bank jargon, and no clear answer to the only question that matters — when does my money arrive.
Decision
Design decisions that moved the needle
Type the bank name, get the SWIFT code auto-filled instead of demanding it. Frame fees by outcome ("arrives in 1–2 days") rather than tier names. Validate inline, detect pasted codes, and keep a persistent summary so people can review without losing their place. Progressive disclosure hid advanced options until they were needed.
How it's built
From Figma to the front end
I didn't hand off a static file. I worked in the codebase with the engineers — building the inline-validation components, the SWIFT lookup interaction, and the accessibility pass (WCAG 2.1 AA) — so the thing that shipped kept the texture of the thing I designed.
Honest outcome
It shipped, and the team's own funnel and support load both moved in the right direction. I'm deliberately not quoting precise figures here — they were directional and I won't dress up numbers I can't fully defend. What I can defend is every interaction decision on this page, and why it was made.