0% found this document useful (0 votes)
55 views79 pages

Numeric Development Flow

The document outlines the functionalities and technical specifications of the Centralized Mapper for UPI Number management by the National Payments Corporation of India (NPCI). It details the registration process, API operations, and guidelines for creating and managing UPI Numbers, including Numeric IDs and Mobile Numbers. Additionally, it provides information on error codes, API specifications, and sample use cases to assist banks in implementing the Centralized Mapper effectively.

Uploaded by

Rajesh Jatav
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
55 views79 pages

Numeric Development Flow

The document outlines the functionalities and technical specifications of the Centralized Mapper for UPI Number management by the National Payments Corporation of India (NPCI). It details the registration process, API operations, and guidelines for creating and managing UPI Numbers, including Numeric IDs and Mobile Numbers. Additionally, it provides information on error codes, API specifications, and sample use cases to assist banks in implementing the Centralized Mapper effectively.

Uploaded by

Rajesh Jatav
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 79

CENTRALIZED MAPPER

FOR UPI NUMBER-TSD


1.6
Centralised Mapper - TSD

Copyright © 2004-2020 NPCI ® All Rights Reserved


National Payments Corporation of India (NPCI), Mumbai, Maharashtra, India
The Programs, which include both the software and documentation, contain
information that is proprietary to National Payments Corporation of India and its
licensors; they are provided under a license agreement containing restrictions on use
and disclosure and are also protected by copyright and other intellectual and industrial
property laws. Except as may be expressly permitted in such license agreement, no
part of the Document may be reproduced or transmitted in any form or by any means,
electronic or mechanical, for any purpose.
The information contained in this document is subject to change without notice. If
you find any problems in the documentation, please report them to us in writing. This
document is not warranted to be error-free.

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

What this guide covers ......................................................................................................................... 5

Prerequisites......................................................................................................................................... 5

Document History ................................................................................................................................. 5

1 Introduction ................................................................................................................................. 7

2 Centralized Mapper ...................................................................................................................... 7


UPI Number ................................................................................................................................ 7
UPI Number as Numeric ID (N) ........................................................................................................... 7
UPI Number as Mobile Number ID (M) .............................................................................................. 8
UPI Number and VPA .......................................................................................................................... 8
Mapper Operations .................................................................................................................... 8

3 RegMapper API ............................................................................................................................ 9


Registration Flow ....................................................................................................................... 9
Creation of UPI Number as Numeric ID by New User ......................................................................... 9
Creation of UPI Number as Numeric ID Existing User ....................................................................... 10
Deregistration of UPI Number .......................................................................................................... 10
Modification of UPI Number ............................................................................................................. 10
RegRegMapper Implementation Usage ............................................................................................ 11

4 ReqValAdd API ........................................................................................................................... 13


Financial Flow........................................................................................................................... 13

5 Get Address API .......................................................................................................................... 13


Types of GetAdd ....................................................................................................................... 14
Status of GetAdd API ................................................................................................................ 15

6 API Flows & Sample Usecases ..................................................................................................... 16


User Creates New UPI Number Successfully ............................................................................. 16
User could not New UPI Number as the number is already available ...................................... 16
User Updating the Status of the UPI Number .......................................................................... 17
User Fetching the Status of the UPI Number through ‘Fetch’ by ‘VPA’ or by ‘ID’ ..................... 17
User Porting the UPI Number (Only Mobile Number ) ............................................................. 18
User tries to create Mobile Number as UPI Number but the mobile number already active in
other PSP ............................................................................................................................................... 19

7 PSP Sync ..................................................................................................................................... 20

v1.4
Page 2 of 78
Centralised Mapper - TSD

8 API Specification ......................................................................................................................... 21


RegMapper API ........................................................................................................................ 21
ReqRegMapper ................................................................................................................................. 21
RespRegMapper ................................................................................................................................ 22
Address Validation API ............................................................................................................. 22
ReqValAdd ........................................................................................................................................ 22
RespValAdd ....................................................................................................................................... 23
Get Address API ........................................................................................................................ 23
ReqGetAdd ........................................................................................................................................ 23
RespGetAdd ...................................................................................................................................... 24
ReqPay API ............................................................................................................................... 24
ReqPay .............................................................................................................................................. 24
RespPay ............................................................................................................................................. 27
ReqMapperConfirmation API ................................................................................................... 28
ReqMapperConfirmation .................................................................................................................. 28
RespMapperConfirmation ................................................................................................................ 28

9 Tag Specifications ....................................................................................................................... 28


ReqRegMapper Field Specifications ......................................................................................... 28
RespRegMapper Field Specifications ........................................................................................ 34
ValAdd New Tag Specification ................................................................................................. 37
ReqPay New Tag Specification ................................................................................................. 38
ReqGetAdd Field Specifications ................................................................................................ 38
RespGetAdd Field Specifications .............................................................................................. 42
ReqMapperConfirmation Field Specifications .......................................................................... 46
RespMapperConfirmation Field Specifications ......................................................................... 50

10 Sample Dumps ........................................................................................................................... 52


Check the availability and add Mobile Number as UPI Number .............................................. 52
Request to Check the availability of Mobile Number ....................................................................... 52
Response from UPI with Available Status ‘New’ ............................................................................... 53
Request to create and add the Mobile Number ............................................................................... 53
Response from UPI for successful addition ...................................................................................... 54
Check the availability and add Numeric ID as UPI Number ...................................................... 54
Request to Check the availability of Numeric ID............................................................................... 54
Response from UPI with Available Status ‘New’ ............................................................................... 55
Request to create and add available Numeric ID.............................................................................. 55
Response from UPI for successful addition ...................................................................................... 56
Deregister UPI Number (Mobile Number) ................................................................................ 56
Request to Deregister Mobile Number ............................................................................................. 56
Response from UPI for Successful Deregistration ............................................................................ 57
Deregister UPI Number (Numeric ID) ....................................................................................... 57
Request to Degregister Numeric ID .................................................................................................. 57
Response from UPI for successful Deregisteration ........................................................................... 58
Financial Transaction through UPI Number (cmId) .................................................................. 59

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

11 Error Codes ................................................................................................................................. 75

Abbreviations ..................................................................................................................................... 76

References .......................................................................................................................................... 77

About NPCI ......................................................................................................................................... 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

What this guide covers


This guide covers the following main topics:
 Technical Specifications of the Centralized Mapper for a numeric UPI ID
 Information about the multiple API’s used in the process
 Tag Specifications for each API that was used in the process
 Error Codes

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

1.3 1. Updated the Cooling 26/7/2021


period to 6 months
2. Numeric digit will be 8-9
3. While transfering mobile
number from one PSP to
other , UPI has to populate
previously linked VPA to the
user
4. Updated the Error Codes
1.4 Updated Sample Dumps – 25/8/2021
Section 9
Updated Section 5 – Added
more clarity
Updated PSP Sync – Section
7
Updated API Flows and
Sample Usecases – Section 6
1.5 Updated PSP Sync 20/10/2021
1.6 PSP Sync and Error codes 09/03/2022

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.

UPI Number as Numeric ID (N)

1. User is allowed to choose a number between 8-9 digit length . The


Mapper should be able to accommodate the number of 6-16 digits
length.
2. User is not allowed to choose 10 and 11 digits number
3. User is not allowed to choose Zero (0) as prefix
4. User is not allowed to use three similar digits at the end of their
Numeric ID
5. User is not allowed to choose a number with all the same digits (0-9) as
their Numeric ID

v1.4
Page 7 of 78
Centralised Mapper - TSD

UPI Number as Mobile Number ID (M)

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

UPI Number and VPA


1. Numeric ID and Mobile Number will be unique by itself across the Central
Mapper

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

4. Multiple Numeric ID can be linked to a single VPA

5. Any Mobile Number can be linked to only one VPA

6. Any VPA can be linked to multiple Numeric ID and/or one Mobile Number

7. Any Numeric ID can be made to ‘Deregister’. The ‘Deregistered’ UPI


Number as Numeric ID will be existing for the user to be made ‘Active’
within 6 months

8. Mobile Number can be made to ‘Inactive’ . It can be made to ‘Active’ at


any point of time

9. PSP can block/unblock UPI Number

10. Transfer of UPI number as Numeric ID between PSP is not allowed

11. Transfer of UPI Number as Mobile Number between PSP will be allowed.

12. Modification of VPA will be based on UPI Number

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

1. Add – Create a new Numeric ID at the time of registration of VPA.


2. Modify – Modify the Numeric ID against VPA by selecting any of the created
Numeric ID’s or Update the UPI Number as Mobile Number against the VPA

@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.

1. Once Pin has been set , PSP will


prompt a request of creating
numeric id . On taking the
consent , a Numeric Id shall be
entered by the user . The user
can also choose mobile number
as numeric id
2. On entering the numeric ID ,
ReqGetAdd API will be triggered
to check the availability of the
id.
3. On success response ,the PSP shall initiate ReqRegMapper API with VPA and
Numeric ID (can be mobile number on Basis of consent) to UPI .

 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

Creation of UPI Number as Numeric ID Existing User


Existing Customer can generate the Numeric ID through Customer Profile Management
ie., updating the VPA. During this activity , customer will be asked for Numeric ID
creation . If the customer agrees , a consent will be taken post which ReqRegMapper
API will be initiated through PSP for Numeric ID creation.

 Note: Apparently, Mobile Number also can be created as Numeric ID


by user through RegRegMapper API. In this scenario , there will be a
validation from PSP to ensure device id of the initiator is same as
numeric id (Mobile Number)

Deregistration of UPI Number


UPI Number as Mobile Number
During de-registration , if UPI number is the mobile number, ReqRegMapper API will
initiate the Modify ‘DEREGISTER’ request through RegRegMapper API to UPI from
sender. UPI will validate the mobile number for active/inactive status and change
status of the numeric id (mobile number) to ‘DEREGISTER’

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 .

UPI Number as Numeric ID


