CN115439253A

CN115439253A - Data management method and device for transaction account, electronic equipment and storage medium

Info

Publication number: CN115439253A
Application number: CN202211248985.0A
Authority: CN
Inventors: 黄嘉豪; 王峰; 周沁薇; 韩翔辉
Original assignee: Shenzhen Futu Network Technology Co Ltd
Current assignee: Shenzhen Futu Network Technology Co Ltd
Priority date: 2022-10-12
Filing date: 2022-10-12
Publication date: 2022-12-06
Also published as: WO2024077780A1

Abstract

The application discloses a data management method and device of a transaction account, electronic equipment and a storage medium, which are applied to terminal equipment, wherein the method comprises the following steps: when detecting that a user starts a target application program in terminal equipment, sending an account data acquisition request to a first server, wherein the account data acquisition request comprises mechanism account number information of a mechanism which has logged in the target application program; when first account data fed back by a first server according to an account data acquisition request are received, caching the first account data; when a control instruction which is triggered by a user through a target page in a target application program and used for controlling an account list to be displayed is acquired, generating a corresponding account list according to first account data, wherein the account list comprises a plurality of account identifications corresponding to a plurality of account information, and the account identifications are used for indicating the types of the corresponding account information; the account list is displayed, so that the account data management efficiency can be effectively improved.

Description

Data management method and device for transaction account, electronic equipment and storage medium

Technical Field

The present application belongs to the field of computer technologies, and in particular, to a data management method and apparatus for a transaction account, an electronic device, and a storage medium.

Background

When using dealer trading software, the clients of large-asset clients, trusts, family offices, asset management companies and other institutions in the market all have the appeal of carrying out asset management in an account authorization mode. However, in the related art, when an organization performs a transaction, related personnel need to specially distinguish the authorization condition of an account to be selected through a complicated query operation, so that the account data management efficiency is low, and further the transaction efficiency is low.

Disclosure of Invention

The embodiment of the application provides an implementation scheme different from that of the related technology, so as to solve the technical problems that in the related technology, when an organization conducts a transaction, the authorization condition of an account to be selected needs to be distinguished by related personnel of the organization through a complex query operation, the transaction process consumes more time, and the account data management efficiency is low.

In a first aspect, the present application provides a data management method for a transaction account, which is applied to a terminal device, and includes:

when detecting that a user starts a target application program in the terminal equipment, sending an account data acquisition request to a first server, wherein the account data acquisition request comprises mechanism account information of a mechanism which has logged in the target application program;

when first account data fed back by the first server according to the account data acquisition request is received, caching the first account data, wherein the first account data comprises a plurality of account information of at least two categories: the first account information of the organization, the second account information authorized by the organization to the first target object, and the third account information authorized by the second target object to the organization;

when a control instruction which is triggered by the user through a target page in the target application program and is used for controlling an account list to be displayed is acquired, generating a corresponding account list according to the first account data, wherein the account list comprises a plurality of account identifications corresponding to the plurality of account information, and the account identifications are used for indicating the categories of the corresponding account information;

and displaying the account list.

In a second aspect, the present application provides a data processing method applied to a first server, including:

receiving an account data acquisition request sent by terminal equipment, wherein the account data acquisition request is sent to the first server when the terminal equipment detects that a user starts a target application program in the terminal equipment, and the account data acquisition request comprises mechanism account information of a mechanism which has logged in the target application program;

determining corresponding first account data according to the mechanism account information in the account data acquisition request and a preset corresponding relation, wherein the first account data comprises a plurality of account information of at least two categories: the first account information of the organization, the second account information authorized by the organization to the first target object, and the third account information authorized by the second target object to the organization;

feeding the first account data back to the terminal device, so that when a control instruction which is triggered by the user through a target page in the target application program and used for controlling an account list is obtained by the terminal device, a corresponding account list is generated according to the first account data, and the account list is displayed, wherein the account list comprises a plurality of account identifications corresponding to the account information, and the account identifications are used for indicating the types of the corresponding account information.

In a third aspect, the present application provides a data management apparatus for a transaction account, which is applied to a terminal device, and includes:

the account data acquisition method comprises a first sending module, a second sending module and a third sending module, wherein the first sending module is used for sending an account data acquisition request to a first server when detecting that a user starts a target application program in terminal equipment, and the account data acquisition request comprises mechanism account number information of a mechanism which logs in the target application program;

the first caching module is configured to cache first account data fed back by the first server according to the account data acquisition request, where the first account data includes multiple account information of at least two categories: first account information of the organization, second account information authorized by the organization to a first target object, and third account information authorized by a second target object to the organization;

a first generating module, configured to generate a corresponding account list according to the first account data when a control instruction for controlling a display account list, which is triggered by the user through a target page in the target application program, is acquired, where the account list includes a plurality of account identifiers corresponding to the plurality of account information, and the account identifiers are used to indicate categories of the corresponding account information;

and the first display module is used for displaying the account list.

In a fourth aspect, the present application provides a data processing apparatus, applied to a first server, including:

the system comprises a first receiving module and a second receiving module, wherein the first receiving module is used for receiving an account data acquisition request sent by terminal equipment, the account data acquisition request is sent to a first server when the terminal equipment detects that a target application program in the terminal equipment is started by a user, and the account data acquisition request comprises mechanism account information of a mechanism which has logged in the target application program;

a determining module, configured to determine, according to the mechanism account information in the account data obtaining request and a preset corresponding relationship, corresponding first account data, where the first account data includes multiple account information in at least two categories: the first account information of the organization, the second account information authorized by the organization to the first target object, and the third account information authorized by the second target object to the organization;

the feedback module feeds the first account data back to the terminal device, so that when the terminal device obtains a control instruction which is triggered by the user through a target page in the target application program and used for controlling an account list to be displayed, the terminal device generates a corresponding account list according to the first account data and displays the account list, wherein the account list comprises a plurality of account identifications corresponding to the plurality of account information, and the account identifications are used for indicating the types of the corresponding account information.

In a fifth aspect, the present application provides an electronic device, comprising:

a processor; and

a memory for storing executable instructions of the processor;

wherein the processor is configured to perform any of the first aspect or the possible embodiments of the first aspect, or any of the possible embodiments of the second aspect or the second aspect, via execution of the executable instructions.

