unified payment interface message dumps upi message dumps, oct.15, 2015.pdf · unified payment...

122
UPI MESSAGE DUMPS v1.0 15/10/2015 Page 1 of 122 UNIFIED PAYMENT INTERFACE MESSAGE DUMPS V1.0

Upload: duongnhan

Post on 04-Apr-2018

231 views

Category:

Documents


1 download

TRANSCRIPT

Page 1: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS v1.0

15/10/2015 Page 1 of 122

UNIFIED PAYMENT INTERFACE MESSAGE DUMPS V1.0

Page 2: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS v1.0

15/10/2015 Page 2 of 122

Documents Details

Document History

Name Version No. Date Description

Unified Payment Interface Message Dumps

1.0 19/09/2015 Provides Message Dumps for

ReqPay, RespPay, ReqAuth and

RespAuth messages

Prepared By: Date

Vikas Sharma 10/10/2015

Mohd Zeeshan Khan 10/10/2015

Reviewed By: Date

Sateesh Palagiri 15/10/2015

K Venkatesh 15/10/2015

Approved By: Date

Dr. Rajendran N 15/10/2015

Author NPCI

Published Date 15/10/2015

Version V1.0

Total Pages 122

Document classification Public

Page 3: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS v1.0

15/10/2015 Page 3 of 122

Contents

CASE 1 ...................................................................................................................................... 6

1.1 Flow:............................................................................................................................ 6

1.2 ReqPay (PSP1 to UPI System) .................................................................................... 6

1.3 MSG_ACK(to be sent for every message) ................................................................ 10

1.4 ReqAuthDetails(UPI to PSP2) .................................................................................. 10

1.5 RespAuthDetails(PSP2 to UPI) ................................................................................. 12

1.6 ReqPay_NPCI_DEBIT_REQ(UPI to PSP1) ............................................................. 14

1.7 RespPay_NPCI_DEBIT_REQ_RES(PSP1 to UPI) .................................................. 18

1.8 ReqPay_NPCI_CREDIT_REQ(UPI to PSP2) .......................................................... 19

1.9 RespPay_NPCI_CREDIT_REQ_RES(PSP2 to UPI) ............................................... 23

1.10 RespPay(UPI to PSP1) .......................................................................................... 24

1.11 ReqTxnConfirmation(UPI to PSP2) ...................................................................... 27

1.12 RespTxnConfirmation(PSP2 to UPI) .................................................................... 27

CASE 2 .................................................................................................................................... 28

2.1 Flow:.......................................................................................................................... 28

2.2 ReqPay(PSP1 to UPI) ............................................................................................... 29

2.3 MSG_ACK(to be send for every message) ............................................................... 32

2.4 ReqAuthDetails(UPI to PSP2) .................................................................................. 32

2.5 RespAuthDetails(PSP2 to UPI) ................................................................................. 34

2.6 ReqPay_NPCI_DEBIT_REQ(UPI to PSP2) ............................................................. 37

2.7 RespPay_NPCI_DEBIT_REQ_RES(PSP2 to UPI) .................................................. 40

2.8 ReqPay_NPCI_CREDIT_REQ(UPI to PSP2) .......................................................... 42

2.9 RespPay_NPCI_CREDIT_REQ_RES(PSP2 to UPI) ............................................... 46

2.10 RespPay(UPI to PSP1) .......................................................................................... 47

2.11 ReqTxnConfirmation(UPI to PSP2) ...................................................................... 49

2.12 RespTxnConfirmation(PSP2 to UPI) .................................................................... 49

CASE 3 .................................................................................................................................... 50

3.1 Flow:.......................................................................................................................... 50

3.2 ReqPay(PSP1 to UPI) ............................................................................................... 51

3.3 MSG_ACK(to be send for every message) ............................................................... 54

3.4 ReqAuthDetails(UPI to PSP2) .................................................................................. 54

Page 4: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS v1.0

15/10/2015 Page 4 of 122

3.5 RespAuthDetails(PSP2 to UPI) ................................................................................. 56

3.6 ReqPay_NPCI_DEBIT_REQ(UPI to PSP1) ............................................................. 58

3.7 RespPay_NPCI_DEBIT_REQ_RES(PSP1 to UPI) .................................................. 62

3.8 RespPay(UPI to PSP1) .............................................................................................. 63

3.9 ReqTxnConfirmation(UPI to PSP2).......................................................................... 64

3.10 RespTxnConfirmation(PSP2 to UPI) .................................................................... 65

CASE 4 .................................................................................................................................... 66

4.1 Flow:.......................................................................................................................... 66

4.2 ReqListAccount: Request for Account List .............................................................. 67

4.3 RespListAccount: Response for Account List .......................................................... 67

4.4 ReqPay(PSP1 to UPI) ............................................................................................... 68

4.5 ReqPay_NPCI_DEBIT_REQ(UPI to PSP1) ............................................................. 71

4.6 RespPay_NPCI_DEBIT_REQ_RES(PSP1 to UPI) .................................................. 75

4.7 RespPay(UPI to PSP1) .............................................................................................. 76

4.8 ReqTxnConfirmation(UPI to PSP2).......................... Error! Bookmark not defined.

4.9 RespTxnConfirmation(PSP2 to UPI) ........................ Error! Bookmark not defined.

CASE 5 .................................................................................................................................... 78

5.1 Flow:.......................................................................................................................... 78

5.2 ReqPay(PSP1 to UPI) ............................................................................................... 79

5.3 MSG_ACK(to be send for every message) ............................................................... 82

5.4 ReqAuthDetails(UPI to PSP2) .................................................................................. 82

5.5 RespAuthDetails(PSP2 to UPI) ................................................................................. 84

5.6 ReqPay_NPCI_DEBIT_REQ(UPI to PAYER BANK) ............................................ 87

5.7 RespPay_NPCI_DEBIT_REQ_RES(PAYER BANK to UPI) ................................. 90

5.8 ReqPay_NPCI_CREDIT_REQ(UPI to PAYEE BANK) ......................................... 92

5.9 RespPay_NPCI_CREDIT_REQ_RES(PAYEE BANK to UPI) .............................. 96

5.10 RespPay(UPI to PSP1) .......................................................................................... 97

5.11 ReqTxnConfirmation(UPI to PAYER BANK) ..................................................... 99

5.12 RespTxnConfirmation(PAYER BANK to UPI).................................................... 99

CASE 6 .................................................................................................................................. 101

6.1 Flow:........................................................................................................................ 101

6.2 ReqPay (PSP1 to UPI System) ................................................................................ 102

6.3 MSG_ACK(to be sent for every message) .............................................................. 105

6.4 ReqAuthDetails(UPI to PSP2) ................................................................................ 105

6.5 RespAuthDetails(PSP2 to UPI) ............................................................................... 107

6.6 ReqPay_NPCI_DEBIT_REQ(UPI to PAYER BANK) .......................................... 109

Page 5: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS v1.0

15/10/2015 Page 5 of 122

6.7 RespPay_NPCI_DEBIT_REQ_RES(PAYER BANK to UPI) ............................... 113

6.8 ReqPay_NPCI_CREDIT_REQ(UPI to PAYEE BANK) ....................................... 114

6.9 RespPay_NPCI_CREDIT_REQ_RES(PAYEE BANK to UPI) ............................ 118

6.10 RespPay(UPI to PSP1) ........................................................................................ 119

6.11 ReqTxnConfirmation(UPI to PSP2) .................................................................... 122

6.12 RespTxnConfirmation(PSP2 to UPI) .................................................................. 122

Page 6: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS v1.0

15/10/2015 Page 6 of 122

CASE 1

TWO PARTY MODEL – Pay Request [Payer PSP & Remitter Bank are one entity and

Payee PSP & Beneficiary Bank are also one entity]

1.1 Flow:

1. Customer initiates a pay Request by entering the Virtual Address of the Payee

customer.

2. Payer PSP sends the ReqPay message to UPI

3. UPI sends ReqAuthDetails message to the respective Payee PSP.

4. Payee PSP validates the Address and responds back with the financial address of the Payee in the RespAuthDetails message to UPI.

5. UPI sends a debit request to Payer PSP 6. Payer PSP debits the account of the customer and responds back to UPI 7. UPI sends a credit request to the Beneficiary Bank based on the financial

address of the Payee 8. Beneficiary Bank credits the customer’s account and responds back with

successful credit to UPI 9. UPI sends a successful confirmation to the Payer PSP and Payee PSP 10. Payer PSP sends the confirmation to the customer.

1.2 ReqPay (PSP1 to UPI System)

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

Page 7: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS v1.0

15/10/2015 Page 7 of 122

<Head ver="1.0" ts="2015-02-16T22:02:35+05:30" orgId="400002" msgId="HENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM"/> <Meta> <Tag name="PAYREQSTART" value="2015-02-16T22:02:00+05:30"/> <Tag name="PAYREQEND" value="2015-02-16T22:02:35+05:30"/> </Meta> <Txn id="8ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM" note="Restaurant Bill " refId="" refUrl="" ts="2015-02-16T22:02:35+05:30" type="PAY" orgTxnId=""> <RiskScores> <Score provider="psp1" type="TXNRISK" value="00030"/> </RiskScores> </Txn> <Payer addr="zeeshan.khan@hdfc" name="Zeeshan Khan" seqNum="1" type="PERSON" code="4814"> <Info> <Identity type="ACCOUNT" verifiedName="Zeeshan Khan" id="7389923983430"/> <Rating verifiedAddress="TRUE"/> </Info> <Device> <Tag name="MOBILE" value="+91.99999.00000"/> <Tag name="GEOCODE" value="288177"/> <Tag name="LOCATION" value="Mumbai,Maharashtra" /> <Tag name="IP" value="124.170.23.22"/> <Tag name="TYPE" value="mob"/> <Tag name="ID" value="750c6be243f1c4b5c9912b95a5742fc5"/> #device advertising id <Tag name="OS" value="android"/> <Tag name="APP" value="NPCIAPP"/> <Tag name="CAPABILITY" value="5200000200010004000639292929292"/> </Device> <Ac addrType="ACCOUNT"> <Detail name="ACTYPE" value="SAVINGS"/> <Detail name="IFSC" value="HDFC0288100"/> <Detail name="ACNUM" value="2678892001828"/> </Ac> <Creds> <Cred type="PIN" subType="MPIN">

<Data code="" ki=""> base-64 encoded and encrypted</Data> #data includes [base 64 encoded]<Transaction Id><delimiter><Common library version><delimiter><Captured credential><delimiter><Transaction amount><delimiter><Random number>[encrypted] ,"|" to be used as delimiter and order of the elements should be same.

</Cred> </Creds> <Amount value="4000" curr="INR"> </Amount> </Payer> <Payees> <Payee addr="rohit.patekar@sbi" name="" seqNum="1" type="" code=""> </Payee> </Payees> </upi:ReqPay>

Index Message Item <XML Tag> Occurrence Sample Value

1.1 API Name <upi> 1..1 ReqPay

1.1.1 API Schema namespace Xmlns 1..1 upi="http://npci.org/upi/schema/

Page 8: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS v1.0

15/10/2015 Page 8 of 122

2.1 Header for the message <Head> 1..1

2.1.1 Version of the API Ver 1..1 1.0

2.1.2 Time of request from the creator of the message

Ts 1..1 2015-02-16T22:02:35+05:30

2.1.3 Organization id that created the message

orgId 1..1 400002

2.1.4 Message identifier-used to correlate between request and response

msgId 1..1 HENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM

3.1 Meta data primarily for analytics purposes

<Meta> 0..1

3.2 Meta data primarily for analytics purposes

<Meta.Tag> 0..1

3.2.1 Name of the property Name 1..n PAYREQSTART

3.2.2 Value of the property Value 1..n 2015-02-16T22:02:00+05:30

4.1 Transaction information, Carried throughout the system, visible to all parties

<Txn> 1..1

4.1.1 Unique Identifier of the transaction across all entities, created by the originator

Id 1..1 8ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM

4.1.2 Description of the transaction(which will be printed on Pass book)

Note 1..1 Restaurant Bill

4.1.3 Consumer reference number to identify (like Loan number, etc.)

refId 1..1

4.1.4 URL for the transaction refUrl 1..1

4.1.5 Transaction origination time by the creator of the message

Ts 1..1 2015-02-16T22:02:35+05:30

4.1.6 Type of the Transaction Type 1..1 PAY

4.1.7 Original transaction ID when reversal/Refund has to be done

orgTxnId 1..1

4.2 Risk Score related to the transaction and the entities

<Txn.RiskScores> 0..1

4.3 Risk Score related to the transaction and the entities

<Txn.RiskScores.Score> 0..1

4.3.1 Entity providing the risk score provider 1..1 psp1

4.3.2 Type of risk Type 1..1 TXNRISK

4.3.3 Value of risk evaluation ranging from 0 (No Risk) to 100 (Maximum Risk)

Value 1..1 00030

5.1 Details related to the Payer <Payer> 1..1

5.1.1 Address of the Payer Addr 1..1 zeeshan.khan@hdfc

5.1.2 Name of the Payer Name 1..1 Zeeshan Khan

5.1.3 Unique identifier for each transaction inside a file including payer and payee

seqNum 1..1 1

5.1.4 Type of the Payer Type 1..1 PERSON

5.1.5 Merchant Classification Code -MCC

Code 1..1 4814

5.2 Information related to the Payer <Payer.Info> 1..1

Page 9: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS v1.0

15/10/2015 Page 9 of 122

5.3 Payer Identity Is mandatory for “collect” and optional for “pay”

<Payer.Info.Identity> 1..1

5.3.1 Type of the identifier Type 1..1 ACCOUNT

5.3.2 Name as per the identifier verifiedName 1..1 Zeeshan Khan

5.3.3. Id Id 1.1 7389923983430

5.4 Rating of the payer <Rating> 0..1

5.4.1 Payer is whitelisted or not verifiedAddress 1..1 TRUE

5.5 Details of Device from which the transaction was initiated

<Payer.Device> 1..1

5.6 Device Tag <Payer.Device.Tag> 1..n

5.6.1 Name of the property Name 1..n MOBILE

5.6.2 Value of the property Value 1..n +91.99999.00000

5.7 Only one entity is allowed for a payer

<Payer.Ac> 1..1

5.7.1 Type of the address addrType 1..1 ACCOUNT

5.8 Details related to Payer Address <Payer.Ac.Detail> 1..n

5.8.1 Name of the property Name 1..n ACTYPE

5.8.2 Value of the property Value 1..n SAVINGS

5.8.3 Name of the property Name 1..n IFSC

5.8.4 Value of the property Value 1..n HDFC0288100

5.8.5 Name of the property Name 1..n ACNUM

5.8.6 Value of the property Value 1..n 2678892001828

5.9 Information related to Payer Credentials

<Payer.Creds> 1..1

5.10 Credentials are used to authenticate the request

<Payer.Creds.Cred> 1..1

5.10.1 Type of financial instrument used for authentication

Type 1..1 PreApproved

5.10.2 Subtype of Financial instrument used for authentication

subtype 1.1 NA

5.11 base-64 encoded/encrypted authentication data

<Payer.Creds.Cred.Data>

1..1 Base 64 encoded value of RES|A12345

5.12 Information related to the amounts in the transaction

<Payer.Amount> 1..1

5.12.1 Transaction amount Value 1..1 4000

5.12.2 Currency of the transaction Curr 1..1 INR

6.1 Details related to the Payees <Payees> 1..1

6.2 Details related to the Payee <Payee> 1..1

6.2.1 Address of the Payee Addr 1..1 rohit.patekar@sbi

6.2.2 Name of the Payee Name 1..1

6.2.3 Unique identifier for each transaction inside a file including Payee and payee

seqNum 1..1 1

6.2.4 Type of the Payee Type 1..1

6.2.5 Merchant Classification Code -MCC

Code 1..1

Page 10: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS v1.0

15/10/2015 Page 10 of 122

1.3 MSG_ACK(to be sent for every message)

<upi:Ack xmlns:upi="" api="" reqMsgId="" err="" ts=""/>

1.4 ReqAuthDetails(UPI to PSP2)

<upi:ReqAuthDetails xmlns:upi="http://npci.org/upi/schema/"> <Head ver="1.0" ts="2015-02-16T22:02:40+05:30" orgId="400001" msgId="NPNSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM"/> <Txn id="8ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM" note="Restaurant Bill " refId=““ refUrl=““ ts="2015-02-16T22:02:35+05:30" type="PAY"> <RiskScores> <Score provider="psp1" type="TXNRISK" value="00030"/> <Score provider="NPCI" type="TXNRISK" value="00030"/> </RiskScores> </Txn> <Payer addr="zeeshan.khan@hdfc" name="Zeeshan Khan" seqNum="1" type="PERSON" code="4814"> <Info> <Identity type="ACCOUNT" verifiedName="Zeeshan Khan" id="7389923983430"/> <Rating verifiedAddress="TRUE"/> </Info> <Amount value="4000" curr="INR"> </Amount> </Payer> <Payees> <Payee addr="rohit.patekar@sbi" name="" seqNum="1" type="" code=""> </Payee> </Payees> </upi:ReqAuthDetails>

Index Message Item <XML Tag> Occurrence

Sample Value

1.1 API Name <ReqAuthDetails> 1..1 ReqAuthDetails

1.1.1 API Schema namespace xmlns 1..1 upi="http://npci.org/upi/schema

2.1 Header for the message <Head> 1..1

2.1.1 Version of the API ver 1..1 1

2.1.2 Time of request from the creator of the message

ts 1..1 2015-02-16T22:02:45+05:30

2.1.3 Organization id that created the message

orgId 1..1 400001

2.1.4 Message identifier-used to correlate between request and response

msgId 1..1 NPNSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM

3.1 Transaction information, Carried throughout the system, visible to all parties

<Txn> 1..1

3.1.1 Unique Identifier of the transaction across all entities created by the originator

id 1..1 8ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM

3.1.2 Description of the transaction(which will be printed on Pass book)

note 1..1 Restaurant Bill

Page 11: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS v1.0

15/10/2015 Page 11 of 122

Index Message Item <XML Tag> Occurrence

Sample Value

3.1.3 Consumer reference number to identify (like Loan number, etc.)

ref 1..1

3.1.4 Transaction origination time by the creator of the message

ts 1..1 2015-02-16T22:02:35+05:30

3.1.5 Type of the Transaction type 1..1 PAY

3.2 Risk Score related to the transaction and the entities

<Txn.RiskScores> 0..1

3.3 Risk Score related to the transaction and the entities

<Txn.RiskScores.Score> 0..1

3.3.1 Entity providing the risk score provider 1..1 Psp2

3.3.2 Type of risk type 1..1 TXNRISK

3.3.3 Value of risk evaluation ranging from 0 (No Risk) to 100 (Maximum Risk)

value 1..1 00030

4.1 Details related to the Payer <Payer> 1..1

4.1.1 Address of the Payer addr 1..1 zeeshan.khan@hdfc

4.1.2 Name of the Payer name 1..1 Zeeshan Khan

4.1.3 Unique identifier for each transaction inside a file including payer and payee

seqNum 1..1 1

4.1.4 Type of the Payer type 1..1 PERSON

4.1.5 Merchant Classification Code -MCC

code 1..1 4814

4.2 Information related to the Payer <Payer.Info> 1..1

4.3 Payer Identity is mandatory for “collect” and optional for “pay”

<Payer.Info.Identity> 1..1

4.3.1 Type of the identifier type 1..1 ACCOUNT

4.3.2 Name as per the identifier verifiedName 1..1 Zeeshan Khan

4.3.3 Identifier Id 1.1 7389923983430

4.4 Rating of the payer <Payer.Info.Rating> 0..1

4.4.1 Payer is whitelisted or not verifiedAddress 1..1 TRUE

4.5 Information related to the amounts in the transaction

<Payer.Amount> 1..1

4.5.1 Transaction amount value 1..1 4000

4.5.2 Currency of the transaction curr 1..1 INR

6.1 Details related to the Payees <Payees> 1..1

6.2 Details related to the Payee <Payee> 1..1

6.2.1 Address of the Payee addr 1..1 rohit.patekar@sbi

6.2.2 Name of the Payee name 1..1

6.2.3 Unique identifier for each transaction inside a file including Payee and payee

seqNum 1..1 1

6.2.4 Type of the Payee type 1..1

6.2.5 Merchant Classification Code -MCC

code 1..1

Page 12: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS v1.0

15/10/2015 Page 12 of 122

1.5 RespAuthDetails(PSP2 to UPI)

<upi:RespAuthDetails xmlns:upi="http://npci.org/upi/schema/"> <Head ver="1.0" ts="2015-02-16T22:02:45+05:30" orgId="400003" msgId="SBNSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM"/> <Resp reqMsgId="NPNSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM" result="SUCCESS" errCode=""/> <Txn id="8ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM" note="Restaurant Bill " refId=““ refUrl=““ ts="2015-02-16T22:02:35+05:30" type="PAY"> <RiskScores> <Score provider="psp2" type="TXNRISK" value="00030"/> <Score provider="NPCI" type="TXNRISK" value="00030"/> </RiskScores> </Txn> <Payer addr="zeeshan.khan@hdfc" name="Zeeshan Khan" seqNum="1" type="PERSON" code="4814"> <Info> <Identity type="ACCOUNT" verifiedName="Zeeshan Khan" id="7389923983430"/> <Rating verifiedAddress="TRUE"/> </Info> <Amount value="4000" curr="INR"> </Amount> </Payer> <Payees> <Payee addr="rohit.patekar@sbi" name="Rohit Patekar" seqNum="1" type="PERSON" code="4814"> #mcc has to be populated <Info> <Identity type="ACCOUNT" verifiedName="Rohit Patekar" id="8392389838"/> <Rating verifiedAddress="TRUE"/> </Info> <Ac addrType="ACCOUNT"> <Detail name="IFSC" value="SBIN0288100"/> <Detail name="ACTYPE" value="SAVINGS"/> <Detail name="ACNUM" value="5678892001828"/> </Ac> <Amount value="4000" curr="INR"> </Amount> </Payee> </Payees> </upi:RespAuthDetails>

Index Message Item <XML Tag> Occurrence Sample Value

1.1 API Name <RespAuthDetails> 1..1 RespAuthDetails

1.1.1 API Schema namespace xmlns 1..1 upi="http://npci.org/upi/schema/

2.1 Header for the message <Head> 1..1

2.1.1 Version of the API ver 1..1 1.0

2.1.2 Time of request from the creator of the message

ts 1..1 2015-02-16T22:02:45+05:30

2.1.3 Organization id that created the message

orgId 1..1 400003

Page 13: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS v1.0

15/10/2015 Page 13 of 122

Index Message Item <XML Tag> Occurrence Sample Value

2.1.4 Message identifier-used to correlate between request and response

msgId 1..1 SBNSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM

3.1 Response <Resp> 1..1

3.1.1 Request Message identifier reqMsgId 1..1 NPNSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM

3.1.2 Result of the transaction result 1..1 SUCCESS

3.1.3 Error code if failed errCode 1..1

4.1 Transaction information, Carried throughout the system, visible to all parties

<Txn> 1..1

4.1.1 Unique Identifier of the transaction across all entities created by the originator

id 1..1 8ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM

4.1.2 Description of the transaction(which will be printed on Pass book)

note 1..1 Restaurant Bill

4.1.3 Consumer reference number to identify (like Loan number, etc.)

ref 1..1

4.1.4 Transaction origination time by the creator of the message

ts 1..1 2015-02-16T22:02:35+05:30

4.1.5 Type of the Transaction type 1..1 PAY

4.2 Risk Score related to the transaction and the entities

<Txn.RiskScores> 0..1

4.3 Risk Score related to the transaction and the entities

<Txn.RiskScores.Score>

0..1

4.3.1 Entity providing the risk score provider 1..1 Psp2

4.3.2 Type of risk type 1..1 TXNRISK

4.3.3 Value of risk evaluation ranging from 0 (No Risk) to 100 (Maximum Risk)

value 1..1 00030

5.1 Details related to the Payer <Payer> 1..1

5.1.1 Address of the Payer addr 1..1 zeeshan.khan@hdfc

5.1.2 Name of the Payer name 1..1 Zeeshan Khan

5.1.3 Unique identifier for each transaction inside a file including payer and payee

seqNum 1..1 1

5.1.4 Type of the Payer type 1..1 PERSON

5.1.5 Merchant Classification Code -MCC code 1..1 4814

5.2 Information related to the Payer <Payer.Info> 1..1

5.3 Payer Identity is mandatory for “collect” and optional for “pay”

<Payer.Info.Identity> 1..1

5.3.1 Type of the identifier type 1..1 ACCOUNT

5.3.2 Name as per the identifier verifiedName 1..1 Zeeshan Khan

5.3.3 Id Id 1.1 7389923983430

5.4 Rating of the payer <Payer.Info.Rating> 0..1

5.4.1 Payer is whitelisted or not verifiedAddress 1..1 TRUE

5.5 Information related to the amounts in the transaction

<Payer.Amount> 1..1

5.5.1 Transaction amount value 1..1 4000

5.5.2 Currency of the transaction curr 1..1 INR

6.1 Details related to the Payees <Payees> 1..1

6.2 Details related to the Payee <Payee> 1..1

6.2.1 Address of the Payee addr 1..1 rohit.patekar@sbi

6.2.2 Name of the Payee name 1..1 Rohit Patekar

Page 14: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS v1.0

15/10/2015 Page 14 of 122

Index Message Item <XML Tag> Occurrence Sample Value

6.2.3 Unique identifier for each transaction inside a file including Payee and payee

seqNum 1..1 1

6.2.4 Type of the Payee type 1..1 PERSON

6.2.5 Merchant Classification Code -MCC code 1..1 4814

6.3 Information related to the Payee <Payee.Info> 1..1

6.4 Payee Identity <Payee.Info.Identity> 1..1

6.4.1 Type of the identifier type 1..1 ACCOUNT

6.4.2 Name as per the identifier verifiedName 1..1 Rohit Patekar

6.4.3 Id Id 1.1 8392389838

6.5 Rating of the Payee <Payee.Info.Rating> 0..1

6.5.1 Payee is whitelisted or not verifiedAddress 1..1 TRUE

6.6 Only one entity is allowed for a Payee <Payee.Ac> 1..1

6.6.1 Type of the address addrType 1..1 ACCOUNT

6.7 Details related to Payee Address <Payee.Ac.Detail> 1..n

6.7.1 Name of the property name 1..n IFSC

6.7.2 Value of the property value 1..n SBIN0288100

6.7.3 Name of the property name 1..n ACTYPE

6.7.4 Value of the property value 1..n SAVINGS

6.7.5 Name of the property name 1..n ACNUM

6.7.6 Value of the property value 1..n 5678892001828

6.8 Information related to the amounts in the transaction

<Payee.Amount> 1..1

6.8.1 Transaction amount value 1..1 4000

6.8.2 Currency of the transaction curr 1..1 INR

1.6 ReqPay_NPCI_DEBIT_REQ(UPI to PSP1)

<upi:ReqPay xmlns:upi="http://npci.org/upi/schema/"> <Head ver="1.0" ts="2015-02-16T22:02:48+05:30" orgId="400001" msgId="HENSVVR4QZS7X1UGPY7JGUV444PL9Z2C3QZ"/> <Meta> <Tag name="PAYREQSTART" value="2015-02-16T22:02:00+05:30"/> <Tag name="PAYREQEND" value="2015-02-16T22:02:35+05:30"/> </Meta> <Txn id="8ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM" note="Restaurant Bill " refId="" refUrl="" ts="2015-02-16T22:02:35+05:30" type="DEBIT" orgTxnId=""> <RiskScores> <Score provider="psp1" type="TXNRISK" value="00030"/> <Score provider="npci" type="TXNRISK" value="00030"/> </RiskScores> </Txn> <Payer addr="zeeshan.khan@hdfc" name="Zeeshan Khan" seqNum="1" type="PERSON" code="4814"> <Info> <Identity type="ACCOUNT" verifiedName="Zeeshan Khan" id="7389923983430"/> <Rating verifiedAddress="TRUE"/> </Info> <Device> <Tag name="MOBILE" value="+91.99999.00000"/> <Tag name="GEOCODE" value="288177"/> <Tag name="LOCATION" value="Mumbai,Maharashtra" />

Page 15: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS v1.0

15/10/2015 Page 15 of 122

<Tag name="IP" value="124.170.23.22"/> <Tag name="TYPE" value="mob"/> <Tag name="ID" value="750c6be243f1c4b5c9912b95a5742fc5"/> #device advertising id <Tag name="OS" value="android"/> <Tag name="APP" value="NPCIAPP"/> <Tag name="CAPABILITY" value="5200000200010004000639292929292"/> </Device> <Ac addrType="ACCOUNT"> <Detail name="ACTYPE" value="SAVINGS"/> <Detail name="IFSC" value="HDFC0288100"/> <Detail name="ACNUM" value="2678892001828"/> </Ac> <Creds> <Cred type="PIN" subType="MPIN">

<Data code="" ki=""> base-64 encoded and encrypted</Data> #data includes [<Transaction Id><delimiter><Common library version><delimiter><Captured credential><delimiter><Transaction amount><delimiter><Random number> ,"|" to be used as delimiter

</Cred>

</Creds> <Amount value="4000" curr="INR"> </Amount> </Payer> <Payees> <Payee addr="rohit.patekar@sbi" name="Rohit Patekar" seqNum="1" type="PERSON" code="4814">#mcc has to be populated <Info> <Identity type="ACCOUNT" verifiedName="Rohit Patekar" id="8392389838"/> <Rating verifiedAddress="TRUE"/> </Info> <Ac addrType="ACCOUNT"> <Detail name="IFSC" value="SBIN0288100"/> <Detail name="ACTYPE" value="SAVINGS"/> <Detail name="ACNUM" value="5678892001828"/> </Ac> <Amount value="4000" curr="INR"> </Amount> </Payee> </Payees> </upi:ReqPay>

Index Message Item <XML Tag> Occurrence Sample Value

1.1 API Name <upi> 1..1 ReqPay

1.1.1 API Schema namespace xmlns 1..1 upi="http://npci.org/upi/schema/

2.1 Header for the message <Head> 1..1

2.1.1 Version of the API ver 1..1 1.0

2.1.2 Time of request from the creator of the message

ts 1..1 2015-02-16T22:02:35+05:30

2.1.3 Organization id that created the message

orgId 1..1 400001

2.1.4 Message identifier-used to correlate between request and response

msgId 1..1 HENSVVR4QZS7X1UGPY7JGUV444PL9Z2C3QM

3.1 Meta data primarily for analytics purposes

<Meta> 0..1

Page 16: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS v1.0

15/10/2015 Page 16 of 122

Index Message Item <XML Tag> Occurrence Sample Value

3.2 Meta data primarily for analytics purposes

<Meta.Tag> 0..1

3.2.1 Name of the property name 1..n PAYREQSTART

3.2.2 Value of the property value 1..n 2015-02-16T22:02:00+05:30

4.1 Transaction information, Carried throughout the system, visible to all parties

<Txn> 1..1

4.1.1 Unique Identifier of the transaction across all entities, created by the originator

id 1..1 8ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM

4.1.2 Description of the transaction(which will be printed on Pass book)

note 1..1 Restaurant Bill

4.1.3 Consumer reference number to identify (like Loan number, etc.)

refId 1..1

4.1.4 URL for the transaction refUrl 1..1

4.1.5 Transaction origination time by the creator of the message

ts 1..1 2015-02-16T22:02:35+05:30

4.1.6 Type of the Transaction type 1..1 CREDIT

4.1.7 Original transaction ID when reversal/Refund has to be done

orgTxnId 1..1

4.2 Risk Score related to the transaction and the entities

<Txn.RiskScores> 0..1

4.3 Risk Score related to the transaction and the entities

<Txn.RiskScores.Score> 0..1

4.3.1 Entity providing the risk score provider 1..1 psp1

4.3.2 Type of risk type 1..1 TXNRISK

4.3.3 Value of risk evaluation ranging from 0 (No Risk) to 100 (Maximum Risk)

value 1..1 00030

5.1 Details related to the Payer <Payer> 1..1

5.1.1 Address of the Payer addr 1..1 zeeshan.khan@hdfc

5.1.2 Name of the Payer name 1..1 Zeeshan Khan

5.1.3 Unique identifier for each transaction inside a file including payer and payee

seqNum 1..1 1

5.1.4 Type of the Payer type 1..1 PERSON

5.1.5 Merchant Classification Code -MCC

code 1..1 4814

5.2 Information related to the Payer <Payer.Info> 1..1

5.3 Payer Identity Is mandatory for “collect” and optional for “pay”

<Payer.Info.Identity> 1..1

5.3.1 Type of the identifier type 1..1 ACCOUNT

5.3.2 Name as per the identifier verifiedName 1..1 Zeeshan Khan

5.3.3. Id Id 1.1 7389923983430

5.4 Rating of the payer <Rating> 0..1

5.4.1 Payer is whitelisted or not verifiedAddress 1..1 TRUE

Page 17: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS v1.0

15/10/2015 Page 17 of 122

Index Message Item <XML Tag> Occurrence Sample Value

5.5 Details of Device from which the transaction was initiated

<Payer.Device> 1..1

5.6 Device Tag <Payer.Device.Tag> 1..n

5.6.1 Name of the property name 1..n MOBILE

5.6.2 Value of the property value 1..n +91.99999.00000

5.7 Only one entity is allowed for a payer

<Payer.Ac> 1..1

5.7.1 Type of the address addrType 1..1 ACCOUNT

5.8 Details related to Payer Address <Payer.Ac.Detail> 1..n

5.8.1 Name of the property name 1..n ACTYPE

5.8.2 Value of the property value 1..n SAVINGS

5.8.3 Name of the property name 1..n IFSC

5.8.4 Value of the property value 1..n HDFC0288100

5.8.5 Name of the property name 1..n ACNUM

5.8.6 Value of the property value 1..n 2678892001828

5.9 Information related to Payer Credentials

<Payer.Creds> 1..1

5.10 Credentials are used to authenticate the request

<Payer.Creds.Cred> 1..1

5.10.1 Type of financial instrument used for authentication

Type 1..1 PreApproved

5.10.2 Subtype of Financial instrument used for authentication

subtype 1.1 NA

5.11 base-64 encoded/encrypted authentication data

<Payer.Creds.Cred.Data> 1..1 Base 64 encoded value of RES|A12345

5.12 Information related to the amounts in the transaction

<Payer.Amount> 1..1

5.12.1 Transaction amount Value 1..1 4000

5.12.2 Currency of the transaction Curr 1..1 INR

6.1 Details related to the Payees <Payees> 1..1

6.2 Details related to the Payee <Payee> 1..1

6.2.1 Address of the Payee Addr 1..1 rohit.patekar@sbi

6.2.2 Name of the Payee Name 1..1

6.2.3 Unique identifier for each transaction inside a file including Payee and payee

