Financial attribute card number binding method and device

Abstract

The invention discloses a financial attribute card number binding method and device, relates to the technical field of bank card processing, can also be used in the financial field, and the method comprises the steps: generating a first encryption identifier based on the basic information of a user, and transmitting the first encryption identifier to a UnionPay database; a retrieval result fed back by the UnionPay database is received, under the condition that the retrieval result indicates that at least one financial attribute card number is retrieved, a financial attribute card number list of the user is obtained based on the retrieval result, and the financial attribute card number list comprises at least one financial attribute card number; displaying the financial attribute card number list on a user interface; and receiving a financial attribute card number selection result, and sending the financial attribute card number selection result to the UnionPay database. According to the invention, the convenience of binding the bank card on the non-bank APP by the client can be improved.

Description

Technical Field

[0001] The present invention relates to the technical field of bank card processing, and can also be used in the financial field, and in particular to a method and device for binding a financial attribute card number. Background Art

[0002] Mobile payment has become the mainstream payment method. Customers need to bind their bank cards before using various payment methods. There are currently two mainstream ways to bind cards: manually inputting the card number, calling up the commercial bank or UnionPay APP or H5 card selection and binding. Both methods have the disadvantages of incomplete bank card information and inconvenience. The technical problem of inconvenience in users binding bank cards on non-bank APPs needs to be solved urgently. Summary of the invention

[0003] In view of the problems in the prior art, an embodiment of the present invention provides a method and device for binding a financial attribute card number, so as to solve the technical problem in the prior art that it is not convenient for users to bind bank cards on non-bank APPs.

[0004] The embodiment of the present invention provides a method for binding a financial attribute card number, which is applied to a terminal and includes:

[0005] Generate a first encrypted identifier based on the basic information of the user, and send the first encrypted identifier to the UnionPay database, wherein the UnionPay database searches for the financial attribute card number corresponding to the user based on the first encrypted identifier and returns the search result, and the UnionPay database stores all financial attribute card numbers corresponding to the basic information, and the financial attribute card number is the card number corresponding to the card created by the user when handling business at a financial institution;

[0006] receiving a search result fed back by the UnionPay database, and if the search result indicates that at least one financial attribute card number has been retrieved, obtaining a list of financial attribute card numbers of the user based on the search result, wherein the list of financial attribute card numbers includes at least one financial attribute card number;

[0007] Display the list of financial attribute card numbers in the user interface;

[0008] A financial attribute card number selection result is received and sent to a UnionPay database, wherein the financial attribute card number selection result carries a target financial attribute card number, and the UnionPay database authorizes and binds the target financial attribute card number.

[0009] Optionally, in one embodiment of the present invention, after receiving the search results fed back from the UnionPay database, it also includes: when the search results indicate that at least one financial attribute card number does not exist in the UnionPay database, prompting the user to manually bind the card; obtaining a predetermined financial attribute card number input by the user, and sending the predetermined financial attribute card number and basic information to the UnionPay database.

[0010] Optionally, in one embodiment of the present invention, it also includes: before generating a first encryption identifier based on the user's basic information, the user creates a financial attribute card number including: obtaining the basic information entered by the user for the first time, generating a second encryption identifier based on the basic information, the second encryption identifier being the first encryption identifier and the key plaintext generated by the basic information; encrypting and encoding the public key corresponding to the key plaintext using the encryption certificate provided by the UnionPay database, obtaining the key ciphertext, and sending the key ciphertext to the UnionPay database.

[0011] The embodiment of the present invention provides a method for binding a financial attribute card, which is applied to a UnionPay database and includes:

[0012] Receiving the first encrypted identifier transmitted by the terminal, and performing a search based on the first encrypted identifier to obtain a search result;

[0013] If the search result indicates that there is a first identifier corresponding to the first encrypted identifier, obtaining at least one financial attribute card number of the user based on the first identifier;

[0014] Packing at least one financial attribute card number to obtain a financial attribute card number list;

[0015] Sending the list of financial attribute card numbers to the terminal, wherein the terminal displays the list of financial attribute card numbers on a user interface of the terminal;

[0016] receiving a financial attribute card number selection result fed back by the terminal, wherein the financial attribute card number selection result carries a target financial attribute card number;

[0017] Authorize and bind the target financial attribute card number based on the financial attribute card number selection result.

[0018] Optionally, in an embodiment of the present invention, the method further includes: if the first identifier corresponding to the first encrypted identifier is not retrieved, returning a query result indicating that at least one financial attribute card number does not exist in the UnionPay database to the terminal.

[0019] Optionally, in one embodiment of the present invention, it also includes: the UnionPay database includes a first database and a second database, the first database stores financial attribute card numbers with the authority to bind financial attribute cards, and the second database stores financial attribute card numbers without the authority to bind financial attribute cards.

[0020] Optionally, in one embodiment of the present invention, it also includes: when a signal is received indicating that a customer will authorize a financial attribute card number that does not have the authority to bind a financial attribute card, a search is performed based on the first encrypted identifier to obtain the first financial attribute card number corresponding to the first encrypted identifier and determine the current database information of the first financial attribute card number; when the current database information is the second database, the first financial attribute card number is stored in the first database and the authority information of the first financial attribute card number is fed back to the terminal, the authority information indicating that the first financial attribute card number has the authority to bind a financial attribute card.

[0021] Optionally, in an embodiment of the present invention, it also includes: obtaining the user's predetermined financial attribute card number and basic information sent by the terminal; verifying the predetermined financial attribute card number and the basic information, and authorizing the binding of the predetermined financial attribute card number if the verification passes.

[0022] Optionally, in one embodiment of the present invention, it also includes: before generating the first encrypted identifier based on the user's basic information, the user creates a financial attribute card number including: obtaining a key ciphertext sent by the terminal; decoding the key ciphertext and decrypting it using the encryption certificate to obtain a key plaintext, and obtaining the user's first encrypted identifier and basic information through the key plaintext; generating at least one financial attribute card number corresponding to the first encrypted identifier and the basic information, and sending the at least one financial attribute card number to the user's terminal via the communication means corresponding to the user contained in the basic information to inform the user.

