Open API >Payment >Remittance & P2P Transfer
Remittance & P2P Transfer
Payment Developer Acquirer
Remittance & P2P Transfer interface intend to better assist UPI Members outside of Mainland China in implementing primary credit business, including cross-border remittance (MoneyExpress) and domestic P2P transfer,etc.
API Introduction
API Introduction
What is it?

Remittance & P2P Transfer interface intend to better assist UPI Members outside of Mainland China in implementing primary credit business, including but not limited to cross-border remittance and domestic P2P transfer, push purchase and push cash withdrawal, etc., making it easier for UPI members to extend business scope.

Key Features

1. Lower technology threshold and reduce development cost for institutions to luanch business.


2. API other than previous ISO format make it easier for institutions to access.


3. Applies to multiple scenarios, including cross-border remittance, domestic P2P, etc.


4. JWS, JWE are used to sign and encrypt online messagesto ensure security. Sensitive data will be encrypted before stored.


When to Use it?

The business scenarios including cross-border remittance and domestic P2P transfer.

Who Use it?
UPI Members who participate in the primary credit business and software developers.
Where to Use it?
This API is available globally except for Mainland China.
Flow Chart
Flow Chart

流程图.png


API Document
API Document
  • CREDIT VERIFY
  • PRIMARY CREDIT
  • MESSAGE RESULT INQUIRY
  • EXCHANGE RATE INQUIRY