If the UPI number is numeric ID , then Only to the same numeric id on which
registration has been done will be processed for deregistration through
‘DEREGISTER’operation using RegRegMapper API. Seemingly , the user can enable the
same numeric ID within three months of deletion period

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.

Modification of UPI Number


Transfer (PORT) UPI Number as Mobile Number between
PSP
User will be allowed to transfer the UPI Number as Mobile Number between PSP’s.
During such modification , user has to select the update mobile number as UPI Number
option from the application on which the number has to be activated.

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

Modify UPI Number as Numeric ID


During creation of numeric ID, User will be allowed to create the UPI Number as
Numeric ID more than once and can enable any UPI Number to an ‘Active’ state for
performing the transaction and it must be linked to active VPA. Hence ,For
modification , user can initiate RegRegMapper API with modify request to UPI with the
number which has to be activated. UPI will update the mapper by activating the
requested number.

RegRegMapper Implementation Usage

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)

Activate the already created


4 MODIFY ACTIVE
Numeric ID against the VPA

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

Deactivate the multiple INACTI


13 MODIFY
Numeric ID VE

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

 Note: If the UPI Number is already existing, proper consent has to be


obtained from customer for modification.

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

5 Get Address API


This API is majorly used to retrieve the VPA linked to the numeric id or mobile number.
The customer can use his own credentials for enquiry. PSP should not allow any 3rd
party to fetch the different credentials. This API is also used during onboarding to see
the availability of the selected numeric id.

GetAdd is mandatory for below scenarios


1. Creation of UPI Number (Mobile Number /Numeric ID)
2. Transfer of Mobile Number to different 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

 Supports to retrieve the status of both ‘Numeric ID’ and ‘Mobile


Number’

 The status of cmId’s of current initiated PSP profile only can be


retrieved.

 If the ‘Mobile Number’ is active or inactive in other PSP , system will


throw error and the status cannot be retrieved .

 If requested Numeric ID is in ‘Active or Inactive or Block or Deregister’


status, PSP should inform user that number is not available and in case
of status ‘New’ PSP will allow to create the number as UPI Number.
‘addr’ tag will not be populated

Type ‘PORT’ is used while transferring mobile number from one PSP to Other PSP

 Supports only ‘Mobile Number’


 User can use this to check if the mobile number is already mapped and
in Áctive’ or Ínactive’ status with other PSP
 The áddr’ tag will give complete VPA without any masking
 Mapper will reject the request when ‘PORT’ is used for creation of New
UPI Mobile Number

Type ‘FETCH’ will have subtype ‘ÍD|VPA’ for retrieve functionality

 Subtype ‘VPA’ – Retrieves all mapped cmId of the corresponding VPA


 Subtype ÍD’- User will give both VPA and cmId , the system would say if
the combination exist or not
 The status of cmId’s of current initiated PSP profile only can be
retrieved

a. For subType=”VPA”, RegIdDetails block not required


b. For subType=”ID” , Payer.addr + RegIdDetails.value is mandatory . In
order to fetch the linked VPA , user has to try the combination
available VPA against the numeric id and getAdd will provide just the
status and it will reject the invalid combination

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

Status of GetAdd API


idStatus = “NEW”

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.

 Note: Similarly blacklisting can be followed in a same existing Block &


Spam process in UPI. The PSP validation requires to be implemented
for the same. There is no change required in Centralized Mapper
 All request to centralized mapper will be validated by UPI where the
Handle & Org id has to be linked to perform the operation

v1.4
Page 15 of 78
Centralised Mapper - TSD

6 API Flows & Sample Usecases

User Creates New UPI Number Successfully


User Creating New UPI Number (Numeric Id or Mobile Number) successfully

1. User will use Type ‘Check’ in


ReqgetAdd and need to enter the
RegIdDetails with Id name as
MOBILE|NUMERICID and the value
2. The RespGetAdd will provide the
Idstatus as ‘New’
3. When the status is ‘New’ PSP can
initiate ReqRegapper with op = ‘ADD’
and setStatus = ‘Active’
4. After successful creation of the
requested number, mapper will respond
with setStatus as ‘Active’.

User could not New UPI Number as the


number is already available
1. User tries to create new UPI
number . User will use Type ‘Check’ in
ReqgetAdd and need to enter the
RegIdDetails with Id name as
MOBILE|NUMERICID and the value

2. The RespGetAdd will provide the


Idstatus either ‘Active’ or ‘Inactive’ or
‘Deregister’ or ‘Block’

PSP should initimate the user that the


requested number is already present in
the mapper and the user cannot choose
this number to create.

v1.4
Page 16 of 78
Centralised Mapper - TSD

User Updating the Status of the UPI


Number
User tries to update the status of the
created UPI Number to from 'Active' to
'Inactive'. User can change the status which
can be either 'Active' or 'Deregister' (Block &
Unblock can be initiated only by PSP)

1. User has to initiate ReqRegapper with op


'MODIFY' and setStatus ‘Inactive’
2. Mapper will update the status and update
through RespRegMapper

User tries to update the status of the


created UPI Number to from 'Active' to
‘Deregister’. The user can change the status
which can be either 'Active' or ‘Inactive’ to
‘Deregister’

1. User has to initiate ReqRegapper with op


'MODIFY' and setStatus ‘Degregister’
2. Mapper will update the status and update
through RespRegMapper

User Fetching the Status of the UPI


Number through ‘Fetch’ by ‘VPA’ or by ‘ID’
Basically , ‘Fetch’ option provides the data and see the latest mapping status of VPA
and ID within the profile .

1. Type Fetch by VPA allows the user to


get the list of ID associated to requested
VPA

User will initate the request through


ReqGetAdd with Type ‘Fetch’ , Subtype ‘
VPA’ & addr (VPA) details

2. Mapper will search and provide the list


of ID’s associated to that VPA in the
RegIdDetails of Resp block through
RespGetAdd

v1.4
Page 17 of 78
Centralised Mapper - TSD

1. Type Fetch by ID helps the user to find


ID is linked to which VPA .

User will initate the request through


ReqGetAdd with Type ‘Fetch’ , Subtype ‘
ID’. The combination of addr +
RegIdDetails.value will be given in the
request

2. Mapper will check the request and


provides the response with Result
‘Success’, idStatus ’Active’ and
lastUpdatedTs

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

User Porting the UPI Number (Only Mobile


Number )
User tries to transfer(Port) the already created UPI number which is Mobile Number
from different PSP to current PSP. User has to login to current PSP and will initate the
request through ReqGetAdd.

1. User will use the type 'PORT' and


will provide the Id name and Value
(Mobile Number) in the RegIdDetails
block
2. Mapper will respond with the addr
(Already Existing & Mapped VPA)
details in the RegIdDetails block of
RespGetAdd
3. PSP will have to take the consent
from the user to proceed with the
transfer. Then app will initiate the
transfer request through
ReqRegMapper with op = 'Modify' and
setStatus = 'Active'. Tag preVpa will
contain the vpa details of old psp
4. Mapper will perform the transfer
operation and will update the
initiator through RespRegMapper
5 & 6.Mapper will also send the
notification of Porting of UPI
Number to old PSP through
RegRegMapperConfirmation and
receive the response

v1.4
Page 18 of 78
Centralised Mapper - TSD

User tries to create Mobile Number as UPI


Number but the mobile number already active in
other PSP
User tries to create the Mobile Number as UPI Number but the number is already
created and mapped to different PSP

1. User will use Type ‘Check’ in


ReqgetAdd and need to enter the
RegIdDetails with Id name as
MOBILE and the value
2. Mapper will throw the Error
'MM18'
ID_MAPPED_TO_DIFFERENT_VPA
3. Then informing the user the app
can take the user journey of
Porting the Mobile Number.The
type 'PORT' will be initiated
through ReqGetAdd.
4. Mapper will respond with the
addr (Already Existing & Mapped
VPA) details in the RegIdDetails
block of RespGetAdd
5. Then app will initiate the
transfer request through
ReqRegMapper with op = 'Modify'
and setStatus = 'Active'. Tag preVpa
will contain the vpa details of old
psp
6. Mapper will perform the transfer
operation and will update the
initiator through RespRegMapper

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

Field Name Description


addr VPA of the Customer
cmId Central Mapper ID
cmId Type Numeric | Mobile Number
Code Merchant Code in case of P2M Transaction
Status NEW|ACTIVE|INACTIVE|DEREGISTER|BLOCK|UNBLOCK|PORTED
Channel Mobile
lastUptdTs Last Updated Time Stamp
expiryTs Expiry Time Stamp
API Name ReqRegMapper
Operation ADD|MODIFY
preVPA Previous VPA

c. The report will be provided in a CSV format as


Mapper_BBB_DDMMYY_NC.csv / pgp /zip
d. During th transfer of mobile number from one PSP to another PSP, for old
PSP, there will be an entry made with status ‘PORTED’ and for Current
PSP , there will be an additional field ‘preVPA’ through which PSP can
distinguish that the respective record has been ported in (transferred)
from different PSP .

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

<Ac addrType ="CARD">


<Detail name="ACTYPE" value="SAVINGS|CURRENT|DEFAULT"/>
<Detail name="CARDNUM" value=""/>
</Ac>
</Payer>
</upi:ReqRegMapper>

 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>

Address Validation API


Using the ValAdd API initiating PSP shall fetch the actual VPA linked to the Numeric
ID.

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

<Tag name=”LOCATION” value=”” />


<Tag name=”IP” value=””/>
<Tag name=”TYPE” value=””/>
<Tag name=”ID” value=””/>
<Tag name=”OS” value=””/>
<Tag name=”APP” value=””/>
<Tag name=”CAPABILITY” value=””/>
<Tag name=”TELECOM” value=””/>
</Device>
</Payer>
<Payee seqNum=”” addr=”XXXXXXXX@mapper.npci”/>
</upi:ReqValAdd>

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>

Get Address API


This new API shall be used for checking the availabilty of an ID before creating a new
record as well as for fetching status in case of timeout of CREATE/MODIFY/DELETE
record.

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 -->