[0023] The embodiment of the present invention provides a device for binding a financial attribute card number, which is applied to a terminal and includes:

[0024] A generation module, used to generate a first encrypted identifier based on the basic information of the user, and send the first encrypted identifier to the UnionPay database, wherein the UnionPay database searches for the financial attribute card number corresponding to the user based on the first encrypted identifier and returns the search result. The UnionPay database stores all financial attribute card numbers corresponding to the basic information, and the financial attribute card number is the card number corresponding to the card created by the user when handling business at a financial institution;

[0025] a receiving module, configured to receive a search result fed back by the UnionPay database, and if the search result indicates that at least one financial attribute card number has been retrieved, obtain a list of financial attribute card numbers of the user based on the search result, wherein the list of financial attribute card numbers includes at least one financial attribute card number;

[0026] A display module is used to display a list of financial attribute card numbers on the user interface;

[0027] The sending module is used to receive the financial attribute card number selection result and send the financial attribute card number selection result to the UnionPay database, wherein the financial attribute card number selection result carries the target financial attribute card number, and the UnionPay database authorizes and binds the target financial attribute card number.

[0028] Optionally, in one embodiment of the present invention, it also includes: a manual card binding unit, which is used to prompt the user to manually bind the card after receiving the search results fed back by the UnionPay database, when the search results indicate that at least one financial attribute card number does not exist in the UnionPay database; an acquisition unit, which is used to obtain a predetermined financial attribute card number input by the user, and send the predetermined financial attribute card number and basic information to the UnionPay database.

[0029] Optionally, in one embodiment of the present invention, it also includes: a creation unit, which is used for the user to create a financial attribute card number before generating a first encryption identifier based on the user's basic information; the creation unit includes: an acquisition subunit, which is used to obtain the basic information entered by the user for the first time, and generate a second encryption identifier based on the basic information, the second encryption identifier is the key plaintext generated by the first encryption identifier and the basic information; an encryption subunit, which is used to use the encryption certificate provided by the UnionPay database to encrypt and encode the public key corresponding to the key plaintext, obtain the key ciphertext, and send the key ciphertext to the UnionPay database.

[0030] The embodiment of the present invention provides a binding device for a financial attribute card, which is applied to a UnionPay database, and includes:

[0031] A first receiving module, used for receiving a first encryption identifier transmitted by a terminal, and performing a search based on the first encryption identifier to obtain a search result;

[0032] an acquisition module, configured to acquire at least one financial attribute card number of the user based on the first identifier if the search result indicates that there is a first identifier corresponding to the first encrypted identifier;

[0033] A packaging module, used to package at least one financial attribute card number to obtain a financial attribute card number list;

[0034] A sending module, used to send the list of financial attribute card numbers to the terminal, wherein the terminal displays the list of financial attribute card numbers on a user interface of the terminal;

[0035] A second receiving module is used to receive a financial attribute card number selection result fed back by the terminal, wherein the financial attribute card number selection result carries a target financial attribute card number;

[0036] The authorization binding module is used to authorize and bind the target financial attribute card number based on the financial attribute card number selection result.

[0037] Optionally, in one embodiment of the present invention, it also includes: the UnionPay database includes a first database and a second database, the first database stores financial attribute card numbers with the authority to bind financial attribute cards, and the second database stores financial attribute card numbers without the authority to bind financial attribute cards.

[0038] Optionally, in one embodiment of the present invention, it also includes: a retrieval unit, which is used to retrieve based on the first encrypted identifier when receiving a signal indicating that a customer will authorize a financial attribute card number that does not have the authority to bind a financial attribute card, obtain the first financial attribute card number corresponding to the first encrypted identifier and determine the current database information of the first financial attribute card number; a feedback unit, which is used to store the first financial attribute card number in the first database and feedback the authority information of the first financial attribute card number to the terminal when the current database information is the second database, the authority information indicating that the first financial attribute card number has the authority to bind a financial attribute card.

[0039] Optionally, in one embodiment of the present invention, it further includes: a returning unit, which is used to return a query result indicating that at least one financial attribute card number does not exist in the UnionPay database to the terminal if the first identifier corresponding to the first encrypted identifier is not retrieved.

[0040] Optionally, in one embodiment of the present invention, it also includes: an acquisition unit, used to acquire the user's predetermined financial attribute card number and basic information sent by the terminal; a verification unit, used to verify the predetermined financial attribute card number and basic information, and authorize binding the predetermined financial attribute card number if the verification passes.

[0041] Optionally, in one embodiment of the present invention, it also includes: a creation unit, which is used for the user to create a financial attribute card number before generating a first encrypted identifier based on the user's basic information; the creation unit includes: an acquisition subunit, which is used to obtain a key ciphertext sent by the terminal; a decryption subunit, which is used to decode the key ciphertext and then use the encryption certificate to decrypt it to obtain a key plaintext, and obtain the user's first encrypted identifier and basic information through the key plaintext; a generation subunit, which is used to generate at least one financial attribute card number corresponding to the first encrypted identifier and the basic information, and send the at least one financial attribute card number to the user's terminal through the communication means corresponding to the user contained in the basic information to inform the user.

[0042] An embodiment of the present invention further provides a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the above-mentioned method for binding a financial attribute card when executing the computer program.

[0043] An embodiment of the present invention further provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, the above-mentioned method for binding a financial attribute card is implemented.

[0044] An embodiment of the present invention further provides a computer program product, which includes a computer program. When the computer program is executed by a processor, the above-mentioned method for binding a financial attribute card is implemented.

[0045] In the embodiment of the present invention, compared with the technical solution in the prior art, a first encrypted identifier is generated based on the basic information of the user, and the first encrypted identifier is sent to the UnionPay database, wherein the UnionPay database searches for the financial attribute card number corresponding to the user based on the first encrypted identifier, and returns the search result, and the UnionPay database stores all the financial attribute card numbers corresponding to the basic information, and the financial attribute card number is the card number corresponding to the card created by the user when handling business in a financial institution; the search result fed back by the UnionPay database is received, and when the search result indicates that at least one financial attribute card number has been retrieved, the user's financial attribute card number list is obtained based on the search result, wherein the financial attribute card number list includes at least one financial attribute card number; the financial attribute card number list is displayed on the user interface; the financial attribute card number selection result is received, and the financial attribute card number selection result is sent to the UnionPay database, wherein the financial attribute card number selection result carries the target financial attribute card number, and the UnionPay database authorizes the binding of the target financial attribute card number. The convenience of users binding bank cards on non-commercial bank APPs can be improved, thereby solving the technical problem that users are not convenient enough to bind bank cards on non-bank APPs in the prior art. BRIEF DESCRIPTION OF THE DRAWINGS

