Documentation
Support Documentation Data Dictionary
Message Response

The Message Response shall always be present in a response message:

• When it is an acknowledgement response, "responseCode”: “00” indicates the request message is well-received. The processing result will be sent in another message later. For example, the “responseCode” of the “ADDITIONAL_PROCESSING” indicates the application gateway has received the request from the UMPS. The result of “ADDITIONAL_PROCESSING” will be sent in the “ADDITIONAL_PROCESSING_RESULT” message.

• When it is a processing result response, "responseCode”: “00” indicates the request message is approved.  

The valid values of data elements in Message Response are shown in the following table. If the message contains a value not shown in the table, the receiver will consider the message rejected, and can display the Response Message as a description.

Response codeResponse MessageError Detail 
00Transaction approved / acknowledged
01Transaction rejected, Refer to card Issuers for reason

The transaction is rejected by the Issuer, contact the Issuer for detailed reason

03Invalid merchant

1.Exceptional MCC;

2.MCC not supported for the transaction with this card ;

3.This merchant is in the blacklist. 

04Card should be captured

The Issuer believes that the card should be captured.

05Cardholder verification failure

1. The transaction information of the e-commerce transaction is sent and received beyond the time limit.

2. The cardholder identity verification fails (for transactions like commission relationship establishment or e-commerce transaction).

3. Certificate information (e.g. type, number and so on) does not comply with the requirement.

4. The cardholder authentication is invalid in case of expiry.

5. The cardholder birth date verification fails.

6. For cross-border remittance, the receiver information provided by the sending institution does not match what is registered at the receiving bank.

7. The CVN2 verification fails.

8. The cardholder authentication is invalid in case of mismatching.

12Invalid related transaction

1. The original transaction has not been accepted; however, a transaction such as reversal and cancellation, related to the original transaction, is received. 

2. The transaction that should occur every other day does not occur every other day. 

3. The cancellation or reversal is conducted for original transaction every other day. 

4. The transaction has not been conducted, but the information of related transaction is received (for example, the pre-authorization transaction has not been accepted, but the pre-authorization completion or pre-authorization cancellation transaction is received). 

13
Invalid transaction amount

Example:

1.0 or other unallowable values;

2.The transferred payment amount limit or the cash payment amount limit is exceeded;

3.The transaction exceeds the upper limit required;

4.The tip amount is beyond the limit 

5.Currency not supported; 

6.In cross-border remittance, the receiver or the sender does not have sufficient yearly foreign exchange quota to send or receive. 

14Invalid card number 

1. The Issuer has no such primary account number.

2. Though the original transaction is located, the primary account number of the related transaction does not match that of the original transaction.

3. The check digit of the card number is incorrect.

4. The account is invalid or closed.

5. The primary account number of the response transaction does not match that of the request transaction. 

15No such Issuer

There is no Issuer matching the primary account number requested in the transaction.

21Card not initialized

1. This card has not been activated or opened;

2. The initial password of this card has not been changed;

3. It is restricted to process transactions by the initial password; 

4. The card is frozen because of not being used for a long period of time or the card is in the "dormant" status.

22Transaction procedure error

1. A cancellation request follows a completed reversal.

2. A related transaction (such as reversal or cancellation) follows a cancelled transaction.

3. A pre-authorization completion transaction follows a completed pre-authorization cancellation transaction.

4. A pre-authorization completion transaction follows a completed pre-authorization reversal transaction.

5. A repeated pre-authorization completion request follows a completed pre-authorization completion transaction.

6. The pre-authorization transaction (including pre-authorization completion and pre-authorization cancellation) is initiated later than the last day of the period allowed for pre-authorization.

7. The transaction is initiated later than the normal payment time.

25Unable to match the original transaction

The original transaction cannot be matched

30Format error

1. XXXX missing/XXX format missing

2. Invalid transaction channel value 

3. Error in field reading 

4. Error in sub-field reading 

5. Failed field examination 

6. Invalid character

7. Bitmap format error 

8. Magnetic track information error

9. Transaction amount missing. 

34Suspected  fraud

1.ARQC authentication error

2.The number of CVN attempts is beyond the limit;

3.Counterfeit card.

40Transaction not supported

1. The Issuer has not enabled such transaction. 

2. The transaction type can be determined according to the message of the Member; however, such transaction has not been enabled. 

3. The Member can determine the transaction type according to the received message; however, such transaction is not included in the authority list or special authority list of the receiver. 

4. The transaction type can be determined according to the message of the Member; however, the message version of the receiver does not support it. 

5. For one IC card transaction, the receiver is in the “Early” state and the receiver does not require ARQC authentication.

41Lost card

The lost card is captured.

43Stolen card

The Issuer confirms that this is a stolen card. Please capture it. 

45Fallback transaction

1.The Issuer does not support fallback transactions of hybrid-card.

2.The Issuer does not support fallback transactions of hybrid-card accepted in this region.

51Insufficient balance