<Payer addr="" name="" seqNum="" type="PERSON|ENTITY" code="">


<RegIdDetails>

v1.4
Page 23 of 78
Centralised Mapper - TSD

<Id name="MOBILE" value=""/>


<Id name="NUMERICID" value=""/>
</RegIdDetails>
<Consent name="CMREGISTRATION" value="Y|N" >
<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>
</Payer>
</upi: ReqGetAdd>

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

<Txn id="" note="" custRef="" refId="" refUrl="" ts="" refCategory=""


type="PAY|COLLECT|DEBIT|CREDIT|REVERSAL|REFUND" orgTxnId="" purpose=""
initiationMode="" subType="" orgRespCode="">
<RiskScores>
<Score provider="sp" type="TXNRISK" value=""/>
<Score provider="npci" type="TXNRISK" value=""/>
</RiskScores>
<Rules>
<Rule name="EXPIREAFTER" value="1 minute to max 64800
minutes"/>
<Rule name="MINAMOUNT" value=""/>
</Rules>
<QR qVer="" ts="" qrMedium="" expireTs="" query="" verToken=""
stan=""/>
</Txn>
<Payer addr="" name="" seqNum="" type="PERSON|ENTITY" code="" cmId="">
<Merchant>
<Identifier subCode="" mid="" sid="" tid=""
merchantType="SMALL|LARGE" merchantGenre="OFFLINE|ONLINE"
onBoardingType="BANK|AGGREGATOR|NETWORK|TPAP" pinCode="" regIdNo="" tier=""
merchantLoc="" merchantInstId="" />
<Ownership
type="PROPRIETARY|PARTNERSHIP|PRIVATE|PUBLIC|OTHERS"/>
<Invoice name="" num="" date="" />
</Merchant>
<Institution type="MTO|BANK" route="MTSS|RDA">
<Name value="" acNum=""/>
<Purpose code="" note=""/>
<Originator name="" type="INDIVIDUAL|COMPANY" refNo="">
<Address location="" city="" country="" geocode=""/>
</Originator>
<Beneficiary name=""/>
</Institution>
<Info>
<Identity id="" type="PAN|AADHAAR|ACCOUNT"
verifiedName="" />
<Rating VerifiedAddress="TRUE|FALSE"/>
</Info>
<Device>
<Tag name="MOBILE" value=""/>
<Tag name="GEOCODE" value=""/>
<Tag name="LOCATION" value="" />
<Tag name="IP" value=""/>
<Tag name="TYPE" value=""/>
<Tag name="ID" value=""/>
<Tag name="OS" value=""/>
<Tag name="APP" value=""/>
<Tag name="CAPABILITY" value=""/>
<Tag name="TELECOM" value=""/>
<Tag name="cardAccpTrId" value=""/>
<Tag name="cardAccIdCode" value=""/>
<Tag name="posEntryCode" value=""/>
<Tag name="posServCdnCode" value=""/>
</Device>

v1.4
Page 25 of 78
Centralised Mapper - TSD

<Ac addrType ="AADHAAR">


<Detail name="IIN" value=""/>
<Detail name="UIDNUM" value=""/>
</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>
<Ac addrType ="CARD">
<Detail name="ACTYPE" value="SAVINGS|CURRENT|DEFAULT"/>
<Detail name="CARDNUM" value=""/>
</Ac>
<Consent name="GST" type="PAN|AADHAAR|AADHAARTOKEN
PASSPORT|VOTERID|DRIVINGLICENSE" value=""/>
<Creds>
<Cred type="AADHAAR" subType="AADHAAR-BIO-FP|AADHAAR-
BIO-IRIS|AADHAAR-BIO-OTP">
<Meta lk="" ac="" sa="" uid="" ver=""/>
<Data code="" Ki=""> base-64 encoded/ encrypted authentication data </Data>
</Cred>
<Cred type="UPI-Mandate" subType="DS">
<Data> base-64 encoded digitally signed UPI-
Mandate</Data>
</Cred>
<Cred type="OTP" subType="SMS|EMAIL|HOTP|TOTP">
<Data code="" ki="">base-64 encoded/encrypted authentication data</Data>
</Cred>
<Cred type="PIN" subType="MPIN">
<Data code="" ki=""> base-64 encoded/encrypted authentication data</Data>
</Cred>
<Cred type="CARD" subType="CVV1|CVV2|EMV">
<Data code="" ki=""> base-64 encoded/encrypted authentication data</Data>
</Cred>
<Cred type="PREAPPROVED" subType="NA">
<Data> base-64 encoded</Data>
</Cred>
</Creds>
<Amount value="" curr="INR">
<Split name="" value=""/>
</Amount>
</Payer>
<Payees>
<Payee addr="" name="" seqNum="" type="PERSON|ENTITY" code=""
cmId="">
<Institution QrPayLoad="" conCode="" netInstId=""/>
<Merchant>
<Identifier subCode="" mid="" sid="" tid=""
merchantType="SMALL|LARGE" merchantGenre="OFFLINE|ONLINE"

v1.4
Page 26 of 78
Centralised Mapper - TSD

onBoardingType="BANK|AGGREGATOR|NETWORK|TPAP" pinCode="" regIdNo=""


tier=""/>
<Ownership type="PROPRIETARY|PARTNERSHIP|PRIVATE|PUBLIC|OTHERS"/>
<Invoice name="" num="" date="" />
</Merchant>
<Info>
<Identity id="" type="PAN|AADHAAR|ACCOUNT"
verifiedName=""/>
<Rating VerifiedAddress="TRUE|FALSE"/>
</Info>
<Device>
<Tag name="MOBILE" value=""/>
<Tag name="GEOCODE" value=""/>
<Tag name="LOCATION" value="" />
<Tag name="IP" value=""/>
<Tag name="TYPE" value=""/>
<Tag name="ID" value=""/>
<Tag name="OS" value=""/>
<Tag name="APP" value=""/>
<Tag name="CAPABILITY" value=""/>
<Tag name="TELECOM" value=""/>
</Device>
<Ac addrType ="AADHAAR">
<Detail name="IIN" value=""/>
<Detail name="UIDNUM" value=""/>
</Ac>
<Ac addrType="ACCOUNT">
<Detail name="IFSC" value=""/>
<Detail name="ACTYPE" value=""/>
<Detail name="ACNUM" value=""/>
</Ac>
<Consent name="GST" type="PAN|AADHAAR|AADHAARTOKEN
PASSPORT|VOTERID|DRIVINGLICENSE" value=""/>
<Amount value="" curr="INR">
<Split name="" value=""/>
</Amount>
</Payee>
</Payees>
</upi:ReqPay>

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

<Resp reqMsgId="" result="SUCCESS|FAILURE|PARTIAL|DEEMED" errCode=""


actn="">
<Ref type="PAYER" seqNum="" addr="" regName="" acNum="" IFSC=""
code="" accType="" settAmount="" orgAmount="" settCurrency="" approvalNum=""
respCode="" reversalRespCode="" balAmt="" cmId=""/>
<Ref type="PAYEE" seqNum="" addr="" regName="" acNum="" IFSC=""
code="" accType="" settAmount="" orgAmount="" settCurrency="" approvalNum=""
respCode="" reversalRespCode="" cmId="" />
<Consent name="GST" type="" value=""/>
</Resp>
</upi:RespPay>

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>

 Note : orgStatus should be success in case of Transfer of mobile


number between PSP

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

1.1 API Name <ReqReg 1..1 Y


Mapper>
1.1.1 API xmlns 1..1 Alphanu Min Y
Schema meric Length : 1
namespac Max
e Length :
255
2.1 Header <Head> 1..1 Alphabe Fixed Y
tic value
2.1.1 Version of ver 1..1 Numeri Min Y
the API c Length : 1
Max
Length : 6
2.1.2 Time of ts 1..1 ISODate Min Y
request Time Length : 1
from the Max
creator of Length :
the 255
message
2.1.3 Organizati orgId 1..1 Numeri Min Y
on id that c Length : 1
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

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

RespRegMapper Field Specifications


Tag Message <XMLTag Occurr Datat Length Mand Enum Values
Num Item > ence ype atory
1.1 API Name <RespRe 1..1 Y
gMapper
>
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
2.1.4 Message msgId 1..1 Alpha Min Y
identifier- numer Length : 1
used to ic Max
correlate Length : 35
between
request
and
response
2.1.5 Product prodTyp 1..1 Alpha Min Y UPI
Type e numer Length : 1
ic Max
Length : 15
3.1 Transactio <Txn> 1..1 Alpha Fixed value Y
n betic
informatio
n, Carried
throughou
t the
system,
visible to
all parties

v1.4
Page 34 of 78
Centralised Mapper - TSD

3.1.1 Unique id 1..1 Alpha Length : 35 Y


Identifier numer
of the ic
transactio
n across all
entities,
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 “CMREGISTRA
the Length : 1 TION”
Transactio Max
n Length : 20
3.1.7 Operation Op 1..1 Code Fixed Y ADD|MODIFY
to be Length
performed
by the
request
4.1 Response <Resp> 1..1 Alpha Fixed value Y
betic

v1.4
Page 35 of 78
Centralised Mapper - TSD

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 SUCCESS|FAIL


the Length : 1 URE
transactio Max
n Length : 20
4.1.3 Error code errCode 1..1 Alpha Min Y Refer
if failed numer Length : 1 section
ic Max 8.21
Length : 20

5.1 Details of <RedIdD 1..1 Code Fixed value Y


