CKYC CERSAI Integration

The CKYC CERSAI Integration is a fully automated, asynchronous process that handles the secure submission of KYC data to the CERSAI SFTP server and the subsequent processing of response files. The entire workflow is designed for high-volume, resilient operations without manual intervention.

Process Overview

The integration operates through a series of scheduled background tasks that manage the entire lifecycle of a KYC batch, from submission to final status update.

Stage 1: Batch Submission and Acknowledgment (RES0)

Once a batch file is generated and digitally signed, the system automatically handles the submission to CERSAI and processes the initial acknowledgment.

1. SFTP Upload: A scheduled task continuously scans for newly created batch files and securely uploads them to the designated CERSAI SFTP server.
2. Monitor for RES0: After a successful upload, the system begins polling the SFTP server for the RES0 acknowledgment file, which typically arrives within two hours.
3. Process RES0: Upon receipt, the RES0 file is downloaded, parsed, and its contents are used to update the status of the batch in the database.
   • Accepted: The batch has been accepted by CERSAI for further processing.
   • Rejected: The batch has failed initial validation and will not be processed. The rejection reasons are logged, and a callback is sent to the financial institution.

Stage 2: Initial Match Results (RES1)

After a batch is accepted, CERSAI performs an initial de-duplication and provides the results in a RES1 file.

1. Monitor for RES1: The system monitors the SFTP server for the RES1 response file, which is expected within six hours of FI approval.
2. Process RES1: The file is downloaded and parsed to extract the status for each individual KYC record within the batch.
   • No Match: No existing KYC record was found. The case proceeds to the next stage for new CKYC ID creation.
   • Confirmed Match: A definitive match was found in the CERSAI database. The system flags this case for the Confirmed Match workflow.
   • Probable Match: One or more potential matches were found. The case is flagged for the Probable Match (RECON) workflow.
   • Rejected: The individual record was rejected due to data or validation issues. The reason is logged, and a callback is triggered.

Stage 3: Final CKYC Status (RES2)

The RES2 file provides the final status for records that were processed for new CKYC ID creation, and it also finalizes the status for cases that went through match resolution.

1. Monitor for RES2: The system polls the SFTP server for the RES2 file, which typically arrives within 24 hours but can sometimes take longer.
2. Process RES2: The file is downloaded and parsed to retrieve the final outcome for each record. The system handles multiple scenarios:
   • CKYC Created: A new 14-digit CKYC ID has been successfully generated. It is extracted from the file, the case is marked as complete, and a success callback is sent.
   • Confirmed Match: For cases that were previously identified as a confirmed match, this status re-confirms the match. The system parses the remarks to extract the existing CKYC number and updates the case accordingly.
   • Probable Match: If the final status is a probable match, the system ensures the case is correctly flagged for the Probable Match (RECON) workflow.
   • Case Rejected: The record was ultimately rejected by CERSAI. The specific rejection reasons (e.g., "FI Recon TAT lapsed") are logged for analysis, and the case is marked as failed.

Automated Match Resolution Workflows

The platform includes sophisticated, automated workflows to handle cases identified as "Confirmed Match" or "Probable Match," ensuring that duplicates are managed efficiently without manual intervention.

Confirmed Match Workflow

For cases flagged as a "Confirmed Match" in the RES1 response, the system initiates an automated process to retrieve the existing CKYC number.

1. Batch Download File Generation: The system aggregates all "Confirmed Match" cases and generates a specialized download batch file compliant with CERSAI specifications.
2. Secure Upload: This new batch file, along with a corresponding trigger file, is securely uploaded to the CERSAI SFTP server.
3. Response Monitoring: The system then monitors the SFTP server for a response file containing the existing CKYC numbers for the matched records.
4. Database Update: Upon receiving the response, the CKYC numbers are extracted and used to update the corresponding case records in the database. The cases are then marked as CKYC Found, and a success callback is sent.

Probable Match (RECON) Workflow

Cases marked as "Probable Match" are routed to an advanced AI-powered reconciliation engine to determine the correct outcome.

1. RECON File Polling: The system periodically polls the CERSAI SFTP server for a RECON file, which contains the details of potential matches for the submitted records.
2. Multi-Factor Match Analysis: Once the RECON file is downloaded, it is parsed, and a multi-stage analysis is performed on each potential match:
   • Face Match (Priority 1): The photograph from the submitted documents is compared against the photographs in the RECON file using an advanced facial recognition API.
   • Name Match (Priority 2): A sophisticated name-matching algorithm compares the customer names, accounting for variations and phonetic similarities.
   • Age Match (Priority 3): The date of birth is compared to identify logical matches.
3. Weighted Scoring & Decisioning: A weighted average score is calculated based on the results of the three matching stages.
   • One Match Accepted: If a single record confidently exceeds the matching threshold, it is accepted as the correct CKYC record.
   • Multiple Matches Accepted: If multiple records exceed the threshold, a tie-breaking logic is applied (e.g., selecting the oldest CKYC record).
   • No Match Accepted: If no record meets the confidence threshold, the system concludes that no valid match exists, and the case is treated as a "No Match" for new CKYC creation.
4. Response and Update: The final decision is recorded, and the database is updated accordingly. The case then proceeds either to CKYC creation or is closed with the found CKYC number.