You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Coming from here, we want to prompt a user who has been issued a virtual Expensify Card to fill out their personal details before accessing the virtual card details the first time in NewDot (if they're not already on file). We don't do this now. If their personal info isn't on file, we fall back to using the business's info with the virtual card. This causes confusion at the point of sale and leads to transaction declines.
Details
We already do this with physical cards. When a user's issued a physical card and has no personal details on file, we:
Prompt them to complete the personal details when they try to order the card on Wallet OR via the prompt in the workspace chat.
Show a time-sensitive home task that leads to a wallet to do this.
Going forward, if a user's issued a virtual Expensify Card and has no or incomplete personal details, let's:
Prompt the user to complete personal details when they try to access the virtual card details for the first time on Wallet.
Show a time-sensitive home task that leads to the wallet to do this.
The virtual card flow on wallet would start with the user tapping Reveal details OR the new Add details button on Wallet OR the new time-sensitive home task. We'd then:
Prompt for the personal details steps, including:
Name.
DOB.
Address.
Phone number.
Show a confirmation page, same as with the existing physical card flow now.
User lands with virtual card details revealed after authenticating.
We call Marqeta's API to update the user's personal details with their user profile, so they're on file with their cards (we may get this for free).
This analogous flow for physical cards with ECUK involves setting a PIN. That will not be applicable for ECUK here because virtual cards do not have PINs.
We'd remove the home task and Add details row on Wallet after the user does this the first time.
We'd only ever show this max once. On future authentication attempts, it's not needed. Nor is it needed if the user is issued future virtual cards OR if their complete personal details are already on file when they try to view card details the first time.
I envision that we'd use this pattern for both US and UK/EU Expensify Cards.
Coming from here, we want to prompt a user who has been issued a virtual Expensify Card to fill out their personal details before accessing the virtual card details the first time in NewDot (if they're not already on file). We don't do this now. If their personal info isn't on file, we fall back to using the business's info with the virtual card. This causes confusion at the point of sale and leads to transaction declines.
Details
Reveal detailsOR the newAdd detailsbutton onWalletOR the new time-sensitive home task. We'd then:Add detailsrow onWalletafter the user does this the first time.Home task
Wallet flow