Transaction account management method, device, computer readable medium and electronic device

Abstract

The present application discloses a transaction account management method, device, computer-readable medium and electronic device, the method comprising: obtaining authorization information initiated by a first user based on a first graphical user interface to authorize a designated account of the first user to a second user; sending the authorization information to a second user client, so that the second user client returns an authorization agreement with a signature of the second user based on the authorization information; obtaining the signature of the first user for the authorization agreement, and performing a legality check on the signed authorization agreement; if the signed authorization agreement passes the verification, an account information change message is initiated to the second user client, so that the second user client displays the designated account on the second graphical user interface of the second user client according to the account information change message. The present application achieves the effect of authorizing the account of the first user to be used by the second user, and the authorization process is signed and verified to ensure the security of the account authorization.

Description

Technical Field

[0001] The present application belongs to the field of computer technology, and specifically relates to a transaction account management method, device, computer-readable medium, and electronic device. Background Art

[0002] In information exchange platforms, users usually need to use accounts to perform some operations. At present, in many information exchange platforms, users can only create one account with their own valid information, or users can create multiple accounts, but these multiple accounts can only be used by themselves and cannot be used by other users, that is, accounts cannot be shared, which makes the flexibility of account use between users low and needs to be improved.

[0003] It should be noted that the information disclosed in the above background technology section is only used to enhance the understanding of the background of the present application, and therefore may include information that does not constitute the prior art known to ordinary technicians in the field. Summary of the invention

[0004] The purpose of the present application is to provide a transaction account management method, device, computer-readable medium and electronic device to solve the problem in the related art that accounts cannot be shared and the flexibility of account use between users is low.

[0005] Other features and advantages of the present application will become apparent from the following detailed description, or may be learned in part by the practice of the present application.

[0006] According to one aspect of an embodiment of the present application, a method for managing a transaction account is provided, comprising:

[0007] Acquire authorization information initiated by a first user based on a first graphical user interface to authorize a designated account of the first user to a second user;

[0008] Sending the authorization information to the second user client, so that the second user client returns an authorization agreement with the second user's signature based on the authorization information;

[0009] Obtaining the first user's signature on the authorization agreement, and performing a validity verification on the signed authorization agreement;

[0010] If the signed authorization agreement is verified to be successful, an account information change message is sent to the second user client, so that the second user client displays the designated account on the second graphical user interface of the second user client according to the account information change message.

[0011] According to one aspect of an embodiment of the present application, a transaction account management device is provided, including:

[0012] An authorization information acquisition module, used to acquire authorization information initiated by a first user based on a first graphical user interface to authorize a designated account of the first user to a second user;

[0013] An authorization agreement acquisition module, used to send the authorization information to the second user client, so that the second user client returns an authorization agreement with the second user's signature based on the authorization information;

[0014] A verification module, used to obtain the signature of the first user on the authorization agreement and perform a legality verification on the signed authorization agreement;

[0015] An information sending module is used to initiate an account information change message to the second user client if the signed authorization agreement verification passes, so that the second user client displays the specified account on the second graphical user interface of the second user client according to the account information change message.

[0016] In one embodiment of the present application, the verification module is specifically used to:

[0017] Verifying the first user signature and the second user signature in the signed authorization agreement respectively to determine whether the first user signature and the second user signature are legal;

[0018] If both the first user signature and the second user signature are legal, then determining that the signed authorization agreement verification has passed;

[0019] If at least one of the first user signature and the second user signature is illegal, it is determined that the signed authorization protocol verification fails.

[0020] In one embodiment of the present application, the verification module is further used to:

[0021] If the signed authorization agreement fails the verification, a re-signed authorization agreement is obtained and the legitimacy of the re-signed authorization agreement is verified.

[0022] In one embodiment of the present application, the authorization information acquisition module is specifically used to:

[0023] determining whether the account selected for authorization by the first user based on the first graphical user interface is an account of a specified type;

[0024] If the account used for authorization is an account of a specified type, the account used for authorization is used as a specified account, and authorization information for authorizing the specified account to the second user is generated according to the specified account and the authorization configuration information of the specified account.

[0025] In one embodiment of the present application, the authorization information acquisition module is further used to: if the account used for authorization is not an account of a specified type, send a prompt message to the first user indicating that the authorization account selection is incorrect, so that the first user reselects the account used for authorization.

[0026] In one embodiment of the present application, the device further includes:

[0027] An account type determination module, used to determine the type of each account of the first user, and set a type identifier for each account according to the type of each account;

[0028] The account display module is used to display the type identification of each account on the first graphical user interface, so that the first user can know the type of each account through the type identification of each account.

[0029] In one embodiment of the present application, the second user client is specifically used for:

[0030] Register a listener to monitor account information change messages;

