Open API >Payment >SaaS Card Issuing Service Platform for Issuers
SaaS Card Issuing Service Platform for Issuers
Payment Developer Issuer Mobile Payment
SaaS Card Issuing Service Platform (SCIS for short) provide a convenient and secure UnionPay standard card issuing solution. By using the SCIS services, issuers outside of mainland China can issue their own UnionPay card and support UnionPay card transactions.
API Introduction
API Introduction
What is it?

SaaS Card Issuing Service Platform (SCIS for short) is a SaaS service that can be accessed by issuers outside of mainland China by leased line. SCIS for issuers is a set of APIs providing virtual card issuance and transaction functions.

Key Features

▪ Easy to maintain

SCIS is a unified service solution based on SaaS service, deployed and maintained by UPI, so as to save maintenance work and cost for issuers.


▪ Easy to access

SCIS has integrated with various UPI platforms, issuers only need to follow the SCIS interface specification to achieve a variety of business services, including QR Code transaction, virtual card transaction.


▪ Security

JWS, JWE are used to sign and encrypt online messages. Sensitive data will be encrypted before stored. All security standards follow the requirements of PCI specification. 


▪ Business Expansibility

The issued cards meet the standards of UnionPay and can be used in the existing bank card transactions, helping issuers to get benefit from UnionPay's new business expansion.


When to Use it?

When issuers want to use SCIS to issue their own UnionPay card for their customers. 

Who Use it?
Issuers outside of mainland China that are authorized to issue UnionPay card, or third-party developers that serve such issuers.
Where to Use it?
This API is available globally except for mainland China.
Things to Know

1. Issuers should use leased line to access SCIS.

2. Issuers' banking system should support both Debit Transaction and Credit Transaction.

3. If issuer want to provide P2P Transfer service for customers, P2P Transfer API shall be supported.

4. SCIS only manages card information, account information and account fund should be managed independently by issuer itself


Flow Chart
Flow Chart

SCIS for app gateway 业务流程图.png

API Document
API Document
Response Code Reference
Response Code Reference
Response code Description
00 Approved or completed successfully
01 Refer to card Issuers
03 Invalid merchant
04 Pick-up
05 ID certification fails
10 Partial amount approved
11 VIP
12 Invalid related transaction
13 Invalid amount
14 Invalid card number (no such account)
15 No such Issuer
16 Approve update of track 3
21 Card not initialized
22 Suspected malfunction,related transaction error
25 Unable to locate the original transaction
30 Format error
34 Fraud
38 PIN try limit exceeded
40 Function requested not supported
41 Lost card
43 Stolen card
45 Fallback transaction is not allowed
51 Insufficient balance
54 Expired card.
55 Incorrect personal identification number
57 Transaction not allowed to be processed by Cardholder
58 Transaction not allowed to be processed by terminal
59 Suspected fraud
61 Transaction amount limit exceeded
62 Restricted card
64 Original transaction amount error
65 Exceeds withdrawal velocity limit
68 Issuer response time-out
75 Allowable number of PIN tries exceeded
90 Cutoff is in progress
91 Issuer not capable to process
92 Financial institution or intermediate network facility cannot be found for routing
94 Duplicated transaction
96 Switch system malfunction
97 ATM/POS terminal number cannot be located
98 Issuer response not received
99 PIN Block Error
A0 MAC failed
A1 Reserved
A2 Successful transaction with defect
A3 Account not found in Transfer-in side
A4 Successful transaction with defect
A5 Successful transaction with defect
A6 Successful transaction with defect
A7 Security processing failure
B1 No arrears (transaction receipt not printed)
C1 Illegal Status of Acquirer
D1 Incorrect IIN
D2 Date Error
D3 Invalid file type
D4 File processed
D5 No such file
D6 Not supported by Receiver
D7 File locked
D8 Unsuccessful
D9 Incorrect file length
DA File decompression error
DB File name error
DC File cannot be received
F1 File record format error
F2 File record repeated
F3 File record not existing
F4 File record error
N1 Items not on Bankbook beyond limit, declined
P1 Contact number (e.g. mobile phone number) of cardholder cannot be found in Issuer’s system
Sequence Chart
Sequence Chart

