Account management method in payment platform and computing device

Abstract

An account management method in a payment platform and a computing device. A first account of a first user and a second account of a second user are registered in a server of the payment platform. The second account comprises a first sub-account, a first account relationship between the first account and the second account is recorded on the server, and the first account relationship is used for indicating that the first account has management authority over the first sub-account. The method comprises: receiving, from a first terminal corresponding to the first account, a management request initiated for the first sub-account; and, on the basis of the first account relationship and the management request, updating account information of the first sub-account.

Description

Account management method in payment platform and computing device

[0001] The present application claims priority from the Chinese patent application No. 202411268094.0 filed on September 11, 2024, and entitled "Account management method in payment platform and computing device", the content of which is incorporated herein by reference in its entirety. TECHNICAL FIELD

[0002] The embodiments of the present specification belong to the technical field of computer technology, and particularly relate to an account management method in a payment platform and a computing device. BACKGROUND

[0003] With the development of Internet technology and social economy, people have become more and more accustomed to using payment platforms for transactions or investment operations. For example, when a user purchases goods at a physical store or a commodity trading platform, he or she may use an account registered in a payment platform to pay for the goods. For another example, a user may use an account registered in a payment platform to purchase a specific financial product. For some specific user groups, such as teenagers and the elderly with relatively poor cognitive abilities, these specific user groups often face problems such as falling victim to online fraud, making improper consumption, or making excessive consumption when using payment platforms. SUMMARY

[0004] The purpose of the present application is to provide an account management method in a payment platform and a computing device.

[0005] In a first aspect, an account management method in a payment platform is provided. The service end of the payment platform registers a first account of a first user and a second account of a second user. The second account includes a first sub-account. The service end records a first account relationship between the first account and the second account. The first account relationship is used to indicate that the first account has management authority over the first sub-account. The method includes: receiving, from a first terminal corresponding to the first account, a management request initiated on the first sub-account; and updating account information of the first sub-account according to the first account relationship and the management request.

[0006] In a second aspect, an account management method in a payment platform is provided. The payment platform has a server end registering a first account of a first user and a second account of a second user. The second account includes a first sub-account. The server end records a first account relationship between the first account and the second account. The first account relationship indicates that the first account has a management privilege over the first sub-account. The method is performed by a first terminal corresponding to the first account. The method includes: obtaining first configuration information of the first sub-account according to a first interaction interface corresponding to the first sub-account; generating a management request for the first sub-account according to the first configuration information; and sending the management request to the server end.

[0007] In a third aspect, an account management method in a payment platform is provided. The payment platform has a server end registering a first account of a first user and a second account of a second user. The second account includes a first sub-account. The server end records a first account relationship between the first account and the second account. The first account relationship indicates that the first account has a management privilege over the first sub-account. The method is performed by a second terminal corresponding to the second account. The method includes: receiving at least part of account information of the second account from the server end. The at least part of account information of the second account includes at least part of account information of the first sub-account; and displaying a fourth interaction interface corresponding to the second account. The fourth interaction interface includes the at least part of account information of the second account.

[0008] In a fourth aspect, an account management method in a payment platform is provided. The payment platform has a server end registering a first account of a first user and a second account of a second user. The second account includes a first sub-account. The server end records a first account relationship between the first account and the second account. The first account relationship indicates that the first account has a management privilege over the first sub-account. The method includes: obtaining first configuration information of the first sub-account through a first interaction interface corresponding to the first account. The first interaction interface is used to display and configure at least part of account information of the first sub-account; and updating display information in the first interaction interface according to the first configuration information.

[0009] In a fifth aspect, a server of a payment platform is provided. The server registers a first account of a first user and a second account of a second user. The second account includes a first sub-account. The server records a first account relationship between the first account and the second account. The first account relationship indicates that the first account has a management right on the first sub-account. The payment platform includes a communication processing unit configured to receive a management request initiated on the first sub-account from a first terminal corresponding to the first account; and a transaction processing unit configured to update account information of the first sub-account according to the first account relationship and the management request.

[0010] In a sixth aspect, a terminal is provided. The terminal is involved in a server of a payment platform that registers a first account of a first user and a second account of a second user. The second account includes a first sub-account. The server records a first account relationship between the first account and the second account. The first account relationship indicates that the first account has a management right on the first sub-account. The terminal corresponds to the first account. The terminal includes an information obtaining unit configured to obtain first configuration information of the first sub-account according to a first interaction interface corresponding to the first sub-account; a request generating unit configured to generate a management request on the first sub-account according to the first configuration information; and a communication processing unit configured to send the management request to the server.

[0011] In a seventh aspect, a terminal is provided. The terminal is involved in a server of a payment platform that registers a first account of a first user and a second account of a second user. The second account includes a first sub-account. The server records a first account relationship between the first account and the second account. The first account relationship indicates that the first account has a management right on the first sub-account. The terminal corresponds to the second account. The terminal includes a communication processing unit configured to receive at least part of account information of the second account from the server. The at least part of account information of the second account includes at least part of account information of the first sub-account; and a display processing unit configured to display a fourth interaction interface corresponding to the second account. The fourth interaction interface includes the at least part of account information of the second account.

[0012] In an eighth aspect, a computer readable storage medium is provided. The computer readable storage medium stores a computer program. When the computer program is executed in a computing device, the computing device performs the method in the first, second, third, or fourth aspect.

[0013] In a ninth aspect, a computing device is provided, including a memory and a processor, the memory having stored therein executable code which, when executed by the processor, implements the method of the first, second, third, or fourth aspects.

[0014] In the technical solution provided by the embodiments of the present specification, the first account of the first user and the second account of the second user are registered in the service end of the payment platform, and the service end records the first account relationship between the first account and the second account, which is used to indicate that the first account has the management authority for the first sub-account included in the second account; the first user can use the first account to initiate a corresponding management request to the service end for the first sub-account included in the second account, so that the service end updates the account information of the first sub-account according to the first account relationship and the management request. In this way, under the premise of meeting the condition that the second user can independently use the first sub-account included in the second account, the first user can also manage the use of the first sub-account by the second user by updating the account information of the first sub-account, which is conducive to avoiding the problems of network fraud, improper consumption, or excessive consumption, etc. that the second user may encounter in the process of using the first sub-account, while taking into account the convenience and security of the second user using the payment platform. BRIEF DESCRIPTION OF DRAWINGS

[0015] In order to more clearly illustrate the technical solutions of the embodiments of the present specification, the drawings needed in the embodiment description will be briefly introduced below. Obviously, the drawings in the following description are only some embodiments described in the present specification, and other drawings can also be obtained according to these drawings without creative labor.

[0016] FIG. 1 is a schematic diagram of a process of establishing an account relationship provided in an embodiment of the present specification;

[0017] FIG. 2 is a schematic diagram of a process of establishing an account relationship provided in an embodiment of the present specification;

[0018] FIG. 3 is a schematic diagram of setting a sub-account for a second account provided in an embodiment of the present specification;

[0019] FIG. 4 is a flowchart of an account management method in a payment platform provided in an embodiment of the present specification;

