Scribd
Upload
16 views

Steps for API Integration v1.1

The CKYCRR streamlines the KYC process by allowing clients to submit their KYC details only once, after which they receive a unique CKYC Identifier for future account engagements. Reporting entities can easily search, download, and update KYC records from CKYCRR, eliminating the need for repeated submissions unless changes are necessary. Additionally, the document outlines the steps for API integration for accessing CKYCRR services, including testing and production setup requirements.

Uploaded by

ashutosh2894
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
16 views

Steps for API Integration v1.1

The CKYCRR streamlines the KYC process by allowing clients to submit their KYC details only once, after which they receive a unique CKYC Identifier for future account engagements. Reporting entities can easily search, download, and update KYC records from CKYCRR, eliminating the need for repeated submissions unless changes are necessary. Additionally, the document outlines the steps for API integration for accessing CKYCRR services, including testing and production setup requirements.

Uploaded by

ashutosh2894
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 5

I.

Overview of the role of CKYCRR in the KYC process


Since the operationalisation of CKYCRR, clients are required to submit their KYC
details only once with any of the reporting entities of RBI, SEBI, IRDAI and PFRDA at
the time of account-opening. Thereafter, they are assigned a unique CKYC Identifier
that can be used by the client when they are establishing an account-based
engagement with the reporting entity. Reporting entities are not required repeat the
KYC process in case the client’s KYC record is already registered with CKYCRR, as
the KYC record can be easily retrieved in an electronic format from the Registry.

When the customer approaches the reporting entity, the following steps can be used
to perform seamless account-opening using the KYC record from CKYCRR.

Step 1 and 2: Search and Download


The CKYC Search function allows the reporting entities to check if a KYC record is
already registered on CKYCRR. Search may be performed based on the 14-digit CKYC
identifier or a valid ID number of an Officially Valid Document (OVD).
If the KYC record is already registered in CKYCRR, then the reporting entity can
retrieve the KYC records online from CKYCRR using the CKYC Download function.
The client is not required to submit the same KYC documents or information or any
other additional identification documents or details, unless the KYC record requires
to be modified due to some change in the information of the client and/or the
reporting entity considers it necessary for enhanced due diligence.
Step 3: Update
In case of changes or differences in the details of a client available in the KYC record,
then the reporting entity can initiate a CKYC Update request in CKYCRR. To initiate
an update request, the reporting entity will need to have the latest KYC record of the
customer. When a record is updated, all the institutions linked* to the KYC record in
CKYCRR will be notified through a system report of the update to the KYC record.
(* Reporting entities who have either uploaded or downloaded a record in CKYCRR
are considered to have an account-based relationship with the client and are therefore
linked to the KYC.)
Upload of KYC records that are not registered in CKYCRR
The reporting entities can use the KYC Upload function to register the KYC record in
CKYCRR where the client’s record is not available in the Registry. In such cases, the
KYC record should be uploaded to CKYCRR within ten days after the commencement
of an account-based relationship with a client.
Post the generation of the CKYC identifier, the reporting entity shall communicate the
same to the client in the writing.
II. CKYC API Integration

The high-level API documents are available on our website – the links are provided
below:

1. Search Document-
https://www.ckycindia.in/ckyc/assets/doc/API-Secured-Search-Document.zip
2. Download Document-
https://www.ckycindia.in/ckyc/assets/doc/SecuredDownloadAPIDocumentve
rsion.zip
In addition, to the above please refer to the technical documents for API signing and
decryption shared separately. Please note the steps are applicable to both Search and
Download API. The integration process may be initiated by sharing the 4 documents
with the technical teams.

The technical teams shall also require the following from the business/ operations
team to successfully perform API integration:

Action points for the operations/business team:


1. Ensure that the API integration is first completed and tested in the CKYC test
environment. To enable this the operations/business team has to :
a. Share the CKYC testbed FI Code with the technical team
b. Ensure that the API requests are sent to the URLs of CKYC test
environment. These are provided in the document link provided
above.
c. Share with the technical team the CERSAI public key that is available
in the folders that are available in the links mentioned above. File name
is “server_pub.cer"
d. Upload the Institution’s digital signature (DSC) public key and register
the IPs in the CKYC testbed portal
i. Login to CKYC testbed as an institutional admin (IA), go to User
management, click on “Upload Public key” option.
ii. Register the IP address from where the API requests will be sent
to CKYC testbed.
iii. Also, extract the public key (in .cer format) from the Institution’s
DSC (Class II or Class III) and upload the same in the CKYC
testbed portal – technical support may be obtained if required.
iv. The private key from the above-mentioned DSC has to be
provided to the technical team so that they may integrate in the
Institution’s API code being developed. Please note the public
key in point (iii) and the private key (iv) must belong to the
same DSC. Private key extraction may require technical
assistance.
2. To test the API integration in the test environment, please share sample test
cases with the technical team. Test cases may be generated by uploading
dummy records in the test environment.
3. Once testing is completed please proceed to integrate the CKYC APIs with
your production setup. Please note the following will be different in
production or the actions have to be repeated in the production environment:
a. FI Code
b. IPs have to be registered and the Institution’s public key will have to be
uploaded in the CKYC live environment by the institutional admin
c. The private key will have to be integrated in the Institution’s API code
d. API requests containing customer’s data have to be sent to the CKYC
live URLs mentioned in the API documents on our website (links
provided above).

You might also like