KYC & OnboardingCKYC Platform
Get a Demo

Central KYC Registry integration

CKYCRR 2.0

Search, download, create and update KYC records on CERSAI’s registry through one API. We handle the tokens, signing, encryption and mutual TLS.

  1. Your appsBanks, NBFCs, insurers, brokers
  2. CKYC PlatformChecks access, validates, records
  3. Secure channelOAuth, JWS, JWE over mTLS
  4. CERSAI CKYCRRThe Central KYC Records Registry
Explore the platform See the API

CKYC Platform

Every CKYC service your onboarding needs.

One secure API for your systems, and a browser console for your team.

Get a Demo
CKYC console: Search records
CKYC console Search screen: search criteria by customer type, OVD type and number, name and date of birth, with the JSON API response and one matched record showing its CKYC reference
Search · Download · Create · Update

The full CKYCRR 2.0 API

Search by OVD, PAN, CKYC number or demographic details. Download with consent, create and update records, and fetch update notifications.

OAuth · JWS · JWE · mTLS

Security handled for you

The platform obtains the token, signs and encrypts each request, calls CKYCRR over mutual TLS, then decrypts and verifies the reply.

Per-client access

One platform, many clients

Each client gets its own API key, API permissions, IP allowlist and validity dates. Keys are stored only as hashes.

Transaction log · Billing

Every call accounted for

Each call is logged with its status, CKYCRR error code, response time and CERSAI request ID, ready for monthly billing. Customer data is never logged or stored.

Simulator mode

Test before the testbed

Switch on the simulator to run complete flows on sample registry responses. Nothing leaves the server, and simulated calls are never billed.

Settings, not code

Change without redeploying

Certificates, credentials and registry options live in settings and take effect within minutes, so testbed and live differences need no rebuild.

Search + Download

Download a KYC record, with the customer’s consent.

The platform takes each download through CKYCRR’s consent journey, one step at a time.

CKYC console: Search + Download
CKYC console Search and Download screen: progress chips for search, initiate and OTP consent marked done and verify OTP in progress, the download form with the CKYC reference filled in, and a notice that the OTP was sent to the registered masked email and mobile

How a download works

  1. Search

    Find the record by OVD, PAN, CKYC number or demographic details.

  2. Initiate

    Start the download with the CKYC reference from the search.

  3. Consent

    Capture consent by OTP, an uploaded consent form or face authentication.

  4. Verify

    Validate the OTP sent to the customer’s registered mobile and email, or resend it.

  5. Fetch

    Receive the complete KYC record as plain JSON.

When the registry already holds the customer’s consent, the platform skips straight from initiate to fetch.

Create + Update

Create and update records, then track them to approval.

  • CreateSubmit a new individual or legal-entity record and get an acknowledgement number.
  • TrackCheck the acknowledgement until CKYCRR issues the CKYC number.
  • ResolveAct on probable matches the registry flags during creation.
  • UpdateSend only the sections that changed on an existing record.
  • Stay currentFetch records updated after a date, page by page.
CKYC console: Create CKYC record
CKYC console Create screen: individual details form beside the JSON response showing an approved status and the generated CKYC number

Client API

Send plain JSON. Get plain JSON back.

Your systems never see an envelope, a certificate or a cipher. Just the registry’s fields, in and out.

RequestPOST /api/Search
apiKey: ••••••••••••••••
{
  "clientId": "NBFC0142",
  "txnId": "SRCH-20261016-0001",
  "ckycType": "INDIVIDUAL",
  "searchOption": "OVD",
  "data": {
    "ovdDetails": [{
      "ovdType": "C",
      "ovdNo": "ABCDE1234A",
      "fullName": "Ramesh Kumar",
      "dob": "01-01-2000",
      "gender": "M"
    }]
  }
}
ResponseSUCCESS
{
  "txnId": "SRCH-20261016-0001",
  "ecsTxnId": 1001,
  "txnType": "SEARCH",
  "status": "SUCCESS",
  "data": {
    "message": "Individual entity records found",
    "data": {
      "searchKey": "IOV26081953046445726",
      "results": [{
        "fullName": "Ramesh Kumar",
        "ckycRefNo": "INRGPK1234567",
        "status": "ACTIVE"
      }]
    }
  }
}

Your reference, every time

Each call carries your own txnId. Duplicates are rejected, so nothing is processed twice.

Errors you can act on

Validation errors name the field at fault. Registry failures return CKYCRR’s own code, unchanged.

One ID for support

Quote the ecsTxnId to us, and we can trace the call down to CERSAI’s request ID.

CKYC console: Sign in
CKYC console sign-in screen: a charcoal brand panel beside a form for username, password and an image CAPTCHA

Web console

A console for your team, not just your code.

  • Sign inUsername, password and an image CAPTCHA, checked on the server.
  • RunSearch, download, create and update from four simple screens.
  • ReviewSee and copy the raw JSON response for every step.
  • Stay safeYour API key stays on the server and is never sent to the browser.

Go live on CKYCRR 2.0 without building the plumbing.

We’ll walk you through search, consent-led download, create and update, end to end.

Get a Demo