Bank card binding method and device, equipment, storage medium and program product

Abstract

The embodiment of the invention provides a bank card binding method and device, equipment, a storage medium and a program product, and the method comprises the steps: responding to the binding operation of a bank card, sending a first request to a server of a bank, and enabling the first request to be used for obtaining the signing information of an authorized user and the bank; receiving signed bank card information and / or signed verification mode information sent by the server, wherein the verification mode information is used for indicating a mode in which the bank verifies the identity of the user; and displaying a first interface according to the information of the signed bank card and / or the signed verification mode information, and binding the bank card in response to interaction between the user and the first interface. And the binding efficiency of the bank card is improved.

Description

Technical Field

[0001] The embodiments of the present disclosure relate to the field of multimedia interaction technology, and in particular to a bank card binding method, apparatus, device, storage medium, and program product. Background Art

[0002] Users can purchase items in the application. Before paying, users need to bind the bank card they have signed with the application.

[0003] Currently, when users bind their bank cards within an app, the app retrieves a link to the bank's website and redirects them to that website, where they can complete the card binding process. However, this process takes a long time to navigate from the app interface to the bank's website, resulting in low card binding efficiency. Summary of the Invention

[0004] The embodiments of the present disclosure provide a bank card binding method, apparatus, device, storage medium, and program product, which are used to solve the technical problem of time-consuming bank card binding in the prior art.

[0005] In a first aspect, an embodiment of the present disclosure provides a bank card binding method, the bank card binding method comprising:

[0006] In response to a bank card binding operation, sending a first request to a server of a bank, wherein the first request is used to obtain contract information between the authorized user and the bank;

[0007] receiving information of a signed bank card and / or information of a signed verification method sent by the server, wherein the verification method information is used to indicate a method by which the bank authenticates the user;

[0008] A first interface is displayed based on the information of the contracted bank card and / or the contracted verification method information, and the bank card is bound in response to the user's interaction with the first interface.

[0009] In a second aspect, an embodiment of the present disclosure provides a bank card binding device, the bank card binding device comprising a sending module, a receiving module, a display module, and a processing module, wherein:

[0010] The sending module is configured to, in response to a bank card binding operation, send a first request to a server of a bank, wherein the first request is configured to obtain contract information between the authorized user and the bank;

[0011] The receiving module is used to receive the information of the contracted bank card and / or the contracted verification method information sent by the server, wherein the verification method information is used to indicate the method by which the bank authenticates the user;

[0012] The display module is configured to display a first interface based on the information of the contracted bank card and / or the contracted verification method information;

[0013] The processing module is used to bind the bank card in response to the interaction between the user and the first interface.

[0014] In a third aspect, the present disclosure provides a terminal device, comprising: a processor and a memory;

[0015] The memory stores computer-executable instructions;

[0016] The processor executes the computer-executable instructions stored in the memory, so that the at least one processor executes the first aspect and various bank card binding methods that may be involved in the first aspect.

[0017] In a fourth aspect, the present disclosure provides a computer-readable storage medium, in which computer-executable instructions are stored. When a processor executes the computer-executable instructions, the bank card binding method as described in the first aspect and various possible bank card binding methods involved in the first aspect are implemented.

[0018] In a fifth aspect, the present disclosure provides a computer program product, including a computer program, which, when executed by a processor, implements the first aspect and various bank card binding methods that may be involved in the first aspect.

[0019] The embodiments of the present disclosure provide a bank card binding method, apparatus, device, storage medium and program product. In response to a bank card binding operation, a terminal device may send a first request to a bank's server, wherein the first request is used to obtain contract information between an authorized user and the bank, receive information about the contracted bank card and / or information about the contracted verification method sent by the server, and the terminal device may display a first interface based on the information about the contracted bank card and / or information about the contracted verification method, and bind the bank card in response to the user's interaction with the first interface. In the above method, since the terminal device can obtain contract information from the bank's server and render a first interface associated with the information about the contracted bank card and / or information about the contracted mobile phone number based on the contract information, the user can bind the bank card in the interface currently displayed by the terminal device, and the terminal device does not need to jump to the bank page. Therefore, the efficiency of bank card binding can be improved. Moreover, since the user does not need to manually enter the bank card number and mobile phone number, the accuracy of bank card binding can be improved, thereby improving the user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] In order to more clearly illustrate the embodiments of the present disclosure or the technical solutions in the prior art, a brief introduction will be given below to the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are some embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0021] Figure 1 A schematic diagram of an application scenario provided by an embodiment of the present disclosure;

[0022] Figure 2 A schematic diagram of a flow chart of a bank card binding method provided in an embodiment of the present disclosure;

[0023] Figure 3 A schematic diagram of a sixth interface provided by an embodiment of the present disclosure;

[0024] Figure 4 A schematic diagram of a seventh interface provided in an embodiment of the present disclosure;

[0025] Figure 5 A schematic diagram of a process for sending a first request provided by an embodiment of the present disclosure;

[0026] Figure 6 A schematic diagram of another bank card binding method provided in an embodiment of the present disclosure;

[0027] Figure 7 A schematic diagram of a first interface provided by an embodiment of the present disclosure;

[0028] Figure 8 A schematic diagram of a second interface provided by an embodiment of the present disclosure;

[0029] Figure 9 A schematic diagram of a bank card binding process provided by an embodiment of the present disclosure;

[0030] Figure 10 A schematic diagram of another bank card binding method provided in an embodiment of the present disclosure;

[0031] Figure 11 A schematic diagram of another bank card binding process provided in an embodiment of the present disclosure;

[0032] Figure 12 A schematic diagram of another bank card binding method provided in an embodiment of the present disclosure;

[0033] Figure 13 A schematic diagram of another bank card binding process provided in an embodiment of the present disclosure;

[0034] Figure 14A schematic structural diagram of a bank card binding device provided in an embodiment of the present disclosure;

[0035] Figure 15 A schematic diagram of the structure of a terminal device provided in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0036] Exemplary embodiments will be described in detail herein, with examples illustrated in the accompanying drawings. In the following description, when referring to the drawings, identical numerals in different figures represent identical or similar elements, unless otherwise indicated. The embodiments described in the following exemplary embodiments are not intended to represent all possible embodiments consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present disclosure, as detailed in the appended claims.

[0037] It is understandable that before using the technical solutions disclosed in the various embodiments of this disclosure, the type, scope of use, usage scenarios, etc. of the personal information involved in this disclosure should be informed to the user and the user's authorization should be obtained in an appropriate manner in accordance with relevant laws and regulations.

[0038] For example, in response to a user's active request, a prompt message is sent to the user to clearly inform the user that the operation requested will require the acquisition and use of the user's personal information. This allows the user to independently choose whether to provide personal information to the electronic device, application, server, storage medium, or other software or hardware that performs the operations of the disclosed technical solution based on the prompt message.

[0039] As an optional but non-limiting implementation, in response to receiving a user's active request, the prompt information may be sent to the user in the form of a pop-up window, in which the prompt information may be presented in the form of text. In addition, the pop-up window may also contain a selection control for the user to select "agree" or "disagree" to provide personal information to the electronic device.

[0040] It is understandable that the above notification and user authorization process are merely illustrative and do not limit the implementation of the present disclosure. Other methods that comply with relevant laws and regulations may also be applied to the implementation of the present disclosure.

[0041] Next, combine Figure 1 , the application scenarios of the embodiments of the present disclosure are described.

[0042] Figure 1 This is a schematic diagram of an application scenario provided by the embodiment of the present disclosure. Figure 1, including: a terminal device. The interface displayed by the terminal device is a video playback interface, which includes the video being played and a window. The window may include information about the product involved in the video. The window may include product images, product information, information about the authorized recipient, Bank 1, Bank 2, product prices, and payment controls. The selection control for Bank 1 is highlighted, that is, the user chooses to bind the bank card of Bank 1 to complete this payment. When the user clicks the payment control, the terminal device may jump to the page of Bank 1, and the user may complete the binding of the bank card of Bank 1 on the page of Bank 1.

[0043] It should be noted that Figure 1 The examples are for application scenarios of the embodiments of the present disclosure, but are not intended to limit the application scenarios of the embodiments of the present disclosure.

