FAQs

At this time, the support has been provided for import of pre-enrolment data in English. During enrolment process, the data is converted from English to local language through the transliteration engine. The operator can correct this data in the presence of the individual seeking to enrol. The software is planned to provide support for import of pre-enrolment data in English, local language or both in future versions. For pre-enrolment data imported in local language, it will not be over-ridden by the transliteration engine. However, a soft keypad / IME will be available for editing the data.

The required address to be entered in English by the individual.  The data entered in English shall be auto transliterated into local language available as per your Aadhaar.  If any difference is noticed in transliteration to Regional language, option available to edit the same.  However, to change the existing Regional language to different Language, you have to approach the nearest Aadhaar enrolment Centre.

Enrolment can be done in following 16 languages:   Assamese, Bengali, English, Gujarati,Hindi, Kannada, Konkani, Malayalam, Marathi, Manipuri, Nepali, Odia, Punjabi, Tamil, Telugu and Urdu.    Normally the operator shall provide Aadhaar enrolment in the Regional Language of that Region.  If you need enrolment in a different language, please request the operator to select the required language before starting enrolment and ensure that the transliteration is proper.

The most common problem that UIDAI have seen is with installation of the IME, and it’s interactions with the language bar. Further, it is possible to configure the Windows language input to assume a local language keyboard. This is not the same as transliteration, but assumes a different keyboard is being used – and the results are very different. UIDAI have also had difficulty in truly transliterating English words into local language, as they are very different from the language model. This can be better handled by using advanced facilities in the IMEs (for ex. Schemes in Google IME) The language support must be configured on a per user basis, and that makes it harder to manage.

At this time, the primary source for data entry is in English. However, as the technology matures, we expect to change the primary language to local language based on reverse transliteration. Since this is a dependency on technology that is not yet available, we cannot assure a date, however – we are targeting a release in Version 3.0.

Supporting a local language implies providing support for:
Data entry in local language
Transliteration of English language data to local language
Labels in local language in the software (on screen)
Labels in local language in the print receipt
Import of pre-enrolment data in local language (upcoming)

Yes, Training, Testing and Certification Policy is applicable for Authentication Operators. To know more, click on the below-mentioned link:

https://uidai.gov.in//images/TTC_Policy_2023.pdf

After the completion of suspension period, suspended Operators can apply for re-training followed by Re-certification exam as per the TT&C Policy.

If a candidate is already working under a Registrar/Enrolment Agency and wants to work with a different Registrar/Enrolment Agency, then he/she will have to appear for re-certification examination, duly authorized by the respective Registrar/Enrolment Agency.

The mock question paper is available on the registration portal: https://uidai.nseitexams.com/UIDAI/LoginAction_input.action