Biometric Authentication
Face-match a live capture against the identity on record — via NIN face-match or BVN face-validation — for step-up identity assurance.
Biometric authentication adds a face match on top of an ID lookup: you capture the person's face and Truztcube matches it against the photo held on their identity record — higher assurance that the person presenting the ID is its true holder.
When to use it
- High-value onboarding or transactions where an ID-number match alone isn't enough.
- Step-up verification when a risk signal fires.
NIN face match
POST /v1/nin/face-match/lookup — match a selfie against the NIN's record.
Body: nin, enterpriseId, requestReason, selfieImage, and livelinessImages (all required),
with optional provisionalId / provisionalIdName.
curl -X POST https://api.truztcube.com/v1/nin/face-match/lookup \
-H "x-api-key: sk_test_your_key" \
-H "Content-Type: application/json" \
-d '{
"nin": "00000000000",
"enterpriseId": "your-enterprise-id",
"requestReason": "KYC",
"selfieImage": "<base64>",
"livelinessImages": ["<base64>", "<base64>"]
}'BVN face validation
POST /v1/bvn/face-validation — validate a face against the BVN record.
Body: number, image, consentGranted, consentReference.
curl -X POST https://api.truztcube.com/v1/bvn/face-validation \
-H "x-api-key: sk_test_your_key" \
-H "Content-Type: application/json" \
-d '{
"number": "00000000000",
"image": "<base64>",
"consentGranted": true,
"consentReference": "your-consent-ref"
}'Response
The response includes the match outcome, a Truztcube verification ID, and the verified record your access level permits.
Biometric data is sensitive
Face images are sensitive personal data. Truztcube passes them through where entitled and does not persist them — see Security.
Related
- ID Verification — the identity lookups these build on.
- API Reference — exact request/response schemas.