[0044] In the related art, users can purchase goods in an application. For example, the application can be a shopping application, or a short video application, which can provide the function of purchasing goods. Before the user pays for the selected goods, the user needs to bind the bank card signed by the user in the application. After the bank card is bound, the user can make payments based on the bound bank card in the application. Currently, when a user binds a bank card in an application, the application can obtain a link to the bank's webpage and jump to the bank's webpage, and the user can complete the bank card binding on the bank's webpage. However, the bank's webpage is usually an HTML5 page, and it takes a long time to jump from the application's interface to the bank page (usually 3 seconds to 4 seconds), and the user needs to manually add the bank card number and mobile phone number. In this way, the operation complexity of bank card binding is high, which leads to low efficiency of bank card binding.

[0045] In order to solve the technical problems in the related art, the embodiment of the present disclosure provides a bank card binding method. In response to the bank card binding operation, the terminal device can send a first request to the bank's server, and the terminal device can receive the information of the contracted bank card and / or the contracted verification method information sent by the server. Wherein, when the contract information includes the contracted verification method information, the terminal device can determine the method of authenticating the user indicated by the verification method information, and display a first interface according to the authentication method, and bind the bank card in response to the user's interaction with the first interface. When the contract information includes the information of the contracted bank card, the terminal device can determine the type, card number and status of the contracted bank card according to the information of the contracted bank card, and display a first interface including the type, card number, status of the bank card, and the selection controls corresponding to each contracted bank card, and bind the bank card in response to the user's interaction with the first interface. In the above method, the terminal device can bind the bank card in the application without jumping to the bank page, and the user does not need to manually enter the bank card number. Therefore, the accuracy of bank card binding can be improved, the complexity of bank card binding can be reduced, and the efficiency of bank card binding can be improved.

[0046] The following detailed description of the technical solution of the present disclosure and how the technical solution of the present disclosure solves the above-mentioned technical problems is provided with specific embodiments. The following specific embodiments may be combined with each other, and the same or similar concepts or processes may not be described in detail in some embodiments. The following embodiments of the present disclosure are described in conjunction with the accompanying drawings.

[0047] Figure 2 This is a flow chart of a bank card binding method provided by an embodiment of the present disclosure. Figure 2 , the method may include:

[0048] S201: In response to a bank card binding operation, a first request is sent to a server of a bank.

[0049] The execution subject of the embodiments of the present disclosure may be a terminal device, or a bank card binding device provided in the terminal device. The bank card binding device may be implemented based on software, or based on a combination of software and hardware, which is not limited in the embodiments of the present disclosure.

[0050] The binding operation may be an operation of binding a bank card in a bank. Figure 1In the embodiment shown, the application can support payments with bank cards of Bank 1 and Bank 2. Therefore, the binding operation can be an operation of binding the bank card of Bank 1 in the application, the binding operation can also be an operation of binding the bank card of Bank 2 in the application, and the binding operation can also be an operation of binding the bank cards of Bank 1 and Bank 2 in the application. The embodiments of the present disclosure are not limited to this.

[0051] In some embodiments, the bank may be the bank corresponding to the binding operation. Figure 1 In the illustrated embodiment, during the binding operation, the user selects Bank 1, and the terminal device may determine to send a first request to the server of Bank 1.

[0052] The first request may be used to obtain the contract information between the authorized user and the bank. For example, after receiving the first request from the terminal device, the bank's server may send the contract information to the terminal device. The server may also determine whether the bank supports the application (i.e., whether the application can use the bank's bank card for payment). If the bank supports the application, the server may send the contract information to the terminal device.

[0053] Optionally, the server may also determine whether the user has signed a contract with the bank. After the user has signed a contract with the bank, the server may send contract information to the terminal device.

[0054] Optionally, the terminal device may predetermine the banks that support the application. That is, when the user binds a bank card, the banks displayed in the application that can be bound are all banks that support the application. For example, if Bank 1 and Bank 2 support payment in the application, but Bank 3 does not, when the user selects a bank card to bind, the interface may display selection controls for Bank 1 and Bank 2, and the interface will not display information related to Bank 3. In this way, the user can choose to bind a bank card from either Bank 1 or Bank 2.

[0055] Optionally, the terminal device can pre-determine whether the user has signed a contract with a bank that supports the application. That is, when the user performs a bank card binding operation, if the user has signed a contract with the bank, the terminal device can perform the binding operation. If the user has not signed a contract with the bank, the terminal device will not perform the binding operation, or determine that the binding operation has failed.

[0056] In some embodiments, the terminal device can send a first request to the bank's server based on the following feasible implementation: displaying a sixth interface, which includes information about at least one type of bank and selection controls for each type of bank; in response to touching the bank selection control, displaying a seventh interface; and in response to inputting authorized user identity information on the seventh interface, sending the first request to the server of the selected bank. In this way, the terminal device can accurately send the first request to the server, thereby improving the accuracy of bank card binding.

