E-KYC Interface Specification Version 1.3

National Payments Corporation of India
NPCI e-KYC Interface

Specification
Version 1.3 Year 2014
Release Year 2014

Table of Contents
Table of Contents
Table of Contents __________________________________________________________________________________ 1
List of Figures ______________________________________________________________________________________ 2
List of Tables _______________________________________________________________________________________ 2
Confidentiality and Copyright Notice __________________________________________________________ 2
Document Control _________________________________________________________________________________ 3
Chapter 1 Introduction ________________________________________________________________________ 4
1.1 Executive Summary_________________________________________________________________________ 4
1.2 Background __________________________________________________________________________________ 4
1.3 Scope __________________________________________________________________________________________ 4
1.4 Audience _____________________________________________________________________________________ 5
Chapter 2 E-KYC on NPCI Network ___________________________________________________________ 5
2.1 Architecture Diagram ______________________________________________________________________ 5
2.1.1 e-KYC with Biometric data - Transaction Flow ____________________________________________________6
2.1.2 e-KYC with OTP- Transaction Flow _________________________________________________________________6
2.2 Message Flow ________________________________________________________________________________ 7

2.3 Transaction Timeout Parameters ________________________________________________________ 7
2.4 Security & Key Management ______________________________________________________________ 7
Chapter 3 Interface Specification ____________________________________________________________ 8
3.1 Message Format _____________________________________________________________________________ 8
3.2 e-KYC __________________________________________________________________________________________ 9
3.3 Transaction Flow _________________________________________________________________________ 10
Chapter 4 Data Elements Definition ________________________________________________________ 13
Chapter 5 Settlement and Reconciliation _________________________________________________ 20
5.1 Settlement and Reconciliation __________________________________________________________ 20
Chapter 6 Risk Management _________________________________________________________________ 20
Chapter 7 Changes Required ________________________________________________________________ 20
Chapter 8 Sample Message Dumps _________________________________________________________ 21
NPCI e-KYC Interface Specification

NPCI © 2011 Confidential Page 1 of 23
List of Figures
List of Figures
Figure 1 e-KYC Architecture Diagram..................................................................................................................... 5
Figure 2 Message Flow .................................................................................................................................................. 7
List of Tables
Table 1 Version History___________________________________________________________________________________ 3
Table 2 e-KYC Request and Response ____________________________________________________________________ 8
Table 3 OTP Request and Response _____________________________________________________________________ 9
Confidentiality and Copyright Notice

© 2011 by National Payments Corporation of India.
This document is of restricted use. No part of this document may be reproduced in any form by any
means without prior written authorization of National Payment Corporation of India (NPCI).

Document Control
Document Control
Document name: NPCI e-KYC Interface Specification
Security classification: Confidential
Distribution list: Member banks
Version History:
Version Issue Date Effective Date

Draft 1.0 Jan 2013 Jan 2013
Draft 1.1 July 2013 July 2013
Version 1.1 rev1 Sept 2013 Sept 2013
Version 1.2 20 Sept ‘13 20 Sept ‘13
Version 1.3 10 Jan 2014 10 Jan 2014
Table 1 Version History
Revision History
Version Date Changes Made

Draft 1.0 4/13/2013 Initial document
Changes made in Message Parameter
Draft 1.1 7/13/2013
Inclusion of Message Dump
Version 1.1 rev1 9/10/2013 Update in Chapter 4- Response code List and Description
Update in MCC, POS Entry Mode and Response Code
Version 1.2 9/20/2013
Change in Message Dump
Changes as per UIDAI Specs aadhaar_kyc_api_1_0_final.pdf
Additional Response Codes added.
Version 1.3 1/10/2013
Response Message tag added to allow banks to see the reason
for failure. Can be ignored by bank.