seqNum 1..1 1

6.2.4 Type of the Payee Type 1..1 PERSON

6.2.5 Merchant Classification Code -MCC

Code 1..1 4814

6.3 Information related to the Payee <Payee.Info> 1..1

6.4 Payee Identity Is mandatory for “collect” and optional for “pay”

<Payee.Info.Identity> 1..1

6.4.1 Type of the identifier type 1..1 ACCOUNT

6.4.2 Name as per the identifier verifiedName 1..1 Rohit Patekar

6.4.3. Id Id 1.1 8392389838

6.5 Rating of the payee <Rating> 0..1

6.5.1 Payee is whitelisted or not verifiedAddress 1..1 TRUE

Page 18: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS v1.0

15/10/2015 Page 18 of 122

Index Message Item <XML Tag> Occurrence Sample Value

6.6 Only one entity is allowed for a payee

<Payee.Ac> 1..1

6.6.1 Type of the address addrType 1..1 ACCOUNT

6.7 Details related to Payee Address <Payee.Ac.Detail> 1..n

6.7.1 Name of the property name 1..n ACTYPE

6.7.2 Value of the property value 1..n SAVINGS

6.7.3 Name of the property name 1..n IFSC

6.7.4 Value of the property value 1..n SBIN0288100

6.7.5 Name of the property name 1..n ACNUM

6.7.6 Value of the property value 1..n 5678892001828

1.7 RespPay_NPCI_DEBIT_REQ_RES(PSP1 to UPI)

<upi:RespPay xmlns:upi="http://npci.org/upi/schema/"> <Head ver="1.0" ts="2015-02-16T22:02:54+05:30" orgId="400002" msgId="NENSVVR4QOS7X1UGPY7JGUV424PL9T2C3QM"/> <Txn id="8ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM" note="Restaurant Bill " refId=““ refUrl=““ ts="2015-02-16T22:02:35+05:30" type="DEBIT"> <RiskScores> <Score provider="psp2" type="TXNRISK" value="00030"/> <Score provider="npci" type="TXNRISK" value="00030"/> </RiskScores> </Txn> <Resp reqMsgId="HENSVVR4QZS7X1UGPY7JGUV444PL9Z2C3QZ" result="SUCCESS" errCode=""> <Ref type="PAYER" seqNum="1" addr="zeeshan.khan@hdfc" settAmount="4000"

settCurrency="INR" acNum ="2678892001828" approvalNum="9399389827" respCode="00"/>

<Ref type="PAYEE" seqNum="1" addr="rohit.patekar@sbi" settAmount="4000" settCurrency="INR" acNum="5678892001828" approvalNum="" respCode=""/> </Resp> </upi:RespPay>

Index Message Item <XML Tag> Occurrence Sample Value

1.1 API Name <RespPay> 1..1 RespPay

1.1.1 API Schema namespace xmlns 1..1 upi="http://npci.org/upi/schema/

2.1 Header for the message <Head> 1..1

2.1.1 Version of the API ver 1..1 1.0

2.1.2 Time of request from the creator of the message

ts 1..1 2015-02-16T22:02:48+05:30

2.1.3 Organization id that created the message

orgId 1..1 400002

2.1.4 Message identifier-used to correlate between request and response

msgId 1..1 NENSVVR4QOS7X1UGPY7JGUV424PL9T2C3QM

3.1 Transaction information, Carried throughout the system, visible to all parties

<Txn> 1..1

Page 19: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS v1.0

15/10/2015 Page 19 of 122

Index Message Item <XML Tag> Occurrence Sample Value

3.1.1 Unique Identifier of the transaction across all entities created by the originator

id 1..1 8ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM

3.1.2 Description of the transaction(which will be printed on Pass book)

note 1..1 Restaurant Bill

3.1.3 Consumer reference number to identify (like Loan number, etc.)

refId 1..1

3.1.4 URL for the transaction refUrl 1..1

3.1.5 Transaction origination time by the creator of the message

ts 1..1 2015-02-16T22:02:35+05:30

3.1.6 Type of the Transaction type 1..1 CREDIT

3.2 Risk Score related to the transaction and the entities

<Txn.RiskScores> 0..1

3.3 Risk Score related to the transaction and the entities

<Txn.RiskScores.Score>

0..1

3.3.1 Entity providing the risk score provider 1..1 psp1

3.3.2 Type of risk type 1..1 TXNRISK

3.3.3 Value of risk evaluation ranging from 0 (No Risk) to 100 (Maximum Risk)

value 1..1 00030

3.4 Response <Resp> 1..1

3.4.1 Request Message identifier reqMsgId 1..1 HENSVVR4QZS7X1UGPY7JGUV444PL9Z2C3QM

3.4.2 Result of the transaction result 1..1 SUCCESS

3.4..3 Error code if failed errCode 1..1

3.5 Response Reference <Ref> 1..n

3.5.1 Customer type type 1..1 PAYER

3.5.2 Sequence Number seqNum 1..1 1

3.5.3 Payment address addr 1..1 zeeshan.khan@hdfc

3.5.4 Settlement Amount settAmount 1..1 4000

3.5.5 Settlement Currency settCurrency 1..1 INR

3.5.6 Approval Reference Number approvalNum 1..1 9399389827

3.5.7 Response code respCode 1..1 00

1.8 ReqPay_NPCI_CREDIT_REQ(UPI to PSP2)

<upi:ReqPay xmlns:upi="http://npci.org/upi/schema/"> <Head ver="1.0" ts="2015-02-16T22:02:54+05:30" orgId="400001" msgId="HENSVVR4QZS7X1UGPY7JGUV444PL9Z2C3QM"/> <Meta> <Tag name="PAYREQSTART" value="2015-02-16T22:02:00+05:30"/> <Tag name="PAYREQEND" value="2015-02-16T22:02:35+05:30"/> </Meta> <Txn id="8ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM" note="Restaurant Bill " refId="" refUrl="" ts="2015-02-16T22:02:35+05:30" type="CREDIT" orgTxnId=""> <RiskScores> <Score provider="psp1" type="TXNRISK" value="00030"/> <Score provider="npci" type="TXNRISK" value="00030"/> </RiskScores> </Txn> <Payer addr="zeeshan.khan@hdfc" name="Zeeshan Khan" seqNum="1" type="PERSON" code="4814"> <Info>

Page 20: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS v1.0

15/10/2015 Page 20 of 122

<Identity type="ACCOUNT" verifiedName="Zeeshan Khan" id="7389923983430"/> <Rating verifiedAddress="TRUE"/> </Info> <Device> <Tag name="MOBILE" value="+91.99999.00000"/> <Tag name="GEOCODE" value="288177"/> <Tag name="LOCATION" value="Mumbai,Maharashtra" /> <Tag name="IP" value="124.170.23.22"/> <Tag name="TYPE" value="mob"/> <Tag name="ID" value="750c6be243f1c4b5c9912b95a5742fc5"/> #device advertising id <Tag name="OS" value="android"/> <Tag name="APP" value="NPCIAPP"/> <Tag name="CAPABILITY" value="5200000200010004000639292929292"/> </Device> <Ac addrType="ACCOUNT"> <Detail name="ACTYPE" value="SAVINGS"/> <Detail name="IFSC" value="HDFC0288100"/> <Detail name="ACNUM" value="2678892001828"/> </Ac> <Creds> <Cred type="PreApproved" subType="NA"> <Data> base-64 encoded</Data> #data includes respCode and approvalRef RES|A12345 </Cred> </Creds> <Amount value="4000" curr="INR"> </Amount> </Payer> <Payees> <Payee addr="rohit.patekar@sbi" name="Rohit Patekar" seqNum="1" type="PERSON" code="4814">#mcc has to be populated <Info> <Identity type="ACCOUNT" verifiedName="Rohit Patekar" id="8392389838"/> <Rating verifiedAddress="TRUE"/> </Info> <Ac addrType="ACCOUNT"> <Detail name="IFSC" value="SBIN0288100"/> <Detail name="ACTYPE" value="SAVINGS"/> <Detail name="ACNUM" value="5678892001828"/> </Ac> <Amount value="4000" curr="INR"> </Amount> </Payee> </Payees> </upi:ReqPay>

Index Message Item <XML Tag> Occurrence Sample Value

1.1 API Name <upi> 1..1 ReqPay

1.1.1 API Schema namespace xmlns 1..1 upi="http://npci.org/upi/schema/

2.1 Header for the message <Head> 1..1

2.1.1 Version of the API ver 1..1 1.0

2.1.2 Time of request from the creator of the message

ts 1..1 2015-02-16T22:02:35+05:30

2.1.3 Organization id that created the message

orgId 1..1 400001

Page 21: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS v1.0

15/10/2015 Page 21 of 122

Index Message Item <XML Tag> Occurrence Sample Value

2.1.4 Message identifier-used to correlate between request and response

msgId 1..1 HENSVVR4QZS7X1UGPY7JGUV444PL9Z2C3QM

3.1 Meta data primarily for analytics purposes

<Meta> 0..1

3.2 Meta data primarily for analytics purposes

<Meta.Tag> 0..1

3.2.1 Name of the property name 1..n PAYREQSTART

3.2.2 Value of the property value 1..n 2015-02-16T22:02:00+05:30

4.1 Transaction information, Carried throughout the system, visible to all parties

<Txn> 1..1

4.1.1 Unique Identifier of the transaction across all entities, created by the originator

id 1..1 8ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM

4.1.2 Description of the transaction(which will be printed on Pass book)

note 1..1 Restaurant Bill

4.1.3 Consumer reference number to identify (like Loan number, etc.)

refId 1..1

4.1.4 URL for the transaction refUrl 1..1

4.1.5 Transaction origination time by the creator of the message

ts 1..1 2015-02-16T22:02:35+05:30

4.1.6 Type of the Transaction type 1..1 CREDIT

4.1.7 Original transaction ID when reversal/Refund has to be done

orgTxnId 1..1

4.2 Risk Score related to the transaction and the entities

<Txn.RiskScores> 0..1

4.3 Risk Score related to the transaction and the entities

<Txn.RiskScores.Score> 0..1

4.3.1 Entity providing the risk score provider 1..1 psp1

4.3.2 Type of risk type 1..1 TXNRISK

4.3.3 Value of risk evaluation ranging from 0 (No Risk) to 100 (Maximum Risk)

value 1..1 00030

5.1 Details related to the Payer <Payer> 1..1

5.1.1 Address of the Payer addr 1..1 zeeshan.khan@hdfc

5.1.2 Name of the Payer name 1..1 Zeeshan Khan

5.1.3 Unique identifier for each transaction inside a file including payer and payee

seqNum 1..1 1

5.1.4 Type of the Payer type 1..1 PERSON

5.1.5 Merchant Classification Code -MCC

code 1..1 4814

5.2 Information related to the Payer <Payer.Info> 1..1

5.3 Payer Identity Is mandatory for “collect” and optional for “pay”

<Payer.Info.Identity> 1..1

5.3.1 Type of the identifier type 1..1 ACCOUNT

5.3.2 Name as per the identifier verifiedName 1..1 Zeeshan Khan

Page 22: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS v1.0

15/10/2015 Page 22 of 122

Index Message Item <XML Tag> Occurrence Sample Value

5.3.3. Id Id 1.1 7389923983430

5.4 Rating of the payer <Rating> 0..1

5.4.1 Payer is whitelisted or not verifiedAddress 1..1 TRUE

5.5 Details of Device from which the transaction was initiated

<Payer.Device> 1..1

5.6 Device Tag <Payer.Device.Tag> 1..n

5.6.1 Name of the property name 1..n MOBILE

5.6.2 Value of the property value 1..n +91.99999.00000

5.7 Only one entity is allowed for a payer

<Payer.Ac> 1..1

5.7.1 Type of the address addrType 1..1 ACCOUNT

5.8 Details related to Payer Address <Payer.Ac.Detail> 1..n

5.8.1 Name of the property name 1..n ACTYPE

5.8.2 Value of the property value 1..n SAVINGS

5.8.3 Name of the property name 1..n IFSC

5.8.4 Value of the property value 1..n HDFC0288100

5.8.5 Name of the property name 1..n ACNUM

5.8.6 Value of the property value 1..n 2678892001828

5.9 Information related to Payer Credentials

<Payer.Creds> 1..1

5.10 Credentials are used to authenticate the request

<Payer.Creds.Cred> 1..1

5.10.1 Type of financial instrument used for authentication

Type 1..1 PreApproved

5.10.2 Subtype of Financial instrument used for authentication

subtype 1.1 NA

5.11 base-64 encoded/encrypted authentication data

<Payer.Creds.Cred.Data> 1..1 Base 64 encoded value of RES|A12345

5.12 Information related to the amounts in the transaction

<Payer.Amount> 1..1

5.12.1 Transaction amount Value 1..1 4000

5.12.2 Currency of the transaction Curr 1..1 INR

6.1 Details related to the Payees <Payees> 1..1

6.2 Details related to the Payee <Payee> 1..1

6.2.1 Address of the Payee Addr 1..1 rohit.patekar@sbi

6.2.2 Name of the Payee Name 1..1

6.2.3 Unique identifier for each transaction inside a file including Payee and payee

seqNum 1..1 1

6.2.4 Type of the Payee Type 1..1 PERSON

6.2.5 Merchant Classification Code -MCC

Code 1..1 4814

6.3 Information related to the Payee <Payee.Info> 1..1

6.4 Payee Identity Is mandatory for “collect” and optional for “pay”

<Payee.Info.Identity> 1..1

6.4.1 Type of the identifier type 1..1 ACCOUNT

6.4.2 Name as per the identifier verifiedName 1..1 Rohit Patekar

Page 23: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS v1.0

15/10/2015 Page 23 of 122

Index Message Item <XML Tag> Occurrence Sample Value

6.4.3. Id Id 1.1 8392389838

6.5 Rating of the payee <Rating> 0..1

6.5.1 Payee is whitelisted or not verifiedAddress 1..1 TRUE

6.6 Only one entity is allowed for a payee

<Payee.Ac> 1..1

6.6.1 Type of the address addrType 1..1 ACCOUNT

6.7 Details related to Payee Address <Payee.Ac.Detail> 1..n

6.7.1 Name of the property name 1..n ACTYPE

6.7.2 Value of the property value 1..n SAVINGS

6.7.3 Name of the property name 1..n IFSC

6.7.4 Value of the property value 1..n SBIN0288100

6.7.5 Name of the property name 1..n ACNUM

6.7.6 Value of the property value 1..n 5678892001828

1.9 RespPay_NPCI_CREDIT_REQ_RES(PSP2 to UPI)

<upi:RespPay xmlns:upi="http://npci.org/upi/schema/"> <Head ver="1.0" ts="2015-02-16T22:02:56+05:30" orgId="400003" msgId="NENSVVR4QOS7X1UGPY7JGUV424PL9T2C3QM"/> <Txn id="8ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM" note="Restaurant Bill " refId=““ refUrl=““ ts="2015-02-16T22:02:35+05:30" type="CREDIT"> <RiskScores> <Score provider="psp2" type="TXNRISK" value="00030"/> <Score provider="npci" type="TXNRISK" value="00030"/> </RiskScores> </Txn> <Resp reqMsgId="HENSVVR4QZS7X1UGPY7JGUV444PL9Z2C3QM" result="SUCCESS" errCode=""> <Ref type="PAYER" seqNum="1" addr="zeeshan.khan@hdfc" settAmount="4000"

settCurrency="INR" acNum ="2678892001828" approvalNum="9399389827" respCode="00"/>

<Ref type="PAYEE" seqNum="1" addr="rohit.patekar@sbi" settAmount="4000" settCurrency="INR" acNum="5678892001828" approvalNum="7786787865" respCode="00"/>

</Resp> </upi:RespPay>

Index Message Item <XML Tag> Occurrence Sample Value

1.1 API Name <RespPay> 1..1 RespPay

1.1.1 API Schema namespace xmlns 1..1 upi="http://npci.org/upi/schema/

2.1 Header for the message <Head> 1..1

2.1.1 Version of the API ver 1..1 1.0

2.1.2 Time of request from the creator of the message

ts 1..1 2015-02-16T22:02:48+05:30

2.1.3 Organization id that created the message

orgId 1..1 400002

2.1.4 Message identifier-used to correlate between request and response

msgId 1..1 NENSVVR4QOS7X1UGPY7JGUV424PL9T2C3QM

Page 24: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS v1.0

15/10/2015 Page 24 of 122

Index Message Item <XML Tag> Occurrence Sample Value

3.1 Transaction information, Carried throughout the system, visible to all parties

<Txn> 1..1

3.1.1 Unique Identifier of the transaction across all entities created by the originator

id 1..1 8ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM

3.1.2 Description of the transaction(which will be printed on Pass book)

note 1..1 Restaurant Bill

3.1.3 Consumer reference number to identify (like Loan number, etc.)

refId 1..1

3.1.4 URL for the transaction refUrl 1..1

3.1.5 Transaction origination time by the creator of the message

ts 1..1 2015-02-16T22:02:35+05:30

3.1.6 Type of the Transaction type 1..1 CREDIT

3.2 Risk Score related to the transaction and the entities

<Txn.RiskScores> 0..1

3.3 Risk Score related to the transaction and the entities

<Txn.RiskScores.Score>

0..1

3.3.1 Entity providing the risk score provider 1..1 psp1

3.3.2 Type of risk type 1..1 TXNRISK

3.3.3 Value of risk evaluation ranging from 0 (No Risk) to 100 (Maximum Risk)

value 1..1 00030

3.4 Response <Resp> 1..1

3.4.1 Request Message identifier reqMsgId 1..1 HENSVVR4QZS7X1UGPY7JGUV444PL9Z2C3QM

3.4.2 Result of the transaction result 1..1 SUCCESS

3.4..3 Error code if failed errCode 1..1

3.5 Response Reference <Ref> 1..n

3.5.1 Customer type type 1..1 PAYER

3.5.2 Sequence Number seqNum 1..1 1

3.5.3 Payment address addr 1..1 zeeshan.khan@hdfc

3.5.4 Settlement Amount settAmount 1..1 4000

3.5.5 Settlement Currency settCurrency 1..1 INR

3.5.6 Approval Reference Number approvalNum 1..1 9399389827

3.5.7 Response code respCode 1..1 00

1.10 RespPay(UPI to PSP1)

<upi:RespPay xmlns:upi="http://npci.org/upi/schema/"> <Head ver="1.0" ts="2015-02-16T22:02:59+05:30" orgId="400001" msgId="NENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM"/> <Txn id="8ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM" note="Restaurant Bill " refId=““ refUrl=““ ts="2015-02-16T22:02:35+05:30" type="PAY"> <RiskScores> <Score provider="psp2" type="TXNRISK" value="00030"/> <Score provider="npci" type="TXNRISK" value="00030"/> </RiskScores> </Txn> <Resp reqMsgId="HENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM" result="SUCCESS" errCode="">

Page 25: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS v1.0

15/10/2015 Page 25 of 122

<Ref type="PAYER" seqNum="1" addr="zeeshan.khan@hdfc" settAmount="4000" settCurrency="INR" approvalNum="9399389827" respCode="00"/> <Ref type="PAYEE" seqNum="1" addr="rohit.patekar@sbi" settAmount="4000" settCurrency="INR" approvalNum="7786787865" respCode="00"/> </Resp> </upi:RespPay>

Index Message Item <XML Tag> Occurrence Sample Value

1.1 API Name <RespPay> 1..1 RespPay

1.1.1 API Schema namespace xmlns 1..1 upi="http://npci.org/upi/schema/

2.1 Header for the message <Head> 1..1

2.1.1 Version of the API ver 1..1 1.0

2.1.2 Time of request from the creator of the message

ts 1..1 2015-02-16T22:02:48+05:30

2.1.3 Organization id that created the message

orgId 1..1 400001

2.1.4 Message identifier-used to correlate between request and response

msgId 1..1 NENSVVR4QOS7X1UGPY7JGUV424PL9T2C3QM

3.1 Transaction information, Carried throughout the system, visible to all parties

<Txn> 1..1

3.1.1 Unique Identifier of the transaction across all entities created by the originator

id 1..1 8ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM

3.1.2 Description of the transaction(which will be printed on Pass book)

note 1..1 Restaurant Bill

3.1.3 Consumer reference number to identify (like Loan number, etc.)

refId 1..1

3.1.4 URL for the transaction refUrl 1..1

3.1.5 Transaction origination time by the creator of the message

ts 1..1 2015-02-16T22:02:35+05:30

3.1.6 Type of the Transaction type 1..1 PAY

3.2 Risk Score related to the transaction and the entities

<Txn.RiskScores> 0..1

3.3 Risk Score related to the transaction and the entities

<Txn.RiskScores.Score>

0..1

3.3.1 Entity providing the risk score provider 1..1 psp1

3.3.2 Type of risk type 1..1 TXNRISK

3.3.3 Value of risk evaluation ranging from 0 (No Risk) to 100 (Maximum Risk)

value 1..1 00030

3.4 Response <Resp> 1..1

3.4.1 Request Message identifier reqMsgId 1..1 HENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM

3.4.2 Result of the transaction result 1..1 SUCCESS

3.4..3 Error code if failed errCode 1..1

3.5 Response Reference <Ref> 1..n

3.5.1 Customer type type 1..1 PAYER

3.5.2 Sequence Number seqNum 1..1 1

3.5.3 Payment address addr 1..1 zeeshan.khan@hdfc

3.5.4 Settlement Amount settAmount 1..1 4000

3.5.5 Settlement Currency settCurrency 1..1 INR

Page 26: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS v1.0

15/10/2015 Page 26 of 122

Index Message Item <XML Tag> Occurrence Sample Value

3.5.6 Approval Reference Number approvalNum 1..1 9399389827

3.5.7 Response code respCode 1..1 00

Page 27: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS v1.0

15/10/2015 Page 27 of 122

1.11 ReqTxnConfirmation(UPI to PSP2)

<upi:ReqTxnConfirmation xmlns:upi="http://npci.org/upi/schema/"> <Head ver="1.0" ts="2015-02-16T22:03:00+05:30" orgId="400001" msgId="HPDSFVC2QOS7X1UGPY2JGUV454YC8T2C6QM"/> <Txn id="8ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM" note="Restaurant Bill" refId=““ refUrl=““ ts="2015-02-16T22:02:35+05:30" type="TxnConfirmation" orgTxnId="HPDSFVC2QOS7X1UGPY2JGUV458PL8T2C6QM"/> <TxnConfirmation note="Restaurant Bill" orgStatus="SUCCESS" orgErrCode=”” type="PAY" orgTxnId="HPDSFVC2QOS7X1UGPY2JGUV458PL8T2C6QM" />

</upi:ReqTxnConfirmation>

1.12 RespTxnConfirmation(PSP2 to UPI)

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

<Head ver="1.0" ts="2015-02-16T22:03:01+05:30" orgId="400003" msgId="HPDSFVC2ZOS7X1UGPY2JGUV494ZC8T2C6QM"/> <Txn id="HPDSFVC2QOS7X1UGPY2JGUV458PL8T2C6QM" note="Restaurant Bill" refId=““ refUrl=““ ts="2015-02-16T22:02:35+05:30" type="TxnConfirmation" orgTxnId="HPDSFVC2QOS7X1UGPY2JGUV458PL8T2C6QM" /> <Resp reqMsgId="HPDSFVC2QOS7X1UGPY2JGUV454YL8T2C6QM" result="SUCCESS" errCode=""/>

</upi:RespTxnConfirmation>

Page 28: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS v1.0

15/10/2015 Page 28 of 122

CASE 2

TWO PARTY MODEL – Collect Request [Payer PSP & Remitter Bank are one entity

and Payee PSP & Beneficiary Bank are also one entity]

2.1 Flow:

1. Customer sends a Collect Request by entering the Virtual Address of the Payer

customer.

2. Payee PSP sends the ReqPay message to UPI

3. UPI sends the ReqAuthDetails to the respective Payer PSP 4. Payer PSP sends a notification to the Payer customer for authorization.

Customer enters the PIN & confirms the payment. Payer PSP sends the RespAuthDetails message to UPI

5. UPI sends the debit request to Payer PSP. 6. Payer PSP debits the customer account and sends response back to UPI. 7. UPI sends a Credit Request to Beneficiary Bank 8. Beneficiary Bank credits the customer’s account and responds successful

credit to UPI 9. UPI sends the RespPay message to Payee PSP 10. UPI Sends the ReqTxnConfirmation to Payer PSP. 11. Payee PSP sends the confirmation to the customer.

Page 29: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS v1.0

15/10/2015 Page 29 of 122

2.2 ReqPay(PSP1 to UPI)

<upi:ReqPay xmlns:upi="http://npci.org/upi/schema/"> <Head ver="1.0" ts="2015-02-16T22:02:35+05:30" orgId="400002" msgId="HDNSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM"/> <Meta> <Tag name="PAYREQSTART" value="2015-02-16T22:02:00+05:30"/> <Tag name="PAYREQEND" value="2015-02-16T22:02:35+05:30"/> </Meta> <Txn id="9ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM" note="Your taxi trip Bill " refId="" refUrl="" ts="2015-02-16T22:02:35+05:30" type="Collect" orgTxnId=""> <RiskScores> <Score provider="psp1" type="TXNRISK" value="00030"/> </RiskScores> <Rules> <Rule name="EXPIREAFTER" value="10080"/> <! Payment request will expire in 7 days (7*24*60 minutes) > </Rules> </Txn> <Payer addr="rohit.patekar@sbi" name="" seqNum="1" type="" code=""> </Payer> <Payees> <Payee addr="zeeshan@hdfc" name="Zeeshan Khan" seqNum="1" type="PERSON" code="4814"> <Info> <Identity type="ACCOUNT" verifiedName="Zeeshan Khan" id="7389923983430"/> <Rating verifiedAddress="TRUE"/> </Info> <Device> <Tag name="MOBILE" value="+91.99999.00000"/> <Tag name="GEOCODE" value="288177"/> <Tag name="LOCATION" value="Mumbai,Maharashtra" /> <Tag name="IP" value="124.170.23.22"/> <Tag name="TYPE" value="mob"/> <Tag name="ID" value="750c6be243f1c4b5c9912b95a5742fc5"/> <Tag name="OS" value="android"/> <Tag name="APP" value="NPCIAPP"/> <Tag name="CAPABILITY" value="5200000200010004000639292929292"/> </Device> <Ac addrType="ACCOUNT"> <Detail name="IFSC" value="HDFC0288100"/> <Detail name="ACTYPE" value="SAVINGS"/> <Detail name="ACNUM" value="2678892001828"/> </Ac> <Amount value="4000" curr="INR"> </Amount> </Payee> </Payees> </upi:ReqPay>

Index Message Item <XML Tag> Occurrence Sample Value

1.1 API Name <upi> 1..1 ReqPay

1.1.1 API Schema namespace Xmlns 1..1 upi="http://npci.org/upi/schema/

2.1 Header for the message <Head> 1..1

2.1.1 Version of the API Ver 1..1 1.0

Page 30: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS v1.0

15/10/2015 Page 30 of 122

Index Message Item <XML Tag> Occurrence Sample Value

2.1.2 Time of request from the creator of the message

Ts 1..1 2015-02-16T22:02:35+05:30

2.1.3 Organization id that created the message

orgId 1..1 400002

2.1.4 Message identifier-used to correlate between request and response

msgId 1..1 HDNSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM

3.1 Meta data primarily for analytics purposes

<Meta> 0..1

3.2 Meta data primarily for analytics purposes

<Meta.Tag> 0..1

3.2.1 Name of the property name 1..n PAYREQSTART

3.2.2 Value of the property value 1..n 2015-02-16T22:02:00+05:30

4.1 Transaction information, Carried throughout the system, visible to all parties

<Txn> 1..1

4.1.1 Unique Identifier of the transaction across all entities, created by the originator

id 1..1 9ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM

4.1.2 Description of the transaction(which will be printed on Pass book)

note 1..1 Your taxi trip Bill

4.1.3 Consumer reference number to identify (like Loan number, etc.)

refId 1..1

4.1.4 URL for the transaction refUrl 1..1

4.1.5 Transaction origination time by the creator of the message

ts 1..1 2015-02-16T22:02:35+05:30

4.1.6 Type of the Transaction type 1..1 Collect

4.1.7 Original transaction ID when reversal/Refund has to be done

orgTxnId 1..1

4.2 Risk Score related to the transaction and the entities

<Txn.RiskScores> 0..1

4.3 Risk Score related to the transaction and the entities

<Txn.RiskScores.Score>

0..1

4.3.1 Entity providing the risk score provider 1..1 psp1

4.3.2 Type of risk type 1..1 TXNRISK

4.3.3 Value of risk evaluation ranging from 0 (No Risk) to 100 (Maximum Risk)

value 1..1 00030

4.4 Rules that govern the payment <Txn.Rules> 0..1

4.5 Rule for the transaction <Txn.Rules.Rule> 0..n

4.5.1 Name of the property name 1..n EXPIREAFTER

4.5.2 Value of the property value 1..n 10080

5.1 Details related to the Payer <Payer> 1..1

5.1.1 Address of the Payer addr 1..1 rohit.patekar@sbi

Page 31: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS v1.0

15/10/2015 Page 31 of 122

Index Message Item <XML Tag> Occurrence Sample Value

5.1.2 Name of the Payer name 1..1

5.1.3 Unique identifier for each transaction inside a file including payer and payee

seqNum 1..1

5.1.4 Type of the Payer type 1..1

5.1.5 Merchant Classification Code -MCC

code 1..1

6.1 Details related to the Payees <Payees> 1..1

6.2 Details related to the Payee <Payee> 1..1

6.2.1 Address of the Payee addr 1..1 zeeshan@hdfc

6.2.2 Name of the Payee name 1..1 Zeeshan Khan

6.2.3 Unique identifier for each transaction inside a file including Payee and payee

seqNum 1..1 1

6.2.4 Type of the Payee type 1..1 PERSON

6.2.5 Merchant Classification Code –MCC

code 1..1 4814

7.1 Information related to the Payee <Payee.Info> 1..1

7.2 Payee Identity Is mandatory for “collect” and optional for “pay”

<Payee.Info.Identity>

1..1

7.2.1 Type of the identifier type 1..1 ACCOUNT

7.2.2 Name as per the identifier verifiedName 1..1 Zeeshan Khan

7.3.3 Id Id 1.1 7389923983430

7.4 Rating of the payee <Rating> 0..1

7.4.1 Payer is whitelisted or not verifiedAddress 1..1 TRUE

7.5 Details of Device from which the transaction was initiated

<Payee.Device> 1..1

7.6 Device Tag <Payee.Device.Tag>

1..n

7.6.1 Name of the property name 1..n MOBILE

7.6.2 Value of the property value 1..n +91.99999.00000

7.7 Only one entity is allowed for a payee

<Payee.Ac> 1..1

7.7.1 Type of the address addrType 1..1 ACCOUNT

7.8 Details related to Payee Address <Payee.Ac.Detail> 1..n

7.8.1 Name of the property name 1..n ACTYPE

7.8.2 Value of the property value 1..n SAVINGS

7.8.3 Name of the property name 1..n IFSC

7.8.4 Value of the property value 1..n HDFC0288100

7.8.5 Name of the property name 1..n ACNUM

7.8.6 Value of the property value 1..n 2678892001828

7.9 Information related to the amounts in the transaction

<Payee.Amount> 1..1

7.9.1 Transaction amount value 1..1 4000

7.9.2 Currency of the transaction curr 1..1 INR

Page 32: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS v1.0

15/10/2015 Page 32 of 122

2.3 MSG_ACK(to be send for every message)

<?xml version='1.0' encoding='UTF-8' standalone='no'?><Ack api='UPI' err=''/>

2.4 ReqAuthDetails(UPI to PSP2)

<upi:ReqAuthDetails xmlns:upi="http://npci.org/upi/schema/"> <Head ver="1.0" ts="2015-02-16T22:02:40+05:30" orgId="400001" msgId="NPNSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM"/> <Txn id="9ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM" note="Your Taxi trip Bill " refId=““ refUrl=““ ts="2015-02-16T22:02:35+05:30" type="Collect"> <RiskScores> <Score provider="psp1" type="TXNRISK" value="00030"/> <Score provider="NPCI" type="TXNRISK" value="00030"/> </RiskScores> <Rules> <Rule name="EXPIREAFTER" value="10080"/> <!--Payment request will expire in 7 days (7*24*60 minutes)--> </Rules> </Txn> <Payer addr="rohit.patekar@sbi" name="" seqNum="1" type="" code=""> </Payer> <Payees> <Payee seqNum="1" addr="zeeshan.khan@hdfc" name="Zeeshan Khan" type="PERSON" code="4814"> <Info> <Identity type="ACCOUNT" verifiedName="Zeeshan Khan" id="7389923983430"/> <Rating verifiedAddress="TRUE"/> </Info> <Amount value="4000" curr="INR"> </Amount> </Payee> </Payees> </upi:ReqAuthDetails>

Index Message Item <XML Tag> Occurrence Sample Value

1.1 API Name <upi> 1..1 ReqAuthDetails

1.1.1 API Schema namespace xmlns 1..1 upi="http://npci.org/upi/schema/

2.1 Header for the message <Head> 1..1

2.1.1 Version of the API ver 1..1 1.0

2.1.2 Time of request from the creator of the message

ts 1..1 2015-02-16T22:02:35+05:30

2.1.3 Organization id that created the message

orgId 1..1 400001

2.1.4 Message identifier-used to correlate between request and response

msgId 1..1 NPNSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM

3.1.1 Unique Identifier of the transaction across all entities, created by the originator

id 1..1 9ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM

3.1.2 Description of the transaction(which will be printed on Pass book)

note 1..1 Your taxi trip Bill

Page 33: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS v1.0

15/10/2015 Page 33 of 122

Index Message Item <XML Tag> Occurrence Sample Value

3.1.3 Consumer reference number to identify (like Loan number, etc.)

ref 1..1

3.1.4 Transaction origination time by the creator of the message

ts 1..1 2015-02-16T22:02:35+05:30

3.1.5 Type of the Transaction type 1..1 Collect

3.2 Risk Score related to the transaction and the entities

<Txn.RiskScores> 0..1

3.3 Risk Score related to the transaction and the entities

<Txn.RiskScores.Score>

0..1

3.3.1 Entity providing the risk score provider 1..1 psp1

3.3.2 Type of risk type 1..1 TXNRISK

3.3.3 Value of risk evaluation ranging from 0 (No Risk) to 100 (Maximum Risk)

value 1..1 00030

3.4 Rules that govern the payment <Txn.Rules> 0..1

3.5 Rule for the transaction <Txn.Rules.Rule> 0..n

3.5.1 Name of the property Name 1..n EXPIREAFTER

3.5.2 Value of the property Value 1..n 10080

4.1 Details related to the Payer <Payer> 1..1

4.1.1 Address of the Payer Addr 1..1 rohit.patekar@sbi

