Remote Aadhaar Seeding Framework

Introduction
As the number of Aadhaars generated has increased, the focus at many States has
shifted to Aadhaar enablement of service delivery applications. Service providers
who integrate with UIDAI’s platform have to overcome the challenge of linking their
database records of customers and beneficiaries with the 12-digit Aadhaar numbers.
Currently most seeding initiatives are organic and limited in scale because of some
of the challenges listed in the previous section. Further since service delivery
databases are owned by various departments, organic seeding initiatives at a
scheme or department level leads to inconvenience for the resident who is a
beneficiary of multiple services from various departments. Finally there are different
levels of infrastructure/ personnel availability at different states as well as differing
channels and processes being used.
UIDAI has been closely involved in enabling States in implementing Aadhaar
enabled service delivery through a variety of initiatives such as the ICT assistance,
coordinated pilot programs, SRDH software and support etc. Along the same lines,
UIDAI currently proposes to enable service delivery owners in expediting seeding of
their databases by developing and hosting an online platform called the Remote
Aadhaar Seeding Framework (RASF) application.
The RASF application is a central platform that enables converging various seeding
channels into one
central staging area
which is then
accessible to
operators at various
departments (service
delivery owners) for
verification of the
seeding and inclusion
into their service
delivery databases.
UIDAI – RASF – Introduction Document
Copyrights © 2012. All rights reserved. Page 15 of 19
The RASF application aims to provide:
1. Online convergence platform for multiple seeding channels and a ready-made
SMS/ online resident self-service channel for the States usage.
2. Controlled access for department operators to verify seeding by comparing
beneficiary record at the department with the UIDAI resident KYR data from
SRDH web services.
3. MIS, fine grained user access management, audit trails and data
import/export features to enable states to adopt a consistent effective and
efficient approach to multi-channel seeding.
3.2 High Level Features
The key high level features of RASF are:
1. Support multiple Seeding Input Channels
a. SMS-Based seeding
b. Online/ Web-Based seeding
c. CSV maps (SRDH compliant formats from camps/ CSCs/ third party seeders/
state SRDH etc.)
d. All seeding requests irrespective of channel would validate availability of all
mandatory inputs, reject duplicate requests and ensure validity of UID number
through Verhoeff algorithm.
2. Verification Utility
a. Plain vanilla Input Viewer
b. Service Delivery data and/ or SRDH Integrated Viewer
3. Fine grained user access management
4. Audit Trails
5. MIS Reports
a. By service domain or scheme (e.g.: PDS)
b. By Geographic area (e.g.: State or Pincode or District)
c. By User (e.g.: Seeder or Verifier or Admin etc.)
d. By any combination of above
*The RASF will utilize the same pincode master database as the enrolment client does for
geographical master data such as states/ districts/ pincodes/ vtc etc.
*RASF will use HTTPS during data transfer as well as use captcha, OTP and
username/password based access control other than auditing all transactions in order to
appropriately handle security considerations.
3.3 Users and Roles
Fine grained access control is expected to be available wherein access can be restricted by
any combination of (a) application feature, (b) geographic area data constraint (state), (c)
service/ scheme domain (PDS/ MNREGA/ JSY etc.) and (d) read/ write access.
UIDAI – RASF – Introduction Document
Copyrights © 2012. All rights reserved. Page 16 of 19
Five primary types of users are envisaged for the RASF application framework, namely
RASF administrator, State administrators, Seeders, Residents and Verifiers. A brief
overview of the typical user types is as below:
3.3.1 RASF Administrator
The RASF administrator at UIDAI can
1. Create/ Modify/ Delete
a. State Administrators (restricted by State)
b. New service domains (Department-Scheme Master)
2. Generate MIS reports
3. Add/ Remove the State SRDH web service integration detail
3.3.2 State Administrators
The State administrator is typically from the State nodal agency and is the administrator for
the State and can
1. Create/ Modify/ Delete
a. Department Administrators (restricted by Department)
2. Generate MIS reports (for the particular State only)
3.3.3 Department Administrators
The Department administrator is typically from any department in the state and is the
administrator for the Department and can
1. Create/ Modify/ Delete
a. Seeders (can be restricted by service domains and geographical areas)
b. Verifiers (can be restricted by service domains)
2. Upload Department KYR data as CSV
3. Generate MIS reports (for the particular Department only)
3.3.4 Seeders
Seeders are approved for access by the Department administrator and can
1. Upload seeding records in single mode through SMS and Online channels
2. Upload seeding records in batch mode through Excel upload channel
3.3.5 Verifiers
Verifiers are approved for access by the Department administrator and can
1. Accept or reject seeding requests from residents and seeders.
2. See MIS reports of their own usage
3.3.6 Residents
Residents can access RASF only after OTP (one time password) authentication and can
place their KYR+ seeding requests either through the SMS or Online channels only.
UIDAI – RASF – Introduction Document
Copyrights © 2012. All rights reserved. Page 17 of 19
3.4 Business Architecture &Process Flow
RASF is to be hosted at UIDAI. The deployment overview of RASF is as shown below:
The primary process flow as expected for RASF is shown below:
UIDAI – RASF – Introduction Document
Copyrights © 2012. All rights reserved. Page 18 of 19
Some of the key points to note corresponding to the process flow as shown above are:
1. The RASF admin is from UIDAI and primarily creates the State administrators (step
1) and the master data (step 2). Other than these two activities, UIDAI uses RASF
only for MIS reports. RASF is managed and used by the State administrators
and other users.
2. States can onboard third party seeders (step 4) to conduct camps/ door to door
campaigns etc. The seeders can then upload seeding requests to RASF. This is
similar to registrars using enrolment agencies for Aadhaar enrolments.
3. SRDH enables verifiers to view UID KYR record for a given seeding request. SRDH
is typically deployed at the State and not by UIDAI. Hence it is the State
administrators’ responsibility to provide the web service details of SRDH as
configuration details to the RASF administrator. Note that SRDH is not necessary
(i.e. verification screen will work without SRDH; this is allowed since verifier might
have access to UID KYR data through some other application outside RASF) but is
highly recommended.
4. A seeding request can come from any channel and consists of a mapping of
Aadhaar number and beneficiary ID (steps 5a or 5b). Seeding requests can be in
single mode (SMS or online request) or batch mode (CSV upload by seeder).
RASF will have pre-determined CSV input format which will be aligned with the
SRDH manual and batch seeding CSV formats. This enables the SRDH user at
the State to upload the CSV to RASF for verification as a seeder.
5. RASF will also highlight to the seeder at the time of seeding request itself (steps
5a and 5b) if one or more of the requests are already accepted valid seeding
from other requests. This requires that RASF always stores the basic request map
even after acceptance by verifiers.
6. Verifiers can compare the UID KYR record to the department KYR record for
verification. Note that SRDH view is available within RASF if the web service is
configured by state admin. It is also possible that the verifier uses SRDH outside
RASF. Similarly the department KYR view is available within RASF if the department
admin has uploaded the department data as CSV. It is again possible that the
verifier uses some other application outside RASF to access and view
department KYR records.
7. Note that after verification, verifiers can export the valid accepted maps as CSV. This
ensures that RASF requires no integration to various service delivery
databases.
8. It is recommended that verifiers are from the service departments (or trusted
third parties chosen by the respective departments) since this creates ownership
of the seeding.
9. It needs to be noted that most of the current challenges faced by seeding initiatives
can be overcome by careful choice of seeding channels. However each seeding
channel has its own pros and cons. For example departmental data in local language
data is a significant issue in inorganic seeding but however is not a hurdle for organic
seeding where the verifier is competent in the local language.
10. UIDAI provides RASF only as an enabling tool for seeding efforts and it is not meant
to replace any existing or envisaged efforts. UIDAI intends to improve RASF and
provide iterations in the near future.
UIDAI – RASF – Introduction Document
Copyrights © 2012. All rights reserved. Page 19 of 19
3.5 Conclusion
A multi-channel convergence approach to seeding can help overcome current
challenges and importantly scale seeding efforts significantly where each channels’
weakness is compensated by usage of other channels. Further since seeding inherently
requires manual comparison of data is most cases, it is important to enable a large
number of verifiers in the ecosystem to be able to work in a coordinated fashion to
effectively scale operations. RASF aims to provide a consistent process oriented
approach to large scale multichannel seeding and hopes to expedite Aadhaar seeding
across the nation.

