Information query method, device and equipment and computer readable storage medium

Abstract

The application discloses an information query method and device, equipment and a computer readable storage medium. The information query method comprises the following steps: obtaining user identity information corresponding to a login account in a target application program; receiving a first input of a user for querying account information; in response to the first input, sending an information query request to an application server, wherein the user identity information is included in the information query request, the information query request is used for instructing the application server to query account information corresponding to a payment account opened by the user in multiple payment institutions according to the user identity information, and the account information comprises at least one of an account number, balance information and bill information of the payment account; receiving the account information sent by the application server; and displaying the account information. According to the embodiment of the application, the operation process of the user for querying the payment account information can be simplified, and the user experience is improved.

Description

TECHNICAL FIELD

[0001] The present application belongs to the technical field of finance, and particularly relates to an information query method and device, equipment and a computer readable storage medium. BACKGROUND

[0002] With more and more financial institutions, users have more and more payment accounts opened in different financial institutions. Some payment accounts are forgotten by users after being opened, and even used by illegal persons for other illegal activities, affecting the credit value of users. Therefore, how to provide convenient payment account management services for users has become a problem to be solved.

[0003] Generally, if a user wants to find out the related information of all payment accounts in his / her name, he / she needs to log in to the website or App (Application) of the financial institution corresponding to each payment account to obtain the information of the corresponding payment account. In this way, if the user has opened too many payment accounts or has forgotten the existence of some payment accounts, the process of the query operation will be too complex and tedious. SUMMARY

[0004] The embodiments of the present application provide an information query method, device, equipment and computer readable storage medium, which can simplify the operation process of the user to query the payment account information and improve the user experience.

[0005] In a first aspect, the embodiments of the present application provide an information query method applied to a terminal device, which comprises:

[0006] obtaining user identity information corresponding to a login account in a target application program;

[0007] receiving a first input of a user for querying account information;

[0008] in response to the first input, sending an information query request to an application server, wherein the information query request comprises the user identity information, and the information query request is used to instruct the application server to query account information corresponding to payment accounts opened by the user in a plurality of payment institutions according to the user identity information, and the account information comprises at least one of an account number, balance information and bill information of the payment account;

[0009] receiving the account information sent by the application server;

[0010] displaying the account information.

[0011] In a second aspect, the embodiments of the present application provide an information query method applied to an application server, which comprises:

[0012] receive an information query request sent by a terminal device, wherein the information query request comprises user identity information corresponding to a login account in a target application program;

[0013] in response to the information query request, query account information corresponding to a payment account opened by the user in a plurality of payment institutions according to the user identity information, wherein the account information comprises at least one of an account number, balance information and billing information of the payment account;

[0014] send the account information to the terminal device.

[0015] In a third aspect, an embodiment of the present application provides an information query device applied to a terminal device, and the device comprises:

[0016] an identity obtaining module configured to obtain user identity information corresponding to a login account in a target application program;

[0017] a first receiving module configured to receive a first input of the user for querying account information;

[0018] a request sending module configured to, in response to the first input, send an information query request to an application server, wherein the information query request comprises the user identity information, and the information query request is used to instruct the application server to query account information corresponding to a payment account opened by the user in a plurality of payment institutions according to the user identity information, and the account information comprises at least one of an account number, balance information and billing information of the payment account;

[0019] an information receiving module configured to receive the account information sent by the application server;

[0020] an information displaying module configured to display the account information.

[0021] In a fourth aspect, an embodiment of the present application provides an information query device applied to an application server, and the device comprises:

[0022] a request receiving module configured to receive an information query request sent by a terminal device, wherein the information query request comprises user identity information corresponding to a login account in a target application program;

[0023] an information querying module configured to, in response to the information query request, query account information corresponding to a payment account opened by the user in a plurality of payment institutions according to the user identity information, wherein the account information comprises at least one of an account number, balance information and billing information of the payment account;

[0024] an information sending module configured to send the account information to the terminal device.

[0025] In a fifth aspect, an electronic device is provided, and the electronic device includes a processor and a memory storing computer program instructions.

[0026] The processor, when executing the computer program instructions, implements the steps of the information query method according to any one of the embodiments of the first aspect.

[0027] In a sixth aspect, a computer readable storage medium is provided, and the computer readable storage medium stores computer program instructions. When the computer program instructions are executed by a processor, the steps of the information query method according to any one of the embodiments of the first aspect are implemented.

[0028] The information query method, device, electronic device and computer readable storage medium provided in the embodiments of the present application can obtain the user identity information of the login account in the target application program, and then send an information query request to the application server by using the user identity information when the user triggers a query operation, so that the application server queries the account information corresponding to the payment accounts opened by the user in multiple payment institutions according to the user identity information, and then displays at least one of the account number, balance information and bill information of the multiple payment accounts corresponding to different payment institutions on the terminal device. In this way, the function of one-key query of multiple payment account information can be realized. In the case that the user has opened too many payment accounts or has forgotten the existence of some payment accounts, the payment account information under the user can also be quickly queried by one-key query, the user operation process required when the user queries the payment account is simplified, and the user experience is improved. BRIEF DESCRIPTION OF DRAWINGS

[0029] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required to be used in the embodiments of the present application will be briefly introduced. For those skilled in the art, other drawings can also be obtained without creative labor on the premise of these drawings.

[0030] Figure 1 is an architecture diagram of an example of the information query system provided by the embodiments of the present application;

[0031] Figure 2 is a flowchart of an embodiment of the information query method provided by the first aspect of the present application;

[0032] Figure 3 is a schematic diagram of an example of the information query page provided by the embodiments of the present application;

[0033] Figure 4 is a schematic diagram of an example of the bank query page provided by the embodiments of the present application;

[0034] Figure 5FIG. 1 is a schematic diagram of an example of a protocol display page provided by an embodiment of the present application;

[0035] Figure 6 FIG. 2 is a schematic diagram of an example of an authorization prompt page provided by an embodiment of the present application;

[0036] Figure 7 FIG. 3 is a schematic diagram of an example of a payment password verification page provided by an embodiment of the present application;

[0037] Figure 8 FIG. 4 is a schematic diagram of an example of a face information collection page provided by an embodiment of the present application;

[0038] Figure 9 FIG. 5 is a schematic diagram of an example of an application feedback page provided by an embodiment of the present application;

[0039] Figure 10 FIG. 6 is a schematic diagram of an example of a query record page provided by an embodiment of the present application;

[0040] Figure 11 FIG. 7 is a schematic diagram of another example of a query record page provided by an embodiment of the present application;

[0041] Figure 12 FIG. 8 is a schematic diagram of an example of a report details page provided by an embodiment of the present application;

[0042] Figure 13 FIG. 9 is a flowchart of another embodiment of the information query method provided by the first aspect of the present application;

[0043] Figure 14 FIG. 10 is a schematic diagram of an example of an authentication prompt interface provided by an embodiment of the present application;

[0044] Figure 15 FIG. 11 is a schematic diagram of an example of a non-support query prompt interface provided by an embodiment of the present application;

[0045] Figure 16 FIG. 12 is a flowchart of yet another embodiment of the information query method provided by the first aspect of the present application;

[0046] Figure 17 FIG. 13 is a schematic diagram of an example of a message prompt page provided by an embodiment of the present application;

[0047] Figure 18 FIG. 14 is a schematic diagram of an example of a report details page displaying part of information provided by an embodiment of the present application;

[0048] Figure 19 FIG. 15 is a schematic diagram of an example of a point use prompt interface provided by an embodiment of the present application;