4.1.2 Name of the Payer Name 1..1

4.1.3 Unique identifier for each transaction inside a file including payer and payee

seqNum 1..1 1

4.1.4 Type of the Payer Type 1..1

4.1.5 Merchant Classification Code -MCC

Code 1..1

5.1 Details related to the Payees <Payees> 1..1

5.2 Details related to the Payee <Payee> 1..1

5.2.1 Address of the Payee Addr 1..1 zeeshan@hdfc

5.2.2 Name of the Payee Name 1..1 Zeeshan Khan

5.2.3 Unique identifier for each transaction inside a file including Payee and payee

seqNum 1..1 1

5.2.4 Type of the Payee Type 1..1 PERSON

5.2.5 Merchant Classification Code –MCC

Code 1..1 4814

6.1 Information related to the Payee <Payee.Info> 1..1

6.2 Payee Identity Is mandatory for “collect” and optional for “pay”

<Payee.Info.Identity> 1..1

6.2.1 Type of the identifier Type 1..1 ACCOUNT

6.2.2 Name as per the identifier verifiedName 1..1 Zeeshan Khan

6.3.3 Id Id 1.1 7389923983430

Page 34: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS v1.0

15/10/2015 Page 34 of 122

Index Message Item <XML Tag> Occurrence Sample Value

6.4 Rating of the payee <Rating> 0..1

6.4.1 Payer is whitelisted or not verifiedAddress 1..1 TRUE

6.5 Information related to the amounts in the transaction

<Payee.Amount> 1..1

6.5.1 Transaction amount Value 1..1 4000

6.5.2 Currency of the transaction Curr 1..1 INR

2.5 RespAuthDetails(PSP2 to UPI)

<upi:RespAuthDetails xmlns:upi="http://npci.org/upi/schema/"> <Head ver="1.0" ts="2015-02-16T22:02:48+05:30" orgId="400003" msgId="SBNSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM"/> <Resp reqMsgId="NPNSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM" result="SUCCESS" errCode=""/> <Txn id="9ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM " note="Your Taxi trip Bill" refId=““ refUrl=““ ts="2015-02-16T22:02:35+05:30" type="Collect"> <RiskScores> <Score provider="psp2" type="TXNRISK" value="00030"/> <Score provider="NPCI" type="TXNRISK" value="00030"/> </RiskScores> </Txn> <Payer addr="rohit.patekar@sbi" name="Rohit Patekar" seqNum="1" type="PERSON" code="4814"> <Info> <Identity type="ACCOUNT" verifiedName="rohit.patekar@sbi" id="8392389838"/> <Rating verifiedAddress="TRUE"/> </Info> <Device> <Tag name="MOBILE" value="+91.99999.88888"/> <Tag name="GEOCODE" value="288177"/> <Tag name="LOCATION" value="Mumbai,Maharashtra" /> <Tag name="IP" value="124.170.23.24"/> <Tag name="TYPE" value="mob"/> <Tag name="ID" value="900c6be276f1c4b5c9912b95a5742fc5"/> <Tag name="OS" value="android"/> <Tag name="APP" value="NPCIAPP"/> <Tag name="CAPABILITY" value="5200000200010004000639292929292"/> </Device> <Ac addrType="ACCOUNT"> <Detail name="IFSC" value="SBIN0288100"/> <Detail name="ACTYPE" value="SAVINGS"/> <Detail name="ACNUM" value="5678892001828"/> </Ac> <Creds> <Cred type="PIN" subType="MPIN">

<Data code="" ki=""> base-64 encoded and encrypted</Data> #data includes [base 64 encoded]<Transaction Id><delimiter><Common library version><delimiter><Captured credential><delimiter><Transaction amount><delimiter><Random number>[encrypted] ,"|" to be used as delimiter

</Cred> <Amount value="4000" curr="INR"> </Amount> </Payer> <Payees>

Page 35: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS v1.0

15/10/2015 Page 35 of 122

<Payee addr="Zeeshan.khan@hdfc" name="Zeeshan Khan" seqNum="1" type="PERSON" code="4814"> <Info> <Identity type="ACCOUNT" verifiedName="Zeeshan Khan" id="7389923983430"/> <Rating verifiedAddress="TRUE"/> </Info> <Amount value="4000" curr="INR"> </Amount> </Payee> </Payees> </upi:RespAuthDetails>

Index Message Item <XML Tag> Occurrence Sample Value

1.1 API Name <RespAuthDetails> 1..1 RespAuthDetails

1.1.1 API Schema namespace xmlns 1..1 upi="http://npci.org/upi/schema/

2.1 Header for the message <Head> 1..1

2.1.1 Version of the API ver 1..1 1.0

2.1.2 Time of request from the creator of the message

ts 1..1 2015-02-16T22:02:48+05:30

2.1.3 Organization id that created the message

orgId 1..1 400003

2.1.4 Message identifier-used to correlate between request and response

msgId 1..1 SBNSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM

3.1 Response <Resp> 1..1

3.1.1 Request Message identifier reqMsgId 1..1 NPNSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM

3.1.2 Result of the transaction result 1..1 SUCCESS

3.1.3 Error code if failed errCode 1..1

4.1 Transaction information, Carried throughout the system, visible to all parties

<Txn> 1..1

4.1.1 Unique Identifier of the transaction across all entities created by the originator

id 1..1 1524104355706

4.1.2 Description of the transaction(which will be printed on Pass book)

note 1..1 Your taxi trip Bill

4.1.3 Consumer reference number to identify (like Loan number, etc.)

ref 1..1

4.1.4 Transaction origination time by the creator of the message

ts 1..1 2015-02-16T22:02:35+05:30

4.1.5 Type of the Transaction type 1..1 Collect

4.2 Risk Score related to the transaction and the entities

<Txn.RiskScores> 0..1

4.3 Risk Score related to the transaction and the entities

<Txn.RiskScores.Score>

0..1

4.3.1 Entity providing the risk score provider 1..1 Psp2

4.3.2 Type of risk type 1..1 TXNRISK

4.3.3 Value of risk evaluation ranging from 0 (No Risk) to 100 (Maximum Risk)

value 1..1 00030

5.1 Details related to the Payer <Payer> 1..1

5.1.1 Address of the Payer addr 1..1 rohit.patekar@sbi

5.1.2 Name of the Payer name 1..1 Rohit Patekar

Page 36: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS v1.0

15/10/2015 Page 36 of 122

Index Message Item <XML Tag> Occurrence Sample Value

5.1.3 Unique identifier for each transaction inside a file including payer and payee

seqNum 1..1 1

5.1.4 Type of the Payer type 1..1 PERSON

5.1.5 Merchant Classification Code -MCC code 1..1 4814

5.2 Information related to the Payer <Payer.Info> 1..1

5.3 Payer Identity is mandatory for “collect” and optional for “pay”

<Payer.Info.Identity> 1..1

5.3.1 Type of the identifier type 1..1 ACCOUNT

5.3.2 Name as per the identifier verifiedName 1..1 rohit.patekar@sbi 5.3.3 Id Id 1.1 8392389838

5.4 Rating of the payer <Payer.Info.Rating> 0..1

5.4.1 Payer is whitelisted or not verifiedAddress 1..1 TRUE

5.5 Details of Device from which the transaction was initiated

<Payer.Device> 1..1

5.6 Device Tag <Payer.Device.Tag> 1..n

5.6.1 Name of the property name 1..n MOBILE

5.6.2 Value of the property value 1..n +91.99999.00000

5.7 Only one entity is allowed for a payer <Payer.Ac> 1..1

5.7.1 Type of the address addrType 1..1 ACCOUNT

5.8 Details related to Payer Address <Payer.Ac.Detail> 1..n

5.8.1 Name of the property name 1..n ACTYPE

5.8.2 Value of the property value 1..n SAVINGS

5.8.3 Name of the property name 1..n IFSC

5.8.4 Value of the property value 1..n SBIN0288100

5.8.5 Name of the property name 1..n ACNUM

5.8.6 Value of the property value 1..n 5678892001828

5.9 Information related to Payer Credentials

<Payer.Creds> 1..1

5.10 Credentials are used to authenticate the request

<Payer.Creds.Cred> 1..1

5.10.1 Type of financial instrument used for authentication

type 1..1 PreApproved

5.10.2 Subtype of Financial instrument used for authentication

subtype 1.1 NA

5.11 base-64 encoded/encrypted authentication data

<Payer.Creds.Cred.Data>

1..1 Base 64 encoded value of RES|A12345

5.12 Information related to the amounts in the transaction

<Payer.Amount> 1..1

5.12.1 Transaction amount value 1..1 4000

5.12.2 Currency of the transaction curr 1..1 INR

6.2 Details related to the Payee <Payee> 1..1

6.2.1 Address of the Payee addr 1..1 Zeeshan.khan@hdfc

6.2.2 Name of the Payee name 1..1 Zeeshan Khan

6.2.3 Unique identifier for each transaction inside a file including Payee and payee

seqNum 1..1 1

6.2.4 Type of the Payee type 1..1 PERSON

6.2.5 Merchant Classification Code -MCC code 1..1 4814

6.3 Information related to the Payee <Payee.Info> 1..1

6.4 Payee Identity <Payee.Info.Identity> 1..1

6.4.1 Type of the identifier type 1..1 ACCOUNT

6.4.2 Name as per the identifier verifiedName 1..1 Zeeshan Khan

Page 37: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS v1.0

15/10/2015 Page 37 of 122

Index Message Item <XML Tag> Occurrence Sample Value

6.4.3 Id Id 1.1 7389923983430

6.5 Information related to the amounts in the transaction

<Payee.Amount> 1..1

6.5.1 Transaction amount value 1..1 4000

6.5.2 Currency of the transaction curr 1..1 INR

2.6 ReqPay_NPCI_DEBIT_REQ(UPI to PSP2)

<upi:ReqPay xmlns:upi="http://npci.org/upi/schema/"> <Head ver="1.0" ts="2015-02-16T22:02:48+05:30" orgId="400001" msgId="HENSVVR4QZS7X1UGCY7JGUV444PL9Z2C3QM"/> <Meta> <Tag name="PAYREQSTART" value="2015-02-16T22:02:00+05:30"/> <Tag name="PAYREQEND" value="2015-02-16T22:02:35+05:30"/> </Meta> <Txn id="9ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM" note="Restaurant Bill " refId="" refUrl="" ts="2015-02-16T22:02:35+05:30" type="DEBIT" orgTxnId=""> <RiskScores> <Score provider="psp1" type="TXNRISK" value="00030"/> <Score provider="npci" type="TXNRISK" value="00030"/> </RiskScores> </Txn> <Payer addr="zeeshan.khan@hdfc" name="Zeeshan Khan" seqNum="1" type="PERSON" code="4814"> <Info> <Identity type="ACCOUNT" verifiedName="Zeeshan Khan" id="7389923983430"/> <Rating verifiedAddress="TRUE"/> </Info> <Device> <Tag name="MOBILE" value="+91.99999.00000"/> <Tag name="GEOCODE" value="288177"/> <Tag name="LOCATION" value="Mumbai,Maharashtra" /> <Tag name="IP" value="124.170.23.22"/> <Tag name="TYPE" value="mob"/> <Tag name="ID" value="750c6be243f1c4b5c9912b95a5742fc5"/> #device advertising id <Tag name="OS" value="android"/> <Tag name="APP" value="NPCIAPP"/> <Tag name="CAPABILITY" value="5200000200010004000639292929292"/> </Device> <Ac addrType="ACCOUNT"> <Detail name="ACTYPE" value="SAVINGS"/> <Detail name="IFSC" value="HDFC0288100"/> <Detail name="ACNUM" value="2678892001828"/> </Ac> <Creds> <Cred type="PIN" subType="MPIN">

<Data code="" ki=""> base-64 encoded and encrypted</Data> #data includes [<Transaction Id><delimiter><Common library version><delimiter><Captured credential><delimiter><Transaction amount><delimiter><Random number> ,"|" to be used as delimiter

</Cred>

</Creds> <Amount value="4000" curr="INR">

Page 38: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS v1.0

15/10/2015 Page 38 of 122

</Amount> </Payer> <Payees> <Payee addr="rohit.patekar@sbi" name="Rohit Patekar" seqNum="1" type="PERSON" code="4814">#mcc has to be populated <Info> <Identity type="ACCOUNT" verifiedName="Rohit Patekar" id="8392389838"/> <Rating verifiedAddress="TRUE"/> </Info> <Ac addrType="ACCOUNT"> <Detail name="IFSC" value="SBIN0288100"/> <Detail name="ACTYPE" value="SAVINGS"/> <Detail name="ACNUM" value="5678892001828"/> </Ac> <Amount value="4000" curr="INR"> </Amount> </Payee> </Payees> </upi:ReqPay>

Index Message Item <XML Tag> Occurrence Sample Value

1.1 API Name <upi> 1..1 ReqPay

1.1.1 API Schema namespace xmlns 1..1 upi="http://npci.org/upi/schema/

2.1 Header for the message <Head> 1..1

2.1.1 Version of the API ver 1..1 1.0

2.1.2 Time of request from the creator of the message

ts 1..1 2015-02-16T22:02:35+05:30

2.1.3 Organization id that created the message

orgId 1..1 400001

2.1.4 Message identifier-used to correlate between request and response

msgId 1..1 HENSVVR4QZS7X1UGPY7JGUV444PL9Z2C3QM

3.1 Meta data primarily for analytics purposes

<Meta> 0..1

3.2 Meta data primarily for analytics purposes

<Meta.Tag> 0..1

3.2.1 Name of the property name 1..n PAYREQSTART

3.2.2 Value of the property value 1..n 2015-02-16T22:02:00+05:30

4.1 Transaction information, Carried throughout the system, visible to all parties

<Txn> 1..1

4.1.1 Unique Identifier of the transaction across all entities, created by the originator

id 1..1 8ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM

4.1.2 Description of the transaction(which will be printed on Pass book)

note 1..1 Restaurant Bill

4.1.3 Consumer reference number to identify (like Loan number, etc.)

refId 1..1

4.1.4 URL for the transaction refUrl 1..1

4.1.5 Transaction origination time by the creator of the message

ts 1..1 2015-02-16T22:02:35+05:30

4.1.6 Type of the Transaction type 1..1 CREDIT

Page 39: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS v1.0

15/10/2015 Page 39 of 122

Index Message Item <XML Tag> Occurrence Sample Value

4.1.7 Original transaction ID when reversal/Refund has to be done

orgTxnId 1..1

4.2 Risk Score related to the transaction and the entities

<Txn.RiskScores> 0..1

4.3 Risk Score related to the transaction and the entities

<Txn.RiskScores.Score> 0..1

4.3.1 Entity providing the risk score provider 1..1 psp1

4.3.2 Type of risk type 1..1 TXNRISK

4.3.3 Value of risk evaluation ranging from 0 (No Risk) to 100 (Maximum Risk)

value 1..1 00030

5.1 Details related to the Payer <Payer> 1..1

5.1.1 Address of the Payer addr 1..1 zeeshan.khan@hdfc

5.1.2 Name of the Payer name 1..1 Zeeshan Khan

5.1.3 Unique identifier for each transaction inside a file including payer and payee

seqNum 1..1 1

5.1.4 Type of the Payer type 1..1 PERSON

5.1.5 Merchant Classification Code -MCC

code 1..1 4814

5.2 Information related to the Payer <Payer.Info> 1..1

5.3 Payer Identity Is mandatory for “collect” and optional for “pay”

<Payer.Info.Identity> 1..1

5.3.1 Type of the identifier type 1..1 ACCOUNT

5.3.2 Name as per the identifier verifiedName 1..1 Zeeshan Khan

5.3.3. Id Id 1.1 7389923983430

5.4 Rating of the payer <Rating> 0..1

5.4.1 Payer is whitelisted or not verifiedAddress 1..1 TRUE

5.5 Details of Device from which the transaction was initiated

<Payer.Device> 1..1

5.6 Device Tag <Payer.Device.Tag> 1..n

5.6.1 Name of the property name 1..n MOBILE

5.6.2 Value of the property value 1..n +91.99999.00000

5.7 Only one entity is allowed for a payer

<Payer.Ac> 1..1

5.7.1 Type of the address addrType 1..1 ACCOUNT

5.8 Details related to Payer Address <Payer.Ac.Detail> 1..n

5.8.1 Name of the property name 1..n ACTYPE

5.8.2 Value of the property value 1..n SAVINGS

5.8.3 Name of the property name 1..n IFSC

5.8.4 Value of the property value 1..n HDFC0288100

5.8.5 Name of the property name 1..n ACNUM

5.8.6 Value of the property value 1..n 2678892001828

5.9 Information related to Payer Credentials

<Payer.Creds> 1..1

5.10 Credentials are used to authenticate the request

<Payer.Creds.Cred> 1..1

Page 40: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS v1.0

15/10/2015 Page 40 of 122

Index Message Item <XML Tag> Occurrence Sample Value

5.10.1 Type of financial instrument used for authentication

Type 1..1 PreApproved

5.10.2 Subtype of Financial instrument used for authentication

subtype 1.1 NA

5.11 base-64 encoded/encrypted authentication data

<Payer.Creds.Cred.Data> 1..1 Base 64 encoded value of RES|A12345

5.12 Information related to the amounts in the transaction

<Payer.Amount> 1..1

5.12.1 Transaction amount Value 1..1 4000

5.12.2 Currency of the transaction Curr 1..1 INR

6.1 Details related to the Payees <Payees> 1..1

6.2 Details related to the Payee <Payee> 1..1

6.2.1 Address of the Payee Addr 1..1 rohit.patekar@sbi

6.2.2 Name of the Payee Name 1..1

6.2.3 Unique identifier for each transaction inside a file including Payee and payee

seqNum 1..1 1

6.2.4 Type of the Payee Type 1..1 PERSON

6.2.5 Merchant Classification Code -MCC

Code 1..1 4814

6.3 Information related to the Payee <Payee.Info> 1..1

6.4 Payee Identity Is mandatory for “collect” and optional for “pay”

<Payee.Info.Identity> 1..1

6.4.1 Type of the identifier type 1..1 ACCOUNT

6.4.2 Name as per the identifier verifiedName 1..1 Rohit Patekar

6.4.3. Id Id 1.1 8392389838

6.5 Rating of the payee <Rating> 0..1

6.5.1 Payee is whitelisted or not verifiedAddress 1..1 TRUE

6.6 Only one entity is allowed for a payee

<Payee.Ac> 1..1

6.6.1 Type of the address addrType 1..1 ACCOUNT

6.7 Details related to Payee Address <Payee.Ac.Detail> 1..n

6.7.1 Name of the property name 1..n ACTYPE

6.7.2 Value of the property value 1..n SAVINGS

6.7.3 Name of the property name 1..n IFSC

6.7.4 Value of the property value 1..n SBIN0288100

6.7.5 Name of the property name 1..n ACNUM

6.7.6 Value of the property value 1..n 5678892001828

2.7 RespPay_NPCI_DEBIT_REQ_RES(PSP2 to UPI)

<upi:RespPay xmlns:upi="http://npci.org/upi/schema/"> <Head ver="1.0" ts="2015-02-16T22:02:54+05:30" orgId="400003" msgId="NENSVVR4QOS7X1UGPY7JGUV424PL9T2C3QN"/> <Txn id="9ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM" note="Restaurant Bill "

Page 41: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS v1.0

15/10/2015 Page 41 of 122

refId=““ refUrl=““ ts="2015-02-16T22:02:35+05:30" type="DEBIT"> <RiskScores> <Score provider="psp2" type="TXNRISK" value="00030"/> <Score provider="npci" type="TXNRISK" value="00030"/> </RiskScores> </Txn> <Resp reqMsgId="HENSVVR4QZS7X1UGCY7JGUV444PL9Z2C3QM" result="SUCCESS" errCode=""> <Ref type="PAYER" seqNum="1" addr="zeeshan.khan@hdfc" settAmount="4000"

settCurrency="INR" acNum ="2678892001828"approvalNum="9399389827" respCode="00"/>

<Ref type="PAYEE" seqNum="1" addr="rohit.patekar@sbi" settAmount="4000" settCurrency="INR" acNum="5678892001828" approvalNum="7786787865" respCode="00"/>

</Resp> </upi:RespPay>

Index Message Item <XML Tag> Occurrence Sample Value

1.1 API Name <RespPay> 1..1 RespPay

1.1.1 API Schema namespace xmlns 1..1 upi="http://npci.org/upi/schema/

2.1 Header for the message <Head> 1..1

2.1.1 Version of the API ver 1..1 1.0

2.1.2 Time of request from the creator of the message

ts 1..1 2015-02-16T22:02:48+05:30

2.1.3 Organization id that created the message

orgId 1..1 400002

2.1.4 Message identifier-used to correlate between request and response

msgId 1..1 NENSVVR4QOS7X1UGPY7JGUV424PL9T2C3QM

3.1 Transaction information, Carried throughout the system, visible to all parties

<Txn> 1..1

3.1.1 Unique Identifier of the transaction across all entities created by the originator

id 1..1 8ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM

3.1.2 Description of the transaction(which will be printed on Pass book)

note 1..1 Restaurant Bill

3.1.3 Consumer reference number to identify (like Loan number, etc.)

refId 1..1

3.1.4 URL for the transaction refUrl 1..1

3.1.5 Transaction origination time by the creator of the message

ts 1..1 2015-02-16T22:02:35+05:30

3.1.6 Type of the Transaction type 1..1 CREDIT

3.2 Risk Score related to the transaction and the entities

<Txn.RiskScores> 0..1

3.3 Risk Score related to the transaction and the entities

<Txn.RiskScores.Score>

0..1

3.3.1 Entity providing the risk score provider 1..1 psp1

3.3.2 Type of risk type 1..1 TXNRISK

3.3.3 Value of risk evaluation ranging from 0 (No Risk) to 100 (Maximum Risk)

value 1..1 00030

3.4 Response <Resp> 1..1

3.4.1 Request Message identifier reqMsgId 1..1 HENSVVR4QZS7X1UGPY7JGUV444PL9Z2C3QM

3.4.2 Result of the transaction result 1..1 SUCCESS

Page 42: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS v1.0

15/10/2015 Page 42 of 122

Index Message Item <XML Tag> Occurrence Sample Value

3.4..3 Error code if failed errCode 1..1

3.5 Response Reference <Ref> 1..n

3.5.1 Customer type type 1..1 PAYER

3.5.2 Sequence Number seqNum 1..1 1

3.5.3 Payment address addr 1..1 zeeshan.khan@hdfc

3.5.4 Settlement Amount settAmount 1..1 4000

3.5.5 Settlement Currency settCurrency 1..1 INR

3.5.6 Approval Reference Number approvalNum 1..1 9399389827

3.5.7 Response code respCode 1..1 00

2.8 ReqPay_NPCI_CREDIT_REQ(UPI to PSP2)

<upi:ReqPay xmlns:upi="http://npci.org/upi/schema/"> <Head ver="1.0" ts="2015-02-16T22:02:35+05:30" orgId="400001" msgId="HENSVVR4QZS7X1UGPY7JGUV424PL9Z2C3QM"/> <Meta> <Tag name="PAYREQSTART" value="2015-02-16T22:02:00+05:30"/> <Tag name="PAYREQEND" value="2015-02-16T22:02:35+05:30"/> </Meta> <Txn id="9ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM" note="Your Taxi trip Bill " refId="" refUrl="" ts="2015-02-16T22:02:35+05:30" type="CREDIT" orgTxnId=""> <RiskScores> <Score provider="psp1" type="TXNRISK" value="00030"/> <Score provider="npci" type="TXNRISK" value="00030"/> </RiskScores> </Txn> <Payer addr="rohit.patekar@sbi" name="Rohit Patekar" seqNum="1" type="PERSON" code="4814"> <Info> <Identity type="ACCOUNT" verifiedName="rohit.patekar@sbi" id="8392389838"/> <Rating verifiedAddress="TRUE"/> </Info> <Device> <Tag name="MOBILE" value="+91.99999.88888"/> <Tag name="GEOCODE" value="288177"/> <Tag name="LOCATION" value="Mumbai,Maharashtra" /> <Tag name="IP" value="124.170.23.24"/> <Tag name="TYPE" value="mob"/> <Tag name="ID" value="900c6be276f1c4b5c9912b95a5742fc5"/> <Tag name="OS" value="android"/> <Tag name="APP" value="NPCIAPP"/> <Tag name="CAPABILITY" value="5200000200010004000639292929292"/> </Device> <Ac addrType="ACCOUNT"> <Detail name="IFSC" value="SBIN0288100"/> <Detail name="ACTYPE" value="SAVINGS"/> <Detail name="ACNUM" value="5678892001828"/> </Ac> <Creds>

Page 43: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS v1.0

15/10/2015 Page 43 of 122

<Cred type="PreApproved" subType="NA"> <Data> base-64 encoded</Data> #data includes respCode and approvalRef RES|A12345 </Cred> </Creds> <Amount value="4000" curr="INR"> </Amount> </Payer> <Payees> <Payee seqNum="2" addr="zeeshan.khan@hdfc" name="Zeeshan Khan" type="PERSON" code="4814"> <Info> <Identity type="ACCOUNT" verifiedName="Zeeshan Khan" id="7389923983430"/> <Rating verifiedAddress="TRUE"/> </Info> <Ac addrType="ACCOUNT"> <Detail name="IFSC" value="HDFC0288100"/> <Detail name="ACTYPE" value="SAVINGS"/> <Detail name="ACNUM" value="2678892001828"/> </Ac> <Amount value="4000" curr="INR"> </Amount> </Payee> </Payees> </upi:ReqPay>

Index Message Item <XML Tag> Occurrence Sample Value

1.1 API Name <upi> 1..1 ReqPay

1.1.1 API Schema namespace Xmlns 1..1 upi="http://npci.org/upi/schema/

2.1 Header for the message <Head> 1..1

2.1.1 Version of the API Ver 1..1 1.0

2.1.2 Time of request from the creator of the message

Ts 1..1 2015-02-16T22:02:35+05:30

2.1.3 Organization id that created the message

orgId 1..1 400001

2.1.4 Message identifier-used to correlate between request and response

msgId 1..1 HENSVVR4QZS7X1UGPY7JGUV424PL9Z2C3QM

3.1 Meta data primarily for analytics purposes

<Meta> 0..1

3.2 Meta data primarily for analytics purposes

<Meta.Tag> 0..1

3.2.1 Name of the property Name 1..n PAYREQSTART

3.2.2 Value of the property Value 1..n 2015-02-16T22:02:00+05:30

4.1 Transaction information, Carried throughout the system, visible to all parties

<Txn> 1..1

4.1.1 Unique Identifier of the transaction across all entities, created by the originator

Id 1..1 9ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM

Page 44: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS v1.0

15/10/2015 Page 44 of 122

Index Message Item <XML Tag> Occurrence Sample Value

4.1.2 Description of the transaction(which will be printed on Pass book)

Note 1..1 Your taxi trip Bill

4.1.3 Consumer reference number to identify (like Loan number, etc.)

refId 1..1

4.1.4 URL for the transaction refUrl 1..1

4.1.5 Transaction origination time by the creator of the message

Ts 1..1 2015-02-16T22:02:35+05:30

4.1.6 Type of the Transaction Type 1..1 CREDIT

4.1.7 Original transaction ID when reversal/Refund has to be done

orgTxnId 1..1

4.2 Risk Score related to the transaction and the entities

<Txn.RiskScores> 0..1

4.3 Risk Score related to the transaction and the entities

<Txn.RiskScores.Score>

0..1

4.3.1 Entity providing the risk score provider 1..1 psp1

4.3.2 Type of risk Type 1..1 TXNRISK

4.3.3 Value of risk evaluation ranging from 0 (No Risk) to 100 (Maximum Risk)

Value 1..1 00030

5.1 Details related to the Payer <Payer> 1..1

5.1.1 Address of the Payer Addr 1..1 rohit.patekar@sbi

5.1.2 Name of the Payer Name 1..1 Rohit Patekar

5.1.3 Unique identifier for each transaction inside a file including payer and payee

seqNum 1..1 1

5.1.4 Type of the Payer Type 1..1 PERSON

5.1.5 Merchant Classification Code -MCC

Code 1..1 4814

5.2 Information related to the Payer <Payer.Info> 1..1

5.3 Payer Identity Is mandatory for “collect” and optional for “pay”

<Payer.Info.Identity>

1..1

5.3.1 Type of the identifier type 1..1 ACCOUNT

5.3.2 Name as per the identifier verifiedName 1..1 rohit.patekar@sbi

5.3.3. Id Id 1.1 8392389838

5.4 Rating of the payer <Rating> 0..1

5.4.1 Payer is whitelisted or not verifiedAddress 1..1 TRUE

5.5 Details of Device from which the transaction was initiated

<Payer.Device> 1..1

5.6 Device Tag <Payer.Device.Tag> 1..n

5.6.1 Name of the property Name 1..n MOBILE

5.6.2 Value of the property Value 1..n +91.99999.00000

5.7 Only one entity is allowed for a payer

<Payer.Ac> 1..1

5.7.1 Type of the address addrType 1..1 ACCOUNT

5.8 Details related to Payer Address <Payer.Ac.Detail> 1..n

5.8.1 Name of the property name 1..n ACTYPE

Page 45: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS v1.0

15/10/2015 Page 45 of 122

Index Message Item <XML Tag> Occurrence Sample Value

5.8.2 Value of the property value 1..n SAVINGS

5.8.3 Name of the property name 1..n IFSC

5.8.4 Value of the property value 1..n SBIN0288100

5.8.5 Name of the property name 1..n ACNUM

5.8.6 Value of the property value 1..n 5678892001828

5.9 Information related to Payer Credentials

<Payer.Creds> 1..1

5.10 Credentials are used to authenticate the request

<Payer.Creds.Cred> 1..1

5.10.1 Type of financial instrument used for authentication

type 1..1 PreApproved

5.10.2 Subtype of Financial instrument used for authentication

subtype 1.1 NA

5.11 base-64 encoded/encrypted authentication data

<Payer.Creds.Cred.Data>

1..1 Base 64 encoded value of RES|A12345

5.12 Information related to the amounts in the transaction

<Payer.Amount> 1..1

5.12.1 Transaction amount value 1..1 4000

5.12.2 Currency of the transaction curr 1..1 INR

5.13 Information if the debit is already authorized

0.1

5.13.1 Response Code respCode 1.1 00

5.13.2 Approval Reference approvalRef 1.1 7786787860

6.1 Details related to the Payees <Payees> 1..1

6.2 Details related to the Payee <Payee> 1..1

6.2.1 Address of the Payee addr 1..1 Zeeshan.khan@hdfc

6.2.2 Name of the Payee name 1..1 Zeeshan Khan

6.2.3 Unique identifier for each transaction inside a file including Payee and payee

seqNum 1..1 1

6.2.4 Type of the Payee type 1..1 PERSON

6.2.5 Merchant Classification Code –MCC

code 1..1 4814

7.1 Information related to the Payee <Payee.Info> 1..1

7.2 Payee Identity Is mandatory for “collect” and optional for “pay”

<Payee.Info.Identity>

1..1

7.2.1 Type of the identifier type 1..1 ACCOUNT

7.2.2 Name as per the identifier verifiedName 1..1 Zeeshan Khan

7.3.3 Id Id 1.1 7389923983430

7.4 Rating of the payee <Rating> 0..1

7.4.1 Payer is whitelisted or not verifiedAddress 1..1 TRUE

7.5 Only one entity is allowed for a payee

<Payee.Ac> 1..1

7.5.1 Type of the address addrType 1..1 ACCOUNT

7.6 Details related to Payee Address <Payee.Ac.Detail> 1..n

7.6.1 Name of the property name 1..n ACTYPE

7.6.2 Value of the property value 1..n SAVINGS

Page 46: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS v1.0

15/10/2015 Page 46 of 122

Index Message Item <XML Tag> Occurrence Sample Value

7.6.3 Name of the property name 1..n IFSC

7.6.4 Value of the property value 1..n HDFC0288100

7.6.5 Name of the property name 1..n ACNUM

7.6.6 Value of the property value 1..n 2678892001828

7.7 Information related to the amounts in the transaction

<Payee.Amount> 1..1

7.7.1 Transaction amount value 1..1 4000

7.7.2 Currency of the transaction curr 1..1 INR

2.9 RespPay_NPCI_CREDIT_REQ_RES(PSP2 to UPI)

<upi:RespPay xmlns:upi="http://npci.org/upi/schema/"> <Head ver="1.0" ts="2015-02-16T22:02:48+05:30" orgId="400002" msgId="NENSVVR4QOS7X1UGPY7JGUV424PL9T2C3QM"/> <Txn id="8ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM" note="Your Taxi trip Bill " refId=““ refUrl=““ ts="2015-02-16T22:02:35+05:30" type="CREDIT"> <RiskScores> <Score provider="psp2" type="TXNRISK" value="00030"/> <Score provider="npci" type="TXNRISK" value="00030"/> </RiskScores> </Txn> <Resp reqMsgId="HENSVVR4QZS7X1UGPY7JGUV424PL9Z2C3QM" result="SUCCESS" errCode=""> <Ref type="PAYEE" seqNum="1" addr="zeeshan.khan@hdfc" settAmount="4000"

settCurrency="INR" acNum ="2678892001828" approvalNum="9399389827" respCode="00"/>

<Ref type="PAYER" seqNum="1" addr="rohit.patekar@sbi" settAmount="4000" settCurrency="INR" acNum="5678892001828" approvalNum="7786787865" respCode="00"/>

</Resp> </upi:RespPay>

Index Message Item <XML Tag> Occurrence Sample Value

1.1 API Name <RespPay> 1..1 RespPay

1.1.1 API Schema namespace xmlns 1..1 upi="http://npci.org/upi/schema/

2.1 Header for the message <Head> 1..1

2.1.1 Version of the API ver 1..1 1.0

2.1.2 Time of request from the creator of the message

ts 1..1 2015-02-16T22:02:48+05:30

2.1.3 Organization id that created the message

orgId 1..1 400002

2.1.4 Message identifier-used to correlate between request and response

msgId 1..1 NENSVVR4QOS7X1UGPY7JGUV424PL9T2C3QM

3.1 Transaction information, Carried throughout the system, visible to all parties

<Txn> 1..1

3.1.1 Unique Identifier of the transaction across all entities created by the originator

id 1..1 8ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM

3.1.2 Description of the transaction(which will be printed on Pass book)

note 1..1 Your Taxi trip Billl

Page 47: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS v1.0

15/10/2015 Page 47 of 122

Index Message Item <XML Tag> Occurrence Sample Value

3.1.3 Consumer reference number to identify (like Loan number, etc.)

refId 1..1

3.1.4 URL for the transaction refUrl 1..1

3.1.5 Transaction origination time by the creator of the message

ts 1..1 2015-02-16T22:02:35+05:30

