CKYC Bulk Automation Process

The CKYC Bulk Automation Process enables financial institutions to efficiently submit large volumes of KYC records to the Central KYC Registry through a scalable, asynchronous workflow that operates in the background.

Overview

Backend bulk processing is designed for institutions that need to:

Process thousands of KYC records without manual intervention
Integrate with existing enterprise systems via a simple data intake API
Automate the creation of CERSAI-compliant batch files
Handle high-volume customer onboarding efficiently

Process Flow

The automation is a multi-stage process that begins with data intake and ends with the secure submission of files to CERSAI.

Stage 1: Data Intake via API

Financial institutions submit individual KYC records to the platform through a secure API endpoint. This initial step is for ingesting data into the system, not for creating the final CERSAI batch file.

Intake Endpoint:

POST /ckyc-upload
Content-Type: application/json
Authorization: Bearer {token}

Data Ingestion: The API accepts a JSON payload containing one or more KYC records.
Initial Validation: The platform performs preliminary validation on the submitted data to ensure required fields are present.
Queued for Processing: Valid records are stored and queued for the next stage in the automation workflow.

Stage 2: Asynchronous AI Processing & Enrichment

Once ingested, each KYC case undergoes an automated processing and enrichment pipeline.

AI Analysis: The platform's AI engine performs OCR on submitted documents, extracts key information, and validates it against the provided data. It may also perform face matching where applicable.
Data Correction: The system automatically corrects common formatting issues to ensure the data aligns with CERSAI specifications.
Manual Review (Optional): Cases with significant discrepancies or low-confidence AI results can be routed to a manual review queue in the CKYC Portal for human oversight. The workflow can be configured as AI-only, Manual-only, or a Hybrid model.

Stage 3: Automated Batch Creation

A scheduled, background process automatically collects all processed and verified KYC records that are ready for submission.

Case Collection: The system queries the database for records that have successfully passed the processing stage and are pending submission.
Intelligent Batching: The collected records are grouped into optimal batches. The system generates a pipe-separated .txt file according to CERSAI's format specifications.
File & Image Packaging: All associated documents and images for the records in the batch are collected, compressed, and packaged into a .zip archive alongside the data file.

Stage 4: Secure SFTP Submission

The final stage involves the automated and secure transfer of the generated batch files to the CERSAI SFTP server.

Secure Connection: The system establishes a secure SFTP connection to CERSAI.
File Upload: The generated .zip archive and a corresponding trigger (.trg) file are uploaded to the designated input directory on the SFTP server.
Status Update: Upon successful upload, the status of all records within the batch is updated in the system to "Submitted to CERSAI".

This entire process, from data intake to SFTP submission, is designed to run automatically with minimal human intervention, providing a seamless and scalable solution for CKYC compliance.

Implementation

Data Preparation

Required Fields:

Customer ID and KYC type
Personal details (name, DOB, gender, nationality)
Identity documents (PAN, Aadhaar, passport, driving license)
Address details (current and permanent)
Contact details (mobile, email)

Validation Rules:

PAN: 10-character alphanumeric format
Aadhaar: 12-digit numeric format
Mobile: 10-digit Indian mobile number
Email: Valid email format
Date: ISO 8601 format (YYYY-MM-DD)

Batch Processing

Batch Size Recommendations:

Small: 100-500 records
Medium: 500-2000 records
Large: 2000-5000 records
Enterprise: 5000+ records

Processing Modes:

Synchronous: Real-time processing
Asynchronous: Background processing
Scheduled: Time-based processing

API Integration

Intake Endpoint:

POST /ckyc-upload
Content-Type: application/json
Authorization: Bearer {token}

Request Body:

The API expects a JSON object containing a list of individual KYC records.

{
  "records": [
    {
      "kyc_ref_no": "YOUR_UNIQUE_REF_123", // FI's unique identifier
      "pan": "ABCDE1234F",
      "basic_details": {
        "applicant_first_name": "Baiju",
        "applicant_last_name": "Dodhia",
        "dob": "1990-01-15",
        "gender": "M"
      },
      "poa": {
        "document_images": [
          {
            "document_body": "base64-encoded-string...",
            "title": "AADHAAR",
            "document_type": "PDF"
          }
        ]
      }
      // ... other required fields for a CKYC record
    }
  ]
}

Success Response Format:

Upon successful submission, the API returns a job_id for tracking.

{
  "job_id": "a1b2c3d4-e5f6-7890-1234-567890abcdef",
  "status": "initiated successfully"
}

Error Response Format:

If the request body is invalid, the API will return an error message.

{
    "status": 500,
    "message": "Invalid request body",
    "e": "Details about the validation error."
}

Error Handling

Common Error Codes

Error Code	Description	Resolution
`INVALID_PAN`	PAN format is incorrect	Verify PAN format and re-upload
`DUPLICATE_RECORD`	Record already exists	Check for existing records
`MISSING_FIELDS`	Required fields are missing	Complete missing information
`VALIDATION_FAILED`	Data validation failed	Review and correct data