Frequently Asked Question

A)   About CKYC

Central KYC Registry is a centralized repository of KYC records of customers in the financial sector with uniform KYC norms and inter-usability of the KYC records across the sector with an objective to reduce the burden of producing KYC documents and getting those verified every time when the customer creates a new relationship with a financial entity.

Central KYC Registry has the below salient features:

  1. Facilitates uniformity & inter-usability of KYC records & process across the financial sector.
  2. Unique KYC identifier linked with independent ID proofs.
  3. Substantial cost reduction by avoiding multiplicity of registration and data upkeep.
  4. KYC data and documents stored in a digitally secure electronic format.
  5. Facilitates KYC Search, Upload, Download, Update.
  6. Secure and advanced user authentication mechanisms for system access.
  7. Data de-duplication to ensure single KYC identifier per applicant.
  8. Real time notification to institutions on updation in KYC details.
  9. Seamless file exchange processes without the need for manual intervention.
  10. API’s for search and download allow for real time account opening for CKYC compliant customers.

Central KYC application can be accessed by authorised institutions or other notified institutions under the Prevention of Money Laundering Act or rules framed by the Government of India or any Regulator (RBI, SEBI, IRDA, and PFRDA) there under.

The PMLA states as per rule (9) (I) (1):

(1A) ″Subject to the provisions of sub-rule (1) of the Prevention of Money-laundering Act, 2002 every reporting entity shall within three days after the commencement of an account-based relationship with a client, file the electronic copy of the client´s KYC records with the Central KYC Records Registry.″

(1C) Where a client submits a KYC Identifier to a reporting entity, then such reporting entity shall retrieve the KYC records online from the Central KYC Records Registry by using the KYC Identifier and shall not require a client to submit the same KYC records or information or any other additional identification documents or details

(1D) A reporting entity after obtaining additional or updated information from a client under subrule (1C), shall as soon as possible furnish the updated information to the Central KYC Records Registry which shall update the existing KYC records of the client and the Central KYC Records Registry shall thereafter inform electronically all reporting entities who have dealt with the concerned client regarding updatation of KYC record of the said client.

B)   Reporting Entity Registration

  • Financial Institutions (FI) have to register at Training video is available at detailing every step.
  • Upon submission of the details online, the system will generate a reference number and the same will be communicated to the nodal officer via email. This reference number has to be quoted on all communications henceforth.
  • FIs would have to register themselves on the test environment and test the application. Admin 1 & 2 shall receive testbed login credentials within 24 working hours for testing purpose.
  • Login to CKYC Testbed account. This is a mock environment. You may test each and every screen. It is mandatory to test Upload, download, search and update functions of CKYCR. Submit the checklist available under the Administration Tab thus confirming testing is complete.
  • CKYC Team shall verify if sufficient testing is performed – minimum requirement has been published on the website . An approval/rejection mail shall be sent to the nodal officer’s email id.
  • FI shall send the duly signed pre-filled FI registration form, supporting documents and testing completion sign off approval mail from CKYCR print out to CERSAI, Tower – 1, Office Block, 4th Floor, Plate-A, (Adjacent to Ring Road), NBCC, Kidwai Nagar East, New Delhi –110023.
  • Kindly note that the live environment and test environment are independent of each other and will require separate registration. The registration code generated in the test environment is NOT the final code. The pre-filled form generated while registering on the live environment has to be sent to CERSAI along with other required documents.

After receiving a sign-off on testing, document verification will take up to 7 working days. If there are any discrepancies, the same will be communicated to the nodal officer through mail.

The nodal officer has to send a mail to quoting their registration reference number requesting CKYC to place their registration on hold. Once the institution is placed on hold a link to the online registration form will be sent to the nodal officer. After making the necessary changes the nodal officer has to resubmit the form online. The revised application form will have to be sent to CERSAI along with supporting documents, if necessary.

A request letter (cover letter) stating changes required to be made to Institution´s details/nodal officer/admin users must be sent to CERSAI, Delhi office. This letter and other documents pertaining to the request must be signed by the head of institution/nodal officer/ authorised signatories as per the board resolution. The cover letter must be supported by the following documents:

  • Relevant sections of the registration form (available under the ´Register´ Tab in must be filled and duly signed.
  • Authorization letter for the new admin users
  • Certified copy of Proof of identity of the new admin users
  • Certified copy of the employee id of the new admin users.
  • In case the documents have been signed as per the board resolution, please share a certified copy of the board resolution.

C)   Connectivity queries

There needs to be internet connectivity with bandwidth of minimum 512 kbps and a scanner with the stipulated specifications.

Please refer connectivity guidelines in download section

  • Webpage based Search, Upload, Download and Update of records
  • SFTP bulk upload for Search, Upload, Download and Update of records
  • API service call for Search and Download of records.

Details for the above three methods are provided in our user manual available under the Download Section in our website.

D)   Digital Signature Queries

Digital signature certificate authentication is required for all users accessing the Central KYC application.

  • Type of Digital Signature: Signing
  • Certificate required for: Digital Security Certificate
  • Class of Certificate: Class II or Class III

