SprintCheck

Client SDKs

How the SDKs work

The client SDKs run a liveness-checked capture flow inside your app and report the result to your callback and your webhook. Here is the full lifecycle.

  1. 1

    Initialize the SDK

    Add the SprintCheck SDK to your app and initialize it once with your API key and encryption key. The SDK signs and calls the verification API for you — your keys never sit in request code you write.

    Android · Flutter · React Native · Expo

  2. 2

    Launch a verification

    Call the SDK's start-verification method with a type — BVN, NIN or facial — and the customer's identifier. The SDK opens its own screen and takes over the flow.

    type: bvn · nin · facial

  3. 3

    The SDK captures and verifies

    The customer completes document input and a liveness-checked selfie in-app. The SDK matches the face against the document photo and returns the outcome to your callback with a confidence score.

    In-app capture · liveness · face match

  4. 4

    Receive the result

    The same outcome is also posted to your webhook as a verification event (source: SDK), and appears in your verification history and dashboard immediately.

    Webhook · event: verification

The confidence value on completed checks is the face-match score (0–100). Most teams accept at 75 and above, and route lower scores to manual review.

Where to next

Install the SDK for your platform — Android, Flutter, React Native or Expo — then wire up webhooks to receive the result on your server. Prefer server-to-server? Call Verify BVN and the other identity endpoints directly.