3.1.6 Type of the Transaction type 1..1 CREDIT

3.2 Risk Score related to the transaction and the entities

<Txn.RiskScores> 0..1

3.3 Risk Score related to the transaction and the entities

<Txn.RiskScores.Score>

0..1

3.3.1 Entity providing the risk score provider 1..1 Psp2

3.3.2 Type of risk type 1..1 TXNRISK

3.3.3 Value of risk evaluation ranging from 0 (No Risk) to 100 (Maximum Risk)

value 1..1 00030

3.4 Response <Resp> 1..1

3.4.1 Request Message identifier reqMsgId 1..1 HENSVVR4QZS7X1UGPY7JGUV424PL9Z2C3QM

3.4.2 Result of the transaction result 1..1 SUCCESS

3.4..3 Error code if failed errCode 1..1

3.5 Response Reference <Ref> 1..n

3.5.1 Customer type type 1..1 PAYEE

3.5.2 Sequence Number seqNum 1..1 1

3.5.3 Payment address addr 1..1 zeeshan.khan@hdfc

3.5.4 Settlement Amount settAmount 1..1 4000

3.5.5 Settlement Currency settCurrency 1..1 INR

3.5.6 Approval Reference Number approvalNum 1..1 9399389827

3.5.7 Response code respCode 1..1 00

2.10 RespPay(UPI to PSP1)

<upi:RespPay xmlns:upi="http://npci.org/upi/schema/"> <Head ver="1.0" ts="2015-02-16T22:02:52+05:30" orgId="400001" msgId="NPCSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM"/> <Txn id="9ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM" note="Your Taxi Trip Bill " refId=““ refUrl=““ ts="2015-02-16T22:02:35+05:30" type="Collect"> <RiskScores> <Score provider="psp2" type="TXNRISK" value="00030"/> <Score provider="npci" type="TXNRISK" value="00030"/> </RiskScores> </Txn> <Resp reqMsgId="HDNSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM" result="SUCCESS" errCode=""> <Ref type="PAYER" seqNum="1" addr="rohit.patekar@sbi" settAmount="4000" settCurrency="INR" approvalNum="9399389827" respCode="00"/> # this will indicate that debit has happened <Ref type="PAYEE" seqNum="1" addr="zeeshan.khan@hdfc" settAmount="4000" settCurrency="INR" approvalNum="" respCode=""/> # PAYEE PSP will do the credit and complete the transaction. </Resp> </upi:RespPay>

Index Message Item <XML Tag> Occurrence Sample Value

1.1 API Name <RespPay> 1..1 RespPay

Page 48: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS v1.0

15/10/2015 Page 48 of 122

Index Message Item <XML Tag> Occurrence Sample Value

1.1.1 API Schema namespace xmlns 1..1 upi="http://npci.org/upi/schema/

2.1 Header for the message <Head> 1..1

2.1.1 Version of the API ver 1..1 1.0

2.1.2 Time of request from the creator of the message

ts 1..1 2015-02-16T22:02:52+05:30

2.1.3 Organization id that created the message

orgId 1..1 400001

2.1.4 Message identifier-used to correlate between request and response

msgId 1..1 NPCSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM

3.1 Transaction information, Carried throughout the system, visible to all parties

<Txn> 1..1

3.1.1 Unique Identifier of the transaction across all entities created by the originator

id 1..1 9ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM

3.1.2 Description of the transaction(which will be printed on Pass book)

note 1..1 Your Taxi trip Bill

3.1.3 Consumer reference number to identify (like Loan number, etc.)

refId 1..1

3.1.4 URL for the transaction refUrl 1..1

3.1.5 Transaction origination time by the creator of the message

ts 1..1 2015-02-16T22:02:35+05:30

3.1.6 Type of the Transaction type 1..1 Collect

3.2 Risk Score related to the transaction and the entities

<Txn.RiskScores> 0..1

3.3 Risk Score related to the transaction and the entities

<Txn.RiskScores.Score>

0..1

3.3.1 Entity providing the risk score provider 1..1 Psp2

3.3.2 Type of risk type 1..1 TXNRISK

3.3.3 Value of risk evaluation ranging from 0 (No Risk) to 100 (Maximum Risk)

value 1..1 00030

3.4 Response <Resp> 1..1

3.4.1 Request Message identifier reqMsgId 1..1 HDNSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM

3.4.2 Result of the transaction result 1..1 SUCCESS

3.4..3 Error code if failed errCode 1..1

3.5 Response Reference <Ref> 1..n

3.5.1 Customer type type 1..1 PAYER

3.5.2 Sequence Number seqNum 1..1 1

3.5.3 Payment address addr 1..1 rohit.patekar@sbi

3.5.4 Settlement Amount settAmount 1..1 4000

3.5.5 Settlement Currency settCurrency 1..1 INR

3.5.6 Approval Reference Number approvalNum 1..1 9399389827

3.5.7 Response code respCode 1..1 00

Page 49: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS v1.0

15/10/2015 Page 49 of 122

2.11 ReqTxnConfirmation(UPI to PSP2)

<upi:ReqTxnConfirmation xmlns:upi="http://npci.org/upi/schema/"> <Head ver="1.0" ts="2015-02-16T22:03:00+05:30" orgId="400001" msgId="HPDSFVC2QOS7X1UGPY2JGUV454YC8T2C6QM"/> <Txn id="8ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM" note="Restaurant Bill" refId=““ refUrl=““ ts="2015-02-16T22:02:35+05:30" type="TxnConfirmation" orgTxnId="9ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM" /> <TxnConfirmation note="Restaurant Bill" orgStatus="SUCCESS" orgErrCode=”” type="COLLECT" orgTxnId="9ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM" />

</upi:ReqTxnConfirmation>

2.12 RespTxnConfirmation(PSP2 to UPI)

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

<Head ver="1.0" ts="2015-02-16T22:03:01+05:30" orgId="400003" msgId="HPDSFVC2ZOS7X1UGPY2JGUV494ZC8T2C6QM"/> <Txn id="HPDSFVC2QOS7X1UGPY2JGUV458PL8T2C6QM" note="Restaurant Bill" refId=““ refUrl=““ ts="2015-02-16T22:02:35+05:30" type="TxnConfirmation" orgTxnId="9ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM" /> <Resp reqMsgId="HPDSFVC2QOS7X1UGPY2JGUV454YL8T2C6QM" result="SUCCESS" errCode=""/>

</upi:RespTxnConfirmation>

Page 50: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS v1.0

15/10/2015 Page 50 of 122

CASE 3

Pay Request - Payer PSP & Remitter Banks are same entity and Payee PSP &

Beneficiary Bank are separate entities.

3.1 Flow:

1. Customer initiates a Pay request by entering the Virtual Address of the Payee customer and PIN

2. Payer PSP debits the customer’s account & sends the ReqPay message to UPI 3. UPI sends ReqAuthDetails message to the respective Payee PSP 4. Payee PSP identifies the Address and responds back with RespAuthDetails

message. 5. UPI sends ISO8583 message to IMPS system 6. IMPS sends a credit message to Beneficiary Bank 7. Beneficiary Bank credits the customer’s account and responds successful

credit to IMPS 8. IMPS system sends a successful credit notification to UPI system 9. UPI sends RespPay message to Payer PSP 10. UPI Sends ReqTxnConfimation to Payee PSP 11. Payer PSP sends a confirmation to the costumer

Page 51: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS v1.0

15/10/2015 Page 51 of 122

3.2 ReqPay(PSP1 to UPI)

<upi:ReqPay xmlns:upi="http://npci.org/upi/schema/"> <Head ver="1.0" ts="2015-02-16T22:02:35+05:30" orgId="400002" msgId="HENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM"/> <Meta> <Tag name="PAYREQSTART" value="2015-02-16T22:02:00+05:30"/> <Tag name="PAYREQEND" value="2015-02-16T22:02:35+05:30"/> </Meta> <Txn id="8ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM" note="Restaurant Bill " refId="" refUrl="" ts="2015-02-16T22:02:35+05:30" type="PAY" orgTxnId=""> <RiskScores> <Score provider="psp1" type="TXNRISK" value="00030"/> <Score provider="npci" type="TXNRISK" value="00030"/> </RiskScores> </Txn> <Payer addr="zeeshan.khan@hdfc" name="Zeeshan Khan" seqNum="1" type="PERSON" code="4814"> <Info> <Identity type="ACCOUNT" verifiedName="Zeeshan Khan" id="7389923983430"/> <Rating verifiedAddress="TRUE"/> </Info> <Device> <Tag name="MOBILE" value="+91.99999.00000"/> <Tag name="GEOCODE" value="288177"/> <Tag name="LOCATION" value="Mumbai,Maharashtra" /> <Tag name="IP" value="124.170.23.22"/> <Tag name="TYPE" value="mob"/> <Tag name="ID" value="750c6be243f1c4b5c9912b95a5742fc5"/> #device advertising id <Tag name="OS" value="android"/> <Tag name="APP" value="NPCIAPP"/> <Tag name="CAPABILITY" value="5200000200010004000639292929292"/> </Device> <Ac addrType="ACCOUNT"> <Detail name="ACTYPE" value="SAVINGS"/> <Detail name="IFSC" value="HDFC0288100"/> <Detail name="ACNUM" value="2678892001828"/> </Ac> <Creds> <Cred type="PreApproved" subType="NA"> <Data> base-64 encoded</Data> #data includes respCode and approvalRef RES|A12345 </Cred> </Creds> <Amount value="4000" curr="INR"> </Amount> </Payer> <Payees> <Payee addr="rohit.patekar@sbi" name="" seqNum="1" type="" code=""> </Payee> </Payees> </upi:ReqPay>

Index Message Item <XML Tag> Occurrence Sample Value

1.1 API Name <upi> 1..1 ReqPay

1.1.1 API Schema namespace xmlns 1..1 upi="http://npci.org/upi/schema/

2.1 Header for the message <Head> 1..1

Page 52: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS v1.0

15/10/2015 Page 52 of 122

Index Message Item <XML Tag> Occurrence Sample Value

2.1.1 Version of the API ver 1..1 1.0

2.1.2 Time of request from the creator of the message

ts 1..1 2015-02-16T22:02:35+05:30

2.1.3 Organization id that created the message

orgId 1..1 400002

2.1.4 Message identifier-used to correlate between request and response

msgId 1..1 HENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM

3.1 Meta data primarily for analytics purposes

<Meta> 0..1

3.2 Meta data primarily for analytics purposes

<Meta.Tag> 0..1

3.2.1 Name of the property name 1..n PAYREQSTART

3.2.2 Value of the property value 1..n 2015-02-16T22:02:00+05:30

4.1 Transaction information, Carried throughout the system, visible to all parties

<Txn> 1..1

4.1.1 Unique Identifier of the transaction across all entities, created by the originator

id 1..1 8ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM

4.1.2 Description of the transaction(which will be printed on Pass book)

note 1..1 Restaurant Bill

4.1.3 Consumer reference number to identify (like Loan number, etc.)

refId 1..1

4.1.4 URL for the transaction refUrl 1..1

4.1.5 Transaction origination time by the creator of the message

ts 1..1 2015-02-16T22:02:35+05:30

4.1.6 Type of the Transaction type 1..1 PAY

4.1.7 Original transaction ID when reversal/Refund has to be done

orgTxnId 1..1

4.2 Risk Score related to the transaction and the entities

<Txn.RiskScores> 0..1

4.3 Risk Score related to the transaction and the entities

<Txn.RiskScores.Score>

0..1

4.3.1 Entity providing the risk score provider 1..1 psp1

4.3.2 Type of risk type 1..1 TXNRISK

4.3.3 Value of risk evaluation ranging from 0 (No Risk) to 100 (Maximum Risk)

value 1..1 00030

5.1 Details related to the Payer <Payer> 1..1

5.1.1 Address of the Payer addr 1..1 zeeshan.khan@hdfc

5.1.2 Name of the Payer name 1..1 Zeeshan Khan

5.1.3 Unique identifier for each transaction inside a file including payer and payee

seqNum 1..1 1

5.1.4 Type of the Payer type 1..1 PERSON

5.1.5 Merchant Classification Code -MCC

code 1..1 4814

5.2 Information related to the Payer <Payer.Info> 1..1

Page 53: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS v1.0

15/10/2015 Page 53 of 122

Index Message Item <XML Tag> Occurrence Sample Value

5.3 Payer Identity Is mandatory for “collect” and optional for “pay”

<Payer.Info.Identity> 1..1

5.3.1 Type of the identifier type 1..1 ACCOUNT

5.3.2 Name as per the identifier verifiedName 1..1 Zeeshan Khan

5.3.3. Id Id 1.1 7389923983430

5.4 Rating of the payer <Rating> 0..1

5.4.1 Payer is whitelisted or not verifiedAddress 1..1 TRUE

5.5 Details of Device from which the transaction was initiated

<Payer.Device> 1..1

5.6 Device Tag <Payer.Device.Tag> 1..n

5.6.1 Name of the property name 1..n MOBILE

5.6.2 Value of the property value 1..n +91.99999.00000

5.7 Only one entity is allowed for a payer

<Payer.Ac> 1..1

5.7.1 Type of the address addrType 1..1 ACCOUNT

5.8 Details related to Payer Address <Payer.Ac.Detail> 1..n

5.8.1 Name of the property name 1..n ACTYPE

5.8.2 Value of the property value 1..n SAVINGS

5.8.3 Name of the property name 1..n IFSC

5.8.4 Value of the property value 1..n HDFC0288100

5.8.5 Name of the property name 1..n ACNUM

5.8.6 Value of the property value 1..n 2678892001828

5.9 Information related to Payer Credentials

<Payer.Creds> 1..1

5.10 Credentials are used to authenticate the request

<Payer.Creds.Cred> 1..1

5.10.1 Type of financial instrument used for authentication

type 1..1 PreApproved

5.10.2 Subtype of Financial instrument used for authentication

subtype 1.1 NA

5.11 base-64 encoded/encrypted authentication data

<Payer.Creds.Cred.Data>

1..1 Base 64 encoded value of RES|A12345

5.12 Information related to the amounts in the transaction

<Payer.Amount> 1..1

5.12.1 Transaction amount value 1..1 4000

5.12.2 Currency of the transaction curr 1..1 INR

6.1 Details related to the Payees <Payees> 1..1

6.2 Details related to the Payee <Payee> 1..1

6.2.1 Address of the Payee addr 1..1 rohit.patekar@sbi

6.2.2 Name of the Payee name 1..1

6.2.3 Unique identifier for each transaction inside a file including Payee and payee

seqNum 1..1 1

6.2.4 Type of the Payee type 1..1

6.2.5 Merchant Classification Code -MCC

code 1..1

Page 54: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS v1.0

15/10/2015 Page 54 of 122

3.3 MSG_ACK(to be send for every message)

<?xml version='1.0' encoding='UTF-8' standalone='no'?><Ack api='UPI' err=''/>

3.4 ReqAuthDetails(UPI to PSP2)

<upi:ReqAuthDetails xmlns:upi="http://npci.org/upi/schema/"> <Head ver="1.0" ts="2015-02-16T22:02:40+05:30" orgId="400001" msgId="NPNSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM"/> <Txn id="8ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM" note="Restaurant Bill " refId=““ refUrl=““ ts="2015-02-16T22:02:35+05:30" type="PAY"> <RiskScores> <Score provider="psp1" type="TXNRISK" value="00030"/> <Score provider="NPCI" type="TXNRISK" value="00030"/> </RiskScores> </Txn> <Payer addr="zeeshan.khan@hdfc" name="Zeeshan Khan" seqNum="1" type="PERSON" code="4814"> <Info> <Identity type="ACCOUNT" verifiedName="Zeeshan Khan" id="7389923983430"/> <Rating verifiedAddress="TRUE"/> </Info> <Amount value="4000" curr="INR"> </Amount> </Payer> <Payees> <Payee addr="rohit.patekar@sbi" name="" seqNum="1" type="" code=""> </Payee> </Payees> </upi:ReqAuthDetails>

Index Message Item <XML Tag> Occurrence Sample Value

1.1 API Name <ReqAuthDetails> 1..1 ReqAuthDetails

1.1.1 API Schema namespace xmlns 1..1 upi="http://npci.org/upi/schema

2.1 Header for the message <Head> 1..1

2.1.1 Version of the API ver 1..1 1.0

2.1.2 Time of request from the creator of the message

ts 1..1 2015-02-16T22:02:45+05:30

2.1.3 Organization id that created the message

orgId 1..1 400001

2.1.4 Message identifier-used to correlate between request and response

msgId 1..1 NPNSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM

3.1 Transaction information, Carried throughout the system, visible to all parties

<Txn> 1..1

3.1.1 Unique Identifier of the transaction across all entities created by the originator

id 1..1 8ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM

Page 55: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS v1.0

15/10/2015 Page 55 of 122

Index Message Item <XML Tag> Occurrence Sample Value

3.1.2 Description of the transaction(which will be printed on Pass book)

note 1..1 Restaurant Bill

3.1.3 Consumer reference number to identify (like Loan number, etc.)

ref 1..1

3.1.4 Transaction origination time by the creator of the message

ts 1..1 2015-02-16T22:02:35+05:30

3.1.5 Type of the Transaction type 1..1 PAY

3.2 Risk Score related to the transaction and the entities

<Txn.RiskScores> 0..1

3.3 Risk Score related to the transaction and the entities

<Txn.RiskScores.Score>

0..1

3.3.1 Entity providing the risk score provider 1..1 Psp1

3.3.2 Type of risk type 1..1 TXNRISK

3.3.3 Value of risk evaluation ranging from 0 (No Risk) to 100 (Maximum Risk)

value 1..1 00030

4.1 Details related to the Payer <Payer> 1..1

4.1.1 Address of the Payer addr 1..1 zeeshan.khan@hdfc

4.1.2 Name of the Payer name 1..1 Zeeshan Khan

4.1.3 Unique identifier for each transaction inside a file including payer and payee

seqNum 1..1 1

4.1.4 Type of the Payer type 1..1 PERSON

4.1.5 Merchant Classification Code -MCC

code 1..1 4814

4.2 Information related to the Payer <Payer.Info> 1..1

4.3 Payer Identity is mandatory for “collect” and optional for “pay”

<Payer.Info.Identity> 1..1

4.3.1 Type of the identifier type 1..1 ACCOUNT

4.3.2 Name as per the identifier verifiedName 1..1 Zeeshan Khan

4.3.3 Identifier Id 1.1 7389923983430

4.4 Rating of the payer <Payer.Info.Rating> 0..1

4.4.1 Payer is whitelisted or not verifiedAddress 1..1 TRUE

4.5 Information related to the amounts in the transaction

<Payer.Amount> 1..1

4.5.1 Transaction amount value 1..1 4000

4.5.2 Currency of the transaction curr 1..1 INR

5.1 Details related to the Payees <Payees> 1..1

5.2 Details related to the Payee <Payee> 1..1

5.2.1 Address of the Payee addr 1..1 rohit.patekar@sbi

5.2.2 Name of the Payee name 1..1

5.2.3 Unique identifier for each transaction inside a file including Payee and payee

seqNum 1..1 1

5.2.4 Type of the Payee type 1..1

5.2.5 Merchant Classification Code -MCC

code 1..1

Page 56: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS v1.0

15/10/2015 Page 56 of 122

3.5 RespAuthDetails(PSP2 to UPI)

<upi:RespAuthDetails xmlns:upi="http://npci.org/upi/schema/"> <Head ver="1.0" ts="2015-02-16T22:02:45+05:30" orgId="400003" msgId="SBNSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM"/> <Resp reqMsgId="NPNSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM" result="SUCCESS" errCode=""/> <Txn id="8ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM" note="Restaurant Bill " refId=““ refUrl=““ ts="2015-02-16T22:02:35+05:30" type="PAY"> <RiskScores> <Score provider="psp2" type="TXNRISK" value="00030"/> <Score provider="NPCI" type="TXNRISK" value="00030"/> </RiskScores> </Txn> <Payer addr="zeeshan.khan@hdfc" name="Zeeshan Khan" seqNum="1" type="PERSON" code="4814"> <Info> <Identity type="ACCOUNT" verifiedName="Zeeshan Khan" id="7389923983430"/> <Rating verifiedAddress="TRUE"/> </Info> <Amount value="4000" curr="INR"> </Amount> </Payer> <Payees> <Payee seqNum="2" addr="rohit.patekar@sbi" name="Rohit Patekar" type="PERSON" code="4814"> <Info> <Identity type="ACCOUNT" verifiedName="Rohit Patekar" id="8392389838"/> <Rating verifiedAddress="TRUE"/> </Info> <Ac addrType="ACCOUNT"> <Detail name="IFSC" value="SBI0288100"/> <Detail name="ACTYPE" value="SAVINGS"/> <Detail name="ACNUM" value="5678892001828"/> </Ac> <Amount value="4000" curr="INR"> </Amount> </Payee> </Payees> </upi:RespAuthDetails>

Index Message Item <XML Tag> Occurrence Sample Value

1.1 API Name <RespAuthDetails> 1..1 RespAuthDetails

1.1.1 API Schema namespace xmlns 1..1 upi="http://npci.org/upi/schema/

2.1 Header for the message <Head> 1..1

2.1.1 Version of the API ver 1..1 1.0

2.1.2 Time of request from the creator of the message

ts 1..1 2015-02-16T22:02:45+05:30

2.1.3 Organization id that created the message

orgId 1..1 400003

2.1.4 Message identifier-used to correlate between request and response

msgId 1..1 SBNSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM

3.1 Response <Resp> 1..1

3.1.1 Request Message identifier reqMsgId 1..1 NPNSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM

3.1.2 Result of the transaction result 1..1 SUCCESS

Page 57: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS v1.0

15/10/2015 Page 57 of 122

Index Message Item <XML Tag> Occurrence Sample Value

3.1.3 Error code if failed errCode 1..1

4.1 Transaction information, Carried throughout the system, visible to all parties

<Txn> 1..1

4.1.1 Unique Identifier of the transaction across all entities created by the originator

id 1..1 8ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM

4.1.2 Description of the transaction(which will be printed on Pass book)

note 1..1 Restaurant Bill

4.1.3 Consumer reference number to identify (like Loan number, etc.)

ref 1..1

4.1.4 Transaction origination time by the creator of the message

ts 1..1 2015-02-16T22:02:35+05:30

4.1.5 Type of the Transaction type 1..1 PAY

4.2 Risk Score related to the transaction and the entities

<Txn.RiskScores> 0..1

4.3 Risk Score related to the transaction and the entities

<Txn.RiskScores.Score>

0..1

4.3.1 Entity providing the risk score provider 1..1 Psp2

4.3.2 Type of risk type 1..1 TXNRISK

4.3.3 Value of risk evaluation ranging from 0 (No Risk) to 100 (Maximum Risk)

value 1..1 00030

5.1 Details related to the Payer <Payer> 1..1

5.1.1 Address of the Payer addr 1..1 zeeshan.khan@hdfc

5.1.2 Name of the Payer name 1..1 Zeeshan Khan

5.1.3 Unique identifier for each transaction inside a file including payer and payee

seqNum 1..1 1

5.1.4 Type of the Payer type 1..1 PERSON

5.1.5 Merchant Classification Code -MCC code 1..1 4814

5.2 Information related to the Payer <Payer.Info> 1..1

5.3 Payer Identity is mandatory for “collect” and optional for “pay”

<Payer.Info.Identity> 1..1

5.3.1 Type of the identifier type 1..1 ACCOUNT

5.3.2 Name as per the identifier verifiedName 1..1 Zeeshan Khan

5.3.3 Id Id 1.1 7389923983430

5.4 Rating of the payer <Payer.Info.Rating> 0..1

5.4.1 Payer is whitelisted or not verifiedAddress 1..1 TRUE

5.5 Information related to the amounts in the transaction

<Payer.Amount> 1..1

5.5 Transaction amount value 1..1 4000

5.6 Currency of the transaction curr 1..1 INR

6.1 Details related to the Payees <Payees> 1..1

6.2 Details related to the Payee <Payee> 1..1

6.2.1 Address of the Payee addr 1..1 rohit.patekar@sbi

6.2.2 Name of the Payee name 1..1 Rohit Patekar

6.2.3 Unique identifier for each transaction inside a file including Payee and payee

seqNum 1..1 2

6.2.4 Type of the Payee type 1..1 PERSON

6.2.5 Merchant Classification Code -MCC code 1..1 4814

6.3 Information related to the Payee <Payee.Info> 1..1

6.4 Payee Identity <Payee.Info.Identity> 1..1

Page 58: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS v1.0

15/10/2015 Page 58 of 122

Index Message Item <XML Tag> Occurrence Sample Value

6.4.1 Type of the identifier type 1..1 ACCOUNT

6.4.2 Name as per the identifier verifiedName 1..1 Rohit Patekar

6.4.3 Id Id 1.1 8392389838

6.5 Rating of the Payee <Payee.Info.Rating> 0..1

6.5.1 Payee is whitelisted or not verifiedAddress 1..1 TRUE

6.6 Only one entity is allowed for a Payee <Payee.Ac> 1..1

6.6.1 Type of the address addrType 1..1 ACCOUNT

6.7 Details related to Payee Address <Payee.Ac.Detail> 1..n

6.7.1 Name of the property name 1..n ACTYPE

6.7.2 Value of the property value 1..n SAVINGS

6.7.1 Name of the property name 1..n IFSC

6.7.2 Value of the property value 1..n SBIN0288100

6.7.1 Name of the property name 1..n ACNUM

6.7.2 Value of the property value 1..n 5678892001828

6.8 Information related to the amounts in the transaction

<Payee.Amount> 1..1

6.8.1 Transaction amount value 1..1 4000

6.8.2 Currency of the transaction curr 1..1 INR

3.6 ReqPay_NPCI_DEBIT_REQ(UPI to PSP1)

<upi:ReqPay xmlns:upi="http://npci.org/upi/schema/"> <Head ver="1.0" ts="2015-02-16T22:02:48+05:30" orgId="400001" msgId="HENSVVR4QZS7X1UGCY7JGUV444PL9Z2C3ZM"/> <Meta> <Tag name="PAYREQSTART" value="2015-02-16T22:02:00+05:30"/> <Tag name="PAYREQEND" value="2015-02-16T22:02:35+05:30"/> </Meta> <Txn id="8ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM" note="Restaurant Bill " refId="" refUrl="" ts="2015-02-16T22:02:35+05:30" type="DEBIT" orgTxnId=""> <RiskScores> <Score provider="psp1" type="TXNRISK" value="00030"/> <Score provider="npci" type="TXNRISK" value="00030"/> </RiskScores> </Txn> <Payer addr="zeeshan.khan@hdfc" name="Zeeshan Khan" seqNum="1" type="PERSON" code="4814"> <Info> <Identity type="ACCOUNT" verifiedName="Zeeshan Khan" id="7389923983430"/> <Rating verifiedAddress="TRUE"/> </Info> <Device> <Tag name="MOBILE" value="+91.99999.00000"/> <Tag name="GEOCODE" value="288177"/> <Tag name="LOCATION" value="Mumbai,Maharashtra" /> <Tag name="IP" value="124.170.23.22"/> <Tag name="TYPE" value="mob"/> <Tag name="ID" value="750c6be243f1c4b5c9912b95a5742fc5"/> #device advertising id <Tag name="OS" value="android"/> <Tag name="APP" value="NPCIAPP"/> <Tag name="CAPABILITY" value="5200000200010004000639292929292"/> </Device>

Page 59: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS v1.0

15/10/2015 Page 59 of 122

<Ac addrType="ACCOUNT"> <Detail name="ACTYPE" value="SAVINGS"/> <Detail name="IFSC" value="HDFC0288100"/> <Detail name="ACNUM" value="2678892001828"/> </Ac> <Creds> <Cred type="PIN" subType="MPIN">

<Data code="" ki=""> base-64 encoded and encrypted</Data> #data includes [<Transaction Id><delimiter><Common library version><delimiter><Captured credential><delimiter><Transaction amount><delimiter><Random number> ,"|" to be used as delimiter

</Cred>

</Creds> <Amount value="4000" curr="INR"> </Amount> </Payer> <Payees> <Payee addr="rohit.patekar@sbi" name="Rohit Patekar" seqNum="1" type="PERSON" code="4814">#mcc has to be populated <Info> <Identity type="ACCOUNT" verifiedName="Rohit Patekar" id="8392389838"/> <Rating verifiedAddress="TRUE"/> </Info> <Ac addrType="ACCOUNT"> <Detail name="IFSC" value="SBIN0288100"/> <Detail name="ACTYPE" value="SAVINGS"/> <Detail name="ACNUM" value="5678892001828"/> </Ac> <Amount value="4000" curr="INR"> </Amount> </Payee> </Payees> </upi:ReqPay>

Index Message Item <XML Tag> Occurrence Sample Value

1.1 API Name <upi> 1..1 ReqPay

1.1.1 API Schema namespace xmlns 1..1 upi="http://npci.org/upi/schema/

2.1 Header for the message <Head> 1..1

2.1.1 Version of the API ver 1..1 1.0

2.1.2 Time of request from the creator of the message

ts 1..1 2015-02-16T22:02:35+05:30

2.1.3 Organization id that created the message

orgId 1..1 400001

2.1.4 Message identifier-used to correlate between request and response

msgId 1..1 HENSVVR4QZS7X1UGPY7JGUV444PL9Z2C3QM

3.1 Meta data primarily for analytics purposes

<Meta> 0..1

3.2 Meta data primarily for analytics purposes

<Meta.Tag> 0..1

3.2.1 Name of the property name 1..n PAYREQSTART

3.2.2 Value of the property value 1..n 2015-02-16T22:02:00+05:30

4.1 Transaction information, Carried throughout the system, visible to all parties

<Txn> 1..1

Page 60: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS v1.0

15/10/2015 Page 60 of 122

Index Message Item <XML Tag> Occurrence Sample Value

4.1.1 Unique Identifier of the transaction across all entities, created by the originator

id 1..1 8ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM

4.1.2 Description of the transaction(which will be printed on Pass book)

note 1..1 Restaurant Bill

4.1.3 Consumer reference number to identify (like Loan number, etc.)

refId 1..1

4.1.4 URL for the transaction refUrl 1..1

4.1.5 Transaction origination time by the creator of the message

ts 1..1 2015-02-16T22:02:35+05:30

4.1.6 Type of the Transaction type 1..1 CREDIT

4.1.7 Original transaction ID when reversal/Refund has to be done

orgTxnId 1..1

4.2 Risk Score related to the transaction and the entities

<Txn.RiskScores> 0..1

4.3 Risk Score related to the transaction and the entities

<Txn.RiskScores.Score> 0..1

4.3.1 Entity providing the risk score provider 1..1 psp1

4.3.2 Type of risk type 1..1 TXNRISK

4.3.3 Value of risk evaluation ranging from 0 (No Risk) to 100 (Maximum Risk)

value 1..1 00030

5.1 Details related to the Payer <Payer> 1..1

5.1.1 Address of the Payer addr 1..1 zeeshan.khan@hdfc

5.1.2 Name of the Payer name 1..1 Zeeshan Khan

5.1.3 Unique identifier for each transaction inside a file including payer and payee

seqNum 1..1 1

5.1.4 Type of the Payer type 1..1 PERSON

5.1.5 Merchant Classification Code -MCC

code 1..1 4814

5.2 Information related to the Payer <Payer.Info> 1..1

5.3 Payer Identity Is mandatory for “collect” and optional for “pay”

<Payer.Info.Identity> 1..1

5.3.1 Type of the identifier type 1..1 ACCOUNT

5.3.2 Name as per the identifier verifiedName 1..1 Zeeshan Khan

5.3.3. Id Id 1.1 7389923983430

5.4 Rating of the payer <Rating> 0..1

5.4.1 Payer is whitelisted or not verifiedAddress 1..1 TRUE

5.5 Details of Device from which the transaction was initiated

<Payer.Device> 1..1

5.6 Device Tag <Payer.Device.Tag> 1..n

5.6.1 Name of the property name 1..n MOBILE

5.6.2 Value of the property value 1..n +91.99999.00000

5.7 Only one entity is allowed for a payer

<Payer.Ac> 1..1

5.7.1 Type of the address addrType 1..1 ACCOUNT

Page 61: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS v1.0

15/10/2015 Page 61 of 122

Index Message Item <XML Tag> Occurrence Sample Value

5.8 Details related to Payer Address <Payer.Ac.Detail> 1..n

5.8.1 Name of the property name 1..n ACTYPE

5.8.2 Value of the property value 1..n SAVINGS

5.8.3 Name of the property name 1..n IFSC

5.8.4 Value of the property value 1..n HDFC0288100

5.8.5 Name of the property name 1..n ACNUM

5.8.6 Value of the property value 1..n 2678892001828

5.9 Information related to Payer Credentials

<Payer.Creds> 1..1

5.10 Credentials are used to authenticate the request

<Payer.Creds.Cred> 1..1

5.10.1 Type of financial instrument used for authentication

Type 1..1 PreApproved

5.10.2 Subtype of Financial instrument used for authentication

subtype 1.1 NA

5.11 base-64 encoded/encrypted authentication data

<Payer.Creds.Cred.Data> 1..1 Base 64 encoded value of RES|A12345

5.12 Information related to the amounts in the transaction

<Payer.Amount> 1..1

5.12.1 Transaction amount Value 1..1 4000

5.12.2 Currency of the transaction Curr 1..1 INR

6.1 Details related to the Payees <Payees> 1..1

6.2 Details related to the Payee <Payee> 1..1

6.2.1 Address of the Payee Addr 1..1 rohit.patekar@sbi

6.2.2 Name of the Payee Name 1..1

6.2.3 Unique identifier for each transaction inside a file including Payee and payee

seqNum 1..1 1

6.2.4 Type of the Payee Type 1..1 PERSON

6.2.5 Merchant Classification Code -MCC

Code 1..1 4814

6.3 Information related to the Payee <Payee.Info> 1..1

6.4 Payee Identity Is mandatory for “collect” and optional for “pay”

<Payee.Info.Identity> 1..1

6.4.1 Type of the identifier type 1..1 ACCOUNT

6.4.2 Name as per the identifier verifiedName 1..1 Rohit Patekar

6.4.3. Id Id 1.1 8392389838

6.5 Rating of the payee <Rating> 0..1

6.5.1 Payee is whitelisted or not verifiedAddress 1..1 TRUE

6.6 Only one entity is allowed for a payee

<Payee.Ac> 1..1

6.6.1 Type of the address addrType 1..1 ACCOUNT

6.7 Details related to Payee Address <Payee.Ac.Detail> 1..n

6.7.1 Name of the property name 1..n ACTYPE

6.7.2 Value of the property value 1..n SAVINGS

6.7.3 Name of the property name 1..n IFSC

6.7.4 Value of the property value 1..n SBIN0288100

Page 62: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS v1.0

15/10/2015 Page 62 of 122