The Digital Signature Certificate (DSC) has to be the same as per the user name in CKYC portal. We request you to change your DSC to match the CKYC User Name to resolve the error.

E)   KYC Management

As per Prevention of Money-laundering (Maintenance of Records) Amendment Rules, 2015, Rule 9 (I) (1A), every reporting entity shall within ten days after the commencement of an account-based relationship with a client, file the electronic copy of the client´s KYC records with the Central KYC Registry.

The Central KYC Registry requires data as per the common KYC template to be captured along with the scanned copy of the certified supporting documents (PoI/PoA)and photograph.

Please generate a PDF file consisting the data you would have received in your system from Aadhaar while performing EKYC /OTP based KYC. This PDF file along with a photograph should be uploaded into CKYC. Aadhaar is one of the officially valid documents that maybe used as both POA and POI, however should you require to upload additional KYC proofs there is a provision for the same.

The data required as per the common template needs to be captured in the CKYCR. However, the same can be captured on the common template or the institution´s account opening forms can be modified to capture the required information. The common template need not be scanned and uploaded onto the Central KYC Registry.

The specifications for scanning the supporting documents and photograph are stated below:

  • Document should be scanned in grey-scale with a scanning resolution of 150-200 DPI.
  • Photograph must be a recent passport style picture preferably in colour.
  • Dimensions 200 x 230 pixels
  • Size of photograph should be less than 50kb
  • Acceptable file format : '.tif', '.tiff', '.pdf', '.jpeg', '.jpg'
  • File Size (Maximum Limit): 350 kb for individual KYC record.

Please ensure that the data is legible and photograph should be of reasonable clarity.

There are four account types in the Central KYC form Normal, Simplified and Small. The account type can be gauged from the nomenclature of CKYC identifier issued to the customer.

  • For Normal Account, any of six officially valid documents (PAN, AADHAAR, Voter ID, Passport, Driving licence, NREGA Job Card) can be submitted for the ID of the customer.
  • For Simplified Measures Account, there are additional OVDs that are allowed as per RBI circular RBI/2015-16/42 dated July 1, 2015 - Point no. 2.3(i) & (ii) and point 3.2.2 I.A (iv) & (v). The KYC identifier for Simplified Measures Account will have a prefix ″L″.
  • For Small Account types, only personal details and photograph duly certified by the customer are required to be submitted. The KYC identifier for Small Account will have a prefix ″S″.
  • For Otp based ekyc accounts, generate a PDF file consisting the data you would have received in your system from Aadhaar while performing EKYC /OTP based KYC. This PDF file along with a photograph should be uploaded into CKYC. The KYC identifier for these accounts will have a prefix ″O″.

A financial institution can bulk upload the KYC details and the scanned images. Images for each record will be required to be zipped separately. The master zip file will be digitally signed by the financial institution.
Bulk upload is provided via SFTP. Based on validations, a response file will be generated. This file will contain the success records, error records and download records. The response file is available for download from the Central KYC application.

A financial institution will initiate an update request when there is a change in the information of the customer as existing in the records of Central KYC Registry.
Where the customer submits a request for updation of the data in the Central KYC Registry, financial institution will accordingly initiate the request after duly verifying the supporting documents. The financial institution will be required to update the details in the following cases:

  • There is a change in the details / information as existing in the KYC records in the linked registry.
  • There is doubt about the adequacy or veracity of previously obtained client identification data.
  • There is a change of the account type (e.g. Minor account to Normal account).

The updated data along with the scanned copy of the supporting document, where required, will be uploaded in the Central KYC Registry.
In order to initiate a modification request, the financial institution will need to be linked with the latest KYC record of the customer.

The CKYC number will be notified to the customer through email/SMS. The institution may view the details in the Daily MIS report under ″Logs and Reports″. If it is a bulk file, the same will be notified through the bulk response file.

On update of a customer record being processed at the Central KYC Registry, all linked financial institutions (institutions that have either uploaded or downloaded the KYC record for that customer), will receive an electronic update notification of KYC record. The financial institutions need to download the last updated record of the customer.