In a sixth aspect, embodiments of the present application provide a computer-readable storage medium, on which a computer program is stored, the computer program, when executed by a processor, implementing the first aspect or any of the possible implementations of the first aspect, or any of the possible implementations of the second aspect or the second aspect.

In a seventh aspect, this application provides a computer program product comprising a computer program that, when executed by a processor, implements the method of the first aspect or any of the possible implementations of the first aspect, or any of the possible implementations of the second aspect or the second aspect.

According to the scheme, when the user is detected to start the target application program in the terminal equipment, an account data acquisition request is sent to the first server, wherein the account data acquisition request comprises mechanism account number information of a mechanism which has logged in the target application program; when first account data fed back by a first server according to an account data acquisition request are received, caching the first account data, wherein the first account data comprises a plurality of account information of at least two categories: the first account information of the organization, the second account information authorized by the organization to the first target object, and the third account information authorized by the second target object to the organization; when a control instruction which is triggered by a user through a target page in a target application program and used for controlling an account list to be displayed is acquired, generating a corresponding account list according to first account data, wherein the account list comprises a plurality of account identifications corresponding to a plurality of account information, and the account identifications are used for indicating the types of the corresponding account information; and displaying the account list. Because the account list comprises a plurality of account identifications corresponding to a plurality of account information for indicating the types of the corresponding account information, when in transaction, related personnel of an organization can distinguish the authorization condition of the account to be selected through the account list, and does not need complicated query operation, thereby saving time and effectively improving the account data management efficiency and the transaction efficiency.

Drawings

In order to more clearly illustrate the embodiments of the present application or technical solutions in related arts, the drawings used in the description of the embodiments or prior arts are briefly introduced below, and it is obvious that the drawings in the description below are some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative efforts. In the drawings:

FIG. 1 is a schematic block diagram of a system provided in an exemplary embodiment of the present application;

FIG. 2 is a flowchart illustrating a data management method for a transaction account according to an exemplary embodiment of the present application;

fig. 3 is a schematic structural diagram of an organization account according to an exemplary embodiment of the present application;

fig. 4 is a schematic diagram of a first data caching process according to an exemplary embodiment of the present application;

FIG. 5 is a schematic diagram of a drop page provided by an exemplary embodiment of the present application;

FIG. 6 is a flowchart illustrating an account list presentation provided by an exemplary embodiment of the present application;

FIG. 7 is a schematic flow chart of transaction verification provided by an exemplary embodiment of the present application;

FIG. 8 is a block diagram of another system provided in an exemplary embodiment of the present application;

FIG. 9 is a schematic view of an account architecture provided by an exemplary embodiment of the present application;

FIG. 10 is a flowchart illustrating a data processing method according to an exemplary embodiment of the present application;

fig. 11 is a schematic structural diagram of a data management apparatus for transaction accounts according to an exemplary embodiment of the present application;

fig. 12 is a schematic structural diagram of a data processing apparatus according to an exemplary embodiment of the present application;

fig. 13 is a schematic block diagram of an electronic device according to an exemplary embodiment of the present application.

Detailed Description

Reference will now be made in detail to embodiments of the present application, examples of which are illustrated in the accompanying drawings. The embodiments described below with reference to the drawings are exemplary and intended to be used for explaining the present application and should not be construed as limiting the present application.

The terms "first" and "second," and the like in the description, the claims, and the drawings of the embodiments of the present application are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the application described herein are, for example, capable of operation in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

First, some terms in the embodiments of the present application are explained below to facilitate understanding by those skilled in the art.

Institutions in the stock market refer to institutional investors who have a large capital, experienced, and professional team in addition to individual investors. Institutions include bank financing, security companies, investment trust companies, social security funds, public fund, insurance funds, and the like. These institutional investors generally have specialized institutional seats in the stock market due to the high volume of funds traded.

Chain of responsibility mode: the so-called chain-of-responsibility mode, in order to avoid coupling a request sender with multiple request handlers, links all the requesting handlers into a chain by the previous object remembering the reference of its next object; when a request occurs, the request may be passed along the chain until an object processes it.

Security traders are companies that deal with securities, or securities companies.

When using securities trader trading software, institutional clients such as security traders, large asset clients, trusts, family offices, asset management companies and the like in the market all have the appeal of performing asset management in an account authorization mode, namely authorizing own accounts to one or more other institutions or users for performing asset management so that the other institutions or users obtain the use authority of authorized accounts. However, in the related art, when an organization conducts a transaction, related personnel need to purposely distinguish the authorization condition of an account for selection through a relatively complex query operation, wherein the authorization condition includes any one of the following conditions: the account data is authorized to other users and authorized by other users, the time consumption is more in the transaction process, and the account data management efficiency is lower. Therefore, the application provides a data management method for transaction accounts, which is used for solving the technical problems that in the related technology, organization related personnel need to specially distinguish the authorization condition of accounts for selection through more complex query operation, the transaction process consumes more time, and the account data management efficiency is lower.

The following describes the technical solutions of the present application and how to solve the above technical problems with specific examples. The following several specific embodiments may be combined with each other, and details of the same or similar concepts or processes may not be repeated in some embodiments. Embodiments of the present application will be described below with reference to the accompanying drawings.

Fig. 1 is a schematic structural diagram of a system according to an exemplary embodiment of the present application. The system can comprise a terminal device 10, a first server 20 and the like; the terminal device 10 and the first server 20 are connected via a network, such as a wired or wireless network connection.

A terminal device 10 for:

when detecting that a user starts a target application program in the terminal equipment, sending an account data acquisition request to a first server, wherein the account data acquisition request comprises mechanism account number information of a mechanism which has logged in the target application program;

when first account data fed back by the first server according to the account data acquisition request is received, caching the first account data, wherein the first account data comprises a plurality of account information of at least two categories: first account information of the organization, second account information authorized by the organization to a first target object, and third account information authorized by a second target object to the organization;

when a control instruction which is triggered by the user through a target page in the target application program and is used for controlling an account list to be displayed is acquired, generating a corresponding account list according to the first account data, wherein the account list comprises a plurality of account identifications corresponding to the account information, and the account identifications are used for indicating the types of the corresponding account information;

and displaying the account list.

A first server 20 for:

receiving an account data acquisition request sent by a terminal device 10, wherein the account data acquisition request is sent to the first server when the terminal device 10 detects that a user starts a target application program in the terminal device 10, and the account data acquisition request includes organization account number information of an organization which has logged in the target application program;

