Signzy CKYC 2.0 API
Bridge your Core Banking System to the new CERSAI 2.0 Registry
With the new CERSAI validations, even small errors can cause instant rejection and customer drop-offs. Signzy connects your CBS system to CKYCRR 2.0, enabling first-time-right verification for faster onboarding, easy CKYC search and download to stay fully compliant.

Migrate to CKYCRR 2.0 without disrupting your onboarding
Strengthen your compliance, improve user experience, and gain a competitive edge with Signzy’s CKYC 2.0 API
CERSAI-ready Aadhaar masking, data, & documents
Auto-fix data errors, adjust and normalize images to CERSAI specs, and mask Aadhaar in real time so every record is submission-ready from the first touch.
Go from any input format to CKYC 2.0 with no manual ops
Convert any input format into CKYC 2.0 JSON schema, visually resolve probable face matches with confidence scores, and push cases straight to CERSAI on approval.
Stay in sync with CERSAI across the customer lifecycle
Listen to CERSAI updates 24/7, scan and verify CKYC QR codes instantly, and support human-readable CKYC IDs for a seamless and automated process.
A CKYC 2.0-ready stack for modern banks and NBFCs
Use flexible, automated workflows that adapt to different countries, risk levels, and compliance needs
Data Validation
Document Quality
Aadhaar Masking
De-duplication
Data Format
Workflow Speed
Record Tracking

Which teams use Signzy’s CKYC API?
50+ banks and businesses trust Signzy to stay RBI, SEBI, and IRDA-compliant.
Book a demoRelevant Industries
Advanced KYC workflows and better security
An intelligence layer that works for your team to automatically fix data errors and optimise images to CERSAI standards
De-Duplication Decision Engine
Name Screening & Grading
Modern Security Protocols
Pre-emptive Error Management
Advanced Encryption Standards
De-Duplication Decision Engine
Name Screening & Grading
Modern Security Protocols
Pre-emptive Error Management
Advanced Encryption Standards

APIs designed to scale seamlessly alongside your growing business.
From banks to fintechs, Signzy processes millions of verification checks every day with consistent performance, regulatory compliance, and enterprise-grade reliability.
APIs designed to scale seamlessly alongside your growing business.
Signzy processes millions of verifications
From banks to fintechs, Signzy processes millions of verification checks every day with consistent performance, regulatory compliance, and enterprise-grade reliability.

The end-to-end verification stack
Enhance every verification step with deeper insights across KYC, KYB, and AML screening.
Video KYC
Real-time vKYC for compliant, secure, and seamless user onboarding in minutes.
Aadhar eSign
Perform end-to-end Aadhaar eSign for fully paperless and automated contract management.
AML Screening
Screen users against sanctions, PEP, adverse media, negative news, and watchlists in real time.
Bank Account Verification
Verify bank account ownership instantly, perform IBAN checks, and reduce payment fraud.
Designed for developers, trusted by compliance teams.
Integrate the platform during lunch hour, customize based on your needs, and go live within 2-4 weeks :)