[0031] When the listener listens to the account information change message, the second user client initiates an account information acquisition request to the server;

[0032] Receiving target account information fed back by the server based on the account information acquisition request, the target account information including the designated account;

[0033] The second graphical user interface of the second user client is updated according to the target account information so that the designated account is displayed on the second graphical user interface.

[0034] According to one aspect of an embodiment of the present application, a computer-readable medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the method for managing a transaction account in the above technical solution is implemented.

[0035] According to one aspect of an embodiment of the present application, an electronic device is provided, comprising: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to execute a method for managing a trading account as in the above technical solution by executing the executable instructions.

[0036] According to one aspect of the embodiments of the present application, a computer program product or a computer program is provided, the computer program product or the computer program comprising computer instructions, the computer instructions being stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the method for managing a trading account as in the above technical solution.

[0037] In the technical solution provided in the embodiment of the present application, the authorization information of the designated account is sent to the second user client to obtain an authorization agreement with the second user's signature, and then the first user signs to form a complete authorization agreement, and the authorization agreement is verified. When the verification passes, the second user can use the designated account, thereby authorizing the first user's account to be used by the second user, that is, account sharing is realized. The authorization process is signed and verified to ensure the security of account authorization.

[0038] It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] The drawings herein are incorporated into the specification and constitute a part of the specification, illustrate embodiments consistent with the present application, and together with the specification are used to explain the principles of the present application. Obviously, the drawings described below are only some embodiments of the present application, and for ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0040] Figure 1 The exemplary system architecture block diagram applying the technical solution of the present application is schematically shown.

[0041] Figure 2 A flowchart of a transaction account management method provided by an embodiment of the present application is schematically shown.

[0042] Figure 3 A flowchart for generating authorization information provided by an embodiment of the present application is schematically shown.

[0043] Figure 4 A flowchart of a transaction account management method provided by an embodiment of the present application is schematically shown.

[0044] Figure 5 The flowchart of a second user client obtaining a designated account provided by an embodiment of the present application is schematically shown.

[0045] Figure 6 The structural block diagram of the transaction account management device provided in an embodiment of the present application is schematically shown.

[0046] Figure 7 The structure block diagram of a computer system suitable for implementing an electronic device of an embodiment of the present application is schematically shown. DETAILED DESCRIPTION

[0047] Example embodiments will now be described more fully with reference to the accompanying drawings. However, example embodiments can be implemented in a variety of forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this application will be more comprehensive and complete and fully convey the concept of the example embodiments to those skilled in the art.

[0048] In addition, described feature, structure or characteristic can be combined in one or more embodiments in any suitable manner. In the following description, many specific details are provided to provide a full understanding of the embodiments of the present application. However, those skilled in the art will appreciate that the technical scheme of the present application can be put into practice without one or more of the specific details, or other methods, components, devices, steps, etc. can be adopted. In other cases, known methods, devices, realizations or operations are not shown or described in detail to avoid blurring the various aspects of the application.

[0049] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically independent entities. That is, these functional entities may be implemented in software form, or in one or more hardware modules or integrated circuits, or in different networks and / or processor devices and / or microcontroller devices.

[0050] The flowcharts shown in the accompanying drawings are only exemplary and do not necessarily include all the contents and operations / steps, nor must they be executed in the order described. For example, some operations / steps can be decomposed, and some operations / steps can be combined or partially combined, so the actual execution order may change according to actual conditions.

[0051] Figure 1 The exemplary system architecture block diagram applying the technical solution of the present application is schematically shown.

[0052] like Figure 1 As shown, the system architecture 100 may include a terminal device 110, a network 120, and a server 130. The terminal device 110 may include various electronic devices such as a smart phone, a tablet computer, a laptop computer, and a desktop computer. The server 130 may be an independent physical server, or a server cluster or a distributed system composed of multiple physical servers, or a cloud server providing cloud computing services. The network 120 may be a communication medium of various connection types that can provide a communication link between the terminal device 110 and the server 130, such as a wired communication link or a wireless communication link.

[0053] According to the implementation requirements, the system architecture in the embodiment of the present application can have any number of terminal devices, networks and servers. For example, the server 130 can be a server group composed of multiple server devices. In addition, the technical solution provided in the embodiment of the present application can be applied to the terminal device 110, can also be applied to the server 130, or can be implemented by the terminal device 110 and the server 130 together, and the present application does not make any special restrictions on this.