feeding back the first account data to the terminal device 10, so that when a control instruction for controlling displaying of an account list triggered by the user through a target page in the target application program is obtained by the terminal device 10, a corresponding account list is generated according to the first account data, and the account list is displayed, where the account list includes a plurality of account identifiers corresponding to the plurality of account information, and the account identifiers are used for indicating categories of the corresponding account information.

The terminal device 10 may be a mobile phone, a tablet computer, or the like. The terminal device 10 may be used to display a graphical user interface. The terminal device is used for interacting with a user through a graphical user interface, for example, downloading and installing a corresponding client through the terminal device and running the client, for example, calling a corresponding application program and running the application program, for example, displaying a corresponding graphical user interface through logging in a website, and the like. The first server 20 may be one server, a server cluster formed by multiple servers, or a cloud platform control center, which is not limited in this embodiment of the present application.

The specific implementation principle and the interaction process in the embodiment of the system can be referred to the following description of the embodiments of the methods.

Fig. 2 is a schematic flowchart of a data management method for a transaction account according to an exemplary embodiment of the present application, the method is applied to the aforementioned terminal device 10, as shown in fig. 2, the method at least includes the following steps S201 to S204:

s201, when it is detected that a user starts a target application program in the terminal device, an account data acquisition request is sent to a first server, wherein the account data acquisition request comprises mechanism account number information of a mechanism which has logged in the target application program.

Optionally, the user starts the target application by clicking an icon of the target application on the terminal device.

Optionally, the user is an administrator in an organization (e.g., a dealer organization) for managing an account number of the organization, the organization often manages a relatively large number of investment classes, in order to facilitate the binning management, a plurality of accounts are opened (e.g., an investment manager uses different accounts to execute different investment portfolio policies), and the administrator has management authority and transaction authority over all accounts under the account number of the organization. The transaction authority refers to investment services such as fund purchase and the like by using funds in accounts, the management authority refers to management of the structure of an organization account, fig. 3 is a schematic diagram of the structure of the organization account provided by an exemplary embodiment of the present application, and as shown in fig. 3, the structure is divided into an internet account layer and an organization account layer, the internet account layer includes an administrator and a plurality of users, and the users are traders or background employees added by the administrator. The institution account layer includes a plurality of accounts: account 1, account 2, account 3, and account 4. The account 1 corresponds to a user a, the accounts 2 and 3 correspond to a user B, the account 4 corresponds to a user C, and for any account, an administrator and the user corresponding to the account all have the management authority and the transaction authority for the account.

Optionally, referring to fig. 3, a primary account is also included under the institution account number, which may be used for saving money only. The aforementioned administrator may also manage the primary account.

Further, in an embodiment of the present application, after the primary account is set up, the method further includes the following steps:

the method comprises the following steps: and acquiring position holding information of the main account, wherein the position holding information comprises investment categories, amount information corresponding to each investment category, information of investment targets and trader information governed by the main account.

The position information of the primary account in this embodiment may include investment categories held in the primary account, such as fund and stock, the investment target may include information of names and identifications of individual stocks, and the trader information may include account information responsible for maintaining resources held in the primary account. Besides, the information of the corresponding trade region of the trade target can be included.

Step two: and determining the account number of an associated account corresponding to the main account based on the position taking information, and generating the associated account according to the account number.

Based on the amount Inv _ k corresponding to the investment classes, the amount information Amo _ i corresponding to each investment class, the amount Obe _ j of the investment targets and the amount Tra _ m of traders governed by the main account, normalization processing is carried out, and the account number Acc _ v of the associated account corresponding to the main account is determined as follows:

wherein epsilon represents an account factor, i represents an identifier corresponding to the investment class, and i and k are natural numbers larger than 1. In the calculating process, the quantity corresponding to the investment categories and the quantity corresponding to the investment targets are subjected to sine and cosine calculation, and the calculated parameters are combined with the amount information corresponding to each investment category to be used as the parameters for determining the account number, so that the objectivity of determining the account number is improved.

Step three: updating the position taken information in the main account and the associated account respectively based on the account data and the position taken information.

By transferring the resources held in the main account to the corresponding associated account, the transaction personnel can directly operate transaction items in the corresponding associated account aiming at the related transaction targets, and the management efficiency and the transaction efficiency of the transaction account are improved in such a way.

Optionally, the mechanism account information may include at least one of: the name of the institution, an identification uniquely identifying the institution (e.g., a uniform social credit code), and a device identification number of the device to which the institution account number is logged.

Optionally, the account data request is used to obtain account data under the current institution account number.

S202, when first account data fed back by the first server according to the account data acquisition request are received, caching the first account data, wherein the first account data comprises a plurality of account information of at least two categories: the first account information of the organization, the second account information authorized by the organization to the first target object, and the third account information authorized by the second target object to the organization.

The account information may include account identification, basic information of the account owner (e.g., account identification), amount of money in the account, and historical transaction data for the account, among other things.

Referring to fig. 3, an account 1, an account 2, and an account 3 are opened by a multi-account function for an institution account, and are in a subordinate relationship with the institution account, that is, the account 1, the account 2, and the account 3 are first account information included in first account data of the institution; the account 4 may be entrusted to the institution for a second target object (such as a customer of the institution), and is in a relationship with the account number of the institution, that is, the account 4 is the third account information included in the first account data of the institution.

Optionally, the aforementioned relationship between the institution account number and the plurality of accounts included in the aforementioned institution account layer may also refer to a relationship between the primary account and the plurality of accounts.

Alternatively, the aforementioned administrator may be the actual owner of the primary account, and may also be a trusted person.

Fig. 4 is a schematic view of a caching flow of first account data according to an exemplary embodiment of the present application, as shown in fig. 4, a terminal device may include a transaction module and an account data repository, after a target application is started, the terminal device invokes a first account data obtaining interface in the account data repository through the transaction module, generates a network protocol request according to the account data repository, and sends the network protocol request, that is, the account data obtaining request, to a first server, after receiving the network protocol request, the first server determines corresponding first account data according to mechanism account information in the account data obtaining request and a preset corresponding relationship, and feeds back the first account data corresponding to the mechanism account information to the account data repository, and the account data receives and caches the first account data. Wherein, the presetting of the corresponding relationship may include: affiliation, and delegation. Wherein the attaching relation is used for indicating the second corresponding relation, and the entrusting relation is used for indicating the first corresponding relation.