[0046] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the prior art descriptions. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work. In the drawings:

[0047] Figure 1 This is a flow chart of a method for binding a financial attribute card in an embodiment of the present invention;

[0048] Figure 2 This is a flow chart of another method for binding a financial attribute card in an embodiment of the present invention;

[0049] Figure 3 This is a flow chart of supplementary authorization during the card binding process in an embodiment of the present invention;

[0050] Figure 4This is a flow chart of encryption and decryption of bank card information transmission in an embodiment of the present invention;

[0051] Figure 5 This is a flowchart of non-commercial bank APP card binding in an embodiment of the present invention;

[0052] Figure 6 This is a flow chart of commercial bank APP card binding in an embodiment of the present invention;

[0053] Figure 7 Schematic diagram of a binding device for a financial attribute card in an embodiment of the present invention;

[0054] Figure 8 It is a schematic diagram of another binding device for a financial attribute card according to an embodiment of the present invention;

[0055] Fig. 9 A schematic diagram of the physical structure of an electronic device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0056] To make the purpose, technical solution and advantages of the embodiments of the present invention more clear, the embodiments of the present invention are further described in detail below in conjunction with the accompanying drawings. Here, the exemplary embodiments of the present invention and their descriptions are used to explain the present invention, but are not intended to limit the present invention.

[0057] Figure 1 FIG. 1 is a flow chart of a method for binding a financial attribute card in an embodiment of the present invention. Figure 1 As shown, an embodiment of the present invention provides a method for binding a financial attribute card number, which is applied to a terminal and includes:

[0058] Step S101, generating a first encrypted identifier based on the basic information of the user, and sending the first encrypted identifier to the UnionPay database, wherein the UnionPay database searches for the financial attribute card number corresponding to the user based on the first encrypted identifier, and returns the search result, and the UnionPay database stores all financial attribute card numbers corresponding to the basic information, and the financial attribute card number is the card number corresponding to the card created by the user when handling business at a financial institution;

[0059] In the above steps, the terminal side transforms the basic information of the user through an algorithm to generate USERID (i.e., the first encrypted identifier). The basic information includes: the user's ID card, mobile phone number and other personal information, and sends USERID to the UnionPay database to retrieve all bank card numbers under the user's name. It should be noted that the UnionPay database stores all the activated bank card numbers (i.e., financial attribute card numbers) corresponding to the user's basic information. The UnionPay database in the present invention integrates the databases of all banks, so that users can retrieve all bank cards activated in all banks at one time when searching the UnionPay database.

[0060] Step S102, receiving the search result fed back by the UnionPay database, and if the search result indicates that at least one financial attribute card number has been retrieved, obtaining a list of financial attribute card numbers of the user based on the search result, wherein the list of financial attribute card numbers includes at least one financial attribute card number;

[0061] In the above steps, after sending USERID to the UnionPay database, the UnionPay database searches for bank cards under the user name based on USERID and returns the search results to the terminal. When the result is that the bank card number under the user name is retrieved, a list of retrieved bank card numbers is obtained.

[0062] Step S103, displaying a list of financial attribute card numbers on the user interface;

[0063] In the above steps, the bank card lists (ie, financial attribute card number lists) are displayed to the user so that the user can select a binding object.

[0064] Step S104, receiving the financial attribute card number selection result, and sending the financial attribute card number selection result to the UnionPay database, wherein the financial attribute card number selection result carries the target financial attribute card number, and the UnionPay database authorizes and binds the target financial attribute card number.

[0065] In the above steps, after the user selects the bank card that he wants to bind in the bank card list, the selection result of the selected bank card is sent to the UnionPay database for binding and data upload.

[0066] In an embodiment of the present invention, a first encrypted identifier is generated based on the basic information of the user, and the first encrypted identifier is sent to the UnionPay database, wherein the UnionPay database searches for the financial attribute card number corresponding to the user based on the first encrypted identifier, and returns the search result, and the UnionPay database stores all financial attribute card numbers corresponding to the basic information, and the financial attribute card number is the card number corresponding to the card created by the user when handling business in a financial institution; the search result fed back by the UnionPay database is received, and when the search result indicates that at least one financial attribute card number has been retrieved, the user's financial attribute card number list is obtained based on the search result, wherein the financial attribute card number list includes at least one financial attribute card number; the financial attribute card number list is displayed on the user interface; the financial attribute card number selection result is received, and the financial attribute card number selection result is sent to the UnionPay database, wherein the financial attribute card number selection result carries the target financial attribute card number, and the UnionPay database authorizes the target financial attribute card number to bind. The method provided by the embodiment of the present invention can improve the convenience of users binding bank cards on non-commercial bank APPs, thereby solving the technical problem that users are not convenient enough to bind bank cards on non-bank APPs in the prior art.

[0067] As an embodiment of the present invention, after receiving the search results fed back by the UnionPay database, it also includes: when the search results indicate that at least one financial attribute card number does not exist in the UnionPay database, prompting the user to manually bind the card; obtaining the predetermined financial attribute card number input by the user, and sending the predetermined financial attribute card number and basic information to the UnionPay database.

[0068] In the above optional embodiment, when the bank card number under the user name cannot be retrieved in the UnionPay database through USERID, the user is prompted to manually bind the card, obtain the bank card number manually entered by the user, and send the bank card number and the user's basic information to the UnionPay database for manual card binding.

[0069] As an embodiment of the present invention, it also includes: before generating a first encryption identifier based on the user's basic information, the user creates a financial attribute card number including: obtaining the basic information input by the user for the first time, generating a second encryption identifier based on the basic information, the second encryption identifier being the first encryption identifier and the key plaintext generated by the basic information; encrypting and encoding the public key corresponding to the key plaintext using the encryption certificate provided by the UnionPay database, obtaining the key ciphertext, and sending the key ciphertext to the UnionPay database.

