CKYC Verification API
New
Search the central KYC records for an existing customer record and pull the stored KYC details. Someone who has completed KYC elsewhere then does not start from a blank form.
Overview
CKYC verification checks whether a customer already has a KYC record filed in India's central KYC records infrastructure. Where a record exists, you retrieve it instead of collecting the same documents a second time. The workflow has two halves. A search asks whether a record exists for the person you are onboarding and returns the identifier with the limited matching details you need to confirm it. A download retrieves the stored record itself, and that step needs the customer's authorization. What a retrieved record contains varies by data source and by record, because it reflects what the filing institution submitted and when. Treat it as a starting position to confirm with the customer.
- Category
- KYC Services
- Coverage
- Customer records already filed in India's central KYC records infrastructure
- Input
- A KYC identifier, or another permitted search input supported by the service contract
- Output
- Whether a record exists and, on authorized download, the stored KYC record
- Typical users
- Lending, insurance, wealth and broking, fintech
- Coverage note
- Only customers whose KYC has already been filed centrally have a record to find
The overview and the sections after the reference are the FinSour API catalog’s own record for this service, rendered unaltered.
Reference in progress
The request and response reference for this endpoint is not published yet.
Everything below this block is the live catalog record for this service, and it is accurate. The platform’s published API contract does not include this service yet, so there is no request or response detail to document. Rather than fill these sections with a plausible example, the page lists what is missing:
- Endpoint URL and method
- The host, path and HTTP verb for this service.
- Authentication
- How a request identifies itself, and where credentials come from.
- Request parameters
- Field names, types, which are required, and validation rules.
- Response schema
- The success body, field by field, with a real example.
- Error codes
- What each failure means and which are worth retrying.
- Rate limits
- Request ceilings, and what happens at the ceiling.
No sample payload, URL, response body, error code, rate limit or latency figure appears anywhere on this site unless it has been supplied and attributed. Each item in this list is removed only when its own detail arrives; none of them is held back to wait for the rest, and none is ever placed beside a guess in the meantime.
Use cases
- Lending and NBFC - reuse an existing KYC record at loan application
- Insurance - onboard a proposer without re-collecting KYC documents
- Wealth and broking - investor onboarding for an existing record holder
- Fintech and PSP - check for a record before starting a fresh KYC journey
- Housing finance - retrieve stored details for applicants and co-applicants
- Microfinance - branch onboarding with less repeated document handling
What this service does
Search and download in one integration
The search establishes whether a record exists and returns the identifier with the limited details you need to confirm the right person. The download retrieves the stored record. Both sit inside one onboarding journey.
The download needs the customer to authorize it
Retrieving a stored record is an authorized act. The download step can require the customer's authorization. That may take the form of a one-time password sent to the mobile number registered against the record, depending on the selected service contract.
Fewer documents collected twice
Where a record already exists, onboarding can move toward the decision. You avoid pausing to re-collect identity and address proofs the customer has already submitted to another institution.
A record to compare against what you are told
A retrieved record can carry identity and address details, a photograph, references to the documents used and the date it was last updated. The fields available differ by data source and by record. Compare it with what the customer states.
How a check runs
Check your eligibility
Start with Get API and tell us about your onboarding journey. Eligibility, supported search inputs and volumes depend on the selected service contract.
Put the search where the customer is
Place it where the result can still change what the flow asks for next: a branch application, a mobile journey or an operations dashboard.
Search, then confirm the match
Submit the search input your service contract supports. Check that the returned details describe the person you are onboarding before you go further.
Take authorization, then download
Ask the customer to authorize the retrieval, record that authorization, and download the stored record only once it is given.
Compare the record, then decide
Compare the retrieved details with what the customer has told you. Collect KYC directly where no record exists or the details no longer hold.
Questions
- What do I send to search for a CKYC record?
- A search input your flow has already collected, such as the KYC identifier the customer supplies, or another permitted input like PAN or a registered mobile number. Which inputs are supported depends on the selected service contract.
- What is the difference between a CKYC search and a CKYC download?
- A search tells you whether a record exists and returns the identifier with limited matching details for confirmation. An authorized download returns the stored KYC record. The fields available vary by data source and by record.
- Do I need consent to search and download a CKYC record?
- You need the customer's authorization: retrieving a stored record is an authorized act. Search and download only for a customer your business is onboarding or servicing, only for that purpose, and only with the authorization the workflow requires. That step can require the customer to authorize it, which may involve a one-time password sent to the registered mobile number.
- What if no CKYC record is found for my customer?
- Not every customer has a record, and a search can also return details that do not describe the person in front of you. Both outcomes need a defined next step in your flow, which is usually collecting KYC directly.
- How current is a downloaded CKYC record?
- A record reflects what the filing institution submitted and when. Addresses change, names are recorded differently and documents are replaced. Compare the retrieved details with what the customer states.
- How do I get access to CKYC search and download?
- Use Get API to start a conversation about the workflow you are building. Access depends on your organization's eligibility and on the selected service contract, along with the supported search inputs and volumes.
Catalog entry last updated .