We have an online store application that uses one-time passwords for user login. The user enters her email address, and we email her a one-time password to log in with.
She doesn't choose any password.
We have a feature that's like a store credit balance—users can easily and quickly make purchases using their balance, and add credit any time while logged in. (The reason our store credit exists is because of outdated payment solutions in our country.)
It's important for us that if someone’s device is stolen, the thief should not be able to use their store credit...
So we make the user choose a password first time they want to add store credit.
Because the user hasn't chosen a password to log in with, we’re worried she might be confused by a password only for store credit.
- Is there any better way to protect their store credit instead of using password?
- If not, how can I explain this mess (of choosing a password) to the user?