Data and Downloads Sections
Authentication Sample Client (Java) kk
This is a sample authentication client software which works with authentication API. This software has the capability to authenticate demographic
This is designed purely as a test tool to reduce the development time taken by the AUAs and device vendors. This is released as source code and developers are free to download, modify, enhance, and use it. THIS IS NOT A SUPPORTED SOFTWARE.
---------------------------------------------------------------------------------------------
User manual - See "Aadhaar e-KYC Basics" book.
----------------------------------------------------------------------------------------------
e-KYC API version 1.0 Sample Client - Full Source Code - updated 08 Jan 2014
e-KYC API version 1.0 Sample Client - Full Binary - updated 08 Jan 2014 (NOTE: Also download Fop and Batik and extract the jar files to "jar" directory for printing to work)
e-KYC API version 2.0 Sample Client - Full Source Code - updated 22nd Sep 2016
e-KYC API version 2.0 Sample Client - Full Binary - updated 22nd Sep 2016
Schema Files for Various APIs
XSD and Protobuf files for Aadhaar Authentication APIs Version 1.6Authentication Clients and Samples in other Languages
Authentication Tools
Biometric data formats (FMR, FIR, IIR) testing tool checks if formats are valid ISO formats and as supported by Aadhaar Authentication. Developers can use this tool to test if the biometric record is proper before testing it online.
Biometric Format Test Tool - Binary and Source - Released on 9 Aug 2012
Bulk demographic authentication tool facilitates Demo Auth, accepting demographic data of the residents through various input modalities. THIS IS A SAMPLE TOOL demonstrating the features of demographic authentication. Both source and binary are provided below.
Binary setup and user manual - Binary - Released on 9 Oct 2013
Source code project - Source - Released on 9 Oct 2013
KYR+ Sample Application (NEW VERSION)
This is a sample reference implementation of KYR+ software which works with Aadhaar Enrolment Client 1.2.x versions. This software has the capability to configure fields and capture additional fields specific to registrars. This is built using Visual Studio 2008 using Windows
This is designed purely as a productivity tool to reduce the development time taken by the registrars on the KYR+ aspect. This is released as source code and registrars are free to download, modify, enhance, and use it. THIS IS NOT A SUPPORTED SOFTWARE.
KYR+ sample application (New Version) - Full source code - released 15
KYR+ sample application (New Version) - Binary - released 15
KYR+ sample application document (New Version) - User Manual - released 15 March, 2011
Decryption Test Utility (1024-bit)
This test decryptor utility is developed to assist Registrars in decrypting the Registrar Enrolment Packets before go-live. This utility works with packets that are encrypted with 1024-bit key (see below for 2048-bit key tool)This utility supports only PFX and PEM formats for private key files. The private key files must be password protected. This tool also supports USB Token with .Net PKCS11 APIs at location "C:\WINDOWS\system32\aetpkss1.dll".
For all the other cases, a modification in the source code of Decryptor Utility is necessary for
This is designed purely as a test tool along with source code provided for initial testing. THIS IS NOT A SUPPORTED SOFTWARE.
Decryption utility binary - last updated 16
Decryption utility source code - last updated 16
Decryption utility "read me" document - last updated 16 Nov, 2010
Decryption Test Utility (2048-bit key)
This test decryptor utility is developed to assist Registrars in decrypting the Registrar Enrolment Packets before go-live. This utility works with packets that are encrypted with 2048-bit key (see above for 1024-bit key tool). This utility supports only PFX and PEM formats for private key files. The private key files must be password protected. This tool also supports USB Token with .Net PKCS11 APIs at location "C:\WINDOWS\system32\aetpkss1.dll".
For all the other cases, a modification in the source code of Decryptor Utility is necessary for
This is designed purely as a test tool along with source code provided for initial testing. THIS IS NOT A SUPPORTED SOFTWARE.
Decryption utility binary - last updated 31
Decryption utility source code - last updated 31
Decryption utility "read me" document - last updated 31 Oct, 2011.
KYR+ Sample Application
(OLD VERSION, see below for new version links) This is a sample reference implementation of KYR+ software which works with Aadhaar Enrolment Client 1.1.x versions. This software has the capability to configure fields and capture additional fields specific to registrars. This software saves the captured data into an embedded database. This is built using Visual Studio 2008 using Windows
This is designed purely as a productivity tool to reduce the development time taken by the registrars on the KYR+ aspect. This is released as source code and registrars are free to download, modify, enhance, and use it. THIS IS NOT A SUPPORTED SOFTWARE.
KYR+ sample application (Old Version) - Full source code for version 3.0 - released 15
KYR+ sample application document (Old Version) - Version 3.0 documentation - released 15 Sept, 2010
FI - Bank Response XML Encryption Certificate
The below certificate should be used for encrypting the response XML before placing them in SFTP INBOX of UIDAI.
Certificate Detail |
Expiry Date |
---|---|
5 Aug 2015 |
Aadhaar authentication requires the identity data of the resident within the XML (PID block) to be encrypted. AES-256 session key is encrypted using UIDAI's 2048- public key. This page contains all certificates available for the ecosystem.
Sample Java application (both binary and source code zip files) to test Aadhaar authentication can be downloaded from here.
Production Public Key Certificates
Note: Latest production public key certificate (for PID Encryption) will always be available under link: https://uidai.gov.in/images/authDoc/uidai_auth_prod.cer
Certificate Detail |
Expiry Date |
---|---|
30 Nov 2019 |
|
27 Feb 2017 |
|
5 Aug 2015 |
UIDAI Digital Signature
For validating & signature in the UIDAI response
Certificate Detail |
Expiry Date |
---|---|
28 Apr 2026 |
|
27 May 2023 |
|
07 June 2020 |
|
10 June 2017 |
|
29 Jul 2015 |
Staging/Testing Public Key Certificates
Note: Latest staging/testing public key certificate will always be available under link https://uidai.gov.in/images/uidai_auth_stage.cer
Certificate Detail |
Expiry Date |
---|---|
25 Aug 2025 |
|
16 Sept 2020 |
|
22 Sept 2020 |
PreProduction Signature/Encryption Public Key Certificates
Please find the keys below for validating the Digital Signature of UIDAI response XML, and encrypting the PID block of request XML in PreProduction Environment.
Certificate Detail |
Expiry Date |
---|---|
03 May 2026 |
|
16 June 2023 |
|
30 October 2020 |
The URL format for integration and testing Aadhaar authentication service by the external entities: http ://
Test URLs: (remember to append AUA code and first two digits of Aadhaar number)
- Auth URL - http://auth.uidai.gov.in/1.6/
/<1st-digit-of-uid>/<2nd-digit-of-uid>/ - e-KYC URL - http://developer.uidai.gov.in/kyc/1.0/
/<1st-digit-of-uid>/<2nd-digit-of-uid>/ - OTP URL - http://developer.uidai.gov.in/otp/1.6/
/<1st-digit-of-uid>/<2nd-digit-of-uid>/ - BFD URL - http://developer.uidai.gov.in/bfd/1.6/
/<1st-digit-of-uid>/<2nd-digit-of-uid>/
URLs for other API versions:
- Auth2.0 - http://developer.uidai.gov.in/authrd/2.0
- Auth2.5 - http://developer.uidai.gov.in/authserver/2.5
- otp 2.5 - http://developer.uidai.gov.in/uidotp/2.5
- KYC2.0 - http://developer.uidai.gov.in/kyc/2.0
- KYC2.5 - http://developer.uidai.gov.in/uidkyc/2.5
Test Codes:
- AUA Code ("ac" attribute) : "public"
- Sub-AUA Code ("sa" attribute) - "public"
- License Key ("lk" attribute) : You can use any of the following license keys given below. Binary distribution of sample client is shipped with the first one below.
- AUA License Key: MG_g7jJVYUIW7cLYXY5yaqKD6D1TuhjTJdQRRKP1qALVyORrG1pf0QU - allows usage of PI, PA, PFA, BIO-FMR, BIO-FIR, BIO-IIR, OTP, PIN, Indian Language, e-KYC.
- ASA License Key: MFoSig475ZNf8Fex6pRZJvHLubNTxkmJDqa4sUYQ1On-CyRk1ZUa6VM
- BFD URL - http://developer.uidai.gov.in/bfd/1.6/
/<1st-digit-of-uid>/<2nd-digit-of-uid>/ - Public key certificate - See chapter on certificates (UIDAI Certificate Details to be linked)(remember to use Staging/Test certificate for testing and production certificate for production)
- Keystore for digital signature for "public" AUA - Keystore in p12 file format (Remove link). You can request p12 file by writing to This email address is being protected from spambots. You need JavaScript enabled to view it.
Following are the test UIDs and their demographic data. All of them have same bio record as given above. If you have your own Aadhaar number (real one) then you can use that to test too.
uid=999941057058
name=Shivshankar Choudhury
dob=13-05-1968
dobt=V
gender=M
phone=2810806979
email=This email address is being protected from spambots. You need JavaScript enabled to view it.
street=12 Maulana Azad Marg
vtc=New Delhi
subdist=New Delhi
district=New Delhi
state=New delhi
pincode=110002
uid=999971658847
name=Kumar Agarwal
dob=04-05-1978
dobt=A
gender=M
phone=2314475929
email=This email address is being protected from spambots. You need JavaScript enabled to view it.
building=IPP, IAP
landmark=Opp RSEB Window
street=5A Madhuban
locality=Veera Desai Road
vtc=Udaipur
district=Udaipur
state=Rajasthan
pincode=313001
uid=999933119405
name=Fatima Bedi
dob=30-07-1943
dobt=A
gender=F
phone=2837032088
email=This email address is being protected from spambots. You need JavaScript enabled to view it.
building=K-3A Rampur Garden
vtc=Bareilly
district=Bareilly
state=Uttar Pradesh
pincode=243001
uid=999955183433
name=Rohit Pandey
dob=08-07-1985
dobt=A
gender=M
phone=2821096353
email=This email address is being protected from spambots. You need JavaScript enabled to view it.
building=603/4 Vindyachal
street=7TH Road Raja Wadi
locality=Neelkanth Valley
poname=Ghatkopar (EAST)
vtc=Mumbai
district=Mumbai
state=Maharastra
pincode=243001
uid=999990501894
name=Anisha Jay Kapoor
gender=F
dob=01-01-1982
dobt=V
building=2B 203
street=14 Main Road
locality=Jayanagar
district=Bangalore
state=Karnataka
pincode=560036
Test UID Creation Process
If you want to make use of your own UIDs (for testing services like e-KYC), you can request for creation of a test UID by writing to This email address is being protected from spambots. You need JavaScript enabled to view it.from your registered e-mail id (email id registered for the UID which is mandatory). You should not request for a test UID for another person. Please send filled-in consent form (link Staging consent form pdf attached) duly signed by the applicant. .
Test UID creation process is time consuming and you should provide minimum 20 days for the activity to get completed. Any follow ups after 20 days, should be done to the above mentioned mail id ONLY. Please note that, the test UIDs will be created at UIDAI's discretion and UIDAI reserves the rights to deny any such requests for any reasons which will not be disclosed to the requester
This page provides guidelines for handling API errors within the application. While developing applications, AUAs need to decide how to handle the errors gracefully and provide resident/operator friendly messages. Simply showing the error on screen is not helpful. This document is an attempt to provide guidelines for doing better error handling.
Any other information regarding errors, please contact auth support team of UIDAI at This email address is being protected from spambots. You need JavaScript enabled to view it..
API Error Code |
Description |
Provision Required in the Application |
Suggested Message to the User |
Suggested instructions to the user |
Probable Reasons |
---|---|---|---|---|---|
100 |
"Pi" (basic) attributes of demographic data did not match |
User should be allowed to |
Please re-enter your <name, |
Ensure correct Aadhaar Information is entered. |
One or more personal information attributes not matching. |
200 |
"Pa" (address) attributes of demographic data did not match |
User should be allowed to |
Please re-enter your <co (care of), house, street, lm (land mark), loc (locality), |
Ensure correct Aadhaar Information is entered.
|
One or more personal address attributes not matching. |
300 |
Biometric data did not match |
User should be allowed to give his finger prints "n" number of times. N should be configurable and should be set as per application requirement. (E.g. For Banking Applications it can be set at a maximum of 5 times) |
Please give your finger prints again. |
Ensure correct Aadhaar number is entered and try authenticating again with another finger; ensure finger is placed correctly; ensure fingers are clean; ensure finger is not very dry; ensure fingerprint scanner is clean.
After repeated failure, if the resident is genuine, exception handling provision would need to be followed to provide service.
Please contact UIDAI helpdesk to inform about the issue and to understand the steps for the
|
Finger print is not given properly, scanner has some dust accumulated, fingers were wet, position of finger not appropriate, scanned finger NFIQ not good |
310 | Duplicate fingers used | Application should prompt user to try again with distinct fingers. | Please try again with distinct fingers. | Error occurs when same finger is sent as two or more separate records within same request. For two-finger auth, if resident puts same finger again, then this happens. | |
311 | Duplicate Irises used | Application should prompt user to try again with distinct irises. | Please try again with distinct irises. | Error occurs when same iris is sent as two or more separate records within same request. | |
312 | FMR and FIR cannot be used in same transaction | Application should ensure that authentication request does not mix FMR and FIR in the same transaction e.g. in case of two finger authentication, data for two distinct fingers should either be sent in FMR format or in FIR format. | Technical Exception <No> | Contact technical helpdesk. | Auth packet cannot mix fingerprint "image" records (FIR) and fingerprint "minutiae" records (FMR). AUA app should choose either one or another. FMR is recommended. |
313 | Single FIR record contains more than one finger | Application should prompt user to try again by placing single finger. | Please try again by placing Single finger on the authentication device. | As per ISO spec, one FIR can contain one or more finger images within itself (like slap, etc). UIDAI currently supports single finger record only. If there is a requirement to send 2 fingers, 2 different biometric records should be sent. | |
314 | Number of FMR/FIR should not exceed 10 | Application should ensure that one auth request should not contain more than 10 FMR/FIR records. | Auth Request has more than 10 finger records | ||
315 | Number of IIR should not exceed 2 | Application should ensure that one auth request should not contain more than 2 IIR records. | Auth Request has more than 2 iris records | ||
400 | "OTP" validation failed | Application should have provision for allowing user to provide OTP value again and after some retries (configurable) option to generate OTP again. | Please provide correct OTP value. | If there are repeated failures user is advised to generate new OTP and send the authentication request using the new OTP. | Incorrect OTP value is entered. Input not matching with the value in CIDR. |
401 | "Tkn" validation failed | Application should derive the value of |
Provided "Tkn" details are not matching with registered values in CIDR. | ||
500 |
Invalid |
Application should not have hard coded digital certificate information. It should be configurable.
|
Technical Exception <No> Note: Application can throw Auth API error code number on screen. So that contact centre or application support helpline can understand the reason. |
Contact technical helpdesk. |
Use of wrong digital certificate for encryption of AES-256 Key (session key). |
501 |
Invalid value for "ci" attribute in "Skey" element |
Application should not have hard coded "ci" attribute value. It should be configurable. |
Technical Exception <>
|
|
Ensure that expiry date of UIDAI certificate used for encryption of Skey is specified as "ci" value. |
502 |
Invalid Pid Encryption |
Application should do extensive testing using UIDAI Test Auth Service to ensure compliance with auth API. |
Technical Exception <No>
|
|
Ensure that correct AES encryption has been used. Ensure that AES key used for encryption of "Pid" XML was encrypted and specified as value for Skey. |
503 |
Invalid HMac encryption |
Application should do extensive testing using UIDAI Test Auth Service to ensure compliance with auth API. |
Technical Exception <No>
|
|
Ensure that correct AES encryption has been used. Ensure that AES key used for encryption of "Hmac" was encrypted and specified as Ensure that same AES key is used for encryption of Pid and Hmac. |
504 | Session key re-initiation required due to expiry or key out of sync | Application should have a provision to send full session key and initiate a new session in case of such failure. | Technical Exception <No> | Please try again. | When Synchronized Session Key scheme is used, this can happen if either session is expired (currently configured to max 4 hrs) or if the key goes out of sync. |
505 | Synchronized Skey usage is not allowed | Application should use full |
Technical Exception <No> | Switch to full |
This happens when AUA does not have |
510 |
Invalid Auth XML format |
Application Authentication request should comply to Authentication API latest version and application should validate its structure before sending it to CIDR for authentication. |
Technical Exception <No>
|
Please ensure that the latest recommended API is used for application development. Refer UIDAI website for the latest version of API. If this does not resolve the issue |
Non compliance with supported Authentication API version structure in CIDR. |
511 |
Invalid PID XML format |
Application Authentication request should comply to PID XML format defined in Authentication API latest version and structural validation should be done before encryption of PID XML. |
Technical Exception <No>
|
Please ensure that the latest recommended API is used for application development. Refer UIDAI website for the latest version of API. If this does not resolve the issue |
Non compliance with supported Authentication API version structure in CIDR. |
520 |
Invalid device |
Application should ensure that "
|
Technical Exception <No>
|
|
Using any other value other than "public" (all lower case, no spaces or special char) will result in this error. |
521 | Invalid Finger device ( |
Application should obtain proper code from fingerprint sensor vendor and use it |
Technical Exception <No> |
FDC codes are assigned as part of certification and application developer should use proper |
|
522 | Invalid Iris device ( |
Application should obtain proper code from iris sensor vendor and use it |
Technical Exception <No> |
IDC codes are assigned as part of certification and application developer should use proper |
|
530 |
Invalid authenticator code |
Application should pass valid AUA code in authentication request which is registered with UIDAI. Value of this code should be configurable. |
Technical Exception <No>
|
|
AUA code used in Authentication request is not valid. or AUA code used in the Auth URL is not same as the AUA code used in the Auth XML. |
540 |
Invalid Auth XML version |
Application should pass supported valid API version in authentication request. Value of this should be configurable. |
Technical Exception <No>
|
|
API version used in Auth XML (Authentication request) is either not supported or invalid. |
541 |
Invalid PID XML version |
Application should pass supported valid API PID XML version in authentication request. Value of this should be configurable. |
Technical Exception <No>
|
|
Version of the "Pid" element used In the PID XML (Authentication request) is either not supported or invalid. |
542 |
AUA not authorized for ASA. |
|
|
Ensure the authentication request is being sent through the authorized ASA as per the records of UIDAI. or Please contact UIDAI helpdesk to report the issue and to understand further steps for the |
This error will be returned if AUA and ASA do not have linking in the portal |
543 |
Sub-AUA not associated with "AUA" |
Application should ensure Sub-AUA is added and associated with correct AUA before sending request to CIDR. |
|
Ensure the authentication request is being sent through the associated AUA as per the records of UIDAI. or Please contact UIDAI helpdesk to report the issue and to understand further steps for the |
This error will be returned if Sub-AUA specified in " |
550 |
Invalid "Uses" element attributes |
Application should use valid attributes defined in API for <Uses> tag and validation on Auth request should be done before sending request to CIDR. |
Technical Exception <No>
|
|
Invalid attributes used in Uses tag. This error is typically reported if "bt" attribute has been specified but bio="n" in Uses element. "bt" attribute is required only if bio="y" in Uses element. |
561 |
Request expired ("Pid->ts" value is older than N hours where N is a configured threshold in authentication server) |
AUA application should not store Pid block and in case of application which are using thick client there should be a provision to sync up date with server at start. |
1. In case of Device/Client based Application a. Either device date/time is behind current date/time or request is old. Please try again. 2. In case of a. Technical Exception <No> |
Please verify that the device/client date/time is synchronised with Indian Standard Time (IST) and resend the authentication request. |
Either Device/Client/Server date/time is behind current one or old stored |
562 |
Timestamp value is future time (value specified "Pid->ts" is ahead of authentication server time beyond acceptable threshold) |
AUA application should not store Pid block and in case of application which are using thick client there should be a provision to sync up date with server at start. |
1. In case of Device/Client based Application a. Either device date/time is ahead current date/time or request is old. Please try again. 2. In case of a. Technical Exception <No> |
Please verify that the device/client date/time is synchronised with Indian Standard Time (IST) and resend the authentication request. |
Device/Client/server date/time is ahead than current date/time. |
563 |
Duplicate request (this error occurs when exactly same authentication request was re-sent by AUA) |
Application should ask user to try again. |
Please submit your request again. |
|
If same "Auth XML" is sent more than once to server, then, 2nd and subsequent requests will fail with this error. |
564 |
HMAC Validation failed |
Application should create HMAC using SHA-256 |
Technical Exception <No>
|
|
HMAC is not calculated using API defined algorithm |
565 |
License key has expired |
Application should have a configurable License key management feature through which one can manage Key without changing application. |
Technical Exception <No>
|
|
Current License has expired. |
566 |
Invalid license key |
Application should have a License key management feature through which one can manage Key without changing application. |
Technical Exception <No>
|
|
License key used in application is invalid. |
567 |
Invalid input (this error occurs when some unsupported characters were found in Indian language values, " |
Application should have client/server level checks to stop users to input unsupported characters. |
Technical Exception <No>
|
|
some unsupported characters were found in Indian language values, " |
568 |
Unsupported Language |
Application should have client/server level checks to restrict users to only select language from API supported local Language. |
Technical Exception <No>
|
|
Value of "lang" attribute is not from the list supported by |
569 |
Digital signature verification failed (this means that authentication request XML was modified after it was signed) |
Application should ensure security of data end to end ie. From client/device to CIDR server by using appropriate communication protocol. |
Technical Exception <No>
|
|
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) |
Application should have an independent module for signing Auth XML and certificate should be stored and manage outside of the application. |
Technical Exception <No>
|
|
|
571 |
PIN Requires reset (this error will be returned if |
|
Please reset your PIN in UIDAI |
Please change your default PIN through UIDAI |
This error will be returned if |
572 |
Invalid biometric position (This error is returned if biometric position value - "pos" attribute in "Bio" element - is not applicable for a given biometric type - "type" attribute in "Bio" element.) |
|
Technical Exception <no> |
|
This error is returned if biometric position value - "pos" attribute in "Bio" element - is not applicable for a given biometric type - "type" attribute in "Bio" element |
573 |
Pi usage not allowed as per license |
Application should have a configurable business rule which can restrict the usage of Pi attribute based on AUA license authorization. |
Technical Exception <No> |
|
Pi usage not allowed as per license |
574 |
Pa usage not allowed as per license |
Application can have a client level check to restrict/allow entry of "pa" attribute as per license of AUA. |
Technical Exception <No> |
|
Pa usage not allowed as per license |
575 |
Pfa usage not allowed as per license |
Application can have a client level check to restrict/allow entry of " |
Technical Exception <No> |
|
Pfa usage not allowed as per license |
576 |
FMR usage not allowed as per license |
Application can have a client level check to restrict/allow entry of "FMR" attribute as per license of AUA. |
Technical Exception <No> |
|
FMR usage not allowed as per license |
577 |
FIR usage not allowed as per license |
Application can have a client level check to restrict/allow entry of "FIR" attribute as per license of AUA. |
Technical Exception <No> |
|
FIR usage not allowed as per license |
578 |
IIR usage not allowed as per license |
Application can have a client level check to restrict/allow entry of "IIR" attribute as per license of AUA. |
Technical Exception <No> |
|
IIR usage not allowed as per license |
579 |
OTP usage not allowed as per license |
Application can have a client level check to restrict/allow entry of "OTP" attribute as per license of AUA. |
Technical Exception <No> |
|
OTP usage not allowed as per license |
580 |
PIN usage not allowed as per license |
Application can have a client level check to restrict/allow entry of "PIN" attribute as per license of AUA. |
Technical Exception <No> |
|
PIN usage not allowed as per license |
581 |
Fuzzy matching usage not allowed as per license |
Application can have a client level check to restrict/allow entry of "ms" attribute in pi, pa and |
Technical Exception <No> |
|
Fuzzy matching usage not allowed as per license |
582 |
Local language usage not allowed as per license |
Application can have a client level check to restrict/allow entry of local language attribute in pi, pa and |
Technical Exception <No> |
|
Local language usage not allowed as per license |
584 |
Invalid Pin code in Meta element |
Pincode should have a valid value (in |
Technical Exception <No> |
|
If |
585 | Invalid Geo code in Meta element | Geo code value must be a valid lat.long value in decimal format as per spec (in |
Technical Exception <No> |
If geo code does not have proper format as per spec (decimal representation with |
|
710 |
Missing "Pi" data as specified in "Uses" |
Application should validate |
Technical Exception <No> |
|
Missing "Pi" data as specified in "Uses" |
720 |
Missing "Pa" data as specified in "Uses" |
Same as 710 |
Technical Exception <No> |
|
Missing "Pa" data as specified in "Uses" |
721 |
Missing " |
Same as 710 |
Technical Exception <No> |
|
Missing " |
730 |
Missing PIN data as specified in "Uses" |
Same as 710 |
Technical Exception <No> |
|
Missing PIN data as specified in "Uses" |
740 |
Missing OTP data as specified in "Uses" |
Same as 710 |
Technical Exception <No> |
|
Missing OTP data as specified in "Uses" |
800 |
Invalid biometric data |
AUA to review biometric device being used and whether templates are ISO compliant. |
Technical Exception <No> |
|
FMR value is not ISO compliant bad header or FIR/IIR value is not compliant, or templates could not be extracted for the given FIR/IIR for matching purposes. |
810 |
Missing biometric data as specified in "Uses" |
Same as 710 |
Technical Exception <No> |
|
Missing biometric data as specified in "Uses" |
811 |
Missing biometric data in CIDR for the given Aadhaar number |
|
Your Biometric data is not available in CIDR. |
Ensure correct Aadhaar number is entered and try authenticating again.
After repeated failure, if the resident is genuine, exception handling provision would need to be followed to provide service.
Please contact UIDAI helpdesk to inform about the issue and to understand the steps for the
|
|
812 |
Resident has not done "Best Finger Detection". Application should initiate BFD application to help resident identify their best fingers. See Aadhaar Best Finger Detection API specification. |
|
You have not done best finger detection so kindly proceed with the BFD process for successful authentication. |
Refer Aadhaar Best Detection API specifications for details on the BFD process. |
Resident has not done "Best Finger Detection". |
820 |
Missing or empty value for "bt" attribute in "Uses" element |
Same as 710 |
Technical Exception <No> |
|
Missing or empty value for "bt" attribute in "Uses" element |
821 |
Invalid value in the "bt" attribute of "Uses" element |
Same as 710 |
Technical Exception <No> |
|
Invalid value in the "bt" attribute of "Uses" element |
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) |
Application should validate that User |
Technical Exception <No> |
|
All factors of Auth are optional. Hence, it is possible to attempt an auth without specify any values for any of the factors Pi, Pa, Pfa, Bio or Pv. If none of these elements have any value that can be used for authentication purposes, then, this error will be reported. |
902 |
Invalid "dob" value in the "Pi" element (this corresponds to a scenarios wherein "dob" attribute is not of the format "YYYY" or "YYYY-MM-DD", or the age of resident is not in valid range) |
Application should have a client level check to check dob date format and age business rules specified (Current Rule is that age should not be less than 0 and greater than 150 years) |
Please enter dob in specified date format or enter age in specified range. |
Re-enter the date of birth or age and resend a new authentication request. |
"dob" attribute is not of the format "YYYY" or "YYYY-MM-DD", or the age of resident is not in valid range. |
910 |
Invalid "mv" value in the "Pi" element |
Same as 710 |
Technical Exception <No> |
|
|
911 |
Invalid "mv" value in the " |
Same as 710 |
Technical Exception <No> |
|
|
912 |
Invalid "ms" value |
Same as 710 |
Technical Exception <No> |
|
|
913 |
Both "Pa" and " |
Same as 710 |
|
|
Attempt to use Pa and |
930-939 |
Technical error that are internal to authentication server |
AUA/ASA should call UIDAI tech support. |
Technical Exception <No> |
|
UIDAI server side issues. UIDAI tech support to review the scenario and take appropriate action. |
940 |
Unauthorized ASA channel |
AUA should consult ASA. |
Technical Exception <No> |
|
|
941
|
Unspecified ASA channel |
AUA should consult ASA. |
Technical Exception <No> |
|
|
980 |
Unsupported option |
AUA to review the auth client to check whether any dev feature is being used in prod |
Technical Exception <No> |
|
Currently this error is not reported. Can be used in future. |
996 | Aadhaar Cancelled |
Aadhaar is no in authenticable status. **Please see ACTN attribute for actionable by the resident. |
|||
997 | Aadhaar Suspended | AUA application should have mechanism to handle this scenario as Aadhaar number is valid but its status is not active. | Your Aadhaar number status is not active. Kindly contact UIDAI Helpline. |
Aadhaar is not in **Please see ACTN attribute for actionable by the resident. |
|
998 | Invalid Aadhaar Number 0r Non Availability of Aadhaar data | AUA application should have a client level validation for Aadhaar number validity ie. should be 12 digits and conform to Verhoeff algorithm. | Ensure you have entered correct Aadhaar number. Please retry with correct Aadhaar number after |
Ensure you have entered correct Aadhaar number. Please retry with correct Aadhaar number after |
If client level validations are done then Aadhaar number does not exist in CIDR. Please retry with correct Aadhaar number after sometime. **Please see ACTN attribute for actionable by the resident. |
999 |
Unknown error |
|
Technical Exception <No> |
Please contact |
|