[0020] FIG. 5 is a schematic diagram of an interaction interface corresponding to a second account provided in an embodiment of the present specification;

[0021] FIG. 6 is a schematic diagram of an interaction interface corresponding to a first account provided in an embodiment of the present specification;

[0022] FIG. 7 is a flowchart of a second embodiment of an account management method in a payment platform according to the present disclosure;

[0023] FIG. 8 is a schematic diagram of a server in a payment platform according to the present disclosure;

[0024] FIG. 9 is a schematic diagram of a terminal according to the present disclosure;

[0025] FIG. 10 is a schematic diagram of a terminal according to the present disclosure. DETAILED DESCRIPTION

[0026] In order to enable those skilled in the art to better understand the technical solutions in the present specification, the technical solutions in the embodiments of the present specification will be described clearly and completely below with reference to the drawings. Obviously, the described embodiments are only some of the embodiments of the present specification, rather than all the embodiments. Based on the embodiments in the present specification, all other embodiments obtained by those skilled in the art without creative work should fall within the scope of protection of the present specification.

[0027] For some special users, such as teenagers and the elderly with relatively poor cognitive abilities, these special users often face problems such as network fraud, improper consumption, or excessive consumption when using the payment platform. Other users, such as parents of teenagers (including but not limited to parents of teenagers) or friends of the elderly (including but not limited to adult children of the elderly), have management needs for the use of the payment platform by the relevant special users in order to avoid problems such as network fraud, improper consumption, or excessive consumption as much as possible when the relevant special users use the payment platform.

[0028] In the related art, taking Alipay Family Card as an example, the Family Card is essentially a pure fund relationship between two independent platform accounts in the payment platform. For example, user A donates a Family Card to user B through the platform account A held by user A, and sets a consumption limit for the Family Card. User B can use the Family Card to make payments in some consumption scenarios. When user B uses the Family Card to make payments, the server of Alipay needs to initiate a round of deductions from the payment channels (balance, balance treasure, bank card, etc.) bound to the platform account A until the deduction is successful.

[0029] In the related art, there are many problems: user B needs to hold a platform account, and for some user groups such as minors, they usually do not have their own mobile phone numbers or email addresses, and may not be able to open a platform account and use a family card; there is no certainty of transaction for user B, if the platform account A is successfully deducted, the user B payment is successful, if the platform account A is failed to deduct, the user B payment is failed; in a use cycle, the amount of the family card is fixed, which may not meet the use demand of user B, and cannot meet the adjustment demand of user A on the amount; for user A, it is difficult to control the payment channel of the actual use of the family card; user A cannot control the consumption scene of user B, and the like.

[0030] At least one account management method in a payment platform and a computing device terminal are provided in the embodiments of the present specification. A first account of a first user and a second account of a second user are registered in a server of the payment platform, and the server records a first account relationship between the first account and the second account, which is used to indicate that the first account has a management permission for a first sub-account included in the second account. The first user can initiate a corresponding management request to the server for the first sub-account included in the second account by using the first account, so that the server updates account information of the first sub-account according to the first account relationship and the management request. In this way, on the premise that the second user can independently use the first sub-account included in the second account, the first user can also manage the use of the first sub-account by the second user by updating the account information of the first sub-account, thereby helping to avoid problems such as network fraud, improper consumption, or excessive consumption of the second user in the process of using the first sub-account, and can balance the convenience and security of the second user using the payment platform.

[0031] In addition, for the problem that minors cannot open a platform account and use a family card, in the technical solution provided by the embodiments of the present specification, a parent can open a platform account for a child in the payment platform and manage the use of a first sub-account of the platform account by the child; the parent reduces the management of the first sub-account in the platform account of the child after the child grows up as a teenager, and the teenager can use a second sub-account which is not managed; the parent stops managing the first sub-account after the teenager becomes an adult, so that the adult can continue to use the payment and financial functions of the second sub-account in the platform account, so that the platform account can gradually transition from a platform account suitable for children to an account suitable for adults.

[0032] Hereinafter, the process of the parents managing the use of the payment platform by the teenagers will be exemplarily described. That is, the second user can be a teenager such as "XX", and the first user can be the parent of "XX", such as the father "XA" or the mother "XB". Correspondingly, the first account can be the platform account registered by "XA" in the service end of the payment platform, such as "account A", or can also be the platform account registered by "XB" in the service end, such as "account B", and the second account can be the platform account registered by "XX" in the service end, such as "z***o".

[0033] Firstly, the process of the service end of the payment platform recording the first account relationship between the first account and the second account will be described. It can be understood that the payment platform can adopt a client / server architecture or a browser / server architecture.

[0034] The recording of the first account relationship can include two opening modes of the first user main visit and the second user invitation.

[0035] In the first user main visit opening mode, if the second user has not registered the second account in the service end of the payment platform, the first user can register the second account for the second user through the first terminal corresponding to the first account, and then the service end records the first account relationship between the first account and the second account. If the second user has registered the second account in the service end, the first user can invite the second user, and when the second user confirms to allow the establishment of the first account relationship between the first account and the second account, the service end records the first account relationship between the first account and the second account. When the first user successfully logs in / connects the service end of the payment platform by using the first account in a terminal, the terminal becomes the first terminal corresponding to the first account; the first user can trigger the first terminal to receive and display the second interaction interface corresponding to the first account from the service end, such as the interface P1 shown in FIG. 2, and then trigger the first terminal to perform one or more rounds of information interaction with the service end through the interface P1, so as to finally make the service end complete the recording of the first account relationship between the first account and the second account.

[0036] For example, referring to FIG. 2, when the second account of the second user is not registered in the server: the first user can first trigger a specific region, such as an image region corresponding to the "create account" text, in the interface P1, so that the first terminal displays another interactive interface, such as the interface P2; then, the identity information of the second user, such as the type of the certificate, the number of the certificate, and the name of the user, can be inputted / selected in the interface P2, and the first terminal displays another interactive interface, such as the interface P3, by triggering a specific region, such as an image region corresponding to the "next" text, in the interface P2; finally, the second account to be registered, such as "z***o", and the corresponding account password can be inputted in the interface P3, and the first terminal sends a first relationship creation request to the server of the payment platform by triggering a specific region, such as an image region corresponding to the "confirm" text, in the interface P3, wherein the first relationship creation request can include the identity information of the second user, the second account "z***o", and the corresponding account password, so that the server registers the second account "z***o" in the server according to the first relationship creation request, and records the first account relationship between the first account, such as "account A", and the second account, such as "z***o".

