Ashley Cheuk

Product Designer

Incorrect password — try again.

Reap · Fintech · B2B

Introduced a multi-card creation flow so businesses can scale efficiently.

Role: Product Designer & Researcher
Year: 3-day design sprint, Nov 2025

Reap is a B2B stable coins payment platform helping businesses manage expenses through virtual credit cards. Reap shared that for businesses scaling operations, their card creation flow had two compounding problems.

Compounding problems

Creating multiple cards required repeating the same process from scratch each time.

Key configurations throughout the flow weren't clear enough to act on confidently.

My Role

End-to-end workflow refinement.

This was a design concept sprint where I owned the full process of journey refinement and task automation through systems thinking. I delivered a final usable prototype to Reap.

Final design

Duplicate or create multiple cards at once

Businesses can now create or duplicate multiple virtual cards or configurations through feedback loops, eliminating the need to repeat the same process from scratch.

Card configurations users can act on confidently

Spending limits, restrictions, and expiry are described and structured intuitively before users commit.

Introduced 2FA to strengthen security

As uncovered through interviews, trust is consistently underdesigned in fintech. Adding a verification checkpoint at the highest-stakes moment costs minimal friction and meaningfully boosts user confidence.

Original design key insights

By interviewing 4 users on the original design, I identified that:

Creating multiple cards is not only time consuming, but creating them all from scratch encourages user errors.
Customizing card settings is not intuitive to many — resulting in a success rate of 75%.
Half of users raised the lack of security in submitting the virtual cards.

Original design

01 · Entry

↳

No batch creation available

02 · Card details

↳

Ambiguous meaning of budget pool and card categories

03 · Card configurations

↳

Unclear visualization of limits and customizations

04 · Review

↳

Limited to one card at a time. Singular password security also reduces trust

05 · Success

↳

Must restart flow for each card

Slide to view →

How might we redesign the card
creation flow so it's intuitive, scalable,
and user-friendly?

Industry benchmarking

I studied virtual card flows from Navan and Klarna, and multi-step credit card flows from Wise and Stripe — four platforms that had solved similar friction points well.

Navan Klarna Wise Stripe

Role based interfaces

Labels paired with contextual examples and reason of relevance reduce interpretation errors and encourages input.

Feedback loops

Showing a card graphic before submission lets users validate their setup and catch errors early.

End-to-end thinking

The best platforms guide users beyond form completion — into how they'll actually use what they've created.

Task automation

Pre-populated fields and suggested values cut repetitive input.

The gap wasn't missing features — it was missing context. Best-in-class platforms don't just collect information, they guide users through it.

Reflection

This was a sprint, not a ship

Creating multiple cards is not only time consuming, but encourages user errors. Here's how I'd measure success:

Quantitative

Time-on-task

How long does it take to create 3+ cards in the new flow vs. the original?

Completion rate

Task completion without error or mid-flow drop-off

Qualitative

A/B sessions

Moderated sessions with Reap users — watching closely for hesitation at card configuration

Post-submission confidence

How did users feel about the customisations chosen?

What I'd explore next

Deeper systems thinking — does card duplication reduce errors or speed them up at a holistic level?

The shortcut assumes users want similar cards. If configurations vary a lot in practice, it might create a false sense of efficiency worth testing.