TT Wallet · Mobile app · 2022
Untangle three entry points before adding a fourth
In a wallet that had 400K+ monthly users at the time, people mixed up Deposit, Buy Crypto and Receive. A wrong pick could mean an irreversible transfer. I was asked to add a credit card entry point. I saw an information architecture problem and redesigned the deposit flow.
Role
Product Designer: research, strategy, UI/UX, flow design
Team
Product, Engineering, Marketing
Duration
2022
400K+
TT Wallet monthly users at the time (platform scale)
The brief
"Add a credit card entry point."
Connect a third-party card service and add one entry point. It looked like a one-day job.
“Let TT Wallet users buy crypto with credit cards, and clean up the deposit entry points.”
What I saw
The structure itself was confusing people
When I walked through the existing paths, I found two problems:
How a small mix-up becomes lost money
A small mix-up
Wrong choice
Keeps going
Confirms
Money lost
Adding one more entry point to a confusing structure would make it worse.
I told the team the deposit flow's information architecture needed a redesign. They agreed to widen the scope.
My first version (v0)
It looked smart. I killed it myself.
Users couldn't tell which feature they needed, so my first idea was to ask them.
Right after tapping Deposit, v0 asked people to pick: "I have crypto" or "I try to buy crypto". Then it sent them to the transfer flow or the card flow.

When I walked through the user journey with the team and played out different situations, "I have crypto" read in very different ways:
v0 asked users for a judgment many couldn't make, then locked them into a path that might be wrong.
Final design
Show users their real situation instead of sorting them
After dropping v0, I rebuilt the deposit flow on three principles.

Side by side, no recommendation
Deposit and Buy Crypto sit side by side with equal weight, and users can switch at any time.
Show options instead of asking questions
The flow lists the supported tokens, so users see which ones they hold.
Nothing is final until the last step
Users can change the token or network until they press "Pay Now."

Four equal buttons. Users mixed up Deposit and Receive.
Four equal buttons. Users mixed up Deposit and Receive.

Equal weight on purpose. No suggested next step. The user decides.
Equal weight on purpose. No suggested next step. The user decides.
My call: decision safety first, faster conversion second.
Hover over a phone to see notes
Friction I accept, and outcomes I don't
Acceptable friction
- Slower decisions
- Some users leave midway
Unacceptable outcomes
- Losing money over a misunderstanding
- A result users didn't expect
Where a choice becomes final
Reversible
No payment yet
Can go back
Review
Irreversible
Payment confirmed
After launch
What I'd watch
- Deposit completion rate
- Support tickets for wrong-network transfers
- How often people switch from Deposit to Buy Crypto
I don't have post-launch conversion data for this version. What I can stand behind is the structure: three entries untangled before a fourth was added.
Reflections
What I learned
Feature requests often hide architecture problems.
If I had just added the entry point, I would have finished fast and made things worse. Now I check whether a brief asks the right question before I start.
Dropping my own design was harder, and worth it
v0 was my design, and it made sense on paper. Dropping it meant admitting my first idea was wrong. If I had kept it anyway, users would have paid for my mistake.