[0037] For example, referring to FIG. 2, when the second account of the second user is not registered in the server: the first user can first trigger a specific region, such as an image region corresponding to the "create account" text, in the interface P1, so that the first terminal displays another interactive interface, such as the interface P2; then, the identity information of the second user, such as the type of the certificate, the number of the certificate, and the name of the user, can be inputted / selected in the interface P2, and the first terminal displays another interactive interface, such as the interface P3, by triggering a specific region, such as an image region corresponding to the "next" text, in the interface P2; finally, the second account to be registered, such as "z***o", and the corresponding account password can be inputted in the interface P3, and the first terminal sends a first relationship creation request to the server of the payment platform by triggering a specific region, such as an image region corresponding to the "confirm" text, in the interface P3, wherein the first relationship creation request can include the identity information of the second user, the second account "z***o", and the corresponding account password, so that the server registers the second account "z***o" in the server according to the first relationship creation request, and records the first account relationship between the first account, such as "account A", and the second account, such as "z***o".

[0038] In the second user invitation opening mode, the second user can invite the first user, and when the first user confirms to allow the establishment of the first account relationship between the first account and the second account, the payment platform records the first account relationship between the first account and the second account. For example, when the first user successfully logs in / connects to the service end of the payment platform by using the second account in a terminal, the terminal becomes the second terminal corresponding to the second account; the second user can trigger the first terminal to send a second relationship creation request for indicating the establishment of the first account relationship to the service end through a corresponding interactive interface, and the service end can provide second prompt information to the first terminal according to the second relationship creation request, so that the first user triggers the first terminal to return second response information corresponding to the second prompt information to the service end. If the second response information indicates that the first user allows to record the first account relationship, the service end can record the first account relationship between the first account, for example, “account A”, and the second account “z***o”.

[0039] After the service end completes the recording of the first account relationship between the first account and the second account, the service end can automatically or at the request of the first terminal corresponding to the first account configure one or multiple sub-accounts with different purposes for the second account. In addition, the first user can configure the account information of the sub-account, such as the pocket money account, according to the different growth stages of the young children.

[0040] For example, referring to FIG. 3, the young children in the primary school stage may need the second account to make daily expenses with low frequency and low amount, such as using the second account to independently purchase snacks, toys, stationery and the like in the school; the parents need to strictly limit the use of the second account, such as prohibiting the use of the second account in online consumption scenarios, limiting the consumption frequency and consumption amount of the second account in offline consumption scenarios. The young children in the middle school stage need to use the second account to make daily expenses with relatively high frequency and relatively large amount, and there may be private consumption that the parents do not expect to know due to privacy, and the young children may expect to make limited online consumption due to improved cognition; the parents need to appropriately relax the restrictions on the use of the second account, such as increasing the consumption frequency, increasing the consumption amount, and no longer limiting the online consumption scenarios, and the like. After the young children enter the university stage, they have strong cognitive ability, and the parents can give up the management of the second account.

[0041] Moreover, the parents can also manage the children's money for various possible purposes, such as managing the small amount of money obtained by the teenagers, such as the red envelopes received from relatives and friends, the scholarship, and the New Year money, which can be relatively small in amount and can be gradually used by the teenagers during their growth, and thus can have a relatively small value-added demand; the parents can also prepare a relatively large amount of education fund or other reserve fund for the children within their ability, which can be used by the teenagers as needed after they grow up, and thus can have a relatively large value-added demand due to the relatively large amount and the small frequency of use.

[0042] In summary, the second account held by the teenager can be configured with a pocket money sub-account (account type belongs to a payment account that can be used for payment purposes), a current financial management sub-account, an education financial management sub-account, and a balance sub-account (or called a default balance account or a second sub-account). The funds in the pocket money sub-account mainly support the second user to make daily expenses; the funds in the current financial management sub-account and the education financial management sub-account can be used to purchase their respective financial products to obtain corresponding value-added; the funds in the balance sub-account are mainly used for private consumption by the second user that the parents do not expect to know. Among them, the first user has management authority over the pocket money sub-account, the current financial management sub-account, and the education financial management sub-account in the second account, and a specific sub-account such as the balance sub-account can not have management authority; in other words, the first sub-account can be the pocket money sub-account, the current financial management sub-account, or the education financial management sub-account in the second account.

[0043] The foregoing description of the sub-account is exemplary, for example, the second account held by the teenager can only be configured with a pocket money sub-account, a financial management sub-account, and a balance sub-account. In actual technical scenarios, the second account should at least include a pocket money sub-account for supporting daily expenses, and the sub-accounts configured for other various business purposes are optional and not mandatory.

[0044] After the service side completes the record of the first account relationship between the first account and the second account, the first user can use the first terminal corresponding to the first account to manage the first sub-accounts included in the second account as needed. The management of the first sub-account by the first user can be performed after the second user initiates an information update request for the first sub-account using the second terminal corresponding to the second account, or can be initiated by the first user according to his own will.

[0045] It should be noted that after the service end completes recording the first account relationship between the first account and the second account, the service end can also generate some new interaction interfaces according to the established first account relationship, such as the first interaction interface, the third interaction interface, and the fourth interaction interface described below, and add access links of these interaction interfaces to a specific interface provided by the payment platform, so that the relevant user can access these interaction interfaces through the specific interface in the terminal, and realize the account management method in the payment platform provided in each embodiment of the present specification through these interaction interfaces.

[0046] FIG. 4 is a flowchart of an account management method in a payment platform provided in an embodiment of the present specification. The method exemplarily describes a process in which a first user uses a first account registered in a service end of a payment platform to manage any first sub-account included in a second account registered in the service end of the payment platform by a second user.

[0047] Referring to FIG. 4, the method can include, but is not limited to, some or all of the following steps S401-S413.

[0048] When the second user successfully logs in / connects to the service end of the payment platform by using the second account in a terminal, the terminal becomes a second terminal corresponding to the second account. Similarly, when the first user successfully logs in / connects to the service end of the payment platform by using the first account in a terminal, the terminal becomes a first terminal corresponding to the first account.

[0049] When the second user expects to change the account information of a certain first sub-account included in the second account, or expects to perform a certain transaction using the second account, such as making a payment using a certain first sub-account, the second terminal can be triggered to perform the following step S401.

[0050] Step S401: obtaining at least part of the account information of the second account from the service end, wherein the at least part of the account information of the second account includes at least part of the account information of the first sub-account.

[0051] Step S403: displaying a fourth interaction interface corresponding to the second account, including at least part of the account information of the second account.

[0052] Exemplarily, referring to FIG. 5, after the second user logs in / connects to the service end of the payment platform by using the second account in a terminal, the terminal becomes a second terminal corresponding to the second account, and the corresponding interaction interface such as the interface P6 exemplified in FIG. 5 can be received and displayed from the service end under the trigger of the second user. In the interface P6, the user name of the second user such as “Shi XX”, the plaintext or ciphertext fund share of each sub-account included in the second account, and the state of each possible service provided by the service end for the second account can be included.

[0053] When the second user expects to change the account information of a certain first sub-account, the second terminal can be provided with corresponding second configuration information through the fourth interaction interface, and triggered to send a corresponding information change request to the server.

[0054] That is, the second terminal can also execute the following steps S405 and S407 under the trigger of the second user.

[0055] In step S405, the second terminal acquires the second configuration information of the first sub-account according to the fourth interaction interface.

[0056] In step S407, the second terminal sends an information change request corresponding to the first sub-account to the server according to the second configuration information.

