Simplifying account aggragtor multi account select to 1 tap experience
Overview
The project focused on redesigning the account aggregator flow at Hyperverge. The goal was to do better than the industry avg consent rates that hover at 50%, every drop-off represents lost revenue for clients.
The challenge was amplified by a critical constraint: once deployed to our Technical Service provider's servers, changes would be locked in for 6-12 months minimum
Team
2 product managers
1 product designer
1 engineer
Duration
2 month
My role
Defining feature specs and end-to-end design and component creation
Before
The old flow did not support multiple bank accounts being selected at one go. We were to take this up to
The problem
Users were previously unable to select multiple bank accounts at a time before they were able to link their banks.
The new flow that we are proposing would enable users to link accounts from multiple banks at one go.
Constraints
Accounts from different banks would load at different times owing to varying server performances.
What this meant: Users would not be able to view all their accounts during the linking process
Each bank required their own individual OTP's
What this meant: Users would need to provide multiple OTP's in case of linking accounts from more than 1 bank
❌ Approach 1 - Slide to link
Using slide to link to make the activity of linking more intentional and making the experience more in line with other apps in the market.
Pros
Intentional for users to link a bank
Cons
Too many CTA's on the screen
❌ Approach 2 - Secondary CTA's + Loading Button
Secondary CTAs on unliked accounts, and once all accounts are loaded, users can proceed to sharing consent
Pros
Notified users with great prominence more accounts were loaded
Cons
No clear primary action on the screen
❌ Approach 3
To solve the multiple OTP problem we combined the linking flow across all account into a single action
Pros
Users could easily multi select accounts and verify account in a single go
Cons
No clear primary action as CTA's for linking and proceeding were seperate
Final Solution
We unified the primary CTA making a single primary action available this greatly simplified the linking flow.
