All Products
Search

This Product

    ID Verification:BANK_CARD_N_META

    Document Center

    ID Verification:BANK_CARD_N_META

    Last Updated:Jun 25, 2026

    Verify bank card holder identity through 2-factor, 3-factor, or 4-factor verification using the BankMetaVerifyIntl API

    API description

    • API operation: BankMetaVerifyIntl

    • Request method: POST and GET

    • Transport protocol: HTTPS

    • Description: Verifies bank card holder information. Supported verification types:

      • 2-factor bank card verification (bank card number + name)

      • 3-factor bank card verification (bank card number + name + certificate number)

      • 4-factor bank card verification (bank card number + name + certificate number + mobile number)

    • QPS limit: Each API has a dedicated QPS limit. For details, see QPS limits of ID Verification server-side APIs.

    • Endpoints:

      Note

      • Benefits of internal network access: An internal network enables private communication between Alibaba Cloud services in the same region. If your application server is also in the same region, use the internal network endpoint to access the ID Verification service for a more secure and stable connection. 

      • Optimization for overseas access: Network conditions outside the Chinese mainland can be complex. To reduce latency and minimize request failures, optimize your integration by following the best practices in Server-side Network Latency Analysis and Optimization.

      China (Hong Kong)

      • Public endpoint: cloudauth-intl.cn-hongkong.aliyuncs.com

      • Internal endpoint: cloudauth-intl-vpc.cn-hongkong.aliyuncs.com

    Online debugging and integration

    Note

    Before you debug or integrate, read the Debug and integrate server-side APIs with OpenAPI guide to understand how to call APIs on the OpenAPI platform and how to obtain the SDK.

    You can debug this API operation in OpenAPI Explorer. You can also generate sample SDK code for this API operation.

    Request parameters

    Name

    Type

    Required

    Description

    Example

    ProductCode

    String

    Yes

    Static field: BANK_CARD_N_META

    BANK_CARD_N_META

    ParamType

    String

    Yes

    Encryption method:

    • normal: Not encrypted (plaintext).

    • md5: MD5-encrypted.

    Important

    • The ciphertext for all parameters must be a 32-bit lowercase MD5 string.

    • Different MD5 tools may produce different ciphertexts. If an API call works before encryption but fails after, try a different MD5 tool.

    normal

    VerifyMode

    String

    Yes

    VERIFY_BANK_CARD: Bank card authentication mode.

    Checks whether the bank card number matches the holder's name, certificate number, and mobile number.

    VERIFY_BANK_CARD

    ProductType

    String

    Yes

    Product type to call:

    • BANK_CARD_2_META: Verifies the bank card number and name.

    • BANK_CARD_3_META: Verifies the bank card number, name, and certificate number.

    • BANK_CARD_4_META: Verifies the bank card number, name, certificate number, and mobile number.

    BANK_CARD_4_META

    BankCard

    String

    Yes

    Bank card number:

    • If ParamType is set to normal, enter the plaintext of the bank card number.

    • If ParamType is set to md5, enter the plaintext of the bank card number except for the last 6 digits, followed by the ciphertext of the last 6 digits.

    • Plaintext: 12345678******

    • Ciphertext: 12345678f8ee21920e37807b43e7e912ab******

    UserName

    String

    Yes

    Name:

    • If ParamType is set to normal, enter the plaintext of the name.

    • If ParamType is set to md5, enter the ciphertext of the first character of the name, followed by the plaintext of the rest of the name.

    • Plaintext: Zhang San

    • Ciphertext: 6499fc7409049355527ef6a2ba5706b8San

    IdentityType

    String

    No

    Certificate type. Defaults to ID card if left empty. For other types, see the Certificate type list.

    01

    IdentifyNum

    String

    No

    Certificate number:

    • If ParamType is set to normal, enter the plaintext of the certificate number.

    • If ParamType is set to md5:

      • For an ID card number, enter the plaintext of the first 6 digits, followed by the ciphertext of the date of birth, and then the plaintext of the last 4 digits.

      • For other certificate types, encrypt the last two digits using MD5.

    Important

    This parameter is required if ProductType is set to one of the following values:

    • BANK_CARD_3_META

    • BANK_CARD_4_META

    • Plaintext: 429001********8211

    • Ciphertext: 42900132fa7bcd874161bea8ec8fd98f******8211

    Mobile

    String

    No

    Mobile number:

    • If ParamType is set to normal, enter the plaintext of the mobile number.

    • If ParamType is set to md5, enter the ciphertext of the mobile number.

    Important

    This parameter is required if ProductType is set to BANK_CARD_4_META.

    • Plaintext: 186****2055

    • Ciphertext: 849169cd3b20621c1c78bd61a1******

    Certificate type list

    IdentityType

    Certificate

    01

    ID card

    02

    Officer's certificate

    03

    Passport

    04

    Mainland Travel Permits for Hong Kong and Macao Residents

    05

    Mainland Travel Permit for Taiwan Residents

    06

    Police officer's certificate

    07

    Soldier's certificate

    08

    Foreign passport

    09

    Foreign Permanent Resident ID Card

    10

    Residence Permit for Hong Kong and Macao Residents

    11

    Residence Permit for Taiwan Residents

    12

    Travel permit

    13

    Exit-Entry Permit

    Response parameters

    Name

    Type

    Description

    Example

    RequestId

    String

    The request ID.

    130A2C10-B9EE-4D84-88E3-5384FF******

    Code

    String

    Return code: For more information, see Server-side HTTP status codes.

    Success

    Message

    String

    A detailed description of the response code.

    success

    ResultObject

    BizCode

    String

    Verification result:

    • 1: Consistent (billed)

    • 2: Inconsistent (billed)

    • 3: No record found (not billed)

    1

    SubCode

    String

    Verification details:

    • 101: Verification passed.

    • 201: Inconsistent authentication information. The cardholder information is incorrect.

    • 202: Inconsistent authentication information. Authenticated payment is not enabled for the bank card.

    • 203: Inconsistent authentication information. The bank card has expired.

    • 204: Inconsistent authentication information. The bank card is restricted.

    • 205: Inconsistent authentication information. This card has been confiscated.

    • 206: Inconsistent authentication information. The bank card is invalid.

    • 207: Inconsistent authentication information. This card has no corresponding issuing bank.

    • 208: Inconsistent authentication information. The card is not initialized or is dormant.

    • 209: Inconsistent authentication information. This card is a fraudulent card or has been retained.

    • 210: Inconsistent authentication information. This card has been reported as lost.

    • 211: Inconsistent authentication information. The number of incorrect password attempts has exceeded the limit.

    • 212: Inconsistent authentication information. The issuing bank does not support this transaction.

    • 213: Inconsistent authentication information. The card status is abnormal or the card is invalid.

    • 214: Inconsistent authentication information. No mobile number is reserved.

    • 215: Inconsistent authentication information. The entered password, expiration date, or CVN2 is incorrect.

    • 216: Inconsistent authentication information. Other card exceptions.

    • 301: Verification failed. The bank card does not support this service.

    • 302: Verification failed. The verification failed or was rejected by the bank. Contact the issuing bank.

    • 303: Verification failed. The bank card does not currently support mobile number verification.

    • 304: Verification failed. The bank card number is incorrect.

    • 305: Verification failed. Other reasons.

    • 306: Verification failed. The number of verification attempts has exceeded the limit.

    101