Biometric payments
Pay with a face. Nothing to steal.
Cards get cloned, passwords get phished, OTPs get intercepted. FacePay authorises payments with a live face check bound to the identity you verified - nothing to steal, nothing to forward, nothing to guess.
The challenge
Every credential-based payment method can be stolen and replayed, while each additional authentication step costs conversion at exactly the wrong moment.
With Amani
- Payments authorised by a liveness-checked face
- Credential theft and replay rendered useless
- Strong Customer Authentication inherence factor satisfied
- Step-up only above your risk thresholds
- Enrolment inherited from KYC onboarding
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: FacePay, Liveness, Biometric Re-authentication, Device & IP Analysis.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();
});Biometric payments - common questions
Do users need to enrol separately?
No - customers verified with Amani KYC are enrolled automatically.
How fast is a FacePay authentication?
About a second, inside your app - no redirect and no waiting for a code.
What if the face check fails?
You configure fallback: retry, step up to another factor, or route to review. Every attempt is scored and logged.
Related use cases
Build this flow with Amani
Compose it in Studio without code, or integrate the API in an afternoon.