Index Message Item <XML Tag> Occurrence Sample Value

6.7.5 Name of the property name 1..n ACNUM

6.7.6 Value of the property value 1..n 5678892001828

3.7 RespPay_NPCI_DEBIT_REQ_RES(PSP1 to UPI)

<upi:RespPay xmlns:upi="http://npci.org/upi/schema/"> <Head ver="1.0" ts="2015-02-16T22:02:54+05:30" orgId="400002" msgId="NENSVVR4QOS7X1UGPY7JGUV424PL9T2C3QP"/> <Txn id="8ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM" note="Restaurant Bill " refId=““ refUrl=““ ts="2015-02-16T22:02:35+05:30" type="DEBIT"> <RiskScores> <Score provider="psp2" type="TXNRISK" value="00030"/> <Score provider="npci" type="TXNRISK" value="00030"/> </RiskScores> </Txn> <Resp reqMsgId="HENSVVR4QZS7X1UGCY7JGUV444PL9Z2C3ZM" result="SUCCESS" errCode=""> <Ref type="PAYER" seqNum="1" addr="zeeshan.khan@hdfc" settAmount="4000"

settCurrency="INR" acNum ="2678892001828" approvalNum="9399389827" respCode="00"/>

<Ref type="PAYEE" seqNum="1" addr="rohit.patekar@sbi" settAmount="4000" settCurrency="INR" acNum="5678892001828" approvalNum="7786787865" respCode="00"/>

</Resp> </upi:RespPay>

Index Message Item <XML Tag> Occurrence Sample Value

1.1 API Name <RespPay> 1..1 RespPay

1.1.1 API Schema namespace xmlns 1..1 upi="http://npci.org/upi/schema/

2.1 Header for the message <Head> 1..1

2.1.1 Version of the API ver 1..1 1.0

2.1.2 Time of request from the creator of the message

ts 1..1 2015-02-16T22:02:48+05:30

2.1.3 Organization id that created the message

orgId 1..1 400002

2.1.4 Message identifier-used to correlate between request and response

msgId 1..1 NENSVVR4QOS7X1UGPY7JGUV424PL9T2C3QM

3.1 Transaction information, Carried throughout the system, visible to all parties

<Txn> 1..1

3.1.1 Unique Identifier of the transaction across all entities created by the originator

id 1..1 8ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM

3.1.2 Description of the transaction(which will be printed on Pass book)

note 1..1 Restaurant Bill

3.1.3 Consumer reference number to identify (like Loan number, etc.)

refId 1..1

3.1.4 URL for the transaction refUrl 1..1

3.1.5 Transaction origination time by the creator of the message

ts 1..1 2015-02-16T22:02:35+05:30

Page 63: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS v1.0

15/10/2015 Page 63 of 122

Index Message Item <XML Tag> Occurrence Sample Value

3.1.6 Type of the Transaction type 1..1 CREDIT

3.2 Risk Score related to the transaction and the entities

<Txn.RiskScores> 0..1

3.3 Risk Score related to the transaction and the entities

<Txn.RiskScores.Score>

0..1

3.3.1 Entity providing the risk score provider 1..1 psp1

3.3.2 Type of risk type 1..1 TXNRISK

3.3.3 Value of risk evaluation ranging from 0 (No Risk) to 100 (Maximum Risk)

value 1..1 00030

3.4 Response <Resp> 1..1

3.4.1 Request Message identifier reqMsgId 1..1 HENSVVR4QZS7X1UGPY7JGUV444PL9Z2C3QM

3.4.2 Result of the transaction result 1..1 SUCCESS

3.4..3 Error code if failed errCode 1..1

3.5 Response Reference <Ref> 1..n

3.5.1 Customer type type 1..1 PAYER

3.5.2 Sequence Number seqNum 1..1 1

3.5.3 Payment address addr 1..1 zeeshan.khan@hdfc

3.5.4 Settlement Amount settAmount 1..1 4000

3.5.5 Settlement Currency settCurrency 1..1 INR

3.5.6 Approval Reference Number approvalNum 1..1 9399389827

3.5.7 Response code respCode 1..1 00

3.8 RespPay(UPI to PSP1)

<upi:RespPay xmlns:upi="http://npci.org/upi/schema/"> <Head ver="1.0" ts="2015-02-16T22:02:48+05:30" orgId="400001" msgId="NENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM"/> <Txn id="8ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM" note="Restaurant Bill " refId=““ refUrl=““ ts="2015-02-16T22:02:35+05:30" type="PAY"> <RiskScores> <Score provider="psp2" type="TXNRISK" value="00030"/> <Score provider="npci" type="TXNRISK" value="00030"/> </RiskScores> </Txn> <Resp reqMsgId="HENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM" result="SUCCESS" errCode=""> <Ref type="PAYER" seqNum="1" addr="zeeshan.khan@hdfc" settAmount="4000" settCurrency="INR" approvalNum="9399389827" respCode="00"/> <Ref type="PAYEE" seqNum="1" addr="rohit.patekar@sbi" settAmount="4000" settCurrency="INR" approvalNum="7786787865" respCode="00"/> </Resp> </upi:RespPay>

Index Message Item <XML Tag> Occurrence Sample Value

1.1 API Name <RespPay> 1..1 RespPay

1.1.1 API Schema namespace xmlns 1..1 upi="http://npci.org/upi/schema/

2.1 Header for the message <Head> 1..1

2.1.1 Version of the API ver 1..1 1.0

Page 64: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS v1.0

15/10/2015 Page 64 of 122

Index Message Item <XML Tag> Occurrence Sample Value

2.1.2 Time of request from the creator of the message

ts 1..1 2015-02-16T22:02:48+05:30

2.1.3 Organization id that created the message

orgId 1..1 400001

2.1.4 Message identifier-used to correlate between request and response

msgId 1..1 NENSVVR4QOS7X1UGPY7JGUV424PL9T2C3QM

3.1 Transaction information, Carried throughout the system, visible to all parties

<Txn> 1..1

3.1.1 Unique Identifier of the transaction across all entities created by the originator

id 1..1 8ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM

3.1.2 Description of the transaction(which will be printed on Pass book)

note 1..1 Restaurant Bill

3.1.3 Consumer reference number to identify (like Loan number, etc.)

refId 1..1

3.1.4 URL for the transaction refUrl 1..1

3.1.5 Transaction origination time by the creator of the message

ts 1..1 2015-02-16T22:02:35+05:30

3.1.6 Type of the Transaction type 1..1 PAY

3.2 Risk Score related to the transaction and the entities

<Txn.RiskScores> 0..1

3.3 Risk Score related to the transaction and the entities

<Txn.RiskScores.Score>

0..1

3.3.1 Entity providing the risk score provider 1..1 Psp2

3.3.2 Type of risk type 1..1 TXNRISK

3.3.3 Value of risk evaluation ranging from 0 (No Risk) to 100 (Maximum Risk)

value 1..1 00030

3.4 Response <Resp> 1..1

3.4.1 Request Message identifier reqMsgId 1..1 HENSVVR4QZS7X1UGPY7JGUV444PL9Z2C3QM

3.4.2 Result of the transaction result 1..1 SUCCESS

3.4..3 Error code if failed errCode 1..1

3.5 Response Reference <Ref> 1..n

3.5.1 Customer type type 1..1 PAYER

3.5.2 Sequence Number seqNum 1..1 1

3.5.3 Payment address addr 1..1 zeeshan.khan@hdfc

3.5.4 Settlement Amount settAmount 1..1 4000

3.5.5 Settlement Currency settCurrency 1..1 INR

3.5.6 Approval Reference Number approvalNum 1..1 9399389827

3.5.7 Response code respCode 1..1 00

3.9 ReqTxnConfirmation(UPI to PSP2)

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

Page 65: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS v1.0

15/10/2015 Page 65 of 122

<Head ver="1.0" ts="2015-02-16T22:03:00+05:30" orgId="400001" msgId="HPDSFVC2QOS7X1UGPY2JGUV454YC8T2C6QM"/> <Txn id="8ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM" note="Restaurant Bill" refId=““ refUrl=““ ts="2015-02-16T22:02:35+05:30" type="TxnConfirmation" orgTxnId="8ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM"/> <TxnConfirmation note="Restaurant Bill" orgStatus="SUCCESS" orgErrCode=”” type="PAY" orgTxnId="8ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM" />

</upi:ReqTxnConfirmation>

3.10 RespTxnConfirmation(PSP2 to UPI)

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

<Head ver="1.0" ts="2015-02-16T22:03:01+05:30" orgId="400003" msgId="HPDSFVC2ZOS7X1UGPY2JGUV494ZC8T2C6QM"/> <Txn id="HPDSFVC2QOS7X1UGPY2JGUV458PL8T2C6QM" note="Restaurant Bill" refId=““ refUrl=““ ts="2015-02-16T22:02:35+05:30" type="TxnConfirmation" orgTxnId="8ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM" /> <Resp reqMsgId="HPDSFVC2QOS7X1UGPY2JGUV454YL8T2C6QM" result="SUCCESS" errCode=""/>

</upi:RespTxnConfirmation>

Page 66: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS

17/07/2015 Page 66 of 122

CASE 4

Payer initiates the transactions using Global Address which gets resolved using NPCI

Mapper.

4.1 Flow:

1. Customer enters the Mobile number/Aadhaar Number of the payee in the PSP app.

2. PSP initiates a ListAccount request to UPI 3. UPI sends the request to central mapper for resolution of Mobile

number/Aadhaar Number. 4. Centeral mapper responds with list of IFSC code linked with the mobile number

or adhaar number. 5. UPI sends the response to payer PSP. Payer PSP display the list to the customer. 6. Customer selects the appropriate IFSC code and sends the Pay request to PSP. 7. Payer PSP sends the request to UPI. 8. UPI intiates a debit request with the payer PSP. 9. Payer PSP debits the account and sends response to UPI. 10. UPI sends a credit request to IMPS 11. IMPS sends a credit request to Beneficiary Bank 12. Beneficiary Bank credits the customer’s account and responds back to IMPS 13. IMPS responds the same to UPI 14. UPI sends RespPay message to the Payer PSP 15. Payer PSP confirms the successful transaction to the customer

Page 67: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS

17/07/2015 Page 67 of 122

4.2 ReqListAccount: Request for Account List

<upi:ReqListAccount xmlns:upi="http://npci.org/upi/schema/"> <Head ver="1.0" ts="2015-02-16T22:02:25+05:30" orgId="" msgId="HENSVVR4QOS7Y1UGPY7JGUV444PL9T2C3QM"/> <Payer addr="Zeeshan.khan@hdfc" name="Zeeshan Khan" seqNum="1" type="PERSON|ENTITY" code="4814"> <Link type="MOBILE" value="9999933333"/> <Creds> <Cred type="OTP" subtype="SMS|EMAIL|HOTP|TOTP"> <Data> base-64 encoded/encrypted authentication data</Data> </Cred> </Creds> </upi:ReqListAccount>

4.3 RespListAccount: Response for Account List

<upi:RespListAccount xmlns:upi="http://npci.org/upi/schema/"> <Head ver="1.0" ts="2015-02-16T22:02:30+05:30" orgId="400001" msgId="FENSVVR4QOS7Y1UGPY7JGUV444PL9T2C3QM"/> <Resp reqMsgId="HENSVVR4QOS7Y1UGPY7JGUV444PL9T2C3QM" result="SUCCESS" errCode=""/> <AccountList> <Account accRefNumber="" maskedAccNumber="" ifsc="HDFC0000101" mmid="" name="Rohit Patkar" aeba="N"/> <Account accRefNumber="" maskedAccNumber="" ifsc="HDFC0000103" mmid="" name="Rohit Patkar" aeba="Y"/> </AccountList> </upi:RespListAccount>

Page 68: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS

17/07/2015 Page 68 of 122

4.4 ReqPay(PSP1 to UPI)

<upi:ReqPay xmlns:upi="http://npci.org/upi/schema/"> <Head ver="1.0" ts="2015-02-16T22:02:35+05:30" orgId="400002" msgId="HENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM"/> <Meta> <Tag name="PAYREQSTART" value="2015-02-16T22:02:00+05:30"/> <Tag name="PAYREQEND" value="2015-02-16T22:02:35+05:30"/> </Meta> <Txn id="8ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM" note="Restaurant Bill " refId="" refUrl="" ts="2015-02-16T22:02:35+05:30" type="PAY" orgTxnId=""> <RiskScores> <Score provider="psp1" type="TXNRISK" value="00030"/> </RiskScores> </Txn> <Payer addr="zeeshan.khan@hdfc" name="Zeeshan Khan" seqNum="1" type="PERSON" code="4814"> <Info> <Identity type="ACCOUNT" verifiedName="Zeeshan Khan" id="7389923983430"/> <Rating verifiedAddress="TRUE"/> </Info> <Device> <Tag name="MOBILE" value="+91.99999.00000"/> <Tag name="GEOCODE" value="288177"/> <Tag name="LOCATION" value="Mumbai,Maharashtra" /> <Tag name="IP" value="124.170.23.22"/> <Tag name="TYPE" value="mob"/> <Tag name="ID" value="750c6be243f1c4b5c9912b95a5742fc5"/> #device advertising id <Tag name="OS" value="android"/> <Tag name="APP" value="NPCIAPP"/> <Tag name="CAPABILITY" value="5200000200010004000639292929292"/> </Device> <Ac addrType="ACCOUNT"> <Detail name="ACTYPE" value="SAVINGS"/> <Detail name="IFSC" value="HDFC0288100"/> <Detail name="ACNUM" value="2678892001828"/> </Ac>

<Creds> <Cred type="PIN" subType="MPIN">

<Data code="" ki=""> base-64 encoded and encrypted</Data> #data includes [base 64 encoded]<Transaction Id><delimiter><Common library version><delimiter><Captured credential><delimiter><Transaction amount><delimiter><Random number>[encrypted] ,"|" to be used as delimiter

</Cred> </Creds> <Amount value="4000" curr="INR"> </Amount> </Payer> <Payees> <Payee addr="9999933333" name="Rohit Patkar" seqNum="1" type="Person" code="4814"> <Ac addrType="ACCOUNT"> <Detail name="ACTYPE" value="SAVINGS"/>

<Detail name="IFSC" value=" HDFC0000103"/> <Detail name="ACNUM" value=""/> </Ac>

Page 69: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS

17/07/2015 Page 69 of 122

</Payee> </Payees> </upi:ReqPay>

Index Message Item <XML Tag> Occurrence Sample Value

1.1 API Name <upi> 1..1 ReqPay

1.1.1 API Schema namespace Xmlns 1..1 upi="http://npci.org/upi/schema/

2.1 Header for the message <Head> 1..1

2.1.1 Version of the API Ver 1..1 1.0

2.1.2 Time of request from the creator of the message

Ts 1..1 2015-02-16T22:02:35+05:30

2.1.3 Organization id that created the message

orgId 1..1 400002

2.1.4 Message identifier-used to correlate between request and response

msgId 1..1 HENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM

3.1 Meta data primarily for analytics purposes

<Meta> 0..1

3.2 Meta data primarily for analytics purposes

<Meta.Tag> 0..1

3.2.1 Name of the property Name 1..n PAYREQSTART

3.2.2 Value of the property Value 1..n 2015-02-16T22:02:00+05:30

4.1 Transaction information, Carried throughout the system, visible to all parties

<Txn> 1..1

4.1.1 Unique Identifier of the transaction across all entities, created by the originator

Id 1..1 8ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM

4.1.2 Description of the transaction(which will be printed on Pass book)

Note 1..1 Restaurant Bill

4.1.3 Consumer reference number to identify (like Loan number, etc.)

refId 1..1

4.1.4 URL for the transaction refUrl 1..1

4.1.5 Transaction origination time by the creator of the message

Ts 1..1 2015-02-16T22:02:35+05:30

4.1.6 Type of the Transaction Type 1..1 PAY

4.1.7 Original transaction ID when reversal/Refund has to be done

orgTxnId 1..1

4.2 Risk Score related to the transaction and the entities

<Txn.RiskScores> 0..1

4.3 Risk Score related to the transaction and the entities

<Txn.RiskScores.Score>

0..1

4.3.1 Entity providing the risk score provider 1..1 psp1

4.3.2 Type of risk Type 1..1 TXNRISK

4.3.3 Value of risk evaluation ranging from 0 (No Risk) to 100 (Maximum Risk)

Value 1..1 00030

Page 70: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS

17/07/2015 Page 70 of 122

Index Message Item <XML Tag> Occurrence Sample Value

5.1 Details related to the Payer <Payer> 1..1

5.1.1 Address of the Payer Addr 1..1 zeeshan.khan@hdfc

5.1.2 Name of the Payer Name 1..1 Zeeshan Khan

5.1.3 Unique identifier for each transaction inside a file including payer and payee

seqNum 1..1 1

5.1.4 Type of the Payer Type 1..1 PERSON

5.1.5 Merchant Classification Code -MCC

Code 1..1 4814

5.2 Information related to the Payer <Payer.Info> 1..1

5.3 Payer Identity Is mandatory for “collect” and optional for “pay”

<Payer.Info.Identity>

1..1

5.3.1 Type of the identifier Type 1..1 ACCOUNT

5.3.2 Name as per the identifier verifiedName 1..1 Zeeshan Khan

5.3.3. Id Id 1.1 7389923983430

5.4 Rating of the payer <Rating> 0..1

5.4.1 Payer is whitelisted or not verifiedAddress 1..1 TRUE

5.5 Details of Device from which the transaction was initiated

<Payer.Device> 1..1

5.6 Device Tag <Payer.Device.Tag> 1..n

5.6.1 Name of the property name 1..n MOBILE

5.6.2 Value of the property value 1..n +91.99999.00000

5.7 Only one entity is allowed for a payer

<Payer.Ac> 1..1

5.7.1 Type of the address addrType 1..1 ACCOUNT

5.8 Details related to Payer Address <Payer.Ac.Detail> 1..n

5.8.1 Name of the property name 1..n ACTYPE

5.8.2 Value of the property value 1..n SAVINGS

5.8.3 Name of the property name 1..n IFSC

5.8.4 Value of the property value 1..n HDFC0288100

5.8.5 Name of the property name 1..n ACNUM

5.8.6 Value of the property value 1..n 2678892001828

5.9 Information related to Payer Credentials

<Payer.Creds> 1..1

5.10 Credentials are used to authenticate the request

<Payer.Creds.Cred> 1..1

5.10.1 Type of financial instrument used for authentication

type 1..1 PreApproved

5.10.2 Subtype of Financial instrument used for authentication

subtype 1.1 NA

5.11 base-64 encoded/encrypted authentication data

<Payer.Creds.Cred.Data>

1..1 Base 64 encoded value of RES|A12345

5.12 Information related to the amounts in the transaction

<Payer.Amount> 1..1

5.12.1 Transaction amount value 1..1 4000

5.12.2 Currency of the transaction curr 1..1 INR

6.1 Details related to the Payees <Payees> 1..1

Page 71: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS

17/07/2015 Page 71 of 122

Index Message Item <XML Tag> Occurrence Sample Value

6.2 Details related to the Payee <Payee> 1..1

6.2.1 Address of the Payee addr 1..1 8879776455

6.2.2 Name of the Payee name 1..1

6.2.3 Unique identifier for each transaction inside a file including Payee and payee

seqNum 1..1 1

6.2.4 Type of the Payee type 1..1

6.2.5 Merchant Classification Code code 1..1

4.5 ReqPay_NPCI_DEBIT_REQ(UPI to PSP1)

<upi:ReqPay xmlns:upi="http://npci.org/upi/schema/"> <Head ver="1.0" ts="2015-02-16T22:02:48+05:30" orgId="400001" msgId="HENSVVR4QZS7X1UGCY7JGUV444PL9Z2C3ZM"/> <Meta> <Tag name="PAYREQSTART" value="2015-02-16T22:02:00+05:30"/> <Tag name="PAYREQEND" value="2015-02-16T22:02:35+05:30"/> </Meta> <Txn id="8ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM" note="Restaurant Bill " refId="" refUrl="" ts="2015-02-16T22:02:35+05:30" type="DEBIT" orgTxnId=""> <RiskScores> <Score provider="psp1" type="TXNRISK" value="00030"/> <Score provider="npci" type="TXNRISK" value="00030"/> </RiskScores> </Txn> <Payer addr="zeeshan.khan@hdfc" name="Zeeshan Khan" seqNum="1" type="PERSON" code="4814"> <Info> <Identity type="ACCOUNT" verifiedName="Zeeshan Khan" id="7389923983430"/> <Rating verifiedAddress="TRUE"/> </Info> <Device> <Tag name="MOBILE" value="+91.99999.00000"/> <Tag name="GEOCODE" value="288177"/> <Tag name="LOCATION" value="Mumbai,Maharashtra" /> <Tag name="IP" value="124.170.23.22"/> <Tag name="TYPE" value="mob"/> <Tag name="ID" value="750c6be243f1c4b5c9912b95a5742fc5"/> #device advertising id <Tag name="OS" value="android"/> <Tag name="APP" value="NPCIAPP"/> <Tag name="CAPABILITY" value="5200000200010004000639292929292"/> </Device> <Ac addrType="ACCOUNT"> <Detail name="ACTYPE" value="SAVINGS"/> <Detail name="IFSC" value="HDFC0288100"/> <Detail name="ACNUM" value="2678892001828"/> </Ac> <Creds> <Cred type="PIN" subType="MPIN">

<Data code="" ki=""> base-64 encoded and encrypted</Data> #data includes [<Transaction Id><delimiter><Common library version><delimiter><Captured credential><delimiter><Transaction amount><delimiter><Random number> ,"|" to be used as delimiter

Page 72: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS

17/07/2015 Page 72 of 122

</Cred>

</Creds> <Amount value="4000" curr="INR"> </Amount> </Payer> <Payees> <Payee addr="rohit.patekar@sbi" name="Rohit Patekar" seqNum="1" type="PERSON" code="4814">#mcc has to be populated <Info> <Identity type="ACCOUNT" verifiedName="Rohit Patekar" id="8392389838"/> <Rating verifiedAddress="TRUE"/> </Info> <Ac addrType="ACCOUNT"> <Detail name="IFSC" value="SBIN0288100"/> <Detail name="ACTYPE" value="SAVINGS"/> <Detail name="ACNUM" value="5678892001828"/> </Ac> <Amount value="4000" curr="INR"> </Amount> </Payee> </Payees> </upi:ReqPay>

Index Message Item <XML Tag> Occurrence Sample Value

1.1 API Name <upi> 1..1 ReqPay

1.1.1 API Schema namespace xmlns 1..1 upi="http://npci.org/upi/schema/

2.1 Header for the message <Head> 1..1

2.1.1 Version of the API ver 1..1 1.0

2.1.2 Time of request from the creator of the message

ts 1..1 2015-02-16T22:02:35+05:30

2.1.3 Organization id that created the message

orgId 1..1 400001

2.1.4 Message identifier-used to correlate between request and response

msgId 1..1 HENSVVR4QZS7X1UGPY7JGUV444PL9Z2C3QM

3.1 Meta data primarily for analytics purposes

<Meta> 0..1

3.2 Meta data primarily for analytics purposes

<Meta.Tag> 0..1

3.2.1 Name of the property name 1..n PAYREQSTART

3.2.2 Value of the property value 1..n 2015-02-16T22:02:00+05:30

4.1 Transaction information, Carried throughout the system, visible to all parties

<Txn> 1..1

4.1.1 Unique Identifier of the transaction across all entities, created by the originator

id 1..1 8ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM

4.1.2 Description of the transaction(which will be printed on Pass book)

note 1..1 Restaurant Bill

4.1.3 Consumer reference number to identify (like Loan number, etc.)

refId 1..1

4.1.4 URL for the transaction refUrl 1..1

Page 73: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS

17/07/2015 Page 73 of 122

Index Message Item <XML Tag> Occurrence Sample Value

4.1.5 Transaction origination time by the creator of the message

ts 1..1 2015-02-16T22:02:35+05:30

4.1.6 Type of the Transaction type 1..1 CREDIT

4.1.7 Original transaction ID when reversal/Refund has to be done

orgTxnId 1..1

4.2 Risk Score related to the transaction and the entities

<Txn.RiskScores> 0..1

4.3 Risk Score related to the transaction and the entities

<Txn.RiskScores.Score> 0..1

4.3.1 Entity providing the risk score provider 1..1 psp1

4.3.2 Type of risk type 1..1 TXNRISK

4.3.3 Value of risk evaluation ranging from 0 (No Risk) to 100 (Maximum Risk)

value 1..1 00030

5.1 Details related to the Payer <Payer> 1..1

5.1.1 Address of the Payer addr 1..1 zeeshan.khan@hdfc

5.1.2 Name of the Payer name 1..1 Zeeshan Khan

5.1.3 Unique identifier for each transaction inside a file including payer and payee

seqNum 1..1 1

5.1.4 Type of the Payer type 1..1 PERSON

5.1.5 Merchant Classification Code -MCC

code 1..1 4814

5.2 Information related to the Payer <Payer.Info> 1..1

5.3 Payer Identity Is mandatory for “collect” and optional for “pay”

<Payer.Info.Identity> 1..1

5.3.1 Type of the identifier type 1..1 ACCOUNT

5.3.2 Name as per the identifier verifiedName 1..1 Zeeshan Khan

5.3.3. Id Id 1.1 7389923983430

5.4 Rating of the payer <Rating> 0..1

5.4.1 Payer is whitelisted or not verifiedAddress 1..1 TRUE

5.5 Details of Device from which the transaction was initiated

<Payer.Device> 1..1

5.6 Device Tag <Payer.Device.Tag> 1..n

5.6.1 Name of the property name 1..n MOBILE

5.6.2 Value of the property value 1..n +91.99999.00000

5.7 Only one entity is allowed for a payer

<Payer.Ac> 1..1

5.7.1 Type of the address addrType 1..1 ACCOUNT

5.8 Details related to Payer Address <Payer.Ac.Detail> 1..n

5.8.1 Name of the property name 1..n ACTYPE

5.8.2 Value of the property value 1..n SAVINGS

5.8.3 Name of the property name 1..n IFSC

5.8.4 Value of the property value 1..n HDFC0288100

5.8.5 Name of the property name 1..n ACNUM

5.8.6 Value of the property value 1..n 2678892001828

Page 74: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS

17/07/2015 Page 74 of 122

Index Message Item <XML Tag> Occurrence Sample Value

5.9 Information related to Payer Credentials

<Payer.Creds> 1..1

5.10 Credentials are used to authenticate the request

<Payer.Creds.Cred> 1..1

5.10.1 Type of financial instrument used for authentication

Type 1..1 PreApproved

5.10.2 Subtype of Financial instrument used for authentication

subtype 1.1 NA

5.11 base-64 encoded/encrypted authentication data

<Payer.Creds.Cred.Data> 1..1 Base 64 encoded value of RES|A12345

5.12 Information related to the amounts in the transaction

<Payer.Amount> 1..1

5.12.1 Transaction amount Value 1..1 4000

5.12.2 Currency of the transaction Curr 1..1 INR

6.1 Details related to the Payees <Payees> 1..1

6.2 Details related to the Payee <Payee> 1..1

6.2.1 Address of the Payee Addr 1..1 rohit.patekar@sbi

6.2.2 Name of the Payee Name 1..1

6.2.3 Unique identifier for each transaction inside a file including Payee and payee

seqNum 1..1 1

6.2.4 Type of the Payee Type 1..1 PERSON

6.2.5 Merchant Classification Code -MCC

Code 1..1 4814

6.3 Information related to the Payee <Payee.Info> 1..1

6.4 Payee Identity Is mandatory for “collect” and optional for “pay”

<Payee.Info.Identity> 1..1

6.4.1 Type of the identifier type 1..1 ACCOUNT

6.4.2 Name as per the identifier verifiedName 1..1 Rohit Patekar

6.4.3. Id Id 1.1 8392389838

6.5 Rating of the payee <Rating> 0..1

6.5.1 Payee is whitelisted or not verifiedAddress 1..1 TRUE

6.6 Only one entity is allowed for a payee

<Payee.Ac> 1..1

6.6.1 Type of the address addrType 1..1 ACCOUNT

6.7 Details related to Payee Address <Payee.Ac.Detail> 1..n

6.7.1 Name of the property name 1..n ACTYPE

6.7.2 Value of the property value 1..n SAVINGS

6.7.3 Name of the property name 1..n IFSC

6.7.4 Value of the property value 1..n SBIN0288100

6.7.5 Name of the property name 1..n ACNUM

6.7.6 Value of the property value 1..n 5678892001828

Page 75: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS

17/07/2015 Page 75 of 122

4.6 RespPay_NPCI_DEBIT_REQ_RES(PSP1 to UPI)

<upi:RespPay xmlns:upi="http://npci.org/upi/schema/"> <Head ver="1.0" ts="2015-02-16T22:02:54+05:30" orgId="400002" msgId="NENSVVR4QOS7X1UGPY7JGUV424PL9T2C3QP"/> <Txn id="8ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM" note="Restaurant Bill " refId=““ refUrl=““ ts="2015-02-16T22:02:35+05:30" type="DEBIT"> <RiskScores> <Score provider="psp2" type="TXNRISK" value="00030"/> <Score provider="npci" type="TXNRISK" value="00030"/> </RiskScores> </Txn> <Resp reqMsgId="HENSVVR4QZS7X1UGCY7JGUV444PL9Z2C3ZM" result="SUCCESS" errCode=""> <Ref type="PAYER" seqNum="1" addr="zeeshan.khan@hdfc" settAmount="4000"

settCurrency="INR" acNum="2678892001828" approvalNum="9399389827" respCode="00"/>

<Ref type="PAYEE" seqNum="1" addr="9999933333" settAmount="4000" settCurrency="INR" acNum="5678892001828" approvalNum="" respCode=""/> </Resp> </upi:RespPay>

Index Message Item <XML Tag> Occurrence Sample Value

1.1 API Name <RespPay> 1..1 RespPay

1.1.1 API Schema namespace xmlns 1..1 upi="http://npci.org/upi/schema/

2.1 Header for the message <Head> 1..1

2.1.1 Version of the API ver 1..1 1.0

2.1.2 Time of request from the creator of the message

ts 1..1 2015-02-16T22:02:48+05:30

2.1.3 Organization id that created the message

orgId 1..1 400002

2.1.4 Message identifier-used to correlate between request and response

msgId 1..1 NENSVVR4QOS7X1UGPY7JGUV424PL9T2C3QM

3.1 Transaction information, Carried throughout the system, visible to all parties

<Txn> 1..1

3.1.1 Unique Identifier of the transaction across all entities created by the originator

id 1..1 8ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM

3.1.2 Description of the transaction(which will be printed on Pass book)

note 1..1 Restaurant Bill

3.1.3 Consumer reference number to identify (like Loan number, etc.)

refId 1..1

3.1.4 URL for the transaction refUrl 1..1

3.1.5 Transaction origination time by the creator of the message

ts 1..1 2015-02-16T22:02:35+05:30

3.1.6 Type of the Transaction type 1..1 CREDIT

3.2 Risk Score related to the transaction and the entities

<Txn.RiskScores> 0..1

3.3 Risk Score related to the transaction and the entities

<Txn.RiskScores.Score>

0..1

3.3.1 Entity providing the risk score provider 1..1 psp1

3.3.2 Type of risk type 1..1 TXNRISK

Page 76: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS

17/07/2015 Page 76 of 122

Index Message Item <XML Tag> Occurrence Sample Value

3.3.3 Value of risk evaluation ranging from 0 (No Risk) to 100 (Maximum Risk)

value 1..1 00030

3.4 Response <Resp> 1..1

3.4.1 Request Message identifier reqMsgId 1..1 HENSVVR4QZS7X1UGPY7JGUV444PL9Z2C3QM

3.4.2 Result of the transaction result 1..1 SUCCESS

3.4..3 Error code if failed errCode 1..1

3.5 Response Reference <Ref> 1..n

3.5.1 Customer type type 1..1 PAYER

3.5.2 Sequence Number seqNum 1..1 1

3.5.3 Payment address addr 1..1 zeeshan.khan@hdfc

3.5.4 Settlement Amount settAmount 1..1 4000

3.5.5 Settlement Currency settCurrency 1..1 INR

3.5.6 Approval Reference Number approvalNum 1..1 9399389827

3.5.7 Response code respCode 1..1 00

4.7 RespPay(UPI to PSP1)

<upi:RespPay xmlns:upi="http://npci.org/upi/schema/"> <Head ver="1.0" ts="2015-02-16T22:02:48+05:30" orgId="400001" msgId="NENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM"/> <Txn id="8ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM" note="Restaurant Bill " refId=““ refUrl=““ ts="2015-02-16T22:02:35+05:30" type="PAY"> <RiskScores> <Score provider="npci" type="TXNRISK" value="00030"/> </RiskScores> </Txn> <Resp reqMsgId="HENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM" result="SUCCESS" errCode=""> <Ref type="PAYER" seqNum="1" addr="zeeshan.khan@hdfc" settAmount="4000" settCurrency="INR" approvalNum="9399389827" respCode="00"/> <Ref type="PAYEE" seqNum="1" addr="9999933333" settAmount="4000" settCurrency="INR" approvalNum="7786787865" respCode="00"/> </Resp> </upi:RespPay>

Index Message Item <XML Tag> Occurrence Sample Value

1.1 API Name <RespPay> 1..1 RespPay

1.1.1 API Schema namespace xmlns 1..1 upi="http://npci.org/upi/schema/

2.1 Header for the message <Head> 1..1

2.1.1 Version of the API ver 1..1 1.0

2.1.2 Time of request from the creator of the message

ts 1..1 2015-02-16T22:02:48+05:30

2.1.3 Organization id that created the message

orgId 1..1 400001

2.1.4 Message identifier-used to correlate between request and response

msgId 1..1 NENSVVR4QOS7X1UGPY7JGUV424PL9T2C3QM

3.1 Transaction information, Carried throughout the system, visible to all parties

<Txn> 1..1

Page 77: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS

17/07/2015 Page 77 of 122

Index Message Item <XML Tag> Occurrence Sample Value

3.1.1 Unique Identifier of the transaction across all entities created by the originator

id 1..1 8ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM

3.1.2 Description of the transaction(which will be printed on Pass book)

note 1..1 Restaurant Bill

3.1.3 Consumer reference number to identify (like Loan number, etc.)

refId 1..1

3.1.4 URL for the transaction refUrl 1..1

3.1.5 Transaction origination time by the creator of the message

ts 1..1 2015-02-16T22:02:35+05:30

3.1.6 Type of the Transaction type 1..1 PAY

3.2 Risk Score related to the transaction and the entities

<Txn.RiskScores> 0..1

3.3 Risk Score related to the transaction and the entities

<Txn.RiskScores.Score>

0..1

3.3.1 Entity providing the risk score provider 1..1 Psp2