AAdhar Challenges in Seeding

It is important to understand the common challenges in seeding so that appropriate
approach can be planned and necessary guidelines and processes be put in place. It is
important to note that the challenges being described in this section cover the overall picture
comprising of various service delivery databases across many states as well as multiple
seeding initiatives using varied channels being undertaken and so some of those are generic
while others are specific to a particular channel. Below are the some of the challenges that
seeding initiatives have been faced with:

1. Quality& Availability of Beneficiary data in Service Delivery databases:
Beneficiary databases have multiple data quality issues. Some of the most common
data quality issues are: errors in the data such as misspelt names/ wrong date of
births, out of date addresses etc. Beneficiary databases are yet to be digitized in
some cases, are distributed across multiple sources (such as district-wise etc.) with
duplication within and across sources, missing fields of KYR or photo data which is
very often because the particular service scheme does not mandate those fields etc.
 
2. Quality of UIDAI Enrolment KYR Data: Considerable improvements in the quality of
the master pincode database (address master which the enrolment client uses),
multiple versions of the enrolment client with improved features to ensure data quality
and transliteration have evolved since enrolments began. This has resulted in
significantly improved quality of enrolment KYR data in later phases of enrolments. In
earlier enrolments however there are cases of misspelt district names, wrongly
mapped pincode to VTC, redundant address fields, poor transliteration etc. Many
seeding initiatives currently are focused on geographic areas where high percentage
of enrolments have been done which naturally uses early enrolment data (early
enrolments = higher percentage of enrolments).
 
3. Availability of UIDAI Enrolment KYR Data: Availability of the UIDAI KYR resident
database (SRDH or equivalent) is critical to seeding initiatives especially for the
inorganic seeding channels and is also critical for verification of seeding irrespective
of channel. Currently very few States have a production quality (accessibility &
performance) resident KYR database with most available enrolment KYR data
available.
 
4. Quality& Availability of UIDAI Enrolment KYR+ Data: KYR+ data is not collected
in all States and among States that do collect KYR+ fields, different States collect
different sets of fields. In all cases, KYR+ data fields are optional during enrolments.
Even in States where KYR+ data is collected, very often residents have opted not to
provide the information and when provided the data is often found unreliable
(erroneous).
 
5. Language of Beneficiary data in Service Delivery databases: Many service
delivery databases in States are in the local language. However the software tools
that compare the SRDH KYR data to beneficiary KYR data are usable only for
English data.
 
6. Mobilization of Residents: Many organic seeding channels require the mobilization
of residents. Mobilization of residents is difficult, tedious and causes inconvenience
to residents.
 
7. Software & Hardware Infrastructure: Large scale seeding initiatives across multiple
service delivery databases is the need of the hour to expedite Aadhaar enabled
service delivery. This requires fairly significant hardware and scalable high
performing software. Most importantly it requires easy to use tools and availability of
UIDAI – RASF – Introduction Document
Copyrights © 2012. All rights reserved. Page 12 of 19
the data through the software for both seeding and seeding verification efforts in the
field to multiple stakeholders.
 
8. Change Management: One of the most significant hurdles in seeding initiatives
currently is many misunderstandings around the concept of seeding and lack of
clarity in the way forward. Some of the common clichés include:
• “Tool ‘X’ does 65% seeding, how much does tool ‘Y’ do?”
– Comparisons between tools is valid only if both tool ‘X’ and ‘Y’ is being used
on
- Same set of UIDAI KYR data (because % seedable is a factor of
availability)
- Same department data (because % seedable is a factor of
quality/quantity of department data which varies state to state and
among departments in state)
• “Accuracy cannot be guaranteed by seeding algorithm ‘X’”
– Accuracy cannot be guaranteed by any seeding algorithm. Our recommended
strategy is to bring Aadhaar numbers into department data marking them as
unverified and putting in place appropriate process to verify through operators
or at transaction point with beneficiary.
– This additionally allows resident to check Aadhaar KYR data and update at
CIDR if necessary (using update channels). If resident verifies seeding and
confirms Aadhaar data correctness, department can over-ride existing
department KYR data (cleaning)
• “Residence presence is required for seeding verification, so algorithmic seeding is
useless”
– Mobilizing residents for seeding is not an easy exercise (note KYR+ collection
success/ failure where mobilization was due to enrolment)
– Is 100% accuracy of seeding a must? Answer should depend on particular
transaction with department for a given scheme. 80% seeding with 1% errors
vs. 20% seeding with 0.1% errors argument.
– Resident presence just for seeding might not be resident-centric, should at
least be for all departments in one visit
– Resident presence although helpful is not necessary. Resident self-service
channels such as SMS and Online portal can be leveraged.
• “So how many duplicates/ bogus records have seeding removed?”
– It should be noted that only when Aadhaar is mandated for a scheme within a
geographical area can there be removal of duplicates/ bogus etc. If a
database has beneficiary records without Aadhaar numbers, there could be
duplicates among themselves or a duplicate of a record with Aadhaar
number. They could also be bogus records. Seeding searches can indicate
duplicates but department will have to reach out and check before removing
• “We should be using bio-auth to ensure seeding accuracy”
– Bio-auth can only tie the Aadhaar number to the person. Seeding is trying to
tie the Aadhaar record to the department record. You could very well tie an
authenticated Aadhaar record to the wrong department record (where KYR
data looks similar).

Channels for Seeding & KYR Plus

Seeding initiatives could be of many types referred to here as ‘channels’ which provide the
source of seeding such as KYR+, SMS or Online based resident/ assisted self-seeding,
manual seeding at point of service, algorithmic seeding etc. Below is a brief overview of the
most prevalent channels:

KYR Plus
Many States have collected various other IDs (such as passport number, PAN number,
Voter ID, Ration Card number etc.) along with the Aadhaar enrollment data. This data is
collectively known as KYR+. Hence at enrolment, few other IDs are already mapped to EIDs.
With the EID-UID map and KYR data available in the State resident database, seeding of the
service delivery database using the EID to beneficiary ID available in KYR+ can be used.
It is important to note in this context that
 not all States collect any KYR+ IDs,
 different States collect different IDs as part of KYR+,
 where collected, it is optional and most residents have not provided the data
 And finally very often the quality of KYR+ data collected is found to be unreliable