[0049] Figure 20FIG. 1 is a schematic diagram of an example of a payment success feedback interface provided by an embodiment of the present application;

[0050] Figure 21 FIG. 2 is a schematic diagram of an example of a mailbox address input page provided by an embodiment of the present application;

[0051] Figure 22 FIG. 3 is a schematic diagram of an example of a mailbox address confirmation page provided by an embodiment of the present application;

[0052] Figure 23 FIG. 4 is a schematic diagram of an example of a feedback information prompt page provided by an embodiment of the present application;

[0053] Figure 24 FIG. 5 is a schematic diagram of another example of a query record page provided by an embodiment of the present application;

[0054] Figure 25 FIG. 6 is a schematic diagram of still another example of a query record page provided by an embodiment of the present application;

[0055] Figure 26 FIG. 7 is a flowchart of an embodiment of an information query method provided by the second aspect of the present application;

[0056] Figure 27 FIG. 8 is a flowchart of an example of a bank card-based information query method provided by an embodiment of the present application;

[0057] Figure 28 FIG. 9 is a structural schematic diagram of an embodiment of an information query device provided by the third aspect of the present application;

[0058] Figure 29 FIG. 10 is a structural schematic diagram of an embodiment of an information query device provided by the fourth aspect of the present application;

[0059] Figure 30 FIG. 11 is a structural schematic diagram of an embodiment of an electronic device provided by the present application. DETAILED DESCRIPTION

[0060] The features and exemplary embodiments of the various aspects of the present application will be described in detail below, in order to make the purposes, technical solutions and advantages of the present application more clear and apparent, the present application will be further described in detail below with reference to the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are only intended to explain the present application, but not to limit the present application. The present application can be implemented without some of these specific details by those skilled in the art. The following description of the embodiments is only to provide a better understanding of the present application by showing examples of the present application.

[0061] It should be noted that, in this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising..." does not exclude the presence of additional identical elements in the process, method, article, or apparatus that includes said element.

[0062] Currently, the industry lacks a unified tool for querying payment account information. If users need to obtain account information for payment accounts opened with different payment institutions, they need to log in to each payment institution's website or app to view it.

[0063] To address the problems of existing technologies, embodiments of this application provide an information query method, apparatus, device, and computer-readable storage medium. This information query method can be applied to scenarios involving querying payment account information from different payment institutions. The system architecture applicable to the information query method provided in this application embodiment is described below.

[0064] Figure 1 This is an example architecture diagram of an information query system to which the information query method provided in this application is applicable.

[0065] like Figure 1 As shown in the diagram, the architecture may include at least one terminal device 10, an application server 11, and at least one institutional server 12. The terminal device 10 has a client application for the target application installed, the application server 11 includes a server corresponding to the target application, and the institutional server 12 includes a backend server for a payment institution. Here, the target application may be an application that supports querying information from multiple payment accounts.

[0066] In addition, the application server 11 can establish a communication connection and exchange information with at least one terminal device 10 via a network, and the application server 11 can also establish a communication connection and exchange information with at least one institutional server 12 via a network. The terminal device 10 can be a mobile phone, tablet computer, all-in-one machine, or other device with communication capabilities, or it can be a device simulated by a virtual machine or simulator. The application server 11 and the institutional server 12 can be cloud servers or server clusters, or other devices with storage and computing capabilities.

[0067] In the embodiment of the present application, the terminal device 10 acquires user identity information corresponding to a login account in a target application program; receives a first input of a user for querying account information; in response to the first input, the application server 11 sends an information query request, and the application server 11 responds to the information query request by querying account information corresponding to a payment account opened by the user in a plurality of payment institutions according to the user identity information; the terminal device 10 receives the account information sent by the application server 11; and displays the account information. Specifically, the application server 11 responds to the information query request by querying the account information corresponding to the payment account opened by the user in the plurality of payment institutions according to the user identity information, which can include: the application server 11 sends an account query request to a plurality of institution servers 12 corresponding to the payment institutions respectively, so as to query the account identifier corresponding to the payment account opened by the user through the institution servers 12 according to the user identity information; the application server 11 receives the account identifier sent by the institution server 12; and calls a preset query interface to query the balance information and the billing information corresponding to the payment account according to the account identifier.

[0068] In this way, the embodiment of the present application can query the account information of all payment accounts under the user name through one-key query, which can simplify the operation process of the user for querying the account information and improve the user experience.

[0069] It should be noted that the payment account involved in the embodiment of the present application includes but is not limited to a bank account and a non-bank account. The bank account can be a bank card, for example, and the non-bank account can be a mobile wallet or other account with payment function.

[0070] According to the above architecture, the information query method provided by the embodiment of the present application will be described in detail. Figures 2-26 The information query method provided by the embodiment of the present application will be described in detail.

[0071] Figure 2 Fig. 1 shows a flowchart of an embodiment of the information query method provided by the present application, which can be applied to the terminal device 10 in the system 100. Figure 1

[0072] As shown in Fig. 1, the information query method can specifically include the following steps: Figure 2

[0073] S210, acquiring user identity information corresponding to a login account in a target application program;

[0074] S220, receiving a first input of a user for querying account information;

[0075] ​​S230, in response to the first input, sending an information query request to the application server, wherein the user identity information is included in the information query request, and the information query request is used to instruct the application server to query account information corresponding to payment accounts opened by the user in multiple payment institutions according to the user identity information, the account information including at least one of the account number, balance information and billing information of the payment account;

[0076] S240, receiving the account information sent by the application server;

[0077] S250, displaying the account information.

[0078] Thus, by obtaining the user identity information of the login account in the target application program, and then sending an information query request to the application server using the user identity information when the user triggers the query operation, the application server queries the account information corresponding to the payment accounts opened by the user in multiple payment institutions according to the user identity information, and then displays at least one of the account number, balance information and billing information of the multiple payment accounts corresponding to different payment institutions on the terminal device. In this way, the function of one-key query of multiple payment account information can be realized. In the case where the user has opened too many payment accounts or has forgotten the existence of some payment accounts, the payment account information under the user can also be quickly queried through one-key query, simplifying the user operation process required when the user queries the payment account and improving the user experience.

[0079] The specific implementation of each step will be described below.

[0080] In some embodiments, in S210 and S220, the first input can be a click input of the user on the information query button displayed in the information query page of the target application program, to trigger the start of the account information query process. In addition, the user identity information can be information that can represent the identity of the user, including but not limited to name, mobile phone number, certificate type, certificate number, etc. The user identity information can be obtained first after starting the target application program, and of course, it can also be displayed on the page displayed after starting, so as to be confirmed by the user.

[0081] Taking a bank card as an example, in some specific examples, the user enters the information query page as shown in Figure 3 after starting the target APP, and obtains and displays the user identity information 32 pre-stored or filled in real time by the current APP login account in the information query page. The user can start the account information query process by clicking the "apply query" button 31 displayed in the information query page, and upload the user identity information to the application server as the basis for querying the payment account.

[0082] In some embodiments, in S230, the information query request can carry the user identity information corresponding to the currently logged-in account, so that the application server can query the account information of the payment account according to the user identity information carried in the information query request after receiving the information query request.

[0083] In addition, in order to improve the flexibility of account information query, the user can select the account information of the payment account opened by the user in which payment institution. In some embodiments, before S210, the information query method provided by the embodiments of the present application can further include:

[0084] displaying the institution information corresponding to a plurality of payment institutions;

[0085] receiving a second input of the user selecting the institution information corresponding to the target payment institution from the plurality of payment institutions.

[0086] Based on this, S230 can specifically include:

[0087] In response to the second input, sending a target information query request for the target payment institution to the application server, wherein the target information query request is used to instruct the application server to query the account information corresponding to the payment account opened by the user in the target payment institution according to the user identity information.

[0088] Here, the displayed institution information can include the institution name, institution icon, etc. For example, the institution name and icon corresponding to a plurality of selectable payment institutions can be displayed on the institution query page of the target application program for the user to select. In addition, the target information query request can carry the institution information of the target payment institution.

[0089] Taking a bank card as an example, in some specific examples, the user can click the custom selection button 33 in the information query page as shown in Figure 3 to jump to the bank query page as shown in Figure 4 to query and select the banks whose card information needs to be queried, and then send the query request for the selected banks to the application server, so that the application server can query the number, balance, bill, etc. of all bank cards handled by the user in these banks.

[0090] In this way, by selectively querying the account information of the payment institution, the flexibility of the account information query can be improved, and the personalized query experience of the user can be improved.

[0091] In addition, in order to improve the security of account information query, in some embodiments, before S210, the information query method provided by the embodiments of the present application can further include:

[0092] displaying user authorization prompt information.

[0093] Based on this, the above S230 can specifically include:

[0094] In the case of user authorization, the information query request is sent to the application server.

[0095] Here, the authorization prompt information can be information for prompting the user to perform an authorization operation, where the authorization operation can be an operation of authorizing the sending of user identity information to each institution server for account information query.

[0096] Taking a bank card as an example, in some specific examples, the authorization prompt information 34 can be displayed in the information query page as shown in FIG. 13A, and when the user clicks on the “Personal Account Query Service Agreement”, the user can be redirected to the display page as shown in FIG. 13B to display the content of the agreement, and the user can authorize by clicking the agree button. In addition, the user can also authorize by clicking the selection control corresponding to the authorization prompt information 34 in the information query page. Figure 3 Figure 5

[0097] In another specific example, in the case where the user does not authorize, if the user directly clicks the “Apply for Query” button 31 in the information query page as shown in FIG. 14A, the authorization prompt information as shown in FIG. 14B can be popped up, and the user can authorize by clicking the agree authorization button, and then send an information query request to the application server, so that the application server queries the corresponding account information from each institution using the authorized user identity information. Figure 3 Figure 6

[0098] In this way, by authorizing the user and then performing the corresponding account query operation, the security of the account information query process can be improved, and the user's personal privacy can be protected.

[0099] In addition, in order to ensure that the information query operation is initiated by the user himself / herself, in some embodiments, after the above S230, the information query method provided by the embodiments of the present application can further include:

[0100] Receiving an identity information collection request sent by the application server;

[0101] In response to the identity information collection request, collecting second identity information input by the user, where the second identity information includes at least one of face information and a payment password corresponding to a login account;

[0102] Sending the second identity information to the application server to enable the application server to verify the identity of the user according to the second identity information, and in the case where the verification is passed, query the account information corresponding to the payment accounts opened by the user in multiple payment institutions according to the user identity information.

[0103] ​​​​For example, after the application server receives an information query request, it can initiate user authentication. After receiving the request, the terminal device can display, as shown below. Figure 7 The payment password verification page shown allows users to enter the payment password associated with their currently logged-in account. Additionally, it can also display... Figure 8 The facial recognition data collection page shown is for real-time collection of user facial information. After the user enters their payment password or after facial information collection, a screen like the one shown will appear. Figure 9 The feedback page shown indicates that the user's application has been successful.

[0104] Thus, by verifying the user's payment password and face before the application server formally submits the information query request, it can be ensured that the user is the one initiating the information query operation, thereby improving the security of the account information query process.

[0105] In some implementations, in steps S240 and S250, after the application server retrieves the account information of multiple payment accounts corresponding to the user's identity information, it can send this account information to the requesting terminal device. The account information can be a personal account report generated by the server after aggregating information from multiple payment accounts. This personal account report may include the account numbers, number of payment accounts, balance, and bills for each payment account opened by the user at different payment institutions. After receiving the account information sent by the server, the terminal device can display the account information on the settings page of the target application on the terminal device.

[0106] For example, taking a bank card as the payment account, in some specific cases, after the user clicks to apply for an inquiry but before the server returns the account information, it is possible to... Figure 10 The query record page shown displays the query progress for each account information report. Once the account information is received, you can view it as follows: Figure 11 The query record page shows the account information reports found. Users can click the "View Report" button corresponding to the account information report they want to view to trigger a redirect to the page. Figure 12 View the full report on the page shown. Alternatively, users can click on the following... Figure 10 The "New Query" button on the query records page, as shown, leads to... Figure 3 The information query page shown.

[0107] In addition, to improve the security of login accounts, in some implementations, before the above-mentioned S210, such as Figure 13 As shown, the information query method provided in this application embodiment may further include steps S201-S209, which will be explained in detail below.

[0108] S201, in response to a starting operation of the target application program, sending an authentication query request to the application server, the authentication query request being used to instruct the application server to query whether the login account has been real-name authenticated, to obtain a first query result.

[0109] Exemplarily, after the target application program is started, the terminal device can send a user identifier of the login account to the application server, the application server can query whether the login account has been real-name authenticated according to the user identifier, to obtain a first query result, and feed back the result to the terminal device.

[0110] S202, receiving the first query result sent by the application server.

[0111] S203, whether the first query result is that the login account has been real-name authenticated; if yes, performing S208; if no, performing S204.

[0112] Exemplarily, the terminal device can determine which page to jump to for display according to the first query result. For example, in the case of not being real-name authenticated, an information collection interface can be displayed to perform user identity authentication, and in the case of being real-name authenticated, an information query page as shown in Figure 3 may be jumped to.

[0113] S204, collecting first identity information input by the user, wherein the first identity information includes a user name, an ID number and face information.

[0114] Here, in the case of the login account being an un-authenticated account, a pop-up window can prompt prompt information as shown in Figure 14 “complete authentication first and then query account information”, the user clicks the “identity authentication” button, jumps to the information collection page, and then the user can input the name, ID number and complete face image collection in the information collection page.

[0115] S205, sending the first identity information to the application server, so that the application server performs identity authentication on the user according to the first identity information, to obtain an identity authentication result.

[0116] Exemplarily, the terminal device uploads the collected information of the three elements of the name, ID number and face image to the application server, and then the application server sends the above three elements to an authoritative data source for comparison, if the comparison is consistent, the identity authentication is passed, and if the comparison is inconsistent, the identity authentication is not passed.

[0117] S206, receiving the identity authentication result sent by the application server.

[0118] S207, whether the identity authentication result is that the authentication is passed; if yes, performing S208; if no, performing S209.

[0119] S208, display an information query page.

[0120] For example, if the identity authentication is passed, the information query page as shown in Figure 3 may be jumped to.

[0121] S209, display a prompt information of unsupported query.

[0122] For example, if the identity authentication is not passed, the prompt information of unsupported query can be displayed to prompt the user that the account information query cannot be currently performed. Of course, the user can also be guided to enter the real-name authentication operation process to facilitate the real-name authentication of the user.

[0123] In this way, since the real-name authentication operation process is relatively complex, the identity authentication can be rapidly completed by the user in the case of no real-name authentication by using the "name + ID number + face" three elements for identity authentication, and the account information query interface can be safely opened. In this way, the user identity authentication efficiency can be improved while ensuring the security of the account information query.

[0124] In addition, if the user is a non-ID card registered real-name user or a domestic prepaid card user, and an overseas user, a pop-up window as shown in Figure 15 is prompted after entering the information query page, and the user can close the current account information query interface by clicking the displayed "back" button.