Introduction
Chapter 1 Introduction
1.1 Executive Summary
National Payments Corporation of India (NPCI) is formed as an umbrella institution for all the retail
payments systems in the country. The core objective is to consolidate and integrate the multiple
systems with varying service levels into nation-wide uniform and standard business process for all
retail payment systems. The other objective was to facilitate an affordable payment mechanism to
benefit the common man across the country and help financial inclusion. Vision and formation of NPCI
is backed by the regulator and Indian Banks Association (IBA). NPCI has defined business lines to
process in country interbank transactions for ATM, POS, 24x7 Remittance, ACH and CTS.
Government of India has initiated Unique Identification Project for citizens of India. It is envisaged to
use the UID schema and infrastructure for the financial inclusion in India. To enable the customers to
use AADHAAR for the financial transaction across the payment networks in the country, NPCI proposes
to facilitate routing of transactions to the central id repository of UIDAI for user authentication
through a single interface.
The UIDAI also provides the service of online authentication of identity on the basis of demographic
and biometric data. Verification of the Proof of Identity (PoI) and Proof of Address (PoA) is a key
requirement for access to financial products. Today, customers provide physical PoI and PoA
documents. Aadhaar is already a valid PoI and PoA document for various services in the Financial,
Telecom, and Government domains.
1.2 Background
UIDAI now proposes to provide an e-KYC service, through which the KYC process can be performed
electronically. As part of the e-KYC process, the resident authorizes UIDAI (through Aadhaar
authentication) to provide their basic demographic data for PoI and PoA along with their photograph
(digitally signed) to service providers.
1.3 Scope
NPCI member banks and non-banking entities can provide a paperless KYC experience by using e-KYC
and avoid the cost of repeated KYC, the cost of paper handling and storage, and the risk of forged
documents. NPCI will access the Aadhaar e-KYC service from UIDAI through the e-KYC API.
NPCI will be providing an e-KYC service to its member banks and non-Banking entities as a KYC Service
Agency (KSA).

E-KYC on NPCI Network
1.4 Audience
This document is a property of NPCI and should be not be circulated to external party without prior
approvals of NPCI management team.
This document will be circulated to NPCI management team, Technical Advisor Committee, Business
user group formed from member banks.
Chapter 2 E-KYC on NPCI Network

Two transactions will be supported by the NPCI E-KYC system as follows:
 OTP - Resident authentication can be strengthened by verifying the possession of the mobile
by resident. One Time Pin (OTP) is a mechanism to achieve this. Aadhaar authentication
supports OTP and can be used by KUA by sending the request through KSA.
 e-KYC – KSA e-KYC API can be used by KUA to obtain latest resident demographic data and
photo data from UIDAI.
2.1 Architecture Diagram
Figure 1 e-KYC Architecture Diagram

2.1.1 e-KYC with Biometric data - Transaction Flow

1. Originating Channel captures Aadhaar number + biometric of resident and forms the
encrypted PID block.
2. KUA system will form the XML Request Message and sends to NPCI KSA system.
3. NPCI forms the KYC XML message and sends to UIDAI.
4. Aadhaar KYC service authenticates the resident and if successful responds with encrypted
demographic and photograph in XML format.
5. Demographic data and photograph in response is encrypted with KUA public key by UIDAI
6. NPCI sends the response back to KUA enabling paper-less electronic KYC.
2.1.2 e-KYC with OTP- Transaction Flow

1. Originating Channel captures Aadhaar number and request for OTP of resident and sends the
request to KUA.
2. KUA system will forward the request to NPCI KSA system.
3. NPCI forms the OTP XML message and sends to UIDAI and If successful OTP response is
received to NPCI and OTP is sent to residents’ registered mobile number.
4. Resident enters OTP and KUA system will form the XML Request Message and sends to NPCI
KSA system.
7. Demographic data and photograph in response is encrypted with KUA public key by UIDAI.

2.2 Message Flow
The below figure depicts detailed message flow from MicroATM to UIDAI e-KYC system
Figure 2 Message Flow
2.3 Transaction Timeout Parameters

1. The Timeout parameter between NPCI and UIDAI server is 10 seconds i.e. NPCI will wait for
10 seconds for the response from UIDAI EKYC server after sending a request. After 10 seconds
a declined response will be sent back to the Acquirer system.
2. The Timeout parameter on the Acquirer switch should be around 30 seconds i.e. if the
Acquirer system doesn’t receive response from NPCI, Acquirer system should send a declined
response to the Originating channel.
3. The Timeout parameter on the Originating channel should be around 60 seconds i.e. if the
Originating system doesn’t receive response from Acquirer system, Originating channel
should decline the transaction and show appropriate message to the operator.
2.4 Security & Key Management

