ONLINE WHERE YOUR AADHAAR CARD USED FOR AUTHENTICATION, AADHAAR BANK ACCOUNT LINKING STATUS, AND AADHAAR AUTHENTICATION HISTORY ONLINE.
- OPEN UIDAI Official Website http://uidai.gov.in.
- CLICK ON ENROLMENT AND UPDATION.
- You find it in Aadhaar Services Section, Click on it.
- CLICK ON Aadhaar Authentication History on the Page.
- Now enter your 12 Digit Aadhaar Number in the box.
- Enter Capcha Number thers after entering Aadhaar Number.
- Click on Generate OTP.
- Authentication Type select All.
- Select Date Range ( Maximum 6 Months).
- Number of Records select 50.
- Enter OTP there.
- You Get the Details of 50 usages as List.
Check your Aadhaar and Bank Account Linking Status DIRECT LINK CLICK HERE
AADHAR ERRORS DETAILS
Error Reference Document |
||
API Error | Description | Suggested Instructions to the user |
100 |
"Pi" (basic) attributes of demographic data did not match |
The provided Personal Identity information didn't match. Please re-enter your <name, lname, gender, dob, dobt, age, phone, email> details correctly. |
200 |
"Pa" (address) attributes of demographic data did not match |
The provided Personal Address information didn't match.Please re-enter your <co (care of), house, street, lm (land mark), loc (locality), vtc, subdist, dist, state, pc (postal pin code), po (post office)>. |
300 |
Biometric data did not match |
Ensure correct aadhaar number is entered for authentication Try authenticating using different finger in case of biometric mismatch Follow best practices AUA application must invoke Best Finger Detection to find the best finger for authentication |
310 | Duplicate fingers used | Resident should provide distinct fingers (two different fingers) for "two finger" authentication. |
311 | Duplicate Iris used | Resident should provide distinct fingers (two different Iris) for "two Iris" authentication. |
312 |
FMR and FIR ( Finger Image Record) cannot be used in same transaction | Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
313 | Single FIR ( Finger Image Record)record contains more than one finger |
Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
314 |
Number of FMR(Finger Minutiae Record )/FIR ( Finger Image Record) should not exceed 10 | Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
315 | Number of IIR ( Iris Image Record) should not exceed 2 |
Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
316 |
Number of FID ( Face Image Data )should not exceed 1. |
Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
330 |
Biometrics locked by Aadhaar holder |
Resident must unlock his biometrics by invoking Resident portal or M-Aadhaar and get his biometric unlocked and get himself authenticated |
400 |
"OTP" validation failed |
Resident must ensure that the correct OTP value is provided for authentication . The resident is advised to generate new OTP in case of repeated authentication failures. |
402 | “txn” value did not match with “txn” value used in Request OTP API. |
Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
500 | Invalid Skeyencryption | Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
501 | Invalid value for "ci" attribute in "Skey" element |
Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
502 | Invalid Pid Encryption | Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
503 |
Invalid HMac encryption |
Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
504 | Session key re-initiation required due to expiry or key out of sync |
Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
505 | Synchronized Skey usage is not allowed | Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
510 | Invalid Auth XML format | Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
511 | Invalid PID XML format | Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
512 |
Invalid Aadhaar holder consent in “rc” attribute of “Auth” |
Resident concent to do aadhaar based authentication must be mandatorily taken by the AUA application. Without explicit informed consent of the Aadhaar holder AUA/Sub-AUA application should not call this API |
513 | Invalid Protobuf Format | Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
520 | Invalid “tid” value | Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
521 | Invalid “dc” code under Meta tag | Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
524 | Invalid “mi” code under Meta tag | Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
527 | Invalid “mc” code under Meta tag. | Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
528 | Device - Key Rotation policy | Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
530 |
Invalid authenticator code |
Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
540 | Invalid Auth XML version | Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
541 |
Invalid PID XML version |
Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
542 | AUA not authorized for ASA. | Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
543 |
Sub-AUA not associated with "AUA" |
Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
550 | Invalid "Uses" element attributes | Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
552 | WADH Validation failed | Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
553 |
Registered devices currently not supported. This feature is being implemented in a phased manner. | Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
554 | Public devices are not allowed to be used | Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
555 | rdsId is invalid and not part of certification registry | Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
556 | rdsVer is invalid and not part of certification registry. |
Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
557 | dpId is invalid and not part of certification registry. | Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
558 | Invalid dih | Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
559 | Device Certificate has expired | Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
560 | DP Master Certificate has expired | Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
561 |
Request expired ("Pid- >ts" value is older than N hours where N is a configured threshold in authentication server) |
Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
562 |
Timestamp value is future time (value specified "Pid->ts" is ahead of authentication server time beyond acceptable threshold) | Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
563 |
Duplicate request (this error occurs when exactly same authentication request was re-sent by AUA) | Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
564 | HMAC Validation failed | Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
565 | AUA License key has expired | Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
566 | Invalid non-decryptable license key | Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
567 |
Invalid input (this error occurs when some unsupported characters were found in Indian language values, "lname" or "lav") |
Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
568 | Unsupported Language | Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
569 |
Digital signature verification failed (this means that authentication request XML was modified after it was signed) |
Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
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 an approved Certification Authority) |
Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
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 Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
573 | Pi usage not allowed as per license | Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
574 | Pa usage not allowed as per license | Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
575 | Pfa usage not allowed as per license | Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
576 | FMR usage not allowed as per license | Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
577 | FIR usage not allowed as per license | Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
578 | IIR usage not allowed as per license | Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
579 | OTP usage not allowed as per license | Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
580 | PIN usage not allowed as per license | Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
581 | Fuzzy matching usage not allowed as per license | Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
582 | Local language usage not allowed as per license | Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
586 | FID usage not allowed as per license. | Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
587 | Name space not allowed. | Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
588 | Registered device not allowed as per license | Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
590 | Public device not allowed as per license. | Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
710 | Missing "Pi" data as specified in "Uses" | Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
720 | Missing "Pa" data as specified in "Uses" | Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
721 | Missing "Pfa" data as specified in "Uses" | Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
730 | Missing PIN data as specified in "Uses" | Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
740 | Missing OTP data as specified in "Uses" | Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
800 | Invalid biometric data | Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
810 | Missing biometric data as specified in "Uses" | Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
811 |
Missing biometric data in CIDR for the given Aadhaar number |
Your Biometric data is not available in CIDR. Please contact UIDAI helpdesk to inform about the issue and to understand the steps for the updation of biometric information in CIDR. |
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. |
820 | Missing or empty value for "bt" attribute in "Uses" element |
Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
821 | Invalid value in the "bt" attribute of "Uses" element | Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
822 | Invalid value in the “bs” attribute of “Bio” element within “Pid” |
Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
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) | Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
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) |
Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
910 | Invalid "mv" value in the "Pi" element | Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
911 | Invalid "mv" value in the "Pfa" element | Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
912 | Invalid "ms" value | Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
913 |
Both "Pa" and "Pfa" are present in the authentication request (Pa and Pfa are mutually exclusive) | Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
940 |
Unauthorized ASA channel |
Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
941 | Unspecified ASA channel | Technical Issue with AUA Application. AUA Application must follow the UIDAI API Specification. |
950 |
OTP store related technical error |
Technical Issue at UIDAI end . AUA/Resident can reach UIDAI contact center for more details. Voice @ 1947 and e-Mail “help@uidai.gov.in” |
951 |
Biometric lock related technical error |
Technical Issue at UIDAI end . AUA/Resident can reach UIDAI contact center for more details. Voice @ 1947 and e-Mail “help@uidai.gov.in” |
995 |
Aadhaar suspended by competent authority |
Your Aadhaar number is suspended .AUA/Resident can reach UIDAI contact center for more details. Voice @ 1947 and e-Mail “help@uidai.gov.in” |
996 |
Aadhaar Cancelled |
Your Aadhaar is cancelled , Resident shall visit Permanent Enrolment Centre with document proofs and follow the re-enrollment process.. AUA/Resident can reach UIDAI contact center for more details. Voice @ 1947 and e-Mail “help@uidai.gov.in” . |
997 |
Aadhaar Suspended |
Your Aadhaar is suspended, Resident shall visit Permanent Enrolment Centre with document proofs and follow the enrolment update process. AUA/Resident can reach UIDAI contact center for more details. Voice @ 1947 and e-Mail “help@uidai.gov.in” . |
998 | Invalid Aadhaar Number 0r Non Availability of Aadhaar data | Ensure you have entered correct Aadhaar number. Please retry with correct Aadhaar number after sometime. |
0 comments:
Post a Comment