The available balance in the account and the credit limit are insufficient, and the amount is beyond the limit for cash withdrawal.

54Expired card

1.It is an expired card. The expiration date is incorrect. 

2.The expiration date is not present, which should be included in the transaction message.

57Restricted card

1. The type of card cannot be used for such transaction.

2. It is out of the service scope.

3. That type of card cannot be accepted.

4. Deposit cannot be conducted with corporate card.

5. This account does not include this kind of currency. 

6. This card is subject to suspected illegal cash withdrawal 

7. The card number or certificate number is in the blacklist. 

58Restricted terminal

1. The Issuer prohibits the related transaction(s) from being conducted at such kind of terminals (specific to some card BINs).

2. The terminal number in the related transaction does not match that in the original transaction. 

59Suspected fraud

CVN authentication fails. 

61Beyond the transaction amount limit

1. The single transaction amount is beyond the limit

2. The daily transaction amount is beyond the limit.

3. The transaction amount is beyond the limit defined by the Cardholder.

62Restricted card acceptance

Card cannot be accepted in the area; 

64Unable to match with original transaction amount 

1.The transaction amount in the request message does not match that in the response message;

2. The transaction amount in the related transaction message does not match that in the original transaction message

65Beyond the transaction velocity limit

1. Exceed the maximum number of transactions

68Response time-out

The Issuer cannot return the response within the time limit. 

90Cutoff in progress

The daily switch is being conducted. 

91Issuer system malfunction

1. The operation of the Issuer (or the transfer-in side/transfer-out side) is abnormal. 

2. The operation of the Issuer (or the transfer-in side/transfer-out side) is abnormal; however, no stand-in authorization agreement is signed with UNIONPAY. 

3. The Issuer (or the transfer-in side/transfer-out side) signs out but does not sign in. 

4. The operation status of the Issuer (or transfer-in side/transfer-out side) is invalid. 

5. The Issuer (or the transfer-in side/transfer-out side) is closed by UNIONPAY. 

92Routing failure

1. No available connectivity line. 

2. Error in IP address format and/or port number

3. State Administration of Foreign Exchange system is closed, or failed in inquiry therein.

94Duplicated transaction


96UnionPay system malfunction

1. The transaction is rejected due to the malfunction of UNIONPAY.

2. UNIONPAY internal processing failed  

3. UNIONPAY is under maintenance and rejects all requests. 

97Terminal not found

The ATM/POS terminal number has not been registered. 

98Response timeout

The Issuer response is time out  

A2Successful transaction with defect

UNIONPAY has forwarded the original requests, but not received the response from the Issuer.

A3Transfer-in account not found

The bankcard account is not found in the fund transfer-in bank. 

A4Successful transaction with defect

The requests have not been received,  the acceptance of the confirmed related transaction is a successful transaction with defect. 

A5Successful transaction with defect

The original transactions are rejected, the acceptance of the confirmed related transaction is a successful transaction with defect.

A6Successful transaction with defect

UNIONPAY has forwarded the original requests, but the response from the Issuer has not been received. 

A7Security processing failure

1. Failure of key generation 

2. Failure of key activation 

3. Failure of key reset 

4. Failure of ARPC generation  

E0Unauthorized access
E1Invalid message

1. The UPI-JWS is missing

2. The UPI-REQPATH is invalid

3. Other required element in JWS header is missing

4. Format error of the UPI-TIMESTAMP 

5. The UPI-TIMESTAMP expires

6. Duplicate message

E2Signature verification failure
E3System busy, please try again later
PGUnknown message resultPENDING


Encrypted Data

If the message contains sensitive information, the plaintext value of the sensitive data elements are constructed in Encrypted Data object (“encData”) in JSON format, and the whole Encrypted Data object shall be encrypted with JWE method. The JWE<encrypted data> shall be the value of “encData”.  The following data elements shall be included in Encrypted Data.

1.CVN2

2.Cardholder Name

• The encoding of Chinese character shall follow the standard GB18030-2000. No space between Chinese characters in the Chinese name. Where Chinese characters cannot be input, Chinese spelling letters (PIN YIN) can be used instead. Family name comes before given name, separated by space, and with initial letters of both names capitalized. Alternatively, English name can be input with given name followed by surname, separated by a space and the initial letters of both names capitalized.

3.ID Type

• Examples:  01: ID card; 03: Passport; 99: Other ID card

4.ID Number

5.Mobile Number

• Format: country calling code -mobile number

6.PAN (Primary Account Number)

7.Expiry Date

8.OTP (One time password)


Encryption Example

When the message contains “pan” and “expiryDate” as sensitive information.

1.Plaintext is: {“pan”:”6212345678901234”, “expiryDate”:”2012”}

2.Use JWE to encrypt the {“pan”:”6212345678901234”, “expiryDate”:”2012”}

3.Construct the “encData”: JWE< encrypted data>. The JWE<encrypted data> shall be the value of “encData”.  


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