NPCI (KSA) will be digitally signing the request with NPCI private key to UIDAI on behalf of bank
(KUA).

Interface Specification
Chapter 3 Interface Specification

This document defines the Interface Specifications between Bank switch, NPCI and UIDAI in detail. It
provides clear understanding of online interfaces, protocols and messages used, to enable
implementation of the interface connection, and to serve as a basic document for future
enhancements.
NPCI e KYC service is exposed as stateless service over HTTPS. Usage of open data format in XML and
widely used protocol such as HTTPS allows easy adoption and deployment of EKYC. To support strong
end to end security and avoid request tampering and man-in-the-middle attacks HTTPS protocol will
be used.
Aadhaar OTP Request service (or simply OTP service) is exposed as stateless service over HTTPS with
the usage of open data format in XML.
3.1 Message Format

e-KYC Request and Response with Biometric/OTP
Parameter Description Request Response
KycRequest Root element M -
TransactionInfo Primary element M +M
Pan Acquirer ID/IIN + ’0’ + Aadhaar Number M +M
of the resident
Proc_code Processing Code M +M
Transm_Date_time Transmission Date & Time M +M
Stan System Trace Audit Number M +M
Local_Trans_Time Local Transaction time M +M
Local_date Local Transaction date M +M
Mcc Merchant Category Code M -
Pos_entry_mode Point of Service Entry Mode M -
Pos_code Point of Service Condition Code M -
AcqId Acquirer ID M +M
RRN Retrieval Reference Number M +M
ResponseCode Response Code - M
ResponseMsg Response Message - M
CA_Tid Card Acceptor Terminal ID M +M
CA_ID Card Acceptor Member ID M +M
CA_TA Card Acceptor Terminal Address M +M
KycReqInfo E KYC Request Data Information M -
KycResponse E KYC Response Data Information - M
Resp Encrypted and encoded response from - M
UIDAI
Table 2 e-KYC Request and Response

OTP Request and Response

Parameter Description Request Response
OtpRequest Root element M -
TransactionInfo Primary element M +M
Pan Acquirer ID/IIN + ‘0’ +Aadhaar Number of M +M
the resident
Proc_code Processing Code M +M
Transm_Date_time Transmission Date & Time M +M
Stan System Trace Audit Number M +M
Local_Trans_Time Local Transaction time M +M
Local_date Local Transaction date M +M
Mcc Merchant Category Code M -
Pos_entry_mode Point of Service Entry Mode M -
Pos_code Point of Service Condition Code M -
AcqId Acquirer ID M +M
RRN Retrieval Reference Number M +M
ResponseCode Response Code - M
ResponseMsg Response Message - M
CA_Tid Card Acceptor Terminal ID M +M
CA_ID Card Acceptor Member ID M +M
CA_TA Card Acceptor Terminal Address M +M
OtpResponse OTP response received from UIDAI - M
Table 3 OTP Request and Response
Note: Request and response in aadhaar_kyc_api_1_0_final.pdf released by UIDAI. KUA will receive
the response and decrypt the KycRes.
3.2 e-KYC
Following is the XML data format for e-KYC Request Message to NPCI.
1. If KUA send the e-KYC request with only Biometric Data. “otp” tag in Uses attribute will be “n”
and “bio” tag will be “y” and will contain encrypted Pid block in KYC Request.
2. If KUA send the only otp request “otp” tag in Uses attribute will be “y” and “bio” tag will be
“n” and will contain OTP which is also encrypted in Pid block in KYC Request.
3. If KUA send the e-KYC request with both Biometric and OTP. Both “otp” and “bio” tag in Uses
attribute will be “y” and will contain encrypted Pid block in KYC Request .
4. OTP is an independent request initiated by KUA to validate the Aadhaar number holder.

3.3 Transaction Flow

e-KYC transaction can be initiated with both Biometric and OTP.
[I] E KYC with Biometric data

1. Originating Channel captures Aadhaar number + biometric of resident and forms the encrypted
PID block.
2. KUA system will form the XML Request Message and sends to NPCI KSA system.
5. Demographic data and photograph in response is encrypted with KUA public key.
[II] E-KYC with OTP