[0057] Continuing with the example above, the interface P6 shown in FIG. 5 is taken as an example here.

[0058] When the second user expects to change the account information of the pocket money sub-account, such as the consumption limit, consumption frequency or consumption scenario set for the pocket money sub-account, the second user can trigger the image area corresponding to the “view limit” label in the interface P6 displayed by the second terminal, so that the second terminal displays another interaction interface, such as the interface P7; the interface P7 can include at least part of the account information of the pocket money sub-account, such as the daily consumption limit, daily consumption frequency and the on-off state of various consumption scenarios set for the pocket money sub-account, the daily consumption limit and the daily consumption frequency of the pocket money sub-account, etc. In the interface P7, the second user can input the consumption limit expected by the second user to the second terminal, for example, by triggering the image area corresponding to the “apply to change the consumption limit” label; for example, by triggering the image area corresponding to the “apply to change the consumption frequency” label, the second user can input the consumption frequency expected by the second user to the second terminal; for example, by triggering the image area corresponding to the “online consumption” label, the second user can input the indication information representing the second user's expectation to turn on the payment scenario “online consumption” to the second terminal. Finally, the second user can trigger the image area corresponding to the “confirm” label, for example, so that the second terminal takes one or more of the consumption limit, consumption frequency and indication information input by the second user through the interface P7 as the second configuration information of the pocket money sub-account by the second user, and sends an information change request corresponding to the pocket money sub-account to the server, which can include the second configuration information.

[0059] It should be particularly noted that the consumption scenario can be set in combination with actual business needs, for example, the online consumption scenario can be specifically divided into online shopping consumption and online game consumption, and here the managed consumption scenarios are not specifically limited.

[0060] When the second user desires to change the account information of the allowance sub-account, and the transfer-out permission set for the allowance sub-account, so that the second user has the transfer-out permission of the allowance sub-account, the second user can trigger a specific region, for example, an image region corresponding to the "transfer-out" word, in the interface P6 displayed by the second terminal, so that the second terminal can display another interactive interface, for example, the interface P8; and the second user can trigger a specific region, for example, an image region corresponding to the "contact immediately" word, in the interface P8, to realize inputting of the indication information representing the second user's desire to obtain the transfer-out permission to the second terminal, and sending of an information change request containing the indication information and corresponding to the allowance sub-account to the server. It should be noted that when the second user already has the transfer-out permission of the allowance sub-account, the second user can trigger a specific region, for example, an image region corresponding to the "transfer-out" word, to make the second terminal display another interactive interface for realizing a payment service, input a desired transfer-out fund share in the interactive interface, and cause the server to transfer funds from the allowance sub-account to other sub-accounts included in the second account or other platform accounts registered in the server according to the fund share input by the second user.

[0061] Similarly, when the second user desires to change the state of various services provided by the payment platform for the second account, for example, desires to bind or unbind a predetermined type of terminal, for example, a children's watch, to the first sub-account under the second account, or desires to start or stop a target service, for example, face payment, provided by the server for the first sub-account, the second user can trigger an image region corresponding to the "children's watch" or "face payment" word in the interface P6 to trigger the second terminal to send a corresponding information change request to the server.

[0062] The foregoing exemplary describes the process in which the second user triggers the second terminal to send a corresponding information change request to the server according to the fourth interactive interface displayed by the second terminal. However, it should be understood that the second user can also perform other forms of information interaction with the terminal through the fourth interactive interface to cause the second terminal to perform corresponding information interaction with the server to complete the transaction desired to be completed by the second user. For example, the second user can trigger an image region corresponding to the "collection" word in the interface P6 to make the second terminal display a collection code corresponding to the allowance sub-account, so that other users can scan the collection code to realize transfer of a corresponding share of funds into the allowance sub-account; for another example, the second user can trigger an image region corresponding to the "payment" word in the interface P6 to make the second terminal display a payment code, so that other users can scan the payment code to realize transfer of a corresponding share of funds from the allowance sub-account to other accounts except the second account; and for another example, the second user can trigger an image region corresponding to the "bill" word in the interface P6 to make the second terminal obtain and display a consumption bill of the allowance sub-account from the server.

[0063] In step S409, the server provides third prompt information to the first terminal corresponding to the first account according to the first account relationship and the information change request. The third prompt information can include the second configuration information included in the information change request received from the second terminal. After receiving the third prompt information, the first terminal can prompt the first user to read the third prompt information, so as to trigger the first user to implement the information change of the first sub-account.

[0064] In step S411, the first terminal acquires the first configuration information of the first sub-account according to the first interactive interface corresponding to the first sub-account, and generates a management request of the first sub-account according to the first configuration information.

[0065] In step S413, the first terminal sends the management request of the first sub-account to the server.

[0066] In a possible implementation, the first user can manage the first sub-account as described above in the case that the second user makes a request through the second terminal.

[0067] For example, the third prompt information can include the second configuration information, and correspond to the first interactive page in the first terminal. If the first user allows to modify the account information of the first sub-account according to the second configuration information, the first interactive interface can be opened in the first terminal, and the first terminal is provided with corresponding operations (such as input operation or confirmation operation) through the first interactive page, so as to provide the first terminal with the first configuration information corresponding to the second configuration information, and trigger the first terminal to send the management request containing the first configuration information to the server. Alternatively, the first user can modify part or all of the second configuration information in the first interactive interface containing the second configuration information, so that the second terminal obtains the first configuration information allowed by the first user, and then triggers the first terminal to send the management request containing the first configuration information to the server.

[0068] The foregoing steps S401-S409 are optional. The first user can also actively trigger the first terminal to send a management request for the first sub-account to the service end. For example, referring to FIG. 6, when the first user logs in the service end of the payment platform in a terminal, the terminal becomes the first terminal corresponding to the first account; the first terminal can obtain and display a first interaction interface corresponding to the first sub-account from the service end under the trigger of the user, for example, interface P9. The interface P9 can include the user name of the second user, for example, “XX”, the plaintext fund shares of part or all of the sub-accounts included in the second account (for example, the plaintext fund shares corresponding to each of the sub-accounts of which the first account has the management right), the states of various possible services provided by the service end for the second account, and the like. When the first user expects to change the account information of a certain first sub-account, the first terminal can be provided with corresponding first configuration information through the first interaction interface, and the first terminal is triggered to send a management request containing the first configuration information and corresponding to the first sub-account to the service end.

