Numeric Development Flow
Numeric Development Flow
NPCI product names are trademarks of National Payments Corporation of India. Other
names may be trademarks of their respective owners.
v1.4
Page 1 of 78
Centralised Mapper - TSD
Contents
Preface ................................................................................................................................................. 5
Audience............................................................................................................................................... 5
Prerequisites......................................................................................................................................... 5
1 Introduction ................................................................................................................................. 7
v1.4
Page 2 of 78
Centralised Mapper - TSD
v1.4
Page 3 of 78
Centralised Mapper - TSD
ReqValAdd is getting initiated for UPI Number (cmId) transaction by Payer PSP ............................ 59
UPI Initiating ReqvalAdd to Payee PSP ............................................................................................. 59
Payee PSP respond RespValAdd to UPI............................................................................................. 60
UPI respond RespValAdd back to Payer PSP ..................................................................................... 60
Initial Reqpay Request from Payer PSP ............................................................................................. 60
ReqAuthDetails initiated by UPI ........................................................................................................ 62
RespAuthDetails from Payee PSP...................................................................................................... 62
ReqPay Debit Request Initiated by UPI ............................................................................................. 64
Resppay for Debit Request from Bank .............................................................................................. 65
ReqPay Credit Request initiated by UPI ........................................................................................... 66
Resppay Credit Request from Bank .................................................................................................. 67
Final Resppay from UPI to Payer PSP ................................................................................................ 68
ReqTxnConfirmation from UPI to Payee PSP .................................................................................... 68
RespTxnConfirmation from Payee PSP to UPI .................................................................................. 69
Fetch by ID (Mobile Number) ................................................................................................... 69
Request to Fetch by ID (Mobile Number) ......................................................................................... 69
Response from UPI............................................................................................................................ 70
Fetch by ID (Numeric ID) .......................................................................................................... 70
Request to Fetch by ID (Numeric ID) ................................................................................................ 70
Response From UPI ........................................................................................................................... 71
Fetch by VPA............................................................................................................................. 71
Request to Fetch by VPA ................................................................................................................... 71
Response from UPI............................................................................................................................ 72
Transfer of Mobile Number from One PSP to Other (PORT) ..................................................... 72
Request to check the Mobile NumberGetAdd .................................................................................. 72
Response for the GetAdd .................................................................................................................. 73
Request to Transfter the Mobile Number ........................................................................................ 73
Response from UPI after Transfer Completion ................................................................................. 74
Notification – Transfer Confirmation Request to Previous PSP ...................................................... 74
Notification – Transfer Confirmation Response from Previous PSP ................................................. 75
Abbreviations ..................................................................................................................................... 76
References .......................................................................................................................................... 77
v1.4
Page 4 of 78
Centralised Mapper - TSD
Preface
The purpose of this document is to explain the proposed centralized mapper which
will be maintained at NPCI and be interoperable
Audience
This guide is intended for Banks to know more about the Centralized Mapper for a
numeric UPI ID
Prerequisites
You should have the following prerequisites to make best use of this document:
Working knowledge of the Centralized Mapper for a numeric UPI ID
Basic knowledge of API’s and their usage within UPI
Document History
Version Number Description Release Date
1.0 Centralised Mapper 25/12/2020
1.1 1.Updated Mapper 11/05/2021
Confirmation API
2.Updated Transfer of
mobile number
1.2 1. Updated Type Fetch in 31/05/2021
GetAdd for retrieve
2. Added idStatus ‘NEW’
and ‘DEREGISTER’
3. Removed Rule Check API
4. Removed Type ‘History’
of GetAdd
5. ReqMapperConfirmation
– update Status and Channel
6. Added Field Specification
for Mapper Confirmation
API
v1.4
Page 5 of 78
Centralised Mapper - TSD
v1.4
Page 6 of 78
Centralised Mapper - TSD
1 Introduction
This document describes the centalized mapper functionalities and steps added in the
customer onboarding process using a centralised mapper. An approach has been
defined for Numeric ID registration and the functional API flow of Pay/Collect scenario
has been endorsed in below sections.
2 Centralized Mapper
Centralized Mapper (CM) will be maintained as a separate service in UPI. This will help
to link the VPA to a number , mobile number or any unique identifier as the case may
be.
Post completing the new customer on-boarding process customer shall now be
prompted for Numeric ID generation. For existing users this will be available as
optional.
In addition to the current VPA and IFSC/Account as a payment option, a simple UPI
Number (Numeric ID or mobile number) can be used for transaction. Apps will have to
make necessary changes required for registration process and doing payments using
these new options.
UPI Number
Customer will be prompted to choose the desired UPI Number which can be Numeric
ID or Mobile Number . We allow customer to create 3 UPI Number per PSP. This can
be 1 Mobile Number and 2 Numeric ID.
v1.4
Page 7 of 78
Centralised Mapper - TSD
1. The Number should be a valid 10 digit Mobile Number against which VPA
is created
2. There will be provision available in Mapper to accommodate the number
of digit increase in future upto 16 digit
2. UPI Number as Numeric ID will have only one VPA linked to it in a ‘Active’
State
3. UPI Number as Mobile Number will have only one VPA linked to it in a
‘Active’ State
6. Any VPA can be linked to multiple Numeric ID and/or one Mobile Number
11. Transfer of UPI Number as Mobile Number between PSP will be allowed.
13. When the user deregister the app , PSP has to deactivate the corresponding
UPI Number
14. The mapper operation will happen only based on the customer consent
Mapper Operations
During the creation of UPI number , a consent from the customer will be taken for
storing the data ( Numeric ID / Mobile Number).Then the registration process will
begin by sending the request through ReqRegMapper API. The ReqRegMapper API will
store the details in Central Mapper in an encrypted format .
v1.4
Page 8 of 78
Centralised Mapper - TSD
The ReqRegMapper API shall perform various operations in the Centralized Mapper
given below
@mapper.npci will be the new handle that shall be appended to the UPI Number
(numeric ID / mobile number) for identifying the request to cenralized mapper.
3 RegMapper API
This API will facilitate UPI Apps to Register/Modify UPI Number at Centralized Mapper.
Using this API user can create the UPI Number more than once and can be mapped to
active VPA. Likewise user can also use the mobile number as UPI number
Registration Flow
Creation of UPI Number as Numeric ID by New User
New User during onboarding selects the bank , Sends the Mobile number and
IFSC code and gets the account number verified through ListAccount API
Then user selects a pin sends via ReqOTP API to issuer and OTP will get initiated
and validated by user against the credentials in CL page.
UPI will store the details in Central Mapper , Check and Validate in mapper in
both Master and Audit table
UPI sends the response to PSP through RespRegMapper to UPI and customer is
successfully on boarded with numeric id
All RegMapper API request will be validated against the OrgID and Handle with
the addr tag in order to avoid the invalid request
v1.4
Page 9 of 78
Centralised Mapper - TSD
There is no cooling period for the deletion of Mobile Number.If the mobile number has
to be reused as Numeric ID, then a registration process has to be followed .
Once the numeric id is deregistered there will be cooling period of Six(6) months which
is Configurable and the id will not be allocated to other person.But the id can be
reclaimed by same VPA through which it has been deleted.
In case of degresistration request , expiryTs will be shared in the response and the PSP
can refer the same to calculate the cooling period of the Numeric Id.
v1.4
Page 10 of 78
Centralised Mapper - TSD
Then the user app will validate the details using GetAddress API with type ‘PORT’ and
display the existing ID which has been already active in different application such as
MobileNumber@Activehandle using Get Address API . During this operation ‘addr’ tag
is populated if the ID exists and already mapped to any other PSP. NPCI will populate
the ‘addr’ only when the ID is in status ‘Active’ or ‘Inactive’. In case of ‘Block’ the
‘addr’ will not be retrieved only the status will be fetched and portability will not be
allowed.
On proceeding further when the user choose the populated id to port it to the current
PSP , ReqReg Mapper will initiate the modify request to UPI and the mobile number
shall be upadated to current PSP.The preVPA of ReqRegmapper will have the ID of the
Old PSP and during the transfer. Presence of this tag is the identifier of the transfer
operation.
Once the transfer is complete ReqMapperConfirmation API will be sent to Old PSP
Operati setStat
S No Scenario Comment
on(op) us
Create Numeric ID as UPI
1 ADD NEW
Number
Create Mobile Number as UPI
2 ADD NEW
Number
Before : CMUser@UPI,
9842212345
Transfer of Mobile Number to After : CMUser@ybl ,
3 MODIFY ACTIVE
different PSP 9842212345
(Transferred from BHIM to
Phonepe)
Before : CMUser@UPI ,
Update One Numeric ID against
12356780
5 different VPA for same PSP MODIFY ACTIVE
After : CMUser1@UPI ,
(change vpa)
12356780
v1.4
Page 11 of 78
Centralised Mapper - TSD
Before : CMUser@UPI ,
12345609
Activate by creating Numeric ID
After : CMUser@UPI ,
6 against the VPA and deactivate ADD
21212134
the current active Numeric ID
(21212134will be created
and made to active)
DEREGI No cooling period for
7 Deregister the Mobile Number MODIFY
STER mobile number deletion
DEREGI '45321890 will be available
8 Deregister the Numeric ID MODIFY
STER only after 6 months.
The deleted record will be
in ‘INACTIVE’ state in CM.
Reclaim the deregistered
9 MODIFY ACTIVE the same can be updated
Numeric ID against Same VPA
to ‘ACTIVE ‘by the same
user.
Reclaim the deactivated the
10 MODFIY ACTIVE
Mobile Number
PSP will initiate a Block
Block the UPI Number (Numeric
11 MODIFY BLOCK and PSP can block only its
ID / Mobile Number)
own UPI Number
Unblock the UPI Number UNBLO PSP will initiate the
12 MODIFY
(Numeric ID / Mobile Number) CK Unblock
1. There is no way to
differentiate the cases,
Mobile number surrendered by when the New user request
existing user without from surrendered mobile
ACTIVE
14 deactivating and new user MODIFY number or Existing user
requested for the creation of changing the App
UPI Number as Mobile Number 2. During transaction user
has to verify the recipient’s
address
New Profile and VPA will be
Linking new Mobile Number created for a New Mobile
15
against existing VPA Number i.e., Fresh
Registration
Creating UPI Number as
16 Numeric ID and Mobile Number
as a single request Not Applicable
Creating multiple Numeric ID
17
as a single request
v1.4
Page 12 of 78
Centralised Mapper - TSD
4 ReqValAdd API
This API has been enhanced and facilitate PSP to fetch “Beneficiary Name” & “UPI ID”
linked with UPI Number during financial transaction
Financial Flow
1. Customer enters the desired
cmId (Central Mapper ID) and
PSP fires a ReqValAdd API with
payee’s address in the format
XXXXXXXX@mapper.npci to
fetch the linked VPA.
2. UPI initiates request to central
mapper for fetching the linked
VPA.
3. The central mapper responds
back with linked VPA against the
cmId.
4. UPI then initiates ReqValAdd to Payee PSP.
5. Payee PSP responds through RespValAdd with all existing parameters.
6. The same response is send by UPI to RespValAdd to Payer PSP. Using this Payer
PSP will display the beneficiary’s name in App.
7. Once customer enters UPI PIN and authenticates,PAY transaction shall be
initiated this time using the VPA obtained in the RespValAdd. cmId should not
be used as the payment address in the financial transaciton.
Note : ReqPay API – When customer initiates the ReqPay for a PAY
transaction, the numeric id of Payer and Payee will be entered as
cmId in the respective Payer and Payee block of ReqPay and RespPay
Similarly COLLECT request shall be raised against the Payer’s VPA
obtained in RespValAdd.
cmID is an optional field for all financial transactions and Mandatory
Field for PSP
For Other Scenarios GetAdd is not mandatory for scenarios but PSP can still do GetAdd
if required
v1.4
Page 13 of 78
Centralised Mapper - TSD
Types of GetAdd
GetAdd will have 3 types called ‘CHECK’ , ‘FETCH’ and “PORT”.
Type ‘CHECK’ is used to fetch the last updated status of the UPI Number
Type ‘PORT’ is used while transferring mobile number from one PSP to Other PSP
In case of timeout i.e. no final response received by Payer PSP ;the PSP can fire a
request to get the last updated status of the vpa/numeric id
v1.4
Page 14 of 78
Centralised Mapper - TSD
During registration , on checking the availabity this status will refer that the requested
ID already doesn’t exists and the user is allowed to create the requested number as
UPI Number in Mapper
idStatus = “ACTIVE”
During registration , on checking the availabity this status will refer that the requested
ID already exists and active in Mapper. The linked VPA is shared in addr tag in the
response. On basis of this PSP shall prompt customer for choosing the different ID for
the VPA linked to mobile number/ID.
Also during the transfer of UPI Number as Mobile Number to different PSP , GetAdd
API will be trigerred to fetch the status of the Mobile Number which will be “ÄCTIVE”
in different PSP.On proceeding with updation, PSP initiates ReqRegMapper with op
type MODIFY with input of mobile number and new VPA.For using old VPA that was
linked to mobile number I has to re-initiate update from that respective app again. (-
- Refer Section 3.1 --)
idStatus = “INACTIVE”
This status refers that the requested UPI number is created but in ‘INACTIVE’ status
but still will be linked to VPA. Hence , this will not be allowed for the payment
idStatus = “DEREGISTER’
This status refers that the ID has been created and deregistered . In case of Mobile
Number since there is no cooling period , user can initiate the registration process for
reuse. In case of Numeric ID , the ID will be available for 6 months with the
‘DEREGISTER’Status. By the same VPA (Same User) the ID can be re –activated before
6 months ( --Refer Section 3.1 --). Later the ID shall be available for other users
idStatus=”BLOCKED”
This status is used to identify blocked/ blacklisted VPA/ID that may be unavailable as
per pre-defined compliance checks.
v1.4
Page 15 of 78
Centralised Mapper - TSD
v1.4
Page 16 of 78
Centralised Mapper - TSD
v1.4
Page 17 of 78
Centralised Mapper - TSD
Note : Fetch cannnot be used for the creation of UPI since , this can be used to retrieve
the details of created UPI number and it is always & already linked to VPA
v1.4
Page 18 of 78
Centralised Mapper - TSD
Note : Mapper will also send the notification of Porting of UPI Number to old PSP
through RegRegMapperConfirmation and receive the response
v1.4
Page 19 of 78
Centralised Mapper - TSD
7 PSP Sync
The approach to sync the list of UPI Numbers Registered / Modified / Deleted between
PSP and UPI Central Mapper has been described below.
1. Firstly, Any operation that is performed on the UPI Number will be notified in
a response to PSP through Online. During ‘ PORT’ (Transfer of Mobile Number
from One PSP to Other PSP ), the Previous PSP will also be notified
through ReqMapperConfirmation API.
2. Also the status of UPI Number can be retrieved through Online using
ReqGetAdd API ‘Check’ & ‘Fetch’ option anytime
Along with above provision, We will also facilitate Bank/PSP providing a Day Wise
Report through URCS system . In the provided Central Mapper Report an entry will be
made for every operation or the changes performed on the UPI Number in a
corresponding day .
a. The Report will be generated after last settlement cycle and will be
placed in Bank Folder.
b. Below details are captured in the report
v1.4
Page 20 of 78
Centralised Mapper - TSD
e.
8 API Specification
RegMapper API
This API shall be used by PSP for adding and updating the numeric id of the customer
in the central mapper as per customer’s consent.
ReqRegMapper
<upi:ReqRegMapper xmlns:upi=”http://npci.org/upi/schema/”>
<Head ver=”2.0” ts=”” orgId=”” msgId=”” prodType= “UPI”/>
<Txn id=”” note=”” refId=”” refUrl=”” ts=”” type=”CMREGISTRATION”
op=”ADD|MODIFY” />
<Payer addr=”” name=”” seqNum=”” type=”PERSON|ENTITY” code=””>
<RegIdDetails>
<Id name=”MOBILE|NUMERICID” value=””
setStatus="NEW|ACTIVE|INACTIVE|BLOCK|UNBLOCK|DEREGISTER" />
</RegIdDetails>
<Consent name=”CMREGISTRATION” value=”Y|N” prevVpa="" />
<Device>
<Tag name=”MOBILE” value=””/>
<Tag name=”GEOCODE” value=””/>
<Tag name=”LOCATION” value=”” />
<Tag name=”IP” value=””/>
<Tag name=”TYPE” value=”MOB|IVR|USDC”/>
<Tag name=”ID” value=””/>
<Tag name=”OS” value=””/>
<Tag name=”APP” value=””/>
<Tag name=”CAPABILITY” value=””/>
<Tag name=”TELECOM” value=””/>
</Device>
</Ac>
<Ac addrType="ACCOUNT">
<Detail name="IFSC" value=""/>
<Detail name="ACTYPE" value=""/>
<Detail name="ACNUM" value=""/>
</Ac>
<Ac addrType ="MOBILE">
<Detail name="MMID" value=""/>
<Detail name="MOBNUM" value=""/>
</Ac>
v1.4
Page 21 of 78
Centralised Mapper - TSD
NOTE: In case of mobile number transfer b/w PSPs new PSP shall fire
a ReqGetAdd first and fetch the old active VPA for validation by the
customer followed by getting consent to update the same. The
ReqRegMapper shall be fired with the VPA received in RespGetAdd in
the ReqRegMapper under tag - prevVpa i.e. last updated vpa
For Numeric ID, addr tag is not mandatory. For Mobile Number , addr
tag is mandatory in response in which Username of the VPA will be
masked and handle will not be present
RespRegMapper
< upi: RespRegMapper xmlns: upi=”http://npci.org/upi/schema/”>
<Head ver=”2.0” ts=”” orgId=”” msgId=”” prodType= “UPI” />
<Txn id=”” note=”” refId=”” refUrl=”” ts=”” type=”CMREGISTRATION”
op=”ADD|MODIFY”/>
<Resp reqMsgId=”” result=”SUCCESS|FAILURE” errCode=”” >
<RegIdDetails addr=””> <!—VPA of customer. In case of mobile
number transfer b/w PSPs the response shall have the final/latest VPA as per CM! --
>
<Id name=”MOBILE|NUMERICID” value=”” setStatus="
NEW|ACTIVE|INACTIVE|BLOCK|UNBLOCK|DEREGISTER " expiryTs = “” />
</RegIdDetails>
</Resp>
ReqValAdd
<upi:ReqValAdd xmlns:upi=”http://npci.org/upi/schema/”>
<Head ver=”2.0” ts=”” orgId=”” msgId=”” prodType= “UPI”/>
<Txn id=”” note=”” refId=”” refUrl=”” ts=”” type=”ValAdd” custRef=”” />
<Payer addr=”” name=”” seqNum=”” type=”PERSON|ENTITY” code=””>
<Info>
<Identity id=”” type=”PAN|AADHAAR|ACCOUNT” verifiedName=”” />
<Rating VerifiedAddress=”TRUE|FALSE”/>
</Info>
<Device>
<Tag name=”MOBILE” value=””/>
<Tag name=”GEOCODE” value=””/>
v1.4
Page 22 of 78
Centralised Mapper - TSD
RespValAdd
The new attributes shall be used to fetch the value of both – Numeric ID (numId) and
the VPA (addr) linked to it.
<upi:RespValAdd xmlns:upi=”http://npci.org/upi/schema/”>
<Head ver=”2.0” ts=”” orgId=”” msgId=”” prodType= “UPI”/>
<Txn id=”” note=”” refId=”” refUrl=”” ts=”” type=”ValAdd” custRef=”” />
<Resp reqMsgId=”” result=”SUCCESS|FAILURE” errCode=”” maskName=””
code=”” type=”” IFSC=”” accType=”” IIN=”” cmId=”” addr=”” channel=””>
<Merchant >
<Identifier subCode=”” mid=”” sid=”” tid=”” merchantType=”” merchantGenre=””
onBoardingType=”” pinCode=”” regIdNo=”” tier=”” />
<Name brand=”” legal=”” franchise=””/>
<Ownership type=””/>
</Merchant>
<FeatureSupported value=”” />
</Resp>
</upi:RespValAdd>
ReqGetAdd
<upi:ReqGetAdd xmlns:upi="http://npci.org/upi/schema/">
<Head ver="2.0" ts="" orgId="" msgId="" prodType="UPI"/>
<Txn id="" note="" refId="" refUrl="" ts="" type="CHECK|FETCH|PORT"
subType=”ID|VPA”/>
<!—For subType=”VPA”, RegIdDetails block not required
For subType=”ID” , Payer.addr + RegIdDetails.value is mandatory -->
v1.4
Page 23 of 78
Centralised Mapper - TSD
RespGetAdd
<upi: RespGetAdd xmlns:upi="http://npci.org/upi/schema/">
<Head ver="2.0" ts="" orgId="" msgId="" prodType="UPI" />
<Txn id="" note="" refId="" refUrl="" ts="" type="CHECK|FETCH|PORT”/>
<Resp reqMsgId="" result="SUCCESS|FAILURE" errCode="">
<RegIdDetails addr="" type="PERSON|ENTITY" idStatus="
NEW|ACTIVE|INACTIVE|BLOCK|UNBLOCK|DEREGISTER" lastUpdatedTs=""
channel="MOB|USDC|IVR" >
<!—VPA of customer !-->
<Id name="MOBILE" value=""/>
< Id name="NUMERICID" value="" seqNum="1|2" />
</RegIdDetails>
</Resp>
</upi:RespGetAdd>
Note : Type ‘PORT’ will while porting of mobile number from one PSP to Other
PSP. The ‘result’ will be success if the number is available and the PSP can
initiate the RegregMapper API for modify request. When ‘result’ is failure user
has to register the mobile number for central mapper
ReqPay API
ReqPay
<upi:ReqPay xmlns:upi="http://npci.org/upi/schema/">
<Head ver="2.0" ts="" orgId="" msgId="" prodType= "UPI"/>
<Meta>
<Tag name="PAYREQSTART" value=""/>
<Tag name="PAYREQEND" value=""/>
</Meta>
v1.4
Page 24 of 78
Centralised Mapper - TSD
v1.4
Page 25 of 78
Centralised Mapper - TSD
v1.4
Page 26 of 78
Centralised Mapper - TSD
RespPay
<upi:RespPay xmlns:upi="http://npci.org/upi/schema/">
<Head ver="2.0" ts="" orgId="" msgId="" prodType= "UPI"/>
<Txn id="" note="" refId="" custRef="" refUrl="" ts="" purpose=""
type="PAY|COLLECT|DEBIT|CREDIT|REVERSAL|REFUND" subType="" initiationMode=""
orgTxnId="" refCategory="">
<RiskScores>
<Score provider="sp" type="TXNRISK" value=""/>
<Score provider="npci" type="TXNRISK" value=""/>
</RiskScores>
</Txn>
v1.4
Page 27 of 78
Centralised Mapper - TSD
ReqMapperConfirmation API
ReqMapperConfirmation
<upi:ReqMapperConfirmation
xmlns:upi="http://npci.org/upi/schema/">
<Head ver="2.0" ts="" orgId="" msgId=""/>
<Txn id="" note="" custRef="" refId="" refUrl="" ts="" type="CMREGISTRATION"
orgTxnId=""/>
<TxnConfirmation note="" orgStatus="SUCCESS|FAILURE" op="ADD|MODIFY"
idType="MOBILE|NUMERICID">
<Ref type="PAYER" addr="" cmId="" code="" channel=”MOB|IVR”
status=”DEREGISTER”/>
</TxnConfirmation>
</upi:ReqMapperConfirmation>
RespMapperConfirmation
<upi:RespMapperConfirmation
xmlns:upi="http://npci.org/upi/schema/">
<Head ver="2.0" ts="" orgId="" msgId=""/>
<Txn id="" custRef="" note="" refId="" refUrl="" ts="" type="CMREGISTRATION"
orgTxnId="" />
<Resp reqMsgId="" result="SUCCESS|FAILURE" errCode=""/>
</upi:RespMapperConfirmation>
9 Tag Specifications
ReqRegMapper Field Specifications
Tag Message <XMLTag Occurren Datatyp Length Mandat Enum
Num Item > ce e ory Values
v1.4
Page 28 of 78
Centralised Mapper - TSD
v1.4
Page 29 of 78
Centralised Mapper - TSD
entities,
created by
the
originator
3.1.2 Descriptio note 1..1 Alphanu Min Y
n of the meric Length : 1
transactio Max
n (which Length :
will be 50
printed on
Pass book)
3.1.3 Consumer refId 1..1 Alphanu Min Y
reference meric Length : 1
number to Max
identify Length :
(like Loan 35
number,
etc.)
3.1.4 URL for refUrl 1..1 Alphanu Min Y
the meric Length : 1
transactio Max
n Length :
35
3.1.5 Transactio ts 1..1 ISODate Min Y
n Time Length : 1
origination Max
time by Length :
the creator 255
of the
message
3.1.6 Type of type 1..1 Code Min Y “CMREGI
the Length : 1 STRATIO
Transactio Max N”
n Length :
20
3.1.7 Operation Op 1..1 Code Fixed Y ADD|MO
to be Length DIFY
performed
by the
request
4.1 Details <Payer> 1..1 Alphabe Fixed Y
related to tic value
the Payer
4.1.1 Address of addr 1..1 Alphanu Min Y
the Payer meric Length : 1
Max
Length :
255
4.1.2 Name of name 1..1 Alphanu Min Y
the Payer meric Length : 1
Max
v1.4
Page 30 of 78
Centralised Mapper - TSD
Length :
99
4.1.3 Unique seqNum 1..1 Numeri Min Y
identifier c Length : 1
for each Max
transactio Length :
n inside a 35
file
including
payer and
payee
4.1.4 Type of type 1..1 Code Fixed Y PERSON|
the Payer value ENTITY
4.1.5 Merchant code 1..1 Numeri Length : 4 N
Classificati c
on Code -
MCC
5.1 Details of <RegIdD 1..1 Code Fixed Y
the etails> value
Registratio
n ID
5.1.1 Name <name> 1..n Alphabe Fixed Y MOBILE|
tic value NUMERI
C ID
5.1.2 Value value 1..n Alphanu Min Y
meric Length : 1
Max
Length :
100
5.1.4 Status of setStatus 1..1 Alphabe Min N NEW|AC
the ID tic Length : 1 TIVE|INA
Max CTIVE|BL
Length : OCK|UN
35 BLOCK|D
EREGIST
ER
6.1 Consent <Consen 1..n Fixed Y
t> value
6.1.1 Name Name 1..n Alphanu Min Y CMREGIS
meric Length : 1 TRATION
Max
Length :
50
6.1.2 Type Type 1..n Code Fixed Y NUMERI
value CID|MO
BILE
6.1.3 Value Value 1..1 Code Fixed Y Y|N
value
6.1.4 Previous prevVpa 1..1 Numeri Min N Only
VPA c Length : 6 during
‘Modify’
v1.4
Page 31 of 78
Centralised Mapper - TSD
Max
Length : 9
7.1 Details of <Payer.D 1..n Alphabe Fixed Y
device evice> tic value
from
which the
transactio
n was
initiated
7.1.1 Name of name 1..n Code(M Fixed Y MOBILE:
the OBILE,G value 91nnnnn
property EOCOD nnnnn
E,LOCAT GEOCOD
ION,IP,T E:nn.nnn
YPE,ID, n,nn.nnn
O n
S,APP,C LOCATIO
A N:Area
PABILIT with city,
Y state and
,TELECO Country
M Code
01-23-
Terminal
Address
24-36-
Terminal
City
37-38-
Terminal
State
Code
39-40-
Terminal
Country
Code
IP:Valid
IP
address
format(v
4,v6)
TYPE:Mi
n Length
– 1 , Max
Length –
20 (Refer
Rule_03
5) ID:Min
Length –
1 , Max
Length
v1.4
Page 32 of 78
Centralised Mapper - TSD
–
3
5
OS:Min
Length –
1 , Max
Length
–
2
0
APP:Min
Length –
1 , Max
Length –
2
0
CAPABILI
TY:Min
Length –
1 , Max
Length –
99 (refer
to DE-
61)
e
.g:
“520000
0200010
004000
6392929
29292
“
.
TELECO
M
OPERAT
OR:Min
Length-
1,Max
Length-
99 (It is
mandato
ry for
USSD)
7.1.2 Value of value 1..n Alphanu Min Y
the meric Length : 1
property Max
Length :
20
v1.4
Page 33 of 78
Centralised Mapper - TSD
v1.4
Page 34 of 78
Centralised Mapper - TSD
v1.4
Page 35 of 78
Centralised Mapper - TSD
v1.4
Page 36 of 78
Centralised Mapper - TSD
The character
"T" is used as
the delimiter.
HH:mm:ss: sss
– is the time:
hours,
minutes,
seconds and
milliseconds.
‘h’ 'Z' part
denotes the
time zone in
the format +-
hh:mm
HH/hh = two
digits of hour
(00 through
23) (am/pm
NOT allowed)
mm = two
digits of
minute (00
through 59)
ss = two
digits of
second (00
through 59)
sss= three
digit of milli
second (000
through 999)
+/- hh:mm =
followed by
time zone
difference
from GMT in
hours and
minut
es.This is
Mandatory
v1.4
Page 37 of 78
Centralised Mapper - TSD
v1.4
Page 38 of 78
Centralised Mapper - TSD
created Max
the Length :
message 20
2.1.4 Message msgId 1..1 Alphanu Min Y
identifier- meric Length : 1
used to Max
correlate Length :
between 35
request
and
response
2.1.5 Product prodTyp 1..1 Alphanu Min Y UPI
Type e meric Length : 1
Max
Length :
15
3.1 Transactio <Txn> 1..1 Alphabe Fixed Y
n tic value
informatio
n, Carried
throughou
t the
system,
visible to
all parties
3.1.1 Unique id 1..1 Alphanu Length : Y
Identifier meric 35
of the
transactio
n across all
entities,
created by
the
originator
3.1.2 Descriptio note 1..1 Alphanu Min Y
n of the meric Length : 1
transactio Max
n(which Length :
will be 50
printed on
Pass book)
3.1.3 Consumer refId 1..1 Alphanu Min Y
reference meric Length : 1
number to Max
identify Length :
(like Loan 35
number,
etc.)
3.1.4 URL for refUrl 1..1 Alphanu Min Y
the meric Length : 1
Max
v1.4
Page 39 of 78
Centralised Mapper - TSD
transactio Length :
n 35
3.1.5 Transactio ts 1..1 ISODate Min Y
n Time Length : 1
origination Max
time by Length :
the creator 255
of the
message
3.1.6 Type of type 1..1 Code Min Y “CHECK|FE
the Length : 1 TCH|PORT”
Transactio Max
n Length :
20
4.1 Details <Payer> 1..1 Alphabe Fixed Y
related to tic value
the Payer
4.1.1 Address of addr 1..1 Alphanu Min Y
the Payer meric Length : 1
Max
Length :
255
4.1.2 Name of name 1..1 Alphanu Min Y
the Payer meric Length : 1
Max
Length :
99
4.1.3 Unique seqNum 1..1 Numeri Min Y
identifier c Length : 1
for each Max
transactio Length :
n inside a 35
file
including
payer and
payee
4.1.4 Type of type 1..1 Code Fixed Y PERSON|E
the Payer value NTITY
4.1.5 Merchant code 1..1 Numeri Length : 4 N
Classificati c
on–n Code
- MCC
5.1 Details of <RedIdD 1..1 Code Fixed Y
the etails> value
Registratio
n ID
5.1.1 Name <name> 1..n Alphabe Fixed Y
tic value
5.1.2 Value value 1..n Alphanu Min Y
meric Length : 1
Max
v1.4
Page 40 of 78
Centralised Mapper - TSD
Length :
100
6.1 Consent <Consen 1..n Alphabe Fixed Y
t> tic value
6.1.1 Name Name 1..n Alphanu Min Y CMREGISTR
meric Length : 1 ATION
Max
Length :
50
6.1.2 Type Type 1..n Code Fixed Y NUMERICID
value |MOBILE
6.1.3 Value Value 1..1 Code Fixed Y Y|N
value
7.1 Details of <Payer.D 1..n Alphabe Fixed Y
device evice> tic value
from
which the
transactio
n was
initiated
7.1.1 Name of name 1..n Code(M Fixed Y MOBILE:91
the OBILE,G value nnnnnnnnn
property EOCOD n
E,LOCAT GEOCODE:
ION,IP,T nn.nnnn,nn
YPE,ID, .nnnn
O LOCATION:
S,APP,C Area with
A city, state
PABILIT and
Y Country
,TELECO Code
M 01-23-
Terminal
Address
24-36-
Terminal
City
37-38-
Terminal
State Code
39-40-
Terminal
Country
Code
IP:Valid IP
address
format(v4,v
6)
TYPE:Min
Length – 1 ,
v1.4
Page 41 of 78
Centralised Mapper - TSD
Max Length
– 20 (Refer
Rule_035)
ID:Min
Length – 1 ,
Max Length
– 35
OS:Min
Length – 1 ,
Max Length
– 20
APP:Min
Length – 1 ,
Max Length
–
20
CAPABILITY
:Min
Length – 1 ,
Max
Length –
99 (refer to
DE-
61) e.g:
“52000002
000100040
00
639292929
292 “.
TELECOM
OPERATOR:
Min
Length-
1,Max
Length-99
(It is
mandatory
for USSD)
7.1.2 Value of value 1..n Alphanu Min Y
the meric Length : 1
property Max
Length :
20
v1.4
Page 42 of 78
Centralised Mapper - TSD
v1.4
Page 43 of 78
Centralised Mapper - TSD
created by
the
originator
3.1.2 Descriptio note 1..1 Alpha Min Y
n of the numer Length : 1
transactio ic Max
n (which Length : 50
will be
printed on
Pass book)
3.1.3 Consumer refId 1..1 Alpha Min Y
reference numer Length : 1
number to ic Max
identify Length : 35
(like Loan
number,
etc.)
3.1.4 URL for refUrl 1..1 Alpha Min Y
the numer Length : 1
transactio ic Max
n Length : 35
3.1.5 Transactio ts 1..1 ISODa Min Y
n teTim Length : 1
origination e Max
time by Length :
the creator 255
of the
message
3.1.6 Type of type 1..1 Code Min Y “CHECK|FETC
the Length : 1 H|PORT”
Transactio Max
n Length : 20
4.1 Response <Resp> 1..1 Alpha Fixed value Y
betic
v1.4
Page 44 of 78
Centralised Mapper - TSD
HH/hh = two
digits of hour
(00 through
23) (am/pm
NOT allowed)
mm = two
digits of
v1.4
Page 45 of 78
Centralised Mapper - TSD
minute (00
through 59)
ss = two
digits of
second (00
through 59)
sss= three
digit of milli
second (000
through 999)
+/- hh:mm =
followed by
time zone
difference
from GMT in
hours and
minut
es.This is
Mandatory
5.1.5 Initiating Channel 1..1 Alpha Fixed value Y MOB|USDC|I
Channel betic VR
5.1.6 Name <name> 1..n Alpha Fixed value Y “MOBILE|NU
betic MERICID”
5.1.7 Value value 1..n Alpha Min Y
numer Length : 1
ic Max
Length :
100
5.1.8 Unique seqNum 1..1 Nume Min Y
identifier ric Length : 1
for each Max
transactio Length : 35
n inside a
file
including
payer and
payee
ReqMapperConfirmation Field
Specifications
Tag Message <XMLTag Occurr Datat Length Mand Enum Values
Num Item > ence ype atory
1.1 API Name <ReqMa 1..1 Y
pperConf
irmation
>
v1.4
Page 46 of 78
Centralised Mapper - TSD
v1.4
Page 47 of 78
Centralised Mapper - TSD
v1.4
Page 48 of 78
Centralised Mapper - TSD
v1.4
Page 49 of 78
Centralised Mapper - TSD
RespMapperConfirmation Field
Specifications
Tag Message <XMLTag Occurr Datat Length Mand Enum Values
Num Item > ence ype atory
1.1 API Name <RespMa 1..1 Y
pperConf
irmation
>
1.1.1 API xmlns 1..1 Alpha Min Y
Schema numer Length : 1
namespac ic Max
e Length :
255
2.1 Header <Head> 1..1 Alpha Fixed value Y
betic
2.1.1 Version of ver 1..1 Nume Min Y
the API ric Length : 1
Max
Length : 6
2.1.2 Time of ts 1..1 ISODa Min Y
request te Length : 1
from the Time Max
creator of Length :
the 255
message
2.1.3 Organizati orgId 1..1 Nume Min Y
on id that ric Length : 1
created Max
the Length : 20
message
v1.4
Page 50 of 78
Centralised Mapper - TSD
v1.4
Page 51 of 78
Centralised Mapper - TSD
will be
printed on
Pass book)
3.1.7 Original orgTxnId 1..1 Alpha Fixed value Y
Transactio betic
n Id. (Txn
Id of
GetAddres
s API)
3.1.8 Customer custRef 1..1 Nume Length=12 Y
reference ric
number
for the
initiated
transactio
n
4.1 Response <Resp> 1..1 Alpha Fixed value Y
betic
4.1.1 Request reqMsgI 1..1 Alpha Length: 35 Y
Message d numer
identifier ic
4.1.2 Result of result 1..1 Code Min Y
the Length : 1
transactio Max
n Length : 20
4.1.3 Error code errCode 1..1 Alpha Min Y
if failed numer Length : 1
ic Max
Length : 20
10 Sample Dumps
v1.4
Page 52 of 78
Centralised Mapper - TSD
v1.4
Page 53 of 78
Centralised Mapper - TSD
v1.4
Page 54 of 78
Centralised Mapper - TSD
ts="2017-01-23T14:14:54.040+05:30" type="CHECK"/>
<Payer addr="testuser12345@andb" code="0000" name="TEST USER"
seqNum="1" type="PERSON">
<Device>
<Tag name="MOBILE" value="919848159011"/>
<Tag name="GEOCODE" value="288177,1234"/>
<Tag name="LOCATION" value="Mumbai,Maharashtra"/>
<Tag name="IP" value="124.170.23.22"/>
<Tag name="TYPE" value="MOB"/>
<Tag name="ID" value="000000000000001"/>
<Tag name="OS" value="android"/>
<Tag name="APP" value="org.npci.upi.security.commonsapp"/>
<Tag name="CAPABILITY" value="5200000200010004000639292929292"/>
</Device>
<Consent name="CMREGISTRATION" value="Y"/>
<RegIdDetails>
<Id name="NUMERICID" value="25082061"/>
</RegIdDetails>
</Payer>
</ns2:ReqGetAdd>
v1.4
Page 55 of 78
Centralised Mapper - TSD
<ns2:ReqRegMapper
xmlns:ns2="http://npci.org/upi/schema/">
<Head msgId="XYD1442cdd8a121449cae3ab0034f72b165" orgId="159047"
prodType="UPI" ts="2021-08-03T13:53:03+05:30" ver="2.0"/>
<Txn custRef="105015571146" id="MMM0000000000005t0xf6TRJPfOSpUgE00"
note="Mapper" op="MODIFY" refId="702314088080" refUrl="http://upi"
v1.4
Page 56 of 78
Centralised Mapper - TSD
ts="2017-01-23T14:14:54.040+05:30" type="CMREGISTRATION"/>
<Payer addr="addmobile@csb" code="0000" name=""
seqNum="1" type="PERSON">
<Device>
<Tag name="MOBILE" value="919769948645"/>
<Tag name="GEOCODE" value=""/>
<Tag name="LOCATION" value=""/>
<Tag name="IP" value="124.170.23.22"/>
<Tag name="TYPE" value="MOB"/>
<Tag name="ID" value="000000000000001"/>
<Tag name="OS" value="android"/>
<Tag name="APP" value="org.npci.upi.security.commonsapp"/>
<Tag name="CAPABILITY" value="5200000200010004000639292929292"/>
</Device>
<Ac addrType="ACCOUNT">
<Detail name="ACTYPE" value="SAVINGS"/>
<Detail name="ACNUM" value="" />
<Detail name="IFSC" value="ANDB0000029"/>
</Ac>
<Consent name="CMREGISTRATION" value="Y"/>
<RegIdDetails>
<Id name="MOBILE" setStatus="DEREGISTER" value="9848055445"/>
</RegIdDetails>
</Payer>
</ns2:ReqRegMapper>
v1.4
Page 57 of 78
Centralised Mapper - TSD
<ns2:ReqRegMapper
xmlns:ns2="http://npci.org/upi/schema/">
<Head msgId="XYD1442cdd8a121449cae3ab0034f72b165" orgId="159047"
prodType="UPI" ts="2021-08-03T13:45:41+05:30" ver="2.0"/>
<Txn custRef="105015571146" id="MMM0000000000005t0xf6TRJPfORDCsboA"
note="Mapper" op="MODIFY" refId="702314088080" refUrl="http://upi"
ts="2017-01-23T14:14:54.040+05:30" type="CMREGISTRATION"/>
<Payer addr="addnumeric01@csb" code="0000" name=""
seqNum="1" type="PERSON">
<Device>
<Tag name="MOBILE" value="919769948645"/>
<Tag name="GEOCODE" value=""/>
<Tag name="LOCATION" value=""/>
<Tag name="IP" value="124.170.23.22"/>
<Tag name="TYPE" value="MOB"/>
<Tag name="ID" value="000000000000001"/>
<Tag name="OS" value="android"/>
<Tag name="APP" value="org.npci.upi.security.commonsapp"/>
<Tag name="CAPABILITY" value="5200000200010004000639292929292"/>
</Device>
<Ac addrType="ACCOUNT">
<Detail name="ACTYPE" value="SAVINGS"/>
<Detail name="ACNUM" value="" />
<Detail name="IFSC" value="ANDB0000029"/>
</Ac>
<Consent name="CMREGISTRATION" value="Y"/>
<RegIdDetails>
<Id name="NUMERICID" setStatus="DEREGISTER" value="55445532"/>
</RegIdDetails>
</Payer>
</ns2:ReqRegMapper>
v1.4
Page 58 of 78
Centralised Mapper - TSD
v1.4
Page 59 of 78
Centralised Mapper - TSD
v1.4
Page 60 of 78
Centralised Mapper - TSD
v1.4
Page 61 of 78
Centralised Mapper - TSD
</Payee>
</Payees>
</ns2:ReqPay>
v1.4
Page 62 of 78
Centralised Mapper - TSD
v1.4
Page 63 of 78
Centralised Mapper - TSD
v1.4
Page 64 of 78
Centralised Mapper - TSD
UyVKLZVLyScXD1sXPd1693Ez4wS+pDpiNQUG/Q0GUmr2yv+pxrAw7vsLHLGQ4T5GxNI0d
KYlZ0rdeGyK/APUqZKvHmtHt/SOasZn57113kXDlS+035mtrftXY1xLPb2uYBo+dUK1/IFQ
cppmy5oNSHSpJ9yXNlswK7M83PyG7KCudgLL3CS+O6xMM+RpwKItYcXjiTB0aoQmxtke67
eg==</Data>
</Cred>
</Creds>
<Amount value="49.00" curr="INR"/>
</Payer>
<Payees>
<Payee addr="fayaz@andb" name="" seqNum="1" type="PERSON" code="0000"
cmId="9769948645">
<Info>
<Identity type="ACCOUNT" verifiedName="" id=""/>
<Rating verifiedAddress="TRUE"></Rating>
</Info>
<Device>
<Tag name="MOBILE" value="919000000006"/>
<Tag name="GEOCODE" value=""/>
<Tag name="LOCATION" value=""/>
<Tag name="IP" value="124.170.23.22"/>
<Tag name="TYPE" value="mob"/>
<Tag name="ID" value="0000000000000023"/>
<Tag name="OS" value="android"/>
<Tag name="APP" value="com.icicibank.eazy"/>
<Tag name="CAPABILITY" value="5200000200010004000639292929292"/>
</Device>
<Ac addrType="ACCOUNT">
<Detail name="IFSC" value="ANDB0009009"/>
<Detail name="ACNUM" value="" />
<Detail name="ACTYPE" value="SAVINGS"/>
</Ac>
<Amount value="49.00" curr="INR"/>
</Payee>
</Payees>
</ns2:ReqPay>
v1.4
Page 65 of 78
Centralised Mapper - TSD
<Rules>
<Rule name="EXPIREAFTER" value="1"/>
<Rule name="MINAMOUNT" value="370.00"/>
</Rules>
</Txn>
<Resp reqMsgId="5t0xf6ZKer9I5Bve9Vw" result="SUCCESS">
<Ref IFSC="ANDB0000001" acNum="" accType="SAVINGS"
addr="@andb" approvalNum="654321" code="0000"
regName="" respCode="00" seqNum="1" settAmount="49.00"
settCurrency="INR" type="PAYER"/>
</Resp>
</ns2:RespPay>
v1.4
Page 66 of 78
Centralised Mapper - TSD
</Device>
<Ac addrType="ACCOUNT">
<Detail name="IFSC" value="ANDB0000001"/>
<Detail name="ACTYPE" value="SAVINGS"/>
<Detail name="ACNUM" value="" />
</Ac>
<Amount value="49.00" curr="INR"/>
</Payer>
<Payees>
<Payee addr="fayaz@andb" name="" seqNum="1" type="PERSON" code="0000"
cmId="9769948645">
<Info>
<Identity type="ACCOUNT" verifiedName="" id=""/>
<Rating verifiedAddress="TRUE"></Rating>
</Info>
<Device>
<Tag name="MOBILE" value="919000000006"/>
<Tag name="GEOCODE" value=""/>
<Tag name="LOCATION" value=""/>
<Tag name="IP" value="124.170.23.22"/>
<Tag name="TYPE" value="mob"/>
<Tag name="ID" value="0000000000000023"/>
<Tag name="OS" value="android"/>
<Tag name="APP" value="com.icicibank.eazy"/>
<Tag name="CAPABILITY" value="5200000200010004000639292929292"/>
</Device>
<Ac addrType="ACCOUNT">
<Detail name="IFSC" value="ANDB0009009"/>
<Detail name="ACNUM" value="" />
<Detail name="ACTYPE" value="SAVINGS"/>
</Ac>
<Amount value="49.00" curr="INR"/>
</Payee>
</Payees>
</ns2:ReqPay>
v1.4
Page 67 of 78
Centralised Mapper - TSD
<Rules>
<Rule name="EXPIREAFTER" value="1"/>
<Rule name="MINAMOUNT" value="370.00"/>
</Rules>
</Txn>
<Resp reqMsgId="5t0xf6ZKer9I5Bwjig3" result="SUCCESS">
<Ref IFSC="ANDB0009009" acNum="" accType="SAVINGS"
addr="@andb" approvalNum="654321" code="0000"
regName="" respCode="00" seqNum="1"
settAmount="49.00" settCurrency="INR" type="PAYEE"/>
</Resp>
</ns2:RespPay>
<ns2:RespPay
xmlns:ns2="http://npci.org/upi/schema/"
xmlns:ns3="http://npci.org/cm/schema/">
<Head ver="2.0" ts="2021-08-20T09:19:30+05:30" orgId="NPCI"
msgId="5t0xf6ZKer9I5By9QeE"/>
<Txn id="MMM0000000000005t0xf6TRJPgu7pSJ1IY" note="Sta" refId="Ref"
refUrl="https://www.sbi.co.in/" ts="2018-11-28T19:00:11+05:30" type="PAY"
custRef="123209246064" initiationMode="00" purpose="00">
<RiskScores>
<Score provider="psp1" type="TXNRISK" value="00090"/>
<Score provider="psp3" type="TXNR2" value="00090"/>
<Score provider="NPCI" type="TXNRISK" value="00999"/>
</RiskScores>
</Txn>
<Resp reqMsgId="5z68jRTbjsje5CSRZtK" result="SUCCESS">
<Ref type="PAYER" seqNum="1" addr="@andb" settAmount="49.00"
settCurrency="INR" approvalNum="654321" respCode="00" regName=""
orgAmount="49.00" acNum="" IFSC="ANDB0000001" code="0000" accType="SAVINGS"/>
<Ref type="PAYEE" seqNum="1" addr="@andb" settAmount="49.00"
settCurrency="INR" approvalNum="654321" respCode="00" regName=""
orgAmount="49.00" acNum="" IFSC="ANDB0009009" code="0000" accType="SAVINGS"
cmId="9769948645"/>
</Resp>
</ns2:RespPay>
v1.4
Page 68 of 78
Centralised Mapper - TSD
v1.4
Page 69 of 78
Centralised Mapper - TSD
</Device>
<Consent name="CMREGISTRATION" value="Y"/>
<RegIdDetails>
<Id name="MOBILE" value="9848020212"/>
</RegIdDetails>
</Payer>
</ns2:ReqGetAdd>
v1.4
Page 70 of 78
Centralised Mapper - TSD
Fetch by VPA
Request to Fetch by VPA
v1.4
Page 71 of 78
Centralised Mapper - TSD
v1.4
Page 72 of 78
Centralised Mapper - TSD
v1.4
Page 73 of 78
Centralised Mapper - TSD
v1.4
Page 74 of 78
Centralised Mapper - TSD
11 Error Codes
v1.4
Page 75 of 78
Centralised Mapper - TSD
Abbreviations
NPCI National Payments Corporation of India
UPI Unified Payments Interface
API Application Program Interface
cmId Central Mapper Id. UPI Number linked to VPA
v1.4
Page 76 of 78
Centralised Mapper - TSD
References
1. BRD – Numerid Mapper for UPI
2. UPI TSD - Unified Payments Interface 2 0 TSD v1 42
About NPCI
National Payments Corporation of India (NPCI) is an umbrella organisation for
operating retail payments and settlement systems in India
It is an initiative by the Reserve Bank of India (RBI) and Indian Banks’ Association
(IBA) under the provisions of the Payment and Settlement Systems Act, 2007, for
creating a robust Payment & Settlement Infrastructure in India.
Considering the utility nature of the objects of NPCI, it has been incorporated as a
“Not for Profit” Company under the provisions of Section 25 of Companies Act 1956
(now Section 8 of Companies Act 2013), with an intention to provide infrastructure to
the entire Banking system in India for physical as well as electronic payment and
settlement systems.
The ten core promoter banks are State Bank of India, Punjab National Bank, Canara
Bank, Bank of Baroda, Union Bank of India, Bank of India, ICICI Bank, HDFC Bank,
Citibank and HSBC.
RuPay is an Indigenously developed Payment System – designed to meet the
expectation and needs of the Indian consumer, banks and merchant eco-system
With Immediate Payment Service (IMPS), India has become the leading country
in the world in real time payments in retail sector
National Automated Clearing House (NACH), an offline web-based system for
bulk push and pull transactions. NACH provides electronic mandate platform to
register mandates facilitating paper less collection process for the corporates and
banks
Aadhaar Payment Bridge (APB) System is helping the Government and
Government agencies in making the Direct Benefit Transfers for various Central as
well as State sponsored schemes
National Financial Switch (NFS) is the largest network of shared Automated
Teller Machines (ATMs) in India
Unified Payments Interface (UPI) has been termed as the revolutionary product
in the payment system
Bharat Bill Payment System is offering one-stop bill payment solution for all
recurring payments
National Electronic Toll Collection (NETC) meets the electronic tolling
requirements of the Indian market by identifying the vehicle uniquely through a
FASTag
With these products the aim is to transform India into a ‘less-cash’ society by touching
every Indian with one or other payment services.
With each passing year we are moving towards our vision to be the best payments
network globally
v1.4
Page 77 of 78
Centralised Mapper - TSD
End of Document
v1.4
Page 78 of 78