the etails>
Registratio
n ID
5.1.1 Address of addr 1..1 Alpha Min Y
the Payer numer Length : 1
ic Max
Length :
255
5.1.2 Name <name> 1..n Alpha Fixed value Y MOBILE|NUM
betic ERICID
5.1.3 Value value 1..n Alpha Min N
numer Length : 1
ic Max
Length :
100
5.1.4 Status of setStatus 1..1 Alpha Min N NEW|ACTIVE|
the ID betic Length : 1 INACTIVE|BLO
Max CK|UNBLOCK|
Length : 35 DEREGISTER
5.1.5 Expiry expiryTs 1..1 ISODa Min N The string
Time teTim Length : 1 format should
Stamp. e Max be:
Will be Length : YYYY-MM-
shared 255 DDTHH:mm:ss
during .sssZ
deregistrat ,
ion where:
YYYY-MM-DD
– is the date:
year- month-
day.

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

ValAdd New Tag Specification


Tag Message <XMLTag Occurren Datatyp Length Mand Enum
Num Item > ce e atory Values

v1.4
Page 37 of 78
Centralised Mapper - TSD

1 UPI cmId 1..1 Numeri Min N


Number of c Length : 6
the VPA Max
Length :
16
2 Address of addr 1..1 Alphanu Min Y
the Payer meric Length : 1
Max
Length :
255
3 Initiating Channel 1..1 Alphabe Fixed Y MOB|USDC
Channel tic value |IVR

ReqPay New Tag Specification


Tag Message <XMLTag Occurren Datatyp Length Mand Enum
Num Item > ce e atory Values
1 Central cmId 1..1 Alphanu Min N
mapper Id/ meric Length : 6
numeric Max
Id/cmId Length :
25

ReqGetAdd Field Specifications


Tag Message <XMLTag Occurren Datatyp Length Mand Enum
Num Item > ce e atory Values
1.1 API Name <ReqGet 1..1 Y
Add>
1.1.1 API xmlns 1..1 Alphanu Min Y
Schema meric Length : 1
namespac Max
e Length :
255
2.1 Header <Head> 1..1 Alphabe Fixed Y
tic value
2.1.1 Version of ver 1..1 Numeri Min Y
the API c Length : 1
Max
Length : 6
2.1.2 Time of ts 1..1 ISODate Min Y
request Time Length : 1
from the Max
creator of Length :
the 255
message
2.1.3 Organizati orgId 1..1 Numeri Min Y
on id that c Length : 1

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

RespGetAdd Field Specifications


Tag Message <XMLTag Occurr Datat Length Mand Enum Values
Num Item > ence ype atory

v1.4
Page 42 of 78
Centralised Mapper - TSD

1.1 API Name <RespGe 1..1 Y


tAdd>
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
2.1.4 Message msgId 1..1 Alpha Min Y
identifier- numer Length : 1
used to ic Max
correlate Length : 35
between
request
and
response
2.1.5 Product prodTyp 1..1 Alpha Min Y UPI
Type e numer Length : 1
ic Max
Length : 15
3.1 Transactio <Txn> 1..1 Alpha Fixed value Y
n betic
informati0
n, Carried
throughou
t the
system,
visible to
all parties
3.1.1 Unique id 1..1 Alpha Length : 35 Y
Identifier numer
of the ic
transactio
n across all
entities,

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

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 “SUCCESS|FAI


the Length : 1 LURE”
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

v1.4
Page 44 of 78
Centralised Mapper - TSD

5.1 Details of <RegIdD 1..1 Code Fixed value Y


the etails>
Registratio
n ID
5.1.1 Address of addr 1..1 Alpha Min Y
the Payer numer Length : 1
ic Max
Length :
255
5.1.2 Type of type 1..1 Code Fixed value Y “PERSON|ENT
the Payer ITY”
5.1.3 Status of idStatus 1..1 Code Fixed value Y “NEW|ÄCTIVE
the Id |INACTIVE|BL
OCK|UNBLOC
K|DEREGISTER

5.1.4 Last lastUpda 1..1 ISODa Min Y The string
Modified tedTs teTim Length : 1 format should
date of the e Max be:
account Length : YYYY-MM-
provider 255 DDTHH:mm:ss
informatio .sssZ
n in the ,
UPI system where:
YYYY-MM-DD
– is the date:
year- month-
day.
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

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

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
2.1.4 Message msgId 1..1 Alpha Min Y
identifier- numer Length : 1
used to ic Max
correlate Length : 35
between
request
and
response
3.1 Transactio <Txn> 1..1 Alpha Fixed value Y
n informati betic
on, Carried
throughou
t the
system,
visible to
all parties
3.1.1 Unique id 1..1 Alpha Length : 35 Y
Identifier numer
of the ic
transactio
n across all
entities,
created by
the
originator
3.1.2 Transactio ts 1..1 ISODa Min Y
n teTim Length : 1
origination e Max
time by

v1.4
Page 47 of 78
Centralised Mapper - TSD

the creator Length :


of the 255
message
3.1.3 Type of type 1..1 Code Fixed Y “CMREGISTRA
the Length TION”
Transactio
n
3.1.4 Consumer refId 1..1 Alpha Min Y
reference numer Length : 1
number to ic Max
identify Length : 35
(like Loan
number,
etc.)
3.1.5 URL for refUrl 1..1 Alpha Min Y
the numer Length : 1
transactio ic Max
n Length : 35
3.1.6 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.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 Transactio <TxnConf 1..1 Alpha Fixed value Y
n irmation> betic
Confirmati
on
4.1.1 Descriptio note 1..1 Alpha Min Y
n of the nu Length : 1
transactio meric Max
n( which Length : 50
will be
printed on
Passbook)

v1.4
Page 48 of 78
Centralised Mapper - TSD

4.1.2 Type of type 1..1 Code Min Y 012_ReqTxn_


the Length : 1 Pay
Transactio Max 013_ReqTxn_
n Length : 20 Collect
4.1.3 Operation Op 1..1 Code Fixed Y ADD|MODIFY
to be Length
performed
by the
request
4.1.4 Type of idType 1..n Alpha Fixed value Y MOBILE|NUM
Identificati betic ERIC ID
on

4.1.5 Orignal orgStatu 1..1 Code Min Y


transactio s Length : 1
n status Max
Length : 20
4.1.6 Ref type type 1..1 Code Y

4.1.7 Address of addr 1..1 Alpha Min Y


the Payer numer Length : 1
ic Max
Length :
255
4.1.8 Name of name 1..1 Alpha Min Y
the Payer numer Length : 1
ic Max
Length : 99
4.1.9 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
5.1 Response <Ref> 1..n Alpha Fixed value Y
Reference betic

5.1.1 Merchant code 1..1 Nume Length : 4 N


Classificati ric
on Code -
MCC

v1.4
Page 49 of 78
Centralised Mapper - TSD

5.1.2 UPI cmId 1..1 Nume Min N


Number of ric Length : 6
the VPA Max
Length : 16
5.1.3 Status of status 1..1 Code Fixed value Y “ÄCTIVE|INAC
the cmId TIVE|NEW|DE
REGISTER|BLO
CK|UNBLOCK

5.1.4 Initiating Channel 1..1 Alpha Fixed value Y MOB|USDC|I
Channel betic VR

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

2.1.4 Message msgId 1..1 Alpha Min Y


