FAQs

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

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

Aadhaar number holder can get the following information in Aadhaar Authentication history against every Authentication done by Aadhaar number holder.

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

An Error Code provide the details/reason for the failure of authentication transaction.  For Error Codes details, Aadhaar number holder 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.

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.

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.

Aadhaar number holder 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 mentioned procedure.

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

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

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

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.

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.

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.

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.

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 Aadhaar number holder once the QR Code is digitally verified using Windows QR code scanner.

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 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

Public certificate for Digital signature validation can be downloaded from here.

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

Identity verification can simply be accomplished by providing an identity document like PAN card, Passport etc to the service provider. However, all these documents, which may be used for identification can still be forged and faked which may or may not be possible to verify offline instantaneously. The document verifier has no technological means to verify the authenticity of the document or the information it contains and has to trust the document producer. Whereas, the XML file generated by the Aadhaar number holder using Aadhaar Paperless Offline e-KYC is digitally signed document using UIDAI digital signature. Thus, the service provider can verify the demographic contents of the file and certify it to be authentic when doing the offline verification