[0125] In addition, since the purposes of different users entering the target application program are different, some are to initiate a new account information query process, and some are to view the account information query result that has been applied. Based on this, in some embodiments, after S202, the information query method provided by the embodiment of the present application can further include:

[0126] receiving a second query result sent by the application server, wherein the second query result is a query result obtained by the application server querying whether there is a historical query record of the login account within a preset time period;

[0127] in the case that the first query result is that the login account has been real-name authenticated, and the second query result is that there is a historical query record, displaying a query record page, wherein the query record page includes at least one historical query record;

[0128] in the case that the first query result is that the login account has been real-name authenticated, and the second query result is that there is no historical query record, displaying an information query page.

[0129] Here, the preset time period can be configured by the background staff according to the actual situation, for example, it can be configured as the last 365 days.

[0130] In some embodiments, after receiving the authentication query request, the application server can further query, according to the user identifier of the login account, whether the login account has applied for account information query in the last 365 days, i.e., whether there is a query record in the last 365 days. If the login account has been real-name authenticated and there is no query record in the last 365 days, the information query page as shown in FIG. 6A can be directly entered; if the login account has been real-name authenticated and there is a query record in the last 365 days, it means that the user is most likely to view the account information query result that has been applied for, and thus the query record page as shown in FIG. 6B can be entered. Figure 3 Figure 11

[0131] In this way, by determining whether the user has queried the account information recently to trigger the display of different pages, the user can be facilitated to perform the account information query or viewing operation, the operation process required by the user can be reduced as much as possible, and thus the user experience can be improved.

[0132] In addition, in order to notify the user to view in time when the account information is queried, in some embodiments, as shown in FIG. 25, the above S250 can specifically include steps S2501-S2503. Details are explained below. Figure 16

[0133] S2501, display viewing prompt information corresponding to the account information.

[0134] Here, the viewing prompt information can be prompt information sent through a short message, an APP in-app message, etc. Taking the account information queried as bank account information as an example, the APP in-app message can be the prompt message 171 displayed in the message page as shown in FIG. 6C. Figure 17

[0135] S2502, receive a fourth input of the user viewing the account information.

[0136] Here, the fourth input can be an input of the user clicking a target application icon to start a target application, can be an input of the user clicking into the account information query function from other pages in the target application, or can be an input of the user clicking an information viewing link provided in the viewing prompt information, which is not limited herein.

[0137] S2503, display the account information in response to the fourth input.

[0138] Exemplarily, after the terminal device receives the account information, the user enters the target application again, can directly enter the query record page as shown in FIG. 6B, and display a “view report” button, and the user can display the account information as shown in FIG. 6A by clicking the “view report” button. Figure 11 Figure 12 Exemplarily, after the terminal device receives the account information, the user enters the target application again, can directly enter the query record page as shown in FIG. 6B, and display a “view report” button, and the user can display the account information as shown in FIG. 6A by clicking the “view report” button.​​​​​

[0139] In this way, by displaying the viewing prompt information, the user can be notified to view the account information in time after the terminal device queries the account information, thereby ensuring the timeliness of the account information.

[0140] In addition, a membership system can be used to divide different account information viewing rights and interests levels by using member points. In some embodiments, the S2503 can specifically include:

[0141] In response to the fourth input, an information viewing request is sent to the application server, where the information viewing request is used to instruct the application server to call a point payment interface of the member management system to deduct points required for viewing the account information from points corresponding to the login account, and obtain a payment result;

[0142] The payment result sent by the application server is received;

[0143] In the case where the payment result is a payment success, the account information is displayed;

[0144] In the case where the payment result is a payment failure, part of the account information is displayed.

[0145] For example, after the user clicks to view the account information, the application server can interact with the member management system according to the information viewing request sent by the terminal device to determine whether the login account can complete and has completed the point payment process, so that the terminal device displays information content with different display degrees for the user on the account information detail page according to different determination results.

[0146] In some specific examples, if the point payment is successful, all account information as shown in Figure 12 is displayed; if the point payment fails, part of the account information as shown in Figure 18 is displayed, where the account balance, bill, and other information are hidden. If the user clicks the detail button 181, the point use prompt information as shown in Figure 19 is displayed, and in the case where the user clicks the confirmation button, the deduction process of the points of the login account can be initiated. The specific deduction process can be referred to the above description, and will not be described here. In the case where the point payment is successful, the feedback information as shown in Figure 20 is displayed, and in the case where the user clicks the back button, all account information as shown in Figure 12 is displayed.

[0147] In this way, by using the member point system, the corresponding points can be deducted when the user views the queried account information details, thereby realizing the division of different account information viewing rights and interests levels and prompting the user to open a membership.

[0148] Of course, the integral payment switch can also be set in the background, and the background staff can set whether to view the detailed content of the account information selectively through the integral payment switch by integral payment, so that the staff can change the corresponding account information display mechanism according to the actual operation strategy.

[0149] In addition, in order to ensure the security of the user when viewing the account information, in some embodiments, after the step of sending the information viewing request to the application server, the information query method provided by the embodiments of the application can further include:

[0150] receiving an information verification request sent by the application server;

[0151] collecting verification information input by the user in response to the information verification request;

[0152] sending the verification information to the application server, so that the application server verifies the identity of the user according to the verification information, and performs a payment operation on the integral corresponding to the logged-in account in the case of verification, and obtains a payment result.

[0153] Exemplarily, after the user triggers to enter the account information viewing process, the application server can send an information verification request to the terminal device, instructing the terminal device to collect corresponding verification information for user identity verification, so as to ensure that the user viewing the account information at this time is the legitimate user himself. The verification information input by the user includes but is not limited to the payment password of the logged-in account, the real-time collected face image, etc.

[0154] In this way, by verifying the identity of the user before performing the integral payment, it can be ensured that the user operating at this time is the legitimate user himself, and thus the security of the user when viewing the account information is ensured.

[0155] In addition, in the report details page as shown in Figure 12 , the user can also jump to the input page as shown in Figure 21 by clicking "save to mailbox", so that the user inputs the mailbox address based on the page. After the user inputs and submits, the pop-up window displays the mailbox address confirmation information as shown in Figure 22 , and after the user clicks the "confirm and send" button, the terminal device sends the mailbox address input by the user to the application server, so that the server sends the report to the mailbox after encryption. After the terminal device receives the feedback information of the application server that the sending is completed, it can jump to the information prompt page as shown in Figure 23 , and display the report password. Of course, the user can also view the report password through the payment password verification in the query record page as shown in Figure 24 .

[0156] In addition, the account information expiration deletion mechanism is further provided in the embodiment of the present application, the application server deletes the account information which is queried and exceeds the preset period, and does not remain for the overage, so as to ensure the timeliness of the account information query and save the memory resources. Of course, the application server can send the account information to the user mailbox before deleting the expired account information, so as to enable the user to backup and archive. On the terminal device, the user can display the related information of the expired account information report through the query record page as shown in Figure 24 and Figure 25 .

[0157] Figure 26 The flow diagram of an embodiment of the information query method provided by the present application is shown, and the information query method can be applied to the application server 11 in Figure 1 .

[0158] As shown in Figure 26 , the information query method can specifically include the following steps:

[0159] S2610, receiving the information query request sent by the terminal device, wherein the user identity information corresponding to the login account in the target application program is included in the information query request;

[0160] S2620, in response to the information query request, querying the account information corresponding to the payment account opened by the user in the plurality of payment institutions according to the user identity information, wherein the account information includes at least one of the account number, the balance information and the bill information of the payment account;