[0054] For example, the first user initiates an authorization request to authorize the designated account to the second user through the first graphical user interface of the terminal device 110. The terminal device 110 obtains the authorization information based on the authorization request and sends the authorization information to the server 130. After receiving the authorization information, the server 130 sends the authorization information to the second user client, so that the second user client returns the authorization agreement with the signature of the second user based on the authorization information. The second client can be set in the same terminal device 110 as the first client of the first user, or in a different terminal device 110, which is not limited in this embodiment. After receiving the authorization agreement with the signature of the second user, the server 130 continues to obtain the signature of the first user for the authorization agreement and performs a legality check on the signed authorization agreement. When the signed authorization agreement is verified, the server 130 initiates an account information change message to the second user client, so that the second user client displays the designated account on the second graphical user interface of the second user client according to the account information change message. The second user can query and use the designated account authorized by the first user in the second graphical user interface of the terminal device 110.

[0055] In one embodiment of the present application, both the first user and the second user can conduct transactions through the blockchain network. The first user can initiate an authorization request to authorize the designated account to the second user through a node in the blockchain network, so that the node in the blockchain network implements the management method of the transaction account provided in the embodiment of the present application. For example, the server 130 that implements the management method of the transaction account provided in the embodiment of the present application is a node in the blockchain network. Blockchain is a new application mode of computer technologies such as distributed data storage, point-to-point transmission, consensus mechanism, encryption algorithm, etc. Blockchain is essentially a decentralized database, a string of data blocks generated by cryptographic methods, each of which contains a batch of network transaction information for verifying the validity of its information (anti-counterfeiting) and generating the next block. Blockchain can include a blockchain underlying platform, a platform product service layer, and an application service layer.

[0056] The underlying blockchain platform can include processing modules such as user management, basic services, smart contracts, and operation monitoring. Among them, the user management module is responsible for the identity information management of all blockchain participants, including maintaining public and private key generation (account management), key management, and the maintenance of the correspondence between the user's real identity and the blockchain address (authority management), etc., and, under authorization, supervises and audits the transactions of certain real identities and provides risk control rule configuration (risk control audit); the basic service module is deployed on all blockchain node devices to verify the validity of business requests, and records valid requests to storage after consensus is reached. For a new business request, the basic service first adapts the interface for parsing and authentication (interface adaptation), and then encrypts the business information through the consensus algorithm (consensus management). The smart contract module is responsible for the registration and issuance of contracts, as well as contract triggering and contract execution. Developers can define the contract logic in a programming language and publish it to the blockchain (contract registration). According to the logic of the contract terms, the key or other events are called to trigger the execution and complete the contract logic. It also provides the function of contract upgrade and cancellation. The operation monitoring module is mainly responsible for the deployment, configuration modification, contract setting, cloud adaptation and real-time status visualization output of the product during the product release process, such as alarm, network monitoring, node equipment health monitoring, etc.

[0057] The platform product service layer provides the basic capabilities and implementation framework of typical applications. Developers can superimpose business features based on these basic capabilities to complete the blockchain implementation of business logic. The application service layer provides application services based on blockchain solutions for business participants to use.

[0058] In this embodiment, through authorization management of trading accounts, the first user's trading authority can be authorized to one, two, or more than two other accounts, so that the virtual resources in the first user's account can be traded and processed through other accounts. The transaction type includes at least one of the following: stocks, funds, options, futures, bonds and other virtual assets, and is not limited to trading markets and regions.

[0059] In this embodiment, corresponding authorized transaction content can also be selected during the account authorization management process, for example, only stock trading authority can be authorized to a certain account, while fund trading authority can be authorized to another account, and so on.

[0060] In one embodiment of the present application, the transaction account management method provided in the embodiment of the present application is executed by the server 130, and the server 130 is used to receive the authorization information sent by the terminal device 110 to authorize the designated account of the first user to the second user, and perform corresponding operations based on the authorization information to display the designated account on the second graphical user interface. Accordingly, the transaction account management device is generally set in the server 130. However, it is easy for those skilled in the art to understand that the transaction account management method provided in the embodiment of the present application can also be executed by the terminal device 110, and accordingly, the transaction account management device can also be set in the terminal device 110, which is not particularly limited in this exemplary embodiment. For example, in an exemplary embodiment, the terminal device 110 generates authorization information to authorize the designated account of the first user to the second user, and performs corresponding operations based on the authorization information to display the designated account on the second graphical user interface.

[0061] The following is a detailed description of the transaction account management method provided by the present application in conjunction with specific implementation methods.

[0062] Figure 2 A flowchart of a transaction account management method provided by an embodiment of the present application is schematically shown. The method can be executed by a terminal device, such as Figure 1 The terminal device 110 shown; the method can also be executed by a server (or called a service end), such as Figure 1 The server 130 shown. Figure 2 As shown, the transaction account management method provided in the embodiment of the present application is executed by the server, including steps 210 to 240, which are as follows:

[0063] Step 210: Obtain authorization information initiated by the first user based on the first graphical user interface to authorize the designated account of the first user to the second user.

