AUA WEBSERVICES | DST-Gujarat

6. UIDAI Error code with description

o “100” – “Pi” (basic) attributes of demographic data did not match.
o “200” – “Pa” (address) attributes of demographic data did not match.
o “300” – Biometric data did not match.
o “310” – Duplicate fingers used.
o “311” – Duplicate Irises used.
o “312” – FMR and FIR cannot be used in same transaction.
o “313” – Single FIR record contains more than one finger.
o “314” – Number of FMR/FIR should not exceed 10.
o “315” – Number of IIR should not exceed 2.
o “316” – Number of FID should not exceed 1.
o “317” – Number of biometric modalities (Face/Finger/IRIS) should not exceed 2.
o “318” – BFD transaction should not contain other modalities in input.
o “330” – Biometrics locked by Aadhaar number holder.
o “331” – Aadhaar locked by Aadhaar number holder for all authentications.
o “332” – Aadhaar number usage is blocked by Aadhaar number holder.
o “400” – Invalid OTP value.
o “402” – “txn” value did not match with “txn” value of Request OTP API.
o “500” – Invalid encryption of session key.
o “501” – Invalid certificate identifier in “ci” attribute of “Skey”.
o “502” – Invalid encryption of PID.
o “503” – Invalid encryption of Hmac.
o “504” – Session key re-initiation required due to expiry or key out of sync.
o “505” – Synchronized Key usage not allowed for the AUA.
o “510” – Invalid Auth XML format.
o “511” – Invalid PID XML format.
o “512” – Invalid consent value in “rc” attribute of “Auth”.
o “513” – Invalid Protobuf Format
o “514” – Invalid UID token in input.
o “515” – Invalid VID Number in input.
o “517” – Expired VID is used in input.
o “520” – Invalid “tid” value.
o “521” – Invalid “dc” code under Meta tag.
o “524” – Invalid “mi” code under Meta tag.
o “527” – Invalid “mc” code under Meta tag.
o “530” – Invalid authenticator code.
O “531” – SUB-AUA code not mapped in UIDAI.
o “540” – Invalid Auth XML version.
o “541” – Invalid PID XML version.
o “542” – AUA not authorized for ASA. This error will be returned if AUA and ASA do not have
linking in the portal.
o “543” – Sub-AUA not associated with “AUA”. This error will be returned if Sub-AUA specified
in “sa” attribute is not added as “Sub-AUA” in portal.

40
 AUA WEBSERVICES | DST-Gujarat

o “550” – Invalid “Uses” element attributes.

o “552” – Invalid “wadh” element.
o “528” – Device key rotation related issue.
o “553” – Registered devices currently not supported. This feature is being implemented in a
phased manner.
o “554” – Public devices are not allowed to be used.
o “555” – rdsId is invalid and not part of certification registry.
o “556” – rdsVer is invalid and not part of certification registry.
o “557” – dpId is invalid and not part of certification registry.
o “558” – Invalid dih
o “559” – Device Certificate has expired
o “560” – DP Master Certificate has expired
o “561” – Request expired (“Pid->ts” value is older than N hours where N is a configured
threshold in authentication server).
o “562” – Timestamp value is future time (value specified “Pid->ts” is ahead of authentication
server time beyond acceptable threshold).
o “563” – Duplicate request (this error occurs when exactly same authentication request was
re-sent by AUA).
o “564” – HMAC Validation failed.
o “565” – AUA license has expired.
o “566” – Invalid non-decrypt able license key.
o “567” – Invalid input (this error occurs when unsupported characters were found in Indian
language values, “lname” or “lav”).
o “568” – Unsupported Language.
o “569” – Digital signature verification failed (means that authentication request XML was
modified after it was signed).
o “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).
o “571” – PIN requires reset.
o “572” – Invalid biometric position.
o “573” – Pi usage not allowed as per license.
o “574”– Pa usage not allowed as per license.
o “575”– Pfa usage not allowed as per license.
o “576” - FMR usage not allowed as per license.
o “577” – FIR usage not allowed as per license.
o “578” – IIR usage not allowed as per license.
o “579” – OTP usage not allowed as per license.
o “580” – PIN usage not allowed as per license.
o “581” – Fuzzy matching usage not allowed as per license.
o “582” – Local language usage not allowed as per license.
o “586” – FID usage not allowed as per license.
o “587” – Name space not allowed.
o “588” – Registered device not allowed as per license.
o “590” – Public device not allowed as per license.

41
 AUA WEBSERVICES | DST-Gujarat

o “591” – BFD usage is not allowed as per license.

o “710” – Missing “Pi” data as specified in “Uses”.
o “720” – Missing “Pa” data as specified in “Uses”.
o “721” – Missing “Pfa” data as specified in “Uses”.
o “730” – Missing PIN data as specified in “Uses”.
o “740” – Missing OTP data as specified in “Uses”.
o “800” – Invalid biometric data.
o “810” – Missing biometric data as specified in “Uses”.
o “811” – Missing biometric data in CIDR for the given Aadhaar Number/Virtual ID.
o “812” – Aadhaar number holder has not done “Best Finger Detection”. Application should
initiate BFD to help Aadhaar number holder identify their best fingers.
o “820” – Missing or empty value for “bt” attribute in “Uses” element.
o “821” – Invalid value in the “bt” attribute of “Uses” element.
o “822” – Invalid value in the “bs” attribute of “Bio” element within “Pid”.
o “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).
o “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 is not in valid range).
o “910” – Invalid “mv” value in the “Pi” element.
o “911” – Invalid “mv” value in the “Pfa” element.
o “912” – Invalid “ms” value.
o “913” – Both “Pa” and “Pfa” are present in the authentication request (Pa and Pfa are
mutually exclusive).
o “914” – Face alone is of allowed as biometric modality. You should send face along with
another biometric modality like Finger or IRIS or OTP.
o “915” – Face auth is not allowed for this age of resident.
o “916” – Invalid face Image format in input.
o “917” – Invalid face capture type.
o “930 to 939” – Technical error that are internal to authentication server.
o “940” – Unauthorized ASA channel.
o “941” – Unspecified ASA channel.
o “950” – OTP store related technical error.
o “951” – Biometric lock related technical error.
o “980” – Unsupported option.
o “995” – Aadhaar suspended by competent authority.
o “996” – Aadhaar cancelled (Aadhaar is not in authenticable status).
o “997” – Aadhaar suspended (Aadhaar is not in authenticable status).
o “998” – Invalid Aadhaar Number/Virtual ID.
o “999” – Unknown error.

42