Skip to main content
This article will introduce a Bank Card Four Elements Verification API integration guide, which can be used to input bank card number, name, account document number, and account phone number to verify the authenticity and consistency of the information.

​
Application Process

To use the Bank Card Four Elements Verification API, first go to the Ace Data Cloud Console to obtain your API Token for future use. If you are not logged in or registered, you will be automatically redirected to the login page inviting you to register and log in, and after completion, you will be automatically returned to the current page. One API Token can call all services on the platform, no need to apply separately for each service. The first application will grant a free quota for a trial experience; when the quota is insufficient, you can recharge the general balance in the console.
📘 Complete documentation: Bank Card Four Elements Verification API →

​
Basic Usage

First, understand the basic usage method, which is to input the bank card number information to obtain the processed result image. You need to simply pass a bank_card field. We can then fill in the corresponding content on the interface, as shown in the figure:

Here we can see that we have set the Request Headers, including:
  • accept: the format of the response result you want to receive, here filled in as application/json, which is JSON format.
  • authorization: the key to call the API, which can be directly selected after application.
Additionally, the Request Body is set, including:
  • bank_card: the bank card number information to be processed, which is a required parameter.
  • id_card: the account document number, which is a required parameter.
  • name: the user’s name, which is a required parameter.
  • phone: the reserved phone number.
  • cert_type: the type of account document, which must be consistent with the account document.
  • encryption: optional, sensitive field encryption parameter (if encrypted text needs to be sent).
After selection, you can find that the corresponding code is also generated on the right side, as shown in the figure:

Click the “Try” button to conduct a test, as shown in the above figure, we obtained the following result:
The returned result has multiple fields, described as follows:
  • result, the authentication result code, with the charging situation as follows.
    • Charging result codes:
      • 0: Authentication passed
      • -1: Authentication not passed
      • -4: Cardholder information is incorrect
      • -5: No card payment activated
      • -6: This card has been confiscated
      • -7: Invalid card number
      • -8: This card has no corresponding issuing bank
      • -9: This card is uninitialized or a dormant card
      • -10: Fraudulent card, card swallowed
      • -11: This card has been reported lost
      • -12: This card has expired
      • -13: Restricted card
      • -14: Exceeded the number of incorrect password attempts
      • -15: The issuing bank does not support this transaction
    • Non-charging result codes:
      • -2: Name verification not passed
      • -3: Bank card number is incorrect
      • -16: Verification center service busy
      • -17: Exceeded the number of verifications, please try again the next day
  • description, business result description.
It can be seen that the bank card number, name, account document number, and account phone number of this bank card have authenticity and consistency. Additionally, if you want to generate the corresponding integration code, you can directly copy it, for example, the CURL code is as follows:
The Python integration code is as follows:

​
Error Handling

When calling the API, if an error occurs, the API will return the corresponding error code and message. For example:
  • 400 token_mismatched: Bad request, possibly due to missing or invalid parameters.
  • 400 api_not_implemented: Bad request, possibly due to missing or invalid parameters.
  • 401 invalid_token: Unauthorized, invalid or missing authorization token.
  • 429 too_many_requests: Too many requests, you have exceeded the rate limit.
  • 500 api_error: Internal server error, something went wrong on the server.

​
Error Response Example

​
Conclusion

Through this document, you have learned how to use the Bank Card Four Elements Verification API for inputting bank card number, name, account document number, and account phone number to verify the authenticity and consistency of the information. We hope this document can help you better integrate and use this API. If you have any questions, please feel free to contact our technical support team.