[0064] Specifically, the first graphical user interface is a graphical user interface provided by the first user client. The graphical user interface, also known as the graphical user interface (GUI), refers to a user interface of a computer operating environment that is displayed in a graphical manner, which is equivalent to the display interface of an electronic device. The client (Client), or user end, refers to an application provided by the content interaction platform, corresponding to the server, and providing local services to customers. The first user can log in to the first user client to open the first graphical user interface and then manage his account information through the first graphical user interface.

[0065] In the embodiment of the present application, a user can create multiple accounts on the client, and an account can be associated with at least two users through authorization operations. The first user first selects the account to be authorized from the multiple accounts displayed on the first graphical user interface as the designated account, and then configures the authorization object of the designated account, and at the same time configures the operation permissions that the authorization object can perform on the designated account. Then, authorization information can be generated based on the authorization object and the configured operation permissions. The authorization object mentioned here is the second user.

[0066] In one embodiment of the present application, Figure 3 As shown, the process of generating authorization information includes steps 310 to 330, specifically:

[0067] Step 310: Determine whether the account selected for authorization by the first user based on the first graphical user interface is an account of a specified type.

[0068] Specifically, an account has a corresponding account type, and the account types include an initiating authorization account, an authorized account, and an unauthorized account. If an account of the first user is an initiating authorization account, it indicates that the account is an account that the first user has authorized to other users. If an account of the first user is an authorized account, it indicates that the account is an account that other users have authorized to the first user. If an account of the first user is an unauthorized account, it indicates that the account has not been authorized, that is, the account is neither an account that the first user has authorized to other users, nor an account that other users have authorized to the first user.

[0069] In the embodiments of the present application, not all types of accounts can be authorized. Generally, the authorized account corresponding to the current user cannot be authorized by the current user to other users, because the authorized account is an account granted by other users to the current user for use, and the authorized account is not the current user's own account, so it cannot be authorized by the current user to other users for use.

[0070] In the embodiment of the present application, the account type that can be authorized is the account of the specified type. Generally, the account of the specified type is set as a non-authorized account. In some cases, the account of the specified type can also be the account that initiates the authorization. When generating the authorization information, it is first determined whether the account selected by the first user for authorization in the first graphical user interface is an account of the specified type, so as to determine whether the account selected by the user can perform the authorization operation.

[0071] In one embodiment of the present application, when the first user logs in to the first user client, the first user client obtains all accounts corresponding to the first user, then determines the type of each account, and sets a type identifier for the account according to the type of the account. The type identifier of each account is then displayed on the first graphical user interface, so that the first user can know the type of each account through the type identifier of each account. For example, the initiating authorization account is set to a green identifier, the authorized user is set to a red identifier, and the type identifier of the unauthorized user is set to empty. Then, in the first graphical user interface, when the first user sees that an account has a green identifier, it can be known that the account is an initiating authorization account; when the first user sees that an account has a red identifier, it can be known that the account is an authorized account; when the first user sees that an account has no identifier, it can be known that the account is an unauthorized account.

[0072] In one embodiment of the present application, an account filter control is set in the first graphical user interface, and the account filter control includes multiple menu items, each menu item corresponds to an account type, and when the first user selects one of the menu items, the first graphical user interface displays all accounts corresponding to the account type. For example, the menu items include an initiating authorization account, an authorized account, and an unauthorized account. When the first user selects the initiating authorization account item, all accounts of the initiating authorization account type are displayed in the first graphical user interface.

[0073] Furthermore, in this embodiment, the specified type of account includes user accounts that are safe, compliant, and have considerable investment returns. In this regard, in this embodiment, the candidate user selected by the first user can be evaluated based on user information, and the authorization parameters of the candidate user can be determined to measure the ability of the candidate user as the second user through the authorization parameters, and when the authorization parameters are less than the set threshold, the first user is reminded whether to continue to authorize the candidate user as the second user. After the first user confirms, the candidate user is treated as the second user and the corresponding processing continues.

[0074] Specifically, in this embodiment, the authorization parameter Par_aut can be determined by the user's credit Use_cre and the investment yield Use_pro. For example, the authorization parameter Par_aut of the candidate user is calculated by the following formula:

[0075] Par_aut=log2(α·Use_cre+β·Use_pro)

[0076] Among them, α and β are setting parameters.

[0077] In this embodiment, the above-mentioned method can improve the security and reliability of user account authorization and management, ensure the account security and yield rate of user authorized transactions, and reduce the risk of account authorization.

[0078] Step 320: If the account used for authorization is an account of a specified type, the account used for authorization is used as the specified account, and authorization information for authorizing the specified account to the second user is generated according to the specified account and the authorization configuration information of the specified account.