FAQ
What is CERSAI's CKYCRR 2.0?
CERSAI's CKYCRR 2.0 refers to the Central KYC Records Registry (CKYCRR) managed by the Central Registry of Securitisation Asset Reconstruction and Security Interest of India (CERSAI), which operates under the regulatory framework of the Prevention of Money Laundering Act (PMLA) and associated rules.
The CKYCRR 2.0 is the next-generation centralised repository for Know Your Customer (KYC) records across all regulated financial institutions in India, designed to store, safeguard, retrieve and share verified customer KYC information in a digital, structured format that supports real-time access and submission.
The CKYCRR replaces repetitive, institution-specific KYC processes by maintaining a single, authoritative database that issues unique 14-digit CKYC identifiers for individual customers and enables seamless interoperability across banks, NBFCs, mutual funds, insurance companies and other regulated entities under RBI, SEBI, IRDAI and PFRDA jurisdictions.
How is CKYC 2.0 different from CKYC 1.0?
CKYC 2.0 is an upgraded version of the earlier CKYC framework, which was largely based on periodic file uploads and manual document handling. The key changes are:
- API-based connectivity: Regulated entities can now submit, search, and retrieve CKYC records through CERSAI's structured APIs instead of relying only on batch or file-based processes.
- Standardised data formats and error codes: Information is exchanged in defined and standardised JSON, improving data consistency and automation.
- Stronger matching and de-duplication: The registry applies enhanced identity matching using officially issued identifiers and demographic data to reduce duplicate records.
- Improved data security and privacy controls: CKYC 2.0 incorporates tighter access controls and masking requirements for sensitive information, in line with regulatory and data-protection guidelines.
- Verification of CKYC data from Source: CERSAI validates each OVDs by doing OCR and verification with the source for each upload/update push.
These changes make CKYC 2.0 more system-driven, interoperable, and audit-ready compared to the earlier framework.
Do existing Core Banking Systems support CKYC 2.0 APIs natively?
Most existing Core Banking Systems (CBS) and legacy customer onboarding systems were originally built for the older CKYC 1.0 workflows, which relied on batch uploads, manual document handling, and flat file formats. As a result:
- Legacy CBS platforms typically do not support the structured JSON schemas required by CKYC 2.0 APIs out-of-the-box.
- Banks and NBFCs must implement middleware or transformation layers to convert customer onboarding data into the new real-time, API-based formats that the CKYCRR 2.0 registry expects.
- Without API readiness, institutions risk high rejection rates, manual rework, and operational delays because CKYC 2.0 demands precise field-level validation and immediate submissions via API endpoints.
- This is why modernised integration stacks like Signzy are critical for CKYC 2.0 compliance and operational efficiency.
How is Aadhaar masking handled under CKYC 2.0?
Under CKYCRR regulatory guidelines, institutions must ensure privacy and data protection compliance when submitting KYC information to the repository. One key requirement is that sensitive identifiers like Aadhaar (first 8 digits) must be masked before submission to protect customer privacy and reduce exposure of personally identifiable information.
Signzy's privacy-first approach strengthens compliance with national data protection expectations and reduces the risk of data misuse across the financial ecosystem.
How does Signzy help with CKYC 2.0 compliance?
Signzy's CKYC 2.0 solution provides a fully integrated compliance layer that bridges your internal systems (like CBS, onboarding platforms, and customer data stores) to the CERSAI CKYCRR 2.0 registry in real time:
- Real-Time API Orchestration: Signzy manages structured JSON data exchange, eliminating the need for manual uploads or custom in-house transformation layers.
- First-Time-Right Data Validation: Signzy auto-validates and sanitises customer data before submission, reducing CERSAI API rejections and customer drop-offs.
- Image & Identity Intelligence: Automated image correction and Aadhaar masking ensure compliance with CKYC 2.0 document quality and privacy requirements.
- De-duplication & Record Hygiene: Advanced matching and decision logic help resolve probable duplicates before submission, aligning with CKYCRR 2.0 expectations.
- Lifecycle Sync: Post-submission updates and lifecycle changes are synchronised back to your core systems, keeping records current without operational overhead.
Together, these capabilities mean fewer errors, improved onboarding conversion, and robust regulatory compliance that aligns directly with CKYCRR 2.0 norms.
How long does it take to integrate CKYC 2.0 with Signzy?
The integration timeline for CERSAI 2.0 with Signzy depends on your internal systems and architecture, but Signzy's platform is designed for integration within 48-72 hours:
- Pre-built API connectors and data transformation modules significantly reduce integration effort compared to custom builds.
- Typical implementation cycles can be measured in days rather than months, because most of the heavy lifting such as data validation logic, compliance workflows, structured API orchestration, and error handling is already embedded in Signzy's compliance stack.
- With sandbox testing, API onboarding, and controlled rollout plans, banks and financial institutions can go live with real-time CKYCRR submissions in a shorter timeframe while maintaining full audit trails and compliance readiness.
My question isn't listed here
If your question isn't covered in the FAQs above, you can reach out to our compliance and integration team on connect@signzy.com.



