Amount field
A currency, then an amount. The rate and the fee are shown before anything is confirmed.
Do
- Show the currency before the amount.
Don’t
- Reveal the rate only after confirmation.
Case study · iBanFirst · 2020–2021
Designing international payments for businesses from what users actually do, and a first Lead role.
A fintech platform for international payments and currency exchange: add and improve features, and understand how businesses really used it.
Watched real sessions in screen recordings, ran interviews and tested changes as prototypes. Mapped a client’s first weeks and audited the onboarding checklist. Contributed to the design system, then evolved it as Lead.
Improvements shipped once users had validated them, payment flows built on shared components, and my first Lead role, in 2021.
How it was measured: a before/after comparison, including the time to complete the same task before and after the change.
The changes play on the screen above, the problem first and then the fix. Pick one to see it again.
iBanFirst lets businesses pay and get paid abroad, hold accounts in several currencies and manage their exchange risk.
I joined in 2020 as Senior Product Designer. The work was to add and improve features on the platform, and to understand better how clients used it.

Before changing a journey, I watched it.
I analysed user journeys from Hotjar session recordings and heatmaps, tested changes as prototypes in Maze, four or five tests in all with 5 participants each, and ran 10 interviews. Improvements went out once users had validated them.
| Method | What it tells |
|---|---|
| Session recordings | Where people hesitate or give up, in the real product. |
| Interviews | Why people do what they do. |
| Prototype tests | Whether a change works, before it is built. |
Here is that loop on a single question: paying in a currency the company doesn’t hold yet.
Observations from recordings, interviews and tests went on one wall, then into themes.
Getting to the first payment
What we took from it
One clear action per step, in the order the client needs it.
Which currency, which account?
What we took from it
Say what will happen before it happens: an account in that currency will be created.
Where is my money?
What we took from it
One balance across banks and currencies, and every payment followed step by step.
Linked banks
What we took from it
Warn when a linked bank needs reconnecting.
From the first transfer to the first statement: five steps, mapped from the onboarding checklist.
Which of our accounts do I send it from?
What details do I need?
Do I already have a dollar account?
What is a hedge, and do I need one?
Where do I find it?
New clients were guided to their first payment by a checklist. Captured at the time, it showed small faults that add up.
Fund the account from the company’s own bank, add a first beneficiary, make a first payment, then simulate a hedge against currency risk.
The funding step’s button says “Add your first beneficiary”.
FixEvery step’s button names that step’s own action.

The numbering jumps from 1 to 3.
FixSteps numbered once, in order, from 1 to 5.

Steps that aren’t open yet look like buttons.
FixLocked steps show a lock, and no button until they open.

“Simulate a hedging”: jargon, and a grammar slip.
Fix“Simulate a currency hedge”, with one line on what it gives you.

“Generate an extract” appears twice, described as a payment.
FixOne step, “Download a statement”, with its own description.

The payment flow opens from the dashboard, in a panel that shows where you are.
The panel shows each step and its progress. If you pay in a currency you do not hold yet, it tells you an account in that currency will be created.



iBanFirst — Payments
The design file of the payment flow: six frames in order, from the dashboard to the validated payment, with the prototype connections that link each control to the next frame.
01 Dashboard
02 Dashboard / Create menu
03 Payment / Details
04 Payment / New currency
05 Payment / Review
06 Payment / ValidatedThe design file of the payment flow: six frames in order, from the dashboard to the validated payment, with the prototype connections that link each control to the next frame.
I contributed to iBanFirst’s design system, then evolved it as Lead.
The payment flows are built from shared components: amounts with their currency, payment statuses, steps, alerts, account rows.
The shared library I contributed to, then evolved as Lead. Shown here: the components behind the payment flows.
iBanFirst design system
No match
A currency, then an amount. The rate and the fee are shown before anything is confirmed.
Three choices made the difference.
In 2021 I became Lead Product Designer (UX/UI).
I evolved the design system I had been contributing to, ran design operations day to day, and shipped key launches with product managers and engineers, validated with users along the way. The same year I moved from Paris to Bordeaux and kept working remotely, with occasional trips to the Paris office.
In October 2021 I joined Ogury as Lead Product Designer.