[0079] Specifically, if the account selected by the first user for authorization is an account of a specified type, it indicates that the account can perform authorization operations, and the account is the designated account for authorization. When the first user initiates the authorization operation of the designated account, it is also necessary to configure the authorization configuration information of the designated account. The authorization configuration information is to configure the permissions that the second user can use to operate the designated account, for example, the fund permissions and transaction permissions that the second user can use when using the designated account. Authorization information can be generated based on the designated account and its authorization configuration information, and of course, the authorization object, that is, the relevant information of the second user.

[0080] Step 330: If the account used for authorization is not an account of the specified type, a prompt message indicating that the authorization account selection is incorrect is sent to the first user, so that the first user can reselect an account for authorization.

[0081] In one embodiment of the present application, if the account selected by the first user is not an account of the specified type, it means that the selected account cannot be authorized, and a prompt message indicating that the authorized account selection is wrong is sent to the first user, for example, an error message prompt box is popped up in the first graphical user interface. After receiving the prompt message, the first user knows that the wrong type of account has been selected, and thus changes the selected account and selects the correct account of the specified type.

[0082] Continue to refer Figure 2 , step 220, sending the authorization information to the second user client, so that the second user client returns an authorization agreement with the second user's signature based on the authorization information.

[0083] Specifically, after obtaining the authorization information, the authorization object in the authorization information, that is, the second user, is determined, and then the authorization information is sent to the second user client. The second user client generates an authorization agreement based on the authorization information. The authorization agreement includes the authorized parties, the account used for authorization, and the authorization configuration information of the account. The authorized parties include the first user and the second user. The second user client displays the authorization agreement on the second graphical user interface so that the second user can know the specific authorization matters. If the second user agrees to the relevant authorization matters, the second user signs the authorization agreement. The second client can obtain the authorization agreement with the second user's signature and return it to the server.

[0084] In one embodiment of the present application, in order to prevent the signature information of the second user from being tampered with, the second user client can encrypt the authorization agreement with the second user's signature and then return it to the server. The encryption process specifically includes: the second user client generates an electronic signature file based on the authorization agreement with the second user's signature, then extracts the digital summary in the electronic signature file through a hash algorithm, and then uses the signature private key to perform asymmetric encryption (such as RSA encryption) on the digital summary to generate a digital signature. Finally, the digital signature and the public key of the electronic signature file and the signature certificate are encapsulated together to form a signature authorization agreement, which is returned to the server. It can be understood that the above encryption process can also be executed after the server receives the authorization agreement with the second user's signature.

[0085] Continue to refer Figure 2 , step 230, obtain the first user's signature on the authorization agreement, and perform a legitimacy check on the signed authorization agreement.

[0086] Specifically, an authorization agreement needs to be signed by all authorized parties before it can take effect. Therefore, after obtaining the authorization agreement with the signature of the second user, the authorization agreement is sent to the first user's client so that the first user signs the authorization agreement, thereby obtaining a complete authorization agreement. It can be understood that in order to prevent information leakage, the authorization agreement signed by the first user can also be encrypted. The encryption method is similar to the encryption method for the authorization agreement signed by the second user described above, which will not be repeated here.

[0087] After obtaining the fully signed authorization agreement, it is necessary to verify the legitimacy of the authorization agreement, that is, to verify whether the signature of the first user and the signature of the second user are both legal. If both the signature of the first user and the signature of the second user are legal, the verification is considered to have passed, and the authorization of the specified account is successful and effective. If one of the two is illegal, the authorization agreement verification fails, and a fully signed authorization agreement needs to be regenerated.

[0088] In one embodiment of the present application, when at least one of the first user's signature and the second user's signature is illegal, a fully signed authorization agreement can be regenerated based on the illegal object. For example, if the illegal object is the first user's signature, the authorization agreement is re-displayed on the first graphical user interface so that the first user can re-sign. If the illegal object is the second user's signature, the authorization information is re-sent to the second user's client so that the second user can sign the authorization agreement based on the re-sent authorization information. If both the first user's signature and the second user's signature are illegal, the authorization information is regenerated, and the process returns to step 210.

[0089] In one embodiment of the present application, when verifying the authorization agreement, the server first decrypts the digital signature with the public key, derives the digital summary, and performs the same hash algorithm on the electronic signature file to obtain a new digital summary, and compares the hash values ​​of the two summaries. If the two hash values ​​are the same, it means that the signature verification has passed; otherwise, it is invalid. It is understandable that the authorization agreement verification can also be performed through manual review.

[0090] In one embodiment of the present application, if the number of illegal times during the verification process reaches a certain threshold, there may be an abnormality in the identity of the authorized participant. At this time, in order to prevent account information leakage, the corresponding designated account is locked and the designated account is not allowed to perform authorized operations within a preset period of time.

[0091] Continue to refer Figure 2 , step 240, if the signed authorization agreement verification passes, then initiate an account information change message to the second user client, so that the second user client displays the specified account on the second graphical user interface of the second user client according to the account information change message.