[0057] The sixth interface can be used to select the bank to which the bound bank card belongs. For example, the sixth interface can include information about Bank 1 (such as the bank's name, etc.), Bank 2, and Bank 3, as well as selection controls for each bank. In other words, the user can choose to bind a bank card from Bank 1, Bank 2, or Bank 3 in the sixth interface.

[0058] The seventh interface may be used to input the identity information of an authorized user. For example, a user may input the identity information of an authorized user on the seventh interface, and the terminal device may verify the identity information. After the verification is passed, the terminal device may send a first request to the server of the bank selected by the user.

[0059] Optionally, the identity information may include the user's name, user identification, and other information, which is not limited in the embodiments of the present disclosure.

[0060] Exemplarily, the sixth interface may include information about Bank 1 and Bank 2. The user may click the selection control of Bank 1, and the terminal device may display the seventh interface, which may include an input field for entering the user's name and the user's identifier. After the user enters the name and identifier in the input field, the terminal device may verify the name and identifier (such as querying the bank with which the user has signed a contract, verifying whether the user's identity information is correct, etc.). After the verification is passed, the terminal device may send a first request to the server of Bank 1. Optionally, the first request may include the user's unique identifier (the user's identifier stored in the bank's server), the identifier of the requested service (such as binding a bank card), etc. The embodiments of the present disclosure are not limited to this.

[0061] Next, combine Figure 3 and Figure 4 , the sixth and seventh interfaces are described in detail.

[0062] Figure 3 This is a schematic diagram of a sixth interface provided by an embodiment of the present disclosure. Figure 3, including: the sixth interface. The sixth interface includes a binding control, Bank 1 Savings Card, Bank 2 Savings Card, Bank 3 Savings Card, Bank 4 Savings Card, and selection controls corresponding to each bank's savings card. The sixth interface also includes a control for adding a bank. When the user clicks this control, the user can select a bound bank from multiple supported banks.

[0063] Figure 4 This is a schematic diagram of a seventh interface provided by an embodiment of the present disclosure. Figure 4 The seventh interface includes an interface for confirming identity information. The interface for confirming identity information includes a name input field, an identification input field, and a keyboard. The user can use the keyboard to enter the user's name in the name input field and the user's identification in the identification input field.

[0064] Optionally, the terminal device may display the sixth interface according to the following feasible implementation: In response to a payment operation for a selected product, the sixth interface is displayed. In this way, when the user binds a bank card, the interface for bank card binding displayed by the terminal device closely matches the interface of the current scenario, thereby improving the user experience.

[0065] For example, after the user selects the product to be purchased, he or she may click on the payment control. After the user clicks on the payment control, the terminal device may display a sixth interface, where the user may select a bank and complete the identification information entry on a seventh interface.

[0066] Optionally, the terminal device may also display the sixth interface based on other user operations. For example, the terminal device may display an interface for adding a bank card, which may include the bank cards that the user has bound and a control for adding a new bank card. When the user clicks the control for adding a new bank card, the terminal device may also display the sixth interface.

[0067] Next, combine Figure 5 , describes the process of the terminal device sending the first request to the server.

[0068] Figure 5 This is a schematic diagram of a process for sending a first request provided by an embodiment of the present disclosure. Figure 5 , including: a terminal device, servers of Bank 1, Bank 2, Bank 3, and Bank 4. The terminal device displays a product purchase interface, which includes a currently playing video associated with the product and a purchase window. This window may include a product image, product information, authorized recipient information, product price, and payment controls.

[0069] See Figure 5When the user clicks the payment control, the terminal device may display the sixth interface. This sixth interface may include the product name, price, a control for immediate payment, Bank 1 savings card, Bank 2 savings card, Bank 3 savings card, Bank 4 savings card, and corresponding selection controls for each bank's savings card. When the user clicks the selection control for Bank 2 savings card, the selection control is highlighted. When the user clicks the control for immediate payment, the terminal device may display the seventh interface.

[0070] See Figure 5 , the seventh interface includes the product name, selling price and a window for confirming identity information. The window for confirming identity information includes a name input field, an identifier input field and a confirmation control. The user can enter name A in the name input field, identifier B in the identifier input field, and click the confirmation control. The terminal device can verify the user's identity information. After the verification is passed, the terminal device can send a first request to the server of Bank 2 to obtain the contract information between the user and Bank 2. In this way, the bank card binding interface has a high degree of matching with the current interface, which improves the interface display effect. In addition, the user can verify the identity information in the application without jumping to the bank page, which improves the efficiency of bank card binding.

[0071] S202: Receive the contracted bank card information and / or contracted verification method information sent by the server.

[0072] In some embodiments, the contract information may include information about the contracted bank card and / or information about the contracted verification method. The contracted bank card information may include any information associated with the bank card, such as the type, card number, and status of the bank card, which is not limited in the present embodiment.

[0073] For example, a user signs a contract with a bank for bank card 1 and bank card 2, wherein the information of bank card 1 may include type A, card number B, and activation status, and the information of bank card 2 may include type C, card number D, and inactivated status.

[0074] In some embodiments, the contracted verification method information can be used to indicate how the bank will authenticate the user. In other words, when the user signs a contract with the bank, they can agree on a verification method. In this way, when the user requests bank services, the bank can verify the user's identity according to the agreed verification method.

[0075] In some embodiments, the verification method information may include a verification method and / or information associated with the verification method.

[0076] Exemplarily, the verification method information may include a verification method, which may be face verification, so that the terminal device can determine that the bank authenticates the user through face information.

[0077] Exemplarily, the verification method information may include information associated with the verification method, which may include a mobile phone number, that is, the verification method information may include the mobile phone number that the user has signed a contract with the bank, so that the terminal device can determine that the bank's verification method is mobile phone number verification.

[0078] Exemplarily, the verification method information may include a verification method and information associated with the verification method. The verification method may be mobile phone number verification, and the information associated with the verification method may include information of at least one contracted mobile phone number.

[0079] In some embodiments, the verification method may include at least one of the following: mobile phone number verification, face verification, fingerprint verification, iris verification, digital certificate verification, and security question verification.

[0080] In some embodiments, if the user and the bank agree in advance on multiple verification methods, the bank may determine the verification method information based on one or more verification methods.

[0081] Exemplarily, the verification methods pre-agreed between the user and the bank include mobile phone number verification, facial verification, and fingerprint verification. If mobile phone number verification is the verification method used last, the bank can determine the verification method information based on the mobile phone number verification method. If facial verification is the verification method used most frequently, the bank can determine the verification method information based on the facial verification method. If fingerprint verification is the verification method requested by the terminal device (e.g., the first request can include a fingerprint verification identifier), the bank can determine the verification method information based on the fingerprint verification method.

[0082] The mobile phone number information may include the mobile phone numbers that the user has reserved at the bank. For example, a bank card can be bound to one or more mobile phone numbers, and a user can sign up for multiple bank cards at the bank. Therefore, the user can reserve one or more mobile phone numbers at the bank.

[0083] For example, a user signs contracts with a bank for bank card 1 and bank card 2, where the mobile phone number bound to bank card 1 is number A, and the mobile phone number bound to bank card 2 is number B. In this way, the information of the mobile phone numbers signed by the user with the bank includes number A and number B.

[0084] In some embodiments, after receiving the first request sent by the terminal device, the server may send the contract information to the terminal device. For example, the server may send the contracted bank card information to the terminal device, the server may send the contracted mobile phone number information to the terminal device, and the terminal device may send the contracted bank card information and the contracted mobile phone number information to the terminal device. This is not limited in the present embodiment.

[0085] S203: Display a first interface based on the information of the contracted bank card and / or the contracted verification method information.

[0086] Optionally, when the contract information received by the terminal device includes information of a contracted bank card, the first interface displayed by the terminal device may include information of multiple bank cards.

[0087] Optionally, when the contract information received by the terminal device includes information about the signed authentication method, the terminal device may display the first interface according to the following feasible implementation method: determining the user authentication method indicated by the authentication method information, and displaying the first interface based on the authentication method. In this way, the terminal device can flexibly display the first interface based on the authentication method, thereby increasing the flexibility of the first interface.

[0088] In some embodiments, the terminal device may determine verification information associated with the identity authentication method (ie, the verification method) based on the identity authentication method, and determine that the first interface is used to input the verification information.

[0089] For example, when the verification method is mobile phone number verification, the first interface can be used to enter the SMS verification code.

[0090] Exemplarily, when the verification method is face verification, the first interface can be used to input face information.

[0091] Exemplarily, when the verification method is fingerprint verification, the first interface can be used to input fingerprint information.

[0092] Exemplarily, when the verification method is iris verification, the first interface can be used to input iris information.

[0093] Exemplarily, when the verification method is digital certificate verification, the first interface can be used to input the digital certificate.

[0094] Exemplarily, when the verification method is security question verification, the first interface can be used to input answers to the security questions.

[0095] In some embodiments, when the contracted verification method information is a mobile phone number, the first interface displayed by the terminal device may include the mobile phone number and may also include an input field for a verification code, wherein the verification code is a verification code sent by the server to the mobile phone number.

[0096] Optionally, when the contract information received by the terminal device includes the contracted verification method information and the contracted bank card information, the terminal device can display a first interface including the information of multiple bank cards, and when the user selects a bank card, the interface for entering the verification information associated with the verification method is displayed on the first interface, or the terminal device can display an interface for entering the verification information associated with the verification method, and when the user enters the verification information, the terminal device can display an interface including the information of multiple bank cards on the first interface. The embodiments of the present disclosure are not limited to this.

[0097] S204: In response to the user's interaction with the first interface, bind the bank card.

[0098] In some embodiments, when the first interface includes information of multiple bank cards, the user can select a bound bank card on the first interface, and after the verification information is verified, the terminal device can bind the bank card selected by the user.

[0099] In some embodiments, when the first interface is used to input verification information, the user can input the verification information on the first interface. After the verification is passed and the user has selected a bound bank card, the terminal device can bind the bank card selected by the user.

[0100] In some embodiments, the terminal device can display a first interface including multiple bank cards, and the user can select a bank card in the first interface. After the user's selection, the terminal device can display a first interface for entering verification information, and the user can enter a verification code in the first interface. After the verification information is verified, the terminal device can bind the bank card selected by the user.

[0101] Exemplarily, the contract information received by the terminal device includes mobile phone number 1, bank card 2, bank card 3, and bank card 4. The terminal device can determine the first interface 1 and the first interface 2. Among them, the first interface 1 includes bank card 2, bank card 3, and bank card 4. The user can select bank card 2 and bank card 3 on the first interface 1, and the terminal device can display the first interface 2. Among them, the first interface 2 includes an input field for mobile phone number 1 and a verification code. The user can enter the verification code sent by the server to mobile phone number 1 in the verification code input field of the first interface 2. After the verification code is verified, the terminal device can bind bank card 2 and bank card 3.

[0102] The disclosed embodiments provide a bank card binding method. In response to a payment operation for a selected commodity, a terminal device may display a sixth interface. In response to touching a bank selection control in the sixth interface, the terminal device may display a seventh interface. In response to inputting authorized user identity information in the seventh interface, the terminal device may send a first request to the server of the selected bank. The terminal device may receive information about a contracted bank card and / or information about a contracted verification method sent by the server, and display a first interface based on the contracted bank card information and / or information about the contracted verification method. In response to a user's interaction with the first interface, the terminal device may bind the contracted bank card. In the above method, the terminal device may bind the bank card within an application without having to jump to a bank page, reducing the time required for bank card binding and thereby improving the efficiency of bank card binding. Furthermore, the user does not need to manually enter the bank card number, thereby improving the accuracy of bank card binding and reducing the complexity of bank card binding. Furthermore, because the interface for bank card binding closely matches the interface of the current scenario, the user experience may be improved.

[0103] exist Figure 2 Based on the embodiment shown, since the contract information received by the terminal device may include the information of the contracted bank card and / or the contracted verification method information, the terminal device has different methods for binding the bank card when the contract information is different. Figure 6 , when the contract information includes the contracted verification method information, and the verification method information includes the mobile phone number information, the method for the terminal device to bind the bank card is described in detail.

[0104] Figure 6 A schematic diagram of another bank card binding method provided in an embodiment of the present disclosure. Figure 6 Based on the embodiment shown, the contract information includes the information of the contracted mobile phone number, see Figure 6 The method flow includes:

[0105] S601. Receive information about the subscribed mobile phone number sent by the server.

[0106] Optionally, the method for the terminal device to receive the information of the subscribed mobile phone number sent by the server can refer to the method in step S201 and step S202, which will not be described in detail in the embodiment of the present disclosure.

[0107] S602. Display the first interface based on the information of the contracted mobile phone number.

[0108] The terminal device can display the first interface based on the following feasible implementation method: sending a second request to the server, displaying the first interface, and receiving the first verification code sent by the server. In this way, when the contract information includes information about the contracted mobile phone number, the terminal device can enter the verification code on the first interface without jumping to the bank page, thereby improving the efficiency of SMS verification.

[0109] The second request may be used to request the server to send the first verification code to the contracted mobile phone number. For example, the terminal device may send the second request to the server, and after receiving the second request, the server may send the first verification code to the contracted mobile phone number.

[0110] Optionally, the verification code may be a text message verification code or any other type of verification code, and the verification code may be a 4-digit number or a 6-digit number, or any other feasible verification code, which is not limited in the embodiments of the present disclosure.

[0111] In some embodiments, after the terminal device obtains the information of the contracted mobile phone number, if the number of contracted mobile phone numbers is 1, the terminal device can send a second request to the server. After receiving the second request, the server can send a first verification code to the mobile phone number.

[0112] In some embodiments, after a terminal device obtains information about a signed mobile phone number, if the number of signed mobile phone numbers is greater than one, the terminal device may display multiple mobile phone numbers, and the user may select one of the numbers. After the user selects a mobile phone number, the terminal device may send a second request to the server, which may include an identifier of the selected mobile phone number. Based on the identifier, the server may send a first verification code to the mobile phone number selected by the user. In this way, the server can send a verification code to the mobile phone number selected by the user, thereby increasing the flexibility of selecting a mobile phone number.

[0113] For example, the information of the subscribed mobile phone numbers obtained by the terminal device includes mobile phone number 1, mobile phone number 2, and mobile phone number 3. The terminal device can display mobile phone number 1, mobile phone number 2, and mobile phone number 3. If the user clicks mobile phone number 1, the terminal device can send a second request to the server. Upon receiving the second request, the server can send a text message verification code to mobile phone number 1.

[0114] In some embodiments, after the terminal device obtains the information of the contracted mobile phone numbers, if the number of contracted mobile phone numbers is greater than one, the terminal device can send a second request to the server. The server can then obtain the most recently used mobile phone number from the multiple mobile phone numbers and send the first verification code to the most recently used mobile phone number. This eliminates the need for the user to select a mobile phone number, avoids the situation where the mobile phone number selected by the user is different from the mobile phone number reserved by the bank, and improves the success rate of bank card binding.

[0115] For example, the terminal device obtains information about the subscribed mobile phone numbers, including mobile phone number 1 and mobile phone number 2. The terminal device may send a second request to the server. If the server determines that mobile phone number 1 is the most recently used mobile phone number (e.g., the last used mobile phone number), the server may send a first verification code to mobile phone number 1. If the server determines that mobile phone number 2 is the most frequently used mobile phone number, the server may send a first verification code to mobile phone number 2.

[0116] In some embodiments, the first interface can be used to enter the first verification code. For example, when the terminal device sends the second request to the server, the first interface can be displayed, and the first interface can include an input field for the verification code, and the user can enter the verification code on the first interface.

[0117] Next, combine Figure 7 , describe the first interface.

[0118] Figure 7 This is a schematic diagram of a first interface provided by an embodiment of the present disclosure. Figure 7 , including: a first interface. The first interface includes a window for entering a text message verification code. The window for entering the text message verification code includes an input field for the text message verification code, a mobile phone number, and a keyboard. The user can enter the text message verification code received by the mobile phone number in the input field. The terminal device can send the text message verification code entered by the user to the server.

[0119] S603: In response to the user's interaction with the first interface, bind the bank card.

[0120] In some embodiments, the terminal device can bind a bank card according to the following feasible implementation method: in response to a first verification code entered on a first interface, a third request is sent to a server, information about a contracted bank card is received from the server, a second interface is displayed based on the contracted bank card information, and in response to a user's interaction with the second interface, the contracted bank card is bound. In this way, after the verification code is verified, the terminal device can display the contracted bank card, and the user can select the contracted bank card for binding. Therefore, the bank card binding operation does not require jumping to the bank page, thereby improving the efficiency of bank card binding.

[0121] The third request may be used to obtain information about the contracted bank card. For example, the third request may include a first verification code input by the user. When the server receives the third request, it may verify the first verification code. If the verification is successful, the server may send the contracted bank card information to the terminal device. That is, if the first verification code received by the server is the same as the first verification code sent by the server, the server may send the contracted bank card information to the terminal device.

[0122] In some embodiments, the terminal device displays a second interface based on the information of the contracted bank card. Specifically, the terminal device may determine the type, card number, and status of the contracted bank card based on the information of the contracted bank card and then display the second interface. In this way, the user can select one or more bound bank cards on the second interface, thereby improving the efficiency of bank card binding.

[0123] The second interface may include the type, card number, status, and selection controls corresponding to each contracted bank card. For example, if the contracted bank card information received by the terminal device includes information about bank card 1, bank card 2, and bank card 3, the terminal device may display the second interface, which may include the type, card number, and status of bank card 1, the type, card number, and status of bank card 2, and the type, card number, and status of bank card 3.

[0124] Next, combine Figure 8 , a detailed description of the second interface is given.

[0125] Figure 8 This is a schematic diagram of a second interface provided by an embodiment of the present disclosure. Figure 8 , including: a second interface. The second interface includes the name of the bank, information of bank card 1, information of bank card 2, information of bank card 3 and a control for immediate binding. The information of bank card 1 includes card number A and activation, the information of bank card 2 includes card number B and activation, and the information of bank card 3 includes card number C and unactivated. The second interface may also include a mobile phone number and a change control, wherein the mobile phone number is the mobile phone number to which the server sends the first verification code. When the user clicks the change control, the terminal device may request the server to resend the first verification code to the replaced mobile phone number. In this way, users can add multiple bank cards at a time, thereby improving the efficiency of bank card binding.

[0126] In some embodiments, since the first verification code has been verified, the terminal device can bind the bank card selected by the user in response to the user selecting a bank card in the second interface.

[0127] Next, combine Figure 9 , which provides a detailed description of the process of binding a terminal device to a contracted bank card.

[0128] Figure 9 This is a schematic diagram of a bank card binding process provided by an embodiment of the present disclosure. Figure 9 , including: a terminal device. The terminal device displays a product purchase interface, which includes a currently playing video associated with the product and a purchase window. The window may include a product image, product information, authorized recipient information, product price, and payment controls.

[0129] See Figure 9 When the user clicks the payment control, the terminal device may display the seventh interface. This seventh interface may include a control for immediate payment, Bank 1 savings card, Bank 2 savings card, Bank 3 savings card, Bank 4 savings card, and corresponding selection controls for each bank's savings card. When the user clicks the selection control for Bank 2 savings card, the selection control is highlighted. When the user clicks the immediate payment control, the terminal device may display the eighth interface.

[0130] See Figure 9 The eighth interface includes a name input field, an identifier input field, and a confirmation control. The user can enter name a in the name input field, enter identifier b in the identifier input field, and click the confirmation control. The terminal device can verify the user's identity information. After the verification is passed, the terminal device can send a data packet to the server of bank 2 ( Figure 9 (not shown) sends a first request, i.e., obtains the mobile phone number that the user has signed a contract with Bank 2.

[0131] See Figure 9 The terminal device may send a second request to Bank 2's server, which may then send a text message verification code to the user's registered mobile phone number. The terminal device may then display a first interface. This first interface includes the registered mobile phone number, an input field for the text message verification code, and a keyboard. The user may enter 123456 in the text message verification code input field, and the terminal device may then send a third request to Bank 2's server, including the text message verification code, to retrieve the user's registered bank card.

[0132] See Figure 9 When the server successfully verifies the SMS verification code, it can send the contracted bank card information to the terminal device. The terminal device can display a second interface, which may include the name of Bank 2, the contracted mobile phone number, a control for changing the mobile phone number, information about Bank Card 1, Bank Card 2, and Bank Card 3, selection controls corresponding to the information of each bank card, and a control for immediately binding.

[0133] See Figure 9 The user clicks the selection control corresponding to Bank Card 1 and Bank Card 2, and both selection controls become highlighted. The user can then click the "Bind Now" control, and the terminal device will display a message confirming successful bank card binding. It will also display a payment window, which includes the information for both bound Bank Card 1 and Bank Card 2. The user can select either bank card to pay for the product. This allows users to quickly bind bank cards, improving bank card binding efficiency.

[0134] The disclosed embodiments provide a bank card binding method, wherein a terminal device can receive information about a signed mobile phone number from a server and display a first interface based on the signed mobile phone number information. In response to a first verification code entered on the first interface, the terminal device can send a third request to the server, receive information about the signed bank card from the server, and display a second interface based on the signed bank card information. In response to a user's interaction with the second interface, the signed bank card is bound. In this way, a user can bind multiple bank cards at once, and the terminal device does not need to jump to the bank page, thereby improving the efficiency of bank card binding.

[0135] Based on any of the above embodiments, Figure 10 , when the contract information includes the information of the contracted bank card, the method of binding the bank card by the terminal device is described in detail.

[0136] Figure 10 A schematic diagram of another bank card binding method provided in an embodiment of the present disclosure. Figure 10 Based on the embodiment shown, the contract information includes the information of the bank card that has signed the contract, see Figure 10 The method flow includes:

[0137] S1001. Receive the contracted bank card information sent by the server.

[0138] Optionally, the method for the terminal device to receive the information of the contracted bank card sent by the server can refer to the method in step S201 and step S202, which will not be described in detail in the embodiment of the present disclosure.

[0139] S1002. Display the first interface based on the information of the contracted bank card.

[0140] The terminal device may display the first interface based on the following feasible implementation: determining the type, card number, and status of the contracted bank card based on the information of the contracted bank card, and then displaying the first interface, wherein the first interface includes the type, card number, status, and selection controls corresponding to each contracted bank card. In this way, the user can bind multiple bank cards in the first interface, improving bank card binding efficiency.

[0141] exist Figure 10 In the embodiment shown, the first interface can be used to add a bank card. In other words, the first interface is used to add a bank card. Figure 6 The second interface in the embodiment shown is the same, i.e. Figure 6 The embodiment shown is to first verify the verification code and then bind the bank card. Figure 10 In the embodiment shown, the bank card is selected first and then the verification code is verified.

[0142] S1003: In response to the user's interaction with the first interface, bind the bank card.

[0143] The terminal device can bind a bank card according to the following feasible implementation: in response to touching a selection control, sending a fourth request to a server, receiving the contracted verification method information sent by the server, displaying a third interface based on the contracted verification method information, and binding the selected bank card in response to user interaction with the third interface. In this way, the user can select a bound bank card in the first interface and enter verification information in the second interface, without having to bind the bank card on the bank page, thereby improving bank card binding efficiency.

[0144] The fourth request may be used to obtain the contracted verification method information. For example, the verification method information may include mobile phone number information. When the user confirms the bound bank card, the terminal device may send the fourth request to the server, and the server may send the contracted mobile phone number information to the terminal device. For example, the verification method information may include facial verification. When the user confirms the bound bank card, the terminal device may send the fourth request to the server, and the server may send the terminal device an indication that the verification method is facial verification.

[0145] In some embodiments, the third interface can be used to input verification information. For example, the third interface can be used to input the second verification code. In other words, when the third interface is used to input the second verification code, the third interface is Figure 6 The first interface in the illustrated embodiment is the same, wherein the second verification code may be a verification code sent by the server to the contracted mobile phone number.

[0146] When the contracted verification method includes a mobile phone number, the terminal device displays the third interface based on the contracted verification method. Specifically, this may include sending a fifth request to the server, displaying the third interface, and receiving the second verification code from the server. This eliminates the need for the terminal device to redirect to the bank's website; users can complete verification of the verification code within the current interface, improving the efficiency of bank card binding.

[0147] In some embodiments, the fifth request may be used to request the server to send a second verification code to a signed mobile phone number. For example, a user may select a mobile phone number from the signed mobile phone numbers, and the terminal device may send the fifth request to the server, which may in turn send the second verification code to the user-selected mobile phone number. For example, upon receiving information about a signed mobile phone number, the terminal device may send the fifth request to the server, which may in turn send the second verification code to the most recently used mobile phone number or the most frequently used mobile phone number.

[0148] In some embodiments, since the user has selected a bank card, the terminal device can send the second verification code to the server in response to the second verification code entered by the user in the third interface. The server can verify the second verification code. When the second verification code is verified, the terminal device can bind the selected bank card.

[0149] Next, combine Figure 11 , which provides a detailed description of the process of binding a terminal device to a contracted bank card.

[0150] Figure 11 This is a schematic diagram of another bank card binding process provided by an embodiment of the present disclosure. Figure 11 , including: a terminal device. The terminal device displays a product purchase interface, which includes a currently playing video associated with the product and a purchase window. The window may include a product image, product information, authorized recipient information, product price, and payment controls.

[0151] See Figure 11 When the user clicks the payment control, the terminal device may display the seventh interface. This seventh interface may include a control for immediate payment, Bank 1 savings card, Bank 2 savings card, Bank 3 savings card, Bank 4 savings card, and corresponding selection controls for each bank's savings card. When the user clicks the selection control for Bank 2 savings card, the selection control is highlighted. When the user clicks the immediate payment control, the terminal device may display the eighth interface.

[0152] See Figure 11 The eighth interface includes a name input field, an identifier input field, and a confirmation control. The user can enter name a in the name input field, enter identifier b in the identifier input field, and click the confirmation control. The terminal device can verify the user's identity information. After the verification is passed, the terminal device can send a data packet to the server of bank 2 ( Figure 11 (not shown) sends a first request, i.e., obtains the bank card signed by the user and bank 2.

[0153] See Figure 11 The terminal device can display a first interface, which may include the name of bank 2, the contracted mobile phone number, a control for changing the mobile phone number, information of bank card 1, information of bank card 2, information of bank card 3, selection controls corresponding to the information of each bank card, and a control for immediate binding.

[0154] See Figure 11The user clicks the selection control corresponding to the information of bank card 1 and the selection control corresponding to the information of bank card 2, and both selection controls may be highlighted. The user may click the "Bind Now" control, and the terminal device may send a fourth request to the server of bank 2, i.e., to obtain the mobile phone number that the user has signed a contract with bank 2.

[0155] See Figure 11 After receiving the mobile phone number, the terminal device can send a fifth request to the server, and the server can send a text message verification code to the mobile phone number. The terminal device can display a third interface. This third interface includes the subscribed mobile phone number, an input field for the text message verification code, and a keyboard. The user can enter 123456 in the text message verification code input field, and the terminal device can send the text message verification code to the bank card.

[0156] See Figure 11 When the server successfully verifies the SMS verification code, the terminal device can display a message indicating that the bank card binding is successful. It can also display a payment window that includes information about bound bank cards 1 and 2. The user can select either bank card to pay for the product. This allows users to quickly bind bank cards, improving bank card binding efficiency.

[0157] In some embodiments, when the contracted authentication method information includes face authentication, fingerprint authentication, iris authentication, digital certificate authentication, and security question authentication, the terminal device does not need to send the fifth request to the server. That is, the terminal device can display the third interface according to the authentication method indicated by the contracted authentication method information. For example, when the authentication method information includes face authentication, the third interface is used to enter facial information.

[0158] Optionally, after the terminal device sends the second request or the fifth request to the server, the method further includes: displaying a fifth interface in response to a change of the mobile phone number, wherein the fifth interface includes multiple contracted mobile phone numbers, and in response to selection of any one of the multiple contracted mobile phone numbers, sending a sixth request to the server. This allows users to flexibly select a contracted mobile phone number, thereby improving the success rate of bank card binding.

[0159] The sixth request can be used to request the server to send a third verification code to the selected mobile phone number. For example, after the server selects a signed mobile phone number, if the user's current mobile phone number is not the one selected by the server, the user can reselect the current mobile phone number. The server can then send the third verification code to the current mobile phone number, thereby improving the success rate of bank card binding.

[0160] The disclosed embodiments provide a bank card binding method, wherein a terminal device can receive information about a contracted bank card sent by a server and display a first interface based on the contracted bank card information. In response to a touch on a selection control, the terminal device can send a fourth request to the server and receive information about the contracted verification method sent by the server. The terminal device can display a third interface based on the contracted verification method information and, in response to a user's interaction with the third interface, bind the selected bank card. In this way, a user can bind multiple bank cards at once without the terminal device having to jump to a bank page, thereby improving bank card binding efficiency.

[0161] Based on any of the above embodiments, Figure 12 , a detailed description is given of the method for the terminal device to bind the bank card when the contract information includes the information of the contracted bank card and the contracted verification method information.

[0162] Figure 12 A schematic diagram of another bank card binding method provided in an embodiment of the present disclosure. Figure 12 Based on the embodiment shown, the contract information includes the information of the bank card that has signed the contract, see Figure 12 The method flow includes:

[0163] S1201. Receive the contracted bank card information and contracted verification method information sent by the server.

[0164] Optionally, the method for the terminal device to receive the information of the contracted bank card and the contracted verification method information sent by the server can refer to the method in step S201 and step S202, and will not be repeated here in the embodiment of the present disclosure.

[0165] S1202. Display the first interface based on the information of the contracted bank card.

[0166] The first interface includes the type, card number, status of the contracted bank cards, and selection controls corresponding to each contracted bank card.

[0167] It should be noted that the terminal device displays the fourth interface ( Figure 6 The second interface in the embodiment shown, Figure 10 The method of the first interface in the embodiment shown can refer to the method in the above embodiment, and the embodiment of the present disclosure will not be repeated here.

[0168] S1203: In response to touching the selection control, displaying a fourth interface in the first interface according to the signed verification method information.

[0169] In some embodiments, when the verification method information includes mobile phone number information, the terminal device may send a seventh request to the server, the seventh request may be used to request the server to send a fourth verification code to the subscribed mobile phone number. The fourth interface may be used to enter verification information.

[0170] Exemplarily, since the terminal device has obtained the contracted mobile phone number, the terminal device can request the server to send a fourth verification code to the contracted mobile phone number, wherein the fourth interface is used to input the fourth verification code.

[0171] It should be noted that when the verification method information includes other verification methods, the method for the terminal device to display the fourth interface can refer to the method in the above embodiment, and the embodiment of the present disclosure will not be repeated here.

[0172] S1204: In response to the user's interaction with the fourth interface, bind the bank card.

[0173] In some embodiments, the terminal device can send the verification information to the server in response to the verification information entered by the user on the fourth interface. The server can verify the verification information. After the verification is passed, the terminal device can determine that the bank card selected by the user is successfully bound.

[0174] Exemplarily, the terminal device may send the fourth verification code to the server in response to the fourth verification code entered by the user on the fourth interface. The server may verify the fourth verification code. When the fourth verification code is the same as the verification code sent by the server, the server determines that the verification is successful and sends a verification success message to the terminal device. The terminal device may determine that the bank card selected by the user is successfully bound.

[0175] Next, combine Figure 13 , which provides a detailed description of the process of binding a terminal device to a contracted bank card.

[0176] Figure 13 This is a schematic diagram of another bank card binding process provided by an embodiment of the present disclosure. Figure 13 , including: a terminal device. The terminal device displays a product purchase interface, which includes a currently playing video associated with the product and a purchase window. The window may include a product image, product information, authorized recipient information, product price, and payment controls.

[0177] See Figure 13When the user clicks the payment control, the terminal device may display the seventh interface. This seventh interface may include a control for immediate payment, Bank 1 savings card, Bank 2 savings card, Bank 3 savings card, Bank 4 savings card, and corresponding selection controls for each bank's savings card. When the user clicks the selection control for Bank 2 savings card, the selection control is highlighted. When the user clicks the immediate payment control, the terminal device may display the eighth interface.

[0178] See Figure 13 The eighth interface includes a name input field, an identifier input field, and a confirmation control. The user can enter name a in the name input field, enter identifier b in the identifier input field, and click the confirmation control. The terminal device can verify the user's identity information. After the verification is passed, the terminal device can send a data packet to the server of bank 2 ( Figure 13 (not shown) sends a first request, that is, obtains the bank card and mobile phone number that the user has signed a contract with Bank 2.

[0179] See Figure 13 The terminal device can display the fourth interface, which may include the name of bank 2, the contracted mobile phone number D, a control for changing the mobile phone number, information of bank card 1, information of bank card 2, information of bank card 3, selection controls corresponding to the information of each bank card, and a control for immediate binding.

[0180] See Figure 13 The user clicks the selection controls corresponding to bank card 1 and bank card 2, and both selection controls may be highlighted. The user may click the "Bind Now" control, and the terminal device may display a fifth interface, which includes the signed mobile phone number D, an input field for the SMS verification code, a keyboard, and a control for changing the mobile phone number. The terminal device may send a sixth request to the server, and the server may send the SMS verification code to mobile phone number D.

[0181] See Figure 13 The user can click the control to change their phone number. The terminal device will display a window showing the phone numbers reserved by Bank 2. This window will include phone numbers D, E, F, G, a confirmation control, and selection controls for each phone number. After the user clicks the selection control for phone number E and then clicks the confirmation control, the terminal device will redisplay the fifth interface. The phone number displayed in this fifth interface will be updated from phone number D to phone number E.

[0182] See Figure 13 , the terminal device can send a sixth request to the server again, and the server can resend the SMS verification code to mobile phone number E. The user can enter the SMS verification code "123456" in the fifth interface, the terminal device can send the SMS verification code to the server, and the server can verify the SMS verification code.

[0183] See Figure 13 After verification is successful (e.g., the server sends a verification success message to the terminal device), the terminal device can display a message indicating successful bank card binding and a payment window containing information about bound bank card 1 and bank card 2. The user can select either bank card to pay for the product. This allows users to quickly bind bank cards, improving bank card binding efficiency.

[0184] The disclosed embodiments provide a bank card binding method, wherein a terminal device can receive information about a contracted bank card and a contracted verification method from a server. The terminal device can display a first interface based on the contracted bank card information. In response to a touch on a selection control, the terminal device displays a fourth interface within the first interface based on the contracted verification method information. In response to a user's interaction with the fourth interface, the bank card is bound. In this way, the terminal device can bind multiple bank cards within an application without having to jump to a bank page, and the user does not need to manually enter the bank card number. Therefore, the accuracy of bank card binding can be improved, the complexity of bank card binding can be reduced, and the efficiency of bank card binding can be improved.

[0185] Figure 14 This is a schematic diagram of the structure of a bank card binding device provided by an embodiment of the present disclosure. Figure 14 The bank card binding device 1400 includes a sending module 1401, a receiving module 1402, a display module 1403 and a processing module 1404, wherein:

[0186] The sending module 1401 is configured to send a first request to a bank server in response to a bank card binding operation, wherein the first request is configured to obtain contract information between the authorized user and the bank;

[0187] The receiving module 1402 is used to receive the contracted bank card information and / or the contracted verification method information sent by the server, wherein the verification method information is used to indicate the method by which the bank authenticates the user;

[0188] The display module 1403 is configured to display a first interface based on the information of the contracted bank card and / or the contracted verification method information;

[0189] The processing module 1404 is configured to bind a bank card in response to the user's interaction with the first interface.

[0190] According to one or more embodiments of the present disclosure, the display module 1403 is specifically configured to:

[0191] Determining a method for authenticating the user as indicated by the verification method information;

[0192] The first interface is displayed according to the identity authentication method.

[0193] In this way, the flexibility of the first interface can be improved.

[0194] According to one or more embodiments of the present disclosure, the display module 1403 is specifically configured to:

[0195] Sending a second request to the server, wherein the second request is used to request the server to send a first verification code to the mobile phone number;

[0196] A first interface is displayed, and a first verification code sent by the server is received, where the first interface is used to input the first verification code.

[0197] In this way, when the contract information includes information about the contracted mobile phone number, the bank card binding device can input the verification code on the first interface without jumping to the bank page, thereby improving the efficiency of SMS verification.

[0198] According to one or more embodiments of the present disclosure, the processing module 1404 is specifically configured to:

[0199] In response to the first verification code input on the first interface, sending a third request to the server, wherein the third request is used to obtain information of the contracted bank card;

[0200] receiving the information of the contracted bank card sent by the server, and displaying a second interface according to the information of the contracted bank card;

[0201] In response to the user's interaction with the second interface, the contracted bank card is bound.

[0202] In this way, after the verification code is verified, the bank card binding device can display the contracted bank card, and the user can select the contracted bank card for binding. Therefore, the bank card binding operation does not need to jump to the bank page, which improves the bank card binding efficiency.

[0203] According to one or more embodiments of the present disclosure, the display module 1403 is specifically configured to:

[0204] Determining the type, card number, and status of the contracted bank card based on the information of the contracted bank card;

[0205] The second interface is displayed, which includes the type, the card number, the status, and selection controls corresponding to each signed bank card.

[0206] In this way, the user can select one or more bank cards to be bound on the second interface, thereby improving the efficiency of bank card binding.

[0207] According to one or more embodiments of the present disclosure, the display module 1403 is specifically configured to:

[0208] Determining the type, card number, and status of the contracted bank card based on the information of the contracted bank card;

[0209] The first interface is displayed, which includes the type, the card number, the status, and selection controls corresponding to each signed bank card.

[0210] In this way, users can bind multiple bank cards in the first interface, thereby improving the efficiency of bank card binding.

[0211] According to one or more embodiments of the present disclosure, the processing module 1404 is specifically configured to:

[0212] In response to touching the selection control, sending a fourth request to the server, the fourth request being used to obtain the signed verification method information;

[0213] receiving the signed verification method information sent by the server, and displaying a third interface according to the signed verification method information;

[0214] In response to the user's interaction with the third interface, the selected bank card is bound.

[0215] In this way, the user can select the bound bank card in the first interface and enter the verification code sent by the server in the second interface, without having to bind the bank card in the bank page, thereby improving the efficiency of bank card binding.

[0216] According to one or more embodiments of the present disclosure, the display module 1403 is specifically configured to:

[0217] Sending a fifth request to the server, wherein the fifth request is used to request the server to send a second verification code to the mobile phone number;

[0218] A third interface is displayed, and a second verification code sent by the server is received. The third interface is used to input the second verification code.

[0219] In this way, the bank card binding device does not need to jump to the bank page, and the user can complete the verification of the verification code in the current interface, thereby improving the efficiency of bank card binding.

[0220] According to one or more embodiments of the present disclosure, the display module 1403 is specifically configured to:

[0221] Displaying a first interface based on the information of the contracted bank card, the first interface including the type, card number, status of the contracted bank card, and selection controls corresponding to each contracted bank card;

[0222] In response to touching the selection control, a fourth interface is displayed in the first interface according to the signed verification method information, and the fourth interface is used to input verification information associated with the verification method information.

[0223] In this way, the bank card binding device can bind multiple bank cards in the application without jumping to the bank page, and the user does not need to manually enter the bank card number and mobile phone number. Therefore, the accuracy of bank card binding can be improved, the complexity of bank card binding can be reduced, and the efficiency of bank card binding can be improved.

[0224] According to one or more embodiments of the present disclosure, the display module 1403 is further configured to:

[0225] In response to the change operation of the mobile phone number, a fifth interface is displayed, wherein the fifth interface includes multiple contracted mobile phone numbers;

[0226] In response to the selection of any one of the multiple contracted mobile phone numbers, a sixth request is sent to the server, and the sixth request is used to request the server to send a third verification code to the selected mobile phone number.

[0227] In this way, users can flexibly choose a contracted mobile phone number to increase the success rate of bank card binding.

[0228] According to one or more embodiments of the present disclosure, the sending module 1401 is specifically configured to:

[0229] Displaying a sixth interface, the sixth interface including information of at least one type of bank and selection controls for each type of bank;

[0230] In response to a touch on the bank selection control, displaying a seventh interface for inputting identity information of an authorized user;

[0231] In response to inputting the identity information of the authorized user on the seventh interface, the first request is sent to the server of the selected bank.

[0232] In this way, the bank card binding device can accurately send the first request to the server, thereby improving the accuracy of bank card binding.

[0233] According to one or more embodiments of the present disclosure, the sending module 1401 is specifically configured to:

[0234] In response to the payment operation for the selected product, the sixth interface is displayed.

[0235] In this way, when the user binds the bank card, the interface for bank card binding displayed by the bank card binding device has a high degree of matching with the interface of the current scene, thereby improving the user experience.

[0236] The information recommendation device provided in the embodiment of the present disclosure can be used to implement the technical solution of the above method embodiment. Its implementation principle and technical effects are similar and will not be described in detail in this embodiment.

[0237] Figure 15 This is a schematic diagram of the structure of a terminal device provided by an embodiment of the present disclosure. Figure 15 , which shows a schematic diagram of the structure of a terminal device 1500 suitable for implementing the embodiment of the present disclosure. Figure 15 As shown, terminal device 1500 may include a processing device (e.g., a central processing unit, a graphics processing unit, etc.) 1501, which can perform various appropriate actions and processes based on programs stored in a read-only memory (ROM) 1502 or programs loaded from a storage device 1508 into a random access memory (RAM) 1503. Various programs and data required for the operation of terminal device 1500 are also stored in RAM 1503. Processing device 1501, ROM 1502, and RAM 1503 are connected to each other via a bus 1504. An input / output (I / O) interface 1505 is also connected to bus 1504.

[0238] Typically, the following devices may be connected to the I / O interface 1505: an input device 1506 including, for example, a touch screen, a touchpad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; an output device 1507 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; a storage device 1508 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 1509. The communication device 1509 may allow the terminal device 1500 to communicate with other devices wirelessly or by wire to exchange data. Figure 15 The terminal device 1500 is shown as having various devices, but it should be understood that it is not required to implement or possess all of the devices shown. More or fewer devices may be implemented or possessed instead.

[0239] In particular, according to an embodiment of the present disclosure, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present disclosure includes a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network via the communication device 1509, or installed from the storage device 1508, or installed from the ROM 1502. When the computer program is executed by the processing device 1501, the above-mentioned functions defined in the method of the embodiment of the present disclosure are performed.

[0240] It should be noted that the computer-readable medium mentioned above in the present disclosure may be a computer-readable signal medium or a computer-readable storage medium, or any combination of the two. A computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or component, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present disclosure, a computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, device, or component. In the present disclosure, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, which carries computer-readable program code. Such a propagated data signal may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium that can transmit, propagate, or transport a program for use by or in conjunction with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium may be transmitted using any suitable medium, including but not limited to wires, optical cables, RF (radio frequency), or any suitable combination thereof.

[0241] The computer-readable medium may be included in the terminal device, or may exist independently without being incorporated into the terminal device.

[0242] The computer-readable medium carries one or more programs. When the one or more programs are executed by the terminal device, the terminal device executes the method shown in the above embodiment.

[0243] An embodiment of the present disclosure provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer-executable instructions. When a processor executes the computer-executable instructions, various methods that may be involved in the above embodiments are implemented.

[0244] An embodiment of the present disclosure provides a computer program product, including a computer program, which implements various possible methods involved in the above embodiments when executed by a processor.

[0245] Since the terminal device can obtain the contract information from the bank's server and render the first interface associated with the information of the contracted bank card and / or the information of the contracted mobile phone number based on the contract information, the user can bind the bank card in the interface currently displayed by the terminal device, and the terminal device does not need to jump to the bank page. Therefore, the efficiency of bank card binding can be improved. Moreover, since the user does not need to manually enter the bank card number and mobile phone number, the accuracy of bank card binding can be improved, thereby improving the user experience.

[0246] Computer program code for performing the operations of the present disclosure may be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving a remote computer, the remote computer may be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0247] The flowcharts and block diagrams in the accompanying drawings illustrate the possible implementation architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each box in the flowchart or block diagram can represent a module, program segment, or a part of code, and the module, program segment, or a part of code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order than that marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flowchart, and the combination of the boxes in the block diagram and / or flowchart, can be implemented with a dedicated hardware-based system that performs the specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0248] The units involved in the embodiments described in this disclosure may be implemented in software or hardware. In some cases, the name of a unit does not limit the unit itself. For example, the first acquisition unit may also be described as a "unit for acquiring at least two Internet Protocol addresses."

[0249] The functions described above herein can be performed at least in part by one or more hardware logic components. For example, without limitation, the hardware logic components of exemplary types that can be used include: field programmable gate array (FPGA), application specific integrated circuit (ASIC), application specific standard product (ASSP), system on chip (SOC), complex programmable logic device (CPLD) etc. In the context of the present disclosure, machine-readable medium can be a tangible medium that can contain or store a program for use with an instruction execution system, device or equipment or used in combination with an instruction execution system, device or equipment. Machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. Machine-readable medium can include but is not limited to electronic, magnetic, optical, electromagnetic, infrared or semiconductor systems, devices or equipment, or any suitable combination of the above. More specific examples of machine-readable storage media can include electrical connections based on one or more lines, portable computer disks, hard disks, random access memories (RAM), read-only memories (ROM), erasable programmable read-only memories (EPROM or flash memory), optical fibers, portable compact disk read-only memories (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the above.

[0250] It should be noted that the modifications of "one" and "multiple" mentioned in the present disclosure are illustrative rather than restrictive, and those skilled in the art should understand that unless otherwise clearly indicated in the context, they should be understood as "one or more".

[0251] The names of the messages or information exchanged between the multiple devices in the embodiments of the present disclosure are for illustrative purposes only and are not intended to limit the scope of these messages or information. It is understood that the data involved in this technical solution (including but not limited to the data itself, the acquisition or use of the data) shall comply with the requirements of relevant laws, regulations and relevant provisions. Data may include information, parameters and messages, such as flow switching indication information.

[0252] The above description is merely a preferred embodiment of the present disclosure and an illustration of the technical principles employed. Those skilled in the art should understand that the scope of disclosure involved in the present disclosure is not limited to the technical solutions formed by the specific combination of the above-mentioned technical features, but also includes other technical solutions formed by any combination of the above-mentioned technical features or their equivalents without departing from the above-mentioned disclosed concepts. For example, a technical solution formed by replacing the above-mentioned features with (but not limited to) technical features with similar functions disclosed in this disclosure.

[0253] In addition, although the operations are described in a specific order, this should not be understood as requiring that these operations be performed in the specific order shown or in a sequential order. Under certain circumstances, multitasking and parallel processing may be advantageous. Similarly, although several specific implementation details are included in the above discussion, these should not be interpreted as limiting the scope of this disclosure. Certain features described in the context of separate embodiments can also be implemented in a single embodiment in combination. Conversely, the various features described in the context of a single embodiment can also be implemented in multiple embodiments individually or in any suitable sub-combination. Although the subject matter has been described in language specific to structural features and / or method logical actions, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or actions described above. On the contrary, the specific features and actions described above are merely example forms of implementing the claims.

Claims

1. A bank card binding method, characterized in that: include: In response to a bank card binding operation, sending a first request to a server of a bank, wherein the first request is used to obtain contract information between the authorized user and the bank; receiving information of a signed bank card and / or information of a signed verification method sent by the server, wherein the verification method information is used to indicate a method by which the bank authenticates the user; A first interface is displayed based on the information of the contracted bank card and / or the contracted verification method information, and the bank card is bound in response to the user's interaction with the first interface.

2. The method according to claim 1, characterized in that According to the signed verification method information, the first interface is displayed, including: Determining a method for authenticating the user as indicated by the verification method information; The first interface is displayed according to the identity authentication method.

3. The method according to claim 2, characterized in that The contracted verification method information includes mobile phone number information, and the identity verification method is mobile phone number verification; displaying the first interface according to the identity verification method includes: Sending a second request to the server, wherein the second request is used to request the server to send a first verification code to the mobile phone number; A first interface is displayed, and a first verification code sent by the server is received, where the first interface is used to input the first verification code.

4. The method according to claim 2 or 3, characterized in that Binding the bank card in response to the user's interaction with the first interface includes: In response to the first verification code input on the first interface, sending a third request to the server, wherein the third request is used to obtain information of the contracted bank card; receiving the information of the contracted bank card sent by the server, and displaying a second interface according to the information of the contracted bank card; In response to the user's interaction with the second interface, the contracted bank card is bound.

5. The method according to claim 4, characterized in that The displaying of the second interface according to the information of the contracted bank card includes: Determining the type, card number, and status of the contracted bank card based on the information of the contracted bank card; The second interface is displayed, which includes the type, the card number, the status, and selection controls corresponding to each signed bank card.

6. The method according to claim 1, characterized in that According to the information of the contracted bank card, a first interface is displayed, including: Determining the type, card number, and status of the contracted bank card based on the information of the contracted bank card; The first interface is displayed, which includes the type, the card number, the status, and selection controls corresponding to each signed bank card.

7. The method according to claim 6, characterized in that Binding the bank card in response to the user's interaction with the first interface includes: In response to touching the selection control, sending a fourth request to the server, the fourth request being used to obtain the signed verification method information; receiving the signed verification method information sent by the server, and displaying a third interface according to the signed verification method information; In response to the user's interaction with the third interface, the selected bank card is bound.

8. The method according to claim 7, characterized in that The contracted verification method information includes mobile phone number information; and the third interface is displayed according to the contracted verification method information, including: Sending a fifth request to the server, wherein the fifth request is used to request the server to send a second verification code to the mobile phone number; A third interface is displayed, and a second verification code sent by the server is received. The third interface is used to input the second verification code.

9. The method according to claim 1, characterized in that Displaying a first interface based on the information of the contracted bank card and the contracted verification method information includes: Displaying a first interface based on the information of the contracted bank card, the first interface including the type, card number, status of the contracted bank card, and selection controls corresponding to each contracted bank card; In response to touching the selection control, a fourth interface is displayed in the first interface according to the signed verification method information, and the fourth interface is used to input verification information associated with the verification method information.

10. The method according to claim 3 or 8, characterized in that After sending the second request or the fifth request to the server, the method further includes: In response to the change operation of the mobile phone number, a fifth interface is displayed, wherein the fifth interface includes multiple contracted mobile phone numbers; In response to the selection of any one of the multiple contracted mobile phone numbers, a sixth request is sent to the server, and the sixth request is used to request the server to send a third verification code to the selected mobile phone number.

11. The method according to any one of claims 1 to 3, characterized in that In response to the bank card binding operation, a first request is sent to the bank's server, including: Displaying a sixth interface, the sixth interface including information of at least one type of bank and selection controls for each type of bank; In response to a touch on the bank selection control, displaying a seventh interface for inputting identity information of an authorized user; In response to inputting the identity information of the authorized user on the seventh interface, the first request is sent to the server of the selected bank.

12. The method according to claim 11, characterized in that The sixth interface is displayed, including: In response to the payment operation for the selected product, the sixth interface is displayed.

13. A bank card binding device, characterized in that: It includes a sending module, a receiving module, a display module and a processing module, wherein: The sending module is configured to, in response to a bank card binding operation, send a first request to a server of a bank, wherein the first request is configured to obtain contract information between the authorized user and the bank; The receiving module is used to receive the contracted bank card information and / or contracted verification method information sent by the server, wherein the verification method information is used to indicate the method by which the bank authenticates the user; The display module is configured to display a first interface based on the information of the contracted bank card and / or the contracted verification method information; The processing module is used to bind the bank card in response to the interaction between the user and the first interface.

14. A terminal device, characterized in that: include: processor and memory; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory, so that the processor executes the bank card binding method according to any one of claims 1 to 12.

15. A computer-readable storage medium, characterized in that The computer-readable storage medium stores computer-executable instructions. When the processor executes the computer-executable instructions, the bank card binding method according to any one of claims 1 to 12 is implemented.

16. A computer program product, characterized in that The invention comprises a computer program, which, when executed by a processor, implements the bank card binding method according to any one of claims 1 to 12.

Images