[0069] For example, when the first user desires to update the account information of the pocket money sub-account, the first terminal can be triggered to display another interactive interface, such as interface P11, by triggering the image area corresponding to the word "pocket money" in interface P9. When the first user desires to transfer a corresponding share of funds into the pocket money sub-account, the first user can input the transfer amount into the first terminal by triggering the image area corresponding to the word "transfer in" in interface P11, and the first terminal can send a management request containing the first configuration information to the server under the trigger of the first user. When the first user desires to transfer a corresponding share of funds out of the pocket money sub-account, the first user can input the transfer amount into the first terminal by triggering the image area corresponding to the word "transfer out" in interface P11, and the first terminal can send a management request containing the first configuration information to the server under the trigger of the first user. When the first user desires to change the daily consumption limit, the daily consumption frequency, or the consumption scenario of the pocket money sub-account, the first user can input the desired daily consumption limit, the desired daily consumption frequency, and the indication information of whether to start or stop a certain consumption scenario into the first terminal by triggering the image area corresponding to the word "consumption limit" in interface P11, and the first terminal can send a management request containing the first configuration information to the server under the trigger of the first user. When the first user desires to allow the second user to have the right to transfer funds from the pocket money sub-account to the balance sub-account, the first user can input one or more of the indication information of whether to allow the second user to have the transfer right, the transfer frequency, and the transfer limit into the first terminal by triggering the image area corresponding to the word "transfer out management" in interface P11, and the first terminal can send a management request containing the first configuration information to the server under the trigger of the first user.

[0070] The foregoing exemplary describes the process that the first user triggers the first terminal to send a corresponding management request to the server based on the interaction interface P11 displayed by the first terminal corresponding to the pocket money sub-account. However, it should be understood that the first user can also interact with the first terminal through the interface P11 in other forms of information to prompt the first terminal to interact with the server to complete the transaction that the first user expects to complete. For example, the first user can trigger the image area corresponding to the "collection" word in the interface P11, so that the first terminal displays the collection code corresponding to the pocket money sub-account, so that other users can scan the collection code to realize the transfer of the corresponding share of funds to the pocket money sub-account; for another example, the first user can trigger the image area corresponding to the "automatic transfer" word in the interface P11 to set the transfer amount and transfer time interval of the automatic transfer of funds from the first account to the pocket money, so that the server can automatically transfer the corresponding share of funds from the first account to the pocket money sub-account according to the user's set transfer amount and transfer time interval. In addition, the consumption bill of the pocket money sub-account can also be displayed in the interface P11.

[0071] Similarly, when the first user expects to change the state of the various services provided by the server for the second account, for example, expects to bind or unbind a predetermined type of terminal such as a children's watch to the first sub-account under the second account or expects to start or close the target service such as face payment provided by the server for the first sub-account, the image area corresponding to the "children's watch" or "face payment" word in the interface P9 can be triggered to trigger the first terminal to send a corresponding information change request to the server.

[0072] Finally, in step S415, the server updates the account information of the first sub-account according to the first account relationship and the management request.

[0073] According to the foregoing example, according to the first configuration information included in the management request, the operation required to be performed in the process of updating the account information of the first sub-account may, for example, include one or more of the following operations: transfer-in or transfer-out operation on the first sub-account, set the consumption scenario of the first sub-account, set the consumption limit of the first sub-account, set the permission of the first sub-account to transfer-out to the second sub-account of the second account, set the permission of the first sub-account to transfer-out to other first sub-accounts included in the second account, start or close the target service provided by the server for the first sub-account, and bind or unbind the first sub-account to the terminal belonging to the predetermined type, and the like.

[0074] The foregoing exemplary describes the process of the first user managing the pocket sub-account under the second account, and it can be understood that the first user can also complete the management of other sub-accounts such as the investment sub-account under the second account through a similar process. For example, the first user can trigger the image area corresponding to the "investment" word in the interface P9 to set the account information of the investment sub-account, such as setting whether the second user is allowed to view the balance and income of the investment sub-account, setting whether the second user has the right to transfer funds from the investment sub-account to a specific sub-account such as the balance sub-account, and the like.

[0075] The first user can also complete other transactions through the foregoing first interaction interface. For example, the first user can also trigger the image area corresponding to the "manage" word in the interface P9 of the foregoing example to make the first terminal display other interaction interfaces such as the interface P10, which can include the basic account information of the second user such as the user name, the ID number, the mobile phone number, and the platform account (i.e., the second account). The first user can trigger the first terminal to interact with the server through the interface P10 to complete the update of the basic account information.

[0076] In a possible implementation, the first terminal can also obtain the third configuration information of the second account provided by the first user to the first terminal according to the third interaction interface corresponding to the second account; and correspondingly, the first terminal can generate a relationship management request of the second account according to the third configuration information, and send the relationship management request of the second account to the server; and then, the server records or deletes the second account relationship between the third account and the second account according to the relationship management request, wherein the second account relationship is used to indicate that the third account has the management right of the first sub-account.

[0077] When the relationship management request is used to request to record or delete the second account relationship between the third account and the second account, the server can send prompt information to the third terminal corresponding to the third account according to the management request, so that the third terminal returns corresponding response information to the server according to the prompt information; if the response information indicates that the third user holding the third account allows to record / delete the second account relationship, the server can delete / record the second account relationship, otherwise the second account relationship will not be deleted.

[0078] When the first account is the first platform account to establish an account relationship with the second account, and the management request is used to request the server to delete the second account relationship, the server can also directly delete the second account relationship without the permission of the third user corresponding to the third account. For example, the interface P10 can display a management member list corresponding to the second account, and the management member list includes the user names of the users corresponding to the accounts that have established an account relationship with the second account. The first user, i.e., “Shi XA”, is the first platform account to establish an account relationship with the second account, and the third user, i.e., “A XB”, establishes a second account relationship with the second account at the invitation of “Shi XA”. Therefore, the first user “Shi XA” can trigger the image area corresponding to the user name “A XB” in the management member in the interface P10, so that the first terminal sends a relationship management request to the server to request to delete the second account relationship, and the server can directly delete the second account relationship.

[0079] Similarly, the first user can trigger the first terminal to send a relationship release request to the server through the interface 10, for example, trigger the trigger area corresponding to the “Close the intimate number of Shi XX” in the interface 10, so that the first terminal sends a relationship release request to the server, and the server can delete the first account relationship between the first account and the second account recorded in the server, so that the first account loses the management permission of the first sub-account. It should be noted that when there is no other account in the server that has established an account relationship with the second account, the server can automatically or at the request of the second user, delete part of the sub-accounts under the second account. For example, when the young child grows up or enters the university stage, the parents may have no restrictions on the use of the second account by the child, at which time the parents can actively release all the account relationships established with the second account, the server can transfer all the funds under the pocket money sub-account and the financial sub-account to the balance account, and delete the pocket money sub-account and the financial sub-account.

[0080] In some embodiments, the second user can use the first sub-account, e.g., the pocket money sub-account, for daily expenses through the second terminal corresponding to the second account or through a predetermined type of terminal, e.g., a child watch, bound to the first sub-account. In this case, the server can receive a payment request corresponding to the first sub-account from the second terminal, the child watch, or a merchant, and the server can process the payment request according to the account of the first sub-account. For example, based on the conditions of the consumption frequency, consumption scenario, and consumption amount set for the account of the first sub-account, it is determined whether the payment request needs to be normally processed. For example, when the current consumption frequency of the first sub-account has reached the daily consumption frequency set for the first sub-account, the server can refuse to normally process the payment request, so that no funds are transferred from the first sub-account to other accounts according to the payment request.

