Payoneer · Senior Product Design · 2023 to 2026

Two Flows, One Path

How I unified the way people pay on Payoneer, on web and native mobile.

At a glance

Role
Senior Product Designer
Timeline
2023 to 2026 (with one long pause)
Platforms
Web, iOS and Android
Status
Ships August 2026
  1. 2023Mapping, research, wireframes
  2. PausedEngineering moved to a company migration (I worked on Withdraw to Bank meanwhile)
  3. 2025Back, with a design system and Maze tests
  4. Sep 2025Handed off web (full walkthrough, open edge cases listed), moved to mobile
  5. May 2026Every mobile flow done
  6. Aug 2026Ships

01The problem

Two products. They never talked.

One paid into a Payoneer balance (instant, if you had their email). The other paid into a bank account (days to verify, then days to send).

People would type in someone's bank details, find out they had a Payoneer account too, and start over. And every new feature got built twice, once per product.

02Research

Flow mapping: internal first, external second

I mapped our 3 existing flows first. Then the same flows at Wise, Revolut, PayPal, Mercury and Airwallex. Every payment came down to 4 questions:

  • 01Who are you paying?
  • 02Where's the money coming from?
  • 03What are the details?
  • 04How do you confirm it?

03Finding the shape

Three structures, a mashed-up winner

  • V15-step flow, scheduling lived inside the amount step.
  • V25-step flow, scheduling got its own step.
  • V34-step flow, recipient and transfer type together, behind a mega dropdown.

No clear winner, but we made a combo. The big plan (3 products and batch payments, all in one place) didn't fly. Research kept withdrawals separate, batch got saved for later, and single payments became this project.

04The real scope

It looked like two flows. It was closer to twenty.

Recipient
  • Saved
  • New
  • Not on Payoneer yet
Currency
  • Same
  • An exchange
Timing
  • Now
  • Scheduled
  • Recurring
Paid from
  • Balance
  • Card
  • Bank
  • Company budget
Paid into
  • One method
  • Several
Roles
  • One person
  • A contributor plus an approver

I mapped every combination, for first-time and returning users, plus errors and payment tracking.

05Round two

Back in 2025. New design system, new rules.

Solid components, but anything new needed the design system team's OK. Testing a prototype in Maze showed people weren't sure which contact to pick, or where the money would land. I made changes, but we never got to test them again.

06Mobile

Same flow. Smaller screen.

In September 2025 I handed the web flow to another designer and joined the mobile team, right as this flow was heading there.

The app's design system was broken. No autolayout, a dark mode that didn't match light mode, 3 ways to select the same thing. A UX consultant agreed we should start fresh, management said yes, so I rebuilt it. This flow was one of the first things built on it.

07Where it stands

Two products. Two mental models. Now one.

Ships August 2026. Metrics stay internal, so no numbers here.