AAdhar Seeding Concept

Aadhaar seeding is a process by which UIDs of residents are included in the service delivery
database of service providers for enabling Aadhaar based authentication during service
delivery, linking of UID to beneficiary ID.
As an example, MNREGA will require authentication before payout therefore in such a
scenario, it will be essential to map UID of the resident with MNREGA Job Card number and
other demographic information. Similarly, banks and insurance carriers may want to map
Aadhaar numbers of all their customers. The objective is not to replace the currently used
unique identifier of the customers/ residents/ beneficiaries with Aadhaar but the objective is
to seamlessly enable Aadhaar authentication without impacting any other interface that the
service providers maintain with their customers.
Aadhaar enrolment involves collection of basic demographic details (called Know Your
Resident (KYR) data) along with biometrics and photograph and generation of EID
(Enrollment ID) which is a transaction reference number. After due processing, UIDAI
generated UID numbers for enrollments that are accepted (based on de-duplication and
quality). The KYR data and photo along with EID and UID numbers are published by UIDAI
back to the registrars as EID-UID XML files.

Aadhaar Enabled Service Delivery

Aadhaar aims to provide an identity infrastructure for delivery of various social welfare
programs and for effective targeting of these services. While welfare is the prime focus of
Aadhaar, it can also be utilized by other enterprises and service providers such as banks,
telcos and others for improving their service delivery.
Applications that use Aadhaar authentication to identify and authenticate the resident as part
of their service delivery are referred to as Aadhaar-enabled applications. The usage of
Aadhaar enabled applications for service delivery is broadly referred to here as “Aadhaar
Enabled Service Delivery”.
Government to Citizen (G2C) Service delivery is currently carried out independently for
various schemes by government departments and in most cases, the required data,
systems, processes and infrastructure is all owned and managed by the departments as
separate initiatives. In the recent past, consolidation at various levels with a view of providing
more effective and efficient resident-friendly service delivery has taken place. For example
there has been consolidation of the service delivery front end (primarily through citizen
service centers).

Aadhaar in service delivery is primarily aimed at revolutionizing identity authentication and
also financial payments. The business architecture of such a service delivery infrastructure
can be visualized

Use of Aadhaar enabled Applications on the mobile phone

While Aadhaar-based benefits and service delivery can be made available to residents via agent-assisted kiosks, the Aadhaar secure authentication model will also enable these services to be delivered to residents directly via their mobile phones. This will ensure that residents may securely access their government benefits, track their bank accounts, send and receive money or make payments from the anytime-anywhere convenience of their mobile phones.
In the beginning these services may be largely informational – such as updates about NREGA payments or bank balances. However it is entirely conceivable for residents to be able to register for work under the NREGA scheme as well as payments of bills, micro-insurance premiums and other money transfer transactions right from their mobile phones. In the case of self-service on the resident’s mobile, security is assured using two-factor authentication (i.e. by proving possession of the resident’s registered Mobile Number and knowledge of the resident’s Aadhaar PIN). These standards are compliant with the Reserve Bank of India’s approved standards for Mobile Banking and Payments.
Version 2.0 – April 2012 Page 25
Aadhaar-based micropayments
Aadhaar, which identifies individuals uniquely on the basis of their demographic information and biometrics, gives individuals the means to clearly establish their identity to public and private agencies across the country. Aadhaar, once it is linked to a bank account, can help poor residents easily establish their identity to banking institutions. As a result, Aadhaar makes it possible for banking institutions to provide ubiquitous, low-cost micro-payments to every resident of India.
Figure 1: Account opening workflow
UIDAI will facilitate Aadhaar-based micro-payments in two phases:
1. During Aadhaar enrollment, UIDAI will collect information from the resident for the purpose of opening an Aadhaar-enabled bank account. The resident’s photograph and demographic data will be sent to a bank to actually open the account.
2. After enrollment, microATMs will be deployed by banks. These handheld devices will make it possible for residents to access their Aadhaar-enabled bank accounts for deposits, withdrawals, remittances, and balance query. The residents will authenticate themselves to the bank by using their Aadhaar number and fingerprint.
It is envisioned that each of India’s 600,000 villages will have two microATMs, as Aadhaar enrollment covers the entire country. Simultaneously,
Version 2.0 – April 2012 Page 26
microATMs will also be deployed where the urban poor reside, to bring about urban financial inclusion.
The key features of UID-enabled micropayments are as follows:
1. UID KYR sufficient for KYC: The strong authentication that the UID will offer, combined with its KYR standards, will remove the need for individual KYC (Know Your Customer) verification by banks for basic, no-frills accounts. It will thus vastly reduce the documentation the poor are required to produce for a bank account, and significantly bring down KYC costs for banks.
2. Ubiquitous BC network and BC choice: The UID’s clear authentication and verification processes will allow banks to network with village-based BCs (Business Correspondents) such as self-help groups and kirana stores. Customers will be able to withdraw money and make deposits at the local BC.
3. A high-volume, low-cost revenue approach: The UID will mitigate the high customer acquisition costs, high transaction costs and fixed IT costs that are now faced in bringing bank accounts to the poor.
4. Electronic transactions: The UID’s authentication processes will allow banks to verify poor residents both in person and remotely. More importantly, this facilitates direct transfer of benefits (eg., MNREGA wages, old age pensions) to the resident directly without the incumbent leakages of a manual disbursement system.
Thus, UIDAI will help bring about the national goal of inclusive growth.
Version 2.0 – April 2012 Page 27
Aadhaar & Civil Society Outreach
It is part of the UIDAI mandate to make special efforts to enable the inclusion of marginalized communities (e.g. the homeless, migrant workers, nomadic/denotified tribes, street children, etc.) in AADHAAR. The Registrars will be required to evolve and implement a special campaign to cover this target group. Registrars could also partner with CSOs at the local level to assist them in spreading awareness of AADHAAR among marginalized groups, in planning special enrolment drives for specific groups, and to authorize CSOs as Introducers for those without Proof of Identity and Address.
Legal Framework
The Unique Identification Authority of India has been set up as an attached office of the Planning Commission. The National Identification Authority of India Bill, 2010 proposes to establish the National Identification Authority of India, thereby giving it the status of a statutory authority established by an Act of Parliament.
Salient features of the National Identification Authority of India Bill, 2010
1. The National Identification Authority of India Bill, 2010, inter alia, seeks to provide―
i. for issue of Aadhaar numbers to every resident by the Authority on providing his demographic information and biometric information to it in such manner as may be specified by regulations;
ii. for authentication of the Aadhaar number of an Aadhaar number holder in relation to his biometric information and demographic information subject to such conditions and on payment of such fees as may be specified by regulations;
iii. for establishment of the National Identification Authority of India consisting of a Chairperson and two part-time Members.
2. The Bill has extra territorial application if the act or conduct constituting the offence or contravention involves the Central Identities Data Repository (CIDR).
3. Residents have been defined to mean individuals usually residing in a village or rural area or town or ward or demarcated area (demarcated by
Version 2.0 – April 2012 Page 28
the Registrar General of Citizen Registration) within a ward in a town or urban area in India.
4. The Aadhaar number will be a random number and once issued will not be re-assigned. It will not bear any attributes or identity data relating to the Aadhaar number holder.
5. An Aadhaar number, subject to authentication, shall be accepted as proof of identity of the Aadhaar number holder.
6. The response to authentication would be a yes or no only. No demographic information or biometric information will be given as a response.
7. Aadhaar number or the authentication thereof shall not, by itself, confer any right of or be proof of citizenship or domicile in respect of an Aadhaar number holder.
8. The Authority shall not require any individual to give information pertaining to his race, religion, caste, tribe, ethnicity, language, income or health.
9. The Authority shall take special measures to issue Aadhaar number to women, children, senior citizens, persons with disability, migrant, unskilled and un-organized workers, nomadic tribes and such other categories of individuals as may be specified by regulations.
10. The Authority has been cast with an obligation to ensure the security and confidentiality of identity information of individuals. The Authority shall take measures (including security safeguards) to ensure that the information in the possession or control of the Authority (including information stored in the Central Identities Data Repository) is secured and protected against any loss or unauthorized access or use or unauthorized disclosure.
11. The Authority will be bound to disclose the information in pursuance of an order of the competent Court or in the interest of national security.
12. An Aadhaar number holder shall be entitled to obtain details of request for authentication of his Aadhaar number and the response provided on the request by the Authority in the manner as may be specified by regulations.
13. The Bill provides for the powers which can be exercised by the Authority and also certain functions which can be discharged by it. These, inter alia, include―
i. Specifying the demographic information and biometric information for enrolment for an Aadhaar number and the processes for collection and verification thereof.
Version 2.0 – April 2012 Page 29
ii. Collecting demographic information and biometric information from any individual seeking an Aadhaar number in such manner as may be specified by regulations.
iii. Appointing of one or more entities to operate the Central Identities Data Repository;
iv. Maintaining and updating the information of individuals in the Central Identities Data Repository in such manner as may be specified by regulations.
v. Specify the usage and applicability of the Aadhaar number for delivery of various benefits and services as may be provided by regulations.
vi. Setting up facilitation centers and grievance redressal mechanisms for redressal of grievances of the residents, Registrars, enrolling agencies and other service providers.
vii. Enter into Memorandum of Understanding or agreements with Central Government, State Government or Union Territories or other agencies for the purpose of performing any of the functions in relations to collecting, storing, securing or processing of information or performing authentication.
14. The Bill also provides for offences and penalties for contravention of the provisions of the legislation. Penalties have been, inter alia, specified for-
i. Impersonation at the time of enrolment by providing any false demographic information or biometric information.
ii. Impersonating or attempting to impersonate another person with the intention of causing harm or mischief to an Aadhaar number holder or with the intention of appropriating the identity of Aadhaar number holder by changing or attempting to change any demographic information or biometric information.
iii. Unauthorized collection of identity information.
iv. Disclosing identity information collected in the course of enrollment or authentication to any unauthorized person.
v. Unauthorized access to the Central Identity Data Repository (CIDR), which also includes –
 Unauthorized downloading, copying or extracting of data from CIDR,
 Introducing any virus or other computer contaminant in the CIDR,