S203, when a control instruction which is triggered by the user through a target page in the target application program and used for controlling an account list to be displayed is acquired, generating a corresponding account list according to the first account data, wherein the account list comprises a plurality of account identifications corresponding to the account information, and the account identifications are used for indicating the types of the corresponding account information; optionally, the account identifier corresponds to account information one to one, and the plurality of account identifiers include: the account identifier corresponding to the first account information, the account identifier corresponding to the second account information, and the account identifier corresponding to the third account information.

And S204, displaying the account list.

Optionally, the target page is a purchase order page, and fig. 5 is a schematic view of the purchase order page provided in an exemplary embodiment of the present application, so that when a user purchases a fund or other service, the user can select a target account and a purchase amount through the purchase order page.

Specifically, as shown in fig. 5, the top of the order page is provided with a return button, a page name "order" and a rule check button with a "buy rule" font displayed. In addition, the order page includes a payment account field, a product name field, and a purchase amount field. The payment account column displays the words of 'payment account' and the target account selected by the user; the product name column displays the word "product name", as well as the name of the item currently transacted, such as "XX fund", and the basic information for that item, such as "7-day-of-year +2.5524%"; the buy amount column displays the word "buy amount" and a transaction currency, such as "USD", representing U.S. dollars, and also includes an amount input box in which an amount input prompt message, such as "$ 0.01" is displayed for prompting the user to input an amount greater than 0.01, when the user does not input an amount in the amount input box.

The user can trigger a control instruction for controlling the display of the account list by clicking the payment account column area, the account list can be displayed in an account selection popup window, and the account selection popup window can be displayed in the lower area of the lower page. As shown in fig. 5, the upper area in the account selection popup is provided with a close button and an account selection popup title displaying a word "select payment account", a target application name is displayed below the close button, and an account list is provided in the area below the target application name.

Fig. 6 is a schematic flow chart of displaying an account list according to an exemplary embodiment of the present application, and as shown in fig. 6, when a user clicks the payment account column region and triggers a control instruction for controlling the display of the account list, the terminal device executes a page display callback function, displays an account selection popup, so that the page controller acquires first account data from the account data repository, generates a corresponding account list according to the first account data, and displays the account list in the account selection popup through a page of placing an order.

Optionally, in addition to the account identifier, the account information further includes an account icon, account tail number information, and balance prompt information of each account. For example, in the account list in fig. 5, "integrated account (0679)" and "integrated account (2013)" are account end number information, "self account" (indicating first account information) and "committed account" (indicating second account information) "are account identifiers, and balance prompt information of the corresponding accounts is displayed below the account end number information: "available for cash $ 35.00", "available for cash $ 1,372.61". The account list can also comprise a selected identifier, and the selected identifier is displayed on the right side of the account identifier corresponding to the target account selected by the user.

In other alternative embodiments, the destination page may also be an organization information page for displaying detailed information of an organization, the organization information page may display a view button in the form of an "account list", and a user may trigger a control instruction for controlling the display of the account list by clicking the view button.

In the embodiment of the application, when a user is detected to start a target application program in terminal equipment, an account data acquisition request is sent to a first server, wherein the account data acquisition request comprises mechanism account number information of a mechanism which has logged in the target application program; when first account data fed back by a first server according to an account data acquisition request are received, caching the first account data, wherein the first account data comprises a plurality of account information of at least two categories: the first account information of the organization, the second account information authorized by the organization to the first target object, and the third account information authorized by the second target object to the organization; when a control instruction which is triggered by a user through a target page in a target application program and used for controlling the display of the account list is acquired, a corresponding account list is generated according to the first account data, the account list comprises a plurality of account identifications corresponding to a plurality of account information, and the account identifications are used for indicating the types of the corresponding account information and displaying the account list. Because the account list comprises a plurality of account identifications corresponding to a plurality of account information for indicating the types of the corresponding account information, the authority related personnel can distinguish the authorization condition of the account for selection through the account list, and do not need complicated query operation, thereby saving time and effectively improving the account data management efficiency.

In some optional embodiments of the present application, the method further comprises steps S301-S304:

s301, when the click operation of the user on the refresh button displayed on the target page is acquired, sending an account data refresh request to the first server.

S302, when second account data fed back by the first server according to the account data acquisition request are received, caching the second account data, wherein the second account data are the refreshed first account data.

And S303, generating a corresponding refreshed account list according to the second account data.

S304, displaying the refreshed account list.

Specifically, a refresh button may be displayed in the destination page, and the account data refresh request is used to acquire the latest account data under the current institution account.

In other embodiments, a refresh button may also be provided in the account list to facilitate the user to refresh when viewing the account list to obtain the latest account data (second account data).

Optionally, the account information included in the account list may be sorted according to a preset priority, where the higher the priority, the preferred account data is, and the preferred account data is preferentially displayed in the current dealer and service scene.

Optionally, the account list further includes false account data, the false account is an account that is not opened by the current institution account, and the false account is displayed in the account list, so that the user can be guided to open more accounts, and the opening rate of the account is improved.

In some optional embodiments of the present application, the method further comprises steps S401-S402:

s401, after the triggering operation of the user on the order placing button displayed in the order placing page of the target application program is detected, transaction verification is carried out, and a verification result is obtained.

In some optional embodiments of the present application, in S401, performing transaction verification to obtain a verification result, including steps S4011 to S4012:

s4011, determining whether the user selects a target account for current transaction, if so, determining whether the target account is an account corresponding to the first account data, if so, determining whether a target amount input by the user is larger than a preset minimum amount, if so, determining whether the target amount is smaller than or equal to a balance in the target account, and if so, determining that a verification result is successful.

S4012, if the user does not select the target account, or the target account is not an account corresponding to the first account data, or it is determined that the target amount input by the user is not greater than a preset minimum amount, or the target amount is greater than the balance in the target account, determining that the verification result is verification failure.

Specifically, transaction verification is performed through a duty chain mode, and a verification result is obtained. Fig. 7 is a schematic flow chart of transaction verification provided in an exemplary embodiment of the present application, and as shown in fig. 7, specifically, the transaction verification responsibility chain may include a first node, a second node, a third node, and a fourth node, and respectively perform the following 4 transaction steps of transaction verification:

