Skip to content
Amani logo

Selfie-only re-auth

Log returning users in with a glance.

You already proved who they are. Selfie-only re-authentication matches a live face against the biometric enrolled at onboarding, turning login into a one-second glance - no password to forget, no code to intercept.

The challenge

Password resets drive support costs and abandonment, while OTP-based login adds delay and expense to every session.

With Amani

  • Passwordless login in about a second
  • Password-reset support volume reduced
  • Liveness on every attempt blocks photo attacks
  • Identity-bound, so a new phone is not a lockout
  • Session risk signals delivered with each login

The stack

Modules powering this flow.

Switch these on in Amani Studio - or call them directly from one API.

For developers

Build this flow.

Three API calls start the session; the modules above run inside it. Compose the journey in Amani Studio without code, or let your AI coding agent wire up the SDK from a single prompt.

  • JWT auth with refresh tokens
  • Regional base URLs (EU · TR · UAE)
  • HMAC-signed webhooks with retries
  • 27 languages in the SDKs

verify.sh

# 1 · Authenticate (server-side only)
curl -X POST 'https://ae.amani.ai/api/v2/user/login/' \
  --form 'username="you@company.com"' \
  --form 'password="••••••••"'

# 2 · Create the customer profile
curl -X POST 'https://ae.amani.ai/api/v2/profile' \
  -H 'Authorization: Bearer $ACCESS_TOKEN' \
  --form 'id_card_number="784199012345678"' \
  --form 'name="Layla Haddad"'

# 3 · Generate the verification URL
curl -X POST 'https://ae.amani.ai/api/v2/profile/url' \
  -H 'Authorization: Bearer $ACCESS_TOKEN' \
  -H 'Content-Type: application/json' \
  --data '{
    "profile": PROFILE_ID,
    "web_sdk_url": "https://verify.amani.ai",
    "language": "en",
    "return_url": "https://yourapp.com/verified"
  }'

# This session runs: Biometric Re-authentication, Liveness, Face Match 1:1.

Selfie-only re-auth - common questions

Do users need to enrol separately?

No - customers verified with Amani KYC are already enrolled from onboarding.

What if a user’s appearance changes?

Templates tolerate glasses, facial hair and ageing. Genuine failures fall back to your configured recovery path.

Can it work alongside passwords?

Yes - many teams run it as an optional fast path first and keep passwords as fallback during migration.

Related use cases

Build this flow with Amani

Compose it in Studio without code, or integrate the API in an afternoon.