Version 2.0 – April 2012 Page 30
 Damaging the data in CIDR, disrupting the access to CIDR,
 Denying or causing denial to access the CIDR,
 Destroying, deleting or altering any information stored in any removable storage media or CIDR,
 Stealing, concealing, destroying or altering any computer source code used by the Authority with an intention to cause damage.
vi. Tampering with data in CIDR or in any removable storage medium with the intent of modifying information relating to Aadhaar number holder or discovering any information thereof.
vii. Attempting to give false biometric information for getting an Aadhaar number or updating the information.
Information, Education and Communication
Information, Education and Communication (IEC) is an important process in developing and executing the communication strategy for the enrolment and Aadhaar enabled services. The main communication objectives of the UIDAI are as follows:
1. Complete Coverage: Ensure communication reaches each resident of India.
2. Understanding Aadhaar: Ensure all residents understand what Aadhaar is, what benefits it can provide to people and how it will be used going ahead.
3. Understanding the Aadhaar process: Ensure residents understand Aadhaar enrolment process, how and when they can get their Aadhaar and know the grievance handling mechanism.
4. Uniform Understanding: Ensure the above understanding is uniform across residents.
5. Sustain Demand: Reassure the first few experiences on usage of Aadhaar and amplify on positive experiences to further create and sustain demand on a regular basis.
The Registrar, along with the UIDAI Regional Offices and Headquarters are required to disseminate information regarding Aadhaar so that benefits of governmental and other schemes reach the intended beneficiaries.
To ensure comprehensive coverage across all the residents, the message of Aadhaar shall be spread through the following communication channels:
i. Broadcast & Telecast: TV, radio, print, internet
Version 2.0 – April 2012 Page 31
ii. Information: News and publications
iii. Outdoors: Posters, handouts, wall paintings, banners, hoardings
iv. Entertainment: Cinema, sports, endorsements
v. Inter-personal: Audio/video screening, telecom, folk and traditional media
Before undertaking the production and dissemination of creative elements the UIDAI ROs in collaboration with the Registrars prepare IEC plans to be implemented. UIDAI provides all the support and guidance to the Registrars for the activities pertaining to core messaging of Aadhaar - its features and benefits.

List of approved 18 States/UTs - for Enrolments by UIDAI’s Non-RGI Registrars

Sl.No. States/UTs
1
ANDHRA PRADESH
2
CHANDIGARH
3
DAMAN & DIU
4
GOA
5
GUJARAT
6
HARYANA
7
HIMACHAL PRADESH
8
JHARKHAND
9
KARNATAKA
10
KERALA
11
MADHYA PRADESH
12
MAHARASHTRA
13
NCT OF DELHI
14
PUDUCHERRY
15
PUNJAB
16
RAJASTHAN
17
SIKKIM
18
TRIPURA

Data Updation Process

The UIDAI has defined broad guidelines at this stage for the updation of demographic and biometric data collected during enrolment, which are as follows:
1. Demographic data updations will be required if there was an error in enrolment or when a resident changes his address / name etc. Biometric data updation will be required for children, and other residents in case of accidents / other loss.
2. The data updation process for demographic data will be a simple process involving document verification standards defined for the enrolment process. Biometric data will also be updated using the same devices and process used for enrolment.
3. Registrars need to maintain atleast a skeletal enrolment network in their respective locations, after the ‘enrolment sweeps’ are completed to facilitate ongoing updation of their databases. Long term/Permanent enrolment stations need to be established by the Registrar at Taluk/Block/Municipality level, so that the residents can continue to enroll even if they have missed the first opportunity. These could be touch points for the residents in case they want to get their data updated.
Details of charges along with further guidelines on the process will be defined by the UIDAI, when this process commences.
Monitoring & Audits
A strong monitoring and audit process is critical to drive rigor in the execution of the processes defined above. Keeping in mind the need to have consistent and standardized implementation, the monitoring & audit process will serve as a control mechanism for the UIDAI and Registrars to deliver on the same.
A twofold process is envisaged at this stage:
Version 2.0 – April 2012 Page 20
1. MIS Analytics & Exception Reports: the UIDAI will generate a set of standard reports for daily / weekly / monthly monitoring of process performance. Additionally, a set of exception reports will be generated for fraud detection, to flag performance issues etc. Registrars can review the list of standard reports on offer and add/modify to the list.
2. Audits: in addition to MIS based monitoring, the UIDAI will conduct sample audits in the entire gamut of enrolment, training, logistics, grievance resolution and updation processes for controllership purposes. It is recommended that Registrars setup a similar process to audit the performance of Enrolment Agencies and other partners they engage with.
As a part of strategy review, it has been decided that demographic and other errors like biometric mix up, process violations would invite Penalties which would be deducted from the amount payable to the Registrar every month. UIDAI will share details with the Registrars who will be required to make detailed enquiries and take follow up action since they have contractual agreements with the enrolment agencies for error free data.

