Biometrics Available
Atlas Return
Re-authenticate returning customers with a selfie matched to their reference faces.
Access by invitation: no account yet? Ask for your sandbox workspace.
What it checks
Your customer is back: one selfie is enough.
Atlas Return compares a new selfie with your customer's reference faces, without asking for their document again.
-
Reference faces
Up to five faces per customer, from their approved verifications or added through the API.
-
Selfie comparison
The new selfie is compared with the reference faces, with a score.
-
Liveness detection
The same checks as Atlas Live: replayed screen, printed photo, reused portrait.
-
Customer status
A flagged customer goes to review, a blocked customer is rejected.
-
History
Each re-authentication joins the customer's history in the console.
-
Deletion on request
A customer and their faces can be deleted through the API, to answer erasure requests.
How it works
For the moments that matter.
- 1 A sensitive action Sign-in from a new device, a transfer, a change of contact details.
- 2 A selfie The customer takes a photo; liveness is checked.
- 3 A comparison Above the threshold, the action is allowed; otherwise, it is blocked or reviewed.
Re-authenticationSample data
Reference faces
New selfie
Match scoreYour threshold
- Liveness passed
- Customer status active
- Compared with 3 faces
Action Allowed
For developers
Add a reference face.
Up to five faces per customer; each one can be viewed and deleted through the API.
Request
curl -X POST https://verify.atlasidv.com/v1/users/by-id/c81d…/faces \
-H "Authorization: Bearer atlas_sk_sandbox_…" \
-d '{ "image": "/9j/4AAQSkZJRg…" }' Response 201 Created
{
"id": "f02b…",
"created_at": "2026-10-03T09:41:12Z"
} Take the next step
Try Atlas Return on your own flows.
A demo on your real cases, then a sandbox space with synthetic identities to integrate without any real data.