[0092] Specifically, when the signed authorization agreement passes the verification, it means that the authorization is effective. On the server side, the designated account has been assigned to the second user name, but for the second user client, if there is no notification information, the second user client will not be able to update the second user's account data. Therefore, it is necessary to initiate an account information change message to the second user client. When the second user client receives the account information change message, it obtains the second user's account information from the server side. Since the second user's account information stored on the server side includes the designated account, the second user client can display the designated account on the second graphical user interface based on the second user's account information returned by the server, and then the second user can use the designated account through the second graphical user interface.

[0093] For example, Figure 4 The flowchart of a transaction account management method provided by an embodiment of the present application is schematically shown, and the method is executed by a client. Figure 4 As shown, the method includes:

[0094] S410: The first user sets a designated account for authorization, an authorized recipient (ie, the second user), transaction authority, and fund authority. The first user client generates authorization information for the designated account and sends it to the second user client.

[0095] S420: The second user client confirms the authorization information and the aforementioned authorization agreement, generates an authorization agreement with the second user's signature, and returns it to the first user client.

[0096] S430: The first user client receives the authorization agreement with the second user's signature, and obtains the first user's signature to form a complete authorization agreement.

[0097] S440: The first user client verifies and reviews the complete authorization agreement. The verification and review is performed by a manual customer service. If the verification passes, the authorization is successful, otherwise, the authorization fails.

[0098] In the technical solution provided in the embodiment of the present application, the authorization information of the designated account is sent to the second user client to obtain an authorization agreement with the second user's signature, and then the first user signs to form a complete authorization agreement, and the authorization agreement is verified. When the verification passes, the second user can use the designated account, thereby authorizing the first user's account to be used by the second user, that is, account sharing is realized. The authorization process is signed and verified to ensure the security of account authorization.

[0099] In one embodiment of the present application, the process of the second user client obtaining information related to the specified account includes: the second user client registers a listener for listening to account information change messages; when the listener listens to the account information change message, the second user client initiates an account information acquisition request to the server; receives target account information feedback from the server based on the account information acquisition request, the target account information includes the specified account; updates the second graphical user interface of the second user client according to the target account information, so that the specified account is displayed on the second graphical user interface.

[0100] Specifically, the listener can monitor specific events, which can be method calls or property changes. When the above specific events occur in the monitored object, a method of the listener will be executed immediately. The second user client registers a listener to monitor account information change messages. When the listener receives an account information change message, it will immediately initiate an account information acquisition request to the server. The account information acquisition request is initiated by the second user client to the server to obtain all account information of the second user. After receiving the account information acquisition request, the server will return the target account information of the second user at the current moment to the second user client. The target account information is the latest account information of the second user at the current moment, including the designated account that has been successfully authorized. The second user client displays the relevant information indicated by the target account information on the second graphical user interface, and the second user can use the designated account to perform related operations.

[0101] In one embodiment of the present application, when the second user uses a designated account to conduct a related transaction, the transaction data can be verified according to the authorization configuration information of the designated account. If the transaction data is verified, the second user is allowed to use the designated account to conduct the current transaction. If the transaction data is not verified, the second user is prohibited from using the designated account to conduct the current transaction. The transaction data is verified, including verification of fund authority, transaction authority, etc. For example, verifying whether the transaction funds of the current transaction exceed the funds set by the fund authority, verifying whether the transaction object of the current transaction is within the transaction object defined by the transaction authority, etc.

[0102] In one embodiment of the present application, if the authorization of a designated account needs to be canceled, the first user only needs to perform a cancellation authorization operation on the designated account in the first graphical user interface, and no operation is required by the second user.

[0103] For example, Figure 5 The flowchart of the second user client obtaining the designated account provided by one embodiment of the present application is schematically shown. Figure 5 As shown, the method includes:

[0104] S510: The second user client registers a listener for listening to account information change messages.

[0105] S520: The server sends an account information change message to the second user client.

[0106] S530: The listener of the second user client listens to the account information change message, and the second user client initiates an account information acquisition request to the server. The account information acquisition request is used to pull target account information from the server. The target account information is all account information of the second user including the specified account.

[0107] S540: The second user client receives the target account information fed back by the server based on the account information acquisition request, and updates the second graphical user interface of the second user client according to the target account information, so that the designated account is displayed on the second graphical user interface.

[0108] It should be noted that although the steps of the method in the present application are described in a specific order in the drawings, this does not require or imply that the steps must be performed in this specific order, or that all the steps shown must be performed to achieve the desired results. Additionally or alternatively, some steps may be omitted, multiple steps may be combined into one step, and / or one step may be decomposed into multiple steps, etc.