Query and Grievance Handling

The UIDAI has setup a Contact Centre to manage all queries and grievances and serve as a single point of contact for the organization. 1. The key stakeholders serviced by the Contact Center are Residents, Registrars, Enrollment Agencies, Authentication User Agencies and Authentication Service Agencies. 2. The Channels of Communication are Phone: Toll Free 1800 180 1947. 7AM to 11 PM. Monday to Saturday. (Currently not available on Sundays & National Holidays) Letter: PO Box 1947, Bangalore 560 001 Fax: 080-2353 1947 E-Mail: help@uidai.gov.in Languages Supported: Hindi, Kannada, Marathi, English, Telugu, Bengali, Tamil, Punjabi and Malayalam. 3. There are two operational sites of contact center one in Bangalore and the other one in Karnal. 4. Any resident seeking enrollment is given a printed acknowledgement form with an ENROLMENT NUMBER, that enables the resident to make queries about her/his enrolment status through any communication channel of the contact centre. 5. The Contact Centre services Enrolment Agencies/Operators on basic technical queries through a Technical Helpdesk only in English and Hindi language. 6. The Registrar is expected to put in place a Team that would serve to quickly address any matters requiring resolution that may pertain to the Registrar, but may be conveyed to the UIDAI Contact Centre. 7. Queries / grievances which need Registrar/Enrolment agency involvement will be transferred to the Registrar appointed Nodal officer through web link http://110.234.122.102/aadhar/ui/loginpage.aspx. (For login credentials e-mail may be sent to arajhansuidai@gmail.com or
Version 2.0 – April 2012 Page 19
amitar@sparshindia.com.) The Time taken for resolutions to be resolved

Aadhaar Generation

This is an automated process run by the CIDR and is described below for reference:
1. Once CIDR receives the enrolment data, it carries out the necessary quality and validation checks & readies for de-duplication.
2. CIDR will run the de-duplication algorithm to match the details of a resident enrolment request with existing entries in the database. Biometric data in the enrolment record i.e., finger and iris prints will be used for the same to ensure uniqueness.
3. If no match is found, Aadhaar no. is issued and letter generated for the same. If duplicate is found, a rejection Letter is generated to inform the resident that a duplicate record exists. If process/data errors are identified, rejection letter is generated and the resident is asked to re-enrol.
4. Details of the final status on each of the Enrolment Nos. will be shared electronically with respective Registrars and Enrolment Agencies periodically.
Last Mile Logistics
This process refers to the Communication of the Aadhaar Number to the Resident by means of a letter:
1. All successful enrolments are communicated through a Letter to each resident, delivered utilizing the Speed Post Service of India Post. UIDAI may also launch a web based Aadhaar letter facility subject to technical and security considerations.
2. Rejections to the enrolment process are also communicated through a Rejection Letter.
Version 2.0 – April 2012 Page 18
3. Undelivered letters are returned to the UIDAI. The resident may request for a letter at a later date by making a request to the Contact Centre.
4. Residents can also check their Aadhaar status directly at website http://www.uidai.gov.in/ using their Enrolment Numbers.

Aadhar Card Data Capture

The Go-live readiness workshop should have been completed and all requirements verified as met, before a Registrar proceeds to this step.
After an enrolment centre is ready, Enrolment Agencies can begin the process of capturing residents’ demographic and biometric data as follows:
1. Capture demographic data :
a. Aadhaar Enrolment/Correction form (containing KYR fields) and Registrar’s KYR+ form (if applicable) is filled by the resident. The data can also be extracted from a pre-filled database. Filling Aadhaar Enrolment/Correction form is mandatory and will be required - even in case of prefilled data.
b. Verify the identity and address of the resident as per defined standards. The verification methods are basis :
i. Document based verification – where the Proof of Identity / Address/Date of Birth/ Relationship documents are verified by the Registrar’s representative
ii. Introducer based – where Introducers authorized by the Registrar, authenticate the identity and address of the resident
iii. Head of Family based – where Head of Family endorses family members based on Proof of Relationship Documents.
Version 2.0 – April 2012 Page 16
c. The Operator must check Resident’s consent for Information sharing and Aadhaar enabled Banking services and record the same.
2. Once demographic data is captured, the operator will proceed to collect biometric data :
a. Exceptions if any (missing finger / eye for eg.,) are recorded as per guidelines detailed in the Enrolment Process Manual
b. Facial Image, Iris and Fingerprints are captured
3. Ask resident to verify if the demographic and biometric data displayed on the screen are accurate; print consent letter and issue acknowledgment once resident confirms accuracy.
4. EA then exports data and transfers to the UIDAI either by uploading the data packets using online sftp mode or by sending the hard disk/memory stick to UIDAI. UIDAI shall soon be discontinuing the practice of receiving data through hard disks and all data must be uploaded through SFTP.
5. File the documents for storage with the Registrar and UIDAI Document Management System (DMS). Instantaneous scanning of resident documents at enrolment centers and integration with their data packets will become mandatory from October 2012.
First Mile Logistics
This process refers to the transfer of digitized enrolment data from the enrolment station to the UIDAI’s Central ID Repository (CIDR)
The Registrar has two options for transferring enrolment data to the CIDR:
1. by directly uploading data to CIDR - using Aadhaar sftp client.
2. via memory sticks/hard disks sent through suitable courier service.
Data must be uploaded to CIDR within 20 days of enrolment.
Monitoring Data Transfer & Recovery of Lost Data: It is expected that each Laptop being used for enrolment will connect to the internet periodically to synch stations with CIDR (Central Identification Data Repository). To enable this, availability of a data stick is mandated.
a. Synching stations informs CIDR in advance, what data to expect.
b. For the data records successfully received at CIDR, the process for deletion of such data residing at the enrolment station is triggered automatically.
Version 2.0 – April 2012 Page 17
c. In cases where there is a problem with data records received from this enrolment station, a fresh instruction for EXPORTING this data again is generated automatically.
Hence this connectivity, at periodic intervals, is vital to ensure proper housekeeping and management of the data transfer process.
Station Sync must be ensured at least once in ten days.

Enrolment Process Of Aadhar Card