1. Originating Channel captures Aadhaar number and request for OTP of resident and forms the
request message and sends the request to KUA.
2. KUA system will forward the request to NPCI KSA system.
3. NPCI forms the OTP XML message and sends to UIDAI and if successful OTP response is
received to NPCI and OTP is sent to residents’ registered mobile number.
4. Resident enters OTP and KUA system will form the XML Request Message and sends to NPCI
KSA system.
7. Demographic data and photograph in response is encrypted with KUA public key.

KYC Transaction with Biometric/OTP

e-KYC Request with Biometric/OTP e-KYC Response with Biometric/OTP
< KycRequest > <KycResponse>

<TransactionInfo> <TransactionInfo>
<Pan></Pan> <Pan></Pan>
<Proc_Code></Proc_Code> <Proc_Code></Proc_Code>
<Transm_Date_time></ Transm_Date_time > <Transm_Date_time></ Transm_Date_time >
<Stan></Stan> <Stan></Stan>
<Local_Trans_Time></Local_Trans_Time> <Local_Trans_Time></Local_Trans_Time>
<Local_date></Local_date> <Local_date></Local_date>
<Mcc></Mcc> <AcqId></AcqId>
<Pos_entry_mode></Pos_entry_mode> <RRN></ RRN>
<Pos_code></Pos_code> <ResponseCode></ResponseCode>
<AcqId></AcqId> <ResponseMsg></ResponseMsg>
<RRN></ RRN> <CA_Tid></CA_Tid>
<CA_Tid></CA_Tid> <CA_ID></CA_ID>
<CA_ID></CA_ID> <CA_TA></CA_TA>
<CA_TA></CA_TA> </TransactionInfo>
</TransactionInfo> <Resp status=“” ko=”” ret=”” code=”” txn=”” ts=””
<KycReqInfo ver=“” ts=“” ra=“” rc=“” mec=”” lr=”” err=””>encrypted and base64 encoded “KycRes”
de=””> element</Resp>
<Auth uid=”” tid=”” ac=”” sa=”” ver=”” txn=”” lk=””> </KycResponse>
<Uses pi=”” pa=”” pfa=”” bio=”” bt=”” pin=”” otp=””/>
<Tkn type=”” value=””/>
<Meta udc=”” fdc=”” idc=”” pip=”” lot=”G|P” lov=””/>
<Skey ci=”” ki=””>encrypted and encoded session
key</Skey>
<Data type=”X|P”>encrypted and encoded PID
block</Data>
<Hmac>SHA-256 Hash of Pid block, encrypted and then
encoded</Hmac>
</Auth>
</KycReqInfo>
</KycRequest>

OTP Transaction
Request for OTP Response for OTP
<OtpRequest> <OtpResponse>
<TransactionInfo> <TransactionInfo>
<Pan></Pan> <Pan></Pan>
<Proc_Code></Proc_Code> <Proc_Code></Proc_Code>
<Transm_Date_Time></Transm_Date_Time> < Transm_Date_Time ></Transm_Date_Time>
<Stan></Stan> <Stan></Stan>
<Local_Trans_Time></Local_Trans_Time> <Local_Trans_Time></Local_Trans_Time>
<Local_date></Local_date> <Local_date></Local_date>
<Mcc></Mcc> <AcqId></AcqId>
<Pos_entry_mode></Pos_entry_mode> <RRN></ RRN>
<Pos_code></Pos_code> <ResponseCode></ResponseCode>
<AcqId></AcqId> <ResponseMsg></ResponseMsg>
<RRN></ RRN> <CA_Tid></CA_Tid>
<CA_Tid></CA_Tid> <CA_ID></CA_ID>
<CA_ID></CA_ID> <CA_TA></CA_TA>
<CA_TA></CA_TA> </TransactionInfo>
</TransactionInfo> <OtpRes ret=”” code=”” txn=”” err=”” ts=”” />
<Otp uid=”” tid=”” ac=”” sa=”” ver=”” txn=”” lk=””> </OtpResponse>
<Opts ch=””/>
</Otp>
</OtpRequest>

