Fragmented Operations
Wallet, KYC, payments, and compliance lived across separate tools.
Case Study · WalletAllIn
Wallet and Payment Operations for a Regulated Finance Product
Financial decisions depended on data scattered across wallet, payment, KYC, and compliance systems. I mapped the workflow and simplified critical decision paths.
RoleProduct Designer
ScopeUX architecture, workflows, UI system
DomainWallets, payments, regulated operations
StatusPublic summary
01 · Context
Financial operations needed clearer decisions, not more screens
I mapped the workflow across systems and clarified where risk, state, and next action belonged.
Hidden Risk Context
Operators had to reconstruct why actions were risky.
Unclear Decisions
Approvals and escalations lacked visibility and confidence.
02 · Design Direction
From transaction UI to operational trust layer
Fragmented review
Users had to connect wallet activity, payment status, and risk context manually before acting.
Guided operations
The interface made state, consequence, and next action visible inside the workflow itself.
"The goal was to make risk, state, and next action visible."
03 · Compliance
Compliance as Product Infrastructure
Compliance became part of the workflow, not a separate system.
Compliance OS Demo
WalletAllIn operations console
04 · Product Work
The work centered on structure, states, and reusable patterns
Unified Operating Model
Connected wallet, payment, KYC, and review workflows.
Guided Decision States
Made risk, review, and payment states explicit.
Reusable Trust Patterns
Created scalable patterns for status, audit, and exceptions.
05 · Outcome
A cleaner product story for high-trust financial workflows
Reduced workflow fragmentationStandardized high-risk statesCreated reusable compliance patternsDelivered an NDA-safe product story