[0081] Correspondingly, the server can also generate a payment record corresponding to the first sub-account according to the processing result of the payment request corresponding to the first sub-account, and send the payment record to the first terminal corresponding to the first account, so that the first terminal can learn the actual use of the first sub-account by the second user in time.

[0082] In some embodiments, similar to the implementation process of the foregoing steps S401 and S403, the second user can trigger the second terminal on demand to send a query request for target information to the server, where the target information belongs to the account information of the first sub-account; and the server can send the target information to the second terminal according to the query request. For example, please continue to refer to FIG. 5, the second user can trigger the image area corresponding to the "bill" in the interface P6, so that the second terminal sends a corresponding query request to the server, and the server can return the consumption bill of the pocket money sub-account to the second terminal according to the query request.

[0083] Based on the same concept as the method shown in the foregoing FIG. 4, another account management method in a payment platform is also provided.

[0084] FIG. 7 is a flowchart of another account management method in a payment platform provided in the embodiments of the present specification. Each step in the method can be independently implemented by the server, the first terminal corresponding to the first account, or the second terminal corresponding to the second account, or cooperatively implemented by the server and the first terminal, or cooperatively implemented by the server and the second terminal. Among them, the same as the method shown in the foregoing FIG. 4, the server of the payment platform registers the first account of the first user and the second account of the second user, the first account includes a first sub-account, and the server records a first account relationship between the first account and the second account, the first account relationship is used to indicate that the first account has a management right to the first sub-account; the second account can also include a second sub-account as a default balance account, and the first account does not have a management right to the second sub-account.

[0085] Referring to FIG. 7, the method can include, but is not limited to, some or all of the following steps 701-707.

[0086] Step S701, creating a first account relationship through a second interaction interface corresponding to the first account.

[0087] The process of creating a first account relationship through a second interaction interface can be referred to the detailed description in the foregoing related content corresponding to FIG. 1 and FIG. 2, which will not be described here again.

[0088] Step S703, obtaining first configuration information of the first sub-account through a first interaction interface corresponding to the first account, where the first interaction interface is used to display and configure at least part of the account information of the first sub-account.

[0089] The at least part of the account information of the first sub-account includes at least one of the following: a balance of the first sub-account, a service permission corresponding to the first sub-account, and usage restriction information of the first sub-account. The implementation of step S703 can refer to the related content in the foregoing steps S411 and S413, for example, refer to the description in the related content corresponding to FIG. 6, and details are not described herein again.

[0090] In step S705, display information in the first interaction interface is updated according to the first configuration information.

[0091] In step S707, a fourth interaction interface corresponding to the second account is updated according to the first configuration information, and the fourth interaction interface is used to display at least part of the account information of the first sub-account.

[0092] For example, after the server completes the update of the account information of the first sub-account according to the management request containing the first configuration information, the first interaction interface and the fourth interaction interface are updated according to the updated account information of the first sub-account. The fourth interaction interface can include at least one of the following controls corresponding to the first sub-account: a receiving control, a paying control, a control for requesting to change the service permission, a control for requesting to change the usage restriction information, a control for transferring out the balance, and a control for inviting others to transfer in. Each control described herein corresponds to each image area that allows the second user to trigger to implement a related transaction in the exemplary description of FIG. 5.

[0093] In addition, similar to the method shown in FIG. 4, the third configuration information of the second account can also be obtained through the third interaction interface corresponding to the first account, the second account relationship between the third account and the second account is recorded or deleted according to the third configuration information, and the second account relationship is used to indicate that the third account has the management permission of the first sub-account.

[0094] In summary, the technical solutions provided in the embodiments of the present specification can meet the all-round perception and management of the parents on the accounts, funds and services of children / old people, help the vulnerable groups to reduce the use threshold and risk of the payment platform, and protect the convenience and security of their use. Compared with the related art: the relationship between the first account and the second account is upgraded from a simple fund relationship to an account relationship, and the management range of the first account on the second account can be expanded to multiple aspects such as sub-accounts, funds and services; between the first account and the second account, the consumption mode is upgraded from a fund deduction relationship to a fund recharge mode, the fund given by the parent to the child or the adult child to the old person is deterministic, and the fund received by the child / old person is also deterministic, and the parent / adult child has management ability and consumption perception on the sub-account; when and how much the child / old person uses each time can be autonomously decided by the child / old person, and the child / old person can also choose not to use, and the fund under the sub-account can be accumulated all the time; in addition to the fund for daily consumption, the parent can also support the child to perform financial management on demand and enjoy the increment brought by the fund under the financial sub-account; and, the affection card requires the child / old person to have a mobile phone, but in the present solution, the old person / child can not be required to have a mobile phone, and the child / old person can use the sub-account such as the first sub-account for daily consumption through a predetermined type of terminal such as a smart watch, a reading pen learning machine and the like bound with the first sub-account.

[0095] Based on the same concept as the foregoing method embodiments, the present specification also provides a service end 800 of a payment platform. Referring to FIG. 8, the service end 800 registers a first account of a first user and a second account of a second user, the first account includes a first sub-account, the service end records a first account relationship between the first account and the second account, the first account relationship is used to indicate that the first account has a management right on the first sub-account, and the payment platform includes: a communication processing unit 801 configured to receive a management request initiated on the first sub-account from a first terminal corresponding to the first account; a transaction processing unit 803 configured to update account information of the first sub-account according to the first account relationship and the management request.

[0096] Based on the same idea as the foregoing method embodiments, the present specification embodiments also provide a terminal 900. Referring to FIG. 9, a server of a payment platform involved by the terminal 900 registers a first account of a first user and a second account of a second user, the first account includes a first sub-account, the server records a first account relationship between the first account and the second account, the first account relationship is used to indicate that the first account has a management right to the first sub-account, the terminal corresponds to the first account, and the terminal includes: an information obtaining unit 901 configured to obtain first configuration information of the first sub-account according to a first interaction interface corresponding to the first sub-account; a request generating unit 903 configured to generate a management request for the first sub-account according to the first configuration information; and a communication processing unit 905 configured to send the management request to the server.

[0097] Based on the same idea as the foregoing method embodiments, the present specification embodiments also provide a terminal 1000. Referring to FIG. 10, a server of a payment platform involved by the terminal 1000 registers a first account of a first user and a second account of a second user, the first account includes a first sub-account, the server records a first account relationship between the first account and the second account, the first account relationship is used to indicate that the first account has a management right to the first sub-account, the terminal corresponds to the second account, and the terminal includes: a communication processing unit 1001 configured to receive at least part of account information of the second account from the server, at least part of the account information of the second account including at least part of account information of the first sub-account; and a display processing unit 1003 configured to display a fourth interaction interface corresponding to the second account, which includes at least part of the account information of the second account.

[0098] The present specification embodiments also provide a computer readable storage medium having computer programs / instructions stored thereon, when the computer programs / instructions are executed in a computer, the computer executes the method steps performed by the server, the first computing device or the second computing device in the foregoing various embodiments.

