Open API >Account Service >SaaS Card Issuing Service Platform for App Gateway
SaaS Card Issuing Service Platform for App Gateway
Account Service Developer Issuer Mobile Payment
SaaS Card Issuing Service Platform (SCIS for short) provides a convenient and secure UnionPay standard card issuing solution. By using the SCIS services, App providers can apply for issuer’s virtual card and the virtual 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 APP providers by leased line or internet. SCIS open API for APP Gateway is a set of APIs provide card enrollment functions and mobile transactions 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.


▪ 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 App providers want to collaborate with SCIS-enabled issuer to use virtual card in mobile transactions. 

Who Use it?
Issuers and App providers authorized by the issuers.
Where to Use it?
This API is available globally except for mainland China.
Things to Know

1. The App providers should be authorized by issuers.

2. The security control of user-side is handled by App and its Gateway.

3. Messages exchanged between the Application Gatewayand the SaaS Card Issuing System(abbreviated as SCIS) are recommended to be in the JSON data interchange format as defined in RFC 7159.

4. The communication mode of SCIS is HTTP, using HTTP(S) protocols. The complete structure of HTTP messages shall contain the HTTP header and body, the HTTP message structure and security is specified in UPI Server-based API General Requirements


Flow Chart
Flow Chart

SCIS for app gateway 业务流程图.png

API Reference
API Reference
  • CVM Inquiry
  • KYC Verification
  • Open Account
  • Card Enrollment
  • Cardface Downloading
  • Account Update Notification
  • Account Update
  • Card Status Management
  • Card Status Notification
  • Card Status Inquiry
  • Card Balance Inquiry
  • Exchange Rate Inquiry
  • P2P Transfer
  • QRC Generation
  • Additional Processing
  • Additional Processing Result
  • Transaction Result Notification
  • Cash Out Token
  • QRC Info Inquiry
  • MPQRC Payment EMV
  • MPQRC Payment URL
  • Bill Payment
  • Credit Transaction
  • Transaction Result Inquiry
Interface description
This message is sent by APPGW to SCIS to get the list of cardholder verification(CV) methods required.
Request Parameter
Field name Identifier Type Length Request Default value Note
Message Information msgInfo  Object M:Mandatory “msgType” value is “CVM_INQUIRY”
Version Number versionNo ANS 5 M:Mandatory Valid Value: "1.0.0"
Message ID msgID AN 17-49 M:Mandatory It is used to match a response to its request. The value must be unique on any message and any day. The value in the response must match the value in the request. Note: Components: "A"/”M”/”U”+ INS ID +Serial Number. "A" is used to indicate this request is generated from an application gateway institutions system. "M" is used to indicate this request is generated from a member institutions system. “U” is used to indicate this request is generated from the UPI system.
Time Stamp timeStamp N 14 M:Mandatory The value in the response must match the value in the request.
Message Type msgType ANS 1-50 M:Mandatory YYYYMMDDhhmmss
INS ID insID AN 1-16 M:Mandatory The distinctive value associated to a institution.
Transaction Information trxInfo Object O:Optional
Card product code prdNo AN 1-4 O:Optional
Synchronous Response parameters
Filed name Identifier Type Length Request Default value Note
Message Information msgInfo  Object M:Mandatory “msgType” value is “CVM_INQUIRY”
Version Number versionNo ANS 5 M:Mandatory Valid Value: "1.0.0"
Message ID msgID AN 17-49 M:Mandatory It is used to match a response to its request. The value must be unique on any message and any day. The value in the response must match the value in the request. Note: Components: "A"/”M”/”U”+ INS ID +Serial Number. "A" is used to indicate this request is generated from an application gateway institutions system. "M" is used to indicate this request is generated from a member institutions system. “U” is used to indicate this request is generated from the UPI system.
Time Stamp timeStamp N 14 M:Mandatory The value in the response must match the value in the request.
Message Type msgType ANS 1-50 M:Mandatory YYYYMMDDhhmmss
INS ID insID AN 1-16 M:Mandatory The distinctive value associated to a institution.
Transaction Information trxInfo Object C:Conditional
Cardholder Verification Method cvm Array 1-255 C:Conditional List of the cardholder verification (CV) methods required. The mobile application shall collect these information from the cardholder. Valid CVs are : • "pan" • "accountNo" • "expiryDate" • "cvn2" • "firstName" • "midName" • "lastName" • "idType" • "idNo", • "mobileNo" • "idCountry" Note1:The "idType", "idNo" and “idCountry” shall be present together. Note 2: If no CV method is required, the object shall be "cvm": [] Present if the Response Code is "00".
Message Response msgResponse Object M:Mandatory
Response Code responseCode AN 2 M:Mandatory It contains a code that defines the response to a request. Please refer to the Response Code and Message for the valid values.
Response Message responseMsg S 1-100 M:Mandatory 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 consumer of the payment outcome. Please refer to the Response Code and Message for details.
Sample code
Request code
Other
{
"msgInfo":
{
"versionNo":"1.0.0",
"msgID":"A3999999920190808154804701987",
"timeStamp":"20190808154804",
"msgType":"CVM_INQUIRY",
"insID":"39999999"
},
"trxInfo":{}
}


Response code
Other
{
"msgInfo":
{
"versionNo":"1.0.0",
"msgID":"A3999999920190808154804701987",
"timeStamp":"20190808154804",
"msgType":"CVM_INQUIRY",
"insID":"39999999"
},
"trxInfo":
{
"cvm":["firstName","midName","lastName","idType","idNo","idCountry"]
},
"msgResponse":
{
"responseCode":"00",
"responseMsg":"Approved"
}
}