Skip to main content
DEVELOPER KYC API

KYC verification API for document-led customer onboarding.

Create live-only API credentials, choose the required documents and identity fields, and let applicants complete a hosted verification flow. Your backend receives a reference and signed status events rather than unnecessary identity media.

Capabilities built around the actual customer journey.

Implementation and testing status is stated separately from commercial activation, so your team can evaluate what is genuinely available.

Hosted KYC orchestration

Guide applicants through consent, document capture, reviewed fields and the required selfie step without building every screen yourself.

Reusable identity with fresh liveness

Merchant-controlled applicant reuse can use eligible saved documents with consent. A fresh selfie and liveness result remains mandatory and is never bypassed.

English and Urdu OCR assistance

The local non-generative OCR path can return original-script text, confidence and source references for manual correction. It does not automatically approve an identity document.

Scoped API and webhooks

Live-only credentials, project-level configuration, explicit webhook events and signed delivery help your application consume only authorized results.

Where this can be used.

  • Customer account opening
  • Marketplace seller onboarding
  • Financial-platform KYC
  • Repeat verification with applicant consent
  • Developer-led identity integrations

A controlled implementation path.

  1. 1Create a Developer project and live-only API key
  2. 2Configure document, identity-reuse and webhook settings
  3. 3Create a hosted verification link from your backend
  4. 4Handle the returned reference and signed result events
  5. 5Complete provider, security and billing acceptance before charging customers

Current availability and acceptance limits

OCR and document storage have isolated integration evidence. General real-provider liveness is not commercially accepted; the active liveness configuration is sandbox-pilot only. Do not treat a stored document or OCR result as an approved verification.

Frequently asked questions

Does the KYC API issue Sandbox API keys?

No new Sandbox API keys are issued. New credentials are live-only. Hosted Sandbox verification links are available within the eligible monthly test-case limit.

Can an applicant reuse a previous document?

Only when the merchant enables reusable identity, the applicant consents and the document is eligible. Fresh selfie/liveness is still required, and disabled reuse does not request an email for that purpose.

Does OCR approval mean KYC approval?

No. OCR only assists extraction. Low-confidence or incomplete fields require correction and review, and the final verification status remains separate.

Evaluate the exact workflow before you go live.

Review the documentation, test the actual document and provider path, or ask our integration team for a scoped technical assessment.