Interface description
For cross-border remittance and domestic P2P transfer, the Sending Party initiates CREDIT_VERIFY request to UPI API to confirm the payee’s account validity before sending out the PRIMARY_CREDIT request.
Request Method
HTTP POST
Request Parameter
Field name Identifier Type Length Request Default value Note
Message ID msgID AN 29 M-Must “S0001034420190711235959123456” It is used to match a response to its request. The value must uniquely identify any message that the institutions initiates on any day. The value in the response must match the value in the request. Format: "S"+ INS ID +Transaction Time + Serial Number INS ID is the 8-digit alphabet and number, uniquely associated with an institution that connected to UPI. Transaction Time is the 14-digit number (YYYYMMDDhhmmss). Serial Number is the 6-digit number uniquely associated with the transaction.
Sending Party IIN sendPartyIIN AN 8 M-Must "00020344" The distinctive value associated to the Sending Party which manages Payer’s account.
Merchant Category Code mcc N 4 M-Must "6012" A 4-digit numeric value, as defined by [UPI OR], indicates the merchant type.
Merchant Country Code merchantCountry N 3 M-Must “156” A 3-digit numeric value, as defined in Technical Specifications on Bankcard Interoperability – Part VI Annex, indicates the country code of the merchant.
Merchant Name merchantName ANS 1-25 M-Must "UnionPay International"
Merchant City merchantCity ANS 1-12 M-Must "Shanghai"
Staged Digital Wallet (SDW) ID sdwID AN 8 C-Condition "00010344" For definition and business cope of SDW, please refer to [UPI OR]. It is present if SDW is used to initiate the transaction.
Device ID  deviceID ANS 1-64 C-Condition The distinctive value associated to a device. It shall be IMEI for Android mobile, and IDFV for iOS mobile. It is present if mobile device is used to initiate the transaction.
Transaction Amount trxAmt ANS 1-13 M-Must "101.10" It is either key-entered by payer or captured by the mobile application from the merchant-presented QRC data, ID "54". The value in this field includes tip or convenience fee, if applicable. For example, the value of transaction amount (ID "54") in the dynamitic QRC data is "100". The value of fixed convenience fee (ID "56") is "1.10". Then the value of "trxAmt" shall be "101.10".
Transaction Currency trxCurrency N 3 M-Must "156" A 3-digit numeric value, as defined in Technical Specifications on Bankcard Interoperability – Part VI Annex in line with ISO 4217, indicates the currency code of the transaction. The mobile application can display the transaction currency in a readable way, such as "RMB".
Transaction Fee Amount trxFeeAmt ANS 1-13 C-Condition "1.10" The tip or the convenience fee. It is present if the Tip or Convenience Fee exists.
Fund Source fundSource N 1 M-Must “3” Valid values:0 – cash ; 1 – debit card; 2 – credit card; 3 – account funds
Encrypted Data encData Object M-Must
Payer’s Name payerName ANS 1-30 M-Must “Zhang San” Chinese spelling letters (PIN YIN) are used if Chinese names are submitted.
Payer’s PAN payerPan ANS 1-19 C-Condition "6200008888888888888" It is present if bankcard account is used to initiate the transaction.
Payee’s Account payeePan ANS 1-19 M-Must "6200008888888888888"
Payee’s Name payeeName ANS 1-30 C-Condition “Li Si” Chinese spelling letters (PIN YIN) are used if Chinese names are submitted. It is present if required by local regulations.
Synchronous Response parameters
Filed name Identifier Type Length Request Default value Note
Message ID msgID AN 29 M-Must “S0001034420190711235959123456” It is used to match a response to its request. The value must uniquely identify any message that the institutions initiates on any day. The value in the response must match the value in the request. Format: "S"+ INS ID +Transaction Time + Serial Number INS ID is the 8-digit alphabet and number, uniquely associated with an institution that connected to UPI. Transaction Time is the 14-digit number (YYYYMMDDhhmmss). Serial Number is the 6-digit number uniquely associated with the transaction.
Transaction Amount trxAmt ANS 1-13 M-Must "101.10" It is either key-entered by payer or captured by the mobile application from the merchant-presented QRC data, ID "54". The value in this field includes tip or convenience fee, if applicable. For example, the value of transaction amount (ID "54") in the dynamitic QRC data is "100". The value of fixed convenience fee (ID "56") is "1.10". Then the value of "trxAmt" shall be "101.10".
Transaction Currency trxCurrency N 3 M-Must "156" A 3-digit numeric value, as defined in Technical Specifications on Bankcard Interoperability – Part VI Annex in line with ISO 4217, indicates the currency code of the transaction. The mobile application can display the transaction currency in a readable way, such as "RMB".
Business Indication businessIndication N 2 C-Condition “A1” Valid value: “A1”: Inbound China Remittance; “07”: Cross-border Remittance Outside of Mainland China. “08” Domestic P2P Outside of Mainland China; It is present if successful.
Receiving Party Name receivePartyName ANS 1-60 C-Condition “ABCD Bank” The name of the Receiving Party which manages Payee’s account. It is present if successful.
Settlement Date settlmtDate N 4 C-Condition It is only returned in Inbound China Remittance (the value of “businessIndicator” is “A1”) if the transaction is successful. Format: MMDD
Settlement Amount settlmtAmt ANS 1-13 C-Condition It is only returned in Inbound China Remittance (the value of “businessIndicator” is “A1”) when transaction currency is different from settlement currency and the transaction is successful.
Settlement Currency settlmtCurrency N 3 C-Condition It is only returned in Inbound China Remittance (the value of “businessIndicator” is “A1”) when transaction currency is different from settlement currency and the transaction is successful.
Settlement Conversion Rate settlmtConvRate N 8 C-Condition It is only returned in Inbound China Remittance (the value of “businessIndicator” is “A1”) when transaction currency is different from settlement currency and the transaction is successful.
Cardholder Billing Amount billingAmt ANS 1-13 C-Condition It is only returned in Inbound China Remittance (the value of “businessIndicator” is “A1”) when transaction currency is different from cardholder billing currency and the transaction is successful.
Cardholder Billing Currency billingCurrency N 3 C-Condition It is only returned in Inbound China Remittance (the value of “businessIndicator” is “A1”) when transaction currency is different from cardholder billing currency and the transaction is successful.
Cardholder Billing Conversion Rate billingConvRate N 8 C-Condition It is only returned in Inbound China Remittance (the value of “businessIndicator” is “A1”) when transaction currency is different from cardholder billing currency and the transaction is successful.
Message Response msgResponse Object M-Must
Response Code responseCode AN 2 M-Must "00" It contains a code that defines the response to a request.
Response Message responseMsg S 1-100 M-Must "Approved" It contains the transaction result and the rejection reason if the transaction fails. The value of this field can be displayed on the mobile application to notify the payer of the payment outcome.
Error Detail errorDetail S 1-255 O-Optional “The Issuer response is time out.” It contains additional detail regarding the problem identified in the message. The information is only for debug purpose. It shall not be displayed to the customer, cashier, etc.
Steps to Launch
Steps to Launch

1. Review and Sign MOU & NDA.

Note:MOU( Memorandum of Understanding)

NDA(Non-disclosure Agreement)

2. Sign membership application forms and settlement agreement,  submit the  membership application forms and related documents.

3. Receive LA and IIN assignment from UPI.

Note: LA(Letter of Authority)

4. Develop the system and operational requirements.

5. Preparation check and launch.


Please submit order in Support Center to contact us.


  • Contact Us
  • If you have any further questions, please register and submit order in your user center.