CERSAIIdentity & KYCReady to ship

Central KYC (CKYC) API Integration

Search and download a citizen's KYC record from the Central KYC Registry using the 14-digit CKYC identifier.

Provider
CERSAI
Version
v1.1
Uptime
99.9%
Latency
360 ms
Access
Licensed
CKYCRDownload

What Central KYC (CKYC) API integration does

The Central KYC Registry, operated by CERSAI, holds KYC records that have already been collected and verified by a regulated entity. If a customer has been onboarded anywhere in the Indian financial system, a record almost certainly exists — and retrieving it is far better for everyone than collecting the same documents a second time.

CKYC integration lets you search for and download a customer's KYC record using their 14-digit CKYC identifier. The record arrives verified by the institution that originally collected it, which means a customer who already banks somewhere can be onboarded to your product without repeating a process they have completed before. In practice this is the single largest available reduction in onboarding drop-off for regulated products, because the step it removes is the one customers abandon at.

What teams build with it

Skip repeat KYC

Pull an existing record instead of collecting documents afresh for a customer already known to the financial system.

Periodic re-KYC

Refresh a customer file at review time from the registry rather than initiating a new collection cycle.

Cross-product onboarding

Onboard an existing customer to a second product — a loan, a policy, a demat account — using their established record.

Record reconciliation

Compare your held record against the registry to detect stale addresses and outdated documents across your book.

Endpoints included

  • POST/ckyc/v1/download
    Returns the stored KYC profile for a CKYC ID with consent.

Try it in the sandbox

Returns the stored KYC profile for a CKYC ID with consent.
POSThttps://sandbox.aeologic.io/ckyc/v1/download
Requestapplication/json
{
  "ckyc_id": "5012-3456-7890-12",
  "id_proof": "PAN",
  "consent": "Y"
}
Response
Run the sample to see a live response
Returns masked / synthetic data in Sandbox

What you need before we start

  • The customer's 14-digit CKYC identifier, or a search path to resolve it
  • Regulated-entity status appropriate to accessing the registry, confirmed during scoping
  • Customer consent for the retrieval, recorded in your flow

How we deliver it

  1. Scoping of your access position with respect to CERSAI
  2. Sandbox integration with synthetic KYC records
  3. Search and download flows wired into your onboarding journey with fallback to fresh KYC
  4. Production rollout with audit logging of every retrieval

Solution bundles that use it

Central KYC (CKYC) API integration — FAQs

What if the customer has no CKYC record?

The API returns a not-found result and your flow falls back to fresh KYC — normally Aadhaar e-KYC or DigiLocker. A well-designed journey attempts CKYC first precisely because the fallback is cheap.

Is the downloaded record legally sufficient?

The CKYC record is the KYC artefact the framework was created to make portable. Whether it is sufficient on its own for a given product depends on your regulator's requirements for that product, which we scope with you.

How current is the data?

It reflects what the originating institution deposited and has since updated. Comparing it against your own record is how firms find stale addresses at scale.

Ship Central KYC (CKYC) in days

Tell us your stack and we'll wire up Central KYC (CKYC) API integration for your team.

Talk to Aeologic