• Issuing Virtual Card

The applicant applies for a new virtual card, Issuer will verify the application information and open a new account, the SCIS issue a new virtual card binding with the new account.

【AP】1、Issuing Virtual Card--Open new account.png

1. The App Gateway submits KYC_VERIFICATION request to the SCIS.

2. The SCIS forwards the request to the Core Banking System.

3. The Core Banking System verify the applicant’s information provided in the request and returns KYC_VERIFICATION response to the SCIS.

4. The SCIS forwards the KYC_VERIFICATION response to the App Gateway.

5. The App Gateway receives the KYC_VERIFICATION response, if the verification result is “AppROVED”, App Gateway submits OPEN_ACCOUNT request to the SCIS, the OPEN_ACCOUNT request will reference to the KYC_VERIFICATION.

6. The SCIS forwards the request to the Core Banking System.

7. The Core Banking System opens a new account base on the OPEN_ACCOUNT request and the  referenced KYC_VERIFICATION, Core Banking System returns OPEN_ACCOUNT response to the SCIS.

8. The SCIS receives the OPEN_ACCOUNT response and issues a new virtual card binding with the new account. SCIS returns OPEN_ACCOUNT response to the App Gateway, App Gateway get the new virtual card information and the new token information in the response message.


• Merchant-presented QR code payment(EMV mode)

The cardholder scans merchant’s QR code to get merchant’s information and initiates payment transaction, the SCIS checks the payment transaction and requests the issuer to debit cardholder’s account.

【AP】3、Merchant-presented QR code payment(EMV mode).png

1. The App Gateway submits MPQRC_PAYMENT_EMV request to the SCIS.

2. The SCIS checks the payer’s card information provided in the MPQRC_PAYMENT_EMV request and submits DEBIT_TRANSACTION request to the Core Banking System.

3. The Core Banking System checks the account information provided in the DEBIT_TRANSACTION request and debit the account.The processing result is returns to the SCIS by DEBIT_TRANSACTION response.

4. The SCIS receives the DEBIT_TRANSACTION response, and returns MPQRC_PAYMNET_EMV response to the App Gateway.


• Merchant-presented QR code payment(URL mode)

The cardholder scans QR code of merchant in mainland China to get merchant’s information and initiates payment transaction, the SCIS checks the payment transaction and requests the issuer to debit cardholder’s account.

【AP】4、Merchant-presented QR code payment(URL mode).png

1. The App Gateway submits QRC_INFO_INQUIRY request to the SCIS.

2. The SCIS receives QRC_INFO_INQUIRY request and returns QRC_INFO_INQUIRY response to the App Gateway.

3. The App Gateway get merchant information in the QRC_INFO_INQUIRY response,and submits MPQRC_PAYMENT_URL request to the SCIS.

4. The SCIS checks the payer’s card information provided in the MPQRC_PAYMENT_URL request, and submits DEBIT_TRANSACTION request to the Core Banking System.

5. The Core Banking System checks the account information provided in the DEBIT_TRANSACTION request and debit the account.The processing result is returns to the SCIS by DEBIT_TRANSACTION response.

6. The SCIS receives the DEBIT_TRANSACTION response, and returns MPQRC_PAYMNET_URL response to the App Gateway.


• Consumer-presented QR code payment

After the merchant scans the QR Code presented in the App, the merchant will submits a QRC payment request, the SCIS checks the payment transaction and requests the issuer to debit cardholder’s account.

Part 1: QRC Generate

【AP】5、Consumer-presented QR code payment.png

1. The App Gateway submits QRC_GENERATION request to the SCIS.

