Page 17 - FIGI: e-KYC use cases in digital financial services

formal contract with UIDAI to be able to use Aadhaar can engage with an existing AUA and such agencies,
authentication services (see Figure 2). Any other which enter into agreements with AUA, are defined
agency seeking to conduct Aadhaar authentication as Sub-AUA.
of its customers/associates etc. for service delivery

Figure 1: Department AUA on-boarding process

b) Authentication Service Agency (ASA) A KUA is any entity, which uses Aadhaar authen-
tication to enable its services and connects to the
ASA is any entity that transmits authentication Aadhaar database through an ASA.
requests to the Aadhaar database on behalf of one
or more AUAs. They play the role of enabling inter- d) e-KYC Service Agency (KSA)
mediaries. They have an established secure connec-
tion with the Aadhaar database and convey authen- KSAs are entities with connectivity with the Aadhaar
tication requests of more than one AUA thereto. database and can share the demographic profile of
ASAs receive the Aadhaar database response and the Aadhaar card holder with the KUAs for authenti-
transmit the same back to the AUA. An ASA may cation purpose. Every KSA is also an ASA.
enter into a formal contract with AUAs. UIDAI has a
set of guidelines that may be included in the contract 2.4.2 Aadhaar authentication and e-KYC
between an ASA and an AUA. However, the contract Aadhaar authentication is the process wherein the
(and commercial terms, if any) between an ASA and Aadhaar Number, along with other attributes, includ-
an AUA is at the sole discretion of the signing parties. ing biometrics, are submitted online to the Aadhaar
database for its verification based on information
c) e-KYC User Agency (KUA) or data or documents available with it. During the
authentication, the person's record is first selected
using the Aadhaar Number and then the demograph-
ic/biometric inputs are matched against the stored

e-KYC use cases in digital financial services 15