Skip to main content

​
Identity Verification

Verify BVN, NIN, and perform KYC checks
Reviewed but tenant-gated namespace. zentra_identity is part of the reviewed public route manifest, but detailed page coverage in this workspace is still being expanded and should be validated against your enabled environment.

​
Overview

Identity checks are reviewed for public exposure, but they remain tenant-gated. Your enabled contract depends on the providers, countries, and verification steps approved for your environment.
Use this namespace when you need regulated identity evidence such as BVN, NIN, selfie comparison, or an async verification status check. Confirm the exact routes, response fields, and fallback behavior enabled for your tenant before moving from sandbox to live.

​
What To Expect

  • Identity checks are policy-sensitive and may differ by tenant, geography, and rollout phase.
  • Request payloads should use stable business identifiers so retries and downstream reviews stay traceable.
  • Verification workflows can be synchronous or asynchronous depending on the provider path behind your tenant.
  • Treat identity responses as regulated data: store only the minimum fields you need and mask any user-facing operational views.

Verify BVN

Start a bank-verification lookup when BVN is enabled for your tenant.

Verify NIN

Review the national-id contract used for supported identity flows.

Verification Status

Check long-running or queued verification outcomes without guessing state.

Trust Review

Confirm enabled providers, live-readiness, and data-handling expectations.