Truztcube Docs

ID Verification

Verify a NIN or BVN against the source register and return the holder's record — with all the NIN lookup modes and BVN tiers Truztcube supports.

ID verification confirms a government identity number and returns the holder's record from the source register. Truztcube supports NIN (via NIMC) and BVN (via the banking register).

NIN verification

Several lookup modes, each a POST under /v1/nin:

ModeEndpointBody
Raw lookup/v1/nin/raw/lookupnin, requestReason, enterpriseId
ShareCode/v1/nin/sharecode/lookupshareCode (required), requestReason, enterpriseId
Phone → NIN/v1/nin/phone/lookupphone number + reason
Face match/v1/nin/face-match/lookupnin, enterpriseId, requestReason, selfieImage, livelinessImages — see Biometrics
curl -X POST https://api.truztcube.com/v1/nin/raw/lookup \
  -H "x-api-key: sk_test_your_key" \
  -H "Content-Type: application/json" \
  -d '{ "nin": "00000000000", "requestReason": "KYC" }'

requestReason records the lawful purpose of the check. Fetch the permitted values from GET /v1/nin/request-reasons.

BVN verification

BVN comes in tiers, each a POST under /v1/bvn. All accept a consent assertion (consentGranted, consentReference) since the data subject must consent to a BVN check.

TierEndpointReturns
Basic/v1/bvn/basicCore record for the BVN
Advance/v1/bvn/advanceFuller record
Face validation/v1/bvn/face-validationRecord + face match (image)
curl -X POST https://api.truztcube.com/v1/bvn/basic \
  -H "x-api-key: sk_test_your_key" \
  -H "Content-Type: application/json" \
  -d '{
    "number": "00000000000",
    "consentGranted": true,
    "consentReference": "your-consent-ref"
  }'

Consent

You assert consent per request; Truztcube records the assertion. Ensure you hold a valid lawful basis for every BVN check — see Security.

Response

Every ID verification returns the standard envelope: a status, a Truztcube verification ID, and the verified fields your access level permits. Empty register fields are omitted rather than null-filled. Exact per-endpoint schemas are in the API Reference.

Access levels & pricing

The fields returned and the per-verification cost depend on your access level. See Pricing.

On this page