[0070] In the above optional embodiment, the bank card needs to be activated before the user binds. The user first provides basic information, generates a USERID based on the basic information, generates a second encryption identifier through the USERID and the basic information, and then uses the encryption certificate uniformly provided by the UnionPay database to encrypt and encode the public key corresponding to the second encryption identifier. After obtaining the key ciphertext, it is sent to the UnionPay database to complete data collection and encryption, thereby improving data security.

[0071] Figure 2 FIG. 1 is a flow chart of another method for binding a financial attribute card according to an embodiment of the present invention. Figure 2 As shown, an embodiment of the present invention provides a method for binding a financial attribute card, which is applied to a UnionPay database, and includes:

[0072] Step S201, receiving a first encryption identifier transmitted by a terminal, and performing a search based on the first encryption identifier to obtain a search result;

[0073] In the above steps, the USERID (ie, the first encrypted identifier) ​​sent by the terminal is first received, and the bank card number corresponding to the USERID is retrieved based on the USERID.

[0074] Step S202, if the search result indicates that there is a first identifier corresponding to the first encrypted identifier, obtaining at least one financial attribute card number of the user based on the first identifier;

[0075] In the above steps, identification information corresponding to the USERID is retrieved through the USERID, and all bank card numbers corresponding to the identification information are obtained through the identification information.

[0076] Step S203, packaging at least one financial attribute card number to obtain a financial attribute card number list;

[0077] In the above steps, the obtained bank card numbers are packaged and assembled into a list to facilitate intuitive selection by users.

[0078] Step S204, sending the list of financial attribute card numbers to the terminal, wherein the terminal displays the list of financial attribute card numbers on a user interface of the terminal;

[0079] In the above steps, a plurality of bank card numbers in a list form are sent to the terminal, and the terminal displays the bank card number list on a user interface of the terminal for the user to select a bound bank card number.

[0080] Step S205, receiving a financial attribute card number selection result fed back by the terminal, wherein the financial attribute card number selection result carries a target financial attribute card number;

[0081] In the above steps, after the user selects the bank card number to be bound, the bank card number selection result is returned by the receiving terminal.

[0082] Step S206: Authorize and bind the target financial attribute card number based on the financial attribute card number selection result.

[0083] In the above steps, the bank card number selected by the user is authorized to be bound according to the result of the user's selection to bind the bank card number.

[0084] In the embodiment of the present invention, the first encrypted identifier transmitted by the receiving terminal is retrieved based on the first encrypted identifier to obtain the retrieval result; when the retrieval result indicates that there is a first identifier corresponding to the first encrypted identifier, at least one financial attribute card number of the user is obtained based on the first identifier; at least one financial attribute card number is packaged to obtain a list of financial attribute card numbers; the list of financial attribute card numbers is sent to the terminal, wherein the terminal displays the list of financial attribute card numbers on the user interface of the terminal; the financial attribute card number selection result fed back by the receiving terminal is carried in the financial attribute card number selection result; and the target financial attribute card number is authorized to be bound based on the financial attribute card number selection result. The method provided by the embodiment of the present invention can improve the convenience of users binding bank cards on non-commercial bank APPs, thereby solving the technical problem that users are not convenient enough to bind bank cards on non-bank APPs in the prior art.

[0085] As an embodiment of the present invention, it also includes: the UnionPay database includes a first database and a second database, the first database stores financial attribute card numbers with the authority to bind financial attribute cards, and the second database stores financial attribute card numbers without the authority to bind financial attribute cards.

[0086] In the above optional embodiment, the UnionPay database adopts a hierarchical storage method to store all bank cards. Specifically, all bank cards of all users are classified and stored in a hierarchical manner, and bank cards that have been authorized to use the quick binding method provided by the embodiment of the present invention are stored in the first database, and bank cards that have not been authorized to use the quick binding method provided by the embodiment of the present invention are stored in the first database. After determining whether the user agrees to use the quick card binding (or "one-click card binding"), it is queried whether the bank card corresponding to the user has been authorized. If not authorized, supplementary authorization is performed.

[0087] As an embodiment of the present invention, it also includes: when a signal is received indicating that a customer will authorize a financial attribute card number that does not have the authority to bind a financial attribute card, a search is performed based on the first encrypted identifier to obtain the first financial attribute card number corresponding to the first encrypted identifier and determine the current database information of the first financial attribute card number; when the current database information is the second database, the first financial attribute card number is stored in the first database and the authority information of the first financial attribute card number is fed back to the terminal, the authority information indicating that the first financial attribute card number has the authority to bind a financial attribute card.

[0088] In the above optional embodiment, specifically, Figure 3 FIG. 1 is a flow chart of supplementary authorization in the card binding process according to an embodiment of the present invention. Figure 3 As shown, the specific steps are as follows:

[0089] Step S301, the user clicks on supplementary authorization;

[0090] Step S302: The commercial bank / non-commercial bank APP guides the customer to select a supplementary authorization institution and check the agreement;

[0091] Step S303: The commercial bank / non-commercial bank service end calls the supplementary authorization interface and sends supplementary authorization information, including APPID, USERID, institution number, etc.

[0092] Step S304, the data integration application UnionPay server changes the customer's bank card of the institution from unauthorized primary storage to authorized secondary storage according to the supplementary authorization institution;

[0093] Step S305, the UnionPay service end notifies the supplementary authorization institution to update the supplementary authorization status;

[0094] Step S306: The supplementary authorization agency updates the unauthorized status.

[0095] As an embodiment of the present invention, the method further includes: if the first identifier corresponding to the first encrypted identifier is not retrieved, returning a query result indicating that at least one financial attribute card number does not exist in the UnionPay database to the terminal.

[0096] In the above optional embodiment, after the bank card number corresponding to USERID is not retrieved, the search result that there is no identification corresponding to USERID in the UnionPay database is returned to the terminal.

[0097] As an embodiment of the present invention, it also includes: acquiring the user's predetermined financial attribute card number and basic information sent by the terminal; verifying the predetermined financial attribute card number and the basic information, and authorizing the binding of the predetermined financial attribute card number if the verification passes.

