PSD3 SCA
Strong Customer Authentication, without the OTP tax.
SCA requires two independent factors. Amani supplies the inherence factor as a liveness-checked face match bound to the verified identity - stronger than an SMS code, faster for the customer, and free of per-message cost.
The challenge
OTP-based SCA is phishable, expensive at scale and a major source of payment abandonment - yet the regulatory requirement is not going away.
With Amani
- Compliant inherence factor for SCA
- Phishing- and SIM-swap-resistant by design
- Payment abandonment reduced versus OTP flows
- SMS costs removed from authentication
- Exemption logic supported through risk scoring
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, Biometric Re-authentication, Liveness, 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();
});PSD3 SCA - common questions
Which SCA factor does Amani provide?
Inherence - something you are. Pair it with your possession or knowledge factor to complete the requirement.
Does it support transaction risk analysis exemptions?
Yes - your own risk engine decides when an exemption applies, and calls Amani for the biometric factor only when it does not.
Is it accepted across the EU?
Biometric inherence factors are explicitly recognised under the SCA framework; we help you document the implementation for your regulator.
Related use cases
Build this flow with Amani
Compose it in Studio without code, or integrate the API in an afternoon.