The first task should lead to the wallet, with verification tied to what comes next.
- Company
- Shiga Digital
Visit Shiga - Industry
- Fintech, cryptocurrency
- Role
- Product Designer
UX writing - Tools
Claude Design, 
Figma- Team
- 1 product designer, 1 product manager, 3 engineers
- Period
- Q1 2026 · 1-week sprint
ENTA brings crypto and fiat services into one wallet. Its individual onboarding asked people to complete identity verification before they could see the product.
Impact TLDR:
- I redesigned the onboarding flow and UX writing around passkeys.
- The new structure separated crypto-only access from ENTA features that require identity verification.
- Dashboard states explained what was available, what was locked and how to unlock it.
Where onboarding lost people
The previous journey put email and password, profile setup and know-your-customer verification (KYC) ahead of the dashboard. People could leave during verification without ever seeing send, receive or swap.
A funnel review with engineering followed sign-up through to the first transaction. Support tickets added the language behind the drop-off: fatigue and confusion before people had moved money. Conversations with product, engineering and compliance helped clarify which actions needed verification.
Crypto-only users wanted to move stablecoins. People using both crypto and fiat needed a route to additional services. Asking both groups to complete the same front-loaded journey hid the distinction between their needs.
The problem was the order of the journey
- Product value arrived too late
- The dashboard sat behind identity verification, leaving little context for why users should continue.
- Different intentions met the same gate
- Crypto-only access and fiat features were treated as a single onboarding requirement.
- Authentication needed its own rethink
- A competitive review of Rabby, Rainbow, Phantom and Fuse informed the exploration of passkeys, device choice and recovery.
Organise access around what the user needs
I rebuilt the individual flow around an email profile, passkey registration and entry to the dashboard. Identity verification then appeared in the context of the feature a person wanted to use.
Two access paths in ENTA
- Crypto-only access
- The proposed profile gives users access to stablecoin send, receive and swap without completing ENTA’s identity-verification upgrade first.
- Crypto and fiat access
- Fiat onramp, offramp, conversion and higher limits remain visible with locked states that explain the verification required to use them.
The dashboard needed to work before, during and after verification. Each locked action had to explain the value of the upgrade clearly enough for users to make an informed next move.
Account type and device choice shape the route
The flow map connects individual and business entry points with mobile and desktop passkey paths. It makes the device handoff, wallet creation and business-workspace setup visible as parts of the authentication journey.
From flow decisions to interface details
The one-week sprint called for early feedback on the flow. I used Claude Design to explore and refine prototypes, with Figma carrying the design and handoff work.
Two moments needed particular care: explaining a locked action before asking for verification, and helping users choose where to create their passkey. The first makes the next step relevant; the second connects sign-up with returning on another device.
Explore the onboarding and wallet prototypes
Switch between individual and business entry points and the wallet dashboards. These later prototype views show the wider ENTA experience alongside the individual onboarding work.
The demo uses mock data and simulated passkeys. Individual sign-up reaches email confirmation; the individual dashboard opens the separate Tier 2 prototype.
Handoff and product screens
The handoff brought the linked flows together in Figma for engineering. Copy review ran alongside design QA, with attention to the passkey setup moment and the dashboard’s verification states.
The selected screens below cover individual sign-up and wallet access, plus business account selection, passkey setup and verification. Open any screen to inspect it at full resolution.
What changed
The design brought the wallet earlier in the individual journey. Passkey-led authentication replaced the password-led structure, while the dashboard explained which actions were ready and which needed verification.
The earlier case study reports under one minute to the dashboard for crypto-only users, and under four minutes through KYC for crypto-and-fiat users. It does not document how those timings were established.
The useful shift was a clear path from an available action to an optional upgrade. Users could see the feature they were working towards, rather than completing setup without knowing what came next.
What I learned
Define the first useful moment
Completing every setup step is not the same as reaching value. Starting with the user’s first useful action makes it easier to decide which requirements belong upfront and which belong in the product.
Make the upgrade worth understanding
A locked feature is still part of the experience. Its label and explanation should help users understand the benefit and the work required to unlock it.
Design authentication beyond sign-up
The passkey decision extends into device changes, return visits and recovery. Those paths need to be considered together so a shorter first journey does not create confusion later.