[0098] In the above optional embodiment, after the terminal retrieves the corresponding bank card using USERID, it receives the bank card number selected by the user and the corresponding basic information, and performs security and integrity verification on the bank card number and basic information. If passed, the bank card is bound; if not passed, the reason for failure is returned to the terminal, prompting additional information or verification of the card number.

[0099] As an embodiment of the present invention, it also includes: before generating a first encrypted identifier based on the user's basic information, the user creates a financial attribute card number including: obtaining a key ciphertext sent by a terminal; decoding the key ciphertext and then decrypting it using an encryption certificate to obtain a key plaintext, and obtaining the user's first encrypted identifier and basic information through the key plaintext; generating at least one financial attribute card number corresponding to the first encrypted identifier and the basic information, and sending the at least one financial attribute card number to the user's terminal through a communication method corresponding to the user contained in the basic information to inform the user.

[0100] Figure 4 FIG. 1 is a flow chart of encryption and decryption of bank card information transmission in an embodiment of the present invention. Figure 4 As shown, the commercial bank randomly generates the key plaintext, and according to the encryption algorithm, uses the public key corresponding to the encryption certificate ID provided by UnionPay to perform RSA encryption, and generates the key ciphertext after base64 encoding. After receiving the request, the UnionPay data integration application decrypts the information, specifically by performing base64 decoding on the key ciphertext, decrypting the key ciphertext using the encryption certificate private key, obtaining the symmetric key plaintext, and then decrypting it according to the encryption algorithm to form the sensitive data plaintext and store it.

[0101] It should be noted that the embodiments of the present invention involve three parties: 1. Data integration application (UnionPay server): on the one hand, it provides bank card information security and hierarchical storage space, and on the other hand, it provides bank card information transmission interface, bank card information query interface, and supplementary authorization interface. 2. Each APP front end: The APP front end page that needs to bind the card can guide the customer to bind the bank card. 3. Each APP server: including commercial bank server and non-commercial bank server. The commercial bank server calls the data integration application to upload the customer's bank card information on the one hand, and calls the data integration application to obtain the customer's full bank card information on the other hand; the non-commercial bank server mainly calls the data integration application to obtain the customer's full bank card information. For the convenience of explanation, each APP front end and each APP server can be regarded as one end for explanation.

[0102] Among them, bank card information transmission interface: the commercial bank service end calls the bank card information transmission interface through a scheduled task, encrypts and uploads the incremental customer bank card information, and the uploaded fields include APPID, USERID, customer reserved name, customer reserved certificate type, customer reserved certificate number, customer reserved mobile phone number, customer account opening bank, customer bank card number, and authorization status (agstatus). Among them, USERID is the customer reserved name + reserved certificate type + the last six digits of the reserved certificate. The deformation processing rules of all commercial banks are consistent, thereby forming the primary key. Among them, the authorization status refers to whether the customer agrees to use the bank card for the one-click card binding function. If agreed, the authorization status (agstatus) is 1, and if not agreed, (agstatus) is 0. After receiving the incremental bank card information, the data integration application (UnionPay service end) stores it hierarchically according to the authorization status.

[0103] Among them, bank card information query interface: after the customer initiates a card binding request in each APP, each APP guides the customer to verify the identity information. The verification method can be face scanning, fingerprint, SMS verification code, etc. After the verification is passed, each APP server calls the bank card information query interface.

[0104] The commercial bank server sends USERID, and the UnionPay data integration application parses the request message after receiving it, matches and encrypts the authorized card list information returned to the account opening bank and secondary storage based on USERID. The commercial bank APP receives the card list information and decrypts it for display to the customer, supporting customers to bind the card with one click; if the USERID is not matched, the customer is guided to fill in the card manually.

[0105] After the customer authorizes, the non-commercial bank server sends the USERID (if the non-commercial bank client has customer information, it will send the USERID directly; if it does not have the USERID, it will guide the customer to enter the information and send it up). The UnionPay data integration application receives the request message and parses it, matches and encrypts the returned card list information of the account opening bank and secondary storage according to the USERID. The commercial bank APP receives the card list information and decrypts it for display to the customer, supporting customers to bind the card with one click; if the USERID is not matched, it will guide the customer to fill in the card manually. If the customer does not authorize, it will guide the customer to fill in the card manually according to the existing information.

[0106] Among them, after the customer selects the bank card and verifies the information, the data integration application will synchronize the card binding information results to the relevant banks. The relevant banks will perform the actual card binding operation. If the card binding fails, it will synchronously return to prompt the customer that the transaction is abnormal.

[0107] Among them, if the customer has not authorized a certain bank, but hopes to bind the bank's bank card when binding the card, he can click on supplementary authorization. The commercial bank / non-commercial bank will call the supplementary authorization interface, send APPID\USERID\supplementary unauthorized institution number, etc., and reversely notify UnionPay to change the first-level unauthorized bank card information to the second-level authorized bank card information and return it, supporting customer binding. At the same time, UnionPay will simultaneously notify the bank to update the authorization status.

[0108] Among them, in order to make information transmission more secure, USERID can be changed to a deformation of document type + document number. When calling the interface, only the deformed USERID can be transmitted without transmitting the specific document type and document number. If necessary, UnionPay can reverse the information according to the deformation rules.

[0109] Furthermore, the cases of commercial bank APP and non-commercial bank APP are described in detail below.

[0110] Figure 5 This is a flowchart of non-commercial bank APP card binding in an embodiment of the present invention;

[0111] Step S501, the customer initiates a card binding transaction in a non-commercial bank APP;

[0112] Step S502, the non-commercial bank APP guides the customer to verify identity information (i.e. basic information);

[0113] Step S503, the non-commercial bank APP server verifies the customer identity information;

[0114] Step S504: The non-commercial bank APP prompts the customer whether to authorize the one-click card binding function;

[0115] If you do not agree to the authorization: jump to steps S515-S517;

[0116] If you agree to the authorization:

[0117] Step S505, determining whether customer identity information is stored;

[0118] If the customer information is stored: jump to step S508;

[0119] If no customer information is stored:

[0120] Step S506: The non-commercial bank APP front end guides the customer to enter the name, ID type and the last six digits of the ID number;

[0121] Step S507, the customer enters his / her name, selects the type of ID, and enters the last six digits of the ID number;

[0122] Step S508: The non-commercial bank APP server combines the deformed name + the ID type + the last six digits of the ID number to generate a USERID, which is encrypted and sent to the server;

[0123] Step S509, the UnionPay server (data integration application) determines whether the USERID is matched;

[0124] If USERID is matched, then

[0125] Step S510, the UnionPay server (data integration application) returns a bank card list;

[0126] Step S511, the commercial bank service end obtains a bank card list;

[0127] Step S512: The commercial bank APP displays a list of bank cards and supports one-click card binding;

[0128] Step S513: The customer completes card binding.

[0129] If no match is found for USERID, then

[0130] Step S514, the UnionPay server (data integration application) returns information not found;

[0131] Step S515, the non-commercial bank APP server returns to the page for guiding manual card input;

[0132] Step S516: The non-commercial bank APP front end guides manual card binding;

[0133] Step S517, the customer binds the card;

[0134] Step S518, UnionPay notifies the user to bind the card;

[0135] Step S519: The commercial bank completes the card binding.

[0136] in addition, Figure 6 This is a flow chart of commercial bank APP card binding in an embodiment of the present invention;

[0137] Step S601, the customer initiates a card binding transaction in the commercial bank APP;

[0138] Step S602, the commercial bank APP guides the customer to verify identity information;

[0139] Step S603, the commercial bank service end verifies the customer identity information;

[0140] Step S604, the commercial bank service end calls the bank card information query interface of the UnionPay service end (data integration application) and sends the USERID to query the bank card information;

[0141] Step S605, the UnionPay server (data integration application) determines the matching USERID;

[0142] If USERID is matched,

[0143] Step S606, the UnionPay server (data integration application) returns a bank card list;

[0144] Step S607, the commercial bank service end obtains a bank card list;

[0145] Step S608: The commercial bank APP displays a list of bank cards and supports one-click card binding;

[0146] Step S609: The customer completes the card binding.

[0147] If no match is found for USERID,

[0148] Step S610, the UnionPay server (data integration application) returns information not found;

[0149] Step S611, the commercial bank service end returns to the page for guiding manual card input;

[0150] Step S612: The commercial bank APP guides manual card binding;

[0151] Step S613, the customer binds the card;

[0152] Step S614, UnionPay notifies the commercial bank to bind the card;

[0153] Step S615: The commercial bank completes the card binding.

[0154] In the method provided in the embodiment of the present invention, UnionPay establishes a hierarchical bank card information storage space, with the first level storing unauthorized bank card information and the second level storing authorized bank card information, and provides a standardized interface for bank card information transmission. All commercial banks, as alliance banks, apply to call the interface. UnionPay allocates an APPID to each commercial bank. The commercial bank calls the interface through the RSA asymmetric encryption algorithm every hour to send incremental customer bank card information. The sent fields include APPID, USERID, customer reserved information, bank card number, mobile phone number, and whether it is authorized. After receiving the message information, UnionPay stores the information in a hierarchical manner according to whether it has been authorized. Among them, the customer reserved information includes name, certificate type, and certificate number. USERID is the customer reserved name + certificate type + the last six digits of the certificate number assembled and transformed for encrypted transmission. All commercial banks send it according to this rule to form a query primary key, and the bank card number is encrypted for transmission.

[0155] UnionPay provides a standardized interface for bank card information query. UnionPay assigns an APPID to each caller. When a customer binds a card on a commercial bank APP, the commercial bank APP calls the query interface and sends APPID and USERID to initiate a call request. UnionPay accepts the request and returns a list of authorized bank cards in secondary storage, supporting customers to bind cards with one click. After the customer selects a card, UnionPay sends the binding information to each commercial bank according to the bank card, and each commercial bank performs the actual card binding operation. When a customer binds a card on other APPs, the user's identity information is first verified (it can be various verification methods such as face recognition, fingerprint, and SMS verification code). After the verification is passed, the customer is prompted whether to use the one-click card binding function. If the customer agrees and the APP already has the customer's name, ID type and ID number, the APP will send APPID and USERID to initiate a call request. UnionPay accepts the request and returns a list of bank cards, supporting customers to bind cards with one click. After the customer selects a card, UnionPay sends the binding information to each commercial bank according to the bank card, and each commercial bank performs the actual card binding operation. If the customer agrees but does not have the customer's name, ID type and ID number, the customer will be guided to enter the additional information and then submit it to the query card list. If the customer does not agree, the customer will be guided to fill in the card manually based on the existing inventory.

[0156] This solution supports customers to supplement authorization during the one-click card binding process. If the customer has not authorized a certain bank but hopes to bind the bank card of this bank when binding the card, he can click on supplement authorization to reversely notify UnionPay to change the first-level unauthorized bank card information to the second-level authorized bank card information and return it, supporting customer binding. At the same time, UnionPay synchronously notifies the bank to update the authorization status, thereby improving the user experience and convenience in the process of binding the bank card; and the present invention establishes a data integration application, and commercial banks form an alliance to form a full bank card information database in the form of encrypted transmission of incremental bank card numbers of different levels based on scheduled tasks, supports commercial banks and non-commercial banks APP to display the full bank card list to customers at one time by calling the interface to send the deformed USERID, supports customers to bind the card with one click, without manually filling in the card or calling up a certain bank APP / H5 to add the card in turn, which can greatly improve the efficiency of card binding and payment.

[0157] Figure 7 FIG. 1 is a schematic diagram of a binding device for a financial attribute card according to an embodiment of the present invention. Figure 7 As shown, an embodiment of the present invention provides a device for binding a financial attribute card number, which is applied to a terminal and includes:

[0158] A generating module 71 is used to generate a first encrypted identifier based on the basic information of the user, and send the first encrypted identifier to the UnionPay database, wherein the UnionPay database searches for the financial attribute card number corresponding to the user based on the first encrypted identifier and returns the search result. The UnionPay database stores all financial attribute card numbers corresponding to the basic information, and the financial attribute card number is the card number corresponding to the card created by the user when handling business at a financial institution;