identifier- numer Length : 1
used to ic Max
correlate Length : 35
between
request
and
response
3.1 Transactio <Txn> 1..1 Alpha Fixed value Y
n informati betic
on, Carried
throughou
t the
system,
visible to
all parties
3.1.1 Unique id 1..1 Alpha Length : 35 Y
Identifier numer
of the ic
transactio
n across all
entities,
created by
the
originator
3.1.2 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.3 Type of type 1..1 Code Fixed Y “CMREGISTRA
the Length TION”
Transactio
n
3.1.4 Consumer refId 1..1 Alpha Min Y
reference numer Length : 1
number to ic Max
identify Length : 35
(like Loan
number,
etc.)
3.1.5 URL for refUrl 1..1 Alpha Min Y
the numer Length : 1
transactio ic Max
n Length : 35
3.1.6 Descriptio note 1..1 Alpha Min Y
n of the numer Length : 1
transactio ic Max
n (which Length : 50

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

Check the availability and add Mobile


Number as UPI Number
Request to Check the availability of Mobile Number

<?xml version="1.0" encoding="UTF-8"?>


<ns2:ReqGetAdd
xmlns:ns2="http://npci.org/upi/schema/">
<Head msgId="XYD1442cdd8a121449cae3ab0034f72b165" orgId="159011"
prodType="UPI" ts="2021-08-25T16:25:12+05:30" ver="2.0"/>
<Txn custRef="105015641974" id="MMM0000000000005t0xf6TRJPgH6X6JSsE"
note="Mapper" refId="702314088080" refUrl="http://upi"
ts="2017-01-23T14:14:54.040+05:30" type="CHECK"/>

v1.4
Page 52 of 78
Centralised Mapper - TSD

<Payer addr="testuser123456@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="MOBILE" value="9848159011"/>
</RegIdDetails>
</Payer>
</ns2:ReqGetAdd>

Response from UPI with Available Status ‘New’


<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ns2:RespGetAdd
xmlns:ns2="http://npci.org/upi/schema/"
xmlns:ns3="http://npci.org/cm/schema/">
<Head ver="2.0" ts="2021-08-25T16:25:12+05:30" orgId="NPCI"
msgId="5t0xf6ZKer9V58kJfUZ"/>
<Txn id="MMM0000000000005t0xf6TRJPgH6X6JSsE" note="Mapper"
refId="702314088080" refUrl="http://upi" ts="2017-01-23T14:14:54.040+05:30"
type="CHECK" custRef="105015641974"/>
<Resp reqMsgId="XYD1442cdd8a121449cae3ab0034f72b165" result="SUCCESS">
<RegIdDetails addr="testuser123456@andb" type="PERSON" idStatus="NEW">
<Id name="MOBILE" value="9848159011"/>
</RegIdDetails>
</Resp>
</ns2:RespGetAdd>

Request to create and add the Mobile Number


<?xml version="1.0" encoding="UTF-8"?>
<ns2:ReqRegMapper
xmlns:ns2="http://npci.org/upi/schema/">
<Head msgId="XYD1442cdd8a121449cae3ab0034f72b165" orgId="159011"
prodType="UPI" ts="2021-08-25T16:27:04+05:30" ver="2.0"/>
<Txn custRef="105015571146" id="MMM0000000000005t0xf6TRJPgH79rlYoU"
note="Mapper" op="ADD" refId="702314088080" refUrl="http://upi"
ts="2017-01-23T14:14:54.040+05:30" type="CMREGISTRATION"/>
<Payer addr="testuser123456@andb" code="0000" name="TEST USER"
seqNum="1" type="PERSON">
<Device>
<Tag name="MOBILE" value="919848159011"/>

v1.4
Page 53 of 78
Centralised Mapper - TSD

<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>
<Ac addrType="ACCOUNT">
<Detail name="ACTYPE" value="SAVINGS"/>
<Detail name="ACNUM" value="029010100347310"/>
<Detail name="IFSC" value="ANDB0000029"/>
</Ac>
<Consent name="CMREGISTRATION" value="Y"/>
<RegIdDetails>
<Id name="MOBILE" setStatus="ACTIVE" value="9848159011"/>
</RegIdDetails>
</Payer>
</ns2:ReqRegMapper>

Response from UPI for successful addition


<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ns2:RespRegMapper
xmlns:ns2="http://npci.org/upi/schema/"
xmlns:ns3="http://npci.org/cm/schema/">
<Head ver="2.0" ts="2021-08-25T16:27:05+05:30" orgId="NPCI"
msgId="5t0xf6ZKer9V5kFcxyp"/>
<Txn id="MMM0000000000005t0xf6TRJPgH79rlYoU" note="Mapper"
refId="702314088080" refUrl="http://upi" ts="2017-01-23T14:14:54.040+05:30"
type="CMREGISTRATION" custRef="105015571146" op="ADD"/>
<Resp reqMsgId="XYD1442cdd8a121449cae3ab0034f72b165" result="SUCCESS">
<RegIdDetails addr="testuser123456@andb">
<Id name="MOBILE" value="9848159011" setStatus="ACTIVE"/>
</RegIdDetails>
</Resp>
</ns2:RespRegMapper>

Check the availability and add


Numeric ID as UPI Number
Request to Check the availability of Numeric ID
<?xml version="1.0" encoding="UTF-8"?>
<ns2:ReqGetAdd
xmlns:ns2="http://npci.org/upi/schema/">
<Head msgId="XYD1442cdd8a121449cae3ab0034f72b165" orgId="159011"
prodType="UPI" ts="2021-08-25T16:13:33+05:30" ver="2.0"/>
<Txn custRef="105015641974" id="MMM0000000000005t0xf6TRJPgH5IUsINi"
note="Mapper" refId="702314088080" refUrl="http://upi"

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>

Response from UPI with Available Status ‘New’


<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ns2:RespGetAdd
xmlns:ns2="http://npci.org/upi/schema/"
xmlns:ns3="http://npci.org/cm/schema/">
<Head ver="2.0" ts="2021-08-25T16:13:34+05:30" orgId="NPCI"
msgId="5t0xf6ZKer9V3U92buJ"/>
<Txn id="MMM0000000000005t0xf6TRJPgH5IUsINi" note="Mapper"
refId="702314088080" refUrl="http://upi" ts="2017-01-23T14:14:54.040+05:30"
type="CHECK" custRef="105015641974"/>
<Resp reqMsgId="XYD1442cdd8a121449cae3ab0034f72b165" result="SUCCESS">
<RegIdDetails type="PERSON" idStatus="NEW">
<Id name="NUMERICID" value="25082061"/>
</RegIdDetails>
</Resp>
</ns2:RespGetAdd>

Request to create and add available Numeric ID


<ns2:ReqRegMapper
xmlns:ns2="http://npci.org/upi/schema/">
<Head msgId="XYD1442cdd8a121449cae3ab0034f72b165" orgId="159011"
prodType="UPI" ts="2021-08-25T16:19:38+05:30" ver="2.0"/>
<Txn custRef="105015571146" id="MMM0000000000005t0xf6TRJPgH6mGegHC"
note="Mapper" op="ADD" refId="702314088080" refUrl="http://upi"
ts="2017-01-23T14:14:54.040+05:30" type="CMREGISTRATION"/>
<Payer addr="testuser12345@andb" code="0000" name="TEST USER"
seqNum="1" type="PERSON">
<Device>
<Tag name="MOBILE" value="919848159011"/>

v1.4
Page 55 of 78
Centralised Mapper - TSD

<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>
<Ac addrType="ACCOUNT">
<Detail name="ACTYPE" value="SAVINGS"/>
<Detail name="ACNUM" value="029010100347310"/>
<Detail name="IFSC" value="ANDB0000029"/>
</Ac>
<Consent name="CMREGISTRATION" value="Y"/>
<RegIdDetails>
<Id name="NUMERICID" setStatus="ACTIVE" value="25082061"/>
</RegIdDetails>
</Payer>
</ns2:ReqRegMapper>

Response from UPI for successful addition


<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ns2:RespRegMapper
xmlns:ns2="http://npci.org/upi/schema/"
xmlns:ns3="http://npci.org/cm/schema/">
<Head ver="2.0" ts="2021-08-25T16:19:38+05:30" orgId="NPCI"
msgId="5t0xf6ZKer9V4xUwwOj"/>
<Txn id="MMM0000000000005t0xf6TRJPgH6mGegHC" note="Mapper"
refId="702314088080" refUrl="http://upi" ts="2017-01-23T14:14:54.040+05:30"
type="CMREGISTRATION" custRef="105015571146" op="ADD"/>
<Resp reqMsgId="XYD1442cdd8a121449cae3ab0034f72b165" result="SUCCESS">
<RegIdDetails addr="testuser12345@andb">
<Id name="NUMERICID" value="25082061" setStatus="ACTIVE"/>
</RegIdDetails>
</Resp>
</ns2:RespRegMapper>

Deregister UPI Number (Mobile


Number)
Request to Deregister Mobile Number

<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>

Response from UPI for Successful Deregistration

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>


<ns2:RespRegMapper
xmlns:ns2="http://npci.org/upi/schema/"
xmlns:ns3="http://npci.org/cm/schema/">
<Head ver="2.0" ts="2021-08-03T13:53:04+05:30" orgId="NPCI"
msgId="5t0xf6ZKer92QB8dVn8"/>
<Txn id="MMM0000000000005t0xf6TRJPfOSpUgE00" note="Mapper"
refId="702314088080" refUrl="http://upi" ts="2017-01-23T14:14:54.040+05:30"
type="CMREGISTRATION" custRef="105015571146" op="MODIFY"/>
<Resp reqMsgId="XYD1442cdd8a121449cae3ab0034f72b165" result="SUCCESS">
<RegIdDetails addr="addmobile@csb">
<Id name="MOBILE" value="9848055445" setStatus="DEREGISTER"/>
</RegIdDetails>
</Resp>
</ns2:RespRegMapper>

Deregister UPI Number (Numeric ID)


Request to Degregister Numeric ID

<?xml version="1.0" encoding="UTF-8"?>

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>

Response from UPI for successful Deregisteration


<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ns2:RespRegMapper
xmlns:ns2="http://npci.org/upi/schema/"
xmlns:ns3="http://npci.org/cm/schema/">
<Head ver="2.0" ts="2021-08-03T13:45:41+05:30" orgId="NPCI"
msgId="5t0xf6ZKer92POP7JZO"/>
<Txn id="MMM0000000000005t0xf6TRJPfORDCsboA" note="Mapper"
refId="702314088080" refUrl="http://upi" ts="2017-01-23T14:14:54.040+05:30"
type="CMREGISTRATION" custRef="105015571146" op="MODIFY"/>
<Resp reqMsgId="XYD1442cdd8a121449cae3ab0034f72b165" result="SUCCESS">
<RegIdDetails addr="addnumeric01@csb">
<Id name="NUMERICID" value="55445532" setStatus="DEREGISTER"expiryTs =
“2017-06-23T14:14:54.040+05:30/>
</RegIdDetails>
</Resp>
</ns2:RespRegMapper>

v1.4
Page 58 of 78
Centralised Mapper - TSD

Financial Transaction through UPI


Number (cmId)
ReqValAdd is getting initiated for UPI Number
(cmId) transaction by Payer PSP

<?xml version="1.0" encoding="UTF-8"?>


<ns2:ReqValAdd
xmlns:ns2="http://npci.org/upi/schema/">
<Head msgId="ANBec5550ce94501b10c88adc980d967aaa" orgId="159011"
ts="2021-08-26T17:22:40+05:30" ver="2.0"/>
<Txn id="MMM0000000000005t0xf6TRJPgJF8vO6Jy" note="validating Address"
refId="bbce92b4a01d4618a0eca5fdecc37ff2row" refUrl="http://npci.com"
ts="2016-02-23T14:16:50+05:30" type="ValAdd"/>
<Payer addr="sri@andb" code="0000" name="UPI" seqNum="1" type="PERSON">
<Info>
<Identity id="1" type="ACCOUNT" verifiedName="Riyaz MOHD"/>
<Rating verifiedAddress="TRUE"/>
</Info>
<Device>
<Tag name="MOBILE" value="919952631017"/>
<Tag name="LOCATION" value="New Delhi"/>
<Tag name="IP" value="127.0.0.4"/>
<Tag name="TYPE" value="MOB"/>
<Tag name="ID" value="12345678901234567890123456789012345"/>
</Device>
</Payer>
<Payee addr="9769948645@mapper.npci" name="Fayaz Mohammad" seqNum="1"/>
</ns2:ReqValAdd>

UPI Initiating ReqvalAdd to Payee PSP


<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ns2:ReqValAdd
xmlns:ns2="http://npci.org/upi/schema/"
xmlns:ns3="http://npci.org/cm/schema/">
<Head ver="2.0" ts="2021-08-26T17:22:41+05:30" orgId="NPCI"
msgId="5t0xf6ZKer9XDjK04Fj"/>
<Txn id="MMM0000000000005t0xf6TRJPgJF8vO6Jy" note="validating Address"
refId="bbce92b4a01d4618a0eca5fdecc37ff2row" refUrl="http://npci.com" ts="2016-
02-23T14:16:50+05:30" type="ValAdd"/>
<Payer addr="sri@andb" name="UPI" seqNum="1" type="PERSON" code="0000">
<Info>
<Identity type="ACCOUNT" verifiedName="Riyaz MOHD" id="1"/>
<Rating verifiedAddress="TRUE"></Rating>
</Info>
<Device>
<Tag name="MOBILE" value="919952631017"/>
<Tag name="LOCATION" value="New Delhi"/>

v1.4
Page 59 of 78
Centralised Mapper - TSD

<Tag name="IP" value="127.0.0.4"/>


<Tag name="TYPE" value="MOB"/>
<Tag name="ID" value="12345678901234567890123456789012345"/>
</Device>
</Payer>
<Payee addr="fayaz@andb" name="Fayaz Mohammad" seqNum="1"
cmId="9769948645"/>
</ns2:ReqValAdd>

Payee PSP respond RespValAdd to UPI


<?xml version="1.0" encoding="UTF-8"?>
<ns2:RespValAdd
xmlns:ns2="http://npci.org/upi/schema/">
<Head msgId="ANB0000000000005t0xf7oRsP9EUwfA4OH" orgId="159011"
ts="2021-08-26T17:22:41+05:30" ver="2.0"/>
<Resp IFSC="ANDK0036046" IIN="600007" accType="SAVINGS" code="0000"
maskName="Fayaz Mohammad"
reqMsgId="5t0xf6ZKer9XDjK04Fj" result="SUCCESS" type="PERSON"/>
<Txn id="MMM0000000000005t0xf6TRJPgJF8vO6Jy" note="validating Address"
refId="bbce92b4a01d4618a0eca5fdecc37ff2row" refUrl="http://npci.com"
ts="2016-02-23T14:16:50+05:30" type="ValAdd"/>
</ns2:RespValAdd>

UPI respond RespValAdd back to Payer PSP


<ns2:RespValAdd
xmlns:ns2="http://npci.org/upi/schema/"
xmlns:ns3="http://npci.org/cm/schema/">
<Head ver="2.0" ts="2021-08-26T17:22:41+05:30" orgId="NPCI"
msgId="5t0xf6ZKer9XDjL0APU"/>
<Resp reqMsgId="ANBec5550ce94501b10c88adc980d967aaa" result="SUCCESS"
maskName="Fayaz Mohammad" code="0000" type="PERSON" IFSC="ANDK0036046"
IIN="600007" accType="SAVINGS" cmId="9769948645" addr="fayaz@andb"/>
<Txn id="MMM0000000000005t0xf6TRJPgJF8vO6Jy" note="validating Address"
refId="bbce92b4a01d4618a0eca5fdecc37ff2row" refUrl="http://npci.com" ts="2016-
02-23T14:16:50+05:30" type="ValAdd"/>
</ns2:RespValAdd>

Initial Reqpay Request from Payer PSP


<ns2:ReqPay
xmlns:ns2="http://npci.org/upi/schema/">
<Head msgId="5z68jRTbjsje5CSRZtK" orgId="159011"
ts="2021-08-20T09:19:25+05:30" ver="2.0"/>
<Meta>
<Tag name="PAYREQSTART" value="2015-03-16T14:16:35+05:25"/>
<Tag name="PAYREQEND" value="2015-03-16T14:15:42+05:35"/>
</Meta>

v1.4
Page 60 of 78
Centralised Mapper - TSD

<Txn custRef="123209246064" id="MMM0000000000005t0xf6TRJPgu7pSJ1IY"


initiationMode="00" note="Sta" purpose="00" refId="Ref"
refUrl="https://www.sbi.co.in/" ts="2018-11-28T19:00:11+05:30" type="PAY">
<RiskScores>
<Score provider="psp1" type="TXNRISK" value="00090"/>
<Score provider="psp3" type="TXNR2" value="00090"/>
</RiskScores>
<Rules>
<Rule name="EXPIREAFTER" value="1"/>
<Rule name="MINAMOUNT" value="370.00"/>
</Rules>
</Txn>
<Payer addr="aswin@andb" name="" seqNum="1" type="PERSON">
<Info>
<Identity id="" type="PAN" verifiedName=""/>
<Rating verifiedAddress="TRUE"/>
</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="5200000200000005600179703232920"/>
</Device>
<Ac addrType="ACCOUNT">
<Detail name="IFSC" value="ANDB0000001"/>
<Detail name="ACTYPE" value="SAVINGS"/>
<Detail name="ACNUM" value="" />
</Ac>
<Creds>
<Cred subType="MPIN" type="PIN">
<Data code="NPCI"
ki="20150822">2.0|B74g32Kw9AJTBY4M6zQBAKTPQ6saJqYWYJ4eu0D9GqtyW3geHu/N
W+D3enZVEIQT91pNkWagsIKU&#xd;
XaQlu3dWMvHrQNbdrfMNjrPTCBNSlTMyKWoOjLveiysupFaPng4NGwfbr/4CWFgXtB9dig
V/fw/b&#xd;
ZOrUzNi0veyVDzKiglvAS6IoHv87JQjOinxo8zE/mPl+dt24s2nSziYpEH3J8CrNQKcfWE+yQ
LkM&#xd;
66gqnETiXF/DUytQGsYLlWVXHC+kD89+CprSUwXhtXJxyWJHH8HYnvT1pPHucQRBNGmo
5e1I/5cF&#xd;
I778VvLL5lG8MMo1HVW+tZ1z9z7ryNyhLLMe7Q==&#xd;
</Data>
</Cred>
</Creds>
<Amount curr="INR" value="49.00"/>
</Payer>
<Payees>
<Payee addr="fayaz@andb" cmId="9769948645" code="0000"
name="" seqNum="1" type="PERSON">
<Amount curr="INR" value="49.00"/>

v1.4
Page 61 of 78
Centralised Mapper - TSD

</Payee>
</Payees>
</ns2:ReqPay>

ReqAuthDetails initiated by UPI

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>


<ns2:ReqAuthDetails
xmlns:ns2="http://npci.org/upi/schema/"
xmlns:ns3="http://npci.org/cm/schema/">
<Head ver="2.0" ts="2021-08-20T09:19:26+05:30" orgId="NPCI"
msgId="5t0xf6ZKer9I5B7Ax2v"/>
<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"/>
</RiskScores>
<Rules>
<Rule name="EXPIREAFTER" value="1"/>
<Rule name="MINAMOUNT" value="370.00"/>
</Rules>
</Txn>
<Payees>
<Payee addr="fayaz@andb" name="" seqNum="1" type="PERSON" code="0000"
cmId="9769948645">
<Amount value="49.00" curr="INR"/>
</Payee>
</Payees>
<Payer addr="aswin@andb" name="" seqNum="1" type="PERSON" code="0000">
<Info>
<Identity type="PAN" verifiedName="" id=""/>
<Rating verifiedAddress="TRUE"></Rating>
</Info>
<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>
</ns2:ReqAuthDetails>

RespAuthDetails from Payee PSP

<?xml version="1.0" encoding="UTF-8"?>


<ns2:RespAuthDetails
xmlns:ns2="http://npci.org/upi/schema/">

v1.4
Page 62 of 78
Centralised Mapper - TSD

<Head msgId="ANB0000000000005t0xf7oRsP9pmNF0Fdd" orgId="159011"


ts="2021-08-20T09:19:26+05:30" ver="2.0"/>
<Resp reqMsgId="5t0xf6ZKer9I5B7Ax2v" result="SUCCESS"/>
<Txn custRef="123209246064" id="MMM0000000000005t0xf6TRJPgu7pSJ1IY"
initiationMode="00" note="Sta" purpose="00" refId="Ref"
refUrl="https://www.sbi.co.in/" ts="2018-11-28T19:00:11+05:30" type="PAY">
<RiskScores>
<Score provider="psp1" type="TXNRISK" value="00090"/>
<Score provider="psp3" type="TXNR2" value="00090"/>
</RiskScores>
<Rules>
<Rule name="EXPIREAFTER" value="1"/>
<Rule name="MINAMOUNT" value="370.00"/>
</Rules>
</Txn>
<Payer addr="aswin@andb" code="0000" name="" seqNum="1" type="PERSON">
<Info>
<Identity id="" type="PAN" verifiedName=""/>
<Rating verifiedAddress="TRUE"/>
</Info>
<Ac addrType="ACCOUNT">
<Detail name="IFSC" value="ANDB0000001"/>
<Detail name="ACTYPE" value="SAVINGS"/>
<Detail name="ACNUM" value="" />
</Ac>
<Amount curr="INR" value="49.00"/>
</Payer>
<Payees>
<Payee addr="fayaz@andb" cmId="9769948645" code="0000"
name="" seqNum="1" type="PERSON">
<Info>
<Identity id="" type="ACCOUNT" verifiedName=""/>
<Rating verifiedAddress="TRUE"/>
</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 curr="INR" value="49.00"/>
</Payee>
</Payees>
</ns2:RespAuthDetails>

v1.4
Page 63 of 78
Centralised Mapper - TSD

ReqPay Debit Request Initiated by UPI

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>


<ns2:ReqPay
xmlns:ns2="http://npci.org/upi/schema/"
xmlns:ns3="http://npci.org/cm/schema/">
<Head ver="2.0" ts="2021-08-20T09:19:29+05:30" orgId="NPCI"
msgId="5t0xf6ZKer9I5Bve9Vw"/>
<Meta>
<Tag name="PAYREQSTART" value="2015-03-16T14:16:35+05:25"/>
<Tag name="PAYREQEND" value="2015-03-16T14:15:42+05:35"/>
</Meta>
<Txn id="MMM0000000000005t0xf6TRJPgu7pSJ1IY" note="Sta" refId="Ref"
refUrl="https://www.sbi.co.in/" ts="2018-11-28T19:00:11+05:30" type="DEBIT"
custRef="123209246064" initiationMode="00" subType="PAY" 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>
<Rules>
<Rule name="EXPIREAFTER" value="1"/>
<Rule name="MINAMOUNT" value="370.00"/>
</Rules>
</Txn>
<Payer addr="aswin@andb" name="" seqNum="1" type="PERSON" code="0000">
<Info>
<Identity type="PAN" 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="5200000200000005600179703232920"/>
</Device>
<Ac addrType="ACCOUNT">
<Detail name="IFSC" value="ANDB0000001"/>
<Detail name="ACTYPE" value="SAVINGS"/>
<Detail name="ACNUM" value="" />
</Ac>
<Creds>
<Cred type="PIN" subType="MPIN">
<Data code="159011"
ki="20210616">NuYPynWC9fmwScwhZ+iRWyhHW8lAvUZ+1Qfkifzt9tAM/GKSjEaazusPK
xKJldtIe/k5fbj6ch7YJWwechkVfn877i7tUu6PoIOjlo55xYi9WL+W+YkVM4g2fXlNMSJSk0

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>

Resppay for Debit Request from Bank

<?xml version="1.0" encoding="UTF-8"?>


<ns2:RespPay
xmlns:ns2="http://npci.org/upi/schema/">
<Head msgId="ANB0000000000005t0xf7oRsP9pmO0P0ak" orgId="159011"
ts="2021-08-20T09:19:30+05:30" ver="2.0"/>
<Txn custRef="123209246064" id="MMM0000000000005t0xf6TRJPgu7pSJ1IY"
initiationMode="00" note="Sta" purpose="00" refId="Ref"
refUrl="https://www.sbi.co.in/" subType="PAY"
ts="2018-11-28T19:00:11+05:30" type="DEBIT">
<RiskScores>
<Score provider="psp1" type="TXNRISK" value="00090"/>
<Score provider="psp3" type="TXNR2" value="00090"/>
<Score provider="NPCI" type="TXNRISK" value="00999"/>
</RiskScores>

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>

ReqPay Credit Request initiated by UPI


<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<ns2:ReqPay
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="5t0xf6ZKer9I5Bwjig3"/>
<Meta>
<Tag name="PAYREQSTART" value="2015-03-16T14:16:35+05:25"/>
<Tag name="PAYREQEND" value="2015-03-16T14:15:42+05:35"/>
</Meta>
<Txn id="MMM0000000000005t0xf6TRJPgu7pSJ1IY" note="Sta" refId="Ref"
refUrl="https://www.sbi.co.in/" ts="2018-11-28T19:00:11+05:30" type="CREDIT"
custRef="123209246064" initiationMode="00" subType="PAY" 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>
<Rules>
<Rule name="EXPIREAFTER" value="1"/>
<Rule name="MINAMOUNT" value="370.00"/>
</Rules>
</Txn>
<Payer addr="aswin@andb" name="" seqNum="1" type="PERSON" code="0000">
<Info>
<Identity type="PAN" 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="5200000200000005600179703232920"/>

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>

Resppay Credit Request from Bank

<?xml version="1.0" encoding="UTF-8"?>


<ns2:RespPay
xmlns:ns2="http://npci.org/upi/schema/">
<Head msgId="ANB0000000000005t0xf7oRsP9pmO2qrCq" orgId="159011"
ts="2021-08-20T09:19:30+05:30" ver="2.0"/>
<Txn custRef="123209246064" id="MMM0000000000005t0xf6TRJPgu7pSJ1IY"
initiationMode="00" note="Sta" purpose="00" refId="Ref"
refUrl="https://www.sbi.co.in/" subType="PAY"
ts="2018-11-28T19:00:11+05:30" type="CREDIT">
<RiskScores>
<Score provider="psp1" type="TXNRISK" value="00090"/>
<Score provider="psp3" type="TXNR2" value="00090"/>
<Score provider="NPCI" type="TXNRISK" value="00999"/>
</RiskScores>

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>

Final Resppay from UPI to Payer PSP

<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>

ReqTxnConfirmation from UPI to Payee PSP

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>


<ns2:ReqTxnConfirmation
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="5t0xf6ZKer9I5ByDDgO"/>

v1.4
Page 68 of 78
Centralised Mapper - TSD

<Txn id="MMM0000000000005t0xf6TRJPgu7pSJ1IY" note="Sta" refId="Ref"


refUrl="https://www.sbi.co.in/" ts="2018-11-28T19:00:11+05:30"
type="TxnConfirmation" orgTxnId="MMM0000000000005t0xf6TRJPgu7pSJ1IY"
custRef="123209246064" initiationMode="00" purpose="00"/>
<TxnConfirmation note="Sta" orgStatus="SUCCESS" type="PAY">
<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"/>
</TxnConfirmation>
</ns2:ReqTxnConfirmation>

RespTxnConfirmation from Payee PSP to UPI


<?xml version="1.0" encoding="UTF-8"?>
<ns2:RespTxnConfirmation
xmlns:ns2="http://npci.org/upi/schema/">
<Head msgId="ANB0000000000005t0xf7oRsP9pmO4132H" orgId="159011"
ts="2021-08-20T09:19:30+05:30" ver="2.0"/>
<Txn custRef="123209246064" id="MMM0000000000005t0xf6TRJPgu7pSJ1IY"
initiationMode="00" note="Sta"
orgTxnId="MMM0000000000005t0xf6TRJPgu7pSJ1IY" purpose="00"
refId="Ref" refUrl="https://www.sbi.co.in/"
ts="2018-11-28T19:00:11+05:30" type="TxnConfirmation"/>
<Resp reqMsgId="5t0xf6ZKer9I5ByDDgO" result="SUCCESS"/>
</ns2:RespTxnConfirmation>

Fetch by ID (Mobile Number)


Request to Fetch by ID (Mobile Number)
<?xml version="1.0" encoding="UTF-8"?>
<ns2:ReqGetAdd
xmlns:ns2="http://npci.org/upi/schema/">
<Head msgId="XYD1442cdd8a121449cae3ab0034f72b165" orgId="159047"
prodType="UPI" ts="2021-08-20T09:32:20+05:30" ver="2.0"/>
<Txn custRef="105015641974" id="MMM0000000000005t0xf6TRJPgu8MszlPG"
note="Mapper" refId="702314088080" refUrl="http://upi" subType="ID"
ts="2017-01-23T14:14:54.040+05:30" type="FETCH"/>
<Payer addr="testingpsp01@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"/>

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>

Response from UPI

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>


<ns2:RespGetAdd
xmlns:ns2="http://npci.org/upi/schema/"
xmlns:ns3="http://npci.org/cm/schema/">
<Head ver="2.0" ts="2021-08-20T09:32:21+05:30" orgId="NPCI"
msgId="5t0xf6ZKer9I6XH8Ox4"/>
<Txn id="MMM0000000000005t0xf6TRJPgu8MszlPG" note="Mapper"
refId="702314088080" refUrl="http://upi" ts="2017-01-23T14:14:54.040+05:30"
type="FETCH" custRef="105015641974" subType="ID"/>
<Resp reqMsgId="XYD1442cdd8a121449cae3ab0034f72b165" result="SUCCESS">
<RegIdDetails addr="testingpsp01@csb” type="PERSON" idStatus="ACTIVE"
lastUpdatedTs="2021-08-20T09:28:13+05:30" channel="MOB">
<Id name="MOBILE" value="9848020212"/>
</RegIdDetails>
</Resp>
</ns2:RespGetAdd>

Fetch by ID (Numeric ID)

Request to Fetch by ID (Numeric ID)

<?xml version="1.0" encoding="UTF-8"?>


<ns2:ReqGetAdd
xmlns:ns2="http://npci.org/upi/schema/">
<Head msgId="XYD1442cdd8a121449cae3ab0034f72b165" orgId="159047"
prodType="UPI" ts="2021-08-20T09:31:08+05:30" ver="2.0"/>
<Txn custRef="105015641974" id="MMM0000000000005t0xf6TRJPgu8EB9eAE"
note="Mapper" refId="702314088080" refUrl="http://upi" subType="ID"
ts="2017-01-23T14:14:54.040+05:30" type="FETCH"/>
<Payer addr="testingpsp01@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"/>

v1.4
Page 70 of 78
Centralised Mapper - TSD

<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="20212223"/>
</RegIdDetails>
</Payer>
</ns2:ReqGetAdd>

Response From UPI

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>


<ns2:RespGetAdd
xmlns:ns2="http://npci.org/upi/schema/"
xmlns:ns3="http://npci.org/cm/schema/">
<Head ver="2.0" ts="2021-08-20T09:31:09+05:30" orgId="NPCI"
msgId="5t0xf6ZKer9I6PPgAjv"/>
<Txn id="MMM0000000000005t0xf6TRJPgu8EB9eAE" note="Mapper"
refId="702314088080" refUrl="http://upi" ts="2017-01-23T14:14:54.040+05:30"
type="FETCH" custRef="105015641974" subType="ID"/>
<Resp reqMsgId="XYD1442cdd8a121449cae3ab0034f72b165" result="SUCCESS">
<RegIdDetails type="PERSON" idStatus="ACTIVE" lastUpdatedTs="2021-08-
20T09:23:10+05:30" channel="MOB">
<Id name="NUMERICID" value="20212223"/>
</RegIdDetails>
</Resp>
</ns2:RespGetAdd>

Fetch by VPA
Request to Fetch by VPA

<?xml version="1.0" encoding="UTF-8"?>


<ns2:ReqGetAdd
xmlns:ns2="http://npci.org/upi/schema/">
<Head msgId="XYD1442cdd8a121449cae3ab0034f72b165" orgId="159047"
prodType="UPI" ts="2021-08-20T09:29:38+05:30" ver="2.0"/>
<Txn custRef="105015641974" id="MMM0000000000005t0xf6TRJPgu8uN7bIk"
note="Mapper" refId="702314088080" refUrl="http://upi" subType="VPA"
ts="2017-01-23T14:14:54.040+05:30" type="FETCH"/>
<Payer addr="testingpsp01@csb" code="0000" name=""
seqNum="1" type="PERSON">
<Device>
<Tag name="MOBILE" value="919769948645"/>
<Tag name="GEOCODE" value=""/>
<Tag name="LOCATION" value=""/>

v1.4
Page 71 of 78
Centralised Mapper - TSD

<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"/>
</Payer>
</ns2:ReqGetAdd>

Response from UPI

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>


<ns2:RespGetAdd
xmlns:ns2="http://npci.org/upi/schema/"
xmlns:ns3="http://npci.org/cm/schema/">
<Head ver="2.0" ts="2021-08-20T09:29:39+05:30" orgId="NPCI"
msgId="5t0xf6ZKer9I6G1iJA5"/>
<Txn id="MMM0000000000005t0xf6TRJPgu8uN7bIk" note="Mapper"
refId="702314088080" refUrl="http://upi" ts="2017-01-23T14:14:54.040+05:30"
type="FETCH" custRef="105015641974" subType="VPA"/>
<Resp reqMsgId="XYD1442cdd8a121449cae3ab0034f72b165" result="SUCCESS">
<RegIdDetails addr="testingpsp01@csb" idStatus="ACTIVE">
<Id name="MOBILE" value="9080924567"/>
</RegIdDetails>
<RegIdDetails addr= “testingpsp01@csb” idStatus="ACTIVE">
<Id name="NUMERICID" value="20212223"/>
</RegIdDetails>
</Resp>
</ns2:RespGetAdd>

Transfer of Mobile Number from One


PSP to Other (PORT)
Request to check the Mobile NumberGetAdd

<?xml version="1.0" encoding="UTF-8"?>


<ns2:ReqGetAdd
xmlns:ns2="http://npci.org/upi/schema/">
<Head msgId="XYD1442cdd8a121449cae3ab0034f72b165" orgId="159047"
prodType="UPI" ts="2021-08-20T09:33:23+05:30" ver="2.0"/>
<Txn custRef="105015641974" id="MMM0000000000005t0xf6TRJPgu8TjbFSM"
note="Mapper" refId="702314088080" refUrl="http://upi"
ts="2017-01-23T14:14:54.040+05:30" type="PORT"/>
<Payer addr="testingpsp01@csb" code="0000" name=""
seqNum="1" type="PERSON">
<Device>

v1.4
Page 72 of 78
Centralised Mapper - TSD

<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>
<Consent name="CMREGISTRATION" value="Y"/>
<RegIdDetails>
<Id name="MOBILE" value="9848020212"/>
</RegIdDetails>
</Payer>
</ns2:ReqGetAdd>

Response for the GetAdd

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>


<ns2:RespGetAdd
xmlns:ns2="http://npci.org/upi/schema/"
xmlns:ns3="http://npci.org/cm/schema/">
<Head ver="2.0" ts="2021-08-20T09:33:23+05:30" orgId="NPCI"
msgId="5t0xf6ZKer9I74wDuam"/>
<Txn id="MMM0000000000005t0xf6TRJPgu8TjbFSM" note="Mapper"
refId="702314088080" refUrl="http://upi" ts="2017-01-23T14:14:54.040+05:30"
type="PORT" custRef="105015641974"/>
<Resp reqMsgId="XYD1442cdd8a121449cae3ab0034f72b165" result="SUCCESS">
<RegIdDetails addr="testingpsp02@csb" type="PERSON" idStatus="ACTIVE"
lastUpdatedTs="2021-08-20T09:28:13+05:30" channel="MOB">
<Id name="MOBILE" value="9848020212"/>
</RegIdDetails>
</Resp>
</ns2:RespGetAdd>

Request to Transfter the Mobile Number

<?xml version="1.0" encoding="UTF-8"?>


<ns2:ReqRegMapper
xmlns:ns2="http://npci.org/upi/schema/">
<Head msgId="XYD1442cdd8a121449cae3ab0034f72b165" orgId="159011"
prodType="UPI" ts="2021-08-20T09:36:27+05:30" ver="2.0"/>
<Txn custRef="105015571146" id="MMM0000000000005t0xf6TRJPgu9doe208"
note="Mapper" op="MODIFY" refId="702314088080" refUrl="http://upi"
ts="2017-01-23T14:14:54.040+05:30" type="CMREGISTRATION"/>
<Payer addr="testingpsp02@andb" code="0000" name=""
seqNum="1" type="PERSON">
<Device>

v1.4
Page 73 of 78
Centralised Mapper - TSD

<Tag name="MOBILE" value="919003250724"/>


<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" prevVpa="testingpsp02@csb" value="Y"/>
<RegIdDetails>
<Id name="MOBILE" setStatus="ACTIVE" value="9848020212"/>
</RegIdDetails>
</Payer>
</ns2:ReqRegMapper>

Response from UPI after Transfer Completion

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>


<ns2:RespRegMapper
xmlns:ns2="http://npci.org/upi/schema/"
xmlns:ns3="http://npci.org/cm/schema/">
<Head ver="2.0" ts="2021-08-20T09:36:27+05:30" orgId="NPCI"
msgId="5t0xf6ZKer9I7oCmdL5"/>
<Txn id="MMM0000000000005t0xf6TRJPgu9doe208" note="Mapper"
refId="702314088080" refUrl="http://upi" ts="2017-01-23T14:14:54.040+05:30"
type="CMREGISTRATION" custRef="105015571146" op="MODIFY"/>
<Resp reqMsgId="XYD1442cdd8a121449cae3ab0034f72b165" result="SUCCESS">
<RegIdDetails addr="testingpsp02@andb">
<Id name="MOBILE" value="9848020212" setStatus="ACTIVE"/>
</RegIdDetails>
</Resp>
</ns2:RespRegMapper>

Notification – Transfer Confirmation Request to


Previous PSP

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>


<ns2:ReqMapperConfirmation
xmlns:ns2="http://npci.org/upi/schema/"
xmlns:ns3="http://npci.org/cm/schema/">

v1.4
Page 74 of 78
Centralised Mapper - TSD

<Head ver="2.0" ts="2021-08-20T09:36:28+05:30" orgId="159047"


msgId="5t0xf6ZKer9I7oDPGW0" prodType="UPI"/>
<Txn id="MMM0000000000005t0xf6TRJPgu9doe208" note="Mapper"
refId="702314088080" refUrl="http://upi" ts="2017-01-23T14:14:54.040+05:30"
type="ReqMapperConfirmation" custRef="105015571146"/>
<TxnConfirmation orgStatus="SUCCESS" op="MODIFY">
<Ref type="PAYER" addr="@andb" cmId="9848020212" channel="MOB"
status="ACTIVE"/>
<Consent name="CMREGISTRATION" value="Y" prevVpa="testingpsp01@csb"/>
</TxnConfirmation>
</ns2:ReqMapperConfirmation>

Notification – Transfer Confirmation Response from


Previous PSP

<?xml version="1.0" encoding="UTF-8"?>


<ns2:RespMapperConfirmation
xmlns:ns2="http://npci.org/upi/schema/">
<Head msgId="CSB0000000000005t0xf7oRsP9poB9Pi12" orgId="159047"
ts="2021-08-20T09:36:28+05:30" ver="2.0"/>
<Txn custRef="105015571146" id="MMM0000000000005t0xf6TRJPgu9doe208"
note="Mapper" refId="702314088080" refUrl="http://upi"
ts="2017-01-23T14:14:54.040+05:30" type="ReqMapperConfirmation"/>
<Resp reqMsgId="5t0xf6ZKer9I7oDPGW0" result="SUCCESS"/>
</ns2:RespMapperConfirmation>

11 Error Codes

Error code Error code description Comments


Consent Validation
C30 Consent not present
C31 Cannot process request with Consent value other than Y
C32 Consent name should be CMREGISTRATION
C33 Please input proper Consent type
RegIdDetails Validation(individual ID tags as well)
V30 RegIdDetails must be present
V31 Id must be present

v1.4
Page 75 of 78
Centralised Mapper - TSD

V32 Id name must be present


V33 Id value must be present
V34 Id must consist of alphanumeric characters only Numeric ID
V35 Id must be larger than 6 digits
V36 Id must not be of length 10/11/12
V37 Id must be shorter than 16 digits
V38 Id must not start with 0
V39 Id must not end with same last three digits
V40 Id must not contain same digits
V41 Id must consist of alphanumeric characters only Mobile ID
V42 Id must consist of proper 10 digited mobile number
Mapping validation
MM1 MAPPING_EXISTS
MM2 MAPPING_DOES_NOT_EXIST
MM3 MAPPING_BLOCKED
MM4 MAPPING_INACTIVE
MM5 VPA_MAPPED_TO_ANOTHER_MOBILE
MM6 VPA_OF_DIFFERENT_ORG
MM7 MAPPING_ACTIVATION_NOT_ALLOWED
MM8 PREVVPA_NOT_SAME_AS_CACHE
MM9 CANNOT_ACTIVATE_DEREGISTERED_MOBILE
MM10 COOLING_PERIOD_NOT_OVER
MM11 TYPE_NOT_SUPPORTED_FOR_GETADD
MM12 TXN_SUBTYPE_ID_NO_REGIDDETAILS_PRESENT
MM13 PROPER_TXN_SUBTYPE_NOT_PRESENT
MM14 PROPER_TXN_TYPE_NOT_PRESENT
MM15 MAPPING_AGAINST_VPA_ABSENT
MM16 CANNOT_PORT_NUMERIC_ID
MM17 CHECK_ACTION_NOT_PERMITTED
MM18 ID_MAPPED_TO_DIFFERENT_VPA
MM19 PORT_ACTION_PROHIBITED
MM20 VAULT_INACCESSIBLE
MM21 CMID_ADDITION_PROHIBITED_BEYOND_THREE

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

You might also like