Skip to content
Amani logo

Biometric 2FA

A second factor that cannot be phished.

SMS codes are the weakest link and the biggest bill. Amani replaces them with a face check bound to the identity you verified at onboarding - unphishable, uninterceptable, and free of per-message costs.

The challenge

OTP interception, SIM swaps and social-engineering defeat SMS-based two-factor authentication, while message costs scale relentlessly with your user base.

With Amani

  • Inherence-factor authentication with no shared secret
  • Immune to phishing, interception and SIM swap
  • Works on any device - not tied to one handset
  • SMS spend removed from authentication flows
  • Every attempt scored with device and liveness signals

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

Biometric 2FA - common questions

How does this differ from Face ID?

Device biometrics unlock a device. Amani proves the verified account owner is present, on any device, bound to your KYC identity.

What if the face check fails?

You configure fallback: retry, another factor, or a fresh document check for recovery.

Does it satisfy strong authentication rules?

It provides the inherence factor for SCA-style requirements and pairs with a possession factor to complete the pair.

Related use cases

Build this flow with Amani

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