Data Elements Definition
Chapter 4 Data Elements Definition

Elements Description
KycRequest Primary Root element of the input XML for e-KYC request
(Mandatory)
TransactionInfo Secondary Root element of the input XML for e KYC request
(Mandatory)
Tags
Pan: Aadhaar Number of the resident (mandatory)
Format: LLVAR
Type n..19
PAN must be populated with the combination of Acquirer ID/IIN and the
resident Aadhaar number.
B B B B B B I U U U U U U U U U U U U
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
B – Acquirer ID/IIN
I – Indicator for UID – valid value “0”, pass zero for e-KYC
U – Unique Identification Number of customer issued by UIDAI
Note: As for non-banking entities IIN is not issued, acquirer ID must be populated
in the first 6 digit of PAN by these entities.
Proc_Code: Processing Code (mandatory)

Format: Fixed
Type:n6
A series of digits that describes the type of transaction and the accounts
affected by the transaction.
It consists of three, two-digit sub fields:
Digit 1 and 2: Transaction Code

13 e-KYC
14 OTP
Digit 3 and 4: From Account Type*
00 Unspecified/unknown
Digit 5 and 6: To Account Number*
00 Unspecified/unknown

Transm_Date_time: Transmission Date and Time (mandatory)

Format: Fixed
Type: n10 MMDDhhmmss
It is the date and time when a transaction request was transmitted by a
processing entity. It is represented in GMT/UTC.
Stan: System Trace Audit Number (mandatory)

Format: Fixed
Type: n6
It is the unique identifier assigned to each transaction by the acquirer bank
switch. It must be different for every transaction even for multiple set of
transactions originated at the same time
Local_Trans_Time : Local Transaction Time (mandatory)

Format: Fixed -hhmmss
Type: n6
Local Transaction Time will be passed in the XML Request message. The local
time at which the transaction began from initiated device location. When a
request originates from bank; it is assumed that the content of this attribute is
the terminal local time.
Local_date : Local Date (mandatory)

Format: Fixed -MMDD
Type: n4
Date, Local Transaction is the local month and day on which Transaction takes
place at the point of service.
Mcc : Merchant Category Code (mandatory)

Format: Fixed
Type: n4
Description: Contains a 4 digit code describing a merchant’s type of business.
Refer to ISO 18245 for list of MCC.

Pos_entry_mode : Point of Service Entry Mode (mandatory)

Format: Fixed
Type: n3
Description: The code describes the way how PAN and PIN are entered at a touch
point.
Data element consists of two sub-fields:
PAN Entry Mode
01 Manual
02 Magnetic stripe read.
05 ICC.
90 Full and unaltered magnetic stripe read (enables CVV validation).
PIN Entry Mode
0 Unspecified.
1 PIN entry capability (OTP transaction)
2 No PIN entry capability.
6 PIN pad inoperative.
9 Reserved for private use (Biometric entry capability)
Pos_code : Point of Service Condition Code (Mandatory)

Format: Fixed
Type: n2
Description: Two-digit code indicating conditions at touch point:
00 Normal
01 Customer not present.
02 Unattended terminal (CAT, ADM)
03 Merchant suspicious.
05 Customer present, card not present.
AcqId : Acquirer ID (mandatory)

Format: LLVAR
Type: n..6
Identifies the acquiring institution from where the request has been initiated.
This ID will be allotted by NPCI.

RRN : Retrieval Request Number (mandatory)

Format: Fixed
Type: an12
The reference, assigned by the acquirer, to identify a transaction uniquely. It
remains unchanged for all messages throughout the life of a transaction and is
used for matching original message with reversal and/or store/forward
messages.
The standard format of RRN is as follows: YDDDHHSSSSSS
Y – Year (last digit of current year)

DDD – Julian date of transaction
HH – Hour of transaction (‘HH’ should be derived from Local_Trans_Time )
SSSSSS – STAN (same as STAN passed in kyc Request)
ResponseCode: Response Code (mandatory in Response)

Format: Fixed
Type: an2
Response Code is mandatory in the response messages.
The following response codes will be supported by the interface.
Sr. Response UIDAI Description

