Stephen ReaProduct, design & AI strategy
Paysend / Product and practice presentation
Paysend
Work / Paysend

Money movement,
made understandable.

Accounts, cards, transfers and business payments needed a clearer shared model. Customers needed to know what would happen before committing money or information.

6mRegistered users · period context
170Countries · period context
12Product designers in the team
Director of Product Design · Consumer and business products
The context

The problem.
The opportunity.

The surface promise is simple: move money. The product underneath includes recipients, currencies, fees, identity checks, accounts, cards, settlement and recovery. The customer should not have to carry that machinery to complete a task with confidence.

Read moreShow less

I worked across the consumer and business product conversation with a team of 12 designers. The available evidence spans product principles, onboarding logic, navigation, account and transfer surfaces, and roadmap structure. The design question was how to keep the offer understandable as it expanded.

Different products. One clearer money model.

Different products. One clearer money model.Open image for a closer look
The design work

The design
decisions.

  1. 01

    Explain the commitment

    Recipient, amount, fee, delivery and confirmation need to be legible before a person decides to proceed.

  2. 02

    Distinguish useful checks

    Verification and review can protect the customer. Repetition, unexplained questions and hidden states create avoidable doubt.

  3. 03

    Connect the product model

    Accounts, cards, transfers and business flows need shared concepts and clear boundaries, rather than separate local versions of the same task.

Supporting evidence / Open an image for a closer look
Consumer product surfaces
Consumer product surfacesAccounts, cards, exchange and transfers from the original portfolio.
Business accounts
Business accountsOriginal portfolio product presentation.
A product-system conversation
A product-system conversationSupporting roadmap and product-area map.
The outcome

What this
shows.

The work connected product structure, interface decisions and the standards used to discuss quality. Its value is visible in a more knowable product model: what the customer is doing, what needs checking and what happens next.

Read moreShow less

The figures describe company scale reported in the original portfolio at the time, not a measured design uplift. The roadmap is supporting evidence; the product visuals are from the original portfolio.

Got something worth
making better?

Let’s talk

Project evidence

Open original ↗