2. The SCIS receives QRC_GENERATION request and returns QRC_GENERATION response to the App Gateway, App Gateway get the consumer-presented QR code in the response.


Part 2: Consumer-presented QR Code Payment

【AP】5、Consumer-presented QR code payment-2.png

1. The merchant scans the QR Code presented in the App and submits Payment request, if the transaction amount of the Payment request exceeds the wallet’s CVM limit,an ADDITIONAL_PROCESSING request is sent to the App Gateway.

2. The App Gateway accepts the ADDITIONAL_PROCESSING request and sends ADDITIONAL_PROCESSING response to the SCIS.

3. The App Gateway notifies cardholder to input verification information on the App, and sends ADDITIONAL_PROCESSING_RESULT request to the SCIS.

4. The SCIS receives ADDITIONAL_PROCESSING_RESULT request and returns ADDITIONAL_PROCESSING_RESULT response to the App Gateway.

5. If the ADDITIONAL_PROCESSING_RESULT request authorizes to continue the payment transaction, the SCIS submits DEBIT_TRANSACTION request to the Core Banking System.

6. The Core Banking System checks the account information provided in the DEBIT_TRANSACTION request and debit the account. The processing result is returns to the SCIS by DEBIT_TRANSACTION response.

7. The SCIS receives the DEBIT_TRANSACTION response and sends TRX_RESULT_NOTIFICATION request to the App Gateway.

8. The App Gateway receives the notification request and returns TRX_RESULT_NOTIFICATION response to the SCIS, the App Gateway notifies the cardholder the payment result. 


• Bill Payment

The App Gateway initiates Bill Payment request, the issuer debits the cardholder’s account and credits the preset merchant’s account.

【AP】6、Bill Payment.png

1. The App Gateway submits BILL_PAYMENT request to the SCIS.

2. The SCIS receives the BILL_PAYMENT request and submits DEBIT_TRANSACTION request to the Core Banking System.

3. The Core Banking System checks the account information and merchant information provided in the DEBIT_TRANSACTION request, the Core Banking System debits the payer’s account and credits the merchant’s account.The processing result is returns to the SCIS by DEBIT_TRANSACTION response.

4. The SCIS receives the DEBIT_TRANSACTION response, and sends BILL_PAYMENT response to the App Gateway.


• Credit Transaction

The App Gateway initiates Credit Transaction request, the issuer debits the preset merchant’s account and credits the cardholder’s account.

【AP】7、Credit Transaction.png

1. The App Gateway submits CREDIT_TRANSACTION request to the SCIS.

2. The SCIS receives the CREDIT_TRANSACTION request and submits CREDIT_TRANSACTION request to the Core Banking System.

3. The Core Banking System checks the account information and merchant information provided in the CREDIT_TRANSACTION request, the Core Banking System debits the merchant’s account and credits the  payee’s account.The processing result is returns to the SCIS by CREDIT_TRANSACTION response.

4. The SCIS receives the CREDIT_TRANSACTION response, and sends CREDIT_TRANSACTION response to the App Gateway.


• P2P Transfer

The App Gateway initiates P2P Transfer request, the issuer debits the payer’s account and credits the payee’s account.

【AP】8、P2P Transfer.png

1. The App Gateway submits P2P_TRANSFER request to the SCIS.

2. The SCIS receives the P2P_TRANSFER request and checks the card information provided in the request, the SCIS forwards the P2P_TRANSFER request to the Core Banking System.

3. The Core Banking System checks the account information provided in the P2P_TRANSFER request, the Core Banking System debits the payer’s account and credits the payee’s account. The processing result is returns to the SCIS by P2P_TRANSFER response.

4. The SCIS receives the P2P_TRANSFER response, and forwards to the App Gateway.


Steps to Launch
Steps to Launch

Step 1: Apply for institution code and card BIN.

Step 2: Apply to access SCIS.

Step 3: Product Testing.

Step 4: Business 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.