[0161] S2630, sending the account information to the terminal device.

[0162] In this way, the application server queries the account information corresponding to the payment account opened by the user in the plurality of payment institutions according to the user identity information uploaded by the terminal device, and the account information includes at least one of the account number, the balance information and the bill information, and then feeds back to the terminal device for display, so that the one-key query of the plurality of payment account information can be realized, and in the case that the payment account opened by the user is too much or the user has forgotten the existence of some payment account, the payment account information under the user name can also be quickly found through the one-key query, the user operation process required when the user queries the payment account is simplified, and the user experience is improved.

[0163] The specific implementation mode of each step is introduced below.

[0164] In some embodiments, in S2610 above, the information query request can be a request carrying the user identity information sent by the terminal device after receiving the first input of the user for querying the account information and obtaining the user identity information corresponding to the login account in the target application. For details, refer to the related description above, which will not be repeated here.

[0165] In some embodiments, in S2620 and S2630 above, the application server can call the pre-configured payment institution links, upload the user identity information on each link, and trigger each payment institution to return the related information of all payment accounts opened by the user through a preset interface.

[0166] In addition, the application server can also simulate the user's behavior of querying the balance or bill, and poll each payment account balance or bill information through the full-channel system.

[0167] Based on this, in some embodiments, S2620 above can specifically include:

[0168] sending an account query request to the institution server corresponding to each payment institution, wherein the account query request is used to instruct the institution server to query the account identifier corresponding to the payment account opened by the user according to the user identity information;

[0169] receiving the account identifier sent by the institution server;

[0170] calling a preset query interface to query the balance information and bill information corresponding to the payment account according to the account identifier.

[0171] Here, the account identifier can be an account number, an identification code, or other information that can uniquely represent the payment account. The preset query interface can be an interface set in the full-channel system for polling each payment account balance or bill information from each payment institution. In addition, the account query request can carry the user identity information, so that the institution server of each payment institution can query the related information of the payment account opened by the user in the institution according to the user identity information. The related information of the payment account includes but is not limited to the account identifier, such as a bank card number.

[0172] In addition, after receiving the account identifier fed back by the institution server of each payment institution, the application server can aggregate information according to the account identifier, such as calculating the number of payment accounts owned by the user in each payment institution.

[0173] In this way, through the above query process, the application server can realize polling of the payment account information owned by the user in each payment institution, and obtain detailed information including the balance and the bill, thereby simplifying the complex operation process required by the user to query each payment account, and realizing one-key query of the detailed information of each payment account.

[0174] In addition, in some embodiments, after S2630, the information query method provided by the embodiment of the application can further include:

[0175] receiving an information viewing request sent by the terminal device;

[0176] In response to the information viewing request, calling an integral payment interface of the member management system to deduct the integral required for viewing the account information from the integral corresponding to the login account, and obtaining a payment result;

[0177] sending the payment result to the terminal device, so that the terminal device displays the account information according to the payment result.

[0178] For example, in the case where the member management system successfully deducts the corresponding integral, the payment result obtained can be payment success, thereby making the terminal device display all the account information; in the case where the member management system fails to deduct the corresponding integral due to insufficient integral of the login account or the like, the payment result obtained can be payment failure, thereby making the terminal device display part of the account information.

[0179] In this way, by deducting the corresponding integral, the differential display of the account information can be realized, thereby promoting the user to actively participate in the member recharge, integral accumulation and the like.

[0180] In order to better describe the whole scheme, based on the above embodiments, taking the payment account as a bank card as an example, some specific examples are given. For example, as shown in the information query method flowchart. Figure 27 The information query method is completed by the interaction between the six ends of the user, the terminal device, the application server, the institution server, the full-channel system and the member management system.

[0181] It should be noted that the application scenarios described in the above embodiments of the application are for more clearly illustrating the technical solutions of the embodiments of the application, and do not constitute a limitation on the technical solutions provided by the embodiments of the application. It can be known by those skilled in the art that, with the appearance of new application scenarios, the technical solutions provided by the embodiments of the application are also applicable to similar technical problems.

[0182] Based on the same inventive concept, the application further provides an information query device. The device will be described in detail in combination with Figure 28

[0183] Figure 28 ​A structural diagram of an embodiment of an information query device provided in the present application is shown. The information query device can be applied to Figure 1 a terminal device 10 in

[0184] As shown in Figure 28 , the information query device 2800 can include:

[0185] an identity acquisition module 2801 configured to acquire user identity information corresponding to a login account in a target application program;

[0186] a first receiving module 2802 configured to receive a first input of a user for querying account information;

[0187] a request sending module 2803 configured to, in response to the first input, send an information query request to an application server, wherein the information query request includes the user identity information, and the information query request is used to instruct the application server to query account information corresponding to payment accounts opened by the user in a plurality of payment institutions according to the user identity information, and the account information includes at least one of an account number, balance information, and bill information of the payment accounts;

[0188] an information receiving module 2804 configured to receive the account information sent by the application server;

[0189] an information display module 2805 configured to display the account information.

[0190] The information query device 2800 is described in detail as follows:

[0191] In some embodiments, the information query device 2800 further includes:

[0192] a first sending module configured to, before receiving a first input of a user for querying account information, in response to a starting operation of the target application program, send an authentication query request to the application server, wherein the authentication query request is used to instruct the application server to query whether the login account has been real-name authenticated, and obtain a first query result;

[0193] a first receiving module configured to receive the first query result sent by the application server;

[0194] a first acquisition module configured to, in a case where the first query result is that the login account has not been real-name authenticated, acquire first identity information input by the user, wherein the first identity information includes a user name, an ID number, and face information;

[0195] a second sending module, configured to send the first identity information to the application server, so that the application server performs identity authentication on the user according to the first identity information, and obtains an identity authentication result;

[0196] a second receiving module, configured to receive the identity authentication result sent by the application server;

[0197] a first display module, configured to display an information query page in a case where the identity authentication result is authentication passed.

[0198] In some embodiments, the information query apparatus 2800 further includes:

[0199] a third receiving module, configured to receive a second query result sent by the application server after receiving the first query result sent by the application server, wherein the second query result is a query result obtained by the application server querying whether there is a historical query record of the login account within a preset time period;

[0200] a second display module, configured to display a query record page in a case where the first query result is that the login account has been real-name authenticated, and the second query result is that there is the historical query record, wherein the query record page includes at least one historical query record;

[0201] a third display module, configured to display the information query page in a case where the first query result is that the login account has been real-name authenticated, and the second query result is that there is no historical query record.

[0202] In some embodiments, the information query apparatus 2800 further includes:

[0203] a fourth receiving module, configured to receive an identity information collection request sent by the application server after sending an information query request to the application server;

[0204] a second collection module, configured to collect second identity information input by the user in response to the identity information collection request, wherein the second identity information includes at least one of face information and a payment password corresponding to the login account;

[0205] a third sending module, configured to send the second identity information to the application server, so that the application server verifies the identity of the user according to the second identity information, and queries account information corresponding to a payment account opened by the user in a plurality of payment institutions according to the user identity information in a case where the verification is passed.

[0206] In some embodiments, the information query apparatus 2800 further includes:

[0207] The fourth display module is configured to display institution information corresponding to a plurality of payment institutions before receiving a first input of the user for querying account information.

[0208] The fifth receiving module is configured to receive a second input of the user for selecting institution information corresponding to a target payment institution from the plurality of payment institutions.

[0209] The request sending module 2803 can be specifically configured to:

[0210] In response to the second input, send a target information query request for the target payment institution to the application server, where the target information query request is used to instruct the application server to query account information corresponding to a payment account opened by the user in the target payment institution according to the user identity information.

[0211] In some embodiments, the information querying apparatus 2800 further includes:

[0212] The fifth display module is configured to display user authorization prompt information before receiving a first input of the user for querying account information.

[0213] The request sending module 2803 can be specifically configured to:

[0214] In the case of user authorization, send the information query request to the application server.

[0215] In some embodiments, the information display module 2805 can specifically include:

[0216] The first display submodule is configured to display viewing prompt information corresponding to the account information.

[0217] The first receiving submodule is configured to receive a fourth input of the user for viewing the account information.

[0218] The second display submodule is configured to display the account information in response to the fourth input.

[0219] In some embodiments, the second display submodule can specifically include:

[0220] The first sending unit is configured to send an information viewing request to the application server in response to the fourth input, where the information viewing request is used to instruct the application server to call an integral payment interface of a member management system, deduct integral required for viewing the account information from integrals corresponding to the login account, and obtain a payment result.

[0221] The first receiving unit is configured to receive the payment result sent by the application server.

[0222] The first display unit is configured to display the account information when the payment result is a payment success.

[0223] The second display unit is configured to display part of the account information when the payment result is a payment failure.

[0224] In some embodiments, the second display sub-module further includes:

[0225] The second receiving unit is configured to receive an information verification request sent by the application server after sending an information query request to the application server.

[0226] The acquisition unit is configured to acquire verification information input by the user in response to the information verification request.

[0227] The second sending unit is configured to send the verification information to the application server, so that the application server verifies the identity of the user according to the verification information, and performs a payment operation on the integral corresponding to the login account for the account information in the case of verification success, to obtain a payment result.

[0228] Thus, by obtaining the user identity information of the login account in the target application program, and then sending an information query request to the application server using the user identity information when the user triggers a query operation, the application server queries the account information corresponding to the payment accounts opened by the user in multiple payment institutions according to the user identity information, and then displays at least one of the account number, balance information and bill information of the multiple payment accounts corresponding to different payment institutions on the terminal device. In this way, the function of one-key query of multiple payment account information can be realized, and in the case that the user has opened too many payment accounts or has forgotten the existence of some payment accounts, the payment account information under the user can also be quickly found through one-key query, simplifying the user operation process required when the user queries the payment account and improving the user experience.

[0229] Figure 29 An embodiment structure of the information query device provided by the present application is shown in the structural schematic diagram. The information query device can be applied to Figure 1 the application server 11.

[0230] As Figure 29 shown, the information query device 2900 can include:

[0231] The request receiving module 2901 is configured to receive an information query request sent by a terminal device, wherein the information query request includes user identity information corresponding to a login account in a target application program.

[0232] The information query module 2902 is configured to query, in response to the information query request, account information corresponding to payment accounts opened by the user at the plurality of payment institutions according to the user identity information, wherein the account information comprises at least one of an account number, balance information and billing information of the payment account.

[0233] The information sending module 2903 is configured to send the account information to the terminal device.

[0234] The information query device 2900 is described in detail as follows.

[0235] In some embodiments, the information query module 2902 can specifically comprise:

[0236] The sending sub-module is configured to send an account query request to the institution servers corresponding to the plurality of payment institutions respectively, wherein the account query request is used to instruct the institution servers to query account identifiers corresponding to payment accounts opened by the user according to the user identity information.

[0237] The receiving sub-module is configured to receive the account identifiers sent by the institution servers.

[0238] The query sub-module is configured to call a preset query interface to query the balance information and the billing information corresponding to the payment accounts according to the account identifiers.

[0239] In some embodiments, the information query device 2900 further comprises:

[0240] The first receiving module is configured to receive an information viewing request sent by the terminal device after the account information is sent to the terminal device.

[0241] The point deduction module is configured to call a point payment interface of a member management system to deduct points required for viewing the account information from points corresponding to the login account in response to the information viewing request, and obtain a payment result.

[0242] The result sending module is configured to send the payment result to the terminal device, so that the terminal device displays the account information according to the payment result.

[0243] Therefore, the application server queries the account information corresponding to the user's payment accounts opened with multiple payment institutions based on the user's identity information uploaded by the terminal device. The account information includes at least one of the following: number of accounts, balance information, and billing information. This information is then displayed to the terminal device, enabling a one-click query of multiple payment account information. Even if a user has opened too many payment accounts or has forgotten the existence of some payment accounts, they can quickly find the payment account information under their name through a one-click query, simplifying the user operation process required for querying payment accounts and improving the user experience.

[0244] Figure 30 A schematic diagram of the hardware structure of an embodiment of the electronic device provided in this application is shown.

[0245] The electronic device 3000 may include a processor 3001 and a memory 3002 storing computer program instructions.

[0246] Specifically, the processor 3001 may include a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits that can be configured to implement the embodiments of this application.

[0247] Memory 3002 may include mass storage for data or instructions. For example, and not limitingly, memory 3002 may include a hard disk drive (HDD), floppy disk drive, flash memory, optical disk, magneto-optical disk, magnetic tape, or Universal Serial Bus (USB) drive, or a combination of two or more of these. Where appropriate, memory 3002 may include removable or non-removable (or fixed) media. Where appropriate, memory 3002 may be internal or external to the integrated gateway disaster recovery device. In a particular embodiment, memory 3002 is non-volatile solid-state memory.

[0248] Memory may include read-only memory (ROM), random access memory (RAM), disk storage media devices, optical storage media devices, flash memory devices, and electrical, optical, or other physical / tangible memory storage devices. Therefore, typically, memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software including computer-executable instructions, and when the software is executed (e.g., by one or more processors), it is operable to perform the operations described with reference to the method according to one aspect of this application.

[0249] The processor 3001 implements the information query method in any of the above embodiments by reading and executing computer program instructions stored in the memory 3002.

[0250] In some examples, the electronic device 3000 can further include a communication interface 3003 and a bus 3010. As shown in the figure, the processor 3001, the memory 3002, and the communication interface 3003 are connected through the bus 3010 and complete communication with each other. Figure 30

[0251] The communication interface 3003 is mainly used to realize the communication between various modules, devices, units and / or equipment in the embodiments of the present application.

[0252] The bus 3010 includes hardware, software or both to couple components of the online data traffic billing device to each other. By way of example, and not limitation, the bus 3010 can include an accelerated graphics port (AGP) or other graphics bus, an enhanced industry standard architecture (EISA) bus, a front-side bus (FSB), a HyperTransport (HT) interconnect, an industry standard architecture (ISA) bus, an InfiniBand (IB) interconnect, a low pin count (LPC) bus, a memory bus, a Micro Channel Architecture (MCA) bus, a peripheral component interconnect (PCI) bus, a PCI-Express (PCI-X) bus, a serial advanced technology attachment (SATA) bus, a video electronics standards board (VLB) bus, or another suitable bus or a combination of two or more of these. Where appropriate, the bus 3010 can include one or more buses. Although the present application describes and illustrates a particular bus, the present application contemplates any suitable bus or interconnect.

[0253] By way of example, the electronic device 3000 can be a mobile phone, a tablet computer, a notebook computer, a palm computer, a vehicle-mounted electronic device, an ultra-mobile personal computer (UMPC), a netbook, or a personal digital assistant (PDA), etc.

[0254] The electronic device 3000 can execute the information query method in the embodiments of the present application, thereby realizing the information query method and device described in combination Figures 2 to 29 with the above embodiments.