[0099] The present specification embodiments also provide a computing device including a memory and a processor, the memory has computer programs / instructions stored therein, and the processor, when executing the computer programs / instructions, implements the method steps performed by the server, the first computing device or the second computing device in the foregoing various embodiments. In other words, the computing device can be implemented as the server, the first terminal or the second terminal in the foregoing various embodiments.

[0100] In the 1990s, it was quite obvious to distinguish whether an improvement in a technology was in hardware (e.g., improvement in circuit structures of diodes, transistors, switches, etc.) or in software (improvement in method flow). However, as technology has evolved, many improvements in method flow today can be considered as direct improvements in hardware circuit structures. Designers almost always obtain the corresponding hardware circuit structures by programming the improved method flow into hardware circuits. Therefore, it cannot be said that an improvement in a method flow cannot be implemented by hardware entity modules. For example, a programmable logic device (PLD) (e.g., a field programmable gate array (FPGA)) is an integrated circuit whose logic function is determined by user programming of the device. A digital system is "integrated" on a PLD by the designer programming it, rather than by asking a chip manufacturer to design and fabricate a custom integrated circuit chip. Moreover, instead of manually fabricating integrated circuit chips, this programming is now mostly implemented by "logic compiler" software, which is similar to software compilers used in program development, and the original code to be compiled is written in a specific programming language, which is called a hardware description language (HDL), and there are many such languages, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description Language), etc., and the most commonly used are VHDL (Very-High-Speed Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should be aware that, as long as the method flow is logically programmed in the above-mentioned hardware description languages and programmed into an integrated circuit, a hardware circuit implementing the logical method flow can be easily obtained.

[0101] The controller can be implemented in any suitable way, for example, the controller can take the form of, for example, a microprocessor or processor and a computer readable medium storing computer readable program code, such as software or firmware, executable by the (micro)processor, logic gates, switches, an application specific integrated circuit (ASIC), a programmable logic controller and an embedded microcontroller, examples of which include but are not limited to the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20 and Silicone Labs C8051F320, the memory controller can also be implemented as part of the control logic of the memory. The skilled person will also appreciate that, in addition to implementing the controller in pure computer readable program code, it is possible to implement the controller in the form of logic gates, switches, an application specific integrated circuit, a programmable logic controller and an embedded microcontroller, etc. to perform the same functions by logically programming the method steps. Such a controller can therefore be considered to be a hardware component, and the means included therein to perform the various functions can also be considered to be structures within the hardware component. Alternatively, or even additionally, the means to perform the various functions can be considered to be both a software module implementing the method and a structure within a hardware component.

[0102] The systems, apparatuses, modules or units illustrated by the above embodiments can be specifically implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a server system. Of course, the present application does not rule out that with the development of future computer technologies, computers implementing the functions of the above embodiments can be personal computers, laptop computers, vehicle human-computer interaction devices, cellular phones, camera phones, smart phones, personal digital assistants, media players, navigation devices, email devices, game consoles, tablet computers, wearable devices, or combinations of any of these devices.

[0103] Although the method operational steps are provided in one or more embodiments herein in the order listed, other embodiments could include fewer or more steps and / or different ordering of the steps, based on the common or inventive concepts. The order in which steps are listed is merely one example of the ordering of the steps. The steps listed in the embodiments can be performed in serial, parallel, or in any order, as long as the end result is that the steps are performed. The term "comprising" or "including" or any other variant is intended to cover both the case where one or more steps are included in the process, method, article, or apparatus, and the case where one or more steps are not included in the process, method, article, or apparatus. The terms "comprising", "including", or any other variant thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises or includes one or more steps does not include only those one or more steps, but can include other steps not expressly listed or inherent to such process, method, article, or apparatus. The use of the terms "first", "second", or any other ordinal term is not meant to indicate any particular order, but is meant to indicate a different class of elements. For example, the use of the term "first" to describe one element does not mean that the element is the first element to be performed, but rather that the element is the first of a different class of elements.

[0104] For the sake of description, the above apparatuses are described in functional modules for convenience. Certainly, when implementing one or more embodiments of the present specification, the functions of the modules can be implemented in one or more software and / or hardware, or the modules implementing the same function can be combined into a combination of sub-modules or sub-units. The above-described apparatus embodiment is only schematic, for example, the division of the units is only a logical function division, and actual implementation can have another division manner, for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the displayed or discussed elements can be indirect coupling or communication connection through some interface, apparatus or unit, and can be electrical, mechanical or other forms.

[0105] The present application is described with reference to flowcharts and / or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It should be understood that each flow and / or block in the flowcharts and / or block diagrams, as well as combinations of flows and / or blocks in the flowcharts and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing apparatus to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing apparatus generate the apparatus for implementing the functions specified in one or more flows or blocks of the flowcharts and / or block diagrams.

[0106] These computer program instructions can also be stored in a computer- readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instructions which implement the function specified in the flowchart or flowsheets and / or block or blocks of the block diagrams.

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

[0108] In one typical configuration, the computing device includes one or more processors (CPUs), input / output interfaces, network interfaces, and memory.

[0109] The memory can include non-persistent memory and / or volatile memory, such as random access memory (RAM) about which the computer stores information about an operating system or application programs, e.g., DRAM, SRAM, etc. The memory is an example of computer readable media.

[0110] Computer readable media includes permanent and non-permanent, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read only memory (ROM), electrically erasable programmable read only memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital versatile disc (DVD), or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage, graphene storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information accessible to computing devices. According to the definition herein, computer readable media does not include transitory media, such as modulated data signals and carrier waves.

[0111] Those skilled in the art will appreciate that the one or more embodiments described herein can be provided as a method, a system or a computer program product. Accordingly, the one or more embodiments described herein can take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the one or more embodiments described herein can take the form of a computer program product on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROMs, optical storage devices, etc.) embodying computer readable code.

[0112] The one or more embodiments described herein can be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform particular tasks or implement particular abstract data types. The one or more embodiments described herein can also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules can be located in both local and remote computer storage media including memory storage devices.

[0113] The various embodiments described in this specification are described in the context of progressive embodiments, with each embodiment building on the previous one. The same or similar parts between embodiments are cross-referenced as appropriate. Each embodiment focuses on the differences between that embodiment and the previous one. In particular, the system embodiments are described relatively simply, as they are substantially similar to the method embodiments. In the description of the specification, the use of the terms "one embodiment", "some embodiments", "example", "specific example" or "some examples" means that the particular feature, structure, material or characteristic being described is included in at least one embodiment or example of the specification. Illustrative descriptions of the above terms do not necessarily refer to the same embodiment or example in this specification. Moreover, the particular features, structures, materials, or characteristics can be combined in any suitable manner in one or more embodiments or examples. Furthermore, the skilled person can combine and combine the features of different embodiments or examples and characteristics of different embodiments or examples, without contradiction.

[0114] The above description merely provides examples of the one or more embodiments described in this specification and does not limit the one or more embodiments described in this specification. The one or more embodiments described in this specification can have various modifications and changes. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the one or more embodiments described in this specification shall be included in the scope of the claims.

