[OK] mounted /solutions/user-verification · use=verification
USER VERIFICATION
device familiarity for step-up workflows
Problem
Passwords, one-time codes, and sessions do not always tell you whether the current device looks familiar for this account or action. That matters during recovery, payout, admin changes, and other high-risk workflows.
How fingerprint.dev helps
enroll
Store visitor_id with a successful account event.
check
Call /identify during a sensitive action.
step up
Use confidence and account history to decide whether to allow, verify, or review.
Common workflows
- Account recovery from an unfamiliar device.
- Password reset followed by a high-risk change.
- New payout destination or billing change.
- Admin action from a device not seen before on that account.
Decision model
Fingerprint.dev does not authenticate users. It gives your verification system another piece of evidence so you can reserve friction for the moments that need it.
read quickstart implementation guide