[0255] ​In addition, in combination with the information query method in the above embodiments, the embodiments of the present application can provide a computer readable storage medium for implementation. The computer readable storage medium has computer program instructions stored thereon; the computer program instructions are executed by a processor to implement any one of the information query methods in the above embodiments. Examples of the computer readable storage medium include non-transitory computer readable storage media, such as a portable disc, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, etc.

[0256] It should be noted that the present application is not limited to the specific configurations and processes described above and shown in the drawings. For the sake of brevity, detailed descriptions of well-known methods are omitted. In the above embodiments, several specific steps are described and shown as examples. However, the method processes of the present application are not limited to the specific steps described and shown, and those skilled in the art can make various changes, modifications and additions, or change the order of the steps, after understanding the spirit of the present application.

[0257] The functional blocks shown in the structural block diagrams described above can be implemented as hardware, software, firmware or a combination thereof. When implemented in hardware, it can be, for example, an electronic circuit, an application specific integrated circuit (ASIC), appropriate firmware, a plug-in, a functional card, etc. When implemented in software, the elements of the present application are program or code segments used to perform the required tasks. The program or code segments can be stored in a machine readable medium or transmitted through a data signal carried in a carrier wave over a transmission medium or communication link. The "machine readable medium" can include any medium capable of storing or transmitting information. Examples of the machine readable medium include electronic circuits, semiconductor memory devices, ROM, flash memory, erasable ROM (EROM), floppy disks, CD-ROMs, optical disks, hard disks, optical fiber media, radio frequency (RF) links, etc. The code segments can be downloaded via a computer network such as the Internet, an intranet, etc.

[0258] It should also be noted that the exemplary embodiments mentioned in the present application describe some methods or systems based on a series of steps or devices. However, the present application is not limited to the order of the above steps, that is, the steps can be executed in the order mentioned in the embodiments, or in an order different from the embodiments, or several steps can be executed simultaneously.

[0259] The computer program instructions can also be loaded onto a computer, other programmable data processing apparatus, or other processing device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other processing device to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0260] The above only is a specific implementation of the present application, and those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process of the above-described system, module and unit can refer to the corresponding process in the foregoing method embodiments, which will not be described herein. It should be understood that the protection scope of the present application is not limited to this, and any person skilled in the art can easily think of various equivalent modifications or replacements within the technical range disclosed in the present application, and these modifications or replacements shall be covered within the protection scope of the present application.

Claims

1. An information query method, applied to a terminal device, characterized in that, include: Obtain the user identity information corresponding to the login account in the target application, wherein the target application is an application that supports querying information of multiple payment accounts; The system receives a first input from a user in the target application for querying account information, wherein the account information includes account information of all payment accounts corresponding to the user's identity information, and the first input is input by the user clicking the information query button displayed on the information query page of the target application; In response to the first input, an information query request is sent to the application server. The information query request includes the user's identity information. The information query request is used to instruct the application server to call a pre-configured payment institution link and send the user's identity information for each link. This triggers each payment institution to send back the account information of all payment accounts opened by the user through a preset interface. The account information includes at least one of the following: the number of accounts, balance information, and billing information of the payment accounts. The application server includes a server corresponding to the target application. Receive the account information sent by the application server; Display the account information; Before receiving the user's first input for querying account information, the method further includes: Displays information about multiple payment institutions; Receive a second input from the user, which selects the institution information corresponding to the target payment institution from the plurality of payment institutions; Sending the information query request to the application server includes: In response to the second input, a target information query request for the target payment institution is sent to the application server, wherein the target information query request is used to instruct the application server to query the account information corresponding to the payment account opened by the user in the target payment institution based on the user identity information; Before receiving the user's first input for querying account information in the target application, the method further includes: In response to the launch operation of the target application, if the first query result is that the login account has been verified with real name and the second query result is that there are historical query records, a query record page is displayed. The query record page includes at least one of the historical query records. The second query result is the query result obtained by the application server querying whether the login account has historical query records within a preset time period. If the first query result indicates that the login account has been verified with real name, and the second query result indicates that there is no historical query record, the information query page is displayed; The method further includes: When displaying the report details page corresponding to the account information, receive an instruction from the user to send the account information to the target email address; In response to the instruction, the target email address is sent to the application server, so that the application server sends the encrypted account information to the target email address; After receiving feedback from the application server indicating completion of the transmission, the system redirects to an information prompt page and displays the report password on the information prompt page. The application server is also used to, when it finds account information that has exceeded the preset period, first send the account information that has exceeded the preset period to the user's email address so that the user can back it up and archive it, and then delete the account information that has exceeded the preset period. The query record page displays the generation time of the personal account report corresponding to the account information that has exceeded the preset period. The query record page is also used by users to view the report password by verifying their payment password.

2. The method according to claim 1, characterized in that, Before receiving the user's first input for querying account information, the method further includes: In response to the launch operation of the target application, an authentication query request is sent to the application server. The authentication query request is used to instruct the application server to query whether the login account has been real-name authenticated and to obtain a first query result. Receive the first query result sent by the application server; If the first query result indicates that the login account is not real-name authenticated, the first identity information input by the user is collected, wherein the first identity information includes the user's name, ID number and facial information; Send the first identity information to the application server so that the application server can authenticate the user based on the first identity information and obtain the authentication result; Receive the authentication result sent by the application server; If the identity authentication result is successful, an information query page will be displayed.

3. The method according to claim 2, characterized in that, After receiving the first query result sent by the application server, the method further includes: Receive the second query result sent by the application server.

4. The method according to claim 1, characterized in that, After sending an information query request to the application server, the method further includes: Receive the identity information collection request sent by the application server; In response to the identity information collection request, the user inputs second identity information, wherein the second identity information includes at least one of facial information and payment password corresponding to the login account; The application server sends the second identity information to the application server so that the application server can verify the user's identity based on the second identity information. If the verification is successful, the application server queries the account information corresponding to the user's payment accounts opened at multiple payment institutions based on the user's identity information.

5. The method according to claim 1, characterized in that, Before receiving the user's first input for querying account information, the method further includes: Display user authorization prompt message; Sending the information query request to the application server includes: With user authorization, the information query request is sent to the application server.

6. The method according to claim 1, characterized in that, The display of the account information includes: Display viewing prompts corresponding to the account information; Receive the fourth input from the user to view the account information; In response to the fourth input, the account information is displayed.

7. The method according to claim 6, characterized in that, The response to the fourth input, displaying the account information, includes: In response to the fourth input, an information viewing request is sent to the application server, wherein the information viewing request is used to instruct the application server to call the points payment interface of the membership management system, deduct the points required to view the account information from the points corresponding to the login account, and obtain the payment result; Receive the payment result sent by the application server; If the payment result is successful, the account information will be displayed. If the payment result is a payment failure, partial information from the account information will be displayed.

8. The method according to claim 7, characterized in that, After sending an information viewing request to the application server, the method further includes: Receive the information verification request sent by the application server; In response to the information verification request, the verification information input by the user is collected; The verification information is sent to the application server so that the application server can verify the user's identity based on the verification information. If the verification is successful, the application server will perform a payment operation on the points corresponding to the logged-in account based on the account information to obtain a payment result.

