Helping businesses to send cross-border payments with confidence.
Role
UX/UI design
Built
Desktop & mobile dashboard concepts
Impact
Rate, fee and total before you commit
The dashboard
Balancing Detail With Simplicity
Finance teams need to act quickly across multiple currencies, without
losing sight of the numbers that matter.
The dashboard reduces noise by bringing balances, wallet performance
and priority actions into a clear hierarchy. Digestible cards and
streamlined calls to action help teams make confident decisions
without searching across the platform.
The platform’s core functionality was in place, but the experience
around it was fragmented. Key tasks were slow, unclear and harder to
complete than they needed to be for teams managing high-value
cross-border payments.
Defining Pain Points With Stakeholders
Sales & Success
Platform usability was slowing sales conversations and client onboarding.
CTO & Developers
Technical constraints and legacy architecture shaped what could change safely.
Support Team
Recurring questions revealed confusion around transparency, subscriptions and payment failures.
What Discovery Revealed
01
Key Data Buried
Wallet balances, FX rates and transaction status were either hidden or below things nobody opened.
02
Complex Core Actions
Sending a payment, approving one or retrying a failed one each took more clicks than the task deserved.
03
No Workflow Cues
Nothing said what mattered, what needed attention, or what to do next. You had to already know.
”
The sentence that reframed the brief
“The data already exists. It’s just scattered.”
Engineering’s point from discovery, in my words rather than a verbatim quote. It moved the brief from building new functionality to restructuring what was already there.
Who it’s for
Financial Controllers At Fast-Paced SMEs
Financial controllers at SMEs, or small and medium-sized businesses,
manage multi-currency transactions and cash flow, ensuring payments go
through smoothly. Understanding their priorities revealed where the
journey created friction, hid critical information or slowed the next
action.
Transactions · recreatedLast 30 days
Brightline Imports3 Apr−€12,897.00 Failed
FX transfer fee10 Mar−€65.00 Pending
Nexus Agritech13 Mar+£16,340.00 Successful
A day’s work
Check wallet balances between meetings, often on a phone.
Watch the rate before committing to a conversion.
Chase the payment that failed or is still sitting pending.
Their Goals
Real-time visibility of balances & current rates
Payment history reachable without hunting for it.
Efficient payment workflows
Fewer failures they only find out about afterwards.
The converter
Clearer Conversions, Confident Users
Currency conversion is a high-stakes task for global businesses.
The pattern already in the product surfaced cost afterwards: pick an
amount, confirm, and the fee and the applied rate turn up on the
receipt. At the moment of decision that looks like the better deal,
which is exactly the problem - the difference lands later, on
transfers where they’re dealing with real money.
By showing the FX rate, fee, and final amount upfront, we reduce uncertainty
and build trust before the user commits. It’s a transparency-first approach
that reduces drop-off and increases confidence in conversions where large
sums matter.
The trade-off
Prioritising Business Urgency And Technical Feasibility
Leadership needed fast wins for sales and support, so I prioritised
changes that improved clarity and conversion without waiting for a
full platform rebuild.
Engineering confirmed the data already existed, but was scattered.
Working closely with them, we used a phased UI approach to surface key
payment insights in fewer clicks while staying within the existing
system constraints.
As the UX/UI designer, I translated stakeholder needs and technical
constraints into reusable interface patterns engineering could deliver
incrementally.
Constraint
Data Existed, But Was Scattered
Design Response
Reorganised and prioritised it around key payment tasks.
Constraint
A Full Rebuild Was Not Viable
Design Response
Worked with existing data, system boundaries and components.
Constraint
Sales And Support Needed Change Quickly
Design Response
Phased delivery around the highest-friction payment journeys.
From Decision To Delivery
AlignValidate priorities with Sales, Support and Engineering.
Build In PhasesReuse existing data and components first.
Release And LearnMonitor task completion, support queries and conversion drop-off.
What I’d measure
What I’d watch if it shipped
No usage data and no test data. Three of these need instrumenting; the fourth is already being counted by Support, which makes it the one available on day one.
01 Projected
Conversion completion
Start to confirmed, on the FX flow. The design bets that showing cost earlier loses fewer people, not more.
02 Projected
Drop-off at confirmation
The exact point where cost used to appear for the first time. If the breakdown works, this is where it shows.
03 Projected
Time on the three recurring tasks
A payment, a balance check, a conversion. These are what a controller does on a Tuesday, repeatedly.
04 Reported
Transparency support tickets
The queue that started this project. Support already counts them, which makes it the one measure available on day one.
First though, the cheapest test there is: a moderated comprehension run on the converter. Show someone the breakdown, take it away, ask what the transfer costs. If they can’t answer, the fee is still hiding.
Testing preview
What We Validated Through Testing
I tested the redesigned payment journeys to understand whether finance
controllers could find the information they needed, understand the
true cost of a conversion, and act without unnecessary friction.
01
Original pain point
Conversion costs appeared too late
What testing validated
Users could see the FX rate, fee and amount received before committing.
02
Original pain point
Key data was scattered across screens
What testing validated
Balances, rates and transaction status were brought into a clearer, task-focused hierarchy.
03
Original pain point
Core tasks took unnecessary steps
What testing validated
Payment and conversion actions were easier to locate and complete.
04
Original pain point
Payment status was easy to miss
What testing validated
Clearer status information made failed and pending payments more visible.
