Start here

Set up your IKYC project.

Use the Dashboard to create a project, define its verification flow, test it in a controlled environment, and monitor its results.

1. Create an organisation, then create a project within it.
2. Open Flow, configure the checks and native mobile consent policy that apply to the project, then save the flow.
3. Create sandbox keys in API Keys and use Verify Now for controlled testing before integration.
4. Live keys and live verification require an approved organisation. Use the approved project only when you are ready for live checks.

Configure the flow

Organisation admins add a check to enable it; remove it or switch it off in its settings to disable it. They can configure each enabled check, including whether it is mandatory, available check tiers, Phone / NIN Match hard-gate behavior, liveness and face-match confidence thresholds, and an advisory confidence score. Admins also configure the native mobile consent policy that applicants must see before a Flutter verification begins.

A mandatory check failure cannot be changed through manual review. Review the flow with the stakeholders who own your verification policy before using it in live verification.

Use the project tabs

Flow

Configure the project's checks and native mobile consent.

Verify Now

Run the project's verification flow or create a verification link without first installing an SDK.

Integration

Configure browser integration settings and find the next steps for implementation.

API Keys

Create project keys for the appropriate environment and keep secret keys on your application server.

Webhooks

Optionally configure signed completion events for your backend.

Members

Manage which organisation members can access the project.

Verifications

Review verification history and check outcomes. Only organisation admins can resolve an eligible needs_review result: enter a 10–500 character reason, choose approve or reject, and confirm the final decision. The decision is audit logged and cannot override mandatory failures.

Logs

Inspect SDK-reported client and provider diagnostics. These records do not block a verification and are not analytics.

Usage

View aggregate total and daily verification counts, verdict breakdowns, and check counts.

Consent Records and Compliance

These project tabs are available to organisation admins only.

Continue to integration

For browser verification, use the public browser key from Integration, set exact allowed origins, and configure your brand name, primary color, logo URL, and privacy URL. Production origins must use HTTPS. Secret keys stay on your application server; use webhooks or status lookup only when your backend needs confirmation. Webhook endpoints must use HTTPS, and their signing secrets are write-only.

Follow the SDK-specific guide for implementation details rather than duplicating client setup in the Dashboard.