High-risk transactions
Step up verification when the stakes rise.
Not every transaction deserves the same scrutiny. Amani applies step-up verification exactly where risk concentrates - large transfers, new payees, unusual patterns - with a biometric check that takes a second and stops a fraud that would take months to unwind.
The challenge
Blanket friction drives customers away, while blanket trust invites losses. Most platforms lack a way to raise assurance dynamically at the point of risk.
With Amani
- Risk-triggered biometric step-up on sensitive actions
- Triggered by your own rules: amount, new payee or device change
- Device and IP risk signals on every step-up
- Low-risk activity stays completely frictionless
- Every decision documented for audit
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, Device & IP Analysis, Liveness, AML / Sanctions Screening.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();
});High-risk transactions - common questions
What triggers a step-up?
Your own payment system decides - amount thresholds, new beneficiaries, device changes - and calls Amani for the biometric check when a rule fires.
Can it block a payment in real time?
Yes - the face check returns in about a second, so your payment flow can hold or decline the transaction when it fails.
How much friction does it add?
A face check takes roughly a second, and only fires on the transactions you flag as high risk.
Related use cases
Build this flow with Amani
Compose it in Studio without code, or integrate the API in an afternoon.