step 1: and checking the target account, namely determining whether the user selects the target account. When the user selects the target account, the right area in the payment account column in fig. 5 displays the account end number information of the target account, and when the user does not select the target account, the right area in the payment account column is blank. And if the user does not select the target user, determining that the verification result is verification failure, and if the user selects the target account, entering a second node and executing the step 2.

Step 2: and checking the target account authority, namely determining whether the target account is the account corresponding to the first account data. That is, it is determined whether the target account selected by the user is an account to which the user has administrative and transaction rights. And if the target account is not the account corresponding to the first account data, determining that the verification result is verification failure, and if the target account is the account corresponding to the first account data, entering a third node and executing the step 3.

And step 3: and checking the input amount, namely determining whether the target amount input by the user is not less than a preset minimum amount. The preset minimum amount is the minimum amount allowed for the transaction, for example, the preset minimum amount may be 0.01. And if the target amount input by the user is less than the preset minimum amount, determining that the verification result is verification failure, and if the target amount input by the user is not less than the preset minimum amount, entering a fourth node and executing the step 4.

And 4, step 4: and checking the balance of the target account, namely determining whether the target amount is less than or equal to the balance in the target account, if the target amount is greater than the balance in the target account, determining that the checking result is checking failure, and if the target amount is less than or equal to the balance in the target account, determining that the checking result is checking success.

If the verification result is successful, the verification result is returned step by step, namely the fourth node returns the verification result to the third node, the third node returns the verification result to the second node, and the second node returns the verification result to the first node. The checking process uses a chain of responsibility mode, and code reusability and maintainability can be improved.

S402, when the verification result indicates that the verification is successful, a transaction request is sent to the second server, so that the second server generates corresponding order information according to the transaction request. Wherein the second server is a server that performs the fund transaction.

Optionally, after the second server generates the corresponding order information, the terminal device may receive an order generation prompt message sent by the second server, display a transaction password input page, and prompt the user to input the transaction password. After the user inputs the password, password verification is carried out, after the password verification is passed, the transaction is completed, and an account information updating request is sent to the first server, wherein the account information updating request is used for indicating the first server to update corresponding data under the target account and the balance of the target account.

Optionally, when the verification result indicates that the verification fails, the prompt information corresponding to the node determining the verification result is displayed according to the node determining the verification result. For example, when it is determined that the user does not select the target account, the node of the verification result is determined to be the first node, and at this time, the first node may correspond to the prompt message in the form of "please select the payment account".

In some optional embodiments of the present application, the method further comprises steps S501-S503:

s501, a first authorization request is sent to the first server, the first authorization request includes the mechanism account information, the account information of the first target object and first to-be-authorized account information applying authorization to the first target object, the first authorization request is used for indicating the first server to send a first authorization application to first equipment corresponding to the account information of the first target object, obtaining first authorization reply information fed back by the first equipment according to the first authorization application, and generating corresponding first authorization prompt information according to the first authorization reply information.

S502, receiving the first authorization prompt message fed back by the first server, wherein the first authorization prompt message comprises a first prompt message used for indicating that authorization passes or a second prompt message used for indicating that authorization does not pass.

S503, displaying the first authorization prompt message.

Fig. 8 is a schematic structural diagram of another system provided in an exemplary embodiment of the present application, where the system may include the terminal device 10, the first server 20, the first device 30, the second device 40, and the like; the terminal device 10, the first device 30, and the second device 40 are respectively connected to the first server 20 through a network, for example, a wired or wireless network connection. The terminal device 10, the first device 30, and the second device 40 may be a mobile phone, a notebook computer, or the like.

Alternatively, information interaction among the terminal device 10, the first device 30, the second device 40, and the like may be implemented by the first server 20.

Specifically, the first server determines, according to account information of a first target object in the first authorization request, a first device corresponding to the first target object, determines a first authorization application according to the first authorization request, and sends the first authorization application to the first device, where the first authorization request is used by an organization to request that first to-be-authorized account information is authorized to another organization or an individual (the first target object), where the first to-be-authorized account information is included in the first account information, the first target object may be a user using the first device, and content included in the first authorization request and content included in the first authorization application may be the same.

Optionally, after receiving an account data acquisition request sent by the terminal device, the first server may determine corresponding first account data according to the mechanism account information in the account data acquisition request and a preset corresponding relationship.

After receiving a first authorization request sent by the terminal device, the first server sends a first authorization application to first equipment corresponding to account information of a first target object according to the first authorization request; after receiving a first authorization application, if a reply instruction which is triggered by a user and aims at the first authorization request is detected, the first device generates corresponding first authorization reply information, sends the first authorization reply information to the first server, generates corresponding first authorization prompt information according to the first authorization reply information, and sends the first authorization prompt information to the terminal device.

If the first authorization reply information indicates that the first target object agrees with the first authorization application, the first server generates first prompt information for indicating that the first target object agrees with the first authorization application and sends the first prompt information to the terminal device.

If the first authorization reply information indicates that the first target object does not agree with the first authorization application, the first target object rejects the delegation of the organization to the first to-be-authorized account information, and the first server may generate second prompt information for indicating that the first target object does not agree with the first authorization application, and send the second prompt information to the terminal device.

If the first authorization reply information indicates that the first target object agrees with the first authorization application, the first server determines the first to-be-authorized account information as second account information, establishes a first corresponding relationship between the second account information of the institution account and the account information of the first target object, and adds the first corresponding relationship to the preset corresponding relationship. The first corresponding relation indicates that the organization entrusts the account information of the organization to the first target object, so that the first target object has management authority and transaction authority on the second account information.

In some optional embodiments of the present application, the method further comprises steps S601-S603:

s601, receiving a second authorization application sent by the first server, wherein the second authorization application is sent when the first server receives a second authorization request sent by second equipment corresponding to the second target object, and the second authorization application comprises mechanism account information, account information of the second target object and second to-be-authorized account information applying authorization to the mechanism.

S602, when a reply instruction which is triggered by the user and aims at the second authorization request is detected, corresponding second authorization reply information is generated.

S603, the second authorization reply information is sent to the first server, so that the first server generates corresponding second authorization prompt information according to the second authorization reply information, and the second authorization prompt information is fed back to the second device.

Optionally, the second authorization request and the second authorization application may contain the same content. When the second device receives the second authorization request, the user may choose to agree or disagree with account information of the second target object and the second account information to be authorized, which are included in the second authorization request, so that the second device generates second authorization reply information.

