Checks whether the account-opening ID number entered by the Client matches the account-opening records under the specified Broker channel. It is the identity verification step in flows such as setting or resetting the trade password. Common flows:
- Reset trade password (
scene = 3): after verification, call POST /v1/auth/send_code with type = reset_trade_password to send a code to the Client’s phone, call POST /v1/member/check_mobile to check it and obtain verify_credentials, and then call POST /v2/member/trade/reset_password to set the new password. If the Client has no bound phone number, use POST /v1/auth/email/send_code and POST /v1/member/check_email instead.
- Set trade password (
scene = 4): after verification, check a code in the same way with type = set_trade_password, and then call POST /v2/member/trade/set_password to set the trade password.
Pass the Broker channel where the Client opened the account in account_channel. If verification fails, show message and let the Client re-enter the number; if the Client repeatedly fails, direct them to customer service.
Never send card_id in plaintext. Encryption: compute the MD5 of the x-timestamp header value (a millisecond timestamp string) as a 32-character lowercase hexadecimal string. Use the UTF-8 bytes of that string as the AES key and its first 16 bytes as the IV, encrypt the plaintext with AES-CBC (PKCS#7 padding), and Base64-encode the ciphertext as k. Then Base64-encode the JSON string {"rd":"<x-timestamp>","k":"<k>"} and send it as the field value. rd must match the x-timestamp header, which the server uses for decryption.