No. Code Error
1 UI - No Response from UIDAI
2 20 - Format Error
3 00 - Received Response from UIDAI (regardless of
Failure/success)
4 92 - No Routing at NPCI
5 91 - Unable to send request to UIDAI
6 K1 K-100 Resident authentication failed
7 K2 K-200 Resident data currently not available
8 K3 K-540 Invalid KYC XML
9 K4 K-541 Invalid e-KYC API version

10 K5 K-542 Invalid resident consent (“rc” attribute in
“Kyc” element)
11 K6 K-543 Invalid timestamp (“ts” attribute in “Kyc”
element)
12 K7 K-544 Invalid resident auth type (“ra” attribute
in “Kyc” element does
not match what is in PID block)
13 K8 K-545 Resident has opted-out of this service
14 K9 K-550 Invalid Uses Attribute
15 KA K-551 Invalid “Txn” namespace
16 KB K-552 Invalid License key
17 KC K-569 Digital signature verification failed for e-

KYC XML
18 KD K-570 Invalid key info in digital signature for e-
KYC XML (it is either
expired, or does not belong to the AUA or
is not created by a well-known
Certification Authority)
19 KE K-600 AUA is invalid or not an authorized KUA
20 KF K-601 ASA is invalid or not an authorized KSA

21 KG K-602 KUA encryption key not available
22 KH K-603 KSA encryption key not available
23 KI K-604 KSA Signature not allowed
24 KJ K-605 Neither KUA key nor KSA encryption key
are available
25 KL K-955 Technical Failure
26 KM K-999 Unknown error
27 O1 110 Aadhaar number does not have verified
mobile/email
28 O2 111 Aadhaar number does not have verified
mobile
29 O3 112 Aadhaar number does not have both email
and mobile
30 O4 510 Invalid “Otp” XML format

31 O5 520 Invalid device
32 O6 530 Invalid AUA code
33 O7 540 Invalid OTP XML version
34 O8 542 AUA not authorized for ASA. This error will
be returned if AUA and ASA do not have
linking in the portal
35 O9 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
36 OA 565 AUA License key has expired or is invalid
37 OB 566 ASA license key has expired or is invalid
38 OC 569 Digital signature verification failed
39 OD 570 Invalid key info in digital signature (this
means that certificate used for signing the
OTP request is not valid – it is either
expired, or does not belong to the AUA or is
not created by a CA)
40 OE 940 Unauthorized ASA channel
41 OF 941 Unspecified ASA channel
42 OG 950 Could not generate and/or send OTP
43 OH 999 Unknown error
Note:
For all declines with RC UI, 20, 92, 91, only <ResponseCode> tag will be available.
Details:
(i) e-Kyc Transaction with Bio/OTP
<ResponseCode> tag will be present but <Resp>tag will be unavailable.
(ii) OTP
< ResponseCode> tag will be present but <OtpRes>tag will be unavailable.
ResponseMsg: Response Message (mandatory in Response)

Format: Variable
Type: an…80
Response Msg is mandatory in the response messages.

CA_Tid : Terminal Identification (mandatory)
Format: Fixed
Type: n6
It should carry value “public” in the request for all transactions originated from
a device unregistered at UIDAI data base. For devices recognized by UIDAI, this
code will be allotted by UIDAI the data element is mandatory.
NOTE: ‘ public’ must be left padded with two spaces making it 8 digit value.
CA_ID : Card Acceptor Identification Code (mandatory)

Format: Fixed
Type: ans15
This is a unique code for the device assigned within the Bank domain.
Character 1-15 Unique Device Code, first 3 digits should have Bank code and last
12 digits should be Unique terminal code allotted to every device by the bank. If
the terminal code is less than 15 digits, the terminal code should be left padded
with zeros to make it 15 digits.
CA_TA : Terminal Address (mandatory)

Format: Fixed
Type: an40
The name and location of the acceptor (Touch Point) where the Request has
been initiated.
Character 1-23 Merchant Name &Address / Bank Correspondent Name &
Address
Character 24-36 City Name
Character 37-38 State
Character 39-40 Country Code (IN)
KycReqInfo Primary Root element of the input XML for e KYC request where all the e KYC
related Data will be passed
(mandatory) Detailed Description is referred from aadhaar_kyc_api_1_0_final.pdf

