Redesign unified Samsung’s fragmented wallet and payment experiences across phone and watch. The new platform simplifies onboarding and payments, elevates trust through visible security, and integrates cards, loyalty, and passes into one intuitive app.
Executive Summary
We reimagined Samsung Wallet/Pay end-to-end, merging disparate features, clarifying security, and streamlining key tasks. The redesign increased adoption, transactions, and satisfaction while establishing a scalable foundation for future financial services.
Problem Statement
Multiple apps and inconsistent flows eroded trust and usability. Users faced confusing setup, unclear security, weak card management, and uncertainty around merchant acceptance, leading to low adoption and high onboarding drop-off.
Research & Discovery
Competitive review: Apple Pay, Google Pay, regional apps
Security perception studies; merchant/partner research
Personas: tech-savvy early adopter; security-conscious mainstream; cash-preferring skeptic
Key insights: show security without friction; unify wallet and loyalty; surface merchant acceptance; integrate tightly with the Samsung ecosystem.
Design Process
Stakeholder and bank workshops; IA redesign; security-first patterns; journey maps from onboarding to payments. Lo-fi to hi-fi prototypes tested with
60+ participants; iterative refinements for speed, trust, and clarity.
Solution
A unified wallet with streamlined onboarding, biometric authentication, clear acceptance indicators, and consistent feedback across phone and watch for fast, trusted payments.
Key Features
Unified dashboard for cards, passes, and loyalty
Camera card capture and bank integration
Biometric auth with clear status and fallback
Tap-to-pay with haptic/visual confirmation
Categorized history and spend insights
Merchant acceptance locator
Loyalty integration with auto-applied rewards
Quick access from lock screen/notifications
Multi-card and default management
Design System & Visual Language
One UI principles with trust-first hierarchy, security color cues, consistent iconography, purposeful motion, dark mode, and accessible targets/contrast.
NFC reliability; bank API/tokenization variance; real-time merchant data; biometric hardware differences; Wear OS sync/battery; EMV/PCI-DSS compliance.
Business Impact
Greater ecosystem stickiness, stronger merchant partnerships, higher transaction revenue, competitive differentiation, and a base for new financial features.
Challenges & Learnings
Balanced security and simplicity via progressive disclosure; managed complex partnerships and regional norms; addressed device constraints; transparency built trust.
Key Takeaways
Make security visible, not obstructive
Simplify to drive adoption
Earn trust through consistency
Optimize onboarding as the conversion moment
Reflection on leading the Samsung Wallet/Pay redesign as Senior Product Designer. Focused on designing for trust in a high-stakes domain by balancing security, simplicity, and speed across global markets and legacy systems.
Role and Context
Led strategy and execution for four designers, partnering with engineers, PMs, and banking partners. Operated under strict security and regulatory constraints while competing with Apple Pay and Google Pay across diverse markets and devices.
Initial Mindset
Strong in mobile UX, new to financial design and payments regulation. Underestimated how deeply security drives behavior and how fragmented features eroded clarity and trust.
Key Design Challenges
Make security visible without friction
Simplify tokenization, biometrics, fraud concepts
Build trust where money risk is high
Unify legacy systems into one wallet
Design for diverse global behaviors
Balance speed with error prevention
Critical Decisions and Trade-offs
Security visibility vs. simplicity: Progressive disclosure at setup and first payment; reduced minimalism for transparency.
Onboarding depth vs. speed: Deeper education upfront to lower anxiety and support load.
Biometric prominence: Primary auth; PIN backup to set modern expectations.
Card hierarchy: Default to most-used; confirm payments over thresholds.
Merchant visibility: Acceptance locator to reduce uncertainty despite complexity.
Skills Developed
Financial UX patterns and mental models
Trust and security design
Cross-platform for mobile and wearables
High-frequency, high-stakes interactions
Progressive disclosure increased trust
Biometric-first strengthened perception of security
Merchant acceptance reduced pre-payment anxiety
Strong confirmations built confidence
Unified wallet simplified mental models
Lock screen access drove habits
Engage banks earlier in exploration
Invest more in regional behavior research
Start error recovery testing sooner
Build a reusable security pattern library
Define trust metrics beyond adoption
Prototype with real transactions earlier
Unexpected Learnings
Users need to see security working
Confirmations should feel substantial
Loyalty drove adoption more than expected
Wear OS shifted phone expectations
Failed payments disproportionately harm trust
Onboarding completion predicts engagement
Treat trust as a designed outcome. Prioritize transparency over minimalism, design error states early, and deliver contextual education through progressive disclosure. Design for behavior change, not just interface efficiency.
Growth as a Designer
Advanced emotional design for anxiety and confidence, reframed regulation as design parameters, improved facilitation across stakeholders, and led through ambiguity at scale.
Key Takeaways
Trust = visibility, consistency, reliability
Security must be felt to be believed
Simplification requires deep domain fluency
Onboarding wins or loses trust
High-frequency flows demand invisible excellence
Design worst-case scenarios first
Ecosystem integration compounds value
Users trade convenience for confidence when money is involved
User Behavior Observations
Users need to see security working; first payment shapes ongoing trust.
Failed transactions cause outsized anxiety; success confirmations matter.
Loyalty rewards drive adoption more than speed; lock screen access builds habits.
Merchant acceptance uncertainty blocks first use; locator reduces friction.
Biometrics preferred over PINs when explained; Wear OS reshapes phone expectations.