Claims

1. A method for account management in a payment platform, a server of the payment platform registering a first account of a first user and a second account of a second user, the second account including a first sub-account, the server recording a first account relationship between the first account and the second account, the first account relationship indicating that the first account has a management right on the first sub-account, the method comprising: receiving, from a first terminal corresponding to the first account, a management request initiated on the first sub-account; and updating account information of the first sub-account according to the first account relationship and the management request. 2.The method of claim 1, wherein the second account further includes a second sub-account, and the second sub-account is a default balance account of the second account. 3.The method of claim 1, further comprising: receiving, from the first terminal, a first relationship creation request, the first relationship creation request indicating to establish the first account relationship; and recording the first account relationship according to the first relationship creation request. 4.The method of claim 3, wherein the first relationship creation request further indicates to create the second account; and the recording the first account relationship according to the first relationship creation request comprises creating the second account according to the first relationship creation request and recording the first account relationship. 5.The method of claim 3, further comprising: providing, to a second terminal corresponding to the second account, first prompt information according to the first relationship creation request; receiving, from the second terminal corresponding to the second account, first response information corresponding to the first prompt information; and recording the first account relationship when the first response information indicates that the second user allows to record the first account relationship. 6.The method of claim 3, further comprising: receiving, from a second terminal corresponding to the second account, a second relationship creation request, the second relationship creation request indicating to establish the first account relationship; providing, to the first terminal, second prompt information according to the second relationship creation request; and wherein the first relationship request includes second response information corresponding to the second prompt information, the second response information indicating that the first user allows to record the first account relationship. 7.The method of claim 1, wherein the management request indicates to perform at least one of the following operations: performing a transfer-in or transfer-out operation on the first sub-account; setting a consumption scenario of the first sub-account; setting a consumption limit of the first sub-account; setting a consumption frequency of the first sub-account; setting a right of the first sub-account to transfer funds to the second sub-account; setting a right of the first sub-account to transfer funds to other first sub-accounts of the second account; starting or stopping a target service provided by the server to the first sub-account; and binding or unbinding a terminal of a predetermined type to the first sub-account. 8.The method of claim 1, further comprising: wherein ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ receiving a payment request corresponding to the first sub-account; processing the payment request according to account information of the first sub-account; generating a payment record corresponding to the first sub-account according to a processing result of the payment request; and sending the payment record to the first terminal.

9. The method of claim 1, further comprising: receiving, from a second terminal corresponding to the second account, an information change request corresponding to the first sub-account; and providing, to the first terminal, third prompt information according to the information change request.

10. The method of any one of claims 1-9, further comprising: receiving, from the first terminal, a relationship management request for the second account; and recording or deleting a second account relationship between a third account and the second account according to the relationship management request, the second account relationship being used to indicate that the third account has a management right for the first sub-account.

11. An account management method in a payment platform, a server of the payment platform registering a first account of a first user and a second account of a second user, the second account including a first sub-account, the server recording a first account relationship between the first account and the second account, the first account relationship being used to indicate that the first account has a management right for the first sub-account, the method being performed by a first terminal corresponding to the first account, and the method comprising: obtaining first configuration information for the first sub-account according to a first interaction interface; generating a management request for the first sub-account according to the first configuration information; and sending the management request to the server.

12. The method of claim 11, further comprising: obtaining relationship creation information for the first account relationship according to a second interaction interface corresponding to the first account; generating a first relationship creation request according to the relationship creation information, the first relationship creation request being used to indicate establishment of the first account relationship; and sending the relationship creation request to the server.

13. The method of claim 12, wherein the relationship creation information includes identity information of the second user, and the first relationship creation request is further used to indicate creation of the second account.

14. The method of claim 12, further comprising: receiving second prompt information from the server, wherein the second prompt information is sent by the server after the server receives a second relationship creation request from a second terminal corresponding to the second account, the second relationship creation request being used to indicate establishment of the first account relationship; and wherein the relationship creation information includes second response information corresponding to the second prompt information, the second response information being used to indicate that the first user allows recording of the first account relationship.

15. The method of claim 11, further comprising: receiving, from the server, a payment record corresponding to the first sub-account, wherein the payment record is sent by the server after the server processes a payment request corresponding to the first sub-account according to account information of the first sub-account. ​ ​ ​ ​ 16. The method of any one of claims 11-15, further comprising: obtaining, according to a third interaction interface corresponding to the first account, third configuration information of the second account; generating, according to the third configuration information, a relationship management request of the second account, for requesting the server to record or delete a second account relationship between a third account and the second account; sending the relationship management request to the server.

17. An account management method in a payment platform, a server of the payment platform registering a first account of a first user and a second account of a second user, the second account including a first sub-account, the server recording a first account relationship between the first account and the second account, the first account relationship indicating that the first account has a management privilege on the first sub-account, the method being performed by a second terminal corresponding to the second account, and the method comprising: receiving, from the server, at least part of account information of the second account, the at least part of account information of the second account including at least part of account information of the first sub-account, the at least part of account information of the first sub-account being configured by the first account; displaying a fourth interaction interface corresponding to the second account, the fourth interaction interface including the at least part of account information of the second account.

18. The method of claim 17, further comprising: obtaining, according to the fourth interaction interface, second configuration information of the first sub-account; sending, to the server, an information change request corresponding to the first sub-account according to the second configuration information.

19. An account management method in a payment platform, a server of the payment platform registering a first account of a first user and a second account of a second user, the second account including a first sub-account, the server recording a first account relationship between the first account and the second account, the first account relationship indicating that the first account has a management privilege on the first sub-account, the method comprising: obtaining, through a first interaction interface corresponding to the first account, first configuration information of the first sub-account, the first interaction interface being used to display and configure at least part of account information of the first sub-account; updating display information in the first interaction interface according to the first configuration information.

20. The method of claim 19, the second account further including a second sub-account, the second sub-account being a default balance account of the second account.

21. The method of claim 19, further comprising: creating the first account relationship through a second interaction interface corresponding to the first account.

22. The method of claim 19, further comprising: obtaining, through a third interaction interface corresponding to the first account, third configuration information of the second account; recording or deleting a second account relationship between a third account and the second account according to the third configuration information, the second account relationship indicating that the third account has a management privilege on the first sub-account.

23. The method of claim 19, wherein the at least part of the account information comprises at least one of: a balance of the first sub-account, a service permission corresponding to the first sub-account, and usage limit information of the first sub-account.

24. The method of claim 19, further comprising: According to the first configuration information, a fourth interaction interface corresponding to the second account is updated, and the fourth interaction interface is used to display at least part of the account information of the first sub-account.

25. The method of claim 24, wherein the fourth interaction interface comprises at least one of the following controls corresponding to the first sub-account: a receiving control, a paying control, a control for requesting to change the service permission, a control for requesting to change the usage limit information, a control for transferring out a balance, and a control for inviting others to transfer in.

26. A computing device comprising a memory and a processor, wherein the memory stores executable code, and the processor executes the executable code to implement the method of any one of claims 1-25.

Images