Clarity
Make the recipient, value, funding source, state, and consequence of an action understandable at the moment of decision.
CASE STUDY / 01
Projects at PayPay
A selection of shipped financial-product work at PayPay, combining hands-on design and team leadership across an interconnected wallet.
- Company
- PayPay
- Role
- Lead Product Designer · Wallet Design Lead
- Team
- Six product designers · product, engineering, research, and business partners
- Period
- 2020—2023
How I approached the problem
01Problem
After P2P Chat launched, new users sometimes typed a number into the message field expecting it to be an amount input. The interface exposed a mismatch between the product model and users’ expectations.
View detail — Problem02Exploration
Make sending money more discoverable without turning arbitrary chat input into a financial action or removing confirmation.
View detail — Exploration03Solution
Recognise a numeric entry and offer an explicit ‘Send ¥X’ shortcut, then route people through the existing review and payment flow instead of converting text directly into a transaction.
View detail — Solution04Validation
The source analytics snapshot shows shortcut taps rising from November to December 2022. This supports adoption, but does not establish that the shortcut caused overall transaction growth.
View detail — Validation
01 — Context
PayPay was expanding from everyday payments into a broader wallet spanning peer-to-peer transfers, points, balances, and personal financial activity. Each area had its own goals and delivery constraints, but customers experienced them as one product.
The work was to make fast, high-consequence financial actions understandable—and to keep the experience coherent while several product teams shipped in parallel.
02 — Problem framing
What the design had to solve.
Trust
Treat confirmation, reversibility, error prevention, and transaction status as core product behaviour—not edge-case polish.
Coherence
Use a shared interaction and visual language across transfers, activity, points, and the wider wallet.
03 — Design reasoning
Design the consequence, not only the screen.
I used one reasoning path to turn feature requirements into complete financial experiences.
Name the financial consequence
Start with what changes for the customer: who receives value, which balance changes, and what must remain visible after the action.
Follow the complete state journey
Map entry, selection, review, confirmation, receipt, notification, history, and recovery instead of treating the feature screen as the whole product.
Make the trade-off explicit
Balance speed against reassurance and information density against comprehension, then document why the chosen hierarchy is safe enough for everyday use.
Align the system before release
Review copy, components, exception states, accessibility, and engineering constraints so the final experience works as part of the wallet—not as an isolated flow.
What must the customer understand before, while, and after money moves?
04 — Shipped problem solving
Four shipped problems. Four design responses.
01P2P CHAT
Bring coordination and money movement into one understandable thread
- Problem
- People used separate contexts to coordinate a purchase, send money, acknowledge receipt, or explain a request. The transfer worked, but the social intent around it was easily lost.
- Design decision
- Connect conversation and transaction states while keeping money actions visually distinct. Recipient, amount, request status, and completion remain traceable from the thread into the payment flow.
- Trade-off
- Make the interaction feel as immediate as messaging without allowing chat conventions to obscure a financial commitment.
02EASY SEND
Turn a common misunderstanding into a safer shortcut
- Problem
- After P2P Chat launched, new users sometimes typed a number into the message field expecting it to be an amount input. The interface exposed a mismatch between the product model and users’ expectations.
- Design decision
- Recognise a numeric entry and offer an explicit ‘Send ¥X’ shortcut, then route people through the existing review and payment flow instead of converting text directly into a transaction.
- Trade-off
- Make sending money more discoverable without turning arbitrary chat input into a financial action or removing confirmation.
Source: product analytics snapshot reproduced in Zeke’s original portfolio, Oct–Dec 2022. Counts are shown as reported and do not by themselves establish causality.
03PFM
Turn a stream of wallet activity into something people can interpret
- Problem
- Payments, transfers, points, and refunds produced activity with different meanings. A flat list made scanning and investigation difficult.
- Design decision
- Use a layered hierarchy: overview for orientation, distinguishable activity types for scanning, and detail when a customer needs to investigate.
- Trade-off
- Provide useful financial context without making an everyday wallet feel like professional accounting software.
PFM shipped, but its section in the source portfolio still contains draft placeholders and a duplicated cover. Detailed imagery is intentionally omitted until reliable source screens are added.
04DESIGN SYSTEM
Turn repeated decisions into a shared product foundation
- Problem
- Parallel teams could solve similar interface problems differently, creating avoidable inconsistency and repeated implementation work.
- Design decision
- Define reusable foundations for spacing, typography, layout, components, and states, then connect system decisions back to shipped product use cases.
- Trade-off
- Standardise recurring patterns while leaving room for a product team to address a genuinely different financial problem.
05 — Transaction design
A transfer is a journey of changing confidence.
The interaction was never only ‘enter an amount and tap send.’ The design had to keep people oriented as risk increased, money moved, and the system resolved.
Context
Keep the entry point and recipient relationship visible.
Amount & source
Make the value and funding source explicit before commitment.
Review
Prioritise the information that can prevent an expensive mistake.
Status
Distinguish completed, pending, rejected, cancelled, and expired states.
After the transfer
Reconnect receipt, notification, history, and recovery to the same transaction.
A simplified model of the shipped P2P journey, redrawn for portfolio clarity. The work shown in the source portfolio was publicly released.
06 — Ecosystem view
Design decisions crossed product boundaries.
P2P Chat, Easy Send, PFM, points, notifications, and transaction history shared the same underlying questions about identity, value, status, and trust. Making those dependencies visible before implementation was both a product-design and design-management responsibility.
01P2P Chat
02Easy Send
SHARED WALLETIdentity · Value
Status · Trust
Status · Trust
03PFM
07 — Design leadership
Scale judgment, not only output.
Set direction
Clarify the problem with product partners, connect feature work to the complete wallet, and give each designer a decision frame rather than a prescribed screen.
Raise decision quality
Review hierarchy, financial language, interaction logic, edge cases, accessibility, and implementation feasibility—not visual finish alone.
Scale ownership
Maintain visibility across parallel initiatives, run critique, and coach designers to explain and defend decisions independently.
08 — Product & team impact
Evidence without inflated metrics.
- 01
P2P Chat, Easy Send, PFM, and the design-system work represented in the source portfolio all reached production.
- 02
Easy Send addressed a documented comprehension problem by turning numeric chat input into an explicit shortcut while preserving review before payment.
- 03
The original analytics snapshot records transactions rising from 16,874,749 in Oct 2022 to 20,117,657 in Dec, and shortcut taps from 386,025 in Nov to 602,357 in Dec.
- 04
Shared foundations gave designers and engineers a more consistent starting point for recurring interface decisions.
Release status and public availability were confirmed by Zeke. Quantitative values are reproduced from the Easy Send product-analytics snapshot in the original portfolio (Oct–Dec 2022); they are descriptive, not a claim that the shortcut alone caused the change. PayPay and related trademarks remain the property of their respective rights holders.
Official product — PayPay on the App Store09 — Reflection
Trust is an ecosystem property.
The strongest design leadership was not approving more screens. It was helping the team frame the consequence, expose the trade-off, and carry a decision through every state of the product. That made problem solving visible at both interface and organisational scale.