Card-Only User Permission
2021
Role
Lead product designer
Team
David Cain – Lead front end eng
Sebastien Windal – Lead iOS eng
Context
There are 3 types of roles users can be within the Mercury ecosystem: admin, custom user, and bookkeeper. For a while, we’ve had admins send in a feature request to assign cards to users without giving them full access to their bank’s status and details.
We decided to create the card-only user permission, which would allow the user to freely use their debit cards (within limits), access their dashboard, and check their transactions.
Admin adds a new card-only user from the “teams” page
When a new card-only user is assigned, the admin must set a daily spending limit and a daily ATM limit along with the source checking account. The invitee will be able to choose between a virtual or physical card as their first debit card, and if another is required, then the admin can issue new cards in the future.
COU chooses their first card during account onboarding
We give the COU the ability to choose between a virtual and a physical card. The virtual card gets issued immediately whereas the physical card will take 1-2 weeks to arrive.
If the user requires both physical and virtual card, then the admin can issue a new card after the COU finishes their account setup.
Dashboard view
The COU dashboard experience is limited to the user’s first debit card details, spending stats, and list of most recent transactions. The user can also view all their transactions from the left panel tab.
Multiple cards view
If a COU is issued multiple debit cards, a “Your Cards” column view will appear in the dashboard where the user can easily switch between cards. Users can also access canceled cards, which will be collapsed in a dropdown to reduce real estate and easily view active cards.
COU experience on iOS
Stats (30 days post roll out)
488 orgs
with active COU in their teams
823
COUs
$300K
Rolling 30 day spend by COUs
2X
virtual cards (than physical cards) created weekly for COUs