Driver registration
Licensed, verified drivers - and no impostors.
A verified driver at sign-up means nothing if someone else drives the car. Amani validates the licence and identity at registration, then re-authenticates the driver biometrically at shift start - every time.
The challenge
Ride-hailing and delivery platforms face impersonation, rented accounts and expired licences - each a passenger-safety incident and a regulatory exposure waiting to happen.
With Amani
- Driving licences verified against document templates
- Driver identity bound biometrically at registration
- Shift-start face checks confirm the right driver
- Licence expiry tracked and re-verification triggered
- Banned drivers blocked from re-registering
The stack
Modules powering this flow.
Switch these on in Amani Studio - or call them directly from one API.
ID Verification
$0.15Verify any ID from 220+ countries in seconds.
ExploreKYC
$0.35Onboard real customers. Block fraud in seconds.
ExploreBiometric Re-authentication
$0.05Log users back in with a selfie.
ExploreFace Match 1:N
$0.10Find duplicates and watchlisted faces at scale.
ExploreLiveness
From $0.15Catch deepfakes, masks and screen replays.
ExploreFor 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: ID Verification, KYC, Biometric Re-authentication, Face Match 1:N, Liveness.with Amani Skills
# Install Amani Skills once
npx -y github:AMANI-AI-ORG/skills --global
# Then ask your coding agent:
You › Add the Amani KYC UI SDK to our Android onboarding right after sign-up, with ID document capture enabled.
# 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();
});Driver registration - common questions
Can you verify driving licences specifically?
Yes - licences from 220+ countries are supported, with expiry and consistency checks.
How often should drivers re-authenticate?
Most platforms check at shift start, with random spot checks during long sessions.
What if a driver fails the check?
You configure the response - retry, block the shift, or escalate to review with full evidence.
Related use cases
Build this flow with Amani
Compose it in Studio without code, or integrate the API in an afternoon.