Block multi-account abuse
One person. One account. Every time.
Bonus abusers, banned users and fraud rings all rely on signing up again. Amani searches every new face against your entire user base and links devices and networks - so the same person cannot quietly become ten customers.
The challenge
Email addresses, phone numbers and even documents can be swapped. Without a biometric identity check, the same individual can farm promotions, evade bans and run coordinated fraud indefinitely.
With Amani
- Every new face searched against your enrolled base
- Previously banned users flagged the moment they return
- Device fingerprint links accounts across reinstalls
- Fraud rings clustered by shared signals
- Promotion and referral abuse cut at the source
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: Face Match 1:N, Device & IP Analysis, Liveness, Email Verification.with Amani Skills
# Install Amani Skills once
npx -y github:AMANI-AI-ORG/skills --global
# Then ask your coding agent:
You › On signup, run an Amani face search against our existing users to block duplicate accounts.
# 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();
});Block multi-account abuse - common questions
How fast is the duplicate search?
Vector search across millions of enrolled faces returns candidates in milliseconds, inline with onboarding.
Is storing faces compliant?
Faces are stored as irreversible templates with consent capture, retention limits and deletion APIs to support GDPR-class obligations.
What about genuine duplicate sign-ups?
Candidate matches can auto-block or route to review with images side-by-side, so legitimate cases are resolved quickly.
Related use cases
Build this flow with Amani
Compose it in Studio without code, or integrate the API in an afternoon.