ZLD Makes Fool
ZLD Makes Fool
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <Otp uid= tid= ac= sa= ver=
lk=>
<Opts ch=/>
<Signature>Digital signature of AUA</Signature> </Otp>
https://<host>/otp/<ver>/<ac>/<uid[0]>/<uid[1]>/<asalk>
host Aadhaar OTP server address. Actual production server address will be provided to A
Note that production servers can only be accessed through secure leased lines. For develo
and testing purposes, public URL auth.uidai.gov.in can be used. ASA server should ensur
actual URL is configurable.
Next part of the URL otp indicates that this is a OTP Request API call instead of regular
authentication API call. Ensure that this is provided.
ver OTP API version (optional). If not provided, URL points to current version. UIDAI may
multiple versions for supporting gradual migration. As of this specification, only valid versi
production use is 1.5.
ac A unique code for the AUA which is assigned by UIDAI. This is an alpha-numeric string
maximum length 10. (A default value public is available for testing.)
uid[0] and uid[1] First 2 digits of Aadhaar Number. Used for load-balancing.
asalk A valid ASA license key. ASAs must send one of their valid license keys at the end o
URL. It is important that license keys are maintained safely. When adding license key to th
ensure it is URL encoded to handle special characters.
e-KYC API
https://<host>/kyc/<ver>/<ac>/<uid[0]>/<uid[1]>/<asalk>
host Aadhaar e-KYC API server address. Actual production server address will be provided
through secure leased lines. KSA server should ensure that actual URL is configurable.
Next part of the URL kyc indicates that this is a e-KYC API call. Ensure that this is provide
ver e-KYC API version (optional). If not provided, URL points to current version. UIDAI may
this specification, default production version is 1.0.
ac A unique code for the AUA (KUA and AUA codes are same since KUA is an AUA having
This is an alpha- numeric string having maximum length 10.
uid[0] and uid[1] First 2 digits of Aadhaar Number. Used for load-balancing.
For security reason PID data collected for Aadhaar e-KYC must NOT be stored on any de
records for all the authentication request metadata along with the response and protect th
UIDAI, 2011-2014 http://uidai.gov.in/ Page 8 of 16
Version 1.0 Aadhaar e-KYC API
asalk A valid ASA license key. ASAs must send one of their valid license keys at the end o
safely. When adding license key to the URL, ensure it is URL encoded to handle special c
ver (mandatory) version of the KYC API. Currently only valid value is 1.0.
ts (mandatory) Timestamp at the time of capture of authentication input. This
value must match ts attribute of PID block of the resident authentication packet under
o If this value is not matching with PID ts, then, an error will be generated.
o Front-end application on the device must send the PID ts value to KUA server to ensur
to ensure authentication input cannot be independently used for e- KYC later.
rc (mandatory) Represents residents explicit consent for accessing the residents identit
Y. If resident does not provide this explicit consent, application SHOULD NOT access resi
mec (optional) Represents residents explicit consent for accessing the mobile numbe
values are Y and N. Default value is N (by default, this API does not return mobile an
lr - (optional) Flag indicating if AUA application require local language data in addition to
default, this API does not return local Indian language data).
de (optional) Flag indicating if KUA is delegating decryption to KSA. If this flag is set to
XML instead of KUA key provided KSA is allowed to do so.
o This is OPTIONAL attribute and hence should be used ONLY when KUA requires to change
if KSA is approved to do decryption.
o By default, KUA public key is always used to encrypt e-KYC response.
o If KUA key is NOT available in CIDR, KSA key will be used to encrypt
provided KSA is authorized to do so.
o A dynamic option of setting de attribute to Y allows KUA to make this
choice at transaction level based on the KSA they use for e-KYC service.
Rad (mandatory)
This element contains base64 encoded Auth XML for resident. Authentication in
Authentication API specification.
Any valid Authentication API version and features can be used while invoking e-KYC. Only
authentication input XML (authentication namespace) must start with UKC:.
IOMPORTANT NOTE: Digital Signature at eKYC XML level is optional
The e-KYC request XML may be digitally signed for message integrity and nonrepudiation purposes.