Setup & Preparation
In order to start enrolments, the Registrar has to complete the following activities, many of which can run in parallel and would have commenced post the Project Initiation Workshop:
1. Enrolment Planning – As a part of the Enrolment Planning workshop, the Registrar is advised to finalize the targeted enrolment nos., locations to be covered and timelines for the same. This data can in turn be used to plan the no. of Enrolment Stations needed, locations for the same, devices needed, operators to be staffed etc. It is strongly recommended that the Registrar enroll all residents of the locality and not limit it to their beneficiaries/ customers. ‘Sweeping’ all residents will give Registrars the benefits of economies of scale and optimizing on the cost of enrolment per resident. However, the Registrars can identify districts, in a phased manner, for the launch of Aadhaar enabled services and focus on enrolment sweep in these districts rather than spreading the entire effort thinly across the State/UT.
2. Define KYR+ fields if any are to be collected and initiate technology integration with respect to data capture API and logistics. Also finalize if pre-enrolment data from existing databases are to be used during enrolment. The Aadhaar Application Software for enrolment should be ready for deployment. See Annexure for details of the Enrolment Software.
3. Identify Enrolment Agencies – Registrars can consider using only agencies from the list empanelled by the UIDAI or they may identify through other sources. If Non-Empanelled Agencies are used, UIDAI strongly advises that these agencies be subject to same terms and conditions of work which apply to the empanelled agencies.
4. Subcontracting has serious impact on the quality and security of data. Agreement with enrolment agencies should have conditions to discourage sub-contracting. Model RFP/Q templates and the list of empanelled agencies have been published on the UIDAI portal.
5. Detailed station deployment plan needs to be uploaded by Enrolment Agency and approved by the Registrar using an online mechanism
Version 2.0 – April 2012 Page 14
developed by UIDAI. Online appointment scheduling should be encouraged for better crowd management at the centers.
6. Procure infrastructure and equipment including biometric devices as per standards defined by the UIDAI for setting up an enrolment centre through the designated enrolment agencies.
7. It is recommended that the Registrar must insist on Enrolment agencies using only Operators/Supervisors who have been trained, certified and their Aadhaar numbers have been generated. Operators/Supervisors may be trained using the modules / agencies that the UIDAI has empanelled for Enrolment Operator training; alternatively, the Registrar can ask operators to cover the modules in ‘self-study’ mode and appear for the test directly. All Enrolment Operators need to be tested and certified, keeping in mind the significant impact they have in collecting good quality and accurate data from residents. See Annexure for details of the Training modules.
8. Registrars must Review Pin Codes in Aadhaar Client Master Data and get Pin Code information corrected and completed prior to starting enrolments in their area.
9. Print and distribute Aadhaar Enrolment/Correction Forms. Registrars can have a separate form for capturing KYR+ data.
10. Define an integrated Information, Education & Communication Plan & Material leveraging the content developed by the UIDAI. The UIDAI’s IEC guidelines list in detail the different kinds of stakeholders to engage (PRI members, introducers, influencers etc.) and the recommended messages and media to use for each of them. The IEC plan lists the activities to be triggered 45/30/15/ 7 days before commencing enrolments. See Annexure for details.
11. Registrar should also identify an Officer to whom all relevant grievances may be forwarded; and two senior officers for managing escalations of the same. The Joint Working Subgroup should also develop probable queries / grievances that can come from the beneficiaries & correct responses for them; finalize the process & turnaround time for responding to the queries/grievances.
12. Before enrolments start, Registrars will need to identify Introducers who can help enroll beneficiaries who lack PoA/PoI documents. They can also leverage CSOs to better reach marginalized residents, act as Introducers,
Version 2.0 – April 2012 Page 15
and build awareness among them to mobilize enrolments from this group.
13. Identify Verifiers and ensure their presence at the enrolment centre during the operational hours of the centre for verifying resident’s documents.
14. Finally if Financial Inclusion solution will be a part of the enrolment process, then work with the UIDAI to identify Banks to partner with; define processes as required to implement the Financial Inclusion solution.
15. Review the Enrolment Centre Setup checklist and verify if all required activities are completed.

Guidelines for Financial Assistance of Aadhar

1. In order to reduce the financial burden of implementing Aadhaar, the Authority has been provided funds by the Central Government to assist the Registrars. To operationalise this arrangement, the States will have to provide the Authority, with details of the Registrar (name and account) through which they would like to receive the assistance.
2. Assistance will also be provided to develop ICT infrastructure; specifically for integrating existing software applications of partner agencies, procurement of hardware and software, engaging consultants / resource persons to advise partner agencies , engaging software agencies, developing cloud applications at the national level for the large scale social sector schemes and providing integration support. Details of the program are available on our website.
3. Identify Enrolment Agencies – Registrars can consider using only agencies from the list empanelled by the UIDAI or they may identify through other sources. If Non-Empanelled Agencies are used, UIDAI strongly advises that these agencies be subject to same terms and conditions of work which apply to the empanelled agencies.
4. Subcontracting has serious impact on the quality and security of data. Agreement with enrolment agencies should have conditions to discourage sub-contracting. Model RFP/Q templates and the list of empanelled agencies have been published on the UIDAI portal.
5. Detailed station deployment plan needs to be uploaded by Enrolment Agency and approved by the Registrar using an online mechanism

Key Policy Highlights

The following is a brief extract of the policy guidelines pertaining to Registrars:
1. The Registrar is a partner of the UIDAI in the implementation of the UID project.
2. The Registrar is under an obligation to enroll residents following the protocols, standards, process and guidelines laid down by the UIDAI.
3. The Registrar is required to ensure the security and accuracy of data (particularly biometric data) collected from residents.
Version 2.0 – April 2012 Page 11
4. Registrars may retain the biometric data collected from residents enrolled by them, if they have clearly articulated strategy for safe custody and utilization of these enrolment packets. The Registrar will have to exercise a fiduciary duty of care with respect to the data collected from residents and shall bear liability for any loss, unauthorized access to and misuse of data in their custody.
5. In order to ensure data integrity and security, the biometrics captured shall be encrypted upon collection by using the encryption key defined by the Registrar. The UIDAI has defined security guidelines for the storage of biometric data in order to give some guidance to the Registrar. The Registrar shall have to define their own security policy and protocols to ensure safety of the Biometric data. In the interest of transparency, it is recommended that the Registrar inform the resident that they will be keeping the biometric data and also define how the data will be used and how it will be kept secure.
6. The Registrars must retain the Aadhaar Enrolment/Correction Form, copy of Proof of Identity / Address/Date of Birth/Relationship and Consent for enrolment documents in proper custody till the time they are handed over to the UIDAI appointed agency for document management.
7. In case of disputes with respect to enrolment of residents, the Registrar is required to co-operate with UIDAI in resolving the matter and shall provide access to necessary background documents and other matters of evidence necessary to resolve the dispute.
8. The Registrar is required to support the UIDAI in conducting audits and checks on the enrolment process and follow the directions of the UIDAI in order to make the system compliant with the UIDAI enrolment framework.
9. NSR will keep UIDAI Regional Office (RO) informed of enrolments within their own premises. Engagement in enrolment activities proposed outside their own premises in any particular State will be approved by the State level UIDIC.
10. Registrars need to define a ‘data updation’ process in order to keep the resident data accurate and complete in their respective databases.
See Annexure for details of the Legal Framework governing Aadhaar.

Becoming Aadhaar Ready

