Aadhaar Generation
Aadhaar generation & issue
Aadhaar Generation involves process like quality check, packet validation, demographic and biometric de-duplication etc. Aadhaar is generated successfully only if:
- Quality of enrolment data meets prescribed standards laid down by UIDAI.
- The enrolment packet passes all the validations done in CIDR
- No Demographic/Biometric duplicate is found
If any of the above conditions is not satisfied, then Aadhaar number will not be issued and the enrolment gets rejected. The processes leading to Aadhaar generation are explained below.
Uploading Enrolment Data to CIDR
Each enrolment data is in a form of software packet which gets encrypted after completion of enrolment in the client itself and is uploaded to the central ID repository (CIDR) using the upload client provided to the Enrolment Agencies by UIDAI. The uploaded packet records are maintained in the client software to prevent duplicate packets being uploaded to the server, thus saving the processing time as well as packet rejection. All the data transfer to the server is performed using secured file transfer Protocol and so there is no chance of leakage of data to any unauthorised agency. The documents received from individuals seeking to enrol are also scanned and becomes part of enrolment packet which is uploaded to CIDR.
CIDR Sanity Checks: Each enrolment packet is exhaustively checked for validity – checksums, packet meta data, etc. – in the CIDR DMZ using automated process before it is moved to the production zone of CIDR for processing.
Data Archival: In CIDR, the contents of packet are read and stored in a table before archiving to ensure that the data is kept securely. The archival system has the following requirements:
- All original packets (enrolments, updates, etc.) are required to be archived as-is, and “forever”, ensuring high availability, and zero data loss
- Archived packet is kept securely and separated from core enrolment and authentication systems.
- Archival system may allow on-demand data retrieval with appropriate access control and approvals.
- Regular back up of Archived data is taken to ensure zero data loss.
If any of the above conditions is not satisfied, then Aadhaar number will not be issued and the enrolment gets rejected. The processes leading to Aadhaar generation are explained below.
Main Processing Pipeline
After the sanity checks pass, the enrolment packet is passed onto the main processing pipeline. At a high level, this includes the following stages:
CIDR Sanity Checks: Each enrolment packet is exhaustively checked for validity – checksums, packet meta data, etc. – in the CIDR DMZ using automated process before it is moved to the production zone of CIDR for processing.
Automated Data Validation: Following validation checks are done in CIDR for demographic data
- Name & Address validations
- Language Validations
- Pincode and Administrative regions
- Regular back up of Archived data is taken to ensure zero data loss.
If any of the above conditions is not satisfied, then Aadhaar number will not be issued and the enrolment gets rejected. The processes leading to Aadhaar generation are explained below.
Uploading Enrolment Data to CIDR
Each enrolment data is in a form of software packet which gets encrypted after completion of enrolment in the client itself and is uploaded to the central ID repository (CIDR) using the upload client provided to the Enrolment Agencies by UIDAI. The uploaded packet records are maintained in the client software to prevent duplicate packets being uploaded to the server, thus saving the processing time as well as packet rejection. All the data transfer to the server is performed using secured file transfer Protocol and so there is no chance of leakage of data to any unauthorised agency. The documents received from individuals seeking to enrol are also scanned and becomes part of enrolment packet which is uploaded to CIDR.
CIDR Sanity Checks: Each enrolment packet is exhaustively checked for validity – checksums, packet meta data, etc. – in the CIDR DMZ using automated process before it is moved to the production zone of CIDR for processing.
Data Archival: In CIDR, the contents of packet are read and stored in a table before archiving to ensure that the data is kept securely. The archival system has the following requirements:
- All original packets (enrolments, updates, etc.) are required to be archived as-is, and “forever”, ensuring high availability, and zero data loss
- Archived packet is kept securely and separated from core enrolment and authentication systems.
- Archival system may allow on-demand data retrieval with appropriate access control and approvals.
- Regular back up of Archived data is taken to ensure zero data loss.
If any of the above conditions is not satisfied, then Aadhaar number will not be issued and the enrolment gets rejected. The processes leading to Aadhaar generation are explained below.
Where to Enrol
Enrolment in all the states/UTs is being covered by UIDAI. Individuals of all states/UTs seeking enrolment, are required to enrol only at nearby Aadhaar Enrolment Centre/Aadhaar Camps.
Content Information
Published on: 17 Apr 2026
Last Updated: 22 May 2026
- Documents
- Aadhaar Dashboard - Unique Identification Authority of India | Government of India
- Handbooks
- Videos - Unique Identification Authority of India | Government of India
- Annual Reports
Content Information
Published on: 17 Apr 2026
Last Updated: 22 May 2026