If the second authorization reply information indicates that the organization agrees with the second authorization application, the second account information to be authorized is determined to be third account information, the first server can generate third prompt information used for indicating that the organization agrees with the second authorization application, create a second corresponding relationship between the organization account information and the third account information, and add the second corresponding relationship to a preset corresponding relationship. The second corresponding relation indicates that the second target object entrusts the account information of the second target object to the organization, so that the organization has management authority and transaction authority on third account information.

If the second authorization reply information indicates that the organization does not approve the second authorization application, the second authorization reply information indicates that the organization rejects the delegation of the second target object to the second to-be-authorized account information, and the first server may generate fourth prompt information for indicating that the organization does not approve the second authorization application, and send the fourth prompt information to the second device.

Through the above scheme, an account architecture of an organization may be formed, and fig. 9 is a schematic structural diagram of the account architecture provided in an exemplary embodiment of the present application. As shown in fig. 9, the account architecture is configured with a view application programming interface, a business application programming interface, a base application programming interface, a data center, and a base module.

Optionally, the second server may further include a wind control server.

Optionally, the institution account does not issue the asset card of the fund front page, and before the order is created, the account owner is not verified in the application, so that the limitation that only the account owner is supported to conduct fund transaction in the related technology is eliminated, and the data processing efficiency is improved.

Specifically, the view application programming interface includes a payment account bar interface and an account selection popup interface for displaying the payment account bar account selection popup on the drop page of the target application, respectively. The service application programming interface provides a scenarized service application programming interface and provides interface packages used by the service scenes, and the interface packages comprise a preferred account interface, an account related protocol data interface and a false account interface, wherein the account related protocol data interface is used for obtaining real account list data from the first server. The basic application programming interfaces comprise a creation application programming interface, a common transaction account application programming interface, a fund account application programming interface, a query application programming interface and the like, and are used for providing data center interface-based packaging and interface packaging of different dealer organizations and the like. The data center provides an interface for acquiring account data (first account data and second account data) externally, and internal implementation ensures the timeliness of account data updating through acquisition failure retry and a timing refresh request network protocol, solves the scene of data pull failure during network jitter and improves the reliability of the interface; the basic module comprises a storage module (used for providing a storage interface), a database module (used for providing a database read-write interface), a network module (used for providing a network protocol request interface) and a data structure model, the performance problem of the interface is solved through the storage module, and the database module is adapted to a scene that data needs to be normally acquired when a network does not return after a target application program is restarted.

In the technical scheme, the method comprises the steps of adding an authorization account related field in a data structure model, adding an application programming interface and implementation for obtaining an authorization account in a basic application programming interface and a business application programming interface, and adding an authorized account in a view application programming interface, so that the authorization account (second account information and/or third account information) can be selected and used when a transaction business such as fund purchase is carried out.

Fig. 10 is a flowchart illustrating a data processing method according to an exemplary embodiment of the present application, where the method is applied to the first server 20, and as shown in fig. 10, the method at least includes the following steps S701 to S703:

s701, receiving an account data acquisition request sent by terminal equipment, wherein the account data acquisition request is sent to a first server when the terminal equipment detects that a user starts a target application program in the terminal equipment, and the account data acquisition request comprises mechanism account number information of a mechanism which has logged in the target application program;

s702, determining corresponding first account data according to the mechanism account information in the account data acquisition request and a preset corresponding relation, wherein the first account data comprises a plurality of account information of at least two categories: the first account information of the organization, the second account information authorized by the organization to the first target object, and the third account information authorized by the second target object to the organization;

s703, feeding back the first account data to the terminal device, so that when the terminal device obtains a control instruction which is triggered by the user through a target page in the target application program and used for controlling an account list to be displayed, a corresponding account list is generated according to the first account data, and the account list is displayed, wherein the account list comprises a plurality of account identifications corresponding to the plurality of account information, and the account identifications are used for indicating the types of the corresponding account information.

In some optional embodiments of the present application, the data processing method further includes steps S801-S805:

s801, receiving a first authorization request sent by the terminal device, wherein the first authorization request comprises the mechanism account information, the account information of the first target object, and first to-be-authorized account information applying for authorization to the first target object;

s802, sending a first authorization application to first equipment corresponding to account information of a first target object according to the first authorization request;

s803, receiving first authorization reply information fed back by the first device for the first authorization application;

s804, if the first authorization reply information indicates that the first target object agrees with the first authorization application, a first corresponding relation between the mechanism account information and the first to-be-authorized account information is created; adding the first corresponding relation to the preset corresponding relation, and generating first prompt information for indicating that the first target object agrees with the first authorization application; sending the first prompt message to the terminal equipment;

s805, if the first authorization reply information indicates that the first target object does not agree with the first authorization application, generating second prompt information for indicating that the first target object does not agree with the first authorization application; and sending the second prompt message to the terminal equipment.

For the specific implementation of the data processing method, reference may be made to the foregoing contents, which are not described herein again.

Fig. 11 is a schematic structural diagram of a data management apparatus for a transaction account according to an exemplary embodiment of the present application, where the apparatus is applied to a terminal device, and includes:

the terminal equipment comprises a first sending module, a second sending module and a third sending module, wherein the first sending module is used for sending an account data acquisition request to a first server when detecting that a user starts a target application program in the terminal equipment, and the account data acquisition request comprises mechanism account number information of a mechanism which has logged in the target application program;

the first caching module is configured to cache first account data fed back by the first server according to the account data acquisition request, where the first account data includes multiple account information of at least two categories: the first account information of the organization, the second account information authorized by the organization to the first target object, and the third account information authorized by the second target object to the organization;

and the first display module is used for displaying the account list.

In some optional embodiments of the present application, the data management apparatus for transaction accounts further includes:

the second sending module is used for sending an account data refreshing request to the first server when the clicking operation of the user on the refreshing button displayed on the target page is obtained;

the second cache module is used for caching second account data fed back by the first server according to the account data acquisition request, wherein the second account data is refreshed first account data;

the second generation module is used for generating a corresponding refreshed account list according to the second account data;

and the second display module is used for displaying the refreshed account list.

the verification module is used for carrying out transaction verification after detecting that the user triggers the order placing button displayed in the order placing page of the target application program to obtain a verification result;

and the third sending module is used for sending a transaction request to a second server when the verification result indicates that the verification is successful, so that the second server generates corresponding order information according to the transaction request.

