Skip to content
Amani logo

Password recovery

Recover accounts without opening a back door.

Account recovery is where attackers walk in. Amani replaces email links and security questions with biometric proof: match the live face to the enrolled identity, and only the real owner gets back in.

The challenge

Recovery flows are the softest target in most products - knowledge questions are guessable, email accounts are compromised, and manual support recovery is exploited by social engineering.

With Amani

  • Biometric proof of the original verified owner
  • Social-engineering path to support agents closed
  • Self-service recovery reduces ticket volume
  • Liveness blocks photo and deepfake attempts
  • Full audit trail of every recovery attempt

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, KYC, Device & IP Analysis.

Password recovery - common questions

What if the user was never biometrically enrolled?

Recovery falls back to a fresh KYC check against the identity on file - a full document and face verification.

Can support staff still override?

You decide. Most teams disable manual override entirely or gate it behind four-eyes approval in Studio.

How quickly can a user recover?

Self-service biometric recovery typically completes in under a minute, with no queue.

Related use cases

Build this flow with Amani

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