Settlement and Reconciliation
Chapter 5 Settlement and Reconciliation

5.1 Settlement and Reconciliation
1. Settlement of these transactions will be performed in the NPCI Dispute Management System
and Daily Settlement Report will be provided to member banks.
2. Acquirer activity report will be circulated to member banks. There will not be any change in
the Acquirer Activity Report file format.
Chapter 6 Risk Management

The following risk management will be done by members. Acquirers will be responsible for following
checking,
i. Acquirer shall not log the Biometric data on the switch or at any hop.
ii. Transaction and incoming message validation coming from Micro ATM/Originating
channel.
iii. Unique key management for the terminals.
iv. Acquirer banks have to store the e-KYC response data in encrypted formats as per PCI
guidelines.
v. Acquirer bank will connect to NPCI network on NPCINET.
vi. Acquirer Bank will be responsible for constructing and transmitting Finger print data
of the resident.
Chapter 7 Changes Required
 Changes for Member Bank and non-banking entities

i. Establish connection between originating channel and KUA system.
ii. Establish connection between KUA system and NPCI KSA system.
iii. Addition of 2 transactions in the interface to the NPCI KSA system.
iv. Changes in the current reconciliation system to reconcile the switching fees for e-KYC
based transactions.
v. Accept the KYC details in the response and process appropriate message to originating
channel.
 Changes in NPCI systems,

i. Process the request from KUA system and forward it to KYC server of UIDAI.
ii. Process the response from UIDAI and respond back to KUA system.

Sample Message Dumps
Chapter 8 Sample Message Dumps

1. Sample OTP
<OtpRequest>
<TransactionInfo>
<Pan>2000020********2521</Pan>
<Proc_Code>140000</Proc_Code>
<Transm_Date_time>0726094813</Transm_Date_time >
<Stan>206661</Stan>
<Local_Trans_Time>151813</Local_Trans_Time>
<Local_date>0726</Local_date>
<Mcc>6012</Mcc>
<Pos_entry_mode>019</Pan_entry_mode>
<Pos_code>05</Pos_code>
<AcqId>200002 </AcqId>
<RRN>320715206661</ RRN>
<CA_Tid> public</CA_Tid>
<CA_ID>UCO000000006000</CA_ID>
<CA_TA>CSB, NERUL MUMBAI MHIN</CA_TA>
</TransactionInfo>
<Otp uid=”99********21” tid=”public” ac=”STGGGGGBNK” sa=”STGGGGGBNK” ver=”1.5” txn=”206661”
lk=”xxxxxxxxxxxxxxxxxxxxxxxxxxx”>
<Opts ch=”01”/>
</Otp>
</OtpRequest>
=========================================================================================
<OtpResponse>
<TransactionInfo>
<Pan>2000020********2521</Pan>
<Transm_Date_time>0726094813</ Transm_Date_time >
<Stan>206661</Stan>
<AcqId>200002 </AcqId>
<RRN>320715206661</ RRN>
<ResponseCode>00</ResponseCode>

<ResponseMsg>Successful</ResponseMsg>
<CA_ID>UCO000000006000</CA_ID>
</TransactionInfo>
<OtpRes ret=”y” code=”5b5b358eeda841178e6fc1767a8889c2” txn=”206661” ts=”2013-07-
29T17:52:58.416+05:30” />
</OtpResponse>
2. Sample e-KYC with Biometric

<KycRequest>
<TransactionInfo>
<Pan>2000020********2521</Pan>
<Transm_Date_time>0726094813</ Transm_Date_time >
<Stan>206661</Stan>
<Mcc>6012</Mcc>
<Pos_entry_mode>019</Pos_entry_mode>
<Pos_code>05</Pos_code>
<AcqId>200002</AcqId>
<RRN>320715206661</RRN>
<CA_ID>UCO000000006000</CA_ID>
</TransactionInfo>
<KycReqInfo ver=“1.0” ts=“2013-07-29T17:52:58.416+05:30” ra=“” rc=“Y” mec=”” lr=”” de=””>
<Auth uid=”99********13” tid=”public” ac=”STGCORPBNK” sa=”STGCORPBNK” ver=”1.6” txn=”206661”
lk=”xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx”>
<Uses pi=”n” pa=”n” pfa=”n” bio=”y” bt=”FMR” pin=”n” otp=”n”/>
<Meta udc=”CRB000000006000” fdc=”NC” idc=”NA” pip=”127.0.0.1” lot=”P” lov=”560103”/>
<Skey ci=”20151110”>xxxxxxxxxxxxxxxxx</Skey>
<Data type=”P”>xxxxxxxxxxxxxxxxx</Data>
<Hmac>xxxxxxxxxxxxxxxxxxxxxxxxxxxx</Hmac>
</Auth>
</KycReqInfo>

