Unique Enrollment Number and Aadhaar Service Center of India

No Aadhaar number holders can change their VID at any time, so there's no point in storing VID. Organizations shouldn't keep VID in any logs or databases.

A new VID will be generated and the old one will be deactivated after the minimum validity period (currently set as 1 calendar day) has elapsed, provided the holder of the Aadhaar number requests regeneration. The last valid VID will be sent to the person who owns the Aadhaar number if the resident chooses to retrieve their VID.

For VID-based authentication, yes, Aadhaar holder permission is required. To authenticate an Aadhaar number, the agency must first obtain the cardholder's informed consent after explaining the authentication's intended use.

Yes Instead of an Aadhaar number, a VID can be used in the Authentication API. By May 31, 2019, different organizations will have updated their Aadhaar authentication app to accept VID as an input for authentication.

The only person who can make a VID is the one who has an Aadhaar number. UIDAI has established a minimum validity period for VIDs, which is currently 1 calendar day, after which they can be replaced (a new VID generated) at any time. e After midnight on the next day, a new VID will be created. An Aadhaar number can only have one VID active at any given time. UIDAI will give those with an Aadhaar number multiple ways to create a VID, retrieve a forgotten VID, or get a new VID issued. The UIDAI resident portal, the eAadhaar app, the Aadhaar enrolment center, and the mAadhaar mobile app are all channels through which these choices will be made available. UIDAI's resident portal currently supports VID generation. Residents will have their VID sent to their registered mobile number via SMS whenever it is needed.

SMS messages sent to the Aadhaar support number 1947 can also be used to generate a VID. Sending "GVIDLast 4 digits of Aadhaar Number" via the resident's registered mobile number to 1947 is required.

UIDAI will, indeed, offer a variety of options for creating and retrieving VIDs. UIDAI will provide access to these features via the resident portal, eAadhaar, Aadhaar Enrollment centers, the mAadhaar mobile app, and other channels. UIDAI's resident portal now has the ability to create a VID. Residents will receive an SMS on their registered mobile number with their VID number whenever it is needed.

Sending an SMS to the Aadhaar helpline number 1947 will also return your VID. To verify their identity, residents can text "RVIDLast 4 digits of Aadhaar Number" to 1947 from their registered mobile phone number.

The mAadhaar app can be downloaded by Indians on both Android and iOS devices. Here are the measures to take for the app's installation:

If an individual registers the same Aadhaar number in more than one mobile device, the first number will be deactivated. One Aadhaar enrollment per device is permitted.

The app does not have a save password feature for the security and privacy of Aadhaar cardholders. Therefore, every time a user wants to access their profile or My Aadhaar, they will need to enter a password.

mAadhaar is more than just a replacement for the Aadhaar card The local can receive the following advantages by downloading the mAadhaar app:

1. Download Aadhaar, or find a way to get your lost or forgotten Aadhaar number back.
2. It is important for residents to be able to view and show their Aadhaar card even when they are not connected to the internet.
3. Change Your Known Address in Aadhaar With or Without Proof
4. You can store and manage the Aadhaar information for your entire family (up to five people) using just one mobile device.
5. Provide service providers with a paperless eKYC or QR code.
6. Locking in Aadhaar or biometrics is a great way to keep it safe.
7. Users who have locked their Aadhaar or do not wish to share their Aadhaar can instead use a VID that has been generated for them or that they have retrieved from the Aadhaar database.
8. Obtain Aadhaar SMS support even when you're not online.
9. Residents can check the status of their service request made after enrolling in Aadhaar, ordering a reprint, or updating their Adhaar data through the App's "Check Request Status Dashboard."
10. Share your common services with those who don't have smartphones so they can use Aadhaar.
11. Obtain a log of all authentication attempts and updates.
12. Schedule a visit to the Aadhaar Seva Kendra.
13. After a successful update request has been processed, residents can access their updated Aadhaar profile information using the Sync feature.
14. Aadhaar Online Services on the UIDAI Website now support Time-based One-Time Password in place of SMS-based OTP.
15. Find your local enrollment center with the help of Locate Enrollment Center (EC).
16. The mAadhaar App's More section contains links to the App's Contact, Usage guidelines, Terms & Conditions, and other relevant information.
17. The Aadhaar enrolment or Aadhaar update/correction forms can be downloaded from the More section, along with links to helpful FAQs and the Chatbot.