3.3.2 Type of risk type 1..1 TXNRISK

3.3.3 Value of risk evaluation ranging from 0 (No Risk) to 100 (Maximum Risk)

value 1..1 00030

3.4 Response <Resp> 1..1

3.4.1 Request Message identifier reqMsgId 1..1 HENSVVR4QZS7X1UGPY7JGUV444PL9Z2C3QM

3.4.2 Result of the transaction result 1..1 SUCCESS

3.4..3 Error code if failed errCode 1..1

3.5 Response Reference <Ref> 1..n

3.5.1 Customer type type 1..1 PAYER

3.5.2 Sequence Number seqNum 1..1 1

3.5.3 Payment address addr 1..1 zeeshan.khan@hdfc

3.5.4 Settlement Amount settAmount 1..1 4000

3.5.5 Settlement Currency settCurrency 1..1 INR

3.5.6 Approval Reference Number approvalNum 1..1 9399389827

3.5.7 Response code respCode 1..1 00

Page 78: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS

17/07/2015 Page 78 of 122

CASE 5

FOUR PARTY MODEL – Collect Request [Payer PSP, Remitter/PAYER Bank, Payee

PSP & Beneficiary/PAYEE Bank ]

5.1 Flow:

1. Customer sends a Collect Request by entering the Virtual Address of the Payer

customer.

2. Payee PSP sends the ReqPay message to UPI

3. UPI sends the ReqAuthDetails to the respective Payer PSP 4. Payer PSP sends a notification to the Payer customer for authorization.

Customer enters the PIN & confirms the payment. Payer PSP sends the RespAuthDetails message to UPI

5. UPI sends the debit request to Payer BANK. 6. Payer BANK debits the customer account and sends response back to UPI. 7. UPI sends a Credit Request to Beneficiary Bank 8. Beneficiary Bank credits the customer’s account and responds successful

credit to UPI 9. UPI sends the RespPay message to Payee PSP 10. Payee PSP sends the confirmation to the customer.

Page 79: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS

17/07/2015 Page 79 of 122

5.2 ReqPay(PSP1 to UPI)

<upi:ReqPay xmlns:upi="http://npci.org/upi/schema/"> <Head ver="1.0" ts="2015-02-16T22:02:35+05:30" orgId="400002" msgId="HDNSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM"/> <Meta> <Tag name="PAYREQSTART" value="2015-02-16T22:02:00+05:30"/> <Tag name="PAYREQEND" value="2015-02-16T22:02:35+05:30"/> </Meta> <Txn id="9ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM" note="Your taxi trip Bill " refId="" refUrl="" ts="2015-02-16T22:02:35+05:30" type="Collect" orgTxnId=""> <RiskScores> <Score provider="psp1" type="TXNRISK" value="00030"/> </RiskScores> <Rules> <Rule name="EXPIREAFTER" value="10080"/> <! Payment request will expire in 7 days (7*24*60 minutes) > </Rules> </Txn> <Payer addr="rohit.patekar@sbi" name="" seqNum="1" type="" code=""> </Payer> <Payees> <Payee addr="zeeshan@hdfc" name="Zeeshan Khan" seqNum="1" type="PERSON" code="4814"> <Info> <Identity type="ACCOUNT" verifiedName="Zeeshan Khan" id="7389923983430"/> <Rating verifiedAddress="TRUE"/> </Info> <Device> <Tag name="MOBILE" value="+91.99999.00000"/> <Tag name="GEOCODE" value="288177"/> <Tag name="LOCATION" value="Mumbai,Maharashtra" /> <Tag name="IP" value="124.170.23.22"/> <Tag name="TYPE" value="mob"/> <Tag name="ID" value="750c6be243f1c4b5c9912b95a5742fc5"/> <Tag name="OS" value="android"/> <Tag name="APP" value="NPCIAPP"/> <Tag name="CAPABILITY" value="5200000200010004000639292929292"/> </Device> <Ac addrType="ACCOUNT"> <Detail name="IFSC" value="ICIC0288100"/> <Detail name="ACTYPE" value="SAVINGS"/> <Detail name="ACNUM" value="2678892001828"/> </Ac> <Amount value="4000" curr="INR"> </Amount> </Payee> </Payees> </upi:ReqPay>

Index Message Item <XML Tag> Occurrence Sample Value

1.1 API Name <upi> 1..1 ReqPay

1.1.1 API Schema namespace Xmlns 1..1 upi="http://npci.org/upi/schema/

2.1 Header for the message <Head> 1..1

Page 80: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS

17/07/2015 Page 80 of 122

Index Message Item <XML Tag> Occurrence Sample Value

2.1.1 Version of the API Ver 1..1 1.0

2.1.2 Time of request from the creator of the message

Ts 1..1 2015-02-16T22:02:35+05:30

2.1.3 Organization id that created the message

orgId 1..1 400002

2.1.4 Message identifier-used to correlate between request and response

msgId 1..1 HDNSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM

3.1 Meta data primarily for analytics purposes

<Meta> 0..1

3.2 Meta data primarily for analytics purposes

<Meta.Tag> 0..1

3.2.1 Name of the property name 1..n PAYREQSTART

3.2.2 Value of the property value 1..n 2015-02-16T22:02:00+05:30

4.1 Transaction information, Carried throughout the system, visible to all parties

<Txn> 1..1

4.1.1 Unique Identifier of the transaction across all entities, created by the originator

id 1..1 9ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM

4.1.2 Description of the transaction(which will be printed on Pass book)

note 1..1 Your taxi trip Bill

4.1.3 Consumer reference number to identify (like Loan number, etc.)

refId 1..1

4.1.4 URL for the transaction refUrl 1..1

4.1.5 Transaction origination time by the creator of the message

ts 1..1 2015-02-16T22:02:35+05:30

4.1.6 Type of the Transaction type 1..1 Collect

4.1.7 Original transaction ID when reversal/Refund has to be done

orgTxnId 1..1

4.2 Risk Score related to the transaction and the entities

<Txn.RiskScores> 0..1

4.3 Risk Score related to the transaction and the entities

<Txn.RiskScores.Score>

0..1

4.3.1 Entity providing the risk score provider 1..1 psp1

4.3.2 Type of risk type 1..1 TXNRISK

4.3.3 Value of risk evaluation ranging from 0 (No Risk) to 100 (Maximum Risk)

value 1..1 00030

4.4 Rules that govern the payment <Txn.Rules> 0..1

4.5 Rule for the transaction <Txn.Rules.Rule> 0..n

4.5.1 Name of the property name 1..n EXPIREAFTER

4.5.2 Value of the property value 1..n 10080

5.1 Details related to the Payer <Payer> 1..1

Page 81: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS

17/07/2015 Page 81 of 122

Index Message Item <XML Tag> Occurrence Sample Value

5.1.1 Address of the Payer addr 1..1 rohit.patekar@sbi

5.1.2 Name of the Payer name 1..1

5.1.3 Unique identifier for each transaction inside a file including payer and payee

seqNum 1..1

5.1.4 Type of the Payer type 1..1

5.1.5 Merchant Classification Code -MCC

code 1..1

6.1 Details related to the Payees <Payees> 1..1

6.2 Details related to the Payee <Payee> 1..1

6.2.1 Address of the Payee addr 1..1 zeeshan@hdfc

6.2.2 Name of the Payee name 1..1 Zeeshan Khan

6.2.3 Unique identifier for each transaction inside a file including Payee and payee

seqNum 1..1 1

6.2.4 Type of the Payee type 1..1 PERSON

6.2.5 Merchant Classification Code –MCC

code 1..1 4814

7.1 Information related to the Payee <Payee.Info> 1..1

7.2 Payee Identity Is mandatory for “collect” and optional for “pay”

<Payee.Info.Identity>

1..1

7.2.1 Type of the identifier type 1..1 ACCOUNT

7.2.2 Name as per the identifier verifiedName 1..1 Zeeshan Khan

7.3.3 Id Id 1.1 7389923983430

7.4 Rating of the payee <Rating> 0..1

7.4.1 Payer is whitelisted or not verifiedAddress 1..1 TRUE

7.5 Details of Device from which the transaction was initiated

<Payee.Device> 1..1

7.6 Device Tag <Payee.Device.Tag>

1..n

7.6.1 Name of the property name 1..n MOBILE

7.6.2 Value of the property value 1..n +91.99999.00000

7.7 Only one entity is allowed for a payee

<Payee.Ac> 1..1

7.7.1 Type of the address addrType 1..1 ACCOUNT

7.8 Details related to Payee Address <Payee.Ac.Detail> 1..n

7.8.1 Name of the property name 1..n ACTYPE

7.8.2 Value of the property value 1..n SAVINGS

7.8.3 Name of the property name 1..n IFSC

7.8.4 Value of the property value 1..n ICIC0288100

7.8.5 Name of the property name 1..n ACNUM

7.8.6 Value of the property value 1..n 2678892001828

7.9 Information related to the amounts in the transaction

<Payee.Amount> 1..1

7.9.1 Transaction amount value 1..1 4000

7.9.2 Currency of the transaction curr 1..1 INR

Page 82: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS

17/07/2015 Page 82 of 122

5.3 MSG_ACK(to be send for every message)

<?xml version='1.0' encoding='UTF-8' standalone='no'?><Ack api='UPI' err=''/>

5.4 ReqAuthDetails(UPI to PSP2)

<upi:ReqAuthDetails xmlns:upi="http://npci.org/upi/schema/"> <Head ver="1.0" ts="2015-02-16T22:02:40+05:30" orgId="400001" msgId="NPNSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM"/> <Txn id="9ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM" note="Your Taxi trip Bill " refId=““ refUrl=““ ts="2015-02-16T22:02:35+05:30" type="Collect"> <RiskScores> <Score provider="psp1" type="TXNRISK" value="00030"/> <Score provider="NPCI" type="TXNRISK" value="00030"/> </RiskScores> <Rules> <Rule name="EXPIREAFTER" value="10080"/> <!--Payment request will expire in 7 days (7*24*60 minutes)--> </Rules> </Txn> <Payer addr="rohit.patekar@sbi" name="" seqNum="1" type="" code=""> </Payer> <Payees> <Payee seqNum="1" addr="zeeshan.khan@hdfc" name="Zeeshan Khan" type="PERSON" code="4814"> <Info> <Identity type="ACCOUNT" verifiedName="Zeeshan Khan" id="7389923983430"/> <Rating verifiedAddress="TRUE"/> </Info> <Amount value="4000" curr="INR"> </Amount> </Payee> </Payees> </upi:ReqAuthDetails>

Index Message Item <XML Tag> Occurrence Sample Value

1.1 API Name <upi> 1..1 ReqAuthDetails

1.1.1 API Schema namespace xmlns 1..1 upi="http://npci.org/upi/schema/

2.1 Header for the message <Head> 1..1

2.1.1 Version of the API ver 1..1 1.0

2.1.2 Time of request from the creator of the message

ts 1..1 2015-02-16T22:02:35+05:30

2.1.3 Organization id that created the message

orgId 1..1 400001

2.1.4 Message identifier-used to correlate between request and response

msgId 1..1 NPNSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM

3.1.1 Unique Identifier of the transaction across all entities, created by the originator

id 1..1 9ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM

3.1.2 Description of the transaction(which will be printed on Pass book)

note 1..1 Your taxi trip Bill

Page 83: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS

17/07/2015 Page 83 of 122

Index Message Item <XML Tag> Occurrence Sample Value

3.1.3 Consumer reference number to identify (like Loan number, etc.)

ref 1..1

3.1.4 Transaction origination time by the creator of the message

ts 1..1 2015-02-16T22:02:35+05:30

3.1.5 Type of the Transaction type 1..1 Collect

3.2 Risk Score related to the transaction and the entities

<Txn.RiskScores> 0..1

3.3 Risk Score related to the transaction and the entities

<Txn.RiskScores.Score>

0..1

3.3.1 Entity providing the risk score provider 1..1 psp1

3.3.2 Type of risk type 1..1 TXNRISK

3.3.3 Value of risk evaluation ranging from 0 (No Risk) to 100 (Maximum Risk)

value 1..1 00030

3.4 Rules that govern the payment <Txn.Rules> 0..1

3.5 Rule for the transaction <Txn.Rules.Rule> 0..n

3.5.1 Name of the property Name 1..n EXPIREAFTER

3.5.2 Value of the property Value 1..n 10080

4.1 Details related to the Payer <Payer> 1..1

4.1.1 Address of the Payer Addr 1..1 rohit.patekar@sbi

4.1.2 Name of the Payer Name 1..1

4.1.3 Unique identifier for each transaction inside a file including payer and payee

seqNum 1..1 1

4.1.4 Type of the Payer Type 1..1

4.1.5 Merchant Classification Code -MCC

Code 1..1

5.1 Details related to the Payees <Payees> 1..1

5.2 Details related to the Payee <Payee> 1..1

5.2.1 Address of the Payee Addr 1..1 zeeshan@hdfc

5.2.2 Name of the Payee Name 1..1 Zeeshan Khan

5.2.3 Unique identifier for each transaction inside a file including Payee and payee

seqNum 1..1 1

5.2.4 Type of the Payee Type 1..1 PERSON

5.2.5 Merchant Classification Code –MCC

Code 1..1 4814

6.1 Information related to the Payee <Payee.Info> 1..1

6.2 Payee Identity Is mandatory for “collect” and optional for “pay”

<Payee.Info.Identity> 1..1

6.2.1 Type of the identifier Type 1..1 ACCOUNT

6.2.2 Name as per the identifier verifiedName 1..1 Zeeshan Khan

6.3.3 Id Id 1.1 7389923983430

Page 84: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS

17/07/2015 Page 84 of 122

Index Message Item <XML Tag> Occurrence Sample Value

6.4 Rating of the payee <Rating> 0..1

6.4.1 Payer is whitelisted or not verifiedAddress 1..1 TRUE

6.5 Information related to the amounts in the transaction

<Payee.Amount> 1..1

6.5.1 Transaction amount Value 1..1 4000

6.5.2 Currency of the transaction Curr 1..1 INR

5.5 RespAuthDetails(PSP2 to UPI)

<upi:RespAuthDetails xmlns:upi="http://npci.org/upi/schema/"> <Head ver="1.0" ts="2015-02-16T22:02:48+05:30" orgId="400003" msgId="SBNSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM"/> <Resp reqMsgId="NPNSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM" result="SUCCESS" errCode=""/> <Txn id="9ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM " note="Your Taxi trip Bill" refId=““ refUrl=““ ts="2015-02-16T22:02:35+05:30" type="Collect"> <RiskScores> <Score provider="psp2" type="TXNRISK" value="00030"/> <Score provider="NPCI" type="TXNRISK" value="00030"/> </RiskScores> </Txn> <Payer addr="rohit.patekar@sbi" name="Rohit Patekar" seqNum="1" type="PERSON" code="4814"> <Info> <Identity type="ACCOUNT" verifiedName="rohit.patekar@sbi" id="8392389838"/> <Rating verifiedAddress="TRUE"/> </Info> <Device> <Tag name="MOBILE" value="+91.99999.88888"/> <Tag name="GEOCODE" value="288177"/> <Tag name="LOCATION" value="Mumbai,Maharashtra" /> <Tag name="IP" value="124.170.23.24"/> <Tag name="TYPE" value="mob"/> <Tag name="ID" value="900c6be276f1c4b5c9912b95a5742fc5"/> <Tag name="OS" value="android"/> <Tag name="APP" value="NPCIAPP"/> <Tag name="CAPABILITY" value="5200000200010004000639292929292"/> </Device> <Ac addrType="ACCOUNT"> <Detail name="IFSC" value="UBIN0288100"/> <Detail name="ACTYPE" value="SAVINGS"/> <Detail name="ACNUM" value="5678892001828"/> </Ac> <Creds> <Cred type="PIN" subType="MPIN">

<Data> base-64 encoded and encrypted</Data> #data includes <code><delimeter><Ki>[base 64 encoded]<delimeter><Transaction Id><delimiter><Common library version><delimiter><Captured credential><delimiter><Transaction amount><delimiter><Random number>[encrypted] ,"|" to be used as delimiter

</Cred> <Amount value="4000" curr="INR"> </Amount> </Payer> <Payees>

Page 85: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS

17/07/2015 Page 85 of 122

<Payee addr="Zeeshan.khan@hdfc" name="Zeeshan Khan" seqNum="1" type="PERSON" code="4814"> <Info> <Identity type="ACCOUNT" verifiedName="Zeeshan Khan" id="7389923983430"/> <Rating verifiedAddress="TRUE"/> </Info> <Amount value="4000" curr="INR"> </Amount> </Payee> </Payees> </upi:RespAuthDetails>

Index Message Item <XML Tag> Occurrence Sample Value

1.1 API Name <RespAuthDetails> 1..1 RespAuthDetails

1.1.1 API Schema namespace xmlns 1..1 upi="http://npci.org/upi/schema/

2.1 Header for the message <Head> 1..1

2.1.1 Version of the API ver 1..1 1.0

2.1.2 Time of request from the creator of the message

ts 1..1 2015-02-16T22:02:48+05:30

2.1.3 Organization id that created the message

orgId 1..1 400003

2.1.4 Message identifier-used to correlate between request and response

msgId 1..1 SBNSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM

3.1 Response <Resp> 1..1

3.1.1 Request Message identifier reqMsgId 1..1 NPNSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM

3.1.2 Result of the transaction result 1..1 SUCCESS

3.1.3 Error code if failed errCode 1..1

4.1 Transaction information, Carried throughout the system, visible to all parties

<Txn> 1..1

4.1.1 Unique Identifier of the transaction across all entities created by the originator

id 1..1 1524104355706

4.1.2 Description of the transaction(which will be printed on Pass book)

note 1..1 Your taxi trip Bill

4.1.3 Consumer reference number to identify (like Loan number, etc.)

ref 1..1

4.1.4 Transaction origination time by the creator of the message

ts 1..1 2015-02-16T22:02:35+05:30

4.1.5 Type of the Transaction type 1..1 Collect

4.2 Risk Score related to the transaction and the entities

<Txn.RiskScores> 0..1

4.3 Risk Score related to the transaction and the entities

<Txn.RiskScores.Score>

0..1

4.3.1 Entity providing the risk score provider 1..1 Psp2

4.3.2 Type of risk type 1..1 TXNRISK

4.3.3 Value of risk evaluation ranging from 0 (No Risk) to 100 (Maximum Risk)

value 1..1 00030

5.1 Details related to the Payer <Payer> 1..1

5.1.1 Address of the Payer addr 1..1 rohit.patekar@sbi

5.1.2 Name of the Payer name 1..1 Rohit Patekar

Page 86: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS

17/07/2015 Page 86 of 122

Index Message Item <XML Tag> Occurrence Sample Value

5.1.3 Unique identifier for each transaction inside a file including payer and payee

seqNum 1..1 1

5.1.4 Type of the Payer type 1..1 PERSON

5.1.5 Merchant Classification Code -MCC code 1..1 4814

5.2 Information related to the Payer <Payer.Info> 1..1

5.3 Payer Identity is mandatory for “collect” and optional for “pay”

<Payer.Info.Identity> 1..1

5.3.1 Type of the identifier type 1..1 ACCOUNT

5.3.2 Name as per the identifier verifiedName 1..1 rohit.patekar@sbi 5.3.3 Id Id 1.1 8392389838

5.4 Rating of the payer <Payer.Info.Rating> 0..1

5.4.1 Payer is whitelisted or not verifiedAddress 1..1 TRUE

5.5 Details of Device from which the transaction was initiated

<Payer.Device> 1..1

5.6 Device Tag <Payer.Device.Tag> 1..n

5.6.1 Name of the property name 1..n MOBILE

5.6.2 Value of the property value 1..n +91.99999.00000

5.7 Only one entity is allowed for a payer <Payer.Ac> 1..1

5.7.1 Type of the address addrType 1..1 ACCOUNT

5.8 Details related to Payer Address <Payer.Ac.Detail> 1..n

5.8.1 Name of the property name 1..n ACTYPE

5.8.2 Value of the property value 1..n SAVINGS

5.8.3 Name of the property name 1..n IFSC

5.8.4 Value of the property value 1..n UBIN0288100

5.8.5 Name of the property name 1..n ACNUM

5.8.6 Value of the property value 1..n 5678892001828

5.9 Information related to Payer Credentials

<Payer.Creds> 1..1

5.10 Credentials are used to authenticate the request

<Payer.Creds.Cred> 1..1

5.10.1 Type of financial instrument used for authentication

type 1..1

5.10.2 Subtype of Financial instrument used for authentication

subtype 1.1 NA

5.11 base-64 encoded/encrypted authentication data

<Payer.Creds.Cred.Data>

1..1 Base 64 encoded value of RES|A12345

5.12 Information related to the amounts in the transaction

<Payer.Amount> 1..1

5.12.1 Transaction amount value 1..1 4000

5.12.2 Currency of the transaction curr 1..1 INR

6.2 Details related to the Payee <Payee> 1..1

6.2.1 Address of the Payee addr 1..1 Zeeshan.khan@hdfc

6.2.2 Name of the Payee name 1..1 Zeeshan Khan

6.2.3 Unique identifier for each transaction inside a file including Payee and payee

seqNum 1..1 1

6.2.4 Type of the Payee type 1..1 PERSON

6.2.5 Merchant Classification Code -MCC code 1..1 4814

6.3 Information related to the Payee <Payee.Info> 1..1

6.4 Payee Identity <Payee.Info.Identity> 1..1

6.4.1 Type of the identifier type 1..1 ACCOUNT

6.4.2 Name as per the identifier verifiedName 1..1 Zeeshan Khan

Page 87: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS

17/07/2015 Page 87 of 122

Index Message Item <XML Tag> Occurrence Sample Value

6.4.3 Id Id 1.1 7389923983430

6.5 Information related to the amounts in the transaction

<Payee.Amount> 1..1

6.5.1 Transaction amount value 1..1 4000

6.5.2 Currency of the transaction curr 1..1 INR

5.6 ReqPay_NPCI_DEBIT_REQ(UPI to PAYER BANK)

<upi:ReqPay xmlns:upi="http://npci.org/upi/schema/"> <Head ver="1.0" ts="2015-02-16T22:02:48+05:30" orgId="400001" msgId="HENSVVR4QZS7X1UGCY7JGUV444PL9Z2C3QM"/> <Meta> <Tag name="PAYREQSTART" value="2015-02-16T22:02:00+05:30"/> <Tag name="PAYREQEND" value="2015-02-16T22:02:35+05:30"/> </Meta> <Txn id="9ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM" note="Restaurant Bill " refId="" refUrl="" ts="2015-02-16T22:02:35+05:30" type="DEBIT" orgTxnId=""> <RiskScores> <Score provider="psp1" type="TXNRISK" value="00030"/> <Score provider="npci" type="TXNRISK" value="00030"/> </RiskScores> </Txn> <Payer addr="rohit.patekar@sbi" name="Rohit Patekar" seqNum="1" type="PERSON" code="4814"> <Info> <Identity type="ACCOUNT" verifiedName="rohit.patekar@sbi" id="8392389838"/> <Rating verifiedAddress="TRUE"/> </Info> <Device> <Tag name="MOBILE" value="+91.99999.88888"/> <Tag name="GEOCODE" value="288177"/> <Tag name="LOCATION" value="Mumbai,Maharashtra" /> <Tag name="IP" value="124.170.23.24"/> <Tag name="TYPE" value="mob"/> <Tag name="ID" value="900c6be276f1c4b5c9912b95a5742fc5"/> <Tag name="OS" value="android"/> <Tag name="APP" value="NPCIAPP"/> <Tag name="CAPABILITY" value="5200000200010004000639292929292"/> </Device> <Ac addrType="ACCOUNT"> <Detail name="IFSC" value="UBIN0288100"/> <Detail name="ACTYPE" value="SAVINGS"/> <Detail name="ACNUM" value="5678892001828"/> </Ac> <Creds> <Cred type="PIN" subType="MPIN">

<Data> base-64 encoded and encrypted</Data> #data includes <code><delimeter><Ki>[base 64 encoded]<delimeter><Transaction Id><delimiter><Common library version><delimiter><Captured credential><delimiter><Transaction amount><delimiter><Random number>[encrypted] ,"|" to be used as delimiter

</Cred> <Amount value="4000" curr="INR">

Page 88: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS

17/07/2015 Page 88 of 122

</Amount> </Payer> <Payees> <Payee seqNum="1" addr="zeeshan.khan@hdfc" name="Zeeshan Khan" type="PERSON" code="4814"> <Info> <Identity type="ACCOUNT" verifiedName="Zeeshan Khan" id="7389923983430"/> <Rating verifiedAddress="TRUE"/> </Info> <Ac addrType="ACCOUNT"> <Detail name="IFSC" value="ICIC0288100"/> <Detail name="ACTYPE" value="SAVINGS"/> <Detail name="ACNUM" value="2678892001828"/> </Ac> <Amount value="4000" curr="INR"> </Amount> </Payee> </Payees> </upi:ReqPay>

Index Message Item <XML Tag> Occurrence Sample Value

1.1 API Name <upi> 1..1 ReqPay

1.1.1 API Schema namespace xmlns 1..1 upi="http://npci.org/upi/schema/

2.1 Header for the message <Head> 1..1

2.1.1 Version of the API ver 1..1 1.0

2.1.2 Time of request from the creator of the message

ts 1..1 2015-02-16T22:02:35+05:30

2.1.3 Organization id that created the message

orgId 1..1 400001

2.1.4 Message identifier-used to correlate between request and response

msgId 1..1 HENSVVR4QZS7X1UGPY7JGUV444PL9Z2C3QM

3.1 Meta data primarily for analytics purposes

<Meta> 0..1

3.2 Meta data primarily for analytics purposes

<Meta.Tag> 0..1

3.2.1 Name of the property name 1..n PAYREQSTART

3.2.2 Value of the property value 1..n 2015-02-16T22:02:00+05:30

4.1 Transaction information, Carried throughout the system, visible to all parties

<Txn> 1..1

4.1.1 Unique Identifier of the transaction across all entities, created by the originator

id 1..1 8ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM

4.1.2 Description of the transaction(which will be printed on Pass book)

note 1..1 Restaurant Bill

4.1.3 Consumer reference number to identify (like Loan number, etc.)

refId 1..1

4.1.4 URL for the transaction refUrl 1..1

4.1.5 Transaction origination time by the creator of the message

ts 1..1 2015-02-16T22:02:35+05:30

4.1.6 Type of the Transaction type 1..1 CREDIT

Page 89: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS

17/07/2015 Page 89 of 122

Index Message Item <XML Tag> Occurrence Sample Value

4.1.7 Original transaction ID when reversal/Refund has to be done

orgTxnId 1..1

4.2 Risk Score related to the transaction and the entities

<Txn.RiskScores> 0..1

4.3 Risk Score related to the transaction and the entities

<Txn.RiskScores.Score> 0..1

4.3.1 Entity providing the risk score provider 1..1 psp1

4.3.2 Type of risk type 1..1 TXNRISK

4.3.3 Value of risk evaluation ranging from 0 (No Risk) to 100 (Maximum Risk)

value 1..1 00030

5.1 Details related to the Payer <Payer> 1..1

5.1.1 Address of the Payer addr 1..1 rohit.patekar@sbi

5.1.2 Name of the Payer name 1..1 Rohit Patkar

5.1.3 Unique identifier for each transaction inside a file including payer and payee

seqNum 1..1 1

5.1.4 Type of the Payer type 1..1 PERSON

5.1.5 Merchant Classification Code –MCC

code 1..1 4814

5.2 Information related to the Payer <Payer.Info> 1..1

5.3 Payer Identity Is mandatory for “collect” and optional for “pay”

<Payer.Info.Identity> 1..1

5.3.1 Type of the identifier type 1..1 ACCOUNT

5.3.2 Name as per the identifier verifiedName 1..1 Rohit Patkar

5.3.3. Id Id 1.1 7389923983430

5.4 Rating of the payer <Rating> 0..1

5.4.1 Payer is whitelisted or not verifiedAddress 1..1 TRUE

5.5 Details of Device from which the transaction was initiated

<Payer.Device> 1..1

5.6 Device Tag <Payer.Device.Tag> 1..n

5.6.1 Name of the property name 1..n MOBILE

5.6.2 Value of the property value 1..n +91.99999.00000

5.7 Only one entity is allowed for a payer

<Payer.Ac> 1..1

5.7.1 Type of the address addrType 1..1 ACCOUNT

5.8 Details related to Payer Address <Payer.Ac.Detail> 1..n

5.8.1 Name of the property name 1..n ACTYPE

5.8.2 Value of the property value 1..n SAVINGS

5.8.3 Name of the property name 1..n IFSC

5.8.4 Value of the property value 1..n UBIN0288100

5.8.5 Name of the property name 1..n ACNUM

5.8.6 Value of the property value 1..n 2678892001828

5.9 Information related to Payer Credentials

<Payer.Creds> 1..1

5.10 Credentials are used to authenticate the request

<Payer.Creds.Cred> 1..1

Page 90: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS

17/07/2015 Page 90 of 122

Index Message Item <XML Tag> Occurrence Sample Value

5.10.1 Type of financial instrument used for authentication

Type 1..1 PreApproved

5.10.2 Subtype of Financial instrument used for authentication

subtype 1.1 NA

5.11 base-64 encoded/encrypted authentication data

<Payer.Creds.Cred.Data> 1..1 Base 64 encoded value of RES|A12345

5.12 Information related to the amounts in the transaction

<Payer.Amount> 1..1

5.12.1 Transaction amount Value 1..1 4000

5.12.2 Currency of the transaction Curr 1..1 INR

6.1 Details related to the Payees <Payees> 1..1

6.2 Details related to the Payee <Payee> 1..1

6.2.1 Address of the Payee Addr 1..1 Zeeshan.khan@hdfc

6.2.2 Name of the Payee Name 1..1

6.2.3 Unique identifier for each transaction inside a file including Payee and payee

seqNum 1..1 1

6.2.4 Type of the Payee Type 1..1 PERSON

6.2.5 Merchant Classification Code –MCC

Code 1..1 4814

6.3 Information related to the Payee <Payee.Info> 1..1

6.4 Payee Identity Is mandatory for “collect” and optional for “pay”

<Payee.Info.Identity> 1..1

6.4.1 Type of the identifier type 1..1 ACCOUNT

6.4.2 Name as per the identifier verifiedName 1..1 Zeeshan Khan

6.4.3. Id Id 1.1 8392389838

6.5 Rating of the payee <Rating> 0..1

6.5.1 Payee is whitelisted or not verifiedAddress 1..1 TRUE

6.6 Only one entity is allowed for a payee

<Payee.Ac> 1..1

6.6.1 Type of the address addrType 1..1 ACCOUNT

6.7 Details related to Payee Address <Payee.Ac.Detail> 1..n

6.7.1 Name of the property name 1..n ACTYPE

6.7.2 Value of the property value 1..n SAVINGS

6.7.3 Name of the property name 1..n IFSC

6.7.4 Value of the property value 1..n ICIC0288100

6.7.5 Name of the property name 1..n ACNUM

6.7.6 Value of the property value 1..n 5678892001828

5.7 RespPay_NPCI_DEBIT_REQ_RES(PAYER BANK to UPI)

<upi:RespPay xmlns:upi="http://npci.org/upi/schema/"> <Head ver="1.0" ts="2015-02-16T22:02:54+05:30" orgId="400003" msgId="NENSVVR4QOS7X1UGPY7JGUV424PL9T2C3QN"/> <Txn id="9ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM" note="Restaurant Bill "

Page 91: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS

17/07/2015 Page 91 of 122

refId=““ refUrl=““ ts="2015-02-16T22:02:35+05:30" type="DEBIT"> <RiskScores> <Score provider="psp2" type="TXNRISK" value="00030"/> <Score provider="npci" type="TXNRISK" value="00030"/> </RiskScores> </Txn> <Resp reqMsgId="HENSVVR4QZS7X1UGCY7JGUV444PL9Z2C3QM" result="SUCCESS" errCode=""> <Ref type="PAYEE" seqNum="1" addr="zeeshan.khan@hdfc" settAmount="4000" settCurrency="INR" acNum="2678892001828" approvalNum="" respCode=""/> <Ref type="PAYER" seqNum="1" addr="rohit.patekar@sbi" settAmount="4000" settCurrency="INR" acNum="5678892001828" approvalNum="7786787865" respCode="00"/> </Resp> </upi:RespPay>

Index Message Item <XML Tag> Occurrence Sample Value

1.1 API Name <RespPay> 1..1 RespPay

1.1.1 API Schema namespace xmlns 1..1 upi="http://npci.org/upi/schema/

2.1 Header for the message <Head> 1..1

2.1.1 Version of the API ver 1..1 1.0

2.1.2 Time of request from the creator of the message

ts 1..1 2015-02-16T22:02:48+05:30

2.1.3 Organization id that created the message

orgId 1..1 400002

2.1.4 Message identifier-used to correlate between request and response

msgId 1..1 NENSVVR4QOS7X1UGPY7JGUV424PL9T2C3QM

3.1 Transaction information, Carried throughout the system, visible to all parties

<Txn> 1..1

3.1.1 Unique Identifier of the transaction across all entities created by the originator

id 1..1 8ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM

3.1.2 Description of the transaction(which will be printed on Pass book)

note 1..1 Restaurant Bill

3.1.3 Consumer reference number to identify (like Loan number, etc.)

refId 1..1

3.1.4 URL for the transaction refUrl 1..1

3.1.5 Transaction origination time by the creator of the message

ts 1..1 2015-02-16T22:02:35+05:30

3.1.6 Type of the Transaction type 1..1 CREDIT

3.2 Risk Score related to the transaction and the entities

<Txn.RiskScores> 0..1

3.3 Risk Score related to the transaction and the entities

<Txn.RiskScores.Score>

0..1

3.3.1 Entity providing the risk score provider 1..1 psp1

3.3.2 Type of risk type 1..1 TXNRISK

3.3.3 Value of risk evaluation ranging from 0 (No Risk) to 100 (Maximum Risk)

value 1..1 00030

3.4 Response <Resp> 1..1

3.4.1 Request Message identifier reqMsgId 1..1 HENSVVR4QZS7X1UGPY7JGUV444PL9Z2C3QM

3.4.2 Result of the transaction result 1..1 SUCCESS

3.4..3 Error code if failed errCode 1..1

Page 92: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS

17/07/2015 Page 92 of 122

Index Message Item <XML Tag> Occurrence Sample Value

3.5 Response Reference <Ref> 1..n

3.5.1 Customer type type 1..1 PAYER

3.5.2 Sequence Number seqNum 1..1 1

3.5.3 Payment address addr 1..1 zeeshan.khan@hdfc

3.5.4 Settlement Amount settAmount 1..1 4000

3.5.5 Settlement Currency settCurrency 1..1 INR

3.5.6 Approval Reference Number approvalNum 1..1 9399389827