[0159] The receiving module 72 is used to receive the search result fed back by the UnionPay database, and if the search result indicates that at least one financial attribute card number has been retrieved, obtain the user's financial attribute card number list based on the search result, wherein the financial attribute card number list includes at least one financial attribute card number;

[0160] A display module 73, used to display a list of financial attribute card numbers on a user interface;

[0161] The sending module 74 is used to receive the financial attribute card number selection result and send the financial attribute card number selection result to the UnionPay database, wherein the financial attribute card number selection result carries the target financial attribute card number, and the UnionPay database authorizes and binds the target financial attribute card number.

[0162] Optionally, in one embodiment of the present invention, it also includes: a manual card binding unit, which is used to prompt the user to manually bind the card after receiving the search results fed back by the UnionPay database, when the search results indicate that at least one financial attribute card number does not exist in the UnionPay database; an acquisition unit, which is used to obtain a predetermined financial attribute card number input by the user, and send the predetermined financial attribute card number and basic information to the UnionPay database.

[0163] Optionally, in one embodiment of the present invention, it also includes: a creation unit, which is used for the user to create a financial attribute card number before generating a first encryption identifier based on the user's basic information; the creation unit includes: an acquisition subunit, which is used to obtain the basic information entered by the user for the first time, and generate a second encryption identifier based on the basic information, the second encryption identifier is the key plaintext generated by the first encryption identifier and the basic information; an encryption subunit, which is used to use the encryption certificate provided by the UnionPay database to encrypt and encode the public key corresponding to the key plaintext, obtain the key ciphertext, and send the key ciphertext to the UnionPay database.

[0164] Figure 8 FIG. 1 is a schematic diagram of another financial attribute card binding device according to an embodiment of the present invention. Figure 8 As shown, an embodiment of the present invention provides a binding device for a financial attribute card, which is applied to a UnionPay database, and includes:

[0165] A first receiving module 81 is used to receive a first encryption identifier transmitted by a terminal, and perform a search based on the first encryption identifier to obtain a search result;

[0166] An acquisition module 82, configured to acquire at least one financial attribute card number of the user based on the first identifier if the search result indicates that there is a first identifier corresponding to the first encrypted identifier;

[0167] A packaging module 83, used to package at least one financial attribute card number to obtain a financial attribute card number list;

[0168] A sending module 84, configured to send the list of financial attribute card numbers to the terminal, wherein the terminal displays the list of financial attribute card numbers on a user interface of the terminal;

[0169] The second receiving module 85 is used to receive the financial attribute card number selection result fed back by the terminal, wherein the financial attribute card number selection result carries the target financial attribute card number;

[0170] The authorization binding module 86 is used to authorize and bind the target financial attribute card number based on the financial attribute card number selection result.

[0171] Optionally, in one embodiment of the present invention, it also includes: the UnionPay database includes a first database and a second database, the first database stores financial attribute card numbers with the authority to bind financial attribute cards, and the second database stores financial attribute card numbers without the authority to bind financial attribute cards.

[0172] Optionally, in one embodiment of the present invention, it also includes: a retrieval unit, which is used to retrieve based on the first encrypted identifier when receiving a signal indicating that a customer will authorize a financial attribute card number that does not have the authority to bind a financial attribute card, obtain the first financial attribute card number corresponding to the first encrypted identifier and determine the current database information of the first financial attribute card number; a feedback unit, which is used to store the first financial attribute card number in the first database and feedback the authority information of the first financial attribute card number to the terminal when the current database information is the second database, the authority information indicating that the first financial attribute card number has the authority to bind a financial attribute card.

[0173] Optionally, in one embodiment of the present invention, it further includes: a returning unit, which is used to return a query result indicating that at least one financial attribute card number does not exist in the UnionPay database to the terminal if the first identifier corresponding to the first encrypted identifier is not retrieved.

[0174] Optionally, in one embodiment of the present invention, it also includes: an acquisition unit, used to acquire the user's predetermined financial attribute card number and basic information sent by the terminal; a verification unit, used to verify the predetermined financial attribute card number and basic information, and authorize binding the predetermined financial attribute card number if the verification passes.

[0175] Optionally, in one embodiment of the present invention, it also includes: a creation unit, which is used for the user to create a financial attribute card number before generating a first encrypted identifier based on the user's basic information; the creation unit includes: an acquisition subunit, which is used to obtain a key ciphertext sent by the terminal; a decryption subunit, which is used to decode the key ciphertext and then use the encryption certificate to decrypt it to obtain a key plaintext, and obtain the user's first encrypted identifier and basic information through the key plaintext; a generation subunit, which is used to generate at least one financial attribute card number corresponding to the first encrypted identifier and the basic information, and send the at least one financial attribute card number to the user's terminal through the communication means corresponding to the user contained in the basic information to inform the user.

[0176] An embodiment of the present invention further provides a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the above-mentioned method for binding a financial attribute card when executing the computer program.

[0177] An embodiment of the present invention further provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the above-mentioned method for binding a financial attribute card is implemented.

[0178] An embodiment of the present invention further provides a computer program product, which includes a computer program. When the computer program is executed by a processor, the computer program implements the above-mentioned method for binding a financial attribute card.

[0179] Fig. 9 A schematic diagram of the physical structure of an electronic device provided in an embodiment of the present invention, such as Fig. 9 As shown, the electronic device includes: a processor (processor) 901, a memory (memory) 902 and a bus 903.

[0180] The processor 901 and the memory 902 communicate with each other via a bus 903 .

[0181] The processor 901 is used to call the program instructions in the memory 902 to execute the methods provided by the above-mentioned method embodiments.

[0182] Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, systems, or computer program products. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0183] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0184] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0185] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0186] The specific embodiments described above further illustrate the objectives, technical solutions and beneficial effects of the present invention in detail. It should be understood that the above description is only a specific embodiment of the present invention and is not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention should be included in the scope of protection of the present invention.

Claims