In some optional embodiments of the present application, the verification module is specifically configured to, when the verification module is used to perform transaction verification and obtain a verification result:

determining whether the user selects a target account for current transaction, if so, determining whether the target account is an account corresponding to the first account data, if so, determining whether a target amount input by the user is larger than a preset minimum amount, if so, determining whether the target amount is smaller than or equal to the balance in the target account, and if so, determining that the verification result is successful;

if the user does not select the target account, or the target account is not the account corresponding to the first account data, or the target amount input by the user is determined to be not more than the preset minimum amount, or the target amount is determined to be more than the balance in the target account, determining that the verification result is verification failure.

a fourth sending module, configured to send a first authorization request to the first server, where the first authorization request includes the mechanism account information, the account information of the first target object, and first to-be-authorized account information that applies for authorization to the first target object, and the first authorization request is used to instruct the first server to send a first authorization application to a first device corresponding to the account information of the first target object, obtain first authorization reply information that is fed back by the first device for the first authorization application, and generate corresponding first authorization prompt information according to the first authorization reply information;

a second receiving module, configured to receive the first authorization prompt message fed back by the first server, where the first authorization prompt message includes a first prompt message used to indicate that authorization passes or a second prompt message used to indicate that authorization fails;

and the third display module is used for displaying the first authorization prompt message.

a third receiving module, configured to receive a second authorization application sent by the first server, where the second authorization application is sent by the first server when receiving a second authorization request sent by a second device corresponding to the second target object, and the second authorization request includes the mechanism account information, the account information of the second target object, and second to-be-authorized account information that applies for authorization to the mechanism;

a third generating module, configured to generate corresponding second authorization reply information when a reply instruction to the second authorization request triggered by the user is detected;

and the fifth sending module is used for sending the second authorization reply information to the first server, so that the first server generates corresponding second authorization prompt information according to the second authorization reply information, and feeds the second authorization prompt information back to the second device.

Fig. 12 is a schematic structural diagram of a data processing apparatus according to an exemplary embodiment of the present application, where the apparatus is applied to a first server, and includes:

the account data acquisition module is used for receiving an account data acquisition request sent by terminal equipment, wherein the account data acquisition request is sent to a first server when the terminal equipment detects that a user starts a target application program in the terminal equipment, and the account data acquisition request comprises mechanism account information of a mechanism which has logged in the target application program;

the feedback module feeds the first account data back to the terminal device, so that when the terminal device obtains a control instruction which is triggered by the user through a target page in the target application program and used for controlling an account list to be displayed, the terminal device generates a corresponding account list according to the first account data and displays the account list, wherein the account list comprises a plurality of account identifications corresponding to the account information, and the account identifications are used for indicating the types of the corresponding account information.

In some optional embodiments of the present application, the data processing apparatus further comprises:

a fourth receiving module, configured to receive a first authorization request sent by the terminal device, where the first authorization request includes the mechanism account information, the account information of the first target object, and first to-be-authorized account information that applies for authorization to the first target object;

a sixth sending module, configured to send a first authorization application to the first device corresponding to the account information of the first target object according to the first authorization request;

a fifth receiving module, configured to receive first authorization reply information fed back by the first device for the first authorization application;

a creating module, configured to create a first corresponding relationship between the institution account information and the first to-be-authorized account information if the first authorization reply information indicates that the first target object agrees with the first authorization application; adding the first corresponding relation to the preset corresponding relation, and generating first prompt information for indicating that the first target object agrees with the first authorization application; sending the first prompt message to the terminal equipment;

a seventh sending module, configured to generate second prompt information for indicating that the first target object does not agree with the first authorization application if the first authorization reply information indicates that the first target object does not agree with the first authorization application; and sending the second prompt message to the terminal equipment.

It is to be understood that the apparatus embodiments and the method embodiments may correspond to each other and similar descriptions may be made with reference to the method embodiments. To avoid repetition, the description is omitted here. Specifically, the apparatus may perform the method embodiment, and the foregoing and other operations and/or functions of each module in the apparatus are respectively corresponding flows in each method in the method embodiment, and for brevity, are not described again here.

The apparatus of the embodiments of the present application is described above in connection with the drawings from the perspective of functional modules. It should be understood that the functional modules may be implemented by hardware, by instructions in software, or by a combination of hardware and software modules. Specifically, the steps of the method embodiments in the present application may be implemented by integrated logic circuits of hardware in a processor and/or instructions in the form of software, and the steps of the method disclosed in conjunction with the embodiments in the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. Alternatively, the software modules may be located in random access memory, flash memory, read only memory, programmable read only memory, electrically erasable programmable memory, registers, and the like, as is well known in the art. The storage medium is located in a memory, and a processor reads information in the memory and combines hardware thereof to complete steps of the above method embodiments.

Fig. 13 is a schematic block diagram of an electronic device provided in an embodiment of the present application, where the electronic device may include:

a memory 1301 and a processor 1302, the memory 1301 being adapted to store a computer program and to transfer the program code to the processor 1302. In other words, the processor 1302 may call and run a computer program from the memory 1301 to implement the method in the embodiment of the present application.

For example, the processor 1302 may be configured to perform the above-described method embodiments according to instructions in the computer program.

In some embodiments of the present application, the processor 1302 may include, but is not limited to:

general purpose processors, digital Signal Processors (DSPs), application Specific Integrated Circuits (ASICs), field Programmable Gate Arrays (FPGAs) or other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components, and the like.

In some embodiments of the present application, the memory 1301 includes, but is not limited to:

volatile memory and/or non-volatile memory. The non-volatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable PROM (EEPROM), or a flash Memory. Volatile Memory can be Random Access Memory (RAM), which acts as external cache Memory. By way of example, but not limitation, many forms of RAM are available, such as Static random access memory (Static RAM, SRAM), dynamic Random Access Memory (DRAM), synchronous Dynamic random access memory (Synchronous DRAM, SDRAM), double Data Rate Synchronous Dynamic random access memory (DDR SDRAM), enhanced Synchronous SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), and Direct Rambus RAM (DR RAM).

In some embodiments of the present application, the computer program may be partitioned into one or more modules, which are stored in the memory 1301 and executed by the processor 1302 to perform the methods provided herein. The one or more modules may be a series of computer program instruction segments capable of performing certain functions, the instruction segments describing the execution of the computer program in the electronic device.