[0109] The following introduces an embodiment of the device of the present application, which can be used to execute the transaction account management method in the above-mentioned embodiment of the present application. Figure 6The structure block diagram of the transaction account management device provided in the embodiment of the present application is schematically shown. Figure 6 As shown, the transaction account management device provided in the embodiment of the present application includes:

[0110] The authorization information acquisition module 610 is used to acquire authorization information initiated by a first user based on a first graphical user interface to authorize a designated account of the first user to a second user;

[0111] The authorization agreement acquisition module 620 is used to send the authorization information to the second user client, so that the second user client returns the authorization agreement with the second user's signature based on the authorization information;

[0112] Verification module 630, used to obtain the signature of the first user on the authorization agreement and perform a validity verification on the signed authorization agreement;

[0113] The information sending module 640 is used to initiate an account information change message to the second user client if the signed authorization agreement verification passes, so that the second user client displays the specified account on the second graphical user interface of the second user client according to the account information change message.

[0114] In one embodiment of the present application, the verification module 630 is specifically used to:

[0115] Verifying the first user signature and the second user signature in the signed authorization agreement respectively to determine whether the first user signature and the second user signature are legal;

[0116] If both the first user signature and the second user signature are legal, then determining that the signed authorization agreement verification has passed;

[0117] If at least one of the first user signature and the second user signature is illegal, it is determined that the signed authorization protocol verification fails.

[0118] In one embodiment of the present application, the verification module 630 is further used to:

[0119] If the signed authorization agreement fails the verification, a re-signed authorization agreement is obtained and the legitimacy of the re-signed authorization agreement is verified.

[0120] In one embodiment of the present application, the authorization information acquisition module 610 is specifically used to:

[0121] determining whether the account selected for authorization by the first user based on the first graphical user interface is an account of a specified type;

[0122] If the account used for authorization is an account of a specified type, the account used for authorization is used as a specified account, and authorization information for authorizing the specified account to the second user is generated according to the specified account and the authorization configuration information of the specified account.

[0123] In one embodiment of the present application, the authorization information acquisition module 610 is also used to: if the account used for authorization is not an account of a specified type, send a prompt message to the first user indicating that the authorization account selection is incorrect, so that the first user reselects the account used for authorization.

[0124] In one embodiment of the present application, the device further includes:

[0125] An account type determination module, used to determine the type of each account of the first user, and set a type identifier for each account according to the type of each account;

[0126] The account display module is used to display the type identification of each account on the first graphical user interface, so that the first user can know the type of each account through the type identification of each account.

[0127] In one embodiment of the present application, the second user client is specifically used for:

[0128] Register a listener to monitor account information change messages;

[0129] When the listener listens to the account information change message, the second user client initiates an account information acquisition request to the server;

[0130] Receiving target account information fed back by the server based on the account information acquisition request, the target account information including the designated account;

[0131] The second graphical user interface of the second user client is updated according to the target account information so that the designated account is displayed on the second graphical user interface.

[0132] The specific details of the transaction account management device provided in each embodiment of the present application have been described in detail in the corresponding method embodiment and will not be repeated here.

[0133] Figure 7 The structure block diagram of a computer system for implementing an electronic device according to an embodiment of the present application is schematically shown.

[0134] It should be noted that Figure 7 The computer system 700 of the electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0135] like Figure 7 As shown, the computer system 700 includes a central processing unit 701 (CPU), which can perform various appropriate actions and processes according to the program stored in the read-only memory 702 (ROM) or the program loaded from the storage part 708 to the random access memory 703 (RAM). Various programs and data required for system operation are also stored in the random access memory 703. The central processing unit 701, the read-only memory 702 and the random access memory 703 are connected to each other through a bus 704. An input / output interface 705 (Input / Output interface, i.e., I / O interface) is also connected to the bus 704.

[0136] The following components are connected to the input / output interface 705: an input section 706 including a keyboard, a mouse, etc.; an output section 707 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker; a storage section 708 including a hard disk, etc.; and a communication section 709 including a network interface card such as a LAN card, a modem, etc. The communication section 709 performs communication processing via a network such as the Internet. A drive 710 is also connected to the input / output interface 705 as needed. A removable medium 711, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 710 as needed so that a computer program read therefrom is installed into the storage section 708 as needed.

[0137] In particular, according to an embodiment of the present application, the process described in each method flow chart can be implemented as a computer software program. For example, an embodiment of the present application includes a computer program product, which includes a computer program carried on a computer readable medium, and the computer program contains a program code for executing the method shown in the flow chart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 709, and / or installed from the removable medium 711. When the computer program is executed by the central processor 701, various functions defined in the system of the present application are executed.