3.5.7 Response code respCode 1..1 00

5.8 ReqPay_NPCI_CREDIT_REQ(UPI to PAYEE BANK)

<upi:ReqPay xmlns:upi="http://npci.org/upi/schema/"> <Head ver="1.0" ts="2015-02-16T22:02:35+05:30" orgId="400001" msgId="HENSVVR4QZS7X1UGPY7JGUV424PL9Z2C3QM"/> <Meta> <Tag name="PAYREQSTART" value="2015-02-16T22:02:00+05:30"/> <Tag name="PAYREQEND" value="2015-02-16T22:02:35+05:30"/> </Meta> <Txn id="9ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM" note="Your Taxi trip Bill " refId="" refUrl="" ts="2015-02-16T22:02:35+05:30" type="CREDIT" orgTxnId=""> <RiskScores> <Score provider="psp1" type="TXNRISK" value="00030"/> <Score provider="npci" type="TXNRISK" value="00030"/> </RiskScores> </Txn> <Payer addr="rohit.patekar@sbi" name="Rohit Patekar" seqNum="1" type="PERSON" code="4814"> <Info> <Identity type="ACCOUNT" verifiedName="rohit.patekar@sbi" id="8392389838"/> <Rating verifiedAddress="TRUE"/> </Info> <Device> <Tag name="MOBILE" value="+91.99999.88888"/> <Tag name="GEOCODE" value="288177"/> <Tag name="LOCATION" value="Mumbai,Maharashtra" /> <Tag name="IP" value="124.170.23.24"/> <Tag name="TYPE" value="mob"/> <Tag name="ID" value="900c6be276f1c4b5c9912b95a5742fc5"/> <Tag name="OS" value="android"/> <Tag name="APP" value="NPCIAPP"/> <Tag name="CAPABILITY" value="5200000200010004000639292929292"/> </Device> <Ac addrType="ACCOUNT"> <Detail name="IFSC" value="SBIN0288100"/> <Detail name="ACTYPE" value="SAVINGS"/> <Detail name="ACNUM" value="5678892001828"/> </Ac> <Creds> <Cred type="PreApproved" subType="NA">

Page 93: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS

17/07/2015 Page 93 of 122

<Data> base-64 encoded</Data> #data includes respCode and approvalRef RES|A12345 </Cred> </Creds> <Amount value="4000" curr="INR"> </Amount> </Payer> <Payees> <Payee seqNum="1" addr="zeeshan.khan@hdfc" name="Zeeshan Khan" type="PERSON" code="4814"> <Info> <Identity type="ACCOUNT" verifiedName="Zeeshan Khan" id="7389923983430"/> <Rating verifiedAddress="TRUE"/> </Info> <Ac addrType="ACCOUNT"> <Detail name="IFSC" value="ICIC0288100"/> <Detail name="ACTYPE" value="SAVINGS"/> <Detail name="ACNUM" value="2678892001828"/> </Ac> <Amount value="4000" curr="INR"> </Amount> </Payee> </Payees> </upi:ReqPay>

Index Message Item <XML Tag> Occurrence Sample Value

1.1 API Name <upi> 1..1 ReqPay

1.1.1 API Schema namespace Xmlns 1..1 upi="http://npci.org/upi/schema/

2.1 Header for the message <Head> 1..1

2.1.1 Version of the API Ver 1..1 1.0

2.1.2 Time of request from the creator of the message

Ts 1..1 2015-02-16T22:02:35+05:30

2.1.3 Organization id that created the message

orgId 1..1 400001

2.1.4 Message identifier-used to correlate between request and response

msgId 1..1 HENSVVR4QZS7X1UGPY7JGUV424PL9Z2C3QM

3.1 Meta data primarily for analytics purposes

<Meta> 0..1

3.2 Meta data primarily for analytics purposes

<Meta.Tag> 0..1

3.2.1 Name of the property Name 1..n PAYREQSTART

3.2.2 Value of the property Value 1..n 2015-02-16T22:02:00+05:30

4.1 Transaction information, Carried throughout the system, visible to all parties

<Txn> 1..1

4.1.1 Unique Identifier of the transaction across all entities, created by the originator

Id 1..1 9ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM

Page 94: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS

17/07/2015 Page 94 of 122

Index Message Item <XML Tag> Occurrence Sample Value

4.1.2 Description of the transaction(which will be printed on Pass book)

Note 1..1 Your taxi trip Bill

4.1.3 Consumer reference number to identify (like Loan number, etc.)

refId 1..1

4.1.4 URL for the transaction refUrl 1..1

4.1.5 Transaction origination time by the creator of the message

Ts 1..1 2015-02-16T22:02:35+05:30

4.1.6 Type of the Transaction Type 1..1 CREDIT

4.1.7 Original transaction ID when reversal/Refund has to be done

orgTxnId 1..1

4.2 Risk Score related to the transaction and the entities

<Txn.RiskScores> 0..1

4.3 Risk Score related to the transaction and the entities

<Txn.RiskScores.Score>

0..1

4.3.1 Entity providing the risk score provider 1..1 psp1

4.3.2 Type of risk Type 1..1 TXNRISK

4.3.3 Value of risk evaluation ranging from 0 (No Risk) to 100 (Maximum Risk)

Value 1..1 00030

5.1 Details related to the Payer <Payer> 1..1

5.1.1 Address of the Payer Addr 1..1 rohit.patekar@sbi

5.1.2 Name of the Payer Name 1..1 Rohit Patekar

5.1.3 Unique identifier for each transaction inside a file including payer and payee

seqNum 1..1 1

5.1.4 Type of the Payer Type 1..1 PERSON

5.1.5 Merchant Classification Code -MCC

Code 1..1 4814

5.2 Information related to the Payer <Payer.Info> 1..1

5.3 Payer Identity Is mandatory for “collect” and optional for “pay”

<Payer.Info.Identity>

1..1

5.3.1 Type of the identifier type 1..1 ACCOUNT

5.3.2 Name as per the identifier verifiedName 1..1 rohit.patekar@sbi

5.3.3. Id Id 1.1 8392389838

5.4 Rating of the payer <Rating> 0..1

5.4.1 Payer is whitelisted or not verifiedAddress 1..1 TRUE

5.5 Details of Device from which the transaction was initiated

<Payer.Device> 1..1

5.6 Device Tag <Payer.Device.Tag> 1..n

5.6.1 Name of the property Name 1..n MOBILE

5.6.2 Value of the property Value 1..n +91.99999.00000

5.7 Only one entity is allowed for a payer

<Payer.Ac> 1..1

5.7.1 Type of the address addrType 1..1 ACCOUNT

5.8 Details related to Payer Address <Payer.Ac.Detail> 1..n

5.8.1 Name of the property name 1..n ACTYPE

Page 95: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS

17/07/2015 Page 95 of 122

Index Message Item <XML Tag> Occurrence Sample Value

5.8.2 Value of the property value 1..n SAVINGS

5.8.3 Name of the property name 1..n IFSC

5.8.4 Value of the property value 1..n SBIN0288100

5.8.5 Name of the property name 1..n ACNUM

5.8.6 Value of the property value 1..n 5678892001828

5.9 Information related to Payer Credentials

<Payer.Creds> 1..1

5.10 Credentials are used to authenticate the request

<Payer.Creds.Cred> 1..1

5.10.1 Type of financial instrument used for authentication

type 1..1 PreApproved

5.10.2 Subtype of Financial instrument used for authentication

subtype 1.1 NA

5.11 base-64 encoded/encrypted authentication data

<Payer.Creds.Cred.Data>

1..1 Base 64 encoded value of RES|A12345

5.12 Information related to the amounts in the transaction

<Payer.Amount> 1..1

5.12.1 Transaction amount value 1..1 4000

5.12.2 Currency of the transaction curr 1..1 INR

5.13 Information if the debit is already authorized

0.1

5.13.1 Response Code respCode 1.1 00

5.13.2 Approval Reference approvalRef 1.1 7786787860

6.1 Details related to the Payees <Payees> 1..1

6.2 Details related to the Payee <Payee> 1..1

6.2.1 Address of the Payee addr 1..1 Zeeshan.khan@hdfc

6.2.2 Name of the Payee name 1..1 Zeeshan Khan

6.2.3 Unique identifier for each transaction inside a file including Payee and payee

seqNum 1..1 1

6.2.4 Type of the Payee type 1..1 PERSON

6.2.5 Merchant Classification Code –MCC

code 1..1 4814

7.1 Information related to the Payee <Payee.Info> 1..1

7.2 Payee Identity Is mandatory for “collect” and optional for “pay”

<Payee.Info.Identity>

1..1

7.2.1 Type of the identifier type 1..1 ACCOUNT

7.2.2 Name as per the identifier verifiedName 1..1 Zeeshan Khan

7.3.3 Id Id 1.1 7389923983430

7.4 Rating of the payee <Rating> 0..1

7.4.1 Payer is whitelisted or not verifiedAddress 1..1 TRUE

7.5 Only one entity is allowed for a payee

<Payee.Ac> 1..1

7.5.1 Type of the address addrType 1..1 ACCOUNT

7.6 Details related to Payee Address <Payee.Ac.Detail> 1..n

7.6.1 Name of the property name 1..n ACTYPE

7.6.2 Value of the property value 1..n SAVINGS

Page 96: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS

17/07/2015 Page 96 of 122

Index Message Item <XML Tag> Occurrence Sample Value

7.6.3 Name of the property name 1..n IFSC

7.6.4 Value of the property value 1..n HDFC0288100

7.6.5 Name of the property name 1..n ACNUM

7.6.6 Value of the property value 1..n 2678892001828

7.7 Information related to the amounts in the transaction

<Payee.Amount> 1..1

7.7.1 Transaction amount value 1..1 4000

7.7.2 Currency of the transaction curr 1..1 INR

5.9 RespPay_NPCI_CREDIT_REQ_RES(PAYEE BANK to UPI)

<upi:RespPay xmlns:upi="http://npci.org/upi/schema/"> <Head ver="1.0" ts="2015-02-16T22:02:48+05:30" orgId="400002" msgId="NENSVVR4QOS7X1UGPY7JGUV424PL9T2C3QM"/> <Txn id="8ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM" note="Your Taxi trip Bill " refId=““ refUrl=““ ts="2015-02-16T22:02:35+05:30" type="CREDIT"> <RiskScores> <Score provider="psp2" type="TXNRISK" value="00030"/> <Score provider="npci" type="TXNRISK" value="00030"/> </RiskScores> </Txn> <Resp reqMsgId="HENSVVR4QZS7X1UGPY7JGUV424PL9Z2C3QM" result="SUCCESS" errCode=""> <Ref type="PAYEE" seqNum="1" addr="zeeshan.khan@hdfc" settAmount="4000"

settCurrency="INR" acNum="2678892001828" approvalNum="9399389827" respCode="00"/>

<Ref type="PAYER" seqNum="1" addr="rohit.patekar@sbi" settAmount="4000" settCurrency="INR" acNum="5678892001828" approvalNum="7786787865" respCode="00"/>

</Resp> </upi:RespPay>

Index Message Item <XML Tag> Occurrence Sample Value

1.1 API Name <RespPay> 1..1 RespPay

1.1.1 API Schema namespace xmlns 1..1 upi="http://npci.org/upi/schema/

2.1 Header for the message <Head> 1..1

2.1.1 Version of the API ver 1..1 1.0

2.1.2 Time of request from the creator of the message

ts 1..1 2015-02-16T22:02:48+05:30

2.1.3 Organization id that created the message

orgId 1..1 400002

2.1.4 Message identifier-used to correlate between request and response

msgId 1..1 NENSVVR4QOS7X1UGPY7JGUV424PL9T2C3QM

3.1 Transaction information, Carried throughout the system, visible to all parties

<Txn> 1..1

3.1.1 Unique Identifier of the transaction across all entities created by the originator

id 1..1 8ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM

3.1.2 Description of the transaction(which will be printed on Pass book)

note 1..1 Your Taxi trip Billl

Page 97: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS

17/07/2015 Page 97 of 122

Index Message Item <XML Tag> Occurrence Sample Value

3.1.3 Consumer reference number to identify (like Loan number, etc.)

refId 1..1

3.1.4 URL for the transaction refUrl 1..1

3.1.5 Transaction origination time by the creator of the message

ts 1..1 2015-02-16T22:02:35+05:30

3.1.6 Type of the Transaction type 1..1 CREDIT

3.2 Risk Score related to the transaction and the entities

<Txn.RiskScores> 0..1

3.3 Risk Score related to the transaction and the entities

<Txn.RiskScores.Score>

0..1

3.3.1 Entity providing the risk score provider 1..1 Psp2

3.3.2 Type of risk type 1..1 TXNRISK

3.3.3 Value of risk evaluation ranging from 0 (No Risk) to 100 (Maximum Risk)

value 1..1 00030

3.4 Response <Resp> 1..1

3.4.1 Request Message identifier reqMsgId 1..1 HENSVVR4QZS7X1UGPY7JGUV424PL9Z2C3QM

3.4.2 Result of the transaction result 1..1 SUCCESS

3.4..3 Error code if failed errCode 1..1

3.5 Response Reference <Ref> 1..n

3.5.1 Customer type type 1..1 PAYEE

3.5.2 Sequence Number seqNum 1..1 1

3.5.3 Payment address addr 1..1 zeeshan.khan@hdfc

3.5.4 Settlement Amount settAmount 1..1 4000

3.5.5 Settlement Currency settCurrency 1..1 INR

3.5.6 Approval Reference Number approvalNum 1..1 9399389827

3.5.7 Response code respCode 1..1 00

5.10 RespPay(UPI to PSP1)

<upi:RespPay xmlns:upi="http://npci.org/upi/schema/"> <Head ver="1.0" ts="2015-02-16T22:02:52+05:30" orgId="400001" msgId="NPCSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM"/> <Txn id="9ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM" note="Your Taxi Trip Bill " refId=““ refUrl=““ ts="2015-02-16T22:02:35+05:30" type="Collect"> <RiskScores> <Score provider="psp2" type="TXNRISK" value="00030"/> <Score provider="npci" type="TXNRISK" value="00030"/> </RiskScores> </Txn> <Resp reqMsgId="HDNSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM" result="SUCCESS" errCode=""> <Ref type="PAYER" seqNum="1" addr="rohit.patekar@sbi" settAmount="4000" settCurrency="INR" approvalNum="9399389827" respCode="00"/> # this will indicate that debit has happened <Ref type="PAYEE" seqNum="1" addr="zeeshan.khan@hdfc" settAmount="4000" settCurrency="INR" approvalNum="" respCode=""/> # PAYEE PSP will do the credit and complete the transaction. </Resp> </upi:RespPay>

Index Message Item <XML Tag> Occurrence Sample Value

1.1 API Name <RespPay> 1..1 RespPay

Page 98: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS

17/07/2015 Page 98 of 122

Index Message Item <XML Tag> Occurrence Sample Value

1.1.1 API Schema namespace xmlns 1..1 upi="http://npci.org/upi/schema/

2.1 Header for the message <Head> 1..1

2.1.1 Version of the API ver 1..1 1.0

2.1.2 Time of request from the creator of the message

ts 1..1 2015-02-16T22:02:52+05:30

2.1.3 Organization id that created the message

orgId 1..1 400001

2.1.4 Message identifier-used to correlate between request and response

msgId 1..1 NPCSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM

3.1 Transaction information, Carried throughout the system, visible to all parties

<Txn> 1..1

3.1.1 Unique Identifier of the transaction across all entities created by the originator

id 1..1 9ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM

3.1.2 Description of the transaction(which will be printed on Pass book)

note 1..1 Your Taxi trip Bill

3.1.3 Consumer reference number to identify (like Loan number, etc.)

refId 1..1

3.1.4 URL for the transaction refUrl 1..1

3.1.5 Transaction origination time by the creator of the message

ts 1..1 2015-02-16T22:02:35+05:30

3.1.6 Type of the Transaction type 1..1 Collect

3.2 Risk Score related to the transaction and the entities

<Txn.RiskScores> 0..1

3.3 Risk Score related to the transaction and the entities

<Txn.RiskScores.Score>

0..1

3.3.1 Entity providing the risk score provider 1..1 Psp2

3.3.2 Type of risk type 1..1 TXNRISK

3.3.3 Value of risk evaluation ranging from 0 (No Risk) to 100 (Maximum Risk)

value 1..1 00030

3.4 Response <Resp> 1..1

3.4.1 Request Message identifier reqMsgId 1..1 HDNSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM

3.4.2 Result of the transaction result 1..1 SUCCESS

3.4..3 Error code if failed errCode 1..1

3.5 Response Reference <Ref> 1..n

3.5.1 Customer type type 1..1 PAYER

3.5.2 Sequence Number seqNum 1..1 1

3.5.3 Payment address addr 1..1 rohit.patekar@sbi

3.5.4 Settlement Amount settAmount 1..1 4000

3.5.5 Settlement Currency settCurrency 1..1 INR

3.5.6 Approval Reference Number approvalNum 1..1 9399389827

3.5.7 Response code respCode 1..1 00

Page 99: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS

17/07/2015 Page 99 of 122

5.11 ReqTxnConfirmation(UPI to PAYER BANK)

<upi:ReqTxnConfirmation xmlns:upi="http://npci.org/upi/schema/"> <Head ver="1.0" ts="2015-02-16T22:03:00+05:30" orgId="400001" msgId="HPDSFVC2QOS7X1UGPY2JGUV454YC8T2C6QM"/> <Txn id="8ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM" note="Restaurant Bill" refId=““ refUrl=““ ts="2015-02-16T22:02:35+05:30" type="TxnConfirmation" orgTxnId="9ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM" /> <TxnConfirmation note="Restaurant Bill" orgStatus="SUCCESS" orgErrCode=”” type="COLLECT" orgTxnId="9ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM" />

</upi:ReqTxnConfirmation>

5.12 RespTxnConfirmation(PAYER BANK to UPI)

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

<Head ver="1.0" ts="2015-02-16T22:03:01+05:30" orgId="400003" msgId="HPDSFVC2ZOS7X1UGPY2JGUV494ZC8T2C6QM"/> <Txn id="HPDSFVC2QOS7X1UGPY2JGUV458PL8T2C6QM" note="Restaurant Bill" refId=““ refUrl=““ ts="2015-02-16T22:02:35+05:30" type="TxnConfirmation" orgTxnId="9ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM" /> <Resp reqMsgId="HPDSFVC2QOS7X1UGPY2JGUV454YL8T2C6QM" result="SUCCESS" errCode=""/>

</upi:RespTxnConfirmation>

Page 100: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS

17/07/2015 Page 100 of 122

Page 101: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS

17/07/2015 Page 101 of 122

CASE 6

FOUR PARTY MODEL – Pay Request [Payer PSP, Remitter/PAYER Bank and Payee

PSP & Beneficiary/PAYEE Bank]

6.1 Flow:

1. Customer initiates a pay Request by entering the Virtual Address of the Payee

customer.

2. Payer PSP sends the ReqPay message to UPI

3. UPI sends ReqAuthDetails message to the respective Payee PSP.

4. Payee PSP validates the Address and responds back with the financial address of the Payee in the RespAuthDetails message to UPI.

5. UPI sends a debit request to Payer BANK 6. Payer BANK debits the account of the customer and responds back to UPI 7. UPI sends a credit request to the Beneficiary Bank based on the financial

address of the Payee 8. Beneficiary Bank credits the customer’s account and responds back with

successful credit to UPI 9. UPI sends a successful confirmation to the Payer PSP 10. UPI Sends ReqTxnConfirmation message to Payee PSP 11. Payer PSP sends the confirmation to the customer.

Page 102: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS

17/07/2015 Page 102 of 122

6.2 ReqPay (PSP1 to UPI System)

<upi:ReqPay xmlns:upi="http://npci.org/upi/schema/"> <Head ver="1.0" ts="2015-02-16T22:02:35+05:30" orgId="400002" msgId="HENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM"/> <Meta> <Tag name="PAYREQSTART" value="2015-02-16T22:02:00+05:30"/> <Tag name="PAYREQEND" value="2015-02-16T22:02:35+05:30"/> </Meta> <Txn id="8ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM" note="Restaurant Bill " refId="" refUrl="" ts="2015-02-16T22:02:35+05:30" type="PAY" orgTxnId=""> <RiskScores> <Score provider="psp1" type="TXNRISK" value="00030"/> </RiskScores> </Txn> <Payer addr="zeeshan.khan@hdfc" name="Zeeshan Khan" seqNum="1" type="PERSON" code="4814"> <Info> <Identity type="ACCOUNT" verifiedName="Zeeshan Khan" id="7389923983430"/> <Rating verifiedAddress="TRUE"/> </Info> <Device> <Tag name="MOBILE" value="+91.99999.00000"/> <Tag name="GEOCODE" value="288177"/> <Tag name="LOCATION" value="Mumbai,Maharashtra" /> <Tag name="IP" value="124.170.23.22"/> <Tag name="TYPE" value="mob"/> <Tag name="ID" value="750c6be243f1c4b5c9912b95a5742fc5"/> #device advertising id <Tag name="OS" value="android"/> <Tag name="APP" value="NPCIAPP"/> <Tag name="CAPABILITY" value="5200000200010004000639292929292"/> </Device> <Ac addrType="ACCOUNT"> <Detail name="ACTYPE" value="SAVINGS"/> <Detail name="IFSC" value="ICIC0288100"/> <Detail name="ACNUM" value="2678892001828"/> </Ac> <Creds> <Cred type="PIN" subType="MPIN">

<Data> base-64 encoded and encrypted</Data> #data includes <code><delimeter><Ki>[base 64 encoded]<delimeter><Transaction Id><delimiter><Common library version><delimiter><Captured credential><delimiter><Transaction amount><delimiter><Random number>[encrypted] ,"|" to be used as delimiter and order of the elements should be same.

</Cred> </Creds> <Amount value="4000" curr="INR"> </Amount> </Payer> <Payees> <Payee addr="rohit.patekar@sbi" name="" seqNum="1" type="" code=""> </Payee> </Payees> </upi:ReqPay>

Page 103: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS

17/07/2015 Page 103 of 122

Index Message Item <XML Tag> Occurrence Sample Value

1.1 API Name <upi> 1..1 ReqPay

1.1.1 API Schema namespace Xmlns 1..1 upi="http://npci.org/upi/schema/

2.1 Header for the message <Head> 1..1

2.1.1 Version of the API Ver 1..1 1.0

2.1.2 Time of request from the creator of the message

Ts 1..1 2015-02-16T22:02:35+05:30

2.1.3 Organization id that created the message

orgId 1..1 400002

2.1.4 Message identifier-used to correlate between request and response

msgId 1..1 HENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM

3.1 Meta data primarily for analytics purposes

<Meta> 0..1

3.2 Meta data primarily for analytics purposes

<Meta.Tag> 0..1

3.2.1 Name of the property Name 1..n PAYREQSTART

3.2.2 Value of the property Value 1..n 2015-02-16T22:02:00+05:30

4.1 Transaction information, Carried throughout the system, visible to all parties

<Txn> 1..1

4.1.1 Unique Identifier of the transaction across all entities, created by the originator

Id 1..1 8ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM

4.1.2 Description of the transaction(which will be printed on Pass book)

Note 1..1 Restaurant Bill

4.1.3 Consumer reference number to identify (like Loan number, etc.)

refId 1..1

4.1.4 URL for the transaction refUrl 1..1

4.1.5 Transaction origination time by the creator of the message

Ts 1..1 2015-02-16T22:02:35+05:30

4.1.6 Type of the Transaction Type 1..1 PAY

4.1.7 Original transaction ID when reversal/Refund has to be done

orgTxnId 1..1

4.2 Risk Score related to the transaction and the entities

<Txn.RiskScores> 0..1

4.3 Risk Score related to the transaction and the entities

<Txn.RiskScores.Score> 0..1

4.3.1 Entity providing the risk score provider 1..1 psp1

4.3.2 Type of risk Type 1..1 TXNRISK

4.3.3 Value of risk evaluation ranging from 0 (No Risk) to 100 (Maximum Risk)

Value 1..1 00030

5.1 Details related to the Payer <Payer> 1..1

5.1.1 Address of the Payer Addr 1..1 zeeshan.khan@hdfc

5.1.2 Name of the Payer Name 1..1 Zeeshan Khan

5.1.3 Unique identifier for each transaction inside a file including payer and payee

seqNum 1..1 1

Page 104: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS

17/07/2015 Page 104 of 122

5.1.4 Type of the Payer Type 1..1 PERSON

5.1.5 Merchant Classification Code -MCC

Code 1..1 4814

5.2 Information related to the Payer <Payer.Info> 1..1

5.3 Payer Identity Is mandatory for “collect” and optional for “pay”

<Payer.Info.Identity> 1..1

5.3.1 Type of the identifier Type 1..1 ACCOUNT

5.3.2 Name as per the identifier verifiedName 1..1 Zeeshan Khan

5.3.3. Id Id 1.1 7389923983430

5.4 Rating of the payer <Rating> 0..1

5.4.1 Payer is whitelisted or not verifiedAddress 1..1 TRUE

5.5 Details of Device from which the transaction was initiated

<Payer.Device> 1..1

5.6 Device Tag <Payer.Device.Tag> 1..n

5.6.1 Name of the property Name 1..n MOBILE

5.6.2 Value of the property Value 1..n +91.99999.00000

5.7 Only one entity is allowed for a payer

<Payer.Ac> 1..1

5.7.1 Type of the address addrType 1..1 ACCOUNT

5.8 Details related to Payer Address <Payer.Ac.Detail> 1..n

5.8.1 Name of the property Name 1..n ACTYPE

5.8.2 Value of the property Value 1..n SAVINGS

5.8.3 Name of the property Name 1..n IFSC

5.8.4 Value of the property Value 1..n ICIC0288100

5.8.5 Name of the property Name 1..n ACNUM

5.8.6 Value of the property Value 1..n 2678892001828

5.9 Information related to Payer Credentials

<Payer.Creds> 1..1

5.10 Credentials are used to authenticate the request

<Payer.Creds.Cred> 1..1

5.10.1 Type of financial instrument used for authentication

Type 1..1 PreApproved

5.10.2 Subtype of Financial instrument used for authentication

subtype 1.1 NA

5.11 base-64 encoded/encrypted authentication data

<Payer.Creds.Cred.Data>

1..1 Base 64 encoded value of RES|A12345

5.12 Information related to the amounts in the transaction

<Payer.Amount> 1..1

5.12.1 Transaction amount Value 1..1 4000

5.12.2 Currency of the transaction Curr 1..1 INR

6.1 Details related to the Payees <Payees> 1..1

6.2 Details related to the Payee <Payee> 1..1

6.2.1 Address of the Payee Addr 1..1 rohit.patekar@sbi

6.2.2 Name of the Payee Name 1..1

6.2.3 Unique identifier for each transaction inside a file including Payee and payee

seqNum 1..1 1

6.2.4 Type of the Payee Type 1..1

Page 105: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS

17/07/2015 Page 105 of 122

6.3 MSG_ACK(to be sent for every message)

<upi:Ack xmlns:upi="" api="" reqMsgId="" err="" ts=""/>

6.4 ReqAuthDetails(UPI to PSP2)

<upi:ReqAuthDetails xmlns:upi="http://npci.org/upi/schema/"> <Head ver="1.0" ts="2015-02-16T22:02:40+05:30" orgId="400001" msgId="NPNSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM"/> <Txn id="8ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM" note="Restaurant Bill " refId=““ refUrl=““ ts="2015-02-16T22:02:35+05:30" type="PAY"> <RiskScores> <Score provider="psp1" type="TXNRISK" value="00030"/> <Score provider="NPCI" type="TXNRISK" value="00030"/> </RiskScores> </Txn> <Payer addr="zeeshan.khan@hdfc" name="Zeeshan Khan" seqNum="1" type="PERSON" code="4814"> <Info> <Identity type="ACCOUNT" verifiedName="Zeeshan Khan" id="7389923983430"/> <Rating verifiedAddress="TRUE"/> </Info> <Amount value="4000" curr="INR"> </Amount> </Payer> <Payees> <Payee addr="rohit.patekar@sbi" name="" seqNum="1" type="" code=""> </Payee> </Payees> </upi:ReqAuthDetails>

Index Message Item <XML Tag> Occurrence

Sample Value

1.1 API Name <ReqAuthDetails> 1..1 ReqAuthDetails

1.1.1 API Schema namespace xmlns 1..1 upi="http://npci.org/upi/schema

2.1 Header for the message <Head> 1..1

2.1.1 Version of the API ver 1..1 1

2.1.2 Time of request from the creator of the message

ts 1..1 2015-02-16T22:02:45+05:30

2.1.3 Organization id that created the message

orgId 1..1 400001

2.1.4 Message identifier-used to correlate between request and response

msgId 1..1 NPNSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM

3.1 Transaction information, Carried throughout the system, visible to all parties

<Txn> 1..1

6.2.5 Merchant Classification Code -MCC

Code 1..1

Page 106: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS

17/07/2015 Page 106 of 122

Index Message Item <XML Tag> Occurrence

Sample Value

3.1.1 Unique Identifier of the transaction across all entities created by the originator

id 1..1 8ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM

3.1.2 Description of the transaction(which will be printed on Pass book)

note 1..1 Restaurant Bill

3.1.3 Consumer reference number to identify (like Loan number, etc.)

ref 1..1

3.1.4 Transaction origination time by the creator of the message

ts 1..1 2015-02-16T22:02:35+05:30

3.1.5 Type of the Transaction type 1..1 PAY

3.2 Risk Score related to the transaction and the entities

<Txn.RiskScores> 0..1

3.3 Risk Score related to the transaction and the entities

<Txn.RiskScores.Score> 0..1

3.3.1 Entity providing the risk score provider 1..1 Psp2

3.3.2 Type of risk type 1..1 TXNRISK

3.3.3 Value of risk evaluation ranging from 0 (No Risk) to 100 (Maximum Risk)

value 1..1 00030

4.1 Details related to the Payer <Payer> 1..1

4.1.1 Address of the Payer addr 1..1 zeeshan.khan@hdfc

4.1.2 Name of the Payer name 1..1 Zeeshan Khan

4.1.3 Unique identifier for each transaction inside a file including payer and payee

seqNum 1..1 1

4.1.4 Type of the Payer type 1..1 PERSON

4.1.5 Merchant Classification Code -MCC

code 1..1 4814

4.2 Information related to the Payer <Payer.Info> 1..1

4.3 Payer Identity is mandatory for “collect” and optional for “pay”

<Payer.Info.Identity> 1..1

4.3.1 Type of the identifier type 1..1 ACCOUNT

4.3.2 Name as per the identifier verifiedName 1..1 Zeeshan Khan

4.3.3 Identifier Id 1.1 7389923983430

4.4 Rating of the payer <Payer.Info.Rating> 0..1

4.4.1 Payer is whitelisted or not verifiedAddress 1..1 TRUE

4.5 Information related to the amounts in the transaction

<Payer.Amount> 1..1

4.5.1 Transaction amount value 1..1 4000

4.5.2 Currency of the transaction curr 1..1 INR

6.1 Details related to the Payees <Payees> 1..1

6.2 Details related to the Payee <Payee> 1..1

6.2.1 Address of the Payee addr 1..1 rohit.patekar@sbi

6.2.2 Name of the Payee name 1..1

6.2.3 Unique identifier for each transaction inside a file including Payee and payee

seqNum 1..1 1

6.2.4 Type of the Payee type 1..1

6.2.5 Merchant Classification Code -MCC

code 1..1

Page 107: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS

17/07/2015 Page 107 of 122

6.5 RespAuthDetails(PSP2 to UPI)

<upi:RespAuthDetails xmlns:upi="http://npci.org/upi/schema/"> <Head ver="1.0" ts="2015-02-16T22:02:45+05:30" orgId="400003" msgId="SBNSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM"/> <Resp reqMsgId="NPNSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM" result="SUCCESS" errCode=""/> <Txn id="8ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM" note="Restaurant Bill " refId=““ refUrl=““ ts="2015-02-16T22:02:35+05:30" type="PAY"> <RiskScores> <Score provider="psp2" type="TXNRISK" value="00030"/> <Score provider="NPCI" type="TXNRISK" value="00030"/> </RiskScores> </Txn> <Payer addr="zeeshan.khan@hdfc" name="Zeeshan Khan" seqNum="1" type="PERSON" code="4814"> <Info> <Identity type="ACCOUNT" verifiedName="Zeeshan Khan" id="7389923983430"/> <Rating verifiedAddress="TRUE"/> </Info> <Amount value="4000" curr="INR"> </Amount> </Payer> <Payees> <Payee addr="rohit.patekar@sbi" name="Rohit Patekar" seqNum="1" type="PERSON" code="4814"> #mcc has to be populated <Info> <Identity type="ACCOUNT" verifiedName="Rohit Patekar" id="8392389838"/> <Rating verifiedAddress="TRUE"/> </Info> <Ac addrType="ACCOUNT"> <Detail name="IFSC" value="UBIN0288100"/> <Detail name="ACTYPE" value="SAVINGS"/> <Detail name="ACNUM" value="5678892001828"/> </Ac> <Amount value="4000" curr="INR"> </Amount> </Payee> </Payees> </upi:RespAuthDetails>

Index Message Item <XML Tag> Occurrence Sample Value

1.1 API Name <RespAuthDetails> 1..1 RespAuthDetails

1.1.1 API Schema namespace xmlns 1..1 upi="http://npci.org/upi/schema/

2.1 Header for the message <Head> 1..1

2.1.1 Version of the API ver 1..1 1.0

2.1.2 Time of request from the creator of the message

ts 1..1 2015-02-16T22:02:45+05:30

Page 108: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS

17/07/2015 Page 108 of 122

Index Message Item <XML Tag> Occurrence Sample Value

2.1.3 Organization id that created the message

orgId 1..1 400003

2.1.4 Message identifier-used to correlate between request and response

msgId 1..1 SBNSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM

3.1 Response <Resp> 1..1

3.1.1 Request Message identifier reqMsgId 1..1 NPNSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM

3.1.2 Result of the transaction result 1..1 SUCCESS

3.1.3 Error code if failed errCode 1..1

4.1 Transaction information, Carried throughout the system, visible to all parties

<Txn> 1..1

4.1.1 Unique Identifier of the transaction across all entities created by the originator

id 1..1 8ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM

4.1.2 Description of the transaction(which will be printed on Pass book)

note 1..1 Restaurant Bill

4.1.3 Consumer reference number to identify (like Loan number, etc.)

ref 1..1

4.1.4 Transaction origination time by the creator of the message

ts 1..1 2015-02-16T22:02:35+05:30

4.1.5 Type of the Transaction type 1..1 PAY

4.2 Risk Score related to the transaction and the entities

<Txn.RiskScores> 0..1

4.3 Risk Score related to the transaction and the entities

<Txn.RiskScores.Score>

0..1

