Each decision shows the option I rejected and why. The trade-offs are reasoned from the benchmark and the constraints above, not from user testing.
Lead with what lands
The EUR amount the recipient gets is the largest number on the amount screen. The USD you send is the input, not the headline.
RejectedSend amount as the headline, the way most banking apps do it. People anchor on the big number, and the question they actually have is "what will Mum get?"
One primary action per screen
Continue, then Confirm and send. Secondary options live in clearly labelled text buttons, never as a second filled button.
RejectedQuick actions (convert, schedule, split) on the review card. They would save a tap for power users but make the one step that moves money harder to scan.
Terms next to claims
Rate lock window, fee and delivery time sit on the same card as the amount. No asterisks.
RejectedA "Fees and terms" link under the button. Cleaner, but it is exactly the footnote pattern the benchmark audit flagged as costing trust.
Hold to send
The final step is a press-and-hold with a progress fill, so nothing is sent by a stray tap in a pocket or on a bus.
RejectedA separate confirmation screen. It is safer than one tap but adds a full screen to every repeat send. Cost I accepted: hold is slower for power users, so I would revisit it if repeat senders drop off at this step.
Verify only when it matters
Anyone can browse rates and get a quote without ID. Identity is checked once, right before the first send, with a 3-step progress bar and a plain "why we ask" line.
RejectedID upload at sign-up. It front-loads the hardest step before people have seen any value, which is where fintech onboarding usually leaks.
Two lock windows, on purpose
Conversions between your own balances lock for 30 seconds because they execute instantly. Transfers show a lock countdown, because they settle later. The prototype shows 24 hours; I assumed an FX partner absorbs that risk.
RejectedOne long lock for everything. If treasury can only fund a 2-hour window, the same countdown handles it, and the expiry state (below) requotes in plain words instead of failing at the last tap.
Open the web app → Open the website → Open the design system →
Mobile is for sending. The web app is for the monthly money admin: account details for clients, history, statements and rate alerts.