[0138] It should be noted that the computer-readable medium shown in the embodiment of the present application may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, but not limited to, a system, device or device of electricity, magnetism, light, electromagnetic, infrared, or semiconductor, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a flash memory, an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present application, a computer-readable storage medium may be any tangible medium containing or storing a program, which may be used by an instruction execution system, device or device or used in combination with it. In the present application, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, wherein a computer-readable program code is carried. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer readable signal media may also be any computer readable medium other than computer readable storage media, which may send, propagate, or transmit programs for use by or in conjunction with an instruction execution system, apparatus, or device. The program code contained on the computer readable medium may be transmitted using any suitable medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

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

[0140] It should be noted that, although several modules or units of the equipment for action execution are mentioned in the above detailed description, this division is not mandatory. In fact, according to the embodiments of the present application, the features and functions of two or more modules or units described above can be embodied in one module or unit. On the contrary, the features and functions of one module or unit described above can be further divided into being embodied by multiple modules or units.

[0141] Through the description of the above implementation methods, it is easy for those skilled in the art to understand that the example implementation methods described here can be implemented by software or by combining software with necessary hardware. Therefore, the technical solution according to the implementation methods of the present application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which can be a personal computer, a server, a touch terminal, or a network device, etc.) to execute the method according to the implementation methods of the present application.

[0142] Those skilled in the art will readily appreciate other embodiments of the present application after considering the specification and practicing the invention disclosed herein. The present application is intended to cover any modification, use or adaptation of the present application, which follows the general principles of the present application and includes common knowledge or customary technical means in the art that are not disclosed in the present application.

[0143] It should be understood that the present application is not limited to the precise structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present application is limited only by the appended claims.

Claims

1. A method for managing a trading account, characterized in that: include: determining whether the account selected for authorization by the first user based on the first graphical user interface is an account of a specified type; If the account used for authorization is an account of a specified type, the account used for authorization is used as a specified account, and authorization information for authorizing the specified account to the second user is generated according to the specified account and the authorization configuration information of the specified account; Sending the authorization information to the second user client, so that the second user client returns an authorization agreement with the second user's signature based on the authorization information; Obtaining the first user's signature on the authorization agreement, and performing a validity verification on the signed authorization agreement; If the signed authorization agreement is verified to be successful, an account information change message is sent to the second user client, so that the second user client displays the designated account on the second graphical user interface of the second user client according to the account information change message.

2. The method for managing a trading account according to claim 1, characterized in that: Perform a validity check on the signed authorization agreement, including: Verifying the first user signature and the second user signature in the signed authorization agreement respectively to determine whether the first user signature and the second user signature are legal; If both the first user signature and the second user signature are legal, then determining that the signed authorization agreement verification has passed; If at least one of the first user signature and the second user signature is illegal, it is determined that the signed authorization protocol verification fails.

3. The method for managing a trading account according to claim 1, characterized in that: The method further comprises: If the signed authorization agreement fails the verification, a re-signed authorization agreement is obtained and the legitimacy of the re-signed authorization agreement is verified.

4. The method for managing a trading account according to claim 1, characterized in that: If the account used for authorization is not an account of the specified type, a prompt message indicating that the authorization account selection is incorrect is sent to the first user, so that the first user reselects an account for authorization.

5. The method for managing a trading account according to claim 1, characterized in that: The method further comprises: Determining the type of each account of the first user, and setting a type identifier for each account according to the type of each account; The type identification of each account is displayed on the first graphical user interface, so that the first user can know the type of each account through the type identification of each account.

6. The method for managing a trading account according to claim 1, characterized in that: Displaying the designated account on a second graphical user interface of the second user client according to the account information change message includes: Register a listener to monitor account information change messages; When the listener listens to the account information change message, the second user client initiates an account information acquisition request to the server; Receiving target account information fed back by the server based on the account information acquisition request, the target account information including the designated account; The second graphical user interface of the second user client is updated according to the target account information so that the designated account is displayed on the second graphical user interface.

7. A transaction account management device, characterized in that: include: an authorization information acquisition module, used to determine whether the account selected for authorization by the first user based on the first graphical user interface is an account of a specified type; If the account used for authorization is an account of a specified type, the account used for authorization is used as a specified account, and authorization information for authorizing the specified account to the second user is generated according to the specified account and the authorization configuration information of the specified account; An authorization agreement acquisition module, used to send the authorization information to the second user client, so that the second user client returns an authorization agreement with the second user's signature based on the authorization information; A verification module, used to obtain the signature of the first user on the authorization agreement and perform a legality verification on the signed authorization agreement; An information sending module is used to initiate an account information change message to the second user client if the signed authorization agreement verification passes, so that the second user client displays the specified account on the second graphical user interface of the second user client according to the account information change message.

8. A computer readable medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method for managing a trading account described in any one of claims 1 to 6 is implemented.

9. An electronic device, characterized in that: include: processor; as well as A memory, configured to store executable instructions of the processor; The processor executes the executable instructions so that the electronic device executes the transaction account management method described in any one of claims 1 to 6.

Images