4.3.1 Entity providing the risk score provider 1..1 Psp2

4.3.2 Type of risk type 1..1 TXNRISK

4.3.3 Value of risk evaluation ranging from 0 (No Risk) to 100 (Maximum Risk)

value 1..1 00030

5.1 Details related to the Payer <Payer> 1..1

5.1.1 Address of the Payer addr 1..1 zeeshan.khan@hdfc

5.1.2 Name of the Payer name 1..1 Zeeshan Khan

5.1.3 Unique identifier for each transaction inside a file including payer and payee

seqNum 1..1 1

5.1.4 Type of the Payer type 1..1 PERSON

5.1.5 Merchant Classification Code -MCC code 1..1 4814

5.2 Information related to the Payer <Payer.Info> 1..1

5.3 Payer Identity is mandatory for “collect” and optional for “pay”

<Payer.Info.Identity> 1..1

5.3.1 Type of the identifier type 1..1 ACCOUNT

5.3.2 Name as per the identifier verifiedName 1..1 Zeeshan Khan

5.3.3 Id Id 1.1 7389923983430

5.4 Rating of the payer <Payer.Info.Rating> 0..1

5.4.1 Payer is whitelisted or not verifiedAddress 1..1 TRUE

5.5 Information related to the amounts in the transaction

<Payer.Amount> 1..1

5.5.1 Transaction amount value 1..1 4000

5.5.2 Currency of the transaction curr 1..1 INR

6.1 Details related to the Payees <Payees> 1..1

6.2 Details related to the Payee <Payee> 1..1

Page 109: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS

17/07/2015 Page 109 of 122

Index Message Item <XML Tag> Occurrence Sample Value

6.2.1 Address of the Payee addr 1..1 rohit.patekar@sbi

6.2.2 Name of the Payee name 1..1 Rohit Patekar

6.2.3 Unique identifier for each transaction inside a file including Payee and payee

seqNum 1..1 1

6.2.4 Type of the Payee type 1..1 PERSON

6.2.5 Merchant Classification Code -MCC code 1..1 4814

6.3 Information related to the Payee <Payee.Info> 1..1

6.4 Payee Identity <Payee.Info.Identity> 1..1

6.4.1 Type of the identifier type 1..1 ACCOUNT

6.4.2 Name as per the identifier verifiedName 1..1 Rohit Patekar

6.4.3 Id Id 1.1 8392389838

6.5 Rating of the Payee <Payee.Info.Rating> 0..1

6.5.1 Payee is whitelisted or not verifiedAddress 1..1 TRUE

6.6 Only one entity is allowed for a Payee <Payee.Ac> 1..1

6.6.1 Type of the address addrType 1..1 ACCOUNT

6.7 Details related to Payee Address <Payee.Ac.Detail> 1..n

6.7.1 Name of the property name 1..n IFSC

6.7.2 Value of the property value 1..n UBIN0288100

6.7.3 Name of the property name 1..n ACTYPE

6.7.4 Value of the property value 1..n SAVINGS

6.7.5 Name of the property name 1..n ACNUM

6.7.6 Value of the property value 1..n 5678892001828

6.8 Information related to the amounts in the transaction

<Payee.Amount> 1..1

6.8.1 Transaction amount value 1..1 4000

6.8.2 Currency of the transaction curr 1..1 INR

6.6 ReqPay_NPCI_DEBIT_REQ(UPI to PAYER BANK)

<upi:ReqPay xmlns:upi="http://npci.org/upi/schema/"> <Head ver="1.0" ts="2015-02-16T22:02:48+05:30" orgId="400001" msgId="HENSVVR4QZS7X1UGPY7JGUV444PL9Z2C3QZ"/> <Meta> <Tag name="PAYREQSTART" value="2015-02-16T22:02:00+05:30"/> <Tag name="PAYREQEND" value="2015-02-16T22:02:35+05:30"/> </Meta> <Txn id="8ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM" note="Restaurant Bill " refId="" refUrl="" ts="2015-02-16T22:02:35+05:30" type="DEBIT" orgTxnId=""> <RiskScores> <Score provider="psp1" type="TXNRISK" value="00030"/> <Score provider="npci" type="TXNRISK" value="00030"/> </RiskScores> </Txn> <Payer addr="zeeshan.khan@hdfc" name="Zeeshan Khan" seqNum="1" type="PERSON" code="4814"> <Info> <Identity type="ACCOUNT" verifiedName="Zeeshan Khan" id="7389923983430"/> <Rating verifiedAddress="TRUE"/> </Info> <Device> <Tag name="MOBILE" value="+91.99999.00000"/>

Page 110: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS

17/07/2015 Page 110 of 122

<Tag name="GEOCODE" value="288177"/> <Tag name="LOCATION" value="Mumbai,Maharashtra" /> <Tag name="IP" value="124.170.23.22"/> <Tag name="TYPE" value="mob"/> <Tag name="ID" value="750c6be243f1c4b5c9912b95a5742fc5"/> #device advertising id <Tag name="OS" value="android"/> <Tag name="APP" value="NPCIAPP"/> <Tag name="CAPABILITY" value="5200000200010004000639292929292"/> </Device> <Ac addrType="ACCOUNT"> <Detail name="ACTYPE" value="SAVINGS"/> <Detail name="IFSC" value="ICIC0288100"/> <Detail name="ACNUM" value="2678892001828"/> </Ac> <Creds> <Cred type="PIN" subType="MPIN">

<Data> base-64 encoded and encrypted</Data> #data includes [<Transaction Id><delimiter><Common library version><delimiter><Captured credential><delimiter><Transaction amount><delimiter><Random number> ,"|" to be used as delimiter

</Cred>

</Creds> <Amount value="4000" curr="INR"> </Amount> </Payer> <Payees> <Payee addr="rohit.patekar@sbi" name="Rohit Patekar" seqNum="1" type="PERSON" code="4814">#mcc has to be populated <Info> <Identity type="ACCOUNT" verifiedName="Rohit Patekar" id="8392389838"/> <Rating verifiedAddress="TRUE"/> </Info> <Ac addrType="ACCOUNT"> <Detail name="IFSC" value="UBIN0288100"/> <Detail name="ACTYPE" value="SAVINGS"/> <Detail name="ACNUM" value="5678892001828"/> </Ac> <Amount value="4000" curr="INR"> </Amount> </Payee> </Payees> </upi:ReqPay>

Index Message Item <XML Tag> Occurrence Sample Value

1.1 API Name <upi> 1..1 ReqPay

1.1.1 API Schema namespace xmlns 1..1 upi="http://npci.org/upi/schema/

2.1 Header for the message <Head> 1..1

2.1.1 Version of the API ver 1..1 1.0

2.1.2 Time of request from the creator of the message

ts 1..1 2015-02-16T22:02:35+05:30

2.1.3 Organization id that created the message

orgId 1..1 400001

2.1.4 Message identifier-used to correlate between request and response

msgId 1..1 HENSVVR4QZS7X1UGPY7JGUV444PL9Z2C3QM

Page 111: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS

17/07/2015 Page 111 of 122

Index Message Item <XML Tag> Occurrence Sample Value

3.1 Meta data primarily for analytics purposes

<Meta> 0..1

3.2 Meta data primarily for analytics purposes

<Meta.Tag> 0..1

3.2.1 Name of the property name 1..n PAYREQSTART

3.2.2 Value of the property value 1..n 2015-02-16T22:02:00+05:30

4.1 Transaction information, Carried throughout the system, visible to all parties

<Txn> 1..1

4.1.1 Unique Identifier of the transaction across all entities, created by the originator

id 1..1 8ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM

4.1.2 Description of the transaction(which will be printed on Pass book)

note 1..1 Restaurant Bill

4.1.3 Consumer reference number to identify (like Loan number, etc.)

refId 1..1

4.1.4 URL for the transaction refUrl 1..1

4.1.5 Transaction origination time by the creator of the message

ts 1..1 2015-02-16T22:02:35+05:30

4.1.6 Type of the Transaction type 1..1 CREDIT

4.1.7 Original transaction ID when reversal/Refund has to be done

orgTxnId 1..1

4.2 Risk Score related to the transaction and the entities

<Txn.RiskScores> 0..1

4.3 Risk Score related to the transaction and the entities

<Txn.RiskScores.Score> 0..1

4.3.1 Entity providing the risk score provider 1..1 psp1

4.3.2 Type of risk type 1..1 TXNRISK

4.3.3 Value of risk evaluation ranging from 0 (No Risk) to 100 (Maximum Risk)

value 1..1 00030

5.1 Details related to the Payer <Payer> 1..1

5.1.1 Address of the Payer addr 1..1 zeeshan.khan@hdfc

5.1.2 Name of the Payer name 1..1 Zeeshan Khan

5.1.3 Unique identifier for each transaction inside a file including payer and payee

seqNum 1..1 1

5.1.4 Type of the Payer type 1..1 PERSON

5.1.5 Merchant Classification Code -MCC

code 1..1 4814

5.2 Information related to the Payer <Payer.Info> 1..1

5.3 Payer Identity Is mandatory for “collect” and optional for “pay”

<Payer.Info.Identity> 1..1

5.3.1 Type of the identifier type 1..1 ACCOUNT

5.3.2 Name as per the identifier verifiedName 1..1 Zeeshan Khan

5.3.3. Id Id 1.1 7389923983430

5.4 Rating of the payer <Rating> 0..1

5.4.1 Payer is whitelisted or not verifiedAddress 1..1 TRUE

Page 112: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS

17/07/2015 Page 112 of 122

Index Message Item <XML Tag> Occurrence Sample Value

5.5 Details of Device from which the transaction was initiated

<Payer.Device> 1..1

5.6 Device Tag <Payer.Device.Tag> 1..n

5.6.1 Name of the property name 1..n MOBILE

5.6.2 Value of the property value 1..n +91.99999.00000

5.7 Only one entity is allowed for a payer

<Payer.Ac> 1..1

5.7.1 Type of the address addrType 1..1 ACCOUNT

5.8 Details related to Payer Address <Payer.Ac.Detail> 1..n

5.8.1 Name of the property name 1..n ACTYPE

5.8.2 Value of the property value 1..n SAVINGS

5.8.3 Name of the property name 1..n IFSC

5.8.4 Value of the property value 1..n ICIC0288100

5.8.5 Name of the property name 1..n ACNUM

5.8.6 Value of the property value 1..n 2678892001828

5.9 Information related to Payer Credentials

<Payer.Creds> 1..1

5.10 Credentials are used to authenticate the request

<Payer.Creds.Cred> 1..1

5.10.1 Type of financial instrument used for authentication

Type 1..1 PreApproved

5.10.2 Subtype of Financial instrument used for authentication

subtype 1.1 NA

5.11 base-64 encoded/encrypted authentication data

<Payer.Creds.Cred.Data> 1..1 Base 64 encoded value of RES|A12345

5.12 Information related to the amounts in the transaction

<Payer.Amount> 1..1

5.12.1 Transaction amount Value 1..1 4000

5.12.2 Currency of the transaction Curr 1..1 INR

6.1 Details related to the Payees <Payees> 1..1

6.2 Details related to the Payee <Payee> 1..1

6.2.1 Address of the Payee Addr 1..1 rohit.patekar@sbi

6.2.2 Name of the Payee Name 1..1

6.2.3 Unique identifier for each transaction inside a file including Payee and payee

seqNum 1..1 1

6.2.4 Type of the Payee Type 1..1 PERSON

6.2.5 Merchant Classification Code -MCC

Code 1..1 4814

6.3 Information related to the Payee <Payee.Info> 1..1

6.4 Payee Identity Is mandatory for “collect” and optional for “pay”

<Payee.Info.Identity> 1..1

6.4.1 Type of the identifier type 1..1 ACCOUNT

6.4.2 Name as per the identifier verifiedName 1..1 Rohit Patekar

6.4.3. Id Id 1.1 8392389838

6.5 Rating of the payee <Rating> 0..1

6.5.1 Payee is whitelisted or not verifiedAddress 1..1 TRUE

Page 113: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS

17/07/2015 Page 113 of 122

Index Message Item <XML Tag> Occurrence Sample Value

6.6 Only one entity is allowed for a payee

<Payee.Ac> 1..1

6.6.1 Type of the address addrType 1..1 ACCOUNT

6.7 Details related to Payee Address <Payee.Ac.Detail> 1..n

6.7.1 Name of the property name 1..n ACTYPE

6.7.2 Value of the property value 1..n SAVINGS

6.7.3 Name of the property name 1..n IFSC

6.7.4 Value of the property value 1..n UBIN0288100

6.7.5 Name of the property name 1..n ACNUM

6.7.6 Value of the property value 1..n 5678892001828

6.7 RespPay_NPCI_DEBIT_REQ_RESP(PAYER BANK to UPI)

<upi:RespPay xmlns:upi="http://npci.org/upi/schema/"> <Head ver="1.0" ts="2015-02-16T22:02:54+05:30" orgId="400002" msgId="NENSVVR4QOS7X1UGPY7JGUV424PL9T2C3QM"/> <Txn id="8ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM" note="Restaurant Bill " refId=““ refUrl=““ ts="2015-02-16T22:02:35+05:30" type="DEBIT"> <RiskScores> <Score provider="psp2" type="TXNRISK" value="00030"/> <Score provider="npci" type="TXNRISK" value="00030"/> </RiskScores> </Txn> <Resp reqMsgId="HENSVVR4QZS7X1UGPY7JGUV444PL9Z2C3QZ" result="SUCCESS" errCode=""> <Ref type="PAYER" seqNum="1" addr="zeeshan.khan@hdfc" settAmount="4000"

settCurrency="INR" acNum="2678892001828" approvalNum="9399389827" respCode="00"/>

<Ref type="PAYEE" seqNum="1" addr="rohit.patekar@sbi" settAmount="4000" settCurrency="INR" acNum="5678892001828" approvalNum="" respCode=""/> </Resp> </upi:RespPay>

Index Message Item <XML Tag> Occurrence Sample Value

1.1 API Name <RespPay> 1..1 RespPay

1.1.1 API Schema namespace xmlns 1..1 upi="http://npci.org/upi/schema/

2.1 Header for the message <Head> 1..1

2.1.1 Version of the API ver 1..1 1.0

2.1.2 Time of request from the creator of the message

ts 1..1 2015-02-16T22:02:48+05:30

2.1.3 Organization id that created the message

orgId 1..1 400002

2.1.4 Message identifier-used to correlate between request and response

msgId 1..1 NENSVVR4QOS7X1UGPY7JGUV424PL9T2C3QM

3.1 Transaction information, Carried throughout the system, visible to all parties

<Txn> 1..1

Page 114: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS

17/07/2015 Page 114 of 122

Index Message Item <XML Tag> Occurrence Sample Value

3.1.1 Unique Identifier of the transaction across all entities created by the originator

id 1..1 8ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM

3.1.2 Description of the transaction(which will be printed on Pass book)

note 1..1 Restaurant Bill

3.1.3 Consumer reference number to identify (like Loan number, etc.)

refId 1..1

3.1.4 URL for the transaction refUrl 1..1

3.1.5 Transaction origination time by the creator of the message

ts 1..1 2015-02-16T22:02:35+05:30

3.1.6 Type of the Transaction type 1..1 CREDIT

3.2 Risk Score related to the transaction and the entities

<Txn.RiskScores> 0..1

3.3 Risk Score related to the transaction and the entities

<Txn.RiskScores.Score>

0..1

3.3.1 Entity providing the risk score provider 1..1 psp1

3.3.2 Type of risk type 1..1 TXNRISK

3.3.3 Value of risk evaluation ranging from 0 (No Risk) to 100 (Maximum Risk)

value 1..1 00030

3.4 Response <Resp> 1..1

3.4.1 Request Message identifier reqMsgId 1..1 HENSVVR4QZS7X1UGPY7JGUV444PL9Z2C3QM

3.4.2 Result of the transaction result 1..1 SUCCESS

3.4..3 Error code if failed errCode 1..1

3.5 Response Reference <Ref> 1..n

3.5.1 Customer type type 1..1 PAYER

3.5.2 Sequence Number seqNum 1..1 1

3.5.3 Payment address addr 1..1 zeeshan.khan@hdfc

3.5.4 Settlement Amount settAmount 1..1 4000

3.5.5 Settlement Currency settCurrency 1..1 INR

3.5.6 Approval Reference Number approvalNum 1..1 9399389827

3.5.7 Response code respCode 1..1 00

6.8 ReqPay_NPCI_CREDIT_REQ(UPI to PAYEE BANK)

<upi:ReqPay xmlns:upi="http://npci.org/upi/schema/"> <Head ver="1.0" ts="2015-02-16T22:02:54+05:30" orgId="400001" msgId="HENSVVR4QZS7X1UGPY7JGUV444PL9Z2C3QM"/> <Meta> <Tag name="PAYREQSTART" value="2015-02-16T22:02:00+05:30"/> <Tag name="PAYREQEND" value="2015-02-16T22:02:35+05:30"/> </Meta> <Txn id="8ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM" note="Restaurant Bill " refId="" refUrl="" ts="2015-02-16T22:02:35+05:30" type="CREDIT" orgTxnId=""> <RiskScores> <Score provider="psp1" type="TXNRISK" value="00030"/> <Score provider="npci" type="TXNRISK" value="00030"/> </RiskScores> </Txn> <Payer addr="zeeshan.khan@hdfc" name="Zeeshan Khan" seqNum="1" type="PERSON" code="4814"> <Info>

Page 115: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS

17/07/2015 Page 115 of 122

<Identity type="ACCOUNT" verifiedName="Zeeshan Khan" id="7389923983430"/> <Rating verifiedAddress="TRUE"/> </Info> <Device> <Tag name="MOBILE" value="+91.99999.00000"/> <Tag name="GEOCODE" value="288177"/> <Tag name="LOCATION" value="Mumbai,Maharashtra" /> <Tag name="IP" value="124.170.23.22"/> <Tag name="TYPE" value="mob"/> <Tag name="ID" value="750c6be243f1c4b5c9912b95a5742fc5"/> #device advertising id <Tag name="OS" value="android"/> <Tag name="APP" value="NPCIAPP"/> <Tag name="CAPABILITY" value="5200000200010004000639292929292"/> </Device> <Ac addrType="ACCOUNT"> <Detail name="ACTYPE" value="SAVINGS"/> <Detail name="IFSC" value="HDFC0288100"/> <Detail name="ACNUM" value="2678892001828"/> </Ac> <Creds> <Cred type="PreApproved" subType="NA"> <Data> base-64 encoded</Data> #data includes respCode and approvalRef RES|A12345 </Cred> </Creds> <Amount value="4000" curr="INR"> </Amount> </Payer> <Payees> <Payee addr="rohit.patekar@sbi" name="Rohit Patekar" seqNum="1" type="PERSON" code="4814">#mcc has to be populated <Info> <Identity type="ACCOUNT" verifiedName="Rohit Patekar" id="8392389838"/> <Rating verifiedAddress="TRUE"/> </Info> <Ac addrType="ACCOUNT"> <Detail name="IFSC" value="SBIN0288100"/> <Detail name="ACTYPE" value="SAVINGS"/> <Detail name="ACNUM" value="5678892001828"/> </Ac> <Amount value="4000" curr="INR"> </Amount> </Payee> </Payees> </upi:ReqPay>

Index Message Item <XML Tag> Occurrence Sample Value

1.1 API Name <upi> 1..1 ReqPay

1.1.1 API Schema namespace xmlns 1..1 upi="http://npci.org/upi/schema/

2.1 Header for the message <Head> 1..1

2.1.1 Version of the API ver 1..1 1.0

2.1.2 Time of request from the creator of the message

ts 1..1 2015-02-16T22:02:35+05:30

2.1.3 Organization id that created the message

orgId 1..1 400001

Page 116: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS

17/07/2015 Page 116 of 122

Index Message Item <XML Tag> Occurrence Sample Value

2.1.4 Message identifier-used to correlate between request and response

msgId 1..1 HENSVVR4QZS7X1UGPY7JGUV444PL9Z2C3QM

3.1 Meta data primarily for analytics purposes

<Meta> 0..1

3.2 Meta data primarily for analytics purposes

<Meta.Tag> 0..1

3.2.1 Name of the property name 1..n PAYREQSTART

3.2.2 Value of the property value 1..n 2015-02-16T22:02:00+05:30

4.1 Transaction information, Carried throughout the system, visible to all parties

<Txn> 1..1

4.1.1 Unique Identifier of the transaction across all entities, created by the originator

id 1..1 8ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM

4.1.2 Description of the transaction(which will be printed on Pass book)

note 1..1 Restaurant Bill

4.1.3 Consumer reference number to identify (like Loan number, etc.)

refId 1..1

4.1.4 URL for the transaction refUrl 1..1

4.1.5 Transaction origination time by the creator of the message

ts 1..1 2015-02-16T22:02:35+05:30

4.1.6 Type of the Transaction type 1..1 CREDIT

4.1.7 Original transaction ID when reversal/Refund has to be done

orgTxnId 1..1

4.2 Risk Score related to the transaction and the entities

<Txn.RiskScores> 0..1

4.3 Risk Score related to the transaction and the entities

<Txn.RiskScores.Score> 0..1

4.3.1 Entity providing the risk score provider 1..1 psp1

4.3.2 Type of risk type 1..1 TXNRISK

4.3.3 Value of risk evaluation ranging from 0 (No Risk) to 100 (Maximum Risk)

value 1..1 00030

5.1 Details related to the Payer <Payer> 1..1

5.1.1 Address of the Payer addr 1..1 zeeshan.khan@hdfc

5.1.2 Name of the Payer name 1..1 Zeeshan Khan

5.1.3 Unique identifier for each transaction inside a file including payer and payee

seqNum 1..1 1

5.1.4 Type of the Payer type 1..1 PERSON

5.1.5 Merchant Classification Code -MCC

code 1..1 4814

5.2 Information related to the Payer <Payer.Info> 1..1

5.3 Payer Identity Is mandatory for “collect” and optional for “pay”

<Payer.Info.Identity> 1..1

5.3.1 Type of the identifier type 1..1 ACCOUNT

5.3.2 Name as per the identifier verifiedName 1..1 Zeeshan Khan

Page 117: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS

17/07/2015 Page 117 of 122

Index Message Item <XML Tag> Occurrence Sample Value

5.3.3. Id Id 1.1 7389923983430

5.4 Rating of the payer <Rating> 0..1

5.4.1 Payer is whitelisted or not verifiedAddress 1..1 TRUE

5.5 Details of Device from which the transaction was initiated

<Payer.Device> 1..1

5.6 Device Tag <Payer.Device.Tag> 1..n

5.6.1 Name of the property name 1..n MOBILE

5.6.2 Value of the property value 1..n +91.99999.00000

5.7 Only one entity is allowed for a payer

<Payer.Ac> 1..1

5.7.1 Type of the address addrType 1..1 ACCOUNT

5.8 Details related to Payer Address <Payer.Ac.Detail> 1..n

5.8.1 Name of the property name 1..n ACTYPE

5.8.2 Value of the property value 1..n SAVINGS

5.8.3 Name of the property name 1..n IFSC

5.8.4 Value of the property value 1..n ICIC0288100

5.8.5 Name of the property name 1..n ACNUM

5.8.6 Value of the property value 1..n 2678892001828

5.9 Information related to Payer Credentials

<Payer.Creds> 1..1

5.10 Credentials are used to authenticate the request

<Payer.Creds.Cred> 1..1

5.10.1 Type of financial instrument used for authentication

Type 1..1 PreApproved

5.10.2 Subtype of Financial instrument used for authentication

subtype 1.1 NA

5.11 base-64 encoded/encrypted authentication data

<Payer.Creds.Cred.Data> 1..1 Base 64 encoded value of RES|A12345

5.12 Information related to the amounts in the transaction

<Payer.Amount> 1..1

5.12.1 Transaction amount Value 1..1 4000

5.12.2 Currency of the transaction Curr 1..1 INR

6.1 Details related to the Payees <Payees> 1..1

6.2 Details related to the Payee <Payee> 1..1

6.2.1 Address of the Payee Addr 1..1 rohit.patekar@sbi

6.2.2 Name of the Payee Name 1..1

6.2.3 Unique identifier for each transaction inside a file including Payee and payee

seqNum 1..1 1

6.2.4 Type of the Payee Type 1..1 PERSON

6.2.5 Merchant Classification Code -MCC

Code 1..1 4814

6.3 Information related to the Payee <Payee.Info> 1..1

6.4 Payee Identity Is mandatory for “collect” and optional for “pay”

<Payee.Info.Identity> 1..1

6.4.1 Type of the identifier type 1..1 ACCOUNT

6.4.2 Name as per the identifier verifiedName 1..1 Rohit Patekar

Page 118: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS

17/07/2015 Page 118 of 122

Index Message Item <XML Tag> Occurrence Sample Value

6.4.3. Id Id 1.1 8392389838

6.5 Rating of the payee <Rating> 0..1

6.5.1 Payee is whitelisted or not verifiedAddress 1..1 TRUE

6.6 Only one entity is allowed for a payee

<Payee.Ac> 1..1

6.6.1 Type of the address addrType 1..1 ACCOUNT

6.7 Details related to Payee Address <Payee.Ac.Detail> 1..n

6.7.1 Name of the property name 1..n ACTYPE

6.7.2 Value of the property value 1..n SAVINGS

6.7.3 Name of the property name 1..n IFSC

6.7.4 Value of the property value 1..n UBIN0288100

6.7.5 Name of the property name 1..n ACNUM

6.7.6 Value of the property value 1..n 5678892001828

6.9 RespPay_NPCI_CREDIT_REQ_RES(PAYEE BANK to UPI)

<upi:RespPay xmlns:upi="http://npci.org/upi/schema/"> <Head ver="1.0" ts="2015-02-16T22:02:56+05:30" orgId="400003" msgId="NENSVVR4QOS7X1UGPY7JGUV424PL9T2C3QM"/> <Txn id="8ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM" note="Restaurant Bill " refId=““ refUrl=““ ts="2015-02-16T22:02:35+05:30" type="CREDIT"> <RiskScores> <Score provider="psp2" type="TXNRISK" value="00030"/> <Score provider="npci" type="TXNRISK" value="00030"/> </RiskScores> </Txn> <Resp reqMsgId="HENSVVR4QZS7X1UGPY7JGUV444PL9Z2C3QM" result="SUCCESS" errCode=""> <Ref type="PAYER" seqNum="1" addr="zeeshan.khan@hdfc" settAmount="4000"

settCurrency="INR" acNum ="2678892001828" approvalNum="9399389827" respCode="00"/>

<Ref type="PAYEE" seqNum="1" addr="rohit.patekar@sbi" settAmount="4000" settCurrency="INR" acNum="5678892001828" Acc approvalNum="7786787865" respCode="00"/> </Resp> </upi:RespPay>

Index Message Item <XML Tag> Occurrence Sample Value

1.1 API Name <RespPay> 1..1 RespPay

1.1.1 API Schema namespace xmlns 1..1 upi="http://npci.org/upi/schema/

2.1 Header for the message <Head> 1..1

2.1.1 Version of the API ver 1..1 1.0

2.1.2 Time of request from the creator of the message

ts 1..1 2015-02-16T22:02:48+05:30

2.1.3 Organization id that created the message

orgId 1..1 400002

2.1.4 Message identifier-used to correlate between request and response

msgId 1..1 NENSVVR4QOS7X1UGPY7JGUV424PL9T2C3QM

Page 119: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS

17/07/2015 Page 119 of 122

Index Message Item <XML Tag> Occurrence Sample Value

3.1 Transaction information, Carried throughout the system, visible to all parties

<Txn> 1..1

3.1.1 Unique Identifier of the transaction across all entities created by the originator

id 1..1 8ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM

3.1.2 Description of the transaction(which will be printed on Pass book)

note 1..1 Restaurant Bill

3.1.3 Consumer reference number to identify (like Loan number, etc.)

refId 1..1

3.1.4 URL for the transaction refUrl 1..1

3.1.5 Transaction origination time by the creator of the message

ts 1..1 2015-02-16T22:02:35+05:30

3.1.6 Type of the Transaction type 1..1 CREDIT

3.2 Risk Score related to the transaction and the entities

<Txn.RiskScores> 0..1

3.3 Risk Score related to the transaction and the entities

<Txn.RiskScores.Score>

0..1

3.3.1 Entity providing the risk score provider 1..1 psp1

3.3.2 Type of risk type 1..1 TXNRISK

3.3.3 Value of risk evaluation ranging from 0 (No Risk) to 100 (Maximum Risk)

value 1..1 00030

3.4 Response <Resp> 1..1

3.4.1 Request Message identifier reqMsgId 1..1 HENSVVR4QZS7X1UGPY7JGUV444PL9Z2C3QM

3.4.2 Result of the transaction result 1..1 SUCCESS

3.4..3 Error code if failed errCode 1..1

3.5 Response Reference <Ref> 1..n

3.5.1 Customer type type 1..1 PAYER

3.5.2 Sequence Number seqNum 1..1 1

3.5.3 Payment address addr 1..1 zeeshan.khan@hdfc

3.5.4 Settlement Amount settAmount 1..1 4000

3.5.5 Settlement Currency settCurrency 1..1 INR

3.5.6 Approval Reference Number approvalNum 1..1 9399389827

3.5.7 Response code respCode 1..1 00

6.10 RespPay(UPI to PSP1)

<upi:RespPay xmlns:upi="http://npci.org/upi/schema/"> <Head ver="1.0" ts="2015-02-16T22:02:59+05:30" orgId="400001" msgId="NENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM"/> <Txn id="8ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM" note="Restaurant Bill " refId=““ refUrl=““ ts="2015-02-16T22:02:35+05:30" type="PAY"> <RiskScores> <Score provider="psp2" type="TXNRISK" value="00030"/> <Score provider="npci" type="TXNRISK" value="00030"/> </RiskScores> </Txn> <Resp reqMsgId="HENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM" result="SUCCESS" errCode="">

Page 120: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS

17/07/2015 Page 120 of 122

<Ref type="PAYER" seqNum="1" addr="zeeshan.khan@hdfc" settAmount="4000" settCurrency="INR" approvalNum="9399389827" respCode="00"/> <Ref type="PAYEE" seqNum="1" addr="rohit.patekar@sbi" settAmount="4000" settCurrency="INR" approvalNum="7786787865" respCode="00"/> </Resp> </upi:RespPay>

Index Message Item <XML Tag> Occurrence Sample Value

1.1 API Name <RespPay> 1..1 RespPay

1.1.1 API Schema namespace xmlns 1..1 upi="http://npci.org/upi/schema/

2.1 Header for the message <Head> 1..1

2.1.1 Version of the API ver 1..1 1.0

2.1.2 Time of request from the creator of the message

ts 1..1 2015-02-16T22:02:48+05:30

2.1.3 Organization id that created the message

orgId 1..1 400001

2.1.4 Message identifier-used to correlate between request and response

msgId 1..1 NENSVVR4QOS7X1UGPY7JGUV424PL9T2C3QM

3.1 Transaction information, Carried throughout the system, visible to all parties

<Txn> 1..1

3.1.1 Unique Identifier of the transaction across all entities created by the originator

id 1..1 8ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM

3.1.2 Description of the transaction(which will be printed on Pass book)

note 1..1 Restaurant Bill

3.1.3 Consumer reference number to identify (like Loan number, etc.)

refId 1..1

3.1.4 URL for the transaction refUrl 1..1

3.1.5 Transaction origination time by the creator of the message

ts 1..1 2015-02-16T22:02:35+05:30

3.1.6 Type of the Transaction type 1..1 PAY

3.2 Risk Score related to the transaction and the entities

<Txn.RiskScores> 0..1

3.3 Risk Score related to the transaction and the entities

<Txn.RiskScores.Score>

0..1

3.3.1 Entity providing the risk score provider 1..1 psp1

3.3.2 Type of risk type 1..1 TXNRISK

3.3.3 Value of risk evaluation ranging from 0 (No Risk) to 100 (Maximum Risk)

value 1..1 00030

3.4 Response <Resp> 1..1

3.4.1 Request Message identifier reqMsgId 1..1 HENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM

3.4.2 Result of the transaction result 1..1 SUCCESS

3.4..3 Error code if failed errCode 1..1

3.5 Response Reference <Ref> 1..n

3.5.1 Customer type type 1..1 PAYER

3.5.2 Sequence Number seqNum 1..1 1

3.5.3 Payment address addr 1..1 zeeshan.khan@hdfc

3.5.4 Settlement Amount settAmount 1..1 4000

3.5.5 Settlement Currency settCurrency 1..1 INR

Page 121: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS

17/07/2015 Page 121 of 122

Index Message Item <XML Tag> Occurrence Sample Value

3.5.6 Approval Reference Number approvalNum 1..1 9399389827

3.5.7 Response code respCode 1..1 00

Page 122: UNIFIED PAYMENT INTERFACE MESSAGE DUMPS UPI Message Dumps, Oct.15, 2015.pdf · Unified Payment Interface Message Dumps 1.0 19/09/2015 Provides Message Dumps for ReqPay, RespPay, ReqAuth

UPI MESSAGE DUMPS

17/07/2015 Page 122 of 122

6.11 ReqTxnConfirmation(UPI to PSP2)

<upi:ReqTxnConfirmation xmlns:upi="http://npci.org/upi/schema/"> <Head ver="1.0" ts="2015-02-16T22:03:00+05:30" orgId="400001" msgId="HPDSFVC2QOS7X1UGPY2JGUV454YC8T2C6QM"/> <Txn id="8ENSVVR4QOS7X1UGPY7JGUV444PL9T2C3QM" note="Restaurant Bill" refId=““ refUrl=““ ts="2015-02-16T22:02:35+05:30" type="TxnConfirmation" orgTxnId="HPDSFVC2QOS7X1UGPY2JGUV458PL8T2C6QM"/> <TxnConfirmation note="Restaurant Bill" orgStatus="SUCCESS" orgErrCode=”” type="PAY" orgTxnId="HPDSFVC2QOS7X1UGPY2JGUV458PL8T2C6QM" />

</upi:ReqTxnConfirmation>

6.12 RespTxnConfirmation(PSP2 to UPI)

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

<Head ver="1.0" ts="2015-02-16T22:03:01+05:30" orgId="400003" msgId="HPDSFVC2ZOS7X1UGPY2JGUV494ZC8T2C6QM"/> <Txn id="HPDSFVC2QOS7X1UGPY2JGUV458PL8T2C6QM" note="Restaurant Bill" refId=““ refUrl=““ ts="2015-02-16T22:02:35+05:30" type="TxnConfirmation" orgTxnId="HPDSFVC2QOS7X1UGPY2JGUV458PL8T2C6QM" /> <Resp reqMsgId="HPDSFVC2QOS7X1UGPY2JGUV454YL8T2C6QM" result="SUCCESS" errCode=""/>

</upi:RespTxnConfirmation>