9. An information query method, applied to an application server, characterized in that, The application server includes a server-side component corresponding to the target application, wherein the target application is an application that supports querying information from multiple payment accounts, and the method includes: The system receives an information query request sent by a terminal device. The information query request includes user identity information corresponding to a login account in a target application. The information query request is generated by the target application in response to a first input, which is a click input by the user on an information query button displayed on the target application's information query page. Before receiving the first input, the terminal device, in response to the launch operation of the target application, displays a query record page if the first query result indicates that the login account is verified with real-name authentication and the second query result indicates that a historical query record exists. It also displays the information query page if the first query result indicates that the login account is verified with real-name authentication and the second query result indicates that no historical query record exists. The query record page includes at least one historical query record. The second query result is the query result obtained by the application server querying whether the login account has a historical query record within a preset time period. In response to the information query request, the system queries the account information corresponding to the payment accounts opened by the user in multiple payment institutions, or the account information corresponding to the payment account opened by the user in the target payment institution, based on the user identity information. The account information includes at least one of the number of accounts, balance information, and billing information of the payment accounts. The account information includes the account information of all payment accounts corresponding to the user identity information. The target payment institution is the payment institution selected by the user from multiple payment institutions displayed in the target application. Send the account information to the terminal device; The step of querying the account information corresponding to the user's payment accounts opened with multiple payment institutions based on the user's identity information includes: Call the pre-configured payment institution link, send the user's identity information for each link, and trigger each payment institution to send back the account information of all payment accounts opened by the user through a preset interface; The method further includes: The terminal device receives a target email address sent by the terminal device, wherein the target email address is sent by the terminal device in response to the user's instruction to send the account information to the target email address when displaying the report details page corresponding to the account information; The encrypted account information is sent to the target email address, so that after the terminal device receives the feedback information that the sending is completed from the application server, it is redirected to the information prompt page and the report password is displayed on the information prompt page; If account information that has exceeded the preset time limit is found, the information is first sent to the user's email address for backup, and then deleted. The query record page is also used to display the generation time of the personal account report corresponding to the account information that has exceeded the preset time limit, and to provide the user with a password to view the report by verifying their payment password.

10. The method according to claim 9, characterized in that, The step of querying the account information corresponding to the user's payment accounts opened with multiple payment institutions based on the user's identity information includes: Send account query requests to the institutional servers corresponding to the multiple payment institutions respectively, wherein the account query requests are used to instruct the institutional servers to query the account identifiers corresponding to the user's activated payment accounts based on the user's identity information; Receive the account identifier sent by the institution's server; Call the preset query interface to query the balance information and billing information corresponding to the payment account based on the account identifier.

11. The method according to claim 9, characterized in that, After sending the account information to the terminal device, the method further includes: Receive information viewing requests sent by the terminal device; In response to the information viewing request, the points payment interface of the membership management system is called to deduct the points required to view the account information from the points corresponding to the logged-in account, and the payment result is obtained; The payment result is sent to the terminal device so that the terminal device displays the account information based on the payment result.

12. An information query device, applied to a terminal device, characterized in that, The device includes: The identity acquisition module is used to acquire the user identity information corresponding to the login account in the target application, wherein the target application is an application that supports querying information of multiple payment accounts. The first receiving module is used to receive a first input from a user in the target application for querying account information. The account information includes account information of all payment accounts corresponding to the user's identity information. The first input is the user's click input on the information query button displayed on the information query page of the target application. A request sending module is used to send an information query request to the application server in response to the first input. The information query request includes the user's identity information. The information query request is used to instruct the application server to call a pre-configured payment institution link, send the user's identity information for each link, and trigger each payment institution to return the account information of all payment accounts opened by the user through a preset interface. The account information includes at least one of the following: the number of accounts, balance information, and billing information of the payment accounts. The application server includes a server corresponding to the target application. An information receiving module is used to receive the account information sent by the application server; An information display module is used to display the account information; The fourth display module is used to display the institution information corresponding to multiple payment institutions before receiving the user's first input for querying account information; The fifth receiving module is used to receive a second input from the user, which is the institution information corresponding to the target payment institution selected from the plurality of payment institutions; The request sending module is specifically used for: In response to the second input, a target information query request for the target payment institution is sent to the application server, wherein the target information query request is used to instruct the application server to query the account information corresponding to the payment account opened by the user in the target payment institution based on the user identity information; The second display module is used to, in response to the launch operation of the target application, display a query record page if the first query result is that the login account has been verified with real name and the second query result is that there are historical query records, before receiving the first input from the user for querying account information in the target application. The query record page includes at least one of the historical query records, and the second query result is the query result obtained by the application server querying whether the login account has historical query records within a preset time period. The third display module is used to display the information query page when the first query result indicates that the login account has been verified with real name and the second query result indicates that there is no historical query record. The first receiving module is further configured to receive an instruction from the user to send the account information to a target email address when displaying the report details page corresponding to the account information; The request sending module is further configured to respond to the instruction by sending the target email address to the application server, so that the application server sends the encrypted account information to the target email address; The second display module is also used to, after receiving feedback information from the application server indicating completion of sending, jump to an information prompt page and display the report password on the information prompt page. The application server is also used to, in the case of querying account information that has exceeded the preset period, first send the account information that has exceeded the preset period to the user's email so that the user can back it up and archive it, and then delete the account information that has exceeded the preset period. The second display module is also used to display the generation time of the personal account report corresponding to the account information that has exceeded the preset period on the query record page. The query record page is also used for users to view the report password by verifying their payment password.

13. An information query device, applied to an application server, characterized in that, The application server includes a server-side component corresponding to the target application, which is an application that supports querying multiple payment account information. The device includes: A request receiving module is used to receive an information query request sent by a terminal device. The information query request includes user identity information corresponding to a login account in a target application. The information query request is generated by the target application in response to a first input, which is a click input by the user on an information query button displayed on the information query page of the target application. Before receiving the first input, the terminal device, in response to the launch operation of the target application, displays a query record page if the first query result is that the login account has been verified with real name and the second query result is that there is a historical query record. If the first query result is that the login account has been verified with real name and the second query result is that there is no historical query record, the terminal device displays the information query page. The query record page includes at least one historical query record. The second query result is the query result obtained by the application server querying whether the login account has a historical query record within a preset time period. The information query module is used to respond to the information query request and query the account information corresponding to the payment accounts opened by the user in multiple payment institutions, or the account information corresponding to the payment account opened by the user in a target payment institution, based on the user identity information. The account information includes at least one of the number of accounts, balance information and billing information of the payment accounts. The account information includes the account information of all payment accounts corresponding to the user identity information. The target payment institution is the payment institution selected by the user from multiple payment institutions displayed in the target application. The information sending module is used to send the account information to the terminal device; The information query module is specifically used for: Call the pre-configured payment institution link, send the user's identity information for each link, and trigger each payment institution to send back the account information of all payment accounts opened by the user through a preset interface; The request receiving module is further configured to receive a target email address sent by the terminal device, wherein the target email address is sent by the terminal device in response to the user's instruction to send the account information to the target email address when displaying the report details page corresponding to the account information; The information sending module is also used to send the encrypted account information to the target email address, so that after the terminal device receives the feedback information that the sending is completed from the application server, it will jump to the information prompt page and display the report password on the information prompt page; The information sending module is also used to, when querying account information that has exceeded the preset period, first send the account information that has exceeded the preset period to the user's email address so that the user can back it up and archive it, and then delete the account information that has exceeded the preset period. The query record page is also used to display the generation time of the personal account report corresponding to the account information that has exceeded the preset period, and to allow the user to view the report password by verifying the payment password.

14. An electronic device, characterized in that, The device includes: a processor and a memory storing computer program instructions; When the processor executes the computer program instructions, it implements the steps of the information query method as described in any one of claims 1-8 or 9-11.

15. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer program instructions, which, when executed by a processor, implement the steps of the information query method as described in any one of claims 1-8 or 9-11.

Images