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:
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.
The nodal officer has to send a mail to helpdesk@ckycindia.in 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.
In the case of change/modification to one of the Institutional admins
An active Institutional admin (IA) can use ‘Institution Admin Request’ option under User Management to initiate a change request with CERSAI to deactivate an existing IA and create a new IA in their place. You may also initiate requests to update IA details using this functionality.
Download the prefilled request form by clicking on the “Download request letter”. Send the duly signed request form and documents as per the checklist on the request form to CERSAI, Delhi. Upon CERSAI’s approval, the service request will be executed and completed.
In the case of change in both the Institutional admins or change in the Institution details/Nodal officer/Head of institution
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:
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 https://www.ckycindia.in/ckyc/assets/doc/Connectivity-Guidelines-2.pdf
Details for the above three methods are provided in our user manual available under the Download Section in our website.
Digital signature certificate authentication is required for all users accessing the Central KYC application.
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.
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:
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.
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:
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 https://www.ckycindia.in/ckyc/downloads/index.html)
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 (https://www.ckycindia.in/ckyc/downloads/index.html) 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.
Customers can give a missed call to 7799022129 to fetch their CKYC card. In case their card CKYC card cannot be fetched in this manner they may use the alternative method mentioned below.
Customers can fetch their KYC card by verifying the mobile number using the link https://www.ckycindia.in/kyc/getkyccard. The link to download your CKYC card will be sent by SMS to your mobile number registered with CKYC.
A record can be downloaded only if anyone of the below authenticating factors is provided correctly:
The organisation hierarchy and access matrix needs to be defined by the Institution´s admin / co-admin. There are three levels of hierarchy:
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.
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.
Reporting entities are requested to select the applicable TDS rate as per section 194J of Income Tax Act, 1961 from the drop down provided while generating the proforma invoice on CKYCRR. Please note it is the responsibility of the person making the payment to deduct TDS, as applicable, on the amount paid. Please ensure TDS deduction is as per Income Tax Act 1961.
The CKYCR pincode master enables auto-population of the district and state fields of the address at the time of upload and update of KYC reocrds (via screen entry or bulk mode).
The record may be uploaded/udpated with a pincode not available in our masters by inputting a valid district - state combination from our District master.
If the pincode is available in our pincode master, the district value should match our master exactly. Where the pincode is not available in the master, the district- state combination should be an exact match to any one of the combinations available in the district master.
The pincode master is derived from the Pincodes directory published by India Post.
a. Merger/Demerger Request tab under Administration module can be used to raise requests to merge two or more institution codes in CKYCRR application to reflect the merger/takeover/amalgamation/acquisition/business closure that has taken place in the real world. The IA admin has to input the type of M&A, Requestor FI Code, and Merger FI Code.
b. After submitting the request, the checker may go to 'Merger/Demerger Approval' and click on 'Action' icon to approve the request. The request will be sent to CERSAI for their approval. In case the request needs to be rejected or modified please click on “Reject”.
The maker may then raise a fresh request with proper details. Post verification of documents, the service request will be approved/rejected by CERSAI. Please refer to the list of documents required to be submitted to CERSAI in the User Manual uplaoded in the Downloads section - https://www.ckycindia.in/ckyc/assets/doc/User_Manual_1.12.1.pdf".Only the Requestor FI Code (Surviving entity) will remain active post CERSAI’s approval of the request. The Merger FI codes will get deactivated.
Once a reporting entity’s FI code is deactivated:
a. they shall not be able to avail CKYC services.
b. its users will not be able login to the deactivated FI code.
c. their SFTP access will be revoked.
d. API access will be revoked.
e. all under process records will be rejected.
f. will stop receiving update notifications from CKYCRR."
a. all regions, branches and users from the merger fi codes (deactivated) will be transferred to the requestor FI Code (surviving entity).
b. Requestor FI Code will be linked to all the records of the merger FI Codes (deactivated entities). Therefore, they shall also receive update notifications about these records.
c. reports, payment receipts and tax invoices of merged FI code (deactivated status) will be available to the requestor FI Code (Surviving entity) for view and download.
d. wallet balance and TDS hold amount will transfer to the requestor FI Code (Surviving entity).
Yes, all the reporting entities registered with Central KYC Records Registry are required to obtain the consent from the customer for downloading their CKYC record from Central KYC Records Registry.
Download consent is to be obtained every time the record is being downloaded from Central KYC Records Registry. This can be made part of account opening form or update form.
Download consent form need not be uploaded on Central KYC Records Registry. The consent form should be retained offline with the reporting entity.
Reporting entity should start obtaining the download consent form from the customer with immediate effect.
The Download Consent form is available for download under the Notifications tab or CLICK HERE for download.