END-TO-END PRODUCT DESIGN — INSIGHTS → RISK FLOWS → PROTOTYPE (DEMO/CODE-READY) → SYSTEM → HANDOFF
A trust-first safety layer that prevents UPI fraud without slowing payments
Defined user + risk needs from high-stakes scenarios, balanced speed vs safety tradeoffs, and shipped a demo-ready prototype + reusable warning system—so decisions are clear before confirm and recovery is effortless after mistakes.
Risk scenarios • decision flows/IA • hi-fi + interactive prototype • narrative walkthrough/demo • component + state system • handoff specs
Metrics: 10 key screens • 12 components • 1 journey map • 3 story iterations • 6 feedback loops
ROLE
Product/UX Designer
EXPERTISE
High-stakes UX • Interaction/Visual Design • Prototyping
YEAR
2025
UPI Shield is a trust-first safety layer for UPI payments that keeps transactions fast while making risk understandable and recovery effortless. I translated high-stakes fraud scenarios into clarity-first decision moments—intent verification, explainable risk cues, safer defaults, and one-tap recovery actions (hold/cancel/report/block)—so users can act with confidence under pressure.
The work spans end-to-end product design from insight to delivery: business + risk requirements → decision flow + IA → hi-fi + interactive prototype (demo/code-ready behaviors) → reusable warning components + state system → handoff-ready specs. I packaged the solution as a narrative walkthrough for stakeholders and engineering, ensuring what we demo matches what ships and scales consistently.
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 risky moment into a clear decision path that’s easy to communicate to stakeholders and consistent to implement.
Deliverables
Threat scenarios • decision flow + IA • risk cues system • interactive prototype • narrative walkthrough/storyboard • reusable warning templates • handoff specs
End-to-end, trust-first product design—aligned early with stakeholders, built around decision moments, and delivered as a demo-ready prototype + ship-ready specs. Focus: reduce cognitive load, prevent high-cost mistakes, and make recovery effortless without slowing payments.
1) Cross-functional + constraints
Partnered with PM + Engineering to translate fraud risk + trust constraints into a clear decision flow—balancing speed vs safety, defining risk states + recovery paths, and aligning early on feasibility so the demo story matches what ships.
2) Templates/flows/diagrams
Used repeatable templates to map risk moments, flow logic, and state behavior—helping stakeholders quickly understand the “before → after” trust narrative and reducing rework during build and reviews.
3) Fast iteration
Iterated rapidly from flows → wireframes → hi-fi → interactive prototype, incorporating feedback loops to refine warning hierarchy, microcopy clarity, confirmation confidence, and recovery behaviors.
Research & Insights
Identified high-risk moments where users act under pressure: “request money” traps, fake support calls, urgency scripts, screen-share manipulation, and misleading merchant names.
Synthesized into 3 key JTBD:
“Pay quickly with confidence.”
“Know if this payment is risky before I confirm.”
“Recover fast if I made a mistake.”
UX flows & information architecture
Designed around decision moments (not screens):
Intent check (Pay vs Request vs Collect)
Risk check (context + patterns + merchant signals)
Confirm (clear receiver + amount + safer defaults)
Recovery (Hold / Cancel / Report / Block + next steps)
Prototyping & iteration
Ran rapid iterations on:
Warning hierarchy (what shows first + primary action)
Microcopy clarity (plain-language “why risky” in 1 line)
Confirm clarity (receiver/amount prominence + friction only when needed)
Edge states (mismatch, unverified, network delay, false positives)
Handoff-ready specs
Delivered a reusable warning + state system:
Variants by risk severity (Low/Medium/High)
States: empty/loading/error/recovery
Dev-ready interaction notes + component specs—so implementation stays consistent, testable, and scalable.
Deliverables
Threat scenarios • decision flow + IA • risk signals system • interactive prototype • narrative walkthrough/storyboard • component + state library • handoff specs
UPI Shield keeps payments calm and fast by making risk understandable before confirm—and making recovery effortless after mistakes. Built as a customer-ready trust story (signals → safer defaults → next steps) and delivered as a reusable system so teams can demo the value quickly and ship consistently.
1) Reusable system contribution
Built a reusable risk + warning component kit with variants (severity, context), layout rules, and state behavior—so the experience stays consistent across flows and scales as new fraud patterns emerge.
2) Demo-ready prototyping + spec handoff
Delivered clickable hi-fi prototypes and clean specs (redlines, variants, empty/loading/error/recovery) and partnered with engineering for implementation + QA—ensuring what we present matches what ships.
Clarity-first confirmation
Redesigned confirm to surface who, what, and why upfront—receiver identity, amount, and context with clear hierarchy.
Impact → fewer “paid the wrong person” mistakes • faster, more confident confirms
Safer defaults in high-risk moments
When risk is elevated, defaults shift to safer actions (review details, verify payee, alternate method, delay payment).
Impact → reduced impulsive confirmation under pressure
Risk cues that don’t panic users
Introduced Low/Medium/High risk badges backed by one-line reasons (unusual amount, new receiver, mismatch name, suspicious pattern).
Impact → better decision-making 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 product design—built to reduce payment anxiety, prevent high-cost errors, and enable calm, fast recovery. Delivered as a demo-ready trust story + a reusable system so teams can align quickly and ship consistently.
Reduced fraud-prone mistakes
Clear intent cues and a stronger confirmation hierarchy minimized “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
Risk cues with plain-language 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 handoff for 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.