KYC Error Codes: IDFC Bank
This article contains the error codes pertaining to the different types of KYC– Minimal KYC and Aadhaar OTP KYC, facilitated by the IDFC Bank.
NSDL Error Codes
The following table lists the possible error codes returned from NSDL.
Error Codes | Error Descriptions | Instructions |
E-000 | Request received is a HTTP request | Send https request |
E-001 | Request received is a get request | Send post request |
E-100 | Auth XML not parsed properly | Refer to the standard Auth XML format and check all the attributes and their value. If everything seems to be correct, then contact nsdl team for further action. |
E-101 | KYC XML not parsed properly | Refer to the standard KYC XML format and check all the attributes and their value. If everything seems to be correct, then contact nsdl team for further action. |
E-102 | Audit logging in DB failed for request | Make sure that length of transaction id is within the range specified by UIDAI |
E-103 | Audit logging in DB failed for response | Forward the same to NSDL team to check |
E-104 | Audit logging in DB failed for error occurred | Make sure that length of transaction id is within the range specified by UIDAI |
E-105 | KYC XSD Validation failed | Refer to the standard KYC XML format and check all the attributes and their value |
E-106 | KYC Request signature verification failed | Please ensure that private key and mechanism used for signing is correct. Also, ensure that data is not changed after signing |
E-107 | Auth Request signature verification failed | Please ensure that private key and mechanism used for signing is correct. Also, ensure that data is not changed after signing |
E-108 | IP verification failed for entity | Please get your IP address mapped with UIDAI |
E-109 | Blank response received from UIDAI | User can try again after sometime |
E-110 | Unable to decrypt response at KSA | Forward the same to NSDL team to check |
E-111 | KYC response signature verification failed | Forward the same to NSDL team to further check it with UIDAI |
E-112 | BFD XSD validation failed | Refer to the standard BFD XML format and check all the attributes and their value. If everything seems to be correct, then contact NSDL team for further action. |
E-113 | OTP XSD validation failed | Refer to the standard BFD XML format and check all the attributes and their value. If everything seems to be correct, then contact nsdl team for further action. |
E-114 | KYC response XML not parsed properly | Refer to the standard KYC XML format and check all the attributes and their value. If everything seems to be correct, then contact nsdl team for further action. |
E-115 | AUTH response XML not parsed properly | Refer to the standard Auth XML format and check all the attributes and their value. If everything seems to be correct, then contact nsdl team for further action. |
E-116 | Signed Auth XML generation Error | Report the same to NSDL team for further action |
E-117 | Signed KYC XML generation Error | Report the same to NSDL team for further action |
E-118 | Auth response signature verification failed | Forward the same to NSDL team to further check it with UIDAI |
E-119 | ASA\KSA is unable to connect to UIDAI server | Report the same to NSDL team for further action |
E-120 | Auth XSD validation failed | Refer to the standard KYC XML format and check all the attributes and their value |
E-122 | Property file unavailable | Report the same to NSDL team for further action |
E-123 | BFD request XML not parsed properly | Refer to the standard BFD XML format and check all the attributes and their value. If everything seems to be correct, then contact nsdl team for further action. |
E-124 | OTP request XML not parsed properly | Refer to the standard OTP XML format and check all the attributes and their value. If everything seems to be correct, then contact nsdl team for further action. |
E-125 | BFD request signature verification failed | Please ensure that private key and mechanism used for signing is correct. Also, ensure that data is not changed after signing |
E-126 | OTP request signature verification failed | Please ensure that private key and mechanism used for signing is correct. Also, ensure that data is not changed after signing |
E-127 | Signed BFD XML generation error | Report the same to NSDL team for further action |
E-128 | Signed OTP XML generation error | Report the same to NSDL team for further action |
E-129 | BFD response XML not parsed properly | Forward the same to NSDL team to further check it with |
E-130 | OTP response XML not parsed properly | Forward the same to NSDL team to further check it with UIDAI |
E-131 | XML decryption error | Kindly check if the certificate has rights for decryption |
E-132 | Error during KYC request signature verification | Please check for the signature. If signature is there, but still getting error then forward the same to NSDL team for further action |
E-133 | Error during KYC response signature verification | Forward the same to NSDL team |
E-134 | Error during AUTH request signature verification | Please check for the signature. If signature is there, but still getting error then forward the same to NSDL team for further action |
E-135 | Error during AUTH response signature verification | Forward the same to NSDL team |
E-136 | Error during BFD request signature verification | Please check for the signature. If signature is there, but still getting error then forward the same to NSDL team for further Action |
E-137 | Error during OTP request signature verification | Forward the same to NSDL team |
E-138 | Error during KYC XSD Validation | Forward the same to NSDL team |
E-139 | Error during AUTH XSD Validation | Forward the same to NSDL Team |
E-140 | Error during BFD XSD Validation | Forward the same to NSDL team |
E-141 | Error during OTP XSD Validation | Forward the same to NSDL Team |
E-142 | Error during IP verification | Entity is not registered with NSDL, kindly register with NSDL |
E-143 | Response received is E | Forward the same to NSDL team |
E-144 | BFD response signature verification failed | Forward the same to NSDL team to further check it with UIDAI |
E-145 | OTP Signature Tag Missing in Request XML | Refer to the standard of Without sign OTP request. |
E-148 | Ekyc services unavailable | Forward the same to NSDL team to check. |
E-149 | Aadhaar number / Virtual ID validation Failed | Use the valid Aadhaar number and virtual IP for authentication and Ekyc purpose |
E-199 | KSA/ASA/MSA Internal Error | Forward the same to NSDL team |
E-200 | One of the mandatory Sub- Aua element is null | Please check if all the mandatory Sub-Aua elements are present and are not null. |
E-201 | Error while validating strSaCd parameter | Please make sure that strSaCd is present and its value is within the defined limits |
E-203 | Error while validating strAadhaar parameter | Please make sure that strAadhaar i.e Aadhaar number is present and is of correct length |
E-204 | Error while validating strAadhaarName parameter | Please make sure that strAadhaarName i.e Aadhaar card holder's name is present |
E-205 | Error while validating strYear parameter | Please make sure that strYear is present and its value is correct |
E-206 | Error while validating strGender parameter | Please make sure that strGender is present and value is correct |
E-207 | Error while validating strTransId parameter | Please make sure that strTransId is present and its length is within the limits |
E-208 | Error while validating strUDC parameter | Please make sure that strUDC is present |
E-209 | Error while validating strMV parameter | Please make sure that strMV is present and its value lies between 0 to 100 |
E-210 | Value of mvThreshold in property file should be in range 1-100 | As the description says, check for the value of mvThreshold in property file |
E-211 | Error while validating strLang: If strLname is provided then strLang is Mandatory failed for Sub-AUA | If strLname is present, it is mandatory to enter strLang(Local Language code) |
E-212 | Error while validating strLmv parameter. Value should be in range 1- 100(inclusive) | Please check that value of strLmv is in the range 1-100 |
E-213 | DSC signature verification | Please check if signature element is proper |
E-214 | Error while validating strOtp parameter | Please make sure that strOtp is present and value is correct |
E-215 | Error while validating strRequestType parameter | Please make sure that strRequestType is present and value is correct |
E-216 | Error while validating strBioType parameter | Please make sure that strBioType is present and value is correct |
E-217 | Error while validating strFingerOnePos parameter | Please make sure that strFingerOnePos is present and value is correct |
E-218 | Error while validating strFingerTwoPos parameter | Please make sure that strFingerTwoPos is present and value is correct |
E-219 | Error while validating strMS parameter | Please make sure that strMS is present and value is correct (E or P) |
E-220 | Blank Signature Tag Exception | Please make sure that AUA/KUA Code is present in the Signature Tag for IP Verification for ASA/KSA Signing |
E-221 | Incorrect OTP Version | Please make sure that the OTP Version is 1.6 for generating verification code |
E-222 | Error during MOU Request Signature Verification | Please check for the signature. If signature is there, but still getting error then forward the same to NSDL team for further action |
E-223 | Error during MOU Response Signature Verification | Forward the same to NSDL team |
E-224 | Error during MOU XSD Validation | Forward the same to NSDL team |
E-225 | MOU XSD Validation Failed | Refer to the standard MOU XML format and check all the attributes and their value |
E-226 | MOU Request Signature Verification Failed | Please ensure that private key and mechanism used for signing is correct. Also, ensure that data is not changed after signing |
E-227 | MOU Response Signature Verification Failed | Forward the same to NSDL team to further check it with UIDAI |
E-228 | MOU XML Not Parsed Properly | Refer to the standard MOU XML format and check all the attributes and their value. If everything seems to be correct, then contact nsdl team for further action. |
E-229 | MOU Response XML Not Parsed Properly | Refer to the standard MOU XML format and check all the attributes and their value. If everything seems to be correct, then contact nsdl team for further action. |
E-230 | Error during DSC signature verification for Sub-AUA | Forward the same to NSDL team |
E-231 | Signed MOU XML Generation Error | Report the same to NSDL team for further action |
E-232 | RESIDENT AUTH XML Not Parsed Properly | Refer to the standard Auth XML format and check all the attributes and their value. If everything seems to be correct, then contact nsdl team for further action. |
E-233 | OPERATOR AUTH XML Not Parsed Properly | Refer to the standard Auth XML format and check all the attributes and their value. If everything seems to be correct, then contact nsdl team for further action. |
E-234 | MOU Signature Tag Missing in Request XML | Refer to the standard of without sign MUA request. |
E-235 | Request Signature Verification Failed | Please ensure that private key and mechanism used for signing is correct. Also check if proper certificate is mapped on the Server. |
E-236 | Error during Request Signature Verification | Please check for the signature. If error exists then check if public certificate is present on the server or if data is getting altered after signing else forward the same to NSDL |
E-237 | Error during KYC Response Encryption | Please check with NSDL e-Gov. |
E-145 | OTP Signature Tag Missing in Request XML | Refer to the standard of without sign OTP request. |
E-555 | Duplicate transaction id error | Please use unique transaction id |
E-563 | Read timeout while connecting to UIDAI | User can try again after sometime |
UIDAI - AUA Error Codes
The following table lists the possible error codes returned from UIDAI - Authentication User Agency.
Error Codes | Sub Error Codes | Error Descriptions |
100 | Pi Mismatch | |
110 | Aadhaar number does not have verified mobile/email | |
111 | Aadhaar number does not have verified mobile | |
112 | Aadhaar number does not have both email and mobile. | |
113 | Aadhaar Number doesn’t have verified email ID. | |
114 | Aadhaar Number doesn’t have verified Mobile Number. | |
115 | Aadhaar Number doesn’t have verified email and Mobile. | |
200 | Pa Mismatch | |
300 | Bio Mismatch | |
310 | Duplicate Finger | |
311 | Duplicate Iris | |
312 | Mixed FIR FMR | |
313 | FIR Finger Exceeded | |
314 | FIR Record Exceeded | |
315 | IIR Record Exceeded | |
316 | FID Record exceeded | |
330 | Biometrics Locked | |
331 | ||
400 | OTP Validation Failed | |
401 | TKN Validation Failed | |
402 | txn value did not match with txn value used in Request OTP API | |
500 | Invalid Skey Encryption | |
501 | Invalid ci Attribute | |
502 | Invalid Pid Encryption | |
503 | Invalid HMAC Encryption | |
504 | Unsynced Session Key | |
505 | Synchronized Skey Disallowed | |
510 | Invalid Auth /Otp XML | |
511 | Invalid Pid XML | |
512 | Invalid Aadhaar holder consent in rc attribute of Auth. | |
513 | Invalid Protobuf Format | |
514 | Invalid UID token in input. | |
515 | Invalid VID Number in input. | |
517 | Expired VID is used in input. | |
520 | Invalid tid value. | |
521 | Invalid Finger Device | |
522 | Invalid Iris Device | |
523 | Invalid ts attribute. Either it is not in correct format or is older than 20 min. | |
524 | Invalid mi code under Meta tag | |
527 | Invalid mc code under Meta tag | |
528 | Device - Key Rotation policy,The device certificate used in the request is not meeting the UIDAI key rotation policy guidelines. | |
530 | Invalid AUA Code | |
531 | Invaild Sub AUA | |
540 | Invalid AuthXML Version | |
541 | Invalid PidXML Version | |
542 | ASA Unauthorized AUA | |
543 | SubAUA AUA UnAssociated | |
550 | Invalid Uses Attributes | |
551 | Invalid tid value | |
552 | WADH Validation failed | |
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 Certificat has expired | |
560 | DP Master Certificate has expired | |
561 | Expired Pid Request | |
562 | Future Timestamp Value | |
563 | Duplicate Auth Request | |
564 | HMAC Validation Failed | |
565 | License Key Expired | |
566 | Invalid License Key | |
567 | Invalid Language Character | |
568 | Unsupported Language | |
569 | Unverified Digital signature | |
570 | Invalid Digital Certificate | |
571 | PIN Requires Reset | |
572 | Invalid Biometric Position | |
573 | Pi Usage Disallowed | |
574 | Pa Usage Disallowed | |
575 | Pfa Usage Disallowed | |
576 | FMR Usage Disallowed | |
577 | FIR Usage Disallowed | |
578 | IIR Usage Disallowed | |
579 | OTP Usage Disallowed | |
580 | PIN Usage Disallowed | |
581 | FuzzyMatch Usage Disallowed | |
582 | Local Language Disallowed | |
584 | Invalid Meta Pincode | |
585 | Invalid Meta Geocode | |
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 | |
591 | BFD usage is not allowed as per license. | |
710 | Pi Missing | |
720 | Pa Missing | |
721 | Pfa Missing | |
730 | PIN Missing | |
740 | OTP Missing | |
800 | Invalid Biometric Data | |
810 | Missing Biometric Data | |
811 | Missing CIDR Biometric | |
812 | Best Finger Detection (BFD) Required | |
820 | Missing bt | |
821 | Invalid bt | |
822 | Invalid value in the bs attribute of Bio element within Pid. | |
901 | Auth Data Absent | |
902 | Invalid dob Value | |
910 | Invalid Pi mv | |
911 | Invalid Pfa mv | |
912 | Invalid ms Value | |
913 | Both Pa pfa Present | |
914 | Face alone is of allowed as biometric modality. You should send face along | |
915 | Face auth is not allowed for this age of resident. | |
916 | Invalid face Image format in input. | |
917 | Invalid face capture type. | |
930 | Technical Error at UIDAI - Biometric SDK error | |
931 | Device vender is not whitelisted at UIDAI | |
932 | Technical Error at UIDAI - Audit error | |
933 | Technical Error at UIDAI - BI Related Technical Error | |
934 | Technical Error at UIDAI - OTP store error | |
935 | Technical Error at UIDAI - Skey store error | |
936 | Technical Error at UIDAI - PIN store error | |
937 | Technical Error at UIDAI - Digital signature error | |
938 | Technical Error at UIDAI - License store error | |
939 | Technical Error at UIDAI - Onboarding error | |
940 | Unauthorized ASA Channel | |
941 | Unspecified ASA Channel | |
950 | OTP store related technical error | |
951 | Biometric lock related technical error | |
952 | OTP Flooding - Please avoid trying to generate the OTP multiple times within short time. | |
953 | Exeeded maximum OTP generation - 5 Times | |
980 | Unsupported Option | |
995 | Aadhaar suspended by competent authority. | |
996 | Aadhaar Cancelled | |
996 | A401 | Aadhaar cancelled being a duplicate. Resident shall use valid Aadhaar. |
996 | A402 | Aadhaar cancelled due to disputed enrolment. Shall re-enrol if resident doesn’t have a valid Aadhaar. |
996 | A403 | Aadhaar cancelled due to technical Issues. Resident shall contact UIDAI contact centre. |
996 | A404 | Aadhaar cancelled due to disputed enrolment (BE). Shall re-enrol if resident doesn’t have a valid Aadhaar. |
996 | A405 | Aadhaar cancelled due to errorneous enrolment (Iris). Shall re-enrol if resident doesn’t have a valid Aadhaar. |
997 | Aadhaar Suspended | |
997 | A301 | Aadhaar suspended due to inactivity. Resident shall follow the Reactivation process. |
997 | A302 | Aadhaar suspended due to Biometrics integrity issue. Resident shall visit Permanent Enrolment Centre with document proofs for update. |
997 | A303 | Aadhaar suspended due to Demographic integrity issue. Resident shall visit Permanent Enrolment Centre / UIDAI website with document proofs for update. |
997 | A304 | Aadhaar suspended due to Address dispute. Resident shall visit Permanent Enrolment Centre with document proofs for update. |
997 | A305 | Aadhaar suspended due to Photo dispute. Resident shall visit Permanent Enrolment Centre with document proofs for update. |
997 | A306 | Aadhaar suspended due to Age dispute. Resident shall update the age. |
997 | A307 | Aadhaar suspended since child has not updated biometrics after age of 5. Resident shall update the biometrics. |
997 | A308 | Aadhaar suspended since resident has not updated biometrics after age of 15. Resident shall update the biometrics. |
997 | A309 | Aadhaar is locked by resident. Resident shall follow the Un-locking process. |
998 | Unavailable Aadhaar Number | |
998 | A201 | Aadhaar number is incorrect. Resident shall use correct Aadhaar. |
998 | A202 | Authentication temporarily not available, resident shall retry after sometime. |
999 | Unknown Error | |
E-000 | Bad Request HTTP Received | |
E-001 | Bad Request GET Received | |
E-100 | Unparsable Auth XML | |
E-101 | Unparsable KYC XML | |
E-102 | Request DB Auditing Failed | |
E-103 | Response DB Auditing Failed | |
E-104 | Error DB Auditing Failed | |
E-105 | KYC XSD Validation Failed | |
E-106 | KYC Request Signature Verification Failed | |
E-107 | Auth Request signature verification failed | |
E-108 | AUA IP Verification Failed at UIDAI | |
E-109 | Blank UIDAI Response | |
E-110 | KSA Response Decryption Error | |
E-111 | KYC Response Signature Verification Failed | |
E-112 | BFD XSD validation failed | |
E-113 | OTP XSD validation failed | |
E-114 | Unparsable KYC Response XML | |
E-115 | Unparsable Auth Response XML | |
E-116 | Signed Auth XML Generation Error | |
E-117 | Signed KYC XML Generation Error | |
E-118 | Auth response signature verification failed | |
E-119 | ASA-UIDAI Connection Error | |
E-120 | Auth XSD validation failed | |
E-122 | Property file unavailable | |
E-123 | Unparsable BFD Request XML | |
E-124 | Unparsable OTP Request XML | |
E-125 | BFD request signature verification failed | |
E-126 | OTP request signature verification failed | |
E-127 | Signed BFD XML | |
E-128 | Signed OTP XML | |
E-129 | Unparsable BFD Response XML | |
E-130 | Unparsable OTP Response XML | |
E-131 | XML Decryption Certificate Error | |
E-132 | KYC Request Signature Verification Error | |
E-133 | KYC Response Signature Verification Error | |
E-134 | Auth Request Signature Verification Error | |
E-135 | Auth Response Signature Verification Error | |
E-136 | BFD Request Signature Verification Error | |
E-137 | OTP Request Signature Verification Error | |
E-138 | KYC XSD Validation Error | |
E-139 | Auth XSD Validation Error | |
E-140 | BFD XSD Validation Error | |
E-141 | OTP XSD Validation Error | |
E-142 | AUA IP Verification Failed at NSDL | |
E-143 | E Response Received | |
E-144 | BFD Response Signature Verification Failed | |
E-145 | OTP Signature Tag Missing in Request XML | |
E-199 | KSA/ASA Internal Error | |
E-200 | Mandatory Sub-Aua Null Element | |
E-201 | strSaCd Parameter Validation Error | |
E-203 | strAadhaar Parameter Validation Error | |
E-204 | strAadhaarName Parameter Validation Error | |
E-205 | strYear Parameter Validation Error | |
E-206 | strGender Parameter Validation Error | |
E-207 | trTransId Parameter Validation Error | |
E-208 | strUDC Parameter Validation Error | |
E-209 | strMV Parameter Validation Error | |
E-210 | mvThreshold Value not in range 1-100 | |
E-211 | strLang Parameter Validation Error | |
E-212 | strLmv Value not in range 1-100 | |
E-213 | Signing Certificate Verification Failed | |
E-214 | strOtp Parameter Validation Error | |
E-215 | strRequestType Parameter Validation Error | |
E-216 | strBioType Parameter Validation Error | |
E-217 | strFingerOnePos Parameter Validation Error | |
E-218 | strFingerTwoPos Parameter Validation Error | |
E-219 | strMS Parameter Validation Error | |
E-220 | Blank Signature Tag Exception | |
E-221 | Incorrect OTP Version | |
E-222 | Error during MOU Request Signature Verification | |
E-223 | Error during MOU Response Signature Verification | |
E-224 | Error during MOU XSD Validation | |
E-225 | MOU XSD Validation Failed | |
E-226 | MOU Request Signature Verification Failed | |
E-227 | MOU Response Signature Verification Failed | |
E-228 | MOU XML Not Parsed Properly | |
E-229 | MOU Response XML Not Parsed Properly | |
E-230 | Signing Certificate Verification Error | |
E-231 | Signed MOU XML Generation Error | |
E-232 | RESIDENT AUTH XML Not Parsed Properly | |
E-233 | OPERATOR AUTH XML Not Parsed Properly | |
E-234 | MOU Signature Tag Missing in Request XML | |
E-235 | Request Signature Verification Failed | |
E-236 | Error during Request Signature Verification | |
E-237 | Error during KYC Response Encryption | |
E-300 | Some server error while processing the request | |
E-301 | Invalid API Version | |
E-302 | Invalid Client Details | |
E-303 | Client Licence key expire | |
E-304 | Request XML not available. | |
E-307 | Failed to connect UIDAI Server! Please try after some time | |
E-308 | Failed to parse Response XML | |
E-555 | Duplicate transaction id error | |
E-563 | UIDAI Connection Read Timeout | |
E-999 | KSA Internal Error | |
K-100 | Resident Authentication Failed | |
K-200 | Resident Data Unavailable | |
K-540 | Invalid KYC XML | |
K-541 | KYC API Invalid | |
K-542 | Invalid rc Attribute | |
K-543 | Invalid ts Attribute | |
K-544 | Invalid ra Attribute | |
K-545 | Resident Opted Out | |
K-546 | Invalid value for pfr attribute | |
K-547 | Invalid value for wadh attribute within PID block | |
K-550 | Invalid Uses Element | |
K-551 | Invalid Txn namespace | |
K-552 | Invalid License Key | |
K-569 | Unverified Digital Signature | |
K-570 | Invalid Digital Certificate | |
K-600 | Unauthorized KUA | |
K-601 | Unauthorized KSA | |
K-602 | KUA Encryption Key Unavailable | |
K-603 | KSA Encryption Key Unavailable | |
K-604 | KSA disallowed Signing | |
K-605 | Neither KUA key nor KSA encryption key are available | |
K-955 | Technical Error | |
K-956 | - | |
K-999 | Unknown Error | |
ASG003 | Error processing authentication request | |
ASG004 | Invalid request from AUA | |
ASG005 | Error referencing Audit component | |
ASG011 | Error processing OTP request | |
ASG021 | Error processing BFD request | |
ASG031 | Error processing KYC request | |
ASA001 | Invalid Auth XML | |
ASA002 | AUA configuration not found | |
ASA003 | Crypto configuration not found | |
ASA004 | ASA configuration not found | |
ASA005 | UIDAI certificate configuration not found | |
ASA006 | Request XML signature verification failed | |
ASA007 | Error preparing XML for ASA signing | |
ASA008 | Invalid CryptoType configured | |
ASA009 | Error signing CIDR request | |
ASA010 | Invalid Aadhaar number | |
ASA011 | No response from CIDR | |
ASA012 | Blank response from CIDR | |
ASA013 | Error connecting to CIDR | |
ASA014 | Error connecting to CIDR - Connection timeout | |
ASA015 | Error reading response from CIDR - Socket timeout | |
ASA016 | Error sending / receiving data from CIDR | |
ASA017 | Invalid response from CIDR | |
ASA018 | Error deserializing CIDR response | |
ASA019 | Error accessing Audit data storage | |
ASA020 | Invalid KYC XML | |
ASA021 | Invalid Auth XML in |
|
ASA022 | Error signing Auth XML in |
|
ASA023 | Error serializing Kyc XML after Signing | |
ASA024 | Error initializing Kyc decryption engine | |
ASA025 | Error decryptng |
|
ASA026 | Error serializing decrypted |
|
ASA030 | Invalid OTP XML | |
ASA031 | Invalid Mobile number | |
ASA040 | Invalid BFD XML | |
ASA051 | Authentication not allowed. Access denied | |
ASA052 | Demographic Authentication not allowed. Access denied | |
ASA053 | KYC not allowed. Access denied | |
ASA054 | OTP not allowed. Access denied | |
ASA055 | BFD not allowed. Access denied | |
ASA056 | Mobile Update (MOU) not allowed. Access denied | |
ASA060 | Invalid MOU Xml | |
ASA061 | Invalid |
|
ASA062 | Invalid Oad data | |
ASA063 | Error preparing |
|
ASA064 | Error preparing Oad xml for signing | |
ASA065 | Error Signing |
|
ASA066 | Error Signing Oad | |
ASA067 | Error Preparing |
|
ASA068 | Error Signing |
|
ASA069 | Invalid Resident Aadhaar Number | |
ASA070 | Invalid Operator Aadhaar Number | |
ASA071 | Resident Aadhaar Number and Operator Aadhaar Number cannot be same | |
ASA777 | Signature element not found to validate signature | |
AGW001 | Error loading settings | |
AGW004 | Invalid request Xml | |
AGW021 | No response from ASA | |
AGW022 | Blank response from ASA | |
AGW023 | Error connecting to ASA | |
AGW024 | Error connecting to ASA - Connection timeout | |
AGW025 | Error reading response from ASA - Socket timeout | |
AGW026 | Error sending / receiving data from ASA | |
AGW027 | Invalid response from ASA |
UIDAI - SRDH Error Codes
The following table lists the possible error codes returned from UIDAI - State Resident Data Hub.
Error Codes | Error Descriptions |
800 | Internal Server Error |
801 | Error in creating AUA service Request |
802 | Error in parsing AUA request XML |
803 | Error in parsing AUA response xml |
804 | Invalid Sub AUA/ License Key |
805 | Sub AUA license expired |
806 | Domain ID not present |
807 | Invalid Aadhaar ID or Aadhaar ID/VID/UID Token length mismatch |
808 | Invalid name (In case the name field contains any special characters or numbers in it this error code will returned by SRDH. Valid name will be as registered with UIDAI) |
809 | Invalid email (Valid email id example: [email protected]) |
810 | Invalid Phone (Phone number should contain exactly 10 digits) |
811 | Missing input (In case of any of the mentioned attribute is missing SRDH will generate this error code) |
812 | In case of demographic authentication one should provide either name, phone or email along with uid field otherwise this error code will be generated by SRDH |
813 | Biometric Input is Missing |
814 | Duplicate Transaction ID |
815 | Invalid transaction ID |
816 | Invalid UDC |
817 | Error in creating OTP service request |
818 | Missing OTP Request Type |
819 | Invalid uses flag values |
820 | Missing langCode input |
821 | Invalid domain ID length |
822 | Invalid input for OTP Request Type |
827 | System Admin Error |
828 | Pin Request is not yet Supported by UIDAI |
829 | Department Code Not Present |
830 | Invalid Department Code |
831 | Invalid TimeStamp Value |
832 | Invalid Iris Type |
833 | Invalid Iris Count |
834 | Invalid Finger Record Type |
835 | Invalid Finger Record Count |
836 | Invalid Terminal Id |
837 | Invalid txn value |
838 | Services barred for one minute after successful transaction |
839 | NPCI request creation failed |
840 | Unable to connect to AUA. Try after some time |
841 | SUBAUA unsupported for TXN version |
842 | Expired or Future SUBAUA TXN Id |
843 | Invalid Reference Key refKey |
844 | Aadhaar Data Vault Error |
845 | Unknown Reference Key refKey |
846 | ADV RefKey service request creation Error |
847 | Invalid VID |
848 | Invalid UID Token |
851 | Missing input (In case of any of the mentioned attribute is missing SRDH will generate this error code) |
901 | Error in creating KUA service Request |
902 | Error in parsing KUA request XML |
903 | Error in parsing KUA response xml |
904 | Consent value has not set or it is set to ‘n’ |
905 | Invalid lData value |
906 | Invalid MEC value |
907 | Invalid DE value |
908 | Invalid PFR value |
910 | Invalid RA value |
M-301 | Request XML not Received at SRDH. Please Try Again. |
M-302 | XSD Validation Failed at SRDH. Please Try Again. |
M-303 | Mandatory Sub-Aua Null Element at SRDH |
M-304 | Mandatory Sub-Aua Blank Element at SRDH |
M-305 | Invalid sa Parameter Received at SRDH |
M-306 | ASA Connection Read Timeout. Please Try Again. |
M-307 | Unparsable Auth Request XML at SRDH. Please Try Again. |
M-308 | No Signature in Request XML Received at SRDH. Please Try Again. |
M-309 | Improper Response Received from ASA. Please Try Again. |
M-310 | Unparsable Auth Response at SRDH. Please Try Again. |
M-311 | Unverified Signature in Request XML Received at SRDH. Please Try Again. |
M-312 | Servier security error. Please try again later. |
M-313 | Unknown ASA host. |
M-314 | AUA to SRDH Connection Failure |
M-315 | Connection to NPCI was not established or Request time out |
M-316 | Missing Txn Rule |
M-333 | SRDH Internal Error. Please Try Again. |
ADV_101 | Missing or Empty Input |
ADV_102 | Internal ADV Error |
ADV_103 | UID Decryption Error |
ADV_104 | UID Encryption Error |
ADV_105 | UID AES Encryption Error |
ADV_501 | ADV Request Creation Error |
ADV_502 | ADV Connection Exception |
ADV_503 | ADV Service Exception |