Let's begin with the top-up screen
What do we know about the users?
From data, we found that users tend to top up small amounts multiple times instead of adding a larger amount at once.
I dug deeper into past research and surveys, and identified several reasons behind this behavior:
Users don’t feel secure keeping a large balance in PayPay.
The current input method for amounts isn’t easy for users.
Many users are unsure how much they actually spend with PayPay each month
Why is this a problem?
Each top-up comes with a processing fee—ranging from about ¥10 to ¥200 depending on the method. With PayPay’s large transaction volume, these fees quickly add up on the operations side, costing tens of millions of yen each month.
How do we going to solve it?
Our goal is to reduce the frequency of top-ups by encouraging users to add larger amounts at once.
For this test, we started with the assumption that:
Showing users their total spending last month with other improvement could encourage them to top up a similar or larger amount at once.
And to validate this assumption, we decided to run an A/B test.
Show users how much they spent last month
Make it easy to top up that amount with just a tap
For the first idea, I thought about adding an entry point to the spending history page, making it easy for users to see their past spending.
So I placed the spending amount directly on the top-up page.
For the second option, I considered adding a new quick amount button that displays the spending amount, placed ahead of the other quick amount buttons.
So I kept the number but moved the descriptive text into a tooltip for a cleaner layout.
As third idea, I considered adding the button and spending information to the bottom bar.
So I switched to a floating button to make it less intrusive, and added a dismiss icon so users could easily close it.
Testing case ①
Testing case ②
Testing case ③
Where I introduced a new pattern that lets users tap the placeholder to auto-fill the recommended amount.
So, I removed the behavior, moved the banner below the input field with a higher-contrast color, and integrated the suggested amount button directly into it.
This made the design less intrusive and maintained the input field as the primary focus in the information hierarchy.
Before
After
So (drumroll...) I proposed adding a “clear amount” icon button that appears when the input field is focused, which is also a common pattern in finance apps.
It’s a small touch, but I believe it also improves the experience for regular users.
So I added a security message and a link to the help page to reassure users and boost their sense of safety.
Highlight to users that they can cash out anytime, plus a link to the help page.
Player ①
I added an extra quick amount button to make it easier for users to input the recommended amount.
To show last month’s spending, I used the input field’s placeholder—since tooltips aren’t ideal for longer text and can impact readability.
Player ②
In this version,
I used a banner to display the user’s spending from the previous month, along with a text button that lets them input the recommended amount with a single tap.
🎉 It’s Player ①

Timeline
Responsibility
Company