Kenya NID

Overview

The Kenya National ID is the official identification document for citizens and residents, recorded in a central population register. Kenya NID lookup requires users to enter their NID number and we will return attributes associated with that number.

• ID: kenya-nid-lookup-2
• Type: eID (database)
• Verification Type: Enrichment
• Regions: Africa
• Countries: KE
• Adoption: 29,000,000
• URL: https://accounts.ecitizen.go.ke/en

Integration with Trinsic

Kenya NID verification is integrated into Trinsic's identity acceptance network allowing businesses to verify users against the government system of record in Kenya.

• Permission required: Yes, this method requires registration before you can activate it for your users. Please contact Trinsic to begin this process.
• Cost: Contact the Trinsic team.

User Flows

Trinsic supports three verification methods for Kenya NID:

1. Kenya NID: User provides their National ID number along with personal information (name, date of birth, gender, phone number). The system verifies that the provided information matches the government database records.

   • NOTE: Trinsic has two providers with this name. Each uses a different subprocessor. Contact the Trinsic team for details.
   • NOTE: Most fields return a simple "1.0" (exact match) or "0.0" (no match) for their match score. However, names and birth dates can also return "0.9" (data that is out of order, but mostly correct) and "0.5" (a partial match). Names are a partial match when their Levenshtein score is less than or equal to 2, dates are a partial match when a single part of the date (year, month or day) is off by one.

2. Kenya NID Lookup: User provides their National ID number. The system retrieves and returns full identity information from the government database.

3. Kenya NID Biometric: User provides their National ID number and completes a liveness check. The system verifies the ID number and matches the user's biometrics against the government database.

Direct Mode Bypass

In direct mode, customers can bypass form-fill steps by passing known identity data about the user when launching the integration.

How to Test

Make sure you are working within your "Test" environment. Then follow the steps for your method below:

Lookup

1. Add kenya-nid-lookup-2 to a verification profile in your "Test" environment.

2. Enter the following credentials:

   • National ID: 00000000

Match

1. Add kenya-nid-match-2 to a verification profile in your "Test" environment.

2. Enter the following credentials:

   • National ID: 00000000
   • Given Name: Joe
   • Middle Name: Doe
   • Family Name: Leo
   • Date of Birth: 09/20/2000
   • Phone Number (if shown): (empty)
     • NOTE: Phone Number is a no-op in Test Mode.

Biometric Match

1. Add kenya-nid-match-biometric-2 to a verification profile in your "Test" environment.
2. Enter the following credentials:
   • National ID: 00000004
3. Perform a liveness check using our Hosted UI.
   • NOTE: If in Direct Mode, include 8 selfies taken in quick succession of a well-lit, centered, authentic human face.
4. Take a test selfie using our Hosted UI. This is only relevant in Test Mode.
   • NOTE: If in Direct Mode, include this additional image. Must differ from the liveness selfies.

Direct API Requirements

📘

Direct is not a requirement.

You can integrate with this provider using the Widget or Hosted UI instead, with no additional integration requirements on your end.

What your integration must support in order to use this provider with the Direct Provider Sessions API.

• Supports Direct Provider Sessions: ✅
• Launch Method: None — No user-facing action is required to start the flow.
• Collection Method: PollResult — Results arrive asynchronously; poll with the resultsAccessKey returned at session creation.
• Requires Input: This provider requires input before verification can proceed.
• Trinsic-Hosted UI: A Trinsic-Hosted Fallback UI exists for this provider, which may be invoked to cover gaps in your integration's capabilities.

Outputs

ℹ️

Normalized Attributes

These attributes form part of our normalized model, a standardized set used across providers. Trinsic normalizes this for you and lets you know when a property is available for each provider.