Stop account takeovers
Stop account takeover before the money moves.
Stolen credentials are cheap and OTPs are phishable. Amani re-verifies the actual human at the moments that matter - login, payout, payee change - with a liveness-checked face match bound to the identity you onboarded.
The challenge
Passwords leak, SMS codes get intercepted and SIM swaps hand attackers the second factor. By the time an unusual transaction is flagged, the funds have already left.
With Amani
- Phishing-resistant biometric authentication on high-risk actions
- Device and IP signals detect session anomalies in real time
- SIM-swap detection before OTPs are trusted
- Step-up rules by amount, payee or risk score
- Attack attempts logged with full forensic detail
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, Phone Verification.with Amani Skills
# Install Amani Skills once
npx -y github:AMANI-AI-ORG/skills --global
# Then ask your coding agent:
You › Before a high-value withdrawal, add an Amani BioMatch face check on iOS to confirm the account owner.
# The matching skill fetches the live docs, pins the
# current SDK version and wires up the integration -
# secrets left as placeholders. Claude Code, Cursor and
# any Agent-Skills-compatible tool.webhooks.ts
// Amani signs every webhook with an HMAC signature using
// your secret. Always verify it before processing.
import crypto from 'node:crypto';
app.post('/webhooks/amani', (req, res) => {
// Confirm the exact header name in the Webhooks API reference.
const signature = req.get('X-Amani-Signature') ?? '';
const expected = crypto
.createHmac('sha256', process.env.AMANI_WEBHOOK_SECRET)
.update(req.rawBody)
.digest('hex');
const valid =
signature.length === expected.length &&
crypto.timingSafeEqual(Buffer.from(signature), Buffer.from(expected));
if (!valid) return res.status(401).end();
const { profile, status } = req.body;
if (status === 'approved') activateAccount(profile);
res.status(200).end();
});Stop account takeovers - common questions
When should we step up to a face check?
Common triggers are login from a new device, payout above a threshold, new payee creation and password or contact-detail changes.
Does this add friction for genuine users?
A face check takes about a second and only fires on the actions you choose - most sessions never see it.
What if the attacker has the user’s photo?
Passive liveness rejects photos, screens, masks and deepfakes, so a stolen image cannot authenticate.
Related use cases
Build this flow with Amani
Compose it in Studio without code, or integrate the API in an afternoon.