1. A method for binding a financial attribute card number, characterized in that: Applied to terminals, including: Generate a first encrypted identifier based on the basic information of the user, and send the first encrypted identifier to the UnionPay database, wherein the UnionPay database searches for the financial attribute card number corresponding to the user based on the first encrypted identifier and returns the search result, wherein the UnionPay database stores all financial attribute card numbers corresponding to the basic information, and the financial attribute card number is the card number corresponding to the card created by the user when handling business at a financial institution; receiving the search result fed back by the UnionPay database, and if the search result indicates that the at least one financial attribute card number has been retrieved, acquiring a financial attribute card number list of the user based on the search result, wherein the financial attribute card number list includes the at least one financial attribute card number; Displaying the financial attribute card number list on the user interface; A financial attribute card number selection result is received, and the financial attribute card number selection result is sent to the UnionPay database, wherein the financial attribute card number selection result carries a target financial attribute card number, and the UnionPay database authorizes and binds the target financial attribute card number.

2. The method according to claim 1, characterized in that After receiving the search result fed back by the UnionPay database, the method further includes: When the search result indicates that the at least one financial attribute card number does not exist in the UnionPay database, prompting the user to manually bind the card; The predetermined financial attribute card number input by the user is obtained, and the predetermined financial attribute card number and the basic information are sent to the UnionPay database.

3. The method according to claim 1, characterized in that Also includes: Before generating the first encrypted identifier based on the basic information of the user, the user creating a financial attribute card number includes: Obtaining basic information input by the user for the first time, and generating a second encryption identifier based on the basic information, where the second encryption identifier is a plaintext key generated from the first encryption identifier and the basic information; The public key corresponding to the key plaintext is encrypted and encoded using the encryption certificate provided by the UnionPay database to obtain the key ciphertext, and the key ciphertext is sent to the UnionPay database.

4. A method for binding a financial attribute card, characterized in that: Applied to UnionPay database, including: Receiving a first encrypted identifier transmitted by a terminal, and performing a search based on the first encrypted identifier to obtain a search result; If the search result indicates that there is a first identifier corresponding to the first encrypted identifier, obtaining at least one financial attribute card number of the user based on the first identifier; Packing the at least one financial attribute card number to obtain a financial attribute card number list; sending the list of financial attribute card numbers to the terminal, wherein the terminal displays the list of financial attribute card numbers on a user interface of the terminal; receiving the financial attribute card number selection result fed back by the terminal, wherein the financial attribute card number selection result carries a target financial attribute card number; Authorize and bind the target financial attribute card number based on the financial attribute card number selection result.

5. The method according to claim 4, characterized in that Also includes: The UnionPay database includes a first database and a second database, wherein the first database stores financial attribute card numbers with permission to bind financial attribute cards, and the second database stores financial attribute card numbers without permission to bind financial attribute cards.

6. The method according to claim 5, characterized in that Also includes: Upon receiving a signal indicating that a customer is authorizing a financial attribute card number that does not have the authority to bind a financial attribute card, searching based on the first encrypted identifier to obtain the first financial attribute card number corresponding to the first encrypted identifier and determining the current database information of the first financial attribute card number; When the current database information is the second database, the first financial attribute card number is stored in the first database and permission information of the first financial attribute card number is fed back to the terminal, wherein the permission information indicates that the first financial attribute card number has permission to bind a financial attribute card.

7. The method according to claim 4, characterized in that Also includes: If the first identifier corresponding to the first encrypted identifier is not retrieved, a query result indicating that the at least one financial attribute card number does not exist in the UnionPay database is returned to the terminal.

8. The method according to claim 4, characterized in that Also includes: Acquire the predetermined financial attribute card number and basic information of the user sent by the terminal; The predetermined financial attribute card number and basic information are verified, and if the verification passes, the predetermined financial attribute card number is authorized to be bound.

9. The method according to claim 4, characterized in that Also includes: Before generating the first encrypted identifier based on the basic information of the user, the user creating a financial attribute card number includes: Obtaining the key ciphertext sent by the terminal; After decoding the key ciphertext, the encryption certificate is used to decrypt the key plaintext to obtain the key plaintext, and the first encryption identifier and basic information of the user are obtained through the key plaintext; At least one financial attribute card number corresponding to the first encrypted identifier and the basic information is generated, and the at least one financial attribute card number is sent to the user's terminal through the communication means corresponding to the user contained in the basic information to inform the user.

10. A device for binding a financial attribute card number, characterized in that: Applied to terminals, including: A generating module, configured to generate a first encrypted identifier based on the basic information of the user, and send the first encrypted identifier to a UnionPay database, wherein the UnionPay database searches for a financial attribute card number corresponding to the user based on the first encrypted identifier and returns a search result, wherein the UnionPay database stores all financial attribute card numbers corresponding to the basic information, and the financial attribute card number is a card number corresponding to a card created by the user when handling business at a financial institution; a receiving module, configured to receive the search result fed back by the UnionPay database, and if the search result indicates that the at least one financial attribute card number has been retrieved, obtain a list of financial attribute card numbers of the user based on the search result, wherein the list of financial attribute card numbers includes the at least one financial attribute card number; A display module, used to display the financial attribute card number list on a user interface; The sending module is used to receive a financial attribute card number selection result and send the financial attribute card number selection result to the UnionPay database, wherein the financial attribute card number selection result carries a target financial attribute card number, and the UnionPay database authorizes and binds the target financial attribute card number.

11. A binding device for a financial attribute card, characterized in that: Applied to UnionPay database, including: A first receiving module, used for receiving a first encryption identifier transmitted by a terminal, and performing a search based on the first encryption identifier to obtain a search result; an acquisition module, configured to acquire at least one financial attribute card number of a user based on the first identifier when the search result indicates that there is a first identifier corresponding to the first encrypted identifier; a packaging module, used to package the at least one financial attribute card number to obtain a financial attribute card number list; a sending module, configured to send the list of financial attribute card numbers to the terminal, wherein the terminal displays the list of financial attribute card numbers on a user interface of the terminal; A second receiving module is configured to receive the financial attribute card number selection result fed back by the terminal, wherein the financial attribute card number selection result carries a target financial attribute card number; The authorization binding module is used to authorize and bind the target financial attribute card number based on the financial attribute card number selection result.

12. A computer device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the method according to any one of claims 1 to 9 is implemented.

13. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 9 is implemented.

Images