One-Stop Cross-Border Shopping — Shop the World
UnionPay Content & Service Platform (UCSP) for Channel Partner
UnionPay Content & Service Platform (UCSP) for Service Provider
UnionPay Transportation Solutions
Traditionally issuers use 8583 format interface for UnionPay primary credit transaction authorization, which is time-consuming to develop and maintain. UPI Primary Credit Transaction Issuing Backend Interface, which uses JSON message format, serves as an easy and friendly alternative to 8583 interface, and supports multiple primary credit transaction scenarios including cross-border remittance, B2B payout, tax refund, P2P transfer, push purchase and push cash withdrawal, etc.
Flexible
Supporting both internet and leased line connection.
Secure
Supported by well-developed security mechanism.
1. Acquirer initiates primary credit transaction to UPI system.
2. UPI system transfers the authorization request to issuer (in JSON format).
3. Issuer authorizes the transaction and responds to UPI (in JSON format).
4. UPI transfers transaction response to acquirer.
Field name | Identifier | Type | Length | Request | Default value | Note | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Message ID | msgID | AN | 37 | M:Mandatory | "U0001034420171230235959000000" | It is used to match a response to its request. The value must uniquely identify any message that the UNIONPAY API initiates on any day. The value in the response must match the value in the request. Components: “U” + Acquirer IIN + Forwarding IIN+ Transmission Year (YYYY) + Transmission Date and Time (MMDDhhmmss) + System Trace Audit Number (6 numeric digits) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Forwarding IIN | forwardingIIN | AN | 8 | M:Mandatory | “00010344” | The Identifier associate to the payment processor. If the transaction is initiated by the UNIONPAY API, this field shall be filled in with UNIONPAY API IIN. If the transaction is initiated by Gateway, PSP, Payment facilitator, etc., this field shall be filled in with the corresponding identifier assigned by UPI. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Sending Party IIN | "sendPartyIIN" | AN | 8 | M:Mandatory | "00020344" | The distinctive value associated to the Sending Party which manages Payer’s account. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Local Transaction Date &Time | localTxnDateTime | N | 10 | M:Mandatory | Format: MMDDhhmmss | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Card Information Capture Method | captureMethod | N | 2 | M:Mandatory | ”01” | Valid Values: • “00”: UNKNOWN; • “01”: MANUAL; • “03”: CONSUMER_PRESENTED_QRC(chip information included); • “04”: CONSUMER_PRESENTED_QRC(chip information excluded); • “05”: CONTACT; • “07”: NFC; • “10”: STORED_CREDENTIALS; • “93”: MERCHANT_PRESENTED_QRC(chip information included); • “94”: MERCHANT_PRESENTED_QRC(chip information excluded) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Terminal Type | terminalType | N | 2 | M:Mandatory | “08” | Valid Values: “03”: POS; “07”: PC; “08”: MOBILE; Reserved Values: “00”: UNKNOWN | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Merchant ID | merchantID | ANS | 1-15 | M:Mandatory | “ABCDE01” | The distinctive value associated to the Merchant. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Merchant Category Code | mcc | N | 4 | M:Mandatory | Convenience store is represented by "5411". | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Merchant Country Code | merchantCountry | N | 3 | M:Mandatory | "156" | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Merchant Name | merchantName | ANS | 1-25 | M:Mandatory | "UnionPay International" | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Merchant City | "merchantCity" | ANS | 1-12 | M:Mandatory | "Shanghai" | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Terminal ID | “terminalID” | ANS | 1-8 | C:Conditional | The unique value associated to the terminal. It is present in POS or counter transactions (“terminalType” = “03” or “06”). | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Staged Digital Wallet (SDW) ID | sdwID | AN | 8 | C:Conditional | "00010344" | For definition and business cope of SDW, please refer to [UPI OR]. It is present if SDW is used to initiate the transaction. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Payment Facilitator ID (PF ID) | “pfID” | AN | 8 | C:Conditional | The Payment Facilitator ID assigned by UPI.It is present if the transaction is submitted by Merchants registered with the Payment Facilitator, who contracts with the Sending Party as TPSP. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Device ID | "deviceID" | ANS | 1-40 | C:Conditional | 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:Mandatory | "101.10" | The value shall only include (numeric) digits "0" to "9" and may contain a single "." character as the decimal mark. When the amount includes decimals, the "." character shall be used to separate the decimals from the integer value, and the "." character may be present even if there are no decimals. The following are examples of valid Transaction Amounts: "98.73", "98" and "98.". The following are NOT valid Transaction Amounts: "98,73" and "3 705". The value must include the transaction fee amount if it exists. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Transaction Currency | trxCurrency | N | 3 | M:Mandatory | "156" | A 3-digit numeric value, as defined by [ISO 4217], that indicates the currency code of the transaction. The currency also applies to the "discount", "costAmount", and "trxFeeAmt" if they exist. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Fund Source | fundSource | N | C:Conditional | It is present if submitted by the Sending Party.Valid values:0 – cash.1 – debit card .2 – credit card.3 – account funds | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Business Indication | businessIndication | AN | “A1” | M:Mandatory | Valid value: "03": Cash Rebate "06": Tax Refund “14”: B2B Payout "07": Cross-border Remittance Outside of Mainland China "08" Domestic P2P Outside of Mainland China | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Receiving Party IIN | “receivePartyIIN” | AN | 8 | M:Mandatory | The distinctive value associated to the Receiving Party. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Settlement Date | settlementDate | N | 4 | M:Mandatory | "1230" | Format:MMDD | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Settlement Currency | settlementCurrency | N | 3 | C:Conditional | “840” | A 3-digit numeric value, as defined by [ISO 4217], that indicates UNIONPAY API’s settlement currency. Present when the " settlementCurrency " has a different value from "trxCurrency" | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Settlement Amount | settlementAmt | ANS | 1-13 | C:Conditional | “15.17” | The value shall only include (numeric) digits "0" to "9" and may contain a single "." character as the decimal mark. When the amount includes decimals, the "." character shall be used to separate the decimals from the integer value, and the "." character may be present even if there are no decimals. Present when the " settlementCurrency " has a different value from "trxCurrency" | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Settlement Conversion Rate | settlementConvRate | ANS | 1-9 | C:Conditional | "71212345" | The 1st digit indicates the number position where the decimal point should be moved from the right (allowed values are 0–7). The 2nd-final digits indicate the value of the conversion rate, and are right justified with no decimal point. For example, 71212345 indicates that the conversion rate is 0.1212345. Present when the " settlementCurrency " has a different value from "trxCurrency" | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Cardholder Billing Currency | cardholderBillingCurrency | N | 3 | C:Conditional | “840” | A 3-digit numeric value, as defined by [ISO 4217], that indicates the currency code of the card account. Present when the "cardholderBillingCurrency" has a different value from "trxCurrency" | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Cardholder Billing Amount | cardholderBillingAmt | ANS | 1-13 | C:Conditional | “15.17” | The value shall only include (numeric) digits "0" to "9" and may contain a single "." character as the decimal mark. When the amount includes decimals, the "." character shall be used to separate the decimals from the integer value, and the "." character may be present even if there are no decimals. Present when the "cardholderBillingCurrency" has a different value from "trxCurrency" | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Cardholder Billing Conversion Rate | cardholderBillingConvRate | ANS | 1-9 | C:Conditional | "71212345" | The 1st digit indicates the number position where the decimal point should be moved from the right (allowed values are 0–7). The 2nd-final digits indicate the value of the conversion rate, and are right justified with no decimal point. For example, 71212345 indicates that the conversion rate is 0.1212345. Present when the "cardholderBillingCurrency" has a different value from "trxCurrency" | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Conversion Date | conversionDate | N | 4 | C:Conditional | "1230" | Present if either "settlementAmt" or “cardholderBillingAmt”exists. Format: MMDD | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Retrieval Reference Number | "retrievalReferenceNumber" | AN | 12 | M:Mandatory | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Payment Reference Number (PAR) | par | AN | 29 | C:Conditional | It is present when PAR is available. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Payer’s Information | payerInfo | Object | C:Conditional | This Payer’s Information is in use of verification or anti money laundering. It is present upon business requirement. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Risk Information | riskInfo | Object | O:Optional | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Token Information | tokenInfo | Object | C:Conditional | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Filed name | Identifier | Type | Length | Request | Default value | Note | |||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Message ID | msgID | AN | 37 | R:Returned | "U0001034420171230235959000000" | It is used to match a response to its request. The value must uniquely identify any message that the UNIONPAY API initiates on any day. The value in the response must match the value in the request. Components: “U” + Acquirer IIN + Forwarding IIN+ Transmission Year (YYYY) + Transmission Date and Time (MMDDhhmmss) + System Trace Audit Number (6 numeric digits) | |||||||||||||||||||||||||
Fund Source | fundSource | N | M:Mandatory | It is present if submitted by the Sending Party.Valid values:0 – cash.1 – debit card .2 – credit card.3 – account funds | |||||||||||||||||||||||||||
Business Indication | businessIndication | AN | “A1” | C:Conditional | Valid value: "03": Cash Rebate "06": Tax Refund “14”: B2B Payout "07": Cross-border Remittance Outside of Mainland China "08" Domestic P2P Outside of Mainland China | ||||||||||||||||||||||||||
Message Response | msgResponse | Object | M:Mandatory | ||||||||||||||||||||||||||||
|
Field name | Identifier | Type | Length | Request | Default value | Note | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Message ID | msgID | AN | 37 | M:Mandatory | "U00010340001034420171230235959000000" | It is used to match a response to its request. The value must uniquely identify any message that the institution initiates on any day. The value in the response must match the value in the request.Format: “U”+ Sending Party IIN + Forwarding IIN + Transmission Date and Time (YYYYMMDDhhmmss) + System Trace Audit Number (6 numeric digits)Transmission Date and Time shall be filled by Beijing time (UTC+8). | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Original Message ID | originalMsgID | AN | 37 | M:Mandatory | “S0001034420190711235959123456” | The same value as the “msgID” of the corresponding ISSUER_PRIMARY_CREDIT message. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Forwarding IIN | forwardingIIN | AN | 8 | M:Mandatory | “00010344” | The distinctive value associated to the institution that connected to UPI. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Sending Party IIN | sendPartyIIN | AN | 8 | M:Mandatory | "00020344" | The distinctive value associated to the Sending Party which manages Payer’s account. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Local Transaction Date &Time | localTxnDateTime | N | 10 | M:Mandatory | Format: MMDDhhmmss | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Card Information Capture Method | captureMethod | N | 2 | M:Mandatory | "94" | Valid Values:“01”: Manual“02”: Magnetic stripe read"03": Consumer-presented QR Code (QRC), chip information included"04": Consumer-presented QRC (barcode also), chip information excluded"05": Integrated circuit card read, card data reliable (contact)"07": qUICS Debit/Credit Integrated Circuit Card read (contactless)“10”: Stored Credential “93”: Merchant-presented QRC, chip information included“94”: Merchant-presented QRC (barcode also), chip information excludedOther values: Reserved | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Terminal Type | terminalType | N | 2 | M:Mandatory | “08” | Valid Values:“03”: POS“06”: Counter“07”: PC “08”: Mobile Device "24": PAD "25": Watch Other values: Reserved | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Merchant ID | merchantID | ANS | 1-15 | M:Mandatory | The merchant identifier associated to a merchant of the acquirer. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Merchant Category Code | mcc | N | 4 | M:Mandatory | "156" | A 4-digit numeric value, as defined by [UPI OR], indicates the merchant type. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Merchant Country Code | merchantCountry | N | 3 | M:Mandatory | “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:Mandatory | "UnionPay International" | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Merchant City | merchantCity | ANS | 1-12 | M:Mandatory | "Shanghai" | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Terminal ID | terminalID | ANS | 1-8 | C:Conditional | The unique value associated to the terminal. It is present in POS or counter transactions (“terminalType” = “03” or “06”). | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Staged Digital Wallet (SDW) ID | sdwID | AN | 8 | C:Conditional | "00010344" | For definition and business cope of SDW, please refer to [UPI OR]. It is present if SDW is used to initiate the transaction. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Payment Facilitator ID (PF ID) | pfID | AN | 8 | C:Conditional | The Payment Facilitator ID assigned by UPI. It is present if the transaction is submitted by Merchants registered with the Payment Facilitator, who contracts with the Sending Party as TPSP. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Device ID | deviceID | ANS | 1-40 | C:Conditional | 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:Mandatory | "101.10" | The value shall only include (numeric) digits "0" to "9" and may contain a single "." character as the decimal mark. When the amount includes decimals, the "." character shall be used to separate the decimals from the integer value, and the "." character may be present even if there are no decimals. The following are examples of valid Transaction Amounts: "98.73", "98" and "98.". The following are NOT valid Transaction Amounts: "98,73" and "3 705". | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Transaction Currency | trxCurrency | N | 3 | M:Mandatory | "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". The currency also applies to the "discount", "costAmount", and "trxFeeAmt" if they exist. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Fund Source | fundSource | N | 1 | C:Conditional | It is present if submitted by the Sending Party. Valid values:0 – cash 1 – debit card 2 – credit card 3 – account funds | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Business Indication | businessIndication | AN | 2 | M:Mandatory | “A1” | Valid value: "03": Cash Rebate "06": Tax Refund "14": Payout "07": Cross-border Remittance Outside of Mainland China "08" Domestic P2P Outside of Mainland China "A1": Inbound China Remittance | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Receiving Party IIN | receivePartyIIN | AN | 8 | M:Mandatory | The distinctive value associated to the Receiving Party. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Settlement Date | settlementDate | N | 4 | M:Mandatory | Format: MMDD | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Settlement Amount | settlementAmt | ANS | 1-13 | C:Conditional | It is present when transaction currency is different from settlement currency. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Settlement Currency | settlementCurrency | N | 3 | C:Conditional | It is present when transaction currency is different from settlement currency. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Settlement Conversion Rate | settlementConvRate | ANS | 1-9 | C:Conditional | It is present when transaction currency is different from settlement currency. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Cardholder Billing Amount | cardholderBillingAmt | ANS | 1-13 | C:Conditional | It is present when transaction currency is different from cardholder billing currency. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Cardholder Billing Currency | cardholderBillingCurrency | N | 3 | C:Conditional | It is present when transaction currency is different from cardholder billing currency. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Cardholder Billing Conversion Rate | cardholderBillingConvRate | ANS | 1-9 | C:Conditional | It is present when transaction currency is different from cardholder billing currency. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Conversion Date | conversionDate | N | 4 | C:Conditional | "1230" | Format: MMDD It is present if either "settlementAmt" or “cardholderBillingAmt”exists | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Retrieval Reference Number | retrievalReferenceNumber | AN | 12 | M:Mandatory | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Encrypted Data | encData | Object | M:Mandatory | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Payment Reference Number (PAR) | par | AN | 29 | C:Conditional | It is present when PAR is available. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Payer’s Information | payerInfo | Object | C:Conditional | This Payer’s Information is in use of verification or anti money laundering. It is present upon business requirement. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Risk Information | riskInfo | Object | O:Optional | It is present if the mobile device is used to initiate the transaction. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Token Information | tokenInfo | Object | C:Conditional | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Filed name | Identifier | Type | Length | Request | Default value | Note | |||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Message ID | msgID | AN | 37 | R:Returned | "U00010340001034420171230235959000000" | It is used to match a response to its request. The value must uniquely identify any message that the institution initiates on any day. The value in the response must match the value in the request.Format: “U”+ Sending Party IIN + Forwarding IIN + Transmission Date and Time (YYYYMMDDhhmmss) + System Trace Audit Number (6 numeric digits)Transmission Date and Time shall be filled by Beijing time (UTC+8). | |||||||||||||||||||||||||
Message Response | msgResponse | M:Mandatory | |||||||||||||||||||||||||||||
|
UnionPay International has adopted unified security requirement, please refer to UPI Server-based API General Requirements for signature and encryption guide.
1. The UnionPay API system sends the ISSUER_PRIMARY_CREDIT request to the payee’s account management institution, i.e. the Receiving Party.
2. The Receiving Party confirms the accuracy and legitimacy of the payee information and conducts necessary risk controls checking, then responds to the UnionPay API.
Exceptional flows:
1. The UnionPay API does not receive the ISSUER_PRIMARY_CREDIT response message within 40s, the UnionPay API initiates the ISSUER_PRIMARY_CREDIT_CONFIRMATION request message to the Receiving Party.
2. The Receiving Party returns the ISSUER_PRIMARY_CREDIT_CONFIRMATION response message to the UnionPay API.
If you are UPI issuers member, you need to fill in the Application Form of API Service Product with Terms and Conditions.
When the business goes online, the card issuing bank shall conduct key exchange with UnionPay international to ensure the transaction security, and the card issuing bank shall submit system parameters such as IIN and API called address
Please contact Developer Operation Team by submitting orders