Open API >Information Service >Bankcard Verification
Bankcard Verification
Information Service Merchant Acquirer Issuer Non-financial Institutions
Verify the consistency of cardholder‘s real name information of bankcard.
API Introduction
API Introduction
What is it?

Based on real name information from authoritative data sources, Bankcard verification service can verify the consistency of bankcard number, name, ID number and/or mobile number under the premise of obtaining the authorization of the cardholder.

Key Features

Real name Verification

When to Use it?

Bank: Account Opening

Insurance company: Insurance Claims

Securities company:  Account Opening & Bind card to pay


Who Use it?
Financial & non-financial institutions that demands to verify identity information of domestic residents.
Where to Use it?
This API is available globally.
Flow Chart
Flow Chart

银行卡信息验证-流程图.png

1.Merchant / Institution provides bankcard information to be verified

2.UPI System transmits the bankcard information to Issuer

3.Issuer returns verification result to UPI

4.UPI returns verification result to Merchant / Institution


API Reference
API Reference
  • BANKCARD_VERIFICATION
Interface description
BANKCARD_VERIFICATION API is used to verify whether the card number is consistent with the customer’s information.
Request Method
HTTP POST
Request Parameter
Field name Identifier Type Length Request Default value Note
Member IIN memberIIN AN 8 M:Mandatory The distinctive value associated to the Member by UPI. If you are already a member, please fill your IIN here.If you are a merchant, please fill your acquirer’s IIN here.
Member Name memberName ANS 1-40 M:Mandatory The UPI member’s name. If you are already a member, please fill your name here.If you are a merchant, please fill your acquirer’s name here.
Merchant ID merchantID ANS 1-15 C:Conditional The distinctive value associated to the Merchant. The value must uniquely identify any Merchant of the Acquirer.If you are already a member, the field will not be presented.If you are a merchant, please fill your MID here.
Merchant Name merchantName ANS 1-25 C:Conditional The Merchant that uses the API interface.If you are already a member, the field will not be presented.If you are a merchant, please fill your name here.
Merchant Category Code mcc N 4 C:Conditional If you are already a member, the field will not be presented.If you are a merchant, please fill your MCC here.
Trade Type tradeType N 4 M:Mandatory The value of trade type is as follows: 0201: two-element-verification (Card Number and Customer Name); 0202: two-element-verification (Card Number and ID Number); 0301: three-element-verification (Card Number, Customer Name and ID Number); 0302: three-element-verification (Card Number, ID Number and Mobile Number); 0401: four-element-verification (Card Number, ID Number, Mobile Number and Customer Name)
Encrypted Data encData Object M:Mandatory JWE
Card Number cardNo ANS 14-19 M:Mandatory Encrypted with the public key of the Encryption Certificate.
Customer Name customerNm S 1-66 C:Conditional Encrypted with the public key of the Encryption Certificate. The name shall be in Simplified Chinese
Mobile Number phoneNo ANS 11 C:Conditional Encrypted with the public key of the Encryption Certificate. District code shall not be included.
ID Number certifID ANS 1-20 C:Conditional Encrypted with the public key of the Encryption Certificate.
Transaction Order ID orderID ANS 35 M:Mandatory Generated by Participants side, it should be unique.
Usage Scenarios scUsageScenarios ANS 2-40 M:Mandatory The scenario that the Participants uses the API interface.
Use Purpose scUsePurpose ANS 2-128 M:Mandatory The purpose that the Participants uses the API interface.
Protocol Version Number protocolVerNm ANS 2-128 M:Mandatory The protocol version number of the electronic agreement that the customer signed with the Participants.
Serial Number serialNm ANS 14-64 M:Mandatory The serial number of the electronic agreement that the customer signed with the Participants. The serial number should be able to locate the date of signing the agreement. Pad “0” ahead if digits are insufficient.
Synchronous Response parameters
Filed name Identifier Type Length Request Default value Note
Message Response msgResponse Object M:Mandatory
Response Code responseCode AN 2 M:Mandatory It contains a code that defines the response to a request.
Response Message responseMsg S 1-100 M:Mandatory It contains the request result and the rejection reason if the request fails. The value of this field can be displayed by the Gateway to notify the user of the request outcome.
Error Details errorDetail S 1-255 C:Conditional It contains additional detail regarding the problem identified in the message.
Security Requirement
Security Requirement


UnionPay International has adopted unified security requirement, please refer to UPI Server-based API General Requirements  for signature and encryption guide.


Steps to Launch
Steps to Launch

Please submit order to contact Developer Team

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