As shown in fig. 13, the electronic device may further include:

a transceiver 1303, the transceiver 1303 may be connected to the processor 1302 or the memory 1301.

The processor 1302 may control the transceiver 1303 to communicate with other devices, and in particular, may transmit information or data to the other devices or receive information or data transmitted by the other devices. The transceiver 1303 may include a transmitter and a receiver. The transceiver 1303 may further include one or more antennas.

It should be understood that the various components in the electronic device are connected by a bus system that includes a power bus, a control bus, and a status signal bus in addition to a data bus.

The present application also provides a computer-readable storage medium having stored thereon a computer program which, when executed by a computer, enables the computer to carry out the methods of the above-described method embodiments. Alternatively, the present application also provides a computer program product containing instructions, which when executed by a computer, cause the computer to execute the method of the above method embodiment.

It is understood that in the specific implementation of the present application, data related to account information and the like is referred to, when the above embodiments of the present application are applied to specific products or technologies, user permission, consent or authorization needs to be obtained, and the collection, use and processing of the related data need to comply with related laws and regulations and standards of related countries and regions.

When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. The procedures or functions described in accordance with the embodiments of the application are all or partially generated when the computer program instructions are loaded and executed on a computer. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored on a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, the computer instructions may be transmitted from one website, computer, first server, or data center to another website, computer, first server, or data center via wired (e.g., coaxial cable, fiber optic, digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a first server, a data center, etc., that includes one or more of the available media. The usable medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a Digital Video Disk (DVD)), or a semiconductor medium (e.g., a Solid State Disk (SSD)), among others.

Those of ordinary skill in the art will appreciate that the various illustrative modules and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the module is only one logical functional division, and other divisions may be realized in practice, for example, a plurality of modules or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed coupling or direct coupling or communication connection between each other may be through some interfaces, indirect coupling or communication connection between devices or modules, and may be in an electrical, mechanical or other form.

Modules described as separate parts may or may not be physically separate, and parts displayed as modules may or may not be physical modules, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. For example, functional modules in the embodiments of the present application may be integrated into one processing module, or each of the modules may exist alone physically, or two or more modules are integrated into one module.

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A data management method of a transaction account is applied to a terminal device and is characterized by comprising the following steps:

and displaying the account list.

2. The method of claim 1, further comprising:

when the click operation of the user on a refresh button displayed on the target page is acquired, sending an account data refresh request to the first server;

when second account data fed back by the first server according to the account data acquisition request is received, caching the second account data, wherein the second account data is refreshed first account data;

generating a corresponding refreshed account list according to the second account data;

and displaying the refreshed account list.

3. The method of claim 1, further comprising:

after detecting the triggering operation of the user on a menu-down button displayed in a menu-down page of a target application program, carrying out transaction verification to obtain a verification result;

and when the verification result indicates that the verification is successful, sending a transaction request to a second server so that the second server generates corresponding order information according to the transaction request.

4. The method of claim 3, wherein the performing transaction verification to obtain a verification result comprises:

determining whether the user selects a target account for current transaction, if so, determining whether the target account is an account corresponding to the first account data, if so, determining whether a target amount input by the user is larger than a preset minimum amount, if so, determining whether the target amount is smaller than or equal to a balance in the target account, and if so, determining that a verification result is successful;

if the user does not select the target account, or the target account is not the account corresponding to the first account data, or the target amount input by the user is determined to be not more than the preset minimum amount, or the target amount is more than the balance in the target account, determining that the verification result is verification failure.

5. The method of claim 1, further comprising:

sending a first authorization request to the first server, where the first authorization request includes the mechanism account information, the account information of the first target object, and first to-be-authorized account information applying for authorization to the first target object, and the first authorization request is used to instruct the first server to send a first authorization application to first equipment corresponding to the account information of the first target object, obtain first authorization reply information fed back by the first equipment for the first authorization application, and generate corresponding first authorization prompt information according to the first authorization reply information;

receiving the first authorization prompt message fed back by the first server, wherein the first authorization prompt message comprises a first prompt message for indicating that authorization is passed or a second prompt message for indicating that authorization is not passed;

and displaying the first authorization prompt message.

6. The method of claim 1, further comprising:

receiving a second authorization application sent by the first server, where the second authorization application is sent by the first server when receiving a second authorization request sent by a second device corresponding to the second target object, and the second authorization request includes the mechanism account information, the account information of the second target object, and second to-be-authorized account information that applies for authorization to the mechanism;

when a reply instruction which is triggered by the user and aims at the second authorization application is detected, generating corresponding second authorization reply information;

and sending the second authorization reply information to the first server, so that the first server generates corresponding second authorization prompt information according to the second authorization reply information, and feeds the second authorization prompt information back to the second device.

7. A data processing method is applied to a first server and is characterized by comprising the following steps:

8. The method of claim 7, further comprising:

receiving a first authorization request sent by the terminal equipment, wherein the first authorization request comprises the mechanism account information, the account information of the first target object and first to-be-authorized account information applying for authorization to the first target object;

sending a first authorization application to first equipment corresponding to account information of a first target object according to the first authorization request;

receiving first authorization reply information fed back by the first device for the first authorization application;

if the first authorization reply information indicates that the first target object agrees with the first authorization application, creating a first corresponding relationship between the institution account information and the first to-be-authorized account information; adding the first corresponding relation to the preset corresponding relation, and generating first prompt information for indicating that the first target object agrees with the first authorization application; sending the first prompt message to the terminal equipment;

if the first authorization reply information indicates that the first target object does not agree with the first authorization application, generating second prompt information for indicating that the first target object does not agree with the first authorization application; and sending the second prompt message to the terminal equipment.

9. A data management device of a transaction account is applied to a terminal device and comprises the following components:

and the first display module is used for displaying the account list.

10. A data processing apparatus, applied to a first server, comprising:

a determining module, configured to determine corresponding first account data according to the mechanism account information in the account data obtaining request and a preset corresponding relationship, where the first account data includes multiple account information in at least two categories as follows: the first account information of the organization, the second account information authorized by the organization to the first target object, and the third account information authorized by the second target object to the organization;

11. An electronic device, comprising:

a processor; and

a memory for storing executable instructions of the processor;

wherein the processor is configured to perform the method of any of claims 1-8 via execution of the executable instructions.

12. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the method of any one of claims 1 to 8.