Use cases / Returning-user authentication
Biometric re-authentication for returning users
Confirm it is the same person before a big withdrawal, a password reset or a new device.
Biometric authenticationLivenessFace matchDevice and IP analysisEmail and phone codes
The problem
Account takeover usually happens after onboarding: a stolen password, a SIM swap, a new device. Passwords and SMS codes alone do not prove the original customer is present.
What ScreenKaptain checks
- A live selfie matched against the face from the customer's approved verification
- Liveness to stop photos and replays
- Device and IP signals such as Tor, VPN and data-centre addresses
- Email and phone one-time codes for step-up
- Every attempt logged against the customer
How it runs
Trigger the check
Create an authentication session for the customer at the risky moment.
Customer takes a selfie
It takes a few seconds in your app or browser.
Allow or stop
Get a match score and decision by webhook.
Start from this workflow
Create it with one API call, or open it in the visual builder and change any step.
curl -X POST https://your-domain/v3/workflows/ \ -H "x-api-key: sk_test_…" \ -H "Content-Type: application/json" \ -d '{"workflow_label":"Returning-user authentication","features":[{"feature":"LIVENESS"},{"feature":"FACE_MATCH"},{"feature":"IP_ANALYSIS"}]}'
Add a biometric step to your riskiest moments.
$10 of free credit every month. No card, no sales call.