FAQs

অনাবাসী ভাৰতীয়সহ ভাৰতৰ যিকোনো বাসিন্দাই (বৈধ ভাৰতীয় পাছপোৰ্ট থকা) আধাৰৰ বাবে নাম ভৰ্তি কৰিব পাৰে। যেতিয়া আবেদনকাৰীয়ে আধাৰ নামভৰ্তি প্ৰপত্ৰ এখন পূৰণ কৰে (https://uidai.gov.in/images/aadhaar_enrolment_correction_form_version_2.1.pdf), তেওঁ এই সন্দৰ্ভত স্বাক্ষৰিত ঘোষণাও দিয়ে। অনাবাসী ভাৰতীয়সকলে গ্ৰহণযোগ্য নথিপত্ৰৰ তালিকা অনুসৰি এটা পৰিচয় প্ৰমাণ আৰু ঠিকনাৰ এটা প্ৰমাণৰ সৈতে আধাৰ কেন্দ্ৰলৈ যাব লাগিব: https://uidai.gov.in/images/commdoc/valid_documents_list.pdf

• পঞ্জীয়ন কেন্দ্ৰত অপাৰেটৰৰ ভূমিকা হ’ল ইউআইডিএআইৰ নিৰ্দেশনা অনুসৰি আৱাসীৰ ডেম’গ্ৰাফিক আৰু বায়’মেট্ৰিক তথ্য গ্ৰহণ কৰা৷ আধাৰ পঞ্জীয়নত এজন অপাৰেটৰে তেওঁৰ ভূমিকা পালনৰ জৰিয়তে ‘‘পোন্ধৰটা নিৰ্দেশনা’’ পালন কৰা বুলি নিশ্চিত কৰা হয়৷
• পঞ্জীয়নৰ সময়চোৱাত আধাৰ ক্লায়েণ্টত নিজৰ অপাৰেটৰ আইডিৰে লগ ইন কৰাটো নিশ্চিত হওক আৰু আসনৰ পৰা উঠি যোৱা অৱস্থাত লগ অফ কৰক যাতে আন কোনেও আপোনাৰ আইডি ব্যৱহাৰ কৰি পঞ্জীয়ন কৰিব নোৱাৰে৷
• প্ৰতিদিনে পঞ্জীয়নৰ সময়ত জিপিএছ স্থানাংক ব্যৱহাৰ কৰক৷
• প্ৰতিবাৰ লগ ইনত যাতে কম্পিউটাৰত তাৰিখ, সময় শেহতীয়া হয় সেয়া নিশ্চিত হওক৷
• নিশ্চিত হওক যাতে অৱস্থান লে’আউট ইউআইডিএআইৰ নিৰ্দেশনা অনুসৰি হয়৷
• সকলক পঞ্জীয়ন/উন্নীতকৰণৰ পূৰ্বে পৰ্যায়সমূহ বিশদভাৱে বুজাই দিয়ক আৰু প্ৰক্ৰিয়াৰ সময়ত ক সহজ হ’বলৈ দি তথ্য গ্ৰহণৰ সুবিধা প্ৰদান কৰক৷
• ‘ফাইণ্ড আধাৰ ফেচিলিটী’ ব্যৱহাৰ কৰি নতুন পঞ্জীয়ন কৰাৰ পূৰ্বে নিশ্চিত হওক যাতে আৱাসীয়ে পূৰ্বে আধাৰত পঞ্জীকৃত হোৱা নাই৷
• পঞ্জীয়ন/উন্নীতকৰণৰ বাবে আবাসীৰ প্ৰয়োজনীয় সকলো প্ৰকৃত তথ্য থকাটো নিশ্চিত হওক আৰু যাৰ পঞ্জীয়ন/উন্নীতকৰণ কৰি আছে, তথ্যসমূহ যাতে সেই আবাসীগৰাকীৰেই হয়৷
• ভৱিষ্যতৰ যোগাযোগৰ বাবে আবাসীক তেওঁলোকৰ ম’বাইল নম্বৰ আৰু ইমেইল আইডি অন্তৰ্ভুক্ত কৰিবলৈ আৰু অন্যান্য ব্যৱহাৰসমূহ যেনে অ’টিপিযুক্ত প্ৰমাণীকৰণ আৰু অনলাইন আধাৰ সুবিধা ব্যৱহাৰ কৰিবলৈ প্ৰোৎসাহিত কৰক৷
• আবাসীৰ আধাৰ পঞ্জীয়ন/উন্নীতকৰণ পত্ৰ যাতে বৈধতাকৰণ কৰা হৈছে আৰু বৈধতাপ্ৰদানকাৰীৰ স্বাক্ষৰ/বুঢ়া আঙুলিৰ চাপ আৰু ষ্টাম্প/প্ৰাৰম্ভিক আদি যাতে মজুত থাকে সেয়া পৰীক্ষা কৰক৷ এই পত্ৰখনত আবাসীৰো(আবেদনকাৰী)স্বাক্ষৰ/বুঢ়া আঙুলিৰ চাপ থাকে৷
• আবেদনকাৰীৰ বায়’মেট্ৰিক কেৱল আধাৰ পঞ্জীয়ন/উন্নীতকৰণৰ ক্ষেত্ৰতহে ব্যৱহাৰ হৈছে, অন্য উদ্দেশ্যত হোৱা নাই সেই বিষয়ে আবেদনকাৰীক জ্ঞাত কৰাটো নিশ্চিত হওক৷
• পৰিচায়ক/এইচঅ’এফৰ পঞ্জীয়নৰ ক্ষেত্ৰত, পত্ৰখনৰ নিৰ্ধাৰিত স্থানত পৰিচায়ক/এইচঅ’এফৰ স্বাক্ষৰ/বুঢ়া আঙুলিৰ চাপৰ সৈতে বিৱৰণসমূহ থকাটো উচিত৷
• আধাৰ ক্লায়েণ্ট ছফ্টৱেৰত (ইচিএমপি/ইউচিএল) আবাসীৰ ডেম’গ্ৰাফিক আৰু বায়’মেট্ৰিক তথ্য ছফ্টৱেৰ ক্লায়েণ্টৰ স্ক্ৰীণত প্ৰদৰ্শিত অনুসৰি ক্ৰমান্বয়ে গ্ৰহণ কৰক৷
• পঞ্জীয়ন/উন্নীতকৰণৰ সময়চোৱাত যাতে আবাসীৰ স্ক্ৰীণখন সকলো সময়তে প্ৰদৰ্শিত হৈ থাকে আৰু আবাসীক সেই তথ্যসমূহ পুনৰাই পৰীক্ষা কৰি চাবলৈ তথা ডেম’গ্ৰাফিক তথ্যসমূহ ছাইন অফ কৰাৰ পূৰ্বে পুনৰাই নিৰীক্ষণ কৰিবলৈ জ্ঞাত কৰাটো নিশ্চিত হওক৷
• প্ৰাপ্তিস্বীকাৰ পত্ৰৰ ছপা আৰু স্বাক্ষৰ কৰি আবাসীক প্ৰদান কৰক আৰু পঞ্জীয়নৰ শেষত সন্মতি পত্ৰত আবাসীৰ স্বাক্ষৰ থকাটো নিশ্চিত হওক৷
• নিশ্চিত হওক যাতে পঞ্জীয়ন/উন্নীতকৰণ পত্ৰ, প্ৰকৃত সমৰ্থন তথ্য আৰু স্বাক্ষৰিত সন্মতি পত্ৰ পঞ্জীয়ন/উন্নীতকৰণ ক্লায়েণ্টত আপলোড কৰা হৈছে আৰু সকলো নথি পত্ৰ আবাসীক ঘূৰাই দিয়া হৈছে৷

• অপাৰেটৰে নিজকে প্ৰমাণীকৰণ কৰি আবাসীৰ তথ্য গ্ৰহণৰ পৰা ছাইন অফ কৰিব৷
• আপুনি কৰা পঞ্জীয়নৰ বাবে অন্য কাকো স্বাক্ষৰ কৰিবলৈ নিদিব৷ আনে কৰা পঞ্জীয়নত আপুনি স্বাক্ষৰ নকৰিব৷
• বাসীৰ বায়’মেট্ৰিক ব্যতিক্ৰমৰ ক্ষেত্ৰত ছাইন অফৰ বাবে অপাৰেটৰে ছুপাৰভাইজাৰৰ ওচৰলৈ যাব৷
• যদি বৈধতাকৰণৰ প্ৰকাৰ পৰিচায়ক/এইচঅ’এফ হয়, তেন্তে পৰিচায়ক/বৈধতাপ্ৰদানকাৰীক পুনৰীক্ষণ স্ক্ৰীণত ছাইন অফ কৰিবলৈ দিব৷
• যদি পঞ্জীয়নৰ সময়ত পৰিচায়কগৰাকী শাৰীৰিকভাৱে উপস্থিত নাথাকে তেন্তে ‘‘এটাচ্চ লেটাৰ’’ চেকবক্স বাচনি কৰক যাতে দিনটোৰ শেষত পৰিচায়কে পঞ্জীয়ন বৈধতাকৰণ কৰিব পাৰে৷
• সন্মতি পত্ৰত ছপা হ’বলগীয়া আইনী/বিবৃতি টেক্সটসমূহ ছপা কৰাৰ বাবে অপাৰেটৰে ভাষা বাচনি কৰিব পাৰে৷
• অপাৰেটৰে আবাসীক কোনটো ভাষাত ৰচিদ ছপা কৰিব লাগিব সেই বিষয়ে সোধা প্ৰয়োজন৷ ঘোষণা কৰা যিকোনো ভাষা বিকল্প বাচনি কৰিলে, ছপা ৰচিদখন বাচনি কৰা ভাষা অৰ্থাৎ ইংৰাজী অথবা যিকোনো স্থানীয় ভাষাত স্ক্ৰীণত ছেট কৰা বিন্যাস অনুসৰি ছপা হৈ ওলাব৷
• সন্মতি পত্ৰ তথা অন্যান্য তথ্যত আবাসীৰ স্বাক্ষৰ গ্ৰহণ কৰক৷ আবাসীৰ সন্মতি পত্ৰখন যথেষ্ট গুৰুত্বপূৰ্ণ কিয়নো এয়া ইউআইডিএআইৰ প্ৰতি আবাসীৰ অনুমোদন অথবা অগ্ৰাহ্যকৰণক সূচায়৷
• স্বাক্ষৰ কৰি আবাসীক প্ৰাপ্তি স্বীকাৰ পত্ৰ প্ৰদান কৰক৷ প্ৰাপ্তি স্বীকাৰ পত্ৰখন হ’ল আবাসীজন পঞ্জীকৃত হোৱাৰ লিখিত নিশ্চিতকৰণ পত্ৰ৷ এয়া গুৰুত্বপূৰ্ণ কিয়নো ইয়াত আবাসীজনৰ পঞ্জীয়ন সংখ্যা, তাৰিখ আৰু সময় উল্লেখ থাকে যাতে আবাসীজনে ইউআইডিএআইৰ সৈতে যোগাযোগ কৰোঁতে আৰু তেওঁৰ আধাৰ স্থিতিৰ বিষয়ে জানিবলৈ যোগাযোগ কেন্দ্ৰ (১৯৪৭)ৰ সৈতে ইয়াক ব্যৱহাৰ কৰিব পাৰে৷
• শুধৰণি প্ৰক্ৰিয়াৰ জৰিয়তে আবাসীৰ তথ্য যদি শুদ্ধ কৰিবলগীয়া থাকে তেন্তে পঞ্জীয়ন সংখ্যা, তাৰিখ আৰু সময়ৰ প্ৰয়োজন৷ সেইবাবে অপাৰেটৰ নিশ্চিত হোৱা প্ৰয়োজন যাতে ছপা হোৱা প্ৰাপ্তি স্বীকাৰ পত্ৰ আৰু সন্মতি পত্ৰ পৰিষ্কাৰ আৰু পঠনযোগ্য হোৱা উচিত৷
• আবাসীক প্ৰাপ্তি স্বীকাৰ পত্ৰ প্ৰদানৰ সময়ত অপাৰেটৰে নিম্নোক্তসমূহ আবাসীক জনোৱা উচিত৷
• প্ৰাপ্তি স্বীকাৰ পত্ৰত ছপা হোৱা নম্বৰটো আধাৰ নম্বৰ নহয় আৰু আবাসীক আধাৰ নম্বৰ পত্ৰৰ জৰিয়তে জ্ঞাত কৰা হ’ব৷ এই বাৰ্তাটো প্ৰাপ্তি স্বীকাৰ পত্ৰটো উল্লেখ থাকে৷
• আবাসীয়ে তেওঁৰ আৰু সন্তানৰ পঞ্জীয়নৰ প্ৰাপ্তি স্বীকাৰ পত্ৰখন ভৱিষ্যতৰ বাবে সঞ্চয় কৰি ৰখা উচিত৷
• পৰিচায়ক ভিত্তিক পঞ্জীয়নৰ ক্ষেত্ৰত পৰিচায়কে নিৰ্ধাৰিত সময়ৰ ভিতৰত ছাইন অফ কৰা উচিত আৰু আবাসীৰ আধাৰ এজন বৈধ পৰিচায়কৰ পৃষ্ঠপোষকতাত হয়৷
• আবাসীৰ তথ্য শুধৰণীৰ বাবে ৯৬ ঘণ্টাৰ সময় উপলব্ধ, সেয়ে যদি কোনো শুধৰণীৰ আৱশ্যক তেন্তে এই সুবিধা গ্ৰহণ কৰা উচিত৷
• আধাৰ প্ৰস্তুতিৰ স্থিতি জানিবলৈ তেওঁলোকে কল চেণ্টাৰত কল কৰিব পাৰে অথবা ই-আধাৰ প’ৰ্টেল/আধাৰ প’ৰ্টেল/ৱেবছাইটত লগ অন কৰিব পাৰে৷
• আধাৰ নম্বৰ স্থানীয় ডাক বিভাগ/অথবা অন্য নিৰ্ধাৰিত এজেন্সীৰ জৰিয়তে পঞ্জীয়নৰ সময়ত আবাসীয়ে প্ৰদান কৰা ঠিকনালৈ প্ৰেৰণ কৰা হয়৷

e-Aadhaar is a password protected electronic copy of Aadhaar, digitally signed by UIDAI. 

As per Aadhaar Act, e-Aadhaar is equally valid like Physical Copy of Aadhaar for all purposes. For validity of eAadhaar, please visit UIDAI circular- https://uidai.gov.in/images/uidai_om_on_e_aadhaar_validity.pdf

Aadhaar Number holder can download e-Aadhaar by visiting UIDAI's MyAadhaar portal - https://myaadhaar.uidai.gov.in or by using mAadhaar app for mobile phones.

OTP for downloading eAadhaar will be received on registered mobile number.

 Masked Aadhaar implies replacing of first 8 digits of Aadhaar number with  “xxxx-xxxx” while only last 4 digits of the Aadhaar Number are visible.

Password of eAadhaar is a combination of the first 4 letters of name in CAPITAL and the year of birth (YYYY).

For Example:

Example 1
Name: SURESH KUMAR
Year of Birth: 1990
Password: SURE1990

Example 2
Name: SAI KUMAR
Year of Birth: 1990
Password: SAIK1990

Example 3
Name: P. KUMAR
Year of Birth: 1990
Password: P.KU1990

Example 4
Name: RIA
Year of Birth: 1990
Password: RIA1990

Resident needs 'Adobe Reader' to view digitally verified e-Aadhaar. To install Adobe Reader in the System visit https://get.adobe.com/reader/

Please visit Aadhaar YouTube Channel and watch tutorial link on https://youtu.be/aVNfUNIccZs?si=ByW1O6BIPMwc0seL

VID can be generated only by the Aadhaar number holder. They can also replace (generate a new VID) their VID from time to time. At any given time only one VID will be valid for an Aadhaar number. UIDAI provide various options to Aadhaar number holders to generate their VID, retrieve their VID in case they forget, and replace their VID with a new number. These options will be made available via UIDAI’s website (www.myaadhaar.uidai.gov.in), eAadhaar download, mAadhaar mobile application, etc.

VID can also be generated by sending an SMS to the Aadhaar helpline number 1947. Resident will have to type “GVIDLast 4 digits of Aadhaar Number” and send it to 1947 through the registered Mobile Number.

No other entity like AUA/KUA can generate VID on behalf of Aadhaar number holder. The VID can be generated by Aadhaar number holder by himself/herself only. Aadhaar number holder will receive the VID through SMS on registered mobile number.

Yes, UIDAI provide multiple ways to generate new and/or retrieve current VID. These options are made available via UIDAI’s website (www.myaadhaar.uidai.gov.in), eAadhaar, mAadhaar mobile application, SMS, etc.

For retrieval of VID, Aadhaar number holder may send SMS to the Aadhaar helpline number 1947. Resident will have to type “RVID Last 4 digits of Aadhaar Number” and send it to 1947 through the registered Mobile Number.

Yes. VID can be used in lieu of Aadhaar number to perform Aadhaar Authentication.

Yes, Aadhaar number holder consent is necessary for VID based authentication. Agency is required to inform the Aadhaar number holder the purpose for authentication and collect explicit consent for performing authentication.

No. Since VID is temporary and can be changed by the Aadhaar number holder, storing VID has no value. Agencies should not store VID in any database or logs.

After the minimum validity period (currently set as 1 calender day or after midnight 12), Aadhaar number holder may requests regeneration of a new VID. In this way, new VID will be generated and the previous VID will be deactivated.
In case, if resident opts for retrieval of VID, the last active VID will be sent to the Aadhaar number holder through SMS. Resident will have to type “RVIDLast 4 digits of Aadhaar Number” and send it to 1947 through the registered Mobile Number.

At this time there is no expiry period defined for VID. VID will be valid till the time a new VID is generated by the Aadhaar number holder.

You can update your demographic details in Aadhaar
1 - By enrolling through nearest enrolment centre. You can search the nearest enrolment centre by clicking https://bhuvan.nrsc.gov.in/aadhaar/
2- Using Online services for address update and document update available at https://myaadhaar.uidai.gov.in/ .

Yes, mobile number should be registered to Aadhaar for using online services.

You can update your mobile number by visiting a Aadhaar Enrolment Centere, you can locate the centre at Bhuvan Aadhaar Portal

Relationships details are not collected in Aadhaar. However you have option to add name of your father/husband/etc  in C/o field. This will be part of your address and no documentary support is required for the same.

You have to enter the details in English, which shall be transliterated into your selected regional language. You can update for any correction in transliteration if required. The following regional languages are available for update of address through online.

Bengali, Gujarati, Hindi, Kannada, Malayalam, Marathi, Odia, Punjabi, Tamil, Telugu and Urdu.

On successful submission of an online address update request,  a SRN (Service Request Number) is generated, which is shown on screen and also sent via SMS to your registered mobile number. After successful submission of the request, please download the invoice containing the SRN number and other details. The status of the update request can be checked at the bottom of the page by login in to Check Aadhaar Update Status

Aadhaar update requests to be supported by valid/proof of address (POA) document. A request can be rejected for invalid document in following scenarios:

1. The Proof of Address(POA) document should be a Valid document, as per document list available at List of Supporting Document
2. Document is in the name of the Aadhaar holder for whom update request is submitted.
3. Address details entered should match the address with the address mentioned in the document.
4. Image uploaded should be clear and colored scan of original document.

Aadhaar Authentication history service hosted on UIDAI Website provides detailed authentication transactions logs for Aadhaar authentication performed by the individual resident in last six months & maximum 50 records can be viewed at instance.

Authentication History service is hosted on UIDAI Website at URL https://resident.uidai.gov.in/aadhaar-auth-history OR resiedent may use this service through mAadhaar App

Resident can check his/her Aadhaar Authentication history from UIDAI Website https://resident.uidai.gov.in/aadhaar-auth-history or through mAadhaar App by using his/her Aadhaar Number/VID & enter security code and follow the metioned procedure.

Note: Registered mobile number is mandatory to avail this service.

Resident can get the following information in Aadhaar Authentication history against every Authentication done by resident.

1. Auth Modality.
2. Date & Time of Authentication.
3. UIDAI Response code.
4. AUA Name
5. AUA Transaction ID (With Code)
6. Authentication Response (Success/Failure)
7. UIDAI Error code

Aadhaar number holder can view details of all authentication records performed by any Authentication User Agency (AUA) or by him/her in the last 6 months. However, maximum of 50 records can be viewed at one point of time. If Aadhaar number holder want to check more records then he/she may require to select the date range in calendar & accordingly authentication records can be viewed.

For every failed authentication transaction record, specific error code is assigned. Please check the details of error code number against that failed authentication transaction to know the reason of failure.

If the listed authentication transaction is not performed by the Aadhaar number holder, resident may contact the respective Authentication User Agency (AUA) for further details.

For every authentication transaction performed by an Aadhaar number holder, UIDAI generates a unique code to identify the transactions and sends the same to Authentication User Agency (AUA) along with the response. This Response Code is helpful to uniquely identify the transaction by AUA as well as UIDAI and may be used for any further enquiry from AUA by the Aadhaar number holder.

For every authentication transaction performed by an Aadhaar number holder, AUA generates a unique Transaction ID to identify the transaction and sends the same to UIDAI as part of the authentication request. This Transaction ID along with Response Code can be used for any further enquiry from AUA by the Aadhaar number holder.

UIDAI provides authentication facility with different modes such as demographic, biometric (fingerprint , Iris or face) or One Time Password (OTP). Auth Modality shows the mode of authentication used to perform that specific authentication transaction.

An Error Code provide the details/reason for the failure of authentication transaction.  For Error Codes details, resident may refer to Aadhaar Authentication API document published on UIDAI website.

Below are Error Code List -

“100” – Personal information demographic data did not match.

“200” – Personal address demographic data did not match.

“300” – Biometric data did not match.

“310” – Duplicate fingers used.

“311” – Duplicate Irises used.

“312” – FMR and FIR cannot be used in same transaction.

“313” – Single FIR record contains more than one finger.

“314” – Number of FMR/FIR should not exceed 10.

“315” – Number of IIR should not exceed 2.

“316” – Number of FID should not exceed 1.

“330” – Biometrics locked by Aadhaar holder.

“400” – Invalid OTP value.

“402” – “txn” value did not match with “txn” value used in Request OTP API.

“500” – Invalid encryption of session key.

“501” – Invalid certificate identifier in “ci” attribute of “Skey”.

“502” – Invalid encryption of PID.

“503” – Invalid encryption of Hmac.

“504” – Session key re-initiation required due to expiry or key out of sync.

“505” – Synchronized Key usage not allowed for the AUA.

“510” – Invalid Auth XML format.

“511” – Invalid PID XML format.

“512” – Invalid Aadhaar holder consent in “rc” attribute of “Auth”.

“520” – Invalid “tid” value.

“521” – Invalid “dc” code under Meta tag.

“524” – Invalid “mi” code under Meta tag.

“527” – Invalid “mc” code under Meta tag.

“530” – Invalid authenticator code.

“540” – Invalid Auth XML version.

“541” – Invalid PID XML version.

“542” – AUA not authorized for ASA. This error will be returned if AUA and ASA do not have linking in the portal.

“543” – Sub-AUA not associated with “AUA”. This error will be returned if Sub-AUA specified in “sa” attribute is not added as “Sub-AUA” in portal.

“550” – Invalid “Uses” element attributes.

“551” – Invalid “tid” value.

“553” – Registered devices currently not supported. This feature is being implemented in a phased manner.

“554” – Public devices are not allowed to be used.

“555” – rdsId is invalid and not part of certification registry.

“556” – rdsVer is invalid and not part of certification registry.

“557” – dpId is invalid and not part of certification registry.

“558” – Invalid dih.

“559” – Device Certificate has expired.

“560” – DP Master Certificate has expired.

“561” – Request expired (“Pid->ts” value is older than N hours where N is a configured threshold in authentication server).

“562” – Timestamp value is future time (value specified “Pid->ts” is ahead of authentication server time beyond acceptable threshold).

“563” – Duplicate request (this error occurs when exactly same authentication request was re-sent by AUA).

“564” – HMAC Validation failed.

“565” – AUA license has expired.

“566” – Invalid non-decryptable license key.

“567” – Invalid input (this error occurs when unsupported characters were found in Indian language values, “lname” or “lav”).

“568” – Unsupported Language.

“569” – Digital signature verification failed (means that authentication request XML was modified after it was signed).

“570” – Invalid key info in digital signature (this means that certificate used for signing the authentication request is not valid – it is either expired, or does not belong to the AUA or is not created by a well-known Certification Authority).

“571” – PIN requires reset.

“572” – Invalid biometric position.

“573” – Pi usage not allowed as per license.

“574”– Pa usage not allowed as per license.

“575”– Pfa usage not allowed as per license.

“576” - FMR usage not allowed as per license.

“577” – FIR usage not allowed as per license.

“578” – IIR usage not allowed as per license.

“579” – OTP usage not allowed as per license.

“580” – PIN usage not allowed as per license.

“581” – Fuzzy matching usage not allowed as per license.

“582” – Local language usage not allowed as per license.

“586” – FID usage not allowed as per license. This feature is being implemented in a phased manner.

“587” – Name space not allowed.

“588” – Registered device not allowed as per license.

“590” – Public device not allowed as per license.

“710” – Missing “Pi” data as specified in “Uses”.

“720” – Missing “Pa” data as specified in “Uses”.

“721” – Missing “Pfa” data as specified in “Uses”.

“730” – Missing PIN data as specified in “Uses”.

“740” – Missing OTP data as specified in “Uses”.

“800” – Invalid biometric data.

“810” – Missing biometric data as specified in “Uses”.

“811” – Missing biometric data in CIDR for the given Aadhaar number.

“812” – Aadhaar holder has not done “Best Finger Detection”. Application should initiate BFD to help Aadhaar holder identify their best fingers.

“820” – Missing or empty value for “bt” attribute in “Uses” element.

“821” – Invalid value in the “bt” attribute of “Uses” element.

“822” – Invalid value in the “bs” attribute of “Bio” element within “Pid”.

“901” – No authentication data found in the request (this corresponds to a scenario wherein none of the auth data – Demo, Pv, or Bios – is present).

“902” – Invalid “dob” value in the “Pi” element (this corresponds to a scenarios wherein “dob” attribute is not of the format “YYYY” or “YYYYMM-DD”, or the age is not in valid range).

“910” – Invalid “mv” value in the “Pi” element.

“911” – Invalid “mv” value in the “Pfa” element.

“912” – Invalid “ms” value.

“913” – Both “Pa” and “Pfa” are present in the authentication request (Pa and Pfa are mutually exclusive).

“930 to 939” – Technical error that are internal to authentication server.

“940” – Unauthorized ASA channel.

“941” – Unspecified ASA channel.

“950” – OTP store related technical error.

“951” – Biometric lock related technical error.

“980” – Unsupported option.

“995” – Aadhaar suspended by competent authority.

“996” – Aadhaar cancelled (Aadhaar is no in authenticable status).

“997” – Aadhaar suspended (Aadhaar is not in authenticatable status).

“998” – Invalid Aadhaar Number.

“999” – Unknown error.

Aadhaar QR code is Quick Response code digitally signed by UIDAI and used for offline verification of identity. It is present on all forms of Aadhaar like e-Aadhaar, Aadhaar letter, Aadhaar PVC card and mAadhaar. It contains last 4 digits of Aadhaar number, name, address, gender, date of birth and photograph of the Aadhaar number holder. It also contains masked mobile number and email-id of the Aadhaar number holder. 

Aadhaar QR code can be used for verification of identity in offline mode. 'Aadhaar QR Code Scanner' app for smartphones and Windows based QR code scanning application  works in Offline mode and does not require internet for scanning purpose.

Aadhaar QR code can ONLY be read using:
1. mAadhaar app available on Google Play Store and app store
2. Aadhaar QR Scanner app available on Google Play Store and app store
3. Windows based application available on UIDAI official website - https://uidai.gov.in/en/ecosystem/authentication-devices-documents/qr-code-reader.html

Post installation of UIDAI’s QR code reader application, QR code of e-Aadhaar need to be scanned using the physical scanner in line with UIDAI Specifications. The application will display the demographic details of resident once the QR Code is digitally verified using Windows QR code scanner.

Any Aadhaar Holder or any User/Service Agencies like Banks, AUAs, KUAs, Hotels etc can use this facility for offline verification of the data in Aadhaar.

It is a secure sharable document which can be used by any Aadhaar number holder for offline verification of Identification.

A resident desirous of using this facility shall generate his/her digitally signed Offline XML by accessing UIDAI website. The Offline XML will contain Name, Address, Photo, Gender, DOB, hash of registered Mobile Number, hash of registered Email Address and reference id which contains last 4 digits of Aadhaar Number followed by time stamp. It will provide Offline Aadhaar Verification facility to service providers/Offline Verification Seeking Entity (OVSE) without the need to collect or store Aadhaar number.

The process of generating Aadhaar Offline e-KYC is explained below:

• Go to URL https://myaadhaar.uidai.gov.in/offline-ekyc
• Enter ‘Aadhaar Number’ or ‘VID’ and enter mentioned ‘Security Code’ in screen, then click on ‘Send OTP’. The OTP will be sent to the registered Mobile Number for the given Aadhaar number or VID. OTP will be available on m-Aadhaar mobile Application of UIDAI. Enter the OTP received. Enter a Share Code which be the password for the ZIP file and click on ‘Download’ button
• The Zip file containing the digitally signed XML will be downloaded to device wherein the above mentioned steps have been performed.

The Offline Aadhaar XML can also be downloaded from mAadhaar app.

Any Aadhaar number holder who desires to establish his/her identity to any service provider (OVSE) using digitally signed XML downloaded from UIDAI website can be a user of this service. The service provider should have provisions of providing this Aadhaar Paperless Offline e-KYC at their facility and do the offline verification

Residents can share the XML ZIP file along with the Share Code to the service provider as per their mutual convenience.

The process of Aadhaar Offline e-KYC Verification by Service Provider is:

Service Providers shall not share, publish or display either XML or Share Code or its contents with anyone else. Any non-compliance of these actions shall invite actions under Sections 29(2), 29 (3), 29(4) and 37 of The Aadhaar Act, 2016 (as amended) and sub regulation 1A of regulation 25, regulation 14A of The Aadhaar (Authentication and Offline Verification) Regulation, 2021 and regulation 6 and 7 of The Aadhaar (Sharing of Information) Regulation, 2016.