In India, the mAadhaar app can be used at any time and in any location. mAadhaar is more than just a replacement for the Aadhaar card. The mAadhaar profile can be used as identification at airports and on trains, and its users can also use the app's features to provide their eKYC or QR code to businesses that require Aadhaar verification before they provide their services.  

The mAadhaar app works with iOS 10 on the iPhone. greater than 0

No The mAadhaar App can be downloaded and used by any resident of India who owns a smartphone.

Only a subset of Aadhaar-enabled services (such as Order Aadhaar reprint, Locate Enrolment Center, Verify Aadhaar, Scanning QR code, etc.) will be available to residents without a registered mobile number.

All the other Aadhaar services and Aadhaar Profile services available through My Aadhaar require a registered mobile number, though. Anyone with a smartphone can create a profile and register to vote. The OTP will be sent to their mobile number, but only that number.

The mAadhaar app is only usable by those who already have an Aadhaar number associated with a mobile phone. In order to create a profile, they need only download an app to their smartphone. The OTP will, however, be sent to only their registered mobile number. Here are the steps you need to follow to create an Aadhaar profile:

1. Get the app going.
2. Select the Aadhaar Registration link from the main dashboard's menu.
3. Make up a 4 digit passcode (remember this code, you'll need it to access your profile later)
4. Make sure you're using a valid Aadhaar and Captcha.
5. To submit, please enter a valid OTP.
6. The individual's details need to be recorded.
7. Once an Aadhaar number is registered, it will appear under the "registered" button.
8. Select the "My Aadhaar" option from the drop-down menu.
9. Key in 4-digit Passcode
10. The Aadhaar Dashboard Shows Up

The mAadhaar app does not allow users to change their personal information, such as their name, date of birth, or phone number. The ability to change your address is currently limited to a document-based system.  

Future updates may include the demographics-related features, though.

No The mAadhaar App can be downloaded and used by any resident of India who owns a smartphone.

Only a subset of Aadhaar's services, like finding an enrollment center or verifying an existing card, or scanning a QR code, will be accessible to residents without a registered mobile number.

All other Aadhaar services and Aadhaar Profile services accessible through My Aadhaar require a registered mobile number. Anyone with a smartphone can create a profile and register to vote. However, only their registered mobile number will receive the OTP.

Both iOS and Android users have access to the same features in the mAadhaar app. All devices (iOS, Android) have the same features and user experience.

Profile summaries (including photo, name, and Aadhaar number) are accessible from the main dashboard by selecting the corresponding tab. How to view your Aadhaar profile:

1. Open the program
2. To access your Aadhaar profile, select it from the main dashboard's sidebar.
3. Type in the 4-digit PIN you chose when creating your profile.
4. The Aadhaar card's front is displayed. To see the reverse, simply slide to the left.
5. Additional profiles can be viewed by continuing to slide to the left.

Aadhaar services can be accessed by tapping the My Aadhaar tab located at the bottom of the Dashboard screen.

Find the complete list of error codes below.

"100" - There was a mismatch between your demographic and personal information.

"200" - Inconsistency in the demographic information for your home address

"300" - Incompatible biometric data

"310" -- Utilization of Extra Fingers

The use of Irises in duplicate (311)

No use of FMR and FIR in the same transaction (312)

More than one finger is recorded in a single FIR record (313).

"314" - No more than 10 FMR/FIR allowed.

The maximum number of IIRs allowed is 2 (315).

"316" - Maximum allowed FID count is 1.

Aadhaar cardholder biometrics locked at 330

"400" - Invalid One-Time Password

Not the same "txn" value was used in the Request OTP API (error code: 402)

"500" - Incorrect session key used for encryption

Error 501: "ci" attribute of "Skey" contains an invalid certificate identifier.

Error Code 502: PID Encryption Failure

Invalid Hmac encryption (503).

Error "504" means the session key has expired or is out of sync and must be re-started.

"505" - The AUA does not permit the use of Synchronized Keys.

510 - Invalid Authorization XML Format

“511” – Invalid PID XML format

Aadhaar holder consent in "rc" attribute of "Auth" is invalid, returning error code "512."

"520" - Unacceptable "tid" value

Meta tag "dc" code is invalid (521).

Meta tag "mi" invalid code (524).

An invalid "mc" code was found in the Meta tag (527).

The authenticator code was invalid (530).

Invalid Authorization XML Version "540"

Invalid PID XML version (541).

AUA not permitted for ASA (542). If the portal does not contain a link between AUA and ASA, this error will be returned.

Sub-AUA 543 that isn't officially part of the AUA. If the portal does not have the "Sub-AUA" added for the Sub-AUA specified in the "sa" attribute, this error will be returned.

Error code 550: Invalid "Uses" element attributes

The value "551" is not a valid "tid."

"553" - Currently unsupported registered devices There will be a gradual rollout of this feature.

No use of electronic devices in public areas (554).

The rdsId you entered (555) is not a valid certification registry identifier.

Error 556: rdsVer is not a valid certification version.

Certification registry does not include dpId (557).

Invalid dih (558).

"559" - Certificate for this Device has Expired

An expired DP Master Certificate (560)

Authentication server has a configured threshold of "N" hours, and the "Pid->ts" value is older than that.

"562" - The timestamp you provided is in the future (the value you provided for "Pid->ts" is too far in the future compared to the time on the authentication server).

Error code 563 means that the same authentication request was sent twice by the AUA.

Invalid HMAC Signature (564).

Expired AUA license (565),

License key "566" is invalid because it cannot be decrypted.

"567" - Invalid input (occurs when Indian language values, "lname" or "lav," contain characters not supported by the system).

"568" - Language Not Supported

Error code 569 indicates that the authentication request XML was altered after it was signed, meaning that the digital signature verification failed.

Error 570: Invalid key information in digital signature (the certificate used to sign the authentication request is invalid because it has expired, does not belong to the AUA, or was not issued by a trusted Certification Authority).

The PIN needs to be reset (571),

Biometric position '572' is invalid.

"573" - License prohibits use of Pi

No use of "574" in Pa. is permitted by license.

The license forbids the use of the number 575 in a Pfa.

License restriction for FM radio use: "576."

License restrictions prohibit "577" use in a FIR context.

License restrictions prohibit "578" use in IIR.

"579" - License prohibits OTP use.

"580" - License prohibits PIN use.

"581" - License prohibits the use of fuzzy matching.

License restriction forbids use of "582" in the local language.

"586" - License prohibits FID use. This update is rolling out gradually.

"587" - No such namespace "/"

"588" - Device registration is prohibited by license.

"590" - Device prohibited by license from use in public

"710" - Pi data required by "Uses" is missing.

Data for "Pa" not present in "Uses," as required by "720."

Data for "Pfa" not present where required by "Uses," error "721.

"730" - Insufficient PIN information, as per "Uses."

"740" - Invalid OTP data, per "Uses" requirements.

"800" - Invalid fingerprint or other biometric information

Biometric information not present, as required by "Uses" ("810").

"811" - Invalid or incomplete CIDR biometric data for the provided Aadhaar number

There was a failure to detect the "Best Finger" in 812 of the Aadhaar holders. BFD should be triggered by the application to aid the Aadhaar cardholder in selecting their best fingers.

"820" - The "bt" attribute in the "Uses" element is either undefined or empty.

"821" - The "bt" attribute of the "Uses" element has an invalid value.

The "bs" attribute of the "Bio" element in the "Pid" element has an invalid value of "822."

"901" - No authentication data was found in the request (this is the case when none of the auth data is provided, be it Demo, Pv, or Bios).

"902" - Invalid "dob" value in the "Pi" element (this corresponds to a scenario where the "dob" attribute is not of the format "YYYY" or "YYYMM-DD," or the age is outside of a valid range).

'910' - Pi element's mv attribute has an invalid value

The "Pfa" element has an invalid "mv" value (911).

Unacceptable "ms" value (912).

"913" - The authentication request contains both "Pa" and "Pfa" (these two options are incompatible with one another).

"930 to 939" — Internal authentication server technical error

"940" – Illegal ASA Frequency

Channel 941 of the ASA is not specified.

"950" - Technical issue with OTP store

Error code 951 indicates a problem with the biometric lock.

Option "980" is not available.

"995" - The competent authority has suspended Aadhaar.

The number "996" indicates that Aadhaar has been canceled.

Aadhaar is not in authenticatable status (error code 997).

Aadhaar Number Invalid, Error Code: 998

Error 999: Unknown cause

For Aadhaar Authentication, the following UIDAI services are utilized by Aadhaar number holders:

• Service providers and Aadhaar number holders will be able to confirm the Aadhaar number is active and active by using this feature.
• Service providers and Aadhaar number holders can use this feature to confirm the Aadhaar number is active and valid.
• Users with an Aadhaar number can lock their biometric authentication for added security. Once the same is locked, it can no longer be used for authentication. Before engaging in any biometric authentication transaction, locals have the option to unlock their biometrics.
• To see if your Aadhaar number has been linked to your bank account, visit the UIDAI website. The NPCI Server is queried for the current status of Aadhaar linking. Under any circumstance, UIDAI shall not be responsible or liable for the correctness of the displayed status The data retrieved from the NPCI server is not stored by UIDAI. The Supreme Court ruled on December 26 that linking a bank account with an Aadhaar number is not obligatory. 9 2018
• Users with an Aadhaar number can check their Aadhaar Authentication history to see every time they've authenticated their number.
• To create a 16-digit Virtual ID (VID), Aadhaar number holders can use a virtual ID generator.

Aadhaar Authentication history service hosted on UIDAI Website provides details of authentication performed by the individual resident in past

The demographic, biometric (fingerprint or iris), and One-Time-Password (OTP) authentication methods are all available through UIDAI. The Auth Modality field reveals the method of authentication that was employed for this particular authentication procedure.

Each instance of a failed authentication transaction is recorded with its own unique error code. In order to determine the cause of the authentication failure, please review the information associated with the specific error code number.

If a resident is unable to complete an authorized authentication transaction using their Aadhaar number, they should get in touch with the appropriate Authentication User Agency (AUA).

Following the on-screen prompts and entering one's Aadhaar Number/VID, residents can view their authentication records through UIDAI websites.

Please be aware that in order to use this service, a valid phone number must be on file.

UIDAI creates a unique code for each authentication transaction performed by an Aadhaar number holder and sends it to the Authentication User Agency (AUA) together with the response. This Response Code is useful for uniquely identifying the transaction by AUA and UIDAI, and the Aadhaar number holder may use it for any follow-up enquiry with AUA.

Against each authentication the resident has performed using Aadhaar, the resident can access the following details.

Authoritative Modality 2 Authentication Date and Time 3 Code returned from UIDAI 4 AUA Name5 AUA Order Number (Including Code)6 Success/Failure of Authentication7 Code d'erreur UIDAI

Every authentication record made in the last six months, whether by an AUA or the holder of the Aadhaar number, can be viewed by the holder of the Aadhaar number. However, only 50 records at a time can be viewed.

AUA creates a unique Transaction ID for each authentication transaction performed by an Aadhaar number holder, and sends it along with the authentication request to UIDAI. The owner of the Aadhaar number can contact AUA with any further questions using the provided Transaction ID and Response Code.

Password is the first four letters of your name, all capitalized, plus your birth year, in YYYY format.

Case in point:
First Example: SURESH KUMARY's Birth Year is 1990, So the Password Is "SURE1990"

Example 2

Example 3

Example 4

Hashing is most often used to check two files for equality. The owner will be able to tell at a glance whether or not two files are different based on their hash values, even without opening them and comparing every single word.

In file backup programs like SyncBack, hashing is used to ensure that no data has been corrupted during the transfer process. A user can check the integrity of the transferred file by comparing their hash values. If they're identical, the transferred file is an exact replica of the original.

For security reasons, some encrypted files (such as virtual drive container files) are created with a hardcoded size and last modification time. It would be impossible to tell at a glance whether or not two seemingly identical files are actually distinct, but their hash values would reveal any discrepancies.

Both e-Aadhaar QR codes include the resident's name, address, date of birth, gender, and a hashed version of their Aadhaar number (known as a "masked" number). e Aadhaar's final four digits The larger QR code also includes a photo.

Only UIDAI's Windows-based app can decode the newly digitally signed QR code and check it against UIDAI's own database of digital signatures. You can get the application from uidai. gov in In addition, a high-quality QR Code scanner that is STQC-approved will be needed.

The use of a LaserJet printer is strongly suggested for printing e-Aadhaar cards that contain the encrypted QR code.

The secure e-Aadhaar QR code must be scanned using the physical scanner after the UIDAI QR code reader application has been installed, per UIDAI Specifications. Once the e-Aadhaar QR code has been digitally verified by UIDAI at the backend, the application will display the resident's demographic information. In the event that the QR code's digital signature cannot be validated, the reader will show the user an appropriate error message.

This feature can be used by anyone to verify their e-Aadhaar information offline, including Aadhaar cardholders and service providers like banks, AUAs, KUAs, and more.

Please take note that on February 20, 2018, a new QR Code was implemented for use with e-Aadhaar, and a client for scanning these codes can be found at uidai. gov starting March 27th, 2018

The Aadhaar secure QR code is included in the UIDAI e-Aadhaar letter. UIDAI has changed the QR code on e-Aadhaar from the old, unprotected version to a new, encrypted one that includes the last four digits of the holder's Aadhaar number as well as their name, address, gender, date of birth, and photograph. A small QR Code containing only demographic information will be located on the front of the cutaway portion, and a larger QR Code containing both demographic information and a photo will be located on the top portion of the front and rear of the cutaway portion. In addition, a digital signature from UIDAI will be used to make this data even more secure and impossible to alter. Only UIDAI's Windows-based Custom client for PCs and Macs can read the new digitally signed QR code and instantly verify it against UIDAI digital signatures. Since QR Code scanners are so widely available, any attempt at e-Aadhaar fraud will be quickly uncovered.

Hashing is an algorithm that takes a file and returns a value encoded as a string of bits. Data is organized into blocks within a file. The information is hashed, which reduces the length of the original string to a fixed-length value called a key. The hash value represents a condensed version of the contents of the file.

The avalanche effect is a characteristic of a good hashing algorithm in which the hash output shifts drastically or completely when even a single bit or byte of data within a file is modified. Any hash function that doesn't do this is thought to have insufficient randomization and is therefore vulnerable to attack.

A hash is typically a long string of hexadecimal digits. Furthermore, hashing is a one-way process; the original data can never be recovered by using it.

A hash is typically a long string of hexadecimal digits. Since hashing is a one-way process, it is impossible to recover the original information.

By checking the HASH, we can be sure that the client installed is the official UIDAI release. For authentication purposes, UIDAI will supply SHA-1 and SHA-256.

It's a safe, transferable document that anyone with an Aadhaar number can use to confirm their identity in person.

If a local wants to sign their Aadhaar information digitally, they can do so through the UIDAI resident portal. The information will be presented in a digitally signed XML file, and it will include the person's name, address, photo, gender, date of birth, hash of registered mobile number, hash of registered email address, and reference id, which is the last four digits of their Aadhaar number, followed by a time stamp. Without requiring them to collect or store Aadhaar numbers, it will allow service providers/Offline Verification Seeking Entity (OVSE) to use the Offline Aadhaar Verification facility.

Offline e-KYC Verification with Aadhaar by Service Provider Process:

The service provider only needs the customer to present an identity document (PAN card, passport, etc.) in order to verify the customer's identity. It may or may not be possible to instantly verify offline whether or not any of the documents that could be used for identification are genuine. Without access to appropriate technological resources, the verifier of a document must rely on the producer's word that the document and its contents are genuine. Aadhaar Paperless Offline e-KYC, on the other hand, generates an XML file that is digitally signed by the UIDAI. As a result, the service provider can confirm the accuracy of the file's demographic information during the offline verification process.

Neither the Share Code nor the XML file, nor any information contained therein, may be distributed, published, or displayed by Service Providers. Actions under Sections 17 and 25 of The Aadhaar (Authentication) Regulation, 2016, Sections 4 and 6 of The Aadhaar (Sharing of Information) Regulation, 2016, and Sections 29(2), 29(3), and 37 of The Aadhaar Act, 2016 will be taken against anyone who does not comply with these requirements.

The Share Code and XML ZIP file can be easily shared between residents and service providers.

Below is a breakdown of how Aadhaar Offline e-KYC is created:

• The address to visit is https://resident.uidai.gov.in/offlineaadhaar.
• Simply type in your "Aadhaar Number" or "VID" and the "Security Code" that is displayed on the screen, and then select either "Send OTP" or "Enter TOTP." If you enter an Aadhaar or VID, an OTP will be sent to the mobile phone associated with that number. UIDAI's m-Aadhaar mobile application is where you can find TOTP. Fill in the received OTP/TOTP. To access the ZIP file, enter the Share Code that was provided to you and then click the "Download" button.
• After following the above steps, the device will download a Zip file containing the digitally signed XML.

Users of this service are Aadhaar cardholders who wish to verify their identity with an OVSE by submitting digitally signed XML obtained from the UIDAI website. Service providers need to be able to provide Aadhaar paperless offline e-KYC at their location and conduct offline verification.