</KycRequest>
=========================================================================================
<KycResponse>
<TransactionInfo>
<Pan>2000020********2521</Pan>
<Transm_Date_time>0726094813</Transm_Date_time>
<Stan>206661</Stan>
<AcqId>200002</AcqId>
<RRN>320715206661</ RRN>
<ResponseCode>00</ResponseCode>
<ResponseMsg>Successful</ResponseMsg>
<CA_ID>UCO000000006000</CA_ID>
</TransactionInfo>
<Resp status=“0” ko=”” ret=”” code=”” txn=”” ts=”” err=””>7kU2tbcel+************1nT7y9</Resp> ---
encrypted & base64 encoded “KycRes” element
</KycResponse>


E-KYC Interface Specification Version 1.3

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

E-KYC Interface Specification Version 1.3

Caricato da

Copyright:

Formati disponibili

National Payments Corporation of India

NPCI e-KYC Interface

Release Year 2014

2.2 Message Flow ________________________________________________________________________________ 7

NPCI e-KYC Interface Specification

Confidentiality and Copyright Notice

NPCI e-KYC Interface Specification

Version Issue Date Effective Date

Version Date Changes Made

NPCI e-KYC Interface Specification

NPCI e-KYC Interface Specification

Chapter 2 E-KYC on NPCI Network

2.1 Architecture Diagram

Figure 1 e-KYC Architecture Diagram

NPCI e-KYC Interface Specification

2.1.1 e-KYC with Biometric data - Transaction Flow

2.1.2 e-KYC with OTP- Transaction Flow

NPCI e-KYC Interface Specification

2.2 Message Flow

Figure 2 Message Flow

2.3 Transaction Timeout Parameters

2.4 Security & Key Management

NPCI e-KYC Interface Specification

Chapter 3 Interface Specification

3.1 Message Format

NPCI e-KYC Interface Specification

OTP Request and Response

Table 3 OTP Request and Response

NPCI e-KYC Interface Specification

3.3 Transaction Flow

[I] E KYC with Biometric data

[II] E-KYC with OTP

NPCI e-KYC Interface Specification

KYC Transaction with Biometric/OTP

< KycRequest > <KycResponse>

NPCI e-KYC Interface Specification

Request for OTP Response for OTP

NPCI e-KYC Interface Specification

Chapter 4 Data Elements Definition

Proc_Code: Processing Code (mandatory)

Digit 1 and 2: Transaction Code

NPCI e-KYC Interface Specification

Transm_Date_time: Transmission Date and Time (mandatory)

Stan: System Trace Audit Number (mandatory)

Local_Trans_Time : Local Transaction Time (mandatory)

Local_date : Local Date (mandatory)

Mcc : Merchant Category Code (mandatory)

NPCI e-KYC Interface Specification

Pos_entry_mode : Point of Service Entry Mode (mandatory)

Pos_code : Point of Service Condition Code (Mandatory)

AcqId : Acquirer ID (mandatory)

NPCI e-KYC Interface Specification

RRN : Retrieval Request Number (mandatory)

Y – Year (last digit of current year)

ResponseCode: Response Code (mandatory in Response)

Sr. Response UIDAI Description

NPCI e-KYC Interface Specification

15 KA K-551 Invalid “Txn” namespace

16 KB K-552 Invalid License key

17 KC K-569 Digital signature verification failed for e-

20 KF K-601 ASA is invalid or not an authorized KSA

NPCI e-KYC Interface Specification

ResponseMsg: Response Message (mandatory in Response)

NPCI e-KYC Interface Specification