Skip to main content
๐Ÿชช

Individual KYC

Verify individuals before onboarding using government-backed registries and biometrics. Run NIN lookups against the NIMC registry, complete BVN Identity or BVN Accounts verification via the NIBSS iGree consent flow, or compare facial images with a liveness check.

๐Ÿชช NIN โ€” NIMC registry๐Ÿ“„ BVN Identity๐Ÿฆ BVN Accounts๐Ÿคณ Face biometrics

Verification Methodsโ€‹

๐Ÿชช
NIN Verification
POST ยท Single step
Cross-checks a National Identification Number against the NIMC registry. Supply the customer's personal details and receive per-field match results.
  • Returns match / partial_match / no_match per field
  • Single API call โ€” no multi-step flow
๐Ÿ“„
BVN Identity
3-step ยท NIBSS iGree
Verifies a customer's core demographic identity via the NIBSS iGree Consent Layer. OTP delivery is handled entirely by NIBSS.
  • Step 1 โ€” Get Auth Methods: initiate flow, receive requestId
  • Step 2 โ€” Verify Auth Method: select OTP channel
  • Step 3 โ€” Fetch BVN Identity: submit OTP, receive profile + face image
๐Ÿฆ
BVN Accounts
3-step ยท NIBSS iGree
Retrieves all bank accounts tied to a customer's BVN via the NIBSS iGree Consent Layer. OTP delivery is handled entirely by NIBSS.
  • Step 1 โ€” Get Auth Methods: initiate flow, receive requestId
  • Step 2 โ€” Verify Auth Method: select OTP channel
  • Step 3 โ€” Fetch BVN Accounts: submit OTP, receive profile + linked accounts
๐Ÿคณ
Face Verification
POST ยท multipart/form-data
Compares two facial images and returns a similarity score, image quality rating, and passive liveness check result.
  • referenceImage โ€” face from BVN record (data.face_image)
  • comparisonImage โ€” live capture at onboarding
  • Accepts multipart/form-data, not JSON
Bearer token required on all endpoints

Every endpoint in this section requires a valid Bearer token. Obtain one from the Access Token endpoint and pass it as Authorization: Bearer <token>.