Shivya Tripathi
Fintech
Self-Initiated
MVP · Product Thinking
High-Stress UX
A fintech error state that focuses on reducing panic,
preserving trust, and giving users control when money is
at risk.
1
Critical
moment
0
Panic
triggers
∞
Trust at
stake
Why I Built WiseTrade
WiseTrade started as a self-initiated idea. I kept noticing how
intimidating investing apps feel for people who are just
starting out. Most of them assume users already know what
they're doing — the language, the risks, the systems.
I wanted to explore what a fintech app would look like if it
behaved more like a calm mentor than a trading terminal —
an app that teaches before pushing action, explains without
overwhelming, and stays composed when things go wrong.
WiseTrade became a way for me to design a product where
learning and investing coexist, instead of one pretending the
other doesn't matter.
New investors are usually
—
Scared of losing money
—
Unsure if they're making the "right" move
—
Hesitant to act because one mistake feels irreversible
🦉
WiseTrade as Calm Mentor
The behavioural contract this product makes with users
Teaches before pushing action — knowledge precedes every
transaction
Explains without overwhelming — the right amount of
context at the right moment
Stays composed when things go wrong — errors become
decision points, not failures
Never dramatizes risk — honest about market realities, calm
in delivery
Design constraint
"How do we design a product where every decision — including
errors — reinforces trust rather than eroding it?"
Defining the Brand Before the Interface
Before designing any screens, I needed to be clear about what kind of fintech this
was. So I worked backwards from how a first-time investor actually feels — not from
brand guidelines or reference apps.
Step 01
Understanding
the user's
mindset
Observation
New investors aren't excited when money is involved.
They're cautious, anxious, and afraid of irreversible
mistakes.
Decision
Calm mentor
A brand that behaves like a calm mentor, not a fast
trading app.
Step 02
Choosing the
tone
Problem → Constraint
Most investing apps are either too playful (reduces
trust) or too technical (increases fear). Neither served
a first-time investor.
Decision
Serious but empathetic
Confident without being cold. The tone has to hold
the user steady.
Step 03
Visual direction
Intent
If the product is about trust and focus, the interface
cannot be loud.
Visual rules
Dark mode dominance for calm and concentration.
Minimal colour. No aggressive reds. Clean, structured
layouts.
Step 04
Building the
identity
Meaning
I needed a symbol representing learning, awareness,
and guidance over time.
Symbol
The owl
Abstracted into a minimal geometric mark. The infinity
form reinforces continuity: learning → investing →
learning again.
Step 05
Colour logic
Emotion → Palette
Dark tones establish trust and legitimacy. Gold signals
guidance and important actions — used sparingly.
Outcome
A dark, trust-first palette where highlights are
intentional, not attention-seeking.
The Moment Where Things Go Wrong
The scenario
For an experienced investor, this is annoying. For a first-time investor, this is terrifying. This
is where most fintech apps unintentionally break trust — and where WiseTrade had its
biggest design opportunity.
What the user is thinking
Not about system logic. About
survival.
"
Is my money stuck?
"
Did I mess this up?
"
Am I about to lose everything?
At this point, no user is thinking about
system limitations, market volatility, or
retry logic.
The usual patterns I wanted to
avoid
How most fintech apps handle
this
— Generic "transaction failed"
messages
— Red warning states that amplify
panic
— Forced retries with no explanation
— No meaningful action except "go
back"
All of these push users into rushed
decisions — exactly what a learning-first
fintech should avoid.
The real opportunity
This wasn't just an error to
handle.
It was an opportunity to slow the user
down, reassure them before they act,
and give them control without
pretending the risk doesn't exist.
Instead of asking "how do we fix the
error?" the real question became:
"How do we protect the user's trust
when the system can't proceed?"
The design principle that shaped every decision in this project
So instead of treating this as a broken action, I treated it as a
decision point. The interface needs to do three things in
sequence — and the order matters as much as the content.
Anything beyond these three things increases panic. The
challenge was resisting the impulse to over-explain or over-
qualify. In high-stress UX, less is almost always more.
Every word, every action label, every piece of visual hierarchy
in this screen was weighed against a single question: does this
make the user feel safer, or does it make them feel worse?
What the user needs in this moment
In this exact order — sequence matters
1
Confirmation that their money is safe
Before any action is offered, fear of loss must be addressed
2
Time to think without pressure
No forced retries. No countdown. Just space.
3
A way to act that doesn't make things worse
Control without chaos — the next step must feel safe
Withdrawal failure state
Design system
The Key Decision: Pausing Instead of Failing
Core mechanic
Hold Withdrawal
The request is paused, not cancelled — and th
user stays in control.
Rather than presenting the error as a dead end, the interface reframes the failure as aprotective
action. It feels intentional, not broken — and it aligns with WiseTrade's role as a calm mentor. The
interface is honest about market fluctuations, but it doesn't dramatize the situation. The goal isn't t
hide risk. It's to prevent panic.
⏸
Stops the immediate panic response
Pausing instead of failing gives the user a
moment to breathe before making another
financial decision.
🔓
Gives users time without locking them
out
The request is held, not deleted. Users can
return, review, or cancel on their own terms.
⚖
Avoids rushed financial decisions
Urgency is the enemy of good financial
decisions. Removing time pressure is itself a
protective design move.
Withdrawal attempt
Full flow overview
Hold state · Trust restored
What This Project Taught Me
Reflection
"When users are under stress, clarity matters more than speed — an
reassurance matters more than features."
This project reinforced how different financial design is
when real money is involved. A technically correct solution
can still fail if it doesn't address the user's emotional state
first.
Designing this made me more conscious of how small
choices — tone, hierarchy, and default actions — can either
increase panic or restore trust. Those are not the same
thing as good UX and bad UX. They are the same UX
working in opposite directions.
The "Hold Withdrawal" mechanic wasn't a technical
solution. It was a psychological one. It told the user: the
system noticed something went wrong, and it's protecting
you while you decide what to do next.
That's the kind of design I want to do — not just surfaces
that work, but products that make people feel capable and
respected even when the system can't give them what
they asked for.
Shivya Tripathi · Product / UX Designer
Home
Work
About
Contact
© 2025