Product Designer

2019 — 2020

Merchant onboarding flow: a payment-collection question, three service package tiers, and a plan configuration screen with a live pricing summary — Three onboarding steps: how a merchant takes payments, which service tier fits, then configuring it with the price updating live

I led product design at Verifone, a global payment service provider, across three workstreams over about a year: merchant onboarding, the payment gateway itself, and the company's first design system.

Onboarding started with a simple question, how a merchant takes payments, then walked them through picking a service tier and configuring it, the monthly price updating live as they added payment methods and picked a contract length.

Grid of payment method logos including Visa, Mastercard, PayPal, Apple Pay, Klarna, Alipay, WeChat Pay, iDEAL, and SEPA — The payment methods a merchant's checkout could support, from major card networks to regional and wallet-based schemes

The gateway underneath supported dozens of payment methods: cards, wallets, and regional schemes, from Visa and Mastercard to iDEAL, Alipay, and WeChat Pay, so a merchant's checkout matched however their customers actually wanted to pay.

Verifone merchant dashboard transactions table with search, date and organization filters, payment method and status columns, and an Export as CSV button — Transaction history with search, filters, and status at a glance, authorized, settled, or settlement requested

Merchants tracked payments through a transactions dashboard: searchable by ID, filterable by date and organization, each row showing payment method and status. A CSV export handled reconciliation.

Verifone design system sheets showing color palette, typography scale, button variations, text input and selector states, and message, alert, and toast patterns — Verifone's first design system: color, type, components, and states documented once for every product team to reuse

I also built Verifone's first design system, color and type scales, input and selector states, buttons, and message patterns for alerts and toasts, so product teams pulled from one shared source instead of rebuilding components per feature.