For Web-based entry, updates of individuals linked to it can be viewed in update notification under Logs and Reports.
For SFTP, a folder called Update Notification will be made available at the end of the day should there be any updates. Update notification report is generated everyday (End of the Day) in CSV format and is available in the respective institution´s SFTP response folder. If there are no updates on that day, a blank file will be generated. The update notification´s file name format will be as follows: FICode_FromDate_ToDate_VersionNo_TotalNumberofRecords.csv
Eg: IN0007_26032017_26032017_1.1_0.csv (Details available in SFTP System Specification V1.5 under
File structure and sample files for the update notifications are available under the ´Downloads´ tab in our website.
Section 6.4 of the User Manual ( has details with respect to screen based update notifications.

The Pin code masters available in the system have been obtained from India Post. However, if the pin code provided by the customer is not found in the system, the institute is requested to manually enter the pin code and also select a valid district and state.

Yes. Central KYC Registry will enable linkage of multiple communication addresses.
An individual wanting to maintain different addresses, office or residential, for different types of relationships, can fill Annexure-A1 and submit the details to the financial institution which in turn will initiate the update request on the Central KYC application.
In case of legal entities, where there may be a requirement to maintain different accounts for branches with different communication address, the entities shall submit the correspondence address details in Annexure-A2.

The CKYC number of any individual will not be displayed in any website as it is confidential data. Individuals may approach the financial institution where they provided their CKYC documents to obtain the number.

A record can be downloaded only if anyone of the below authenticating factors is provided correctly:

  1. Date of birth
  2. Pincode + year of birth
  3. Mobile number

F)   CKYC Application User Hierarchy

The organisation hierarchy and access matrix needs to be defined by the Institution´s admin / co-admin. There are three levels of hierarchy:

  • Institute
    • Admin prefix IA (eg. IA008162
    • User prefix IU (eg. IU008162)
  • Region
    • Admin prefix IRA (eg. IRA008162)
    • User prefix IRU (eg. IRA008162)
  • Branch
    • Admin prefix IBA (eg. IBA008162)
    • User prefix IBU (eg. IBU008162)

    For all activities pertaining to creation/ deactivation of users, KYC records and payments, there is a maker-checker requirement.
    A maker can be a ´User´ as well as an ´Admin´ across all levels in the user hierarchy. A checker can only be an ´Admin´. If an ´Admin´ is the maker, the checker needs to be another ´Admin´ at the same level.

It is mandatory for an institution to create at least one region and one. The institute may create as many regions and branches as required. There need not be an exact mapping of the physical branches to the branches in CKYCR ‾ however this is left to the discretion of the institution.

G)   Billing Management

  • Charges per KYC record are as follows:
    • Upload Rs. 0.80
    • Download Rs. 1.10
    • Update Rs.1.15
  • There is no cost associated with Search
  • The above fee structure remains the same for all channels of Search, Upload, Download & Update

For availing the services of the Central KYC Registry, financial institutions need to make an advance payment to CERSAI´s account which will be maintained in a web wallet that can be monitored by the institution. For every service availed, the requisite amount will be deducted from the wallet balance. If there is insufficient balance, the financial institution will not be able to avail the paid services until the balance is replenished.
To make the advance payment, the institution will be required to generate a proforma invoice through the Central KYC application. This option is available in ″Proforma Invoice list″ under Billing Management. The payment has to be effected through NEFT/RTGS to CERSAI´s bank account and the reference of system generated proforma invoice has to be mentioned in the ´Remarks´ field during funds transfer.The CERSAI Bank details will be available on the proforma invoice itself.
The institution is required to update payment details like TDS, UTR No. and payment date against each proforma invoice generated.
Upon confirmation of the payment receipt, the balance will be updated in the wallet. In case of tax deducted at source (TDS), the institutions are required to upload a copy of the TDS certificate against the respective invoices.
The institution will be intimated when the balance goes below the threshold and minimum limits set by them. The institution can download / print the usage details until the previous day.

Institution Admins, Account Users and Regional Admins are authorised to generate proforma invoice for institutes and carry out billing activities.

When a financial institution makes payment to CERSAI´s account through NEFT/RTGS, the corresponding proforma invoice reference number needs to be mentioned in the ″Remarks″ field during transfer. In case Proforma invoice number is not mentioned or incorrect invoice number is provided during payment then Institution web wallet will not be credited until payment is linked with correct invoice. The UTR number along with amount paid will be displayed in ´Unconfirmed transactions´ option under Billing Management. The user has to click on ´Link´ to view all the proforma invoices generated. Select the proforma invoice against which the payment has been made and click on ´Link Proforma Invoice´. If the payable amount mentioned in the linked proforma invoice matches the actual payment made, then the web wallet will be credited by the creditable amount mentioned in proforma invoice.

Reporting entity can view the details of the payment under the Wallet details. It provides the wallet balance, minimum balance, threshold balance and TDS hold amount, if any.

The amount credited to and debited from the institution´s web wallet for a particular interval of time is available in the ´Ledger Report´ option under the Billing Management menu.Along with amount credited and debited user can also see the opening balance on date selected in ″From date″ field and closing balance on date selected in ″To date″ field.
In case of debit, user can see the detailed view of usage by clicking on the hyper link provided under Particulars column that will redirect the user to the usage intimation screen.
In case of credit, user can see the detailed view of Invoice by clicking on the hyperlink provided under Particulars column. This will redirect the user to the Proforma invoice details screen.

GSTIN registration is mandatory for proforma invoice creation. The financial institution (FI) can register their GSTIN number by clicking on the GSTIN Details option under the Billing Management Tab. Please refer to the user manual for the maker – checker process followed to complete GSTIN registration on the CKYC portal.
The place of supply and PAN number shall be auto-populated based on the details provided at the time of the institution’s registration with CKYC. Default place of supply state will be as per registered address. Place of Supply state will change if ‘GST as per Communication Address’ is selected. User needs to enter last 3 characters (alphanumeric) of GSTIN. FI needs to check ‘GST not applicable” if they fall under that category.

We currently do not facilitate cheque payments.