The Registrar On-boarding Process
1. Identify Nodal Department for Aadhaar; set up Apex/empowered committee headed by CM and implementation committee (UIDIC) headed by Chief Secretary; sign MoU. Any Non-State Registrar (NSR) desirous of undertaking enrolments in a particular State/UT will also be co-opted in UIDIC by the UIDAI Regional Office.
2. Identify Departments which will act as Registrars along with a nodal Officer. Other Departments which are not included as Registrars in the project at the time of enrolment, will have the option of ‘Aadhaar enabling’ their systems at a later date
3. Identify Agency for Receiving financial assistance for enrolment: The Authority will financially support its Registrars for successful Aadhaar number generation. To operationalise this arrangement, the States will have to provide the Authority, details of the Registrar (name and account details) through which they would like to receive the amount.
4. Setup Joint Working Group – headed by the Head of the Nodal Dept/Registrar. The other members should be the Nodal Officers, & members who can lead the Technology, Process, IEC, applications teams from the Registrar’s side. UIDAI will nominate appropriate representatives to assist the State Government/Registrars in carrying through the entire process. Bank representatives may be included where the Financial Inclusion (FI) solution is a part of enrolment.
5. A Project Initiation Workshop will mark the commencement of the project and include an overview of Aadhaar for the benefit of new entrants into the team, outline the Enrolment and IEC Implementation approach and plan (how and what needs to be done), roles & responsibilities of the Joint Working Group and the high level timelines and project plan. This must be attended by members from the Implementation Committee and the Joint Working Group. See Annexure for details of Roles & Responsibilities.
Version 2.0 – April 2012 Page 10
6. A sensitization training cum workshop can be setup in parallel for members of the Registrar’s organization who need to be aware of the project/plans etc. It is recommended that similar sensitization sessions be organized by the Registrar Department for key functionaries of the district / village level governing bodies and other influencers who can contribute to the success of this project.
7. This will be followed by a Workshop to define the Enrolment Strategy and detail the process and technical integration required to start enrolments. This will include the Enrolment Plan, no. of districts and residents to be covered per month and therefore the infrastructure and other requirements to meet the same. This is expected to be attended by the Joint Working Group with optional participation from the Implementation Committee.
8. This will be followed by a set of sub-group workshops and meetings with members of the process, technology, IEC and applications teams respectively to identify the key areas of integration and implement the same.
9. The Registrars are expected to give special attention to Social Inclusion. Define the role of Civil Society Organizations (CSOs) in the enrolment process and develop a panel of CSOs at the local level who can help enrol marginalized communities.
10. A Go Live readiness Workshop will be scheduled 2-3 weeks before scheduled ‘go-live’ date to take stock of the implementation status on items required to start enrolments.

How will Aadhaar be built

Aadhaar will be built in partnership with Registrars. Registrars will collect demographic & biometric data from residents directly or through Enrolment Agencies. Aadhaar will be issued by the UIDAI to residents after de-duplication of data.
Financial support will also be provided for Registrars to operationalise this program as per approval of the Government of India from time to time. The
IssuesOfflineOnlineAddresses duplicate recordsInformationResides in “smartcard”Resides in “virtual card”Business applicationResides in each deviceResides onlinein the backend cloudDevice typeComplex, expensiveSimple, inexpensiveCost &lifecycle managementHighLowFlexibility to add applicationsDifficultEasyInteroperable /choice Real-timeFraud detection and analyticsDifficultEasyAny Device (Incl. mobile) Can workwithout connectivity
Version 2.0 – April 2012 Page 8
Government had initially approved 20 crore enrolments in pilot phase till March 2012. Another 40 crore enrolments across 18 States/ UTs have been approved (Refer Annexure for list of States/ UTs). These enrolments are to be done by UIDAI’s non- RGI Registrars over the next 18-24 months starting April 2012.
What is the Aadhaar Ecosystem?
The UIDAI has identified the following partners and defined processes for Registrars to commence operations:
1. Enrolment Agencies: To enable quick on-boarding of enrolment agencies, UIDAI has empanelled enrolment agencies across all States and Union Territories. These agencies have been categorized by technical and financial strength and the list is available on our website under the ‘Registrars & Enrolments’ tab.
2. Device Certification Agency: To support Registrars in deploying the right devices for the enrolment process, UIDAI has appointed STQC (Standardization, Testing & Quality Certification) as the device certification agency. STQC will certify biometric devices (Fingerprint Scanner & Iris Camera) by make & model.
3. Training & Certification Agencies: To bring all enrolment operators to a uniform skill level, UIDAI has built standardized training content, empanelled Training Agencies that are authorized to deliver our training and appointed Sify and MeritTrac as the Testing & Certification agency.
4. Agency for Document Management: UIDAI has appointed HP for managing hard copies of resident’s documents collected during enrolment process.
5. Financial Institutions: UIDAI has signed MoUs with various Banks who will open UID Enabled Bank Accounts (UEBA). This will not only pave the way for financial inclusion of marginalized residents, but also offer significantly lower cost channels for Registrars to transfer financial benefits directly to residents. UIDAI’s approach on Financial Inclusion is in line with Financial Inclusion targets & strategy outlined by RBI & GoI.
6. The UIDAI is also working with a number of public and private sector organizations to UID-enable their application so that the residents start accruing comprehensive benefits
Version 2.0 – April 2012 Page 9
The UIDAI has also defined detailed Registrar Onboarding Process and Roles and Responsibility documents in order to support Registrars across the stages of becoming Aadhaar Ready.

Aadhaar enabled Applications

Aadhaar can be used in any system which needs to establish the identity of a resident and/or provide secure access for the resident to services/benefits offered by the system. Aadhaar can be used in the delivery of the following programs (indicative list – details in Annexure):
 Food & Nutrition – Public Distribution System, Food Security, Mid Day Meals, Integrated Child Development Scheme
 Employment – Mahatma Gandhi National Rural Employment Guarantee Scheme, Swarnajayanti Gram Swarozgar Yojana, Prime Minister’s Employment Guarantee Program
 Education – Sarva Shikhsha Abhiyaan, Right to Education
 Inclusion & Social Security – Development of Primitive Tribe Groups, Indira Gandhi National Old Age Pension Scheme, Indira Awas Yojana
 Healthcare – Rashtriya Swasthya Bima Yojana, Janashri Bima Yojana, Janani Suraksha Yojana, Aam Aadmi Bima Yojana
 Other miscellaneous purposes including Property Transactions, Voter ID, PAN Card etc.
As per its mandate, the UIDAI will actively work on defining the usage of Aadhaar nos. across applications and services, in partnership with concerned Registrars and agencies.
Integration of Aadhaar brings two primary benefits to the Registrar and agencies:
Version 2.0 – April 2012 Page 6
1. De-duplication: Since UIDAI will ensure that the same resident will not be issued two Aadhaar numbers, these numbers are truly unique and can be used to de-duplicate, integrate existing databases or create new ones.
2. Authentication: At the time of delivering a service to the resident, UIDAI recommends that the Aadhaar number is captured along with a biometric (one or more fingerprints, iris), verify online with UIDAI and deliver the service only to the valid resident. In situations where the biometric is not available or the need for authentication is not as high, demographic data along with the Aadhaar number can be verified with UIDAI, and used as a more basic verification. UIDAI does not guarantee the authenticity of the resident in this case.
Thus, Registrars who partner with the UIDAI to enroll residents, can integrate Aadhaar nos. into their programs (referred here as applications), to leverage the benefits of Aadhaar from day 1 of starting operations. These benefits will accrue as soon as enrolment starts – in the form of de-duplicating the existing databases and removing fake/ghost identities. In addition, benefits of substantially larger scale can be realized if Aadhaar number and Aadhaar based authentication is integrated into the Registrar’s existing systems to track and accurately deliver benefits to targeted residents. The monitoring of these systems by residents, community and state authorities could also be made more efficient and effective by using Aadhaar enabled online/mobile solutions.
However, State Governments need not wait to develop their customized applications before starting the enrolment process. Registrars can integrate Aadhaar –based authentication at a later date also, by re-designing their systems and processes to include the Aadhaar ID and Aadhaar based authentication.

Aadhaar Overview

Aadhaar, which means ‘foundation’ in many Indian languages, has the following Features and Benefits:
1. One Aadhaar = 1 beneficiary: Aadhaar is a unique number, and no resident can have a duplicate number since it is linked to their individual biometrics; thereby identifying fake and ghost identities which result in leakages today. Savings from eliminating duplicates and fakes through Aadhaar-based identification will enable government to expand benefits to other eligible residents
2. Portability: Aadhaar is a universal number, and agencies and services can contact the central Unique Identification database from anywhere in the country to confirm a beneficiary’s identity
3. Inclusion of those without any existing identity documents: A problem in reaching benefits to poor and marginalized residents is that they often lack the identification documents they need to receive State benefits. The ‘Introducer’ system, which has been approved for data verification for the UIDAI, will enable such residents to establish an identity
4. Electronic benefit transfers: the UID-enabled-Bank-Account network will offer a secure and low cost platform to directly remit benefits to residents without the heavy costs associated today with benefit distribution; the leakages in the current system will also be stemmed as a result
5. Aadhaar-based authentication to confirm entitlement delivered to the beneficiary: the UIDAI will offer online authentication services for agencies who wish to validate a resident’s identity; this service will enable confirmation of the entitlement actually reaching the intended beneficiary
6. Improved services through increased transparency: Clear accountability and transparent monitoring would significantly improve access and quality of entitlements to beneficiaries and the agency alike
Version 2.0 – April 2012 Page 5
7. Self-service puts residents in control: Using Aadhaar as an authentication mechanism, residents should be able to access up-to-date information about their entitlements, demand services and redress their grievances directly from their mobile phone, kiosks or other means. In the case of self-service on the resident’s mobile, security is assured using two-factor authentication (i.e. by proving possession of the resident’s registered Mobile Number and knowledge of the resident’s Aadhaar PIN). These standards are compliant with the Reserve Bank of India’s approved standards for Mobile Banking and Payments. (Please see Annexure for how mobile phone can be used for Aadhaar enabled applications)

Aadhar Card Introduction

The inability to prove identity is one of the biggest barriers preventing the poor from accessing benefits and subsidies. There is No nationally accepted, verified identity number in the country that can be used with ease and confidence by both the residents and agencies. Different service providers also often have different requirements in the documents they demand from the residents, the forms that require filling out and the information they collect on the individual. Such duplication of effort and identity silos increase the overall cost of identification and cause inconvenience to the resident. Any process that uniquely identifies a resident and ensures instant identity verification would help to reduce transaction costs, transform delivery of a host of social welfare programs and help to eliminate duplicate identities and fraud. The savings on this account can be immense and today when States are fiscally stressed, freeing up of resources would provide the desired flexibility in either extending the welfare net or increasing the benefits under the existing programs or simply improving the fiscal situation .

Keeping the above in mind, the Unique Identification number (Aadhaar) has been conceived by the Government of India as a means for residents to clearly and uniquely verify their identity anywhere in the country.
This handbook is meant to give an overview of Aadhaar, the process to generate Aadhaar numbers, use its authentication services and update it on an ongoing basis. Detailed process manuals, which are or will be available on the UIDAI website, may be referred for implementation.
Previous attempts at building ‘unique’ databases have been beset by quality issues and challenges in the lack of consistent implementation. This project therefore has defined detailed guidelines and templates for the same; especially keeping in mind that Aadhaar will be built through a network of Registrars and enrolment agencies dispersed across the country. The success of the project will be strongly determined by the quality of data collected; as such all partners may therefore keep in mind the need to adhere to these guidelines.
Version 2.0 – April 2012 Page 4
As our partners, Registrars are requested to share feedback extensively and engage with the UIDAI in making this a robust and successful exercise. The handbook and the manuals will be updated on the basis of feedback and will be posted on our website on a continuous basis.

Contact us

Contact us

If you have query then Please contact us @ mycomplaint@gmail.com 

Privacy Policy

Our Goal is to provide you with the best lists of hard to good content ….. period……. Browse around and let us know if you have any questions.


At Results of election , we recognize that privacy of your personal information is important. Here is information on what types of personal information we receive and collect when you use visit Best Martial Arts, and how we safeguard your information. We never sell your personal information to third parties.

Cookies Stuffing
We do use cookies to store information, such as your personal preferences when you visit our site. This could include only showing you a popup once in your visit, or the ability to login to some of our features, such as forums.

We also use third party advertisements on Results of election to support our site. Some of these advertisers may use technology such as cookies and web beacons when they advertise on our site, which will also send these advertisers (such as Google through the Google AdSense program) information including your IP address, your ISP , the browser you used to visit our site, and in some cases, whether you have Flash installed. This is generally used for geotargeting purposes (showing New York real estate ads to someone in New York, for example) or showing certain ads based on specific sites visited (such as showing cooking ads to someone who frequents cooking sites).

You can chose to disable or selectively turn off our cookies or third-party cookies in your browser settings, or by managing preferences in programs such as Norton Internet Security. However, this can affect how you are able to interact with our site as well as other websites. This could include the inability to login to services or programs, such as logging into forums or accounts.

About us

about us

Our Goal is to provide you with the best lists of hard to good content ….. period……. Browse around and let us know if you have any questions.


At Results of election , we recognize that privacy of your personal information is important. Here is information on what types of personal information we receive and collect when you use visit Best Martial Arts, and how we safeguard your information. We never sell your personal information to third parties.

Cookies Stuffing
We do use cookies to store information, such as your personal preferences when you visit our site. This could include only showing you a popup once in your visit, or the ability to login to some of our features, such as forums.

We also use third party advertisements on Results of election to support our site. Some of these advertisers may use technology such as cookies and web beacons when they advertise on our site, which will also send these advertisers (such as Google through the Google AdSense program) information including your IP address, your ISP , the browser you used to visit our site, and in some cases, whether you have Flash installed. This is generally used for geotargeting purposes (showing New York real estate ads to someone in New York, for example) or showing certain ads based on specific sites visited (such as showing cooking ads to someone who frequents cooking sites).

You can chose to disable or selectively turn off our cookies or third-party cookies in your browser settings, or by managing preferences in programs such as Norton Internet Security. However, this can affect how you are able to interact with our site as well as other websites. This could include the inability to login to services or programs, such as logging into forums or accounts.