CUSTOMER STORYTELLING — JOURNEY → DECK → INTERACTIVE DEMO → HANDOFF
A customer-ready story for safer UPI payments—risk signals teams can demo and ship
Translated fraud + payment constraints into a clear journey narrative, interactive prototype, and deck-ready system—built to explain risk decisions fast, reduce errors, and scale with reusable patterns and consistent language.
Metrics: 10 key screens • 12 components • 1 journey map • 3 story iterations • 6 feedback loops
ROLE
Experience Design (UX)
EXPERTISE
Journey • Content system • Prototype • Handoff
YEAR
2024
UPI Shield is a trust-first safety layer for UPI payments—built to help users verify intent, understand risk, and recover safely without slowing down everyday transactions. Instead of fear-based warnings, it uses clarity-first risk cues, safer defaults, and one-tap recovery actions (cancel / hold / report / block) so decisions stay fast, confident, and explainable.
The work is designed for both demo and delivery: risk + business requirements → threat scenarios → decision flow → interactive prototype → reusable warning components + edge states → handoff-ready specs. Everything is packaged as a customer-ready story that teams can present consistently and engineers can implement reliably.
Timeline
3–5 weeks — Requirements/Threat scenarios → Decision flow → Hi-fi → Interactive demo → Validation loops → Handoff
Shipped: warning component kit + variants, risk states (empty/loading/error/recovery), and dev-ready specs for consistent rollout.
Why this matters
UPI fraud often happens in seconds—users act under pressure (calls, urgency, fake “refunds”). A good solution must reduce cognitive load, explain risk in plain language, and make the safest next action the easiest—while providing recovery when mistakes happen.
UPI Shield turns a high-stakes moment into a clear decision path that’s easy to demo to stakeholders and consistent to implement in production.
Deliverables
Decision flow • Risk-cues system • Interactive prototype • Storyboard • Reusable warning templates • Handoff specs
End-to-end, trust-first experience design—aligned early with stakeholders, built around decision moments, and packaged as demo-ready storytelling assets + ship-ready specs.
1) Cross-functional + constraints
Partnered with PM + Engineering to translate fraud risk + trust constraints into a clear decision system (moments, logic, and edge cases).
Aligned on feasibility early so what we demo matches what we can ship.
2) Templates/flows/diagrams
Used reusable templates to map risk moments, decision flows, and state behavior—making the “before → after” story easy to understand and reducing rework in build + review.
3) Fast iteration
Iterated rapidly from flows → wireframes → hi-fi → interactive prototype.
Used feedback loops to refine warning clarity, hierarchy, and the safest next action at every step.
Research & Insights
Identified high-risk moments where users act under pressure: “refund” scams, fake support calls, urgency scripts, screen-share manipulation, misleading merchant names.
Synthesized into 3 JTBD:
“Verify intent before I pay.”
“Understand risk in one glance.”
“Recover quickly if I made a mistake.”
Defined success metrics: decision clarity, time-to-confirm, error avoidance, perceived control.
UX flows & information architecture
Designed around decision moments (not screens):
Intent check (pay vs request vs collect)
Risk check (context + patterns + merchant/payee signals)
Confirm (amount/payee clarity + safer defaults)
Recovery (hold/cancel/report/block + next steps)
Prototyping & iteration
Ran rapid iterations on:
Warning hierarchy (what shows first, what’s expandable, what’s the primary action)
Microcopy rules (plain language, “why risky” in one line, no panic tone)
Confirm clarity (receiver + amount prominence, friction only when needed)
Edge states (mismatch, unverified payee, network delay, false positives)
Handoff-ready specs
Delivered a reusable warning + state system:
Variants by risk severity + scenario
Empty/loading/error/recovery states
Dev-ready interaction notes + component specs—so implementation stays consistent, testable, and scalable
Deliverables
Decision flow • Risk signals system • Interactive prototype • Storyboard/deck-ready narrative • Component + state library
UPI Shield delivers calm, fast payments by making risk understandable before confirm—and making recovery effortless after mistakes. Built as a customer-ready story: clear signals, safer defaults, and one-tap next steps—easy to demo and consistent to ship.
1) Reusable system contribution
Built a scalable risk + warning system (severity levels, context rules, layout patterns, and state behavior) so experiences stay consistent across flows and adapt as fraud patterns evolve.
2) Demo-ready prototyping + spec handoff
Delivered interactive prototypes and clean handoff specs (states, variants, redlines, empty/loading/error/recovery) and partnered with Engineering for implementation + QA—ensuring what we present matches what ships.
Clarity-first confirmation
Redesigned the confirm step to surface who, what, and why upfront—receiver identity + amount + context—with clear hierarchy.
Impact → fewer “wrong person” mistakes • faster, more confident confirms
Safer defaults in high-risk moments
When risk increases, defaults shift to safer actions (review details, verify payee, use alternate method, delay payment) with minimal extra effort.
Impact → reduced impulsive confirmations under pressure
Risk cues that don’t panic users
Introduced Low / Medium / High risk badges backed by one-line reasons (unusual amount, new payee, mismatch, suspicious request pattern) in plain language.
Impact → better decisions without fear-based UX
One-tap recovery & reporting
If something feels wrong, users can Hold / Cancel / Report / Block with clear next-step guidance (what happens next, support options, timeline).
Impact → faster recovery • reduced helplessness after mistakes
Outcomes from UPI Shield’s end-to-end experience design—built to reduce payment anxiety, prevent high-cost errors, and enable calm, fast recovery. Packaged as a customer-ready trust story that’s easy to present and consistent to ship.
Reduced fraud-prone mistakes
Clear intent cues + a stronger confirmation hierarchy reduced “request vs pay” confusion and wrong-recipient sends—especially under pressure.
Impact → fewer wrong actions • higher perceived control • safer decisions before confirm
Faster, more confident confirmations
Plain-language risk reasons helped users understand “why risky” in seconds—without overthinking or panic.
Impact → less hesitation • fewer “what now?” moments • quicker confident confirms
Stronger recovery when users slip up
One-tap Hold / Cancel / Report / Block flows reduced panic and provided immediate next steps with clear outcomes.
Impact → faster recovery • fewer dead-ends • higher confidence after mistakes
Scalable foundation for shipping
Reusable warning components + state-driven patterns kept behavior consistent across scenarios and simplified rollout.
Impact → cleaner specs • faster iteration loops • easier expansion (new risk rules, new payment contexts)
Learning
In high-stakes finance UX, trust isn’t “more warnings”—it’s clear intent, explainable risk, and graceful recovery.