Information interaction method and device, electronic equipment, storage medium and program product

Abstract

An information interaction method, apparatus, device, medium, and program product are disclosed. The method includes: receiving a first trigger from a first user on a first account, wherein the first account belongs to the first user and is associated with a second user, the first user has first permissions on the first account, and the second user has second permissions on the first account; displaying a first interface of the first account, wherein the first interface is used by the first user to configure at least some of the permissions of the second permissions. This addresses the payment security and payment configuration flexibility issues of payment accounts in certain scenarios in related technologies, enabling flexible configuration of the first account.

Description

Technical Field

[0001] This invention relates to the field of computer processing technology, and in particular to an information interaction method, device, electronic device, storage medium, and program product. Background Technology

[0002] With the rapid development of mobile payment technology, various online and offline payment scenarios are constantly increasing, and users' demands for payment security and convenience are becoming increasingly prominent. Currently, in the payment field, the security or flexibility of payments in certain scenarios still needs improvement. Summary of the Invention

[0003] This invention provides an information interaction method, device, electronic device, storage medium, and program product that solves the payment security or flexibility problems of payment accounts in certain scenarios in related technologies.

[0004] In one scenario, this paper provides an information exchange method, which includes: Receive a first trigger from a first user for a first account, the first account belongs to the first user and is associated with a second user, the first user has first permissions for the first account, and the second user has second permissions for the first account; The first interface of the first account is displayed, and the first interface is used by the first user to configure at least part of the permission content of the second permission.

[0005] In one scenario, this paper provides an information exchange method, which includes: A third interface is displayed, which is associated with the second user; The information of the first account is displayed through the third interface, and the first account belongs to the first user. The information displayed for the first account includes at least one of the following: In response to at least a first condition being met, resource transfer information of the first user through the first account is displayed, wherein the first condition includes first configuration information indicating that the second user is allowed to view the resource transfer information of the first account, the first configuration information being configured by the first user; or... Upon receiving a first notification message, the first notification message indicates that the first user's resource transfer through the first account satisfies the second condition or that a risk exists; or, Display a first control, which is used to process resource transfers made by the first user through the first account; or... The first processing prompt is displayed to prompt the second user whether to enter a processing command or confirm the processing command. The processing command is used to process the resource transfer performed by the first user through the first account.

[0006] In one scenario, this paper provides an information exchange method, which includes: Displaying a second interface, the second interface being used by the first user to open a first account; wherein, it further includes at least one of the following: the second interface is displayed via a seventh trigger, the seventh trigger being used by the second user to invite the first user to open the first account; or, the second interface includes a first area, the first area displaying the information of the second user; In response to the authentication of the first user, the activation status of the first account is displayed; This also includes at least one of the following: The first user has first permissions on the first account, and the second user has second permissions on the first account, wherein the first permissions include configuring at least a portion of the permissions specified in the second permissions; or... The second permission includes at least one of the following: viewing the resource transfer information of the first user through the first account; receiving a first notification message, the first notification message indicating that the resource transfer of the first user through the first account meets a second condition or there is a risk; and a second processing permission, the second processing permission being used to process the resource transfer of the first user through the first account.

[0007] In one scenario, this paper provides an information exchange method, which includes: In response to the ninth trigger of the second user, third information is displayed. The ninth trigger is used for the second user to confirm the invitation to the first user to open the first account. The third information includes the invitation method that the second user can use when sending the invitation to the first user. In response to the tenth trigger by the second user, fourth information corresponding to the selected channel identifier is displayed, wherein the fourth information includes at least one of the following: invitation information for the second user to invite the first user to open the first account; status notification information obtained by the second user after sending the invitation information to the first user; This also includes at least one of the following: The first user has first permissions on the first account, and the second user has second permissions on the first account, wherein the first permissions include configuring at least a portion of the permissions specified in the second permissions; or... The second permission includes at least one of the following: viewing the first resource transfer information of the first user through the first account, wherein the first resource transfer information satisfies a first condition; receiving a first notification message, wherein the first notification message indicates that the resource transfer of the first user through the first account satisfies a pre-first condition or that there is a risk; and a second processing permission, wherein the second processing permission is used to process the resource transfer of the first user through the first account.

[0008] In one instance, this document also provides an information interaction device, which includes: The first module is used to receive a first trigger from a first user for a first account, wherein the first account belongs to the first user and is associated with a second user, the first user has first permissions for the first account, and the second user has second permissions for the first account. The second module is used to display the first interface of the first account, wherein the first interface is used by the first user to configure at least part of the permission content of the second permission.

[0009] In one instance, this document also provides an information interaction device, which includes: The third module is used to display a third interface, which is associated with the second user. The fourth module is used to display information about the first account through the third interface, wherein the first account belongs to the first user; The display of information about the first account includes: displaying second information about the first account, the second information being associated with resource transfers made by the first user through the first account, the second user having second permissions to the first account, and the second information being associated with the second permissions.

[0010] In one instance, this document also provides an information interaction device, which includes: The fifth module is used to display a second interface for a first user to open a first account; wherein, it further includes at least one of the following: the second interface is displayed via a fourth trigger, the fourth trigger being used by a second user to invite the first user to open the first account; or, the second interface includes a first area, the first area displaying the information of the second user; The sixth module is used to display the activation status of the first account in response to authentication of the first user; wherein, it further includes at least one of the following: the first user has a first permission to the first account, the second user has a second permission to the first account, the first permission includes configuring at least a portion of the permission content in the second permission; or, the second user has a second permission to the first account, second information of the first account is associated with the second permission, and the second information is associated with resource transfers performed by the first user through the first account.

[0011] In one instance, this document also provides an information interaction device, which includes: The seventh module is used to respond to the ninth trigger of the second user and display the third information. The ninth trigger is used for the second user to confirm the invitation to the first user to open the first account. The third information includes the invitation method that the second user can use when sending the invitation to the first user. The eighth module is configured to respond to the tenth trigger of the second user by displaying fourth information corresponding to the selected invitation method. The fourth information includes at least one of the following: invitation information for the second user to invite the first user to activate the first account; status notification information obtained by the second user after sending the invitation information to the first user; and further includes at least one of the following: the first user has a first permission to the first account, and the second user has a second permission to the first account, the first permission including configuring at least a portion of the permission content in the second permission; or, the second permission includes at least one of the following: viewing first resource transfer information of the first user through the first account, the first resource transfer information satisfying a first condition; receiving a first notification message indicating that the resource transfer of the first user through the first account satisfies the first condition or poses a risk; and a second processing permission for processing the resource transfer of the first user through the first account.

[0012] In one instance, this document also provides an electronic device comprising: One or more processors; Storage device for storing one or more programs. When the one or more programs are executed by the one or more processors, the one or more processors implement the information interaction method as described herein.

[0013] In one instance, this document also provides a storage medium containing computer-executable instructions that, when executed by a computer processor, are used to perform the information interaction methods as described herein.

[0014] In another scenario, this document also provides a computer program product, including a computer program that, when executed by a processor, implements the information interaction method as described herein.

[0015] In some scenarios, because the first account is associated with both a first user and a second user, and the first user has first-level permissions while the second user has second-level permissions, this multi-user permission structure allows the same payment account to serve the operational needs of different roles. In other scenarios, configuring at least some of the second user's permissions through the first interface allows the first user to flexibly set the permissions available or restricted for the second user based on actual payment scenarios or management needs. This simplifies the second user's operational path while ensuring account security, reduces payment interruptions or additional authorization steps caused by unclear permissions, and supports visual display of permission configuration, improving the flexibility and convenience of permission configuration. In still other scenarios, based on the first user's first permissions to the first account, pre-defining and dynamically adjusting the second user's permissions helps unify account management rules, reduces abnormal handling processes caused by insufficient or unauthorized operations during payment, and thus improves the overall operational efficiency and security of the payment system. Attached Figure Description

[0016] The above and other features, advantages, and aspects of the embodiments described herein will become more apparent when taken in conjunction with the accompanying drawings and the following detailed description. Throughout the drawings, the same or similar reference numerals denote the same or similar elements. It should be understood that the drawings are schematic, and the originals and elements are not necessarily drawn to scale.

[0017] Figure 1 This is a schematic diagram of the structure of an information interaction system under one scenario. Figure 2 This is a flowchart illustrating an information interaction method in one scenario. Figure 3 This is a schematic diagram of the first interface in one scenario. Figure 4 This is a schematic diagram illustrating the interface for displaying a second user in one scenario. Figure 5 This is a flowchart illustrating another method of information interaction. Figure 6 This is a flowchart illustrating an information interaction method in one scenario. Figure 7 This is a flowchart illustrating another method of information interaction. Figure 8 This is a flowchart illustrating another method of information exchange. Figure 9This is a flowchart illustrating another method of information exchange. Figure 10 This is a flowchart illustrating another method of information exchange. Figure 11 This is a flowchart illustrating an information interaction method in one scenario. Figure 12 This is a schematic diagram of the interface for authenticating the first user in one scenario. Figure 13 This is a schematic diagram of an interface displaying information for the first account in one scenario. Figure 14 This is a flowchart illustrating an information interaction method in one scenario. Figure 15 This is a schematic diagram of an interface for displaying third information in one scenario. Figure 16 This is a schematic diagram of the interface for a fourth information display method under one scenario; Figure 17 This is a flowchart illustrating another method of information exchange. Figure 18 This is a schematic diagram of the structure of an information interaction device in one scenario. Figure 19 This is a schematic diagram of the structure of an information interaction device in one scenario. Figure 20 This is a schematic diagram of the structure of an information interaction device in one scenario. Figure 21 This is a schematic diagram of the structure of an information interaction device in one scenario. Figure 22 This is a schematic diagram of the structure of an electronic device used to implement an information interaction method in one scenario. Detailed Implementation

[0018] The embodiments will now be described in more detail with reference to the accompanying drawings. While some embodiments are shown in the drawings, it should be understood that the provided solutions can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of the provided solutions. It should be understood that the illustrated drawings and embodiments are for illustrative purposes only and are not intended to limit the scope of protection of the provided solutions.

[0019] It should be understood that the steps described in the method implementation may be performed in different orders and / or in parallel. Furthermore, the method implementation may include additional steps and / or omit the steps shown. The scope of this document is not limited in this respect.

[0020] The term "comprising" and its variations as used herein are open-ended inclusions, meaning "including but not limited to". The term "based on" means "at least partially based on". The term "one situation" means "at least one situation"; the term "another situation" means "at least one additional situation"; the term "some situations" means "at least some situations". Definitions of other terms will be given in the following description.

[0021] It should be noted that the concepts of "first" and "second" mentioned are only used to distinguish different devices, modules or units, and are not used to limit the order of the functions performed by these devices, modules or units or their interdependencies.

[0022] It should be noted that the terms "one" and "more" used in this document are illustrative rather than restrictive, and those skilled in the art should understand that, unless otherwise expressly indicated in the context, they should be understood as "one or more".

[0023] The names of messages or information exchanged between multiple devices in this document are for illustrative purposes only and are not intended to limit the scope of these messages or information.

[0024] It is understood that before using the solutions provided in the various implementation methods described herein, users should be informed of the types, scope of use, and usage scenarios of the personal information involved in this document in an appropriate manner in accordance with relevant laws and regulations, and user authorization should be obtained.

[0025] For example, upon receiving a user's proactive request, a prompt message can be sent to the user to explicitly inform them that the requested operation will require the acquisition and use of the user's personal information. This allows the user to independently choose, based on the prompt message, whether to provide personal information to the software or hardware such as electronic devices, applications, servers, or storage media performing the operations described herein.

[0026] As an optional but non-limiting implementation, in response to a user's active request, sending a prompt message to the user can be done via a pop-up window, where the prompt message can be presented in text format. Furthermore, the pop-up window can also include a selection control allowing the user to choose "agree" or "disagree" to provide personal information to the electronic device.

[0027] It is understood that the above notification and user authorization process is merely illustrative and does not limit the implementation method described in this article. Other methods that comply with relevant laws and regulations may also be applied to the implementation method described in this article.

[0028] It is understood that the data involved in this article (including but not limited to the data itself, the acquisition or use of the data) shall comply with the requirements of relevant laws, regulations and related provisions.

[0029] In the field of electronic payments, the security of electronic accounts needs improvement in some scenarios. For example, in some situations, if only the first user controls all payment permissions for their payment account, there may be security risks. In other situations, when the first user needs a second user to perform related operations on the first user's account, the second user needs to access the first user's payment account interface to perform the relevant operations, which is inconvenient and inflexible.

[0030] This paper proposes a method for setting account permissions in a multi-user collaborative manner. This method grants different permissions to multiple users for resource transfer operations on the same account, thereby improving payment security while ensuring ease of use. In one scenario, the proposed solution allows a first account to be associated with a first user and a second user. The first user possesses first permissions, which include configuring certain aspects of the second user's second permissions on the first account. This approach allows the second user to participate in account-related operations, reducing security risks in certain scenarios, while also enabling flexible configuration of the second user's permissions on the first account according to the first user's needs. This significantly improves the security of resource transfers in multi-user scenarios. When collaboration needs change, the first user does not need to recreate an account or change the association; they can adapt to the collaboration requirements by adjusting the second user's permissions, thus achieving flexible configuration of the first account.

[0031] In one scenario, the configurable second permission may include at least one of the following: the second user's scope of information viewing for the first account; the second user's permission to receive information from the first account; and the second user's second processing permission, wherein the second processing permission is used to process resource transfers made by the first user through the first account.

[0032] In one scenario, the provided solution receives a first trigger from a first user on a first account associated with a second user and displays a first interface for configuring at least some of the second permissions, allowing the first user to flexibly set the operational boundaries of the second user on the first account as needed. In another scenario, the provided solution enables multiple users to manage the same account according to their permissions. In yet another scenario, the provided solution can dynamically adjust security policies for different scenarios, thereby effectively improving payment security and usage flexibility of accounts in multi-user collaborative scenarios.

[0033] In some cases, the provided solution can be applied to Figure 1The information interaction system shown is a client 101 and a server 102. The client 101 may include, but is not limited to, web applications such as browsers, applications (Apps), Hyper Text Markup Language (HTML) applications, lightweight applications (also known as mini-programs), or cloud applications. The client 101 may be deployed on an electronic device and relies on the operation of that device or certain applications on the device to implement its functions. The electronic device may be, for example, a device with a display screen that supports information browsing, such as a smartphone, tablet, personal computer, or other client terminal. For ease of understanding, Figure 1 The client is primarily represented in the form of a device. Other applications, such as payment applications and session applications, can also be configured on the electronic device. Server 102 deploys an intelligent system, which can be one or more servers providing various services. That is, it can be implemented as a distributed server cluster composed of multiple servers, or as a single server; furthermore, it can be a distributed system server, a server integrating blockchain technology, a cloud server, or an intelligent cloud computing server or intelligent cloud host deployed with machine learning models, etc.

[0034] In some cases, the provided scheme can be executed by client 101. For example, in this document, client 101 receives a first trigger from a first user for a first account and displays a first interface for the first account on client 101. Furthermore, client 101 receives permission configuration operations through its first interface, whereby the first user configures at least a portion of the second permissions for a second user.

[0035] In some cases, the information interaction method can be executed by client 101, or by client 101 and server 102, with different functional parts of the information interaction deployed on client 101 and server 102 respectively. Specifically, the first and second modules of the information interaction device are deployed on client 101, and client 101 and server 102 achieve data interaction and functional collaboration through network communication. It should be understood that... Figure 1 The number of clients and servers shown is for illustrative purposes only. Any number of clients and servers can be configured to meet specific implementation requirements.

[0036] In some cases, client 101 and server 102 can implement the provided information interaction methods and payment information processing methods by running computer programs. For example, computer executable instructions can be microprogram-level commands, machine instructions, or software instructions. Computer programs can be native programs or software modules in an operating system; they can be native applications (APPs), i.e., programs that need to be installed in the operating system to run, such as video APPs or instant messaging APPs; or they can be applets that can be embedded in any APP, i.e., programs that only need to be downloaded to a browser environment to run. In short, the aforementioned computer executable instructions can be any form of instruction, and the aforementioned computer programs can be any form of application, module, or plugin.

[0037] Figure 2 This is a flowchart illustrating an information exchange method for one scenario, applicable to account permission configuration in electronic payments, such as a scenario where a first user configures permissions related to a second user within their first account. This information exchange method can be executed by an information exchange device, which can be implemented in software and / or hardware, optionally through a computer program. Figure 2 As shown, the information interaction method may include: S210, Receive a first trigger from the first user for the first account, the first account belongs to the first user and is associated with the second user, the first user has first permissions for the first account, and the second user has second permissions for the first account.

[0038] In this context, "first user" can be understood as the owner of the first account. That is, the first user owns the first account. In some cases, "first user" can be understood as the actual user of the first account. That is, the first user has the right to use the first account. In other cases, "first user" can be a user capable of initiating permission configuration operations for the first account. These permission configuration operations can be used to configure relevant permissions for a second user regarding the first account.

[0039] Optionally, the first user may be selected by the second user, and the method of determining the first user may include at least one of the following: determining the first user based on the user identifier entered by the second user; determining the first user based on the second user's user selection operation on the user list; or determining the user who receives the account activation link sent by the second user as the first user.

[0040] In one scenario, during the configuration of the first account, if a user identifier is received from the second user for the account configuration items, the user corresponding to the user identifier can be identified as the first user.

[0041] In another scenario, during the configuration of the first account, in response to the account configuration operation, a user list is displayed, which includes user identifiers of multiple candidate users. Furthermore, upon receiving an identifier selection trigger for any user identifier, the candidate user corresponding to the selected user identifier can be determined as the first user.

[0042] The first permission can be understood as the permission that the first user has over the first account. For example, the first permission may include at least one of the following: usage permission of the first account; first processing permission, used to process resource transfers through the first account; first configuration permission, used to configure at least some information of the first account; and second configuration permission, used to configure at least some of the permission content of the second permission. The first user can use the resources in the first account for processing based on the first permission, and can also configure the account information of the first account based on the first permission. The configured account information may include the relevant permissions of the second user over the first account. In one scenario, the first user's usage permission may include at least one of the following: resource transfer-out permission, used to transfer resources from the first account to a fourth account of the first user or a third user, where the fourth account is different from the first account; resource transfer-in permission, used to transfer resources into the first account; information viewing permission, used to view the resource transfer information of the first account; and information setting permission, used to adjust the information visibility range of the first account to the second user. The information visibility range includes at least one of the following: visible information content and the time range corresponding to the visible information content.

[0043] In one scenario, the second configuration permission may include at least one of the following: configuring the second user's information viewing scope for the first account; configuring the second user's information receiving permission for the first account; and configuring the second user's second processing permission, which is used to process resource transfers made by the first user through the first account. In some scenarios, the provided solution, by flexibly configuring the second user's permissions to view, receive, and process information transfers for the first account, achieves fine-grained control of account permissions, improving usability in co-management scenarios while ensuring account security.

[0044] It should be noted that the number of second users co-managing the first account with the first user can be one or more. If there is only one second user, the second user's information viewing scope, information receiving permissions, and second processing permissions for the first account can be directly configured. If there are multiple second users, the information viewing scope, information receiving permissions, and second processing permissions for each second user can be different, and each second user can be configured separately.

[0045] The information viewing scope can be understood as the permission boundary that a second user can view related information of a first account. The information viewing scope can be used to restrict the account information content that a second user can view, and this account information content can include at least one of the following: account information type, information detail level. The information viewing scope can be used in scenarios involving multi-user collaborative account management to restrict the visibility of a second user's account information to the first account, achieving hierarchical display of account information and privacy protection. The information viewing scope can include at least one of the following: the first account's balance information, the first account's resource transfer information within a first time period, the first account's transaction details for obtaining resources of a first resource type, transaction details where the resource transfer amount in the first account exceeds a first threshold, the first account's credit limit usage information, and the first account's bound platform information.

[0046] In some scenarios, the provided solution allows the first user to configure the information viewing scope of the second permission through a first interface. Optionally, the configuration method for the information viewing scope may include: displaying multiple first identifiers on the first interface, whereby the first identifiers indicate the information viewing scope for the first account; receiving selection operations for the first identifiers; and associating the selected first identifier with the second user. In some scenarios, the provided solution, through visual identifier display and association with selection operations, achieves intuitive and flexible configuration of the second user's information viewing scope, improving the convenience and accuracy of permission settings.

[0047] The first identifier can be understood as a visual indicator used to intuitively indicate the scope of information viewing. Each first identifier can correspond to a type of configurable account information viewing permissions.

[0048] In one scenario, there is only one second user associated with the first account. In response to the first user's permission configuration for the first account, a first interface is displayed, showing multiple first identifiers. Furthermore, upon receiving a selection operation for a first identifier, the selected first identifier can be associated with a second user, allowing the second user to view the first account's information based on the information viewing scope corresponding to the associated first identifier.

[0049] In another scenario, if there are multiple second users associated with the first account, in response to the first user's permission configuration for the first account, multiple user identifiers for the second users are displayed. Furthermore, upon receiving a selection operation for a user identifier, a first interface corresponding to the selected user identifier is displayed, and multiple first identifiers are shown on the first interface. Further, upon receiving a selection operation for a first identifier, the selected first identifier can be associated with the selected second user, allowing the second user to view the account information of the first account based on the information viewing scope corresponding to the associated first identifier.

[0050] The information receiving permission can be understood as the permission used to limit the second user's ability to receive notification messages related to the first account. The information receiving permission can be used to control whether to allow sending notification messages related to the first account to the second user, and the conditions that must be met to send such notification messages. Optionally, the configuration information related to the information receiving permission may include at least one of the following: a second condition that must be met to send a notification message to the second user, and the content of the message sent to the second user after the second condition is met.

[0051] The second condition can be understood as a trigger condition for determining whether to send a notification message to the second user. That is, if the first condition is met, a notification message related to the first account is sent to the second user. Optionally, the second condition may include at least one of the following: the first account performs a first resource transfer operation, the balance of the first account reaches a first value, the first account performs an abnormal transaction operation, or the difference between the usage limit and the usage limit of the first account is within a first interval; the first resource transfer operation may include at least one of the following: all resource transfer operations performed by the first account, resource transfer operations performed by the first account for resources of the first resource type, resource transfer operations performed by the first account within a second time period, or resource transfer operations performed by the first account where the amount of resource transfer exceeds a second threshold.

[0052] The information sent to the second user after the second condition is met can be understood as notification information related to the first account sent to the second user. Optionally, the information content may include at least one of the following: balance change information of the first account, resource transfer information of the first account, abnormal transaction notification information of the first account, credit limit usage information of the first account, and payment request information initiated by the first user through the first account.

[0053] The first account can be understood as a payment account belonging to the first user. The first account can be used to provide payment resources to the first user. The first account can support association and binding with a second user, enabling the first and second users to collaboratively manage the first account. Unlike single-user management accounts in related technologies, the information in the first account can support multi-user collaborative processing and the configuration of differentiated permissions. The first account can be used to meet the permission management needs of account information in multi-user collaborative management scenarios. For example, the first user can view all information in the first account, while the second user can view information in the first account that has been authorized by the first user. Another example is that the first user can view detailed information about resource transfers in the first account, which may include complete information such as the resource recipient identifier, the amount of resources transferred, the object identifier of the object involved in the transfer, and the resource transfer time; the second user, by default, views partial or summary information about resource transfers in the first account, which may include the object category of the object involved in the transfer and the amount of resources transferred. In short, the resource transfer information that the first user can view is more detailed than that of the second user. For example, the first user can transfer resources out of the first account. Unlike the first user, the first account can restrict the second user from transferring resources out of the first account, meaning the second user does not have the permission to transfer resources out of the first account.

[0054] In some cases, the activation of the first account may include at least one of the following: the second user actively activates the account for the first user; the first user sends an account activation request to the second user. The first account can be a payment account managed collaboratively by multiple people, such as a family account, a corporate reserve fund, or a guardian-managed account. For example, in the case of a family account, the first user can be a parent, and the second user can be a child; the parents can use the resources in the family account for payments; the children do not have access to the resources in the family account; and the children have viewing access to some information in the family account.

[0055] The second user and the first user are different users. The second user can be a user who collaborates with the first user to manage the information of the first account. In simpler terms, the second user can be any entity other than the first user that has administrative privileges over the first account. For example, the second user can be the user who opened the first account; the first user can be the user who uses the first account. Another example is that the first user can be the user who opened the first account, and the second user is the administrator appointed by the first user for the first account. The second user can collaborate with the first user to manage the resource processing of the first account.

[0056] Optionally, the second user may be selected by the first user. The method for determining the second user may include at least one of the following: determining the second user based on the user identifier entered by the first user; determining the second user based on the first user's user selection operation on the user list; or determining the user who received the account application link sent by the first user as the second user.

[0057] In one scenario, when applying to open a first account, the system receives the user identifier input by the first user, identifies the user corresponding to the received user identifier as the second user, and sends an account application request to the second user.

[0058] In another scenario, when applying to open the first account, the system receives the first user's user selection operation from the user list, identifies the selected user as the second user, and sends an account application request to the second user.

[0059] The second permission can be understood as the permission that the second user has over the first account. The second permission is used to manage the first account. The second permission includes at least the management permissions granted by the first user to the second user regarding the first account. In some cases, in the provided solution, the second permission may optionally include at least one of the following: viewing the first resource transfer information of the first user through the first account; receiving a first notification message indicating that the resource transfer by the first user through the first account meets a second condition or poses a risk; and a second processing permission used to process the resource transfer by the first user through the first account.

[0060] In some cases, the second permission may include: viewing information about the first user transferring first resources through the first account.

[0061] The first resource transfer information can be understood as at least a portion of the resource transfer information that can be viewed by the second user within the second resource transfer information of the first user through the first account. The second resource transfer information can be understood as all resource transfer information of the first user through the first account. Optionally, the first resource transfer information may include at least one of the following: a third identifier; a fourth identifier. The third identifier can be understood as identifier information representing the content of the object involved in the resource transfer process. The third identifier can be used to indicate the content of the object involved in the resource transfer process. The object involved in the resource transfer process can be understood as the object obtained after transferring resources from the first account. The content of the object involved in the resource transfer process may include at least one of the following: resource transfer time, resource transfer amount, resource transfer location, and resource transfer scenario. The fourth identifier can be understood as identifier information representing the resource type within the resources involved in the resource transfer process. The fourth identifier can be used to indicate the type of the object involved in the resource transfer process. For example, the type of object may include at least one of the following: daily necessities, food and beverage, transportation, and large-scale shopping.

[0062] In some cases, the provided solution allows a second user to view the first user's first resource transfer information through the first account based on their corresponding second permissions.

[0063] In some cases, the second permission may include receiving the first notification message.

[0064] The first notification message can be understood as an abnormal transaction notification pushed to the second user. The first notification message can be used to instruct the first user that resource transfer through the first account meets the second condition or that a risk exists. Optionally, the first notification message may include at least one of the following: balance change information of the first account, resource transfer information of the first account, abnormal transaction alert information of the first account, credit limit usage information of the first account, payment request information initiated by the first user through the first account, and resource transfer risk alert information.

[0065] The second condition can be understood as a pre-set trigger condition used to determine whether to send the first notification message to the second user. That is, if the second condition is met, a first notification message related to the first account is sent to the second user. In one scenario, by pre-setting the second condition to determine whether to send the first notification message to the second user, it is possible to identify scenarios where the second user needs to manage the first account, avoiding information interference caused by a large number of irrelevant notifications. It also ensures that, while improving the payment security of the first account, not all of the first user's transaction information needs to be synchronized to the second user, thereby reducing unnecessary information dissemination and the resources consumed by information transmission. This second condition is flexibly configurable, allowing the second user to receive timely reminders when the preset rules are met, thus improving the efficiency of the second user's management of the first account.

[0066] Optionally, the second condition may include at least one of the following: the first account performs a first resource transfer operation, the balance of the first account reaches a first value, the first account performs an abnormal transaction operation, or the difference between the usage limit and the usage limit limit of the first account is within a first interval; the first resource transfer operation may include at least one of the following: all resource transfer operations performed by the first account, resource transfer operations performed by the first account for resources of the first resource type, resource transfer operations performed by the first account within a second time period, or resource transfer operations performed by the first account where the amount of resource transfer exceeds a second threshold.

[0067] In one scenario, if the resource transfer amount by the first user through the first account exceeds a second threshold, it is determined that the resource transfer meets the second condition. Further, a first notification message corresponding to the resource transfer is generated and sent to the second user. In another scenario, the provided solution can automatically detect whether the resource transfer amount exceeds the limit. Once the limit is exceeded, it determines that the second condition is met and sends a notification to the second user, achieving automated identification of resource transfers exceeding the set limit. The second user can be informed of resource changes in the first account without manually checking the resource transfer information. Furthermore, collaborative management by the second user helps improve the security of resource transfers by the first account.

[0068] In another scenario, in response to the risk of resource transfer by the first user through the first account, a first notification message corresponding to the resource transfer is generated and sent to the second user. In one scenario, the provided solution links risk identification with the notification mechanism, enabling the second user to be aware of risk events before potential losses occur, enhancing the account's risk control capabilities, helping to mitigate risks caused by resource transfers through the first account, and improving the security of resource processing by the first account in certain scenarios. In some cases, the second permission may include: a second processing permission, used to process resource transfers by the first user through the first account.

[0069] The second processing permission can be understood as the permission of the second user to process resource transfer information generated by the first user through the first account. In other words, the second processing permission can be used to allow the second user to block or confirm resource transfer operations performed by the first user through the first account. Resource transfer can be understood as the first user performing resource flow operations such as payment, transfer, and consumption through the first account.

[0070] In one scenario, the proposed solution grants a second user the authority to process resource transfer information generated by the first user through the first account, thereby making the resource transfer process no longer entirely dependent on the unilateral operation of the first user, but allowing for processing by the second user. This effectively reduces the abnormal risks associated with resource transfers by the first user through the first account and significantly improves the security of resource transfers through the first account.

[0071] In some scenarios, the provided solution allows for sending a resource transfer notification to the second user when the first user initiates a resource transfer request to the first account and the resource transfer information related to the request meets the second condition. Furthermore, upon receiving the resource transfer notification, the second user can process the resource transfer information according to their second processing authority.

[0072] In certain circumstances, if a first user initiates a resource transfer request to a first account, and the amount of resources transferred in connection with the request exceeds a third threshold, a resource transfer notification may be sent to a second user. Furthermore, upon receiving the resource transfer notification, the second user may, based on second processing authority, block the resource transfer information, thereby preventing the first user from completing the payment through the first account.

[0073] The first trigger can be understood as an operation input by the first user on the interactive interface of the first account. In other words, the first trigger can be an interactive operation performed by the first user to initiate the permission configuration process of the first account, such as clicking a specific control in the interactive interface. In some cases, the first trigger can be used to initiate the permission configuration process of the first account. For example, the first trigger can be an operation initiated by the first user, which can be used to trigger the display of the permission configuration interface of the first account; or, for example, the first trigger can be a voice command, which instructs the configuration of permissions for the first account. Optionally, the first trigger can include at least one of the following: a trigger operation by the first user on a permission setting control; a selection operation by the first user on a permission configuration option; a permission configuration request for the first account initiated by the first user via a voice command; the first user clicking on the first account in the account list to bring up the operation menu and selecting a permission setting item; or the first user initiating the permission configuration operation of the first account through a shortcut.

[0074] S220. Display the first interface of the first account, the first interface being used by the first user to configure at least some of the permissions of the second permission.

[0075] The first interface can be understood as the interactive interface related to the first user and the first account. This interface can be used to configure the information viewing scope of the first permission. The first interface can be the information display interface and operation receiving interface of the first account. The first interface can be used by the first user to configure at least some of the permission content of the second permission. The first interface can be used by the first user to configure and adjust at least some of the permission content of the second user's second permission through interactive operations. The presentation form of the first interface can include at least one of the following: mobile application interface; computer platform interface; web client interface; H5 web page interface. The first user can configure all or part of the permission content of the second permission.

[0076] It should be noted that the first interface can be associated with a second user. When there are multiple second users, different second users can correspond to different first interfaces. The first interface can display the account permission information corresponding to the corresponding second user, as well as receive permission configuration operations for the second permissions of the corresponding second user.

[0077] In one scenario, if there is only one second user associated with the first account, a first trigger from the first user regarding the first account is received, and the first interface of the first account is displayed. Further, a permission configuration trigger from the first user regarding the first interface is received, and the permission content of the second user's second permissions is configured according to the received permission configuration trigger.

[0078] In another scenario, if there are multiple second users associated with the first account, a first trigger from the first user regarding the first account is received, and the user identifiers of the multiple second users associated with the first account are displayed. Furthermore, upon receiving a selection operation for a user identifier, the first interface of the second user corresponding to the selected user identifier can be displayed. Further, a permission configuration trigger from the first user regarding the first interface is received, and the permission content of the second permissions for the selected second user is configured according to the received permission configuration trigger.

[0079] For example, Figure 3 This is a schematic diagram of the first interface in one scenario. For example... Figure 3 As shown, the first interface 30 includes four information viewing range options: information viewing range 301, information viewing range 302, information viewing range 303, and information viewing range 304. Information viewing range 301 is used to configure viewing permissions for the first account's balance information; information viewing range 302 is used to configure that only risky transactions can be viewed; information viewing range 303 is used to configure that only transactions with resource transfer amounts exceeding a first threshold can be viewed; and information viewing range 304 is used to configure that all transactions are visible. The first interface also includes an information receiving permission option, information receiving permission 305, which is used to configure sending a notification message to the second user when the first account's balance is less than a second threshold.

[0080] In some cases, to further ensure the security of resource processing for the first account, the provided solution can perform risk detection on resource transfer operations performed by the first user on the first account. Furthermore, if a risk is detected in the resource transfer operation, a risk notification is sent to the second user.

[0081] Optionally, the provided solution also includes: receiving a third trigger from the first user and sending the first information to the second user. In some cases, the provided solution can proactively push the first information to the second user by responding to the third trigger, realizing real-time interaction of authorization and notification between users and improving the real-time performance and interaction efficiency of account association operations.

[0082] The third trigger can be understood as a resource transfer initiated by the first user for the first account. The third trigger is used to process the resources of the first account. For example, processing the resources of the first account may include at least one of the following: resource transfer-out processing, payment processing. Optionally, the third trigger may include at least one of the following: a resource transfer-out request from the first user for the first account; a payment request from the first user for the first account.

[0083] In one scenario, the first message can be understood as a risk warning sent to the second user. The first message can be used to indicate to the first user that there is a risk in the first user's handling of resources related to the first account. The first message can be used to explicitly inform the first user that they are currently performing resource handling operations on the first account, and that such resource handling operations are risky.

[0084] In one scenario, "risk of resource processing" indicates that resource processing may affect the information security or resource security of the first account. For example, the risk of resource processing may include at least one of the following: the amount of resource processing exceeds a preset security threshold; the transaction object of the resource processing is an unfamiliar account or a non-whitelisted account; the resource processing occurs during a preset risk period; the location or device of the resource processing is a first-time use or abnormal login environment; multiple resource processing operations are initiated consecutively within a short period; the purpose or scenario of the resource processing is of a high-risk type; or the first account is currently in an abnormal state when initiating resource processing.

[0085] In one scenario, the first information may be sent in at least one of the following ways: sending the first information to the second user via a telecommunications operator's network; sending the first information to the second user via an email system; or sending the first information to the second user via a chat interface between the first user and the second user.

[0086] In one scenario, in response to receiving a resource transfer request from a first user for a first account, if the amount of resource processing corresponding to the resource transfer request exceeds a preset security threshold, it is determined that there is a risk in the first user's processing of resources for the first account, first information is generated to indicate that there is a risk in the resource processing, and the first information is sent to a second user so that the second user can be aware of it in a timely manner and supervise or intervene in the resource processing.

[0087] In some scenarios, the provided solution allows for the activation of a first account before the first account is applied. The activation process for the first account may include: displaying a second interface for the first user to activate the first account; furthermore, it may include at least one of the following: the second interface is displayed via a fourth trigger, which is used by the second user to invite the first user to activate the first account; or, the second interface includes a first area displaying the second user's information; and, in response to authentication of the first user, displaying the activation status of the first account. In some scenarios, the provided solution achieves integrated display and identity authentication linkage of the invitation-to-activate process, clearly defining the invitation relationship while ensuring the security and continuity of the account activation process.

[0088] The second interface can be understood as the interactive interface used by the first user to open the first account. The second interface can be used to display the account opening process and the second user's information. The presentation format of the second interface can include at least one of the following: a mobile application interface; a desktop platform interface; a web client interface; or an H5 webpage interface.

[0089] In one scenario, the second interface is displayed via a fourth trigger. This can be understood as the second interface not being actively triggered by the first user, but rather appearing after receiving a fourth trigger from the second user. The fourth trigger can be understood as an account activation invitation initiated by the second user to the first user. The fourth trigger can be used by the second user to invite the first user to activate the first account.

[0090] Optionally, the fourth trigger may include at least one of the following: sending an invitation message to the first user via a communication operator's network, the content of which may include text information, multimedia information, link information, etc.; sending an invitation message to the first user via email; sending an invitation message to the first user through a conversation interface between the second user and the first user; or receiving a scan operation by the first user on a multi-dimensional code displayed by the second user.

[0091] In some cases, in the provided solution, in response to receiving a fourth trigger initiated by a second user to a first user, a second interface is displayed to the first user. The first area can be understood as an independent display area on the second interface. The first area can be used to display information about the second user who initiated the fourth trigger. The first area can be located anywhere on the second interface. Optionally, the location of the first area on the second interface can include at least one of the following: top, bottom, left, and right. The information of the second user can be understood as identification information used to uniquely identify the second user. Optionally, the information of the second user can include at least one of the following: user nickname, user avatar, user identity identifier, and relationship with the first user.

[0092] It should be noted that the number of second users associated with the first account can be one or more. To ensure that the first user is aware of the second user who invited them to open the first account, the information of the second user who initiated the fourth trigger can be displayed on the second interface. Authentication of the first user can be understood as verifying the first user's identity, which may include at least one of the following: real-name verification, facial verification. The activation status can be understood as the account activation result fed back to the first user. Optionally, the activation status may include at least one of the following: account opening successful, account opening in progress, authentication failed, account opening failed, information to be supplemented.

[0093] In some cases, the provided solution can confirm that the first account has been successfully activated and display the first account information to the first user if the first user authentication is successful.

[0094] Optionally, in response to authentication of the first user, the activation status of the first account is displayed, including: receiving first attribute information provided by the first user through the second interface, and displaying the information of the first account in response to successful verification of the first attribute information.

[0095] The first attribute information can be understood as the identity and account-related information submitted by the first user when opening the first account. The first attribute information can be used to uniquely identify the first user. Optionally, the first attribute information may include at least one of the following: user name, user identifier, user facial information, and relationship information with the second user. The information of the first account can be understood as the account content related to the first account. Optionally, the information of the first account may include at least one of the following: account number, account limit, account status, information of the associated second user, and permission configuration entry.

[0096] In one scenario, in response to a fourth trigger that receives an invitation from a second user to the first user to activate a first account, a second interface is displayed to the first user, and the information of the second user who initiated the fourth trigger is shown in the first area of ​​the second interface. Furthermore, the second interface receives first attribute information provided by the first user. If the received first attribute information is verified, it can be determined that the first account has been successfully activated, and the information of the first account is displayed.

[0097] To allow the first user to intuitively understand the management status of the first account, after configuring the second user, the system can also display the second users that have been associated with the first account. Optionally, the provided solution may also include: displaying the second users associated with the first account, with one or more second users.

[0098] The information displayed for the second user may include at least one of the following: user nickname, user avatar, user identity identifier, relationship with the first user, and type tag.

[0099] In one scenario, after configuring the second user, the interface can display information about all the second users who have been associated with the first account, so that the first user can intuitively view all the second users bound to the first account, making it easier for the first user to configure and manage the second users separately.

[0100] For example, Figure 4 This is a schematic diagram illustrating the interface for displaying a second user in one scenario. For example... Figure 4 As shown, the display interface shows two second users, namely Second User A and Second User B. The information displayed for the second users includes: user avatar, user name, relationship with the first user, type label, and association with the first account. The type label for Second User A can be "Main Administrator," and the type label for Second User B can be "Assistant Administrator." The display interface also shows the second user's add control 41 and permission description 42, which can include: viewing the account balance; recharging the first account; viewing the first account's anonymized statements; receiving risk transaction notifications; and being unable to spend or transfer funds.

[0101] In some scenarios, because the first account is associated with both a first user and a second user, and the first user has first-level permissions while the second user has second-level permissions, this multi-user permission structure allows the same payment account to serve the operational needs of different roles. In other scenarios, configuring at least some of the second user's permissions through the first interface allows the first user to flexibly set the permissions available or restricted for the second user based on actual payment scenarios or management needs. This simplifies the second user's operational path while ensuring account security, reduces payment interruptions or additional authorization steps caused by unclear permissions, and supports visual display of permission configuration, improving the flexibility and convenience of permission configuration. In still other scenarios, based on the first user's first permissions to the first account, pre-defining and on-demand adjusting the second user's permissions helps unify account management rules, reduces abnormal handling processes caused by insufficient or unauthorized operations during payment, and thus improves the overall operational efficiency and security of the payment system.

[0102] Figure 5 This is a flowchart illustrating an information interaction method under another scenario. The solution provided in this scenario can be combined with implementation methods in other scenarios. For the same or related parts, they can be described in conjunction with the descriptions of other scenarios, and will not be repeated here. Figure 5 As shown, the method in this case may specifically include: S310, Receive a first trigger from the first user for the first account, the first account belongs to the first user and is associated with the second user, the first user has first permissions for the first account, and the second user has second permissions for the first account.

[0103] S320. Display the first interface of the first account. The first interface is used by the first user to configure at least some of the permissions of the second permission.

[0104] S330: Receive the second trigger and adjust the second user's second permissions.

[0105] The second trigger can be understood as an operation command initiated by the first user to trigger the dynamic adjustment process of the second permission. The second trigger can be used to initiate the permission adjustment process for the second permission. The second trigger can be used to adjust the permission content of the second permission. Optionally, the second trigger can be used for at least one of the following: modifying the second permission of the second user, configuring the second user associated with the first account, or changing the type tag corresponding to the second user; The second user with different tag types has different second permissions. Modifying the second user's second permissions can be understood as the first user, through a second trigger, changing the content of the second permissions of the associated second user. The change of permission content may include at least one of the following: modifying the information viewing scope of the first account, modifying the information receiving permissions of the first account, or modifying the second processing permissions of the second account.

[0106] Configuring a second user associated with a first account can be understood as the first user managing a user list of the second user associated with the first account through a second trigger. This user list management can include at least one of the following: adding a second user, unbinding an already associated second user, or changing the association status of a second user. A type tag can be understood as a classification identifier used to identify the role type of a second user. Second users with different type tags have different second permissions. In some cases, the provided solution can pre-set at least one type tag and set corresponding account permissions for each type tag. Furthermore, when a second user is associated with any type tag, the account permission corresponding to the associated type tag can be determined as the second permission of that second user. Optionally, the type tag can include at least one of the following: primary administrator, secondary administrator.

[0107] Change the type label for the second user. This can be understood as the first user adjusting the second user's type label through a second trigger. Changing the type label for the second user can be used to quickly switch the second user's permission level.

[0108] In one scenario, a second trigger is received to modify the second user's second permissions, and the permission content of the triggered second user's second permissions is modified.

[0109] In one scenario, a second trigger is received to configure a second user associated with a first account, the second user associated with the first account is configured, and an association is established between the first account and the configured second user.

[0110] In another scenario, a second trigger is received to change the type label corresponding to the second user, the type label corresponding to the triggered second user is changed, and the second permission corresponding to the second user is determined based on the changed type label.

[0111] In some cases, the beneficial effects of the provided exemplary solutions include: the ability to dynamically adjust the permissions of a second user in response to user-triggered actions, enabling flexible changes to shared account permissions and improving the convenience and real-time nature of permission management.

[0112] Figure 6 This is a flowchart illustrating an information interaction method for one scenario, applicable to mobile payment account information viewing, such as a scenario where a second user views information about their associated first account. This information interaction method can be executed by an information interaction device, which can be implemented in software and / or hardware, optionally through a computer program. Figure 6 As shown, the information interaction method may include: S410, Display the third interface, which is associated with the second user.

[0113] The third interface can be understood as the interactive interface provided to the second user. The third interface can be used to display information about the first account and receive account configuration operations from the second user for the first account.

[0114] In one scenario, the presentation of the third interface may include at least one of the following: a mobile application interface; a computer platform interface; a web client interface; or an H5 web page interface.

[0115] In one scenario, the third interface is associated with the second user and may include at least one of the following: the third interface is a visual operation interface for the second user targeting the first account; the third interface displays the account information of the first account; the operation permissions of the third interface are only open to the currently logged-in second user; the operation data generated by the third interface can be bound and stored with the second user.

[0116] It should be noted that when the first account is associated with more than one second user, the third interface associated with each second user can be different. In other words, the content displayed on the third interface associated with different second users can be different.

[0117] In some cases, the provided solution associates the third interface with the second user, including at least one of the following: the third interface is displayed through a second account belonging to the second user; or the third interface is displayed through a device associated with the second identifier, which is associated with the second user.

[0118] Optionally, the third interface may be associated with the second user, including: displaying the third interface through the second account, where the second account belongs to the second user.

[0119] The second account can be understood as a payment account belonging to the second user. The second user has the right to use and own the second account.

[0120] In one scenario, for at least one second user associated with the first account, the system receives an account login operation from the second user, logs into the second account, and displays a third interface associated with the second user through the second account.

[0121] Optionally, the third interface is associated with the second user, including: displaying the third interface through a device associated with the second identifier, wherein the second identifier is associated with the second user.

[0122] The second identifier can be understood as information used to identify the second user. Optionally, the second identifier may include at least one of the following: a barcode, a multi-dimensional barcode, an invitation code, a device binding code, or a serial number.

[0123] The device associated with the second identifier can be a terminal hardware device that has been pre-bound to the second identifier. The device associated with the second identifier can have completed the binding authentication of the second identifier and is used to display the interactive interface; for example, it can be a terminal device such as a mobile phone, tablet computer, or personal computer.

[0124] In one scenario, for at least one second user associated with a first account, a device pre-bound to a second identifier of the second user is identified, and a third interface associated with the second user is displayed on the device.

[0125] S420: The information of the first account is displayed through the third interface. The first account belongs to the first user.

[0126] The information of the first account can be understood as information associated with the first account. In one scenario, the first user has primary permissions to the first account, and the information of the first account displayed through the third interface is associated with these primary permissions.

[0127] In some cases, the provided solution displays information about the first account, including: displaying second information about the first account, the second information being associated with resource transfers made by the first user through the first account, the second user having second permissions to the first account, and the second information being associated with the second permissions.

[0128] The second information can be understood as related information concerning the resource transfer of the first account and viewable with the second user's permissions. The second information may be various related data, status content, and prompts generated after the first user transfers resources through the first account. This information may be information that is allowed to be displayed to the second user after permission filtering according to the second user's second permissions. Optionally, the second information may include at least one of the following: first resource transfer information of the first user through the first account; resource transfer risk notification messages; resource transfer processing information.

[0129] In some cases, displaying second information about the first account includes at least one of the following: in response to at least a first condition being met, displaying first resource transfer information of the first user through the first account, wherein the first condition includes first configuration information indicating that the second user is allowed to view the first resource transfer information of the first account, the first configuration information being configured by the first user; or... Upon receiving a first notification message, the first notification message indicates that the first user's resource transfer through the first account satisfies the second condition or that a risk exists; or, Display a first control, which is used to process resource transfers made by the first user through the first account; or... The first processing prompt is displayed to prompt the second user whether to enter a processing command or confirm the processing command. The processing command is used to process the resource transfer performed by the first user through the first account.

[0130] In some cases, the beneficial effects of the provided exemplary solutions include: by associating a third interface with a second user and displaying the information of the first account (belonging to the first user) on that interface, a scenario of "displaying the account information of another user (the first user) on the interface of a specific user (the second user)" is realized, which makes it convenient for the second user to quickly view, verify or operate the account content related to the first user.

[0131] In some cases, the beneficial effects of the provided exemplary solutions include: applicability to scenarios requiring cross-user access to account information, such as family member management, corporate sub-account management, authorized agency or supervision scenarios (e.g., parents viewing children's accounts, financial personnel viewing principals' accounts, etc.), and improved system availability under multi-user collaboration or authorization delegation.

[0132] In some cases, the beneficial effects of the provided exemplary solutions include: since the interface is clearly associated with the second user, the system can design independent access control logic accordingly to ensure that the information of the first account is only visible to specific second users, avoiding global disclosure, thereby balancing information sharing and data security.

[0133] In some cases, the beneficial effects of the provided exemplary solutions include: the second user can directly view the information of the first account on the same third interface without switching accounts or jumping to multiple pages, reducing operation steps and improving efficiency and experience.

[0134] Figure 7 This is a flowchart illustrating an information interaction method under another scenario. The solution provided in this scenario can be combined with implementation methods in other scenarios. For the same or related parts, they can be described in conjunction with the descriptions of other scenarios, and will not be repeated here. Figure 7 As shown, the method in this case may specifically include: S510, Display the third interface, which is associated with the second user.

[0135] S520, in response to at least the first condition being met, the first user's first resource transfer information through the first account is displayed on the third interface.

[0136] The first condition can be understood as the triggering condition for granting the second user permission to view the first resource transfer information. If at least the first condition is met, the first resource transfer information transferred by the first user through the first account can be displayed to the second user. The first condition may include first configuration information indicating that the second user is allowed to view the first resource transfer information of the first account, where the first configuration information is configured by the first user. Meeting at least the first condition can be understood as a necessary condition for viewing the first resource transfer information.

[0137] The first configuration information can be understood as the permission rules configured by the first user, which can be used to limit the information viewing permissions of the second user.

[0138] In one scenario, the provided solution, upon meeting the first condition, can obtain the first resource transfer information of the first user through the first account and display the first resource information through a third interface. In some cases, to further protect the account privacy and information security of the first user and prevent the second user from viewing the resource transfer information generated by the first user through the first account without authorization, the provided solution allows for viewing with authorization when displaying the resource transfer information generated by the first user through the first account.

[0139] Optionally, displaying the first resource transfer information of the first user through the first account includes: in response to the fifth trigger of the second user, sending a first request to the first user; and in response to the first user allowing the second user to view the first resource transfer information, displaying the first resource transfer information.

[0140] The fifth trigger can be understood as an interactive operation command initiated by the second user, which can be used by the second user to view the resource transfer information of the first account. The first request can be understood as a resource transfer viewing request sent to the first user. The first request can be used to ask whether the second user is allowed to view the resource transfer information of the first account.

[0141] In one scenario, in response to a second user's request to view resource transfer information for the first account, a first request is sent to the first user. Furthermore, upon receiving a trigger from the first user granting permission for the second user to view resource status information in response to the first request, the resource transfer information for the first account is displayed to the second user.

[0142] In some cases, the beneficial effects of the provided exemplary solution include: the resource transfer information of the first account can be displayed on the second user's exclusive interface according to the permission configuration, realizing transparent information display under hierarchical permissions, which makes it easier for the second user to accurately manage the transfer of resources in the account.

[0143] Figure 8 This is a flowchart illustrating an information interaction method under another scenario. The solution provided in this scenario can be combined with implementation methods in other scenarios. For the same or related parts, they can be described in conjunction with the descriptions of other scenarios, and will not be repeated here. Figure 8 As shown, the method in this case may specifically include: S610, Display the third interface, which is associated with the second user.

[0144] S620: Receive the first notification message through the third interface.

[0145] The first notification message indicates that the first user's resource transfer through the first account meets the second condition or that there is a risk. In some cases, the first notification message can be understood as an abnormal transaction notification pushed to the second user. For example, the first notification message may include at least one of the following: balance change information of the first account, resource transfer information of the first account, abnormal transaction prompt information of the first account, credit limit usage information of the first account, payment request information initiated by the first user through the first account, and resource transfer risk warning information.

[0146] The second condition can be understood as a trigger condition for determining whether to send the first notification message to the second user. That is, if the second condition is met, a first notification message related to the first account is sent to the second user. For example, the second condition may include at least one of the following: the first account performs a first resource transfer operation, the balance of the first account reaches a first value, the first account performs an abnormal transaction operation, or the difference between the usage limit and the usage limit of the first account is within a first interval; the first resource transfer operation may include at least one of the following: all resource transfer operations performed by the first account, resource transfer operations performed by the first account for resources of the first resource type, resource transfer operations performed by the first account within a second time period, or resource transfer operations performed by the first account where the amount of resource transfer exceeds a second threshold.

[0147] In one scenario, if the amount of resource transfer by the first user through the first account exceeds a second threshold, it is determined that the resource transfer meets the second condition. Further, a first notification message corresponding to the resource transfer is generated and sent to the second user.

[0148] In another scenario, in response to the risk of resource transfer by the first user through the first account, a first notification message corresponding to the resource transfer is generated and sent to the second user.

[0149] In some cases, the beneficial effects of the provided exemplary solutions include: pushing account transaction and risk notifications to the second user's dedicated interface, enabling the second user to be aware of abnormal transactions in the first account in a timely manner, thereby improving the timeliness of account management and risk warning capabilities.

[0150] Figure 9 This is a flowchart illustrating an information interaction method under another scenario. The solution provided in this scenario can be combined with implementation methods in other scenarios. For the same or related parts, they can be described in conjunction with the descriptions of other scenarios, and will not be repeated here. Figure 9 As shown, the method in this case may specifically include: S710, Display the third interface, which is associated with the second user.

[0151] S720: The first control is displayed through a third interface.

[0152] The first control is used to process resource transfers made by the first user through the first account. In one scenario, the first control can be understood as a clickable control or operation entry point displayed on the interface. The first control can be used to process resource transfers made by the first user through the first account.

[0153] In one scenario, the first control allows a second user to intervene in resource transfers performed by the first user through the first account. For example, the intervention operation may include at least one of the following: confirmation, rejection, freezing, interception, reminder, and identity verification. The display timing of the first control may include at least one of the following: the first user performs a resource transfer through the first account; the amount of resources transferred by the first user through the first account exceeds a preset threshold; the time of the resource transfer performed by the first user through the first account falls within a preset time period; or the resource type transferred by the first user through the first account is a preset resource type.

[0154] In one scenario, the control form of the first control may include at least one of the following: an operation button, a switch slider control, a selection box control, a slide confirmation control, or a pop-up confirmation control.

[0155] In one scenario, in response to the first user transferring more resources through the first account than a preset threshold, a notification is sent to the second user. Furthermore, upon receiving the notification, the second user displays a first control corresponding to this resource transfer.

[0156] In some scenarios, to facilitate timely intervention by a second user upon learning of risks or anomalies related to resource transfers, thus ensuring the security of resources within the first account, the provided solution, in addition to displaying a primary control for handling resource transfer operations on the interface, also provides a corresponding resource transfer processing flow: responding to the display of the primary control, receiving a sixth trigger on the primary control, and processing resource transfers made by the first user through the first account. In some cases, the provided solution directly executes resource transfer processing by triggering the primary control, achieving rapid intervention in risky or abnormal resource transfers, and improving operational efficiency and fund security in account co-management scenarios.

[0157] The sixth trigger can be understood as an operation instruction executed by the second user on the first control, which can be used to intervene in the resource transfer. Optionally, the sixth trigger can be used for at least one of the following: canceling the resource transfer, interrupting the resource transfer, or performing a resource return operation corresponding to the resource transfer process. Canceling the resource transfer can be understood as withdrawing the current resource transfer application, so that the transaction is not executed and does not take effect. Interrupting the resource transfer can be understood as terminating the process during the resource transfer execution and stopping the continued transfer of resources. The resource return operation can be understood as the operation of returning the transferred resources to the original account after the resource transfer has been partially or fully completed.

[0158] In one scenario, if the first control is included in the information of the first account displayed, a second trigger is received for canceling the resource transfer using the first control, and the resource transfer performed by the first user through the first account is canceled.

[0159] In another scenario, if the first control is included in the information of the first account displayed, a second trigger is received for interrupting the resource transfer of the first control, and the resource transfer process performed by the first user through the first account is interrupted, stopping the continued transfer of resources.

[0160] In some cases, the beneficial effects of the provided exemplary solutions include: by displaying the first control on a third interface dedicated to the second user, the second user can quickly perform account-related operations, thereby improving the convenience and targeted nature of account management.

[0161] Figure 10 This is a flowchart illustrating an information interaction method under another scenario. The solution provided in this scenario can be combined with implementation methods in other scenarios. For the same or related parts, they can be described in conjunction with the descriptions of other scenarios, and will not be repeated here. Figure 10 As shown, the method in this case may specifically include: S810, Display the third interface, which is associated with the second user.

[0162] S820: The first processing prompt is displayed through the third interface.

[0163] The first processing prompt is used to prompt the second user whether to input or confirm a processing instruction. The processing instruction is used to process the resource transfer performed by the first user through the first account. The first processing prompt can be understood as a prompt message displayed on the interface, which guides the second user to input or select a processing instruction. The processing instruction is used to process the resource transfer performed by the first user through the first account. The information format of the second prompt message can include at least one of the following: text prompt, voice prompt, graphic prompt, and video prompt. The processing instruction can be understood as an operation instruction issued by the second user through input, selection, or click operations, which can be used to indicate the processing method for the resource transfer performed by the first user through the first account. Optionally, the processing instruction includes at least one of the following: voice instruction, text instruction, and action instruction.

[0164] Optionally, the provided solution may further include: in response to displaying a first processing prompt, receiving a processing instruction input by a second user, and processing a resource transfer performed by the first user through a first account.

[0165] In one scenario, in response to a first user performing a resource transfer through a first account, a first processing prompt corresponding to the resource transfer is displayed on a third interface associated with the second user. Further, in response to receiving a voice command input by the second user, the resource transfer is processed according to the received voice command.

[0166] For example, in a scenario where the second user interacts with the corresponding third interface via voice, a voice command can be used to prompt the second user: "You can cancel the first user's processing of this order. Please confirm whether to cancel." Furthermore, upon receiving a cancellation instruction from the second user, the order is cancelled. For instance, if the second user says "cancel," the order is cancelled.

[0167] In scenarios where the second user interacts with their corresponding third interface through action commands, a second prompt message can be sent to the second user: "You have the authority to process a refund for this order. Please confirm whether you need a refund." Furthermore, upon receiving a confirmation request for a refund from the second user, the refund operation can be executed for the order.

[0168] In some cases, the beneficial effects of the provided exemplary solutions include: by displaying a dedicated third interface for the associated second user and popping up corresponding processing prompts, the second user can be accurately reminded to perform account-related management operations in a timely manner, thereby improving the efficiency of information interaction and the relevance of information reminders.

[0169] Figure 11 This is a flowchart illustrating an information exchange method for one scenario, applicable to mobile payment account opening, such as a scenario where a second user opens a first account for a first user. This information exchange method can be executed by an information exchange device, which can be implemented in software and / or hardware, optionally through a computer program. Figure 11 As shown, the information interaction method may include: S910, Display the second interface, which is used for the first user to open the first account.

[0170] This includes at least one of the following: the second interface is displayed via a fourth trigger, which is used by the second user to invite the first user to open a first account; or, the second interface includes a first area that displays the second user's information.

[0171] S920, in response to authentication of the first user, displays the activation status of the first account.

[0172] The authentication of the first user can be understood as verifying the identity of the first user, which may include at least one of the following: real-name verification and facial verification. The activation status can be understood as the account activation result returned to the first user. Optionally, the activation status may include at least one of the following: successful account opening, account opening in progress, authentication failed, account opening failed, and information pending.

[0173] In some cases, the provided solution can confirm that the first account has been successfully activated and display the first account information to the first user if the first user authentication is successful.

[0174] Optionally, in response to authentication of the first user, the activation status of the first account is displayed, including: receiving first attribute information provided by the first user through the second interface, and displaying the information of the first account in response to successful verification of the first attribute information.

[0175] The first attribute information can be understood as the identity and account-related information submitted by the first user when opening the first account. The first attribute information can be used to uniquely identify the first user. Optionally, the first attribute information may include at least one of the following: user name, user identifier, user facial information, and relationship information with the second user. The information of the first account can be understood as the account content related to the first account. Optionally, the information of the first account may include at least one of the following: account number, account limit, account status, information of the associated second user, and permission configuration entry.

[0176] In one scenario, in response to a fourth trigger that receives an invitation from a second user to the first user to activate a first account, a second interface is displayed to the first user, and the information of the second user who initiated the fourth trigger is shown in the first area of ​​the second interface. Furthermore, the second interface receives first attribute information provided by the first user. If the received first attribute information is verified, it can be determined that the first account has been successfully activated, and the information of the first account is displayed.

[0177] For example, Figure 12 This is a schematic diagram of the interface for authenticating the first user in one scenario. For example... Figure 12 As shown, the display interface includes a facial authentication area 701 and an authentication information risk warning 702. The facial authentication area 701 receives the first user's facial information to authenticate the first user. Further, if the user's facial information verification is successful, the first account information is displayed to the first user, as shown in the image. Figure 13 As shown. Figure 13 This is a schematic diagram of an interface displaying information for the first account in one scenario. For example... Figure 13As shown, the display interface includes an activation status display area 801, a card display area 802 for the first account, a resource transfer control 803, an account binding control 804, and a display area 805 showing the association information between the second user and the first account. Figure 13 As shown, once the user's facial information verification is successful, the first account is activated. The activation status display area 801 can show that the first account has been successfully activated. The card display area 802 can display the information of the first account, including the account name, the amount of resources in the first account, and the account identifier. The resource transfer control 803 can be used to transfer resources to the first account. The account binding control 804 can be used to bind the first account to the payment account of the second user. The association information display area 805 can display the username of the second user A associated with the first account, the relationship between the second user A and the first user A, and the association relationship between the second user A and the first account A.

[0178] In some cases, the provided solution may also include at least one of the following: the first user has a first permission to the first account, and the second user has a second permission to the first account, wherein the first permission includes configuring at least a portion of the permission content in the second permission; or, the second user has a second permission to the first account, wherein second information of the first account is associated with the second permission, and the second information is associated with resource transfers performed by the first user through the first account.

[0179] The first permission can be understood as the permission that the first user has over the first account. For example, the first permission may include at least one of the following: usage permission of the first account; first processing permission, used to process resource transfers through the first account; first configuration permission, used to configure at least some information of the first account; and second configuration permission, used to configure at least some of the permission content of the second permission. The first user can use the resources in the first account for processing based on the first permission, and can also configure the account information of the first account based on the first permission. The configured account information may include the relevant permissions of the second user over the first account. In one scenario, the first user's usage permission may include at least one of the following: resource transfer-out permission, used to transfer resources from the first account to a fourth account of the first user or a third user, where the fourth account is different from the first account; resource transfer-in permission, used to transfer resources into the first account; information viewing permission, used to view the resource transfer information of the first account; and information setting permission, used to adjust the information visibility range of the first account to the second user. The information visibility range includes at least one of the following: visible information content and the time range corresponding to the visible information content.

[0180] The second information can be understood as related information that is bound to the resource transfer of the first account and is viewable with the second user's permissions. The second information may be various related data, status content, and prompts generated after the first user transfers resources through the first account. This type of information may be exclusive information that is allowed to be displayed to the second user after permission filtering according to the second user's second permissions. Optionally, the second information may include at least one of the following: the first user's first resource transfer information through the first account; resource transfer risk notification messages; resource transfer processing information.

[0181] The second permission can be understood as the permission that the second user has over the first account. The second permission is used to manage the first account. The second permission includes at least the management permissions granted by the first user to the second user regarding the first account. In some cases, in the provided solution, the second permission may optionally include at least one of the following: viewing the first resource transfer information of the first user through the first account; receiving a first notification message indicating that the resource transfer by the first user through the first account meets a second condition or poses a risk; and a second processing permission used to process the resource transfer by the first user through the first account.

[0182] Optionally, the second permission may include: viewing the first user's first resource transfer information through the first account.

[0183] Here, the first resource transfer information can be understood as resource transfer information that the second user has viewing permission for. The first resource transfer information can be part or all of the resource transfer information of the first account.

[0184] In one scenario, the first resource transfer information may include at least one of the following: a third identifier; a fourth identifier. The third identifier can be understood as identifier information characterizing the content of the object involved in the resource transfer process. The third identifier can be used to indicate the content of the object involved in the resource transfer process. The resources involved in the resource transfer process can be understood as the resources involved in the resource transfer process, and the resources may include resources obtained after transferring resources from the first account. The resource content may include at least one of the following: resource transfer time, resource transfer amount, resource transfer location, and resource transfer scenario. The fourth identifier can be understood as identifier information characterizing the resource type within the resources involved in the resource transfer process. The fourth identifier can be used to indicate the type of the object involved in the resource transfer process. For example, the type of object may include at least one of the following: daily necessities, food and beverage, transportation, medical and health care, education and learning, game top-up, live streaming rewards, entertainment consumption, and large-scale shopping.

[0185] In some cases, the provided solution allows a second user to view the resource transfer information of the first user through the first account based on their corresponding second permissions.

[0186] Optionally, the second permission may include: receiving the first notification message.

[0187] The first notification message can be understood as an abnormal transaction notification pushed to the second user. The first notification message can be used to instruct the first user that resource transfer through the first account meets the second condition or that a risk exists. Optionally, the first notification message may include at least one of the following: balance change information of the first account, resource transfer information of the first account, abnormal transaction alert information of the first account, credit limit usage information of the first account, payment request information initiated by the first user through the first account, and resource transfer risk alert information.

[0188] The second condition can be understood as a pre-set trigger condition used to determine whether to send the first notification message to the second user. That is, if the second condition is met, a first notification message related to the first account is sent to the second user. Optionally, the second condition may include at least one of the following: the first account performs a first resource transfer operation, the balance of the first account reaches a first value, the first account performs an abnormal transaction operation, or the difference between the usage limit and the usage limit of the first account is within a first interval; the first resource transfer operation may include at least one of the following: all resource transfer operations performed by the first account, resource transfer operations performed by the first account for resources of the first resource type, resource transfer operations performed by the first account within a second time period, or resource transfer operations performed by the first account where the amount of resource transfer exceeds a second threshold.

[0189] In one scenario, if the amount of resource transfer by the first user through the first account exceeds a second threshold, it is determined that the resource transfer meets the second condition. Further, a first notification message corresponding to the resource transfer is generated and sent to the second user.

[0190] In another scenario, in response to the risk of resource transfer by the first user through the first account, a first notification message corresponding to the resource transfer is generated and sent to the second user.

[0191] Optionally, the second permission may include: a second processing permission, which is used to process the resource transfer of the first user through the first account.

[0192] The second processing permission can be understood as the permission of a second user to process resource transfers initiated by a first user through a first account. In other words, the second processing permission can be used to allow a second user to block or confirm resource transfer operations initiated by a first user through a first account.

[0193] In one scenario, if a first user initiates a resource transfer request to a first account, and the amount of resources transferred in connection with the request exceeds a third threshold, a resource transfer notification can be sent to a second user. Furthermore, upon receiving the resource transfer notification, the second user can, based on their processing authority, block the resource transfer information, preventing the first user from completing the payment through the first account.

[0194] In some cases, the provided solution may also include at least one of the following: responding to a second user transferring resources to a first account, displaying resource transfer information, which includes at least the second user's information; receiving an eighth trigger from the first user to associate the first account with a third account, wherein the provider of the first account and the provider of the third account are different or the same; a second interface including the second user's information; and the second interface including association information between the second user and the first account. In some cases, the provided solution clearly displays the transferor's information during resource transfer and supports cross-platform or same-platform account association, while presenting users and association relationships on the interface. This improves the traceability of account association and fund transfers, while ensuring intuitive operation and flexible account management.

[0195] Optionally, the provided solution may also include: displaying resource transfer information in response to a second user transferring resources to a first account.

[0196] The resource transfer information can be understood as record information related to the resource transfer from the second user to the first account. This information is used to record resource transfer operations. It includes at least the second user's information, clearly showing the first user the entity responsible for performing the resource transfer. The information may also include at least one of the following: the amount of resources transferred; the time of the resource transfer; or information entered by the second user and sent to the first user.

[0197] In one scenario, in response to a second user transferring resources to the first account, resource transfer information is generated based on the received resource transfer, the resource transfer is completed, and the resource transfer information is displayed.

[0198] Optionally, the provided solution may also include: receiving an eighth trigger from the first user and associating the first account with the third account.

[0199] The eighth trigger can be understood as an instruction executed by the first user on the interface to initiate an account association operation. The eighth trigger can be used to associate the first account with a third account. The third account can be understood as another account that can be associated and bound to the first account. The third account can be an account managed by a single user or an account managed by multiple users. The provider of the first account and the provider of the third account may be different or the same. If the providers of the first account and the third account are different, it can be understood that the first account is provided by the first payment service provider, and the third account is provided by the second payment service provider; the first payment service provider and the second payment service provider are different. If the second payment service provider and the first payment service provider are different, it can be understood that the two payment service providers are independent payment entities, belonging to different payment service operation systems, and have no direct hierarchical relationship. If the providers of the first account and the third account are the same, it can be understood that the first account is provided by the first payment service provider, and the third account can also be provided by the first payment service provider.

[0200] In one scenario, the account identifier of at least one associatable third account is displayed. Upon receiving a selection operation for the account identifier, the third account corresponding to the selected account identifier is associated with the first account, establishing a binding, mapping, or authorization relationship between the first account and its associated third account.

[0201] Optionally, the provided solution may also include: the second interface including information about the second user; the second interface including association information between the second user and the first account.

[0202] The second user's information can be understood as identification information used to uniquely identify the second user. Optionally, the second user's information may include at least one of the following: user nickname, user avatar, user identity identifier, and relationship with the first user. It should be noted that the number of second users associated with the first account can be one or more. To ensure the first user is aware of the second user who invited them to open the first account, the information of the second user who initiated the fourth trigger can be displayed on the second interface. Association information can be understood as relevant descriptions or identifiers indicating a relationship between the second user and the first account. Optionally, association information may include at least one of the following: association status, association time, second user's type tag, and association remarks.

[0203] In some cases, the beneficial effects of the provided exemplary solution include: Displaying a second interface for opening a first account via a fourth trigger from the second user quickly brings up the invitation to open an account, simplifying the invitation process and improving the efficiency of account opening promotion. Furthermore, displaying the second user's information in the first area of ​​the second interface allows the first user to clearly identify the source of the invitation, enhancing the credibility of the account opening operation. Furthermore, displaying the account opening status only after the first user has completed authentication verifies the identity of the account holder, reduces the risk of illegal account opening, and ensures the security of the account opening process. The first user can configure the second user's second permissions, achieving hierarchical control of account permissions, allowing the account holder to flexibly restrict the operational scope of associated users. Configuring resource transfer viewing, risk notification receiving, and processing permissions for the second user enables them to monitor account fund changes in real time, promptly handle abnormal operations, and improve account fund security. This organic combination of technical features solves the limitations in the flexibility of account permission configuration and payment service adaptability in related technologies, as well as the relatively cumbersome permission configuration process. It ensures both the convenience and security of account opening, and achieves refined co-management of associated accounts through permission configuration. While enhancing the credibility of the account opening process, it also takes into account the flexibility of account use and the security of resource transfer.

[0204] Figure 14 This is a flowchart illustrating an information exchange method for one scenario, applicable to mobile payment account opening, such as a scenario where a second user opens a first account for a first user. This information exchange method can be executed by an information exchange device, which can be implemented in software and / or hardware, optionally through a computer program. Figure 14 As shown, the information interaction method may include: S1010, in response to the ninth trigger from the second user, displays the third information.

[0205] The ninth trigger can be understood as an interactive operation performed by the second user on the interface to confirm the invitation to open an account. The ninth trigger can be used by the second user to confirm the invitation to the first user to open the first account. For example, the first trigger includes at least one of the following: a trigger operation targeting the account opening control; a trigger operation targeting the account opening function entry point; a combined trigger operation that initiates an opening application after selecting a specified first user.

[0206] The third information can be understood as information related to the invitation process displayed to the second user. This third information can include any information related to the invitation process; optionally, it includes the invitation methods that the second user can use when sending the invitation to the first user. Inviting the first user to open a first account can be understood as the second user initiating an invitation to guide the first user to open a first account belonging to the first user.

[0207] An invitation method can be understood as a channel through which a second user can send an invitation to a first user. In some cases, the invitation method can be at least one of the following: sending invitation information to the first user's electronic device via a telecommunications operator's network or email; displaying a fifth identifier on a fourth interface, which is triggered by the second user's eleventh trigger, used to generate the fifth identifier, which the first user uses to obtain the invitation information by scanning the second identifier; or sending a conversation message to the first user through the conversation interface between the second and first users, the conversation message including the invitation information. In some cases, the provided solution offers multiple invitation channels to adapt to different scenarios when sending invitation information to the first user, improving the flexibility and coverage of invitation sending while ensuring the convenience and ease of use of the invitation process.

[0208] The invitation information can be understood as a notification initiated by the second user to invite the first user to activate or associate the first account. The invitation information may include at least one of the following: the second user's information, the information of the first account to be activated, an invitation link, a QR code, or a verification code.

[0209] In one scenario, the invitation information corresponding to the first account can be sent to the first user via a telecommunications operator's network.

[0210] In another scenario, an email containing the invitation information can be sent to the first user's email address.

[0211] Optionally, the invitation method may include: displaying a fifth identifier on the fourth interface, the fourth interface being displayed through the eleventh trigger of the second user, the eleventh trigger being used to generate the fifth identifier, and the fifth identifier being used by the first user to obtain invitation information by scanning the second identifier.

[0212] The fourth interface can be understood as the interface used to present invitation identification information. The fifth identifier can be understood as the identifier information used for invitation, which can be scanned and identified. Optionally, the fifth identifier may include at least one of the following: a barcode or a multi-dimensional code. The eleventh trigger can be understood as the operation performed by the second user to generate the invitation identifier. Optionally, the eleventh trigger may include at least one of the following: a trigger operation for the identifier generation control; a trigger operation for a preset area in the interface; a confirmation trigger after selecting the first user to be invited.

[0213] In one scenario, upon receiving a trigger operation for the identifier generation control, a fifth identifier is generated to invite the first user, and the fifth identifier is displayed on the fourth interface, so that the first user can obtain the invitation information by scanning the fifth identifier.

[0214] Optionally, the invitation method may include: sending a conversation message to the first user through the conversation interface between the second user and the first user, the conversation message including invitation information. Here, the conversation interface can be understood as the interactive interface through which the first user and the second user engage in real-time chat within the same application.

[0215] In one scenario, the conversation interface between the second user and the first user is displayed. In response to the second user's message editing operation on the conversation interface, the invitation information is sent to the first user in the form of a conversation message.

[0216] For example, Figure 15 This is a schematic diagram of an interface illustrating a third information display method in one scenario. For example... Figure 15 As shown, the display interface shows the account icon 1001 of the first account to be activated, the account activation invitation control 1002, and the account description display area 1003 for the first account. Furthermore, upon receiving a click trigger on the account activation control 1002, third information containing three invitation methods is displayed, as shown in the image. Figure 16 As shown. Figure 16 This is a schematic diagram of the interface for a fourth information display method in one scenario, such as... Figure 16 As shown, the fourth interface displays three invitation methods: Invitation Method A, Invitation Method B, and Invitation Method C.

[0217] S1020, in response to the tenth trigger of the second user, display the fourth information corresponding to the selected invitation method.

[0218] The tenth trigger can be understood as the operation performed by the second user on the interface to select and confirm the invitation method. Optionally, the tenth trigger may include at least one of the following: a click trigger for the invitation method input; a voice trigger for the invitation method input; or an action trigger for the invitation method input. The fourth information can be understood as content related to the invitation method. Optionally, the fourth information may include at least one of the following: invitation information used by the second user to invite the first user to open the first account; or status notification information obtained by the second user after sending the invitation information to the first user.

[0219] The invitation information can be understood as information used to invite the first user to open the first account. For example, the invitation information may include at least one of the following: an invitation link, an invitation code, an invitation message, an account opening portal, information of the second user, and information of the first account to be opened.

[0220] The status notification information can be understood as a feedback prompt indicating the sending result after the second user sends an invitation. For example, the status notification information may include at least one of the following: invitation sent, sent successfully, invitation pending receipt, or the recipient has viewed it.

[0221] In one scenario, at least one invitation method is displayed. Furthermore, upon receiving a click trigger for an invitation method, invitation information corresponding to the selected invitation method can be displayed. Further, in response to an invitation sending trigger, invitation information is sent to the first user according to the selected invitation method, and status notification information corresponding to the selected invitation method is displayed.

[0222] In some cases, the provided solution may also include at least one of the following: a first user has a first permission to a first account, and a second user has a second permission to the first account, wherein the first permission includes configuring at least a portion of the permission content in the second permission; or, the second permission includes at least one of the following: viewing resource transfer information of the first user through the first account; receiving a first notification message, wherein the first notification message indicates that the resource transfer of the first user through the first account meets a pre-first condition or there is a risk; and a second processing permission, wherein the second processing permission is used to process the resource transfer of the first user through the first account.

[0223] The first permission can be understood as the permission that the first user has over the first account. For example, the first permission may include at least one of the following: usage permission of the first account; first processing permission, used to process resource transfers through the first account; first configuration permission, used to configure at least some information of the first account; and second configuration permission, used to configure at least some of the permission content of the second permission. The first user can use the resources in the first account for processing based on the first permission, and can also configure the account information of the first account based on the first permission. The configured account information may include the relevant permissions of the second user over the first account. In one scenario, the first user's usage permission may include at least one of the following: resource transfer-out permission, used to transfer resources from the first account to a fourth account of the first user or a third user, where the fourth account is different from the first account; resource transfer-in permission, used to transfer resources into the first account; information viewing permission, used to view the resource transfer information of the first account; and information setting permission, used to adjust the information visibility range of the first account to the second user. The information visibility range includes at least one of the following: visible information content and the time range corresponding to the visible information content.

[0224] The second information can be understood as related information that is bound to the resource transfer of the first account and is viewable with the second user's permissions. The second information may be various related data, status content, and prompts generated after the first user transfers resources through the first account. This type of information may be exclusive information that is allowed to be displayed to the second user after permission filtering according to the second user's second permissions. Optionally, the second information may include at least one of the following: the first user's first resource transfer information through the first account; resource transfer risk notification messages; resource transfer processing information.

[0225] The second permission can be understood as the permission that the second user has over the first account. The second permission is used to manage the first account. The second permission includes at least the management permissions granted by the first user to the second user regarding the first account. In some cases, in the provided solution, the second permission may optionally include at least one of the following: viewing the first resource transfer information of the first user through the first account; receiving a first notification message indicating that the resource transfer by the first user through the first account meets a second condition or poses a risk; and a second processing permission used to process the resource transfer by the first user through the first account.

[0226] Optionally, the second permission may include: viewing the first user's first resource transfer information through the first account.

[0227] Here, the first resource transfer information can be understood as resource transfer information that the second user has viewing permission for. The first resource transfer information can be part or all of the resource transfer information of the first account.

[0228] In one scenario, the first resource transfer information may include at least one of the following: a third identifier; a fourth identifier. The third identifier can be understood as identifier information characterizing the content of the object involved in the resource transfer process. The third identifier can be used to indicate the content of the object involved in the resource transfer process. The resources involved in the resource transfer process can be understood as the resources involved in the resource transfer process, and the resources may include resources obtained after transferring resources from the first account. The resource content may include at least one of the following: resource transfer time, resource transfer amount, resource transfer location, and resource transfer scenario. The fourth identifier can be understood as identifier information characterizing the resource type within the resources involved in the resource transfer process. The fourth identifier can be used to indicate the type of the object involved in the resource transfer process. For example, the type of object may include at least one of the following: daily necessities, food and beverage, transportation, medical and health care, education and learning, game top-up, live streaming rewards, entertainment consumption, and large-scale shopping.

[0229] In some cases, the provided solution allows a second user to view the resource transfer information of the first user through the first account based on their corresponding second permissions.

[0230] Optionally, the second permission may include: receiving the first notification message.

[0231] The first notification message can be understood as an abnormal transaction notification pushed to the second user. The first notification message can be used to instruct the first user that resource transfer through the first account meets the second condition or that a risk exists. Optionally, the first notification message may include at least one of the following: balance change information of the first account, resource transfer information of the first account, abnormal transaction alert information of the first account, credit limit usage information of the first account, payment request information initiated by the first user through the first account, and resource transfer risk alert information.

[0232] The second condition can be understood as a pre-set trigger condition used to determine whether to send the first notification message to the second user. That is, if the second condition is met, a first notification message related to the first account is sent to the second user. Optionally, the second condition may include at least one of the following: the first account performs a first resource transfer operation, the balance of the first account reaches a first value, the first account performs an abnormal transaction operation, or the difference between the usage limit and the usage limit of the first account is within a first interval; the first resource transfer operation may include at least one of the following: all resource transfer operations performed by the first account, resource transfer operations performed by the first account for resources of the first resource type, resource transfer operations performed by the first account within a second time period, or resource transfer operations performed by the first account where the amount of resource transfer exceeds a second threshold.

[0233] In one scenario, if the amount of resource transfer by the first user through the first account exceeds a second threshold, it is determined that the resource transfer meets the second condition. Further, a first notification message corresponding to the resource transfer is generated and sent to the second user.

[0234] In another scenario, in response to the risk of resource transfer by the first user through the first account, a first notification message corresponding to the resource transfer is generated and sent to the second user.

[0235] Optionally, the second permission may include: a second processing permission, which is used to process the resource transfer of the first user through the first account.

[0236] The second processing permission can be understood as the permission of a second user to process resource transfers initiated by a first user through a first account. In other words, the second processing permission can be used to allow a second user to block or confirm resource transfer operations initiated by a first user through a first account.

[0237] In one scenario, if a first user initiates a resource transfer request to a first account, and the amount of resources transferred in connection with the request exceeds a third threshold, a resource transfer notification can be sent to a second user. Furthermore, upon receiving the resource transfer notification, the second user can, based on their processing authority, block the resource transfer information, preventing the first user from completing the payment through the first account.

[0238] In some cases, the provided solution also allows the second user to supplement the resources of the first account. For example, the provided solution further includes: in response to a thirteenth trigger, transferring resources from the second user's second account to the first account; and displaying the fifth interface of the first account.

[0239] The thirteenth trigger can be used to confirm the transfer of resources to the first account. Alternatively, the thirteenth trigger is the initiation signal for executing the operation of "transferring resources from the second account to the first account." In one scenario, this could involve displaying a second control to confirm the transfer of resources to the first account; in response to the second account being selected and a trigger operation being received on the second control, the resource transfer is performed from the second user's second account to the first account.

[0240] The second account belongs to the second user. That is, the second user has ownership and usage rights to the second account. The second account can be managed independently by the second user, or it can be jointly managed by the second user and a third user.

[0241] The fifth interface can be understood as the interface that displays information related to the first account. The fifth interface can include any account information related to the first account.

[0242] In one scenario, the fifth interface may include at least one of the following: information about the first user, and association information between the first user and the first account. The information about the first user can be understood as information used to identify the first user. For example, the information about the first user may include at least one of the following: user nickname, user avatar, user identification, and relationship with the second user.

[0243] Association information can be understood as relevant descriptions or identifiers indicating an association relationship between the first user and the first account. For example, association information may include at least one of the following: association status, association time, and association remarks.

[0244] In some scenarios, the beneficial effects of the provided exemplary solutions include: displaying multiple invitation methods in response to the ninth trigger provides second users with a clear choice of invitation channels, improving the convenience and flexibility of the account opening invitation process. Displaying the corresponding invitation content and sending status in response to the tenth trigger allows second users to intuitively obtain invitation information and sending results, facilitating timely monitoring of the invitation progress. Furthermore, the first user can configure certain permissions for the second user, enabling refined management of account permissions and ensuring the first user's control over their own account. Configuring viewing, notification, and processing permissions for the second user allows for effective management of resource transfers within the first account, enhancing the security of account fund usage. This organic combination of technical features solves account payment security issues in certain scenarios within related technologies, simplifies the account opening invitation process, and, combined with a permission configuration mechanism, ensures account security and controllable permissions while achieving convenient invitations. Overall, it improves the efficiency of account opening and promotion while also achieving standardization and security in the co-management of associated accounts.

[0245] Figure 17 This is a flowchart illustrating an information interaction method under another scenario. The solution provided in this scenario can be combined with implementation methods in other scenarios. For the same or related parts, they can be described in conjunction with the descriptions of other scenarios, and will not be repeated here. Figure 17 As shown, the method in this case may specifically include: S1110, in response to the ninth trigger of the second user, display the third information.

[0246] S1120, In response to the tenth trigger of the second user, display the fourth information corresponding to the selected invitation method.

[0247] S1130. Receive the twelfth trigger and send a first request to the first user. The twelfth trigger is used by the second user to view the first resource transfer information of the first account.

[0248] The twelfth trigger can be understood as an interactive operation command initiated by the second user. This interactive operation command can be used by the second user to view the first resource transfer information of the first account. The first request can be understood as a resource transfer viewing request sent to the first user. The first request can be used to ask whether the second user is allowed to view the first resource transfer information of the first account.

[0249] In one scenario, in response to a second user's request to view resource transfers for the first account, a first request is sent to the first user.

[0250] S1140. In response to the first user allowing the second user to view the first resource transfer information, the first resource transfer information is displayed.

[0251] In one scenario, the provided solution, upon receiving a trigger from the first user requesting permission from the first user to view the resource transfer information for the second user, displays the first resource transfer information of the first account to the second user.

[0252] In some cases, the beneficial effects of the provided exemplary solutions include: by initiating a viewing request first and then displaying the information after authorization, the security verification of viewing permissions for associated accounts is achieved, which protects the account privacy of the first user and allows the second user to legally view resource transfer information.

[0253] Figure 18 This is a schematic diagram of the structure of an information interaction device in one scenario, such as... Figure 18 As shown, the device includes a first module 1210 and a second module 1220. The first module 1210 is used to receive a first trigger from a first user for a first account, the first account belonging to the first user and associated with a second user, the first user having first permissions on the first account, and the second user having second permissions on the first account. The second module 1220 is used to display a first interface of the first account, the first interface being used by the first user to configure at least a portion of the second permissions.

[0254] In some situations, the beneficial effects of the provided device include: accurately responding to user operations and locating the target associated account and corresponding permissions, providing an accurate data foundation for subsequent permission configuration, and ensuring the directionality of permission management operations. It can intuitively display the permission configuration entry and configurable content, simplifying the first user's configuration of associated user permissions and improving the ease of use of permission management. This organic combination of technical features solves the limitations in the flexibility of account permission configuration and payment service adaptability in related technologies, as well as the relatively cumbersome permission configuration process. It enables the first user using the first account to flexibly configure the account permissions of associated users, achieving refined control over the account permissions of associated users. While ensuring the management permissions of the account's owner, it improves the flexibility and security of associated account permission management.

[0255] In one scenario, the first permission includes at least one of the following: configuring the second user's information viewing scope for the first account; configuring the second user's information receiving permission for the first account, wherein the configuration information related to the information receiving permission includes at least one of the following: a first condition that must be met to send the notification message to the second user, and the information content to be sent to the second user after the first condition is met; configuring the second user's second processing permission, wherein the second processing permission is used to process the resource transfer of the first user through the first account.

[0256] In one embodiment, the device further includes: an identifier display module and an identifier selection module; wherein the identifier display module is used to display a plurality of first identifiers on the first interface, the first identifiers being used to indicate the scope of information viewing for the first account; the identifier selection module is used to receive a selection operation for the first identifier and associate the selected first identifier with the second user.

[0257] In one embodiment, the device further includes a user display module for displaying a second user associated with the first account, wherein the number of second users is one or more.

[0258] In one scenario, the device further includes: a permission adjustment module, configured to receive a second trigger and adjust the second permission of the second user, wherein the second trigger is used for at least one of the following: modifying the second permission of the second user, configuring the second user associated with the first account, or changing the type tag corresponding to the second user; wherein the second permission of the second user corresponds to different type tags.

[0259] In one scenario, the device further includes: an information sending module, configured to receive a third trigger from the first user and send first information to the second user, wherein the third trigger is configured to process the resources of the first account, and the first information is configured to indicate to the first user that there is a risk in processing the resources of the first account.

[0260] In one embodiment, the device further includes: an interface display module and an account status display module. The interface display module is used to display a second interface for a first user to activate a first account; and further includes at least one of the following: the second interface is displayed via a fourth trigger, the fourth trigger being used by a second user to invite the first user to activate the first account; or, the second interface includes a first area displaying information about the second user; the account status display module is used to display the activation status of the first account in response to authentication of the first user.

[0261] The aforementioned information interaction device can execute the information interaction method provided in any embodiment of this document, and has the corresponding functional modules and beneficial effects for executing the information interaction method.

[0262] It is worth noting that the various units and modules included in the above-mentioned information interaction device are only divided according to functional logic, but are not limited to the above division, as long as the corresponding functions can be realized; in addition, the names of each functional unit are only for easy differentiation and are not used to limit the protection scope of the embodiments in this article.

[0263] Figure 19This is a schematic diagram of the structure of an information interaction device in one scenario, such as... Figure 19 As shown, the device includes a third module 1310 and a fourth module 1320. The third module 1310 is used to display a third interface associated with a second user. The fourth module 1320 is used to display information about a first account through the third interface, the first account belonging to the first user. Displaying the information about the first account includes displaying second information about the first account, the second information being associated with resource transfers performed by the first user through the first account, the second user having second permissions on the first account, and the second information being associated with the second permissions.

[0264] In some situations, the beneficial effects of the provided device include: by displaying a third interface associated with the second user, it provides the second user with a dedicated operation and interaction entry point, ensuring that the interface display matches the user's identity and improving the targeting of the interaction. Displaying the first account information through the third interface allows the second user to intuitively access the associated account content within a dedicated interface, avoiding information confusion and improving the convenience of information viewing. By displaying account information corresponding to the second permissions, account information can be accurately pushed according to the permission scope, ensuring the information security of the first account while meeting the reasonable viewing needs of the second user. The first user can configure some of the second user's permissions, realizing hierarchical management of account permissions and allowing the first user to flexibly control the operation scope of associated users. Configuring resource transfer viewing, risk notification receiving, and processing permissions for the second user allows the second user to manage account resource dynamics in real time, intervene in abnormal transfers in a timely manner, and improve the security of account funds. The organic combination of this series of technical features solves the problems of the limitations in the flexibility of account permission configuration and payment service adaptability in related technologies, as well as the relatively cumbersome permission configuration process, achieving refined display and permission control of associated account information. While ensuring the security of the primary account information, it enables secondary users to perform monitoring and processing operations according to their permissions, thereby improving the security and convenience of joint management of related accounts.

[0265] In one scenario, the fourth module 1320 is configured to perform at least one of the following operations: in response to at least a first condition being met, displaying first resource transfer information of the first user through the first account, wherein the first condition includes first configuration information indicating that the second user is allowed to view the first resource transfer information of the first account, the first configuration information being configured by the first user; or, receiving a first notification message indicating that the resource transfer of the first user through the first account meets a second condition or that there is a risk; or, displaying a first control for processing the resource transfer performed by the first user through the first account; or, displaying a first processing prompt for prompting the second user whether to input a processing instruction or confirm a processing instruction, the processing instruction being used to process the resource transfer performed by the first user through the first account.

[0266] In one scenario, the third module 1310 is configured to perform at least one of the following operations: displaying a third interface via a second account belonging to a second user; or displaying the third interface via a device associated with a second identifier, which is associated with the second user.

[0267] In one scenario, it further includes at least one of the following: the resource transfer information includes at least one of the following: a third identifier, the third identifier being used to indicate the content of the object involved in the resource transfer processing; a fourth identifier, the fourth identifier being used to indicate the type of the object involved in the resource transfer processing; the display of the resource transfer information of the first user through the first account includes: in response to a fifth trigger of the second user, sending a first request to the first user; in response to the first user allowing the second user to view the resource transfer information, displaying the resource transfer information, the fifth trigger being used by the second user to view the resource transfer information of the first account; in response to displaying the first control, receiving a sixth trigger for the first control, processing the resource transfer performed by the first user through the first account, wherein the sixth trigger is used for at least one of the following: canceling the resource transfer, interrupting the resource transfer, performing a resource return operation corresponding to the resource transfer processing; in response to displaying the first processing prompt, receiving the processing instruction input by the second user, processing the resource transfer performed by the first user through the first account, wherein the processing instruction includes at least one of the following: a voice instruction, a text instruction, an action instruction.

[0268] In one scenario, the device further includes a resource transfer module for transferring resources to the first account through a second account, the second account belonging to the second user.

[0269] The aforementioned information interaction device can execute the information interaction method provided in any embodiment of this document, and has the corresponding functional modules and beneficial effects for executing the information interaction method.

[0270] It is worth noting that the various units and modules included in the above-mentioned information interaction device are only divided according to functional logic, but are not limited to the above division, as long as the corresponding functions can be realized; in addition, the names of each functional unit are only for easy differentiation and are not used to limit the protection scope of the embodiments in this article.

[0271] Figure 20 This is a schematic diagram of the structure of an information interaction device in one scenario, such as... Figure 20 As shown, the device includes a fifth module 1410 and a sixth module 1420. The fifth module 1410 is used to display a second interface for a first user to activate a first account; it further includes at least one of the following: the second interface is displayed via a fourth trigger, the fourth trigger being used by a second user to invite the first user to activate the first account; or, the second interface includes a first area displaying information of the second user. The sixth module 1420 is used to display the activation status of the first account in response to authentication of the first user; it further includes at least one of the following: the first user has a first permission for the first account, and the second user has a second permission for the first account, the first permission including configuring at least a portion of the permission content in the second permission; or, the second user has a second permission for the first account, the second permission being associated with second information of the first account, the second information being associated with resource transfers performed by the first user through the first account.

[0272] In some cases, the beneficial effects of the provided device include: Displaying a second interface for opening a first account via a fourth trigger from the second user quickly brings up the invitation to open an account, simplifying the invitation process and improving the efficiency of account opening promotion. Displaying the second user's information in the first area of ​​the second interface allows the first user to clearly identify the source of the invitation, enhancing the credibility of the account opening operation. Furthermore, displaying the account opening status only after the first user has completed authentication verifies the identity of the account holder, reduces the risk of illegal account opening, and ensures the security of the account opening process. The first user can configure the second user's second permissions, achieving hierarchical control of account permissions, allowing the account holder to flexibly restrict the operational scope of associated users. By configuring the second user with permissions to view resource transfers, receive and process risk notifications, they can monitor account fund changes in real time, promptly handle abnormal operations, and improve the security of account funds. This organic combination of technical features solves the limitations in the flexibility of account permission configuration and the adaptability to payment services in related technologies, as well as the relatively cumbersome permission configuration process. It ensures both the convenience and security of account opening, and achieves refined co-management of associated accounts through permission configuration. While enhancing the credibility of the account opening process, it also takes into account the flexibility of account use and the security of resource transfer.

[0273] In one scenario, the second permission may further include at least one of the following: the second permission includes at least one of the following: viewing first resource transfer information of the first user through the first account; receiving a first notification message indicating that the resource transfer of the first user through the first account meets a second condition or is at risk; a second processing permission for processing the resource transfer of the first user through the first account; in response to the second user transferring resources to the first account, displaying resource transfer information, the resource transfer information including at least the information of the second user; receiving an eighth trigger from the first user to associate the first account with a third account, wherein the provider of the first account and the provider of the third account are different or the same; the second interface includes the information of the second user; the second interface includes the association information between the second user and the first account.

[0274] The aforementioned information interaction device can execute the information interaction method provided in any embodiment of this document, and has the corresponding functional modules and beneficial effects for executing the information interaction method.

[0275] It is worth noting that the various units and modules included in the above-mentioned information interaction device are only divided according to functional logic, but are not limited to the above division, as long as the corresponding functions can be realized; in addition, the names of each functional unit are only for easy differentiation and are not used to limit the protection scope of the embodiments in this article.

[0276] Figure 21 This is a schematic diagram of the structure of an information interaction device in one scenario, such as... Figure 21 As shown, the device includes a seventh module 1510 and an eighth module 1520. The seventh module 1510 is used to display third information in response to a ninth trigger by a second user. The ninth trigger is used for the second user to confirm an invitation to the first user to open a first account. The third information includes the invitation method that the second user can use when sending the invitation to the first user. The eighth module 1520 is used to display fourth information corresponding to the selected invitation method in response to a tenth trigger by the second user. This fourth information further includes at least one of the following: the first user has a first permission for the first account, and the second user has a second permission for the first account, where the first permission includes configuring at least a portion of the second permission content; or, the second user has a second permission for the first account, where the second permission includes at least one of the following: viewing first resource transfer information of the first user through the first account, where the first resource transfer information satisfies a first condition; receiving a first notification message indicating that the resource transfer of the first user through the first account satisfies a second condition or poses a risk; and a second processing permission for processing the resource transfer of the first user through the first account.

[0277] In some situations, the beneficial effects of the provided device include: displaying multiple invitation methods in response to the ninth trigger, providing a clear choice of invitation channels for the second user and improving the convenience and flexibility of the account opening invitation process. Displaying the corresponding invitation content and sending status in response to the tenth trigger allows the second user to intuitively obtain invitation information and sending results, facilitating timely monitoring of the invitation progress. The first user can configure certain permissions for the second user, enabling refined management of account permissions and ensuring the first user's control over their own account. By configuring viewing, notification, and processing permissions for the second user, they can effectively manage the transfer of resources in the first account, improving the security of account fund usage. This organic combination of technical features solves the limitations in the flexibility of account permission configuration and payment service adaptability in related technologies, as well as the relatively cumbersome permission configuration process. It simplifies the account opening invitation process and, combined with the permission configuration mechanism, ensures account security and controllable permissions while achieving convenient invitations. Overall, it improves the efficiency of account opening and promotion while achieving standardization and security of co-management of associated accounts.

[0278] In one scenario, the invitation method includes at least one of the following: sending the invitation information to the first user's electronic device via a telecommunications operator's network or email; displaying a second identifier on a fourth interface, the fourth interface being displayed via an eleventh trigger of the second user, the eleventh trigger being used to generate the second identifier, the second identifier being used by the first user to obtain the invitation information by scanning the second identifier; and sending a session message to the first user via a session interface between the second user and the first user, the session message including the invitation information.

[0279] In one scenario, the eighth module 1520 includes a request sending unit and an information display unit. The request sending unit is configured to receive a twelfth trigger and send a first request to the first user, the twelfth trigger being used by the second user to view first resource transfer information of the first account. The information display unit is configured to display the first resource transfer information in response to the first user allowing the second user to view the first resource transfer information, wherein the first resource transfer information includes at least one of the following: a third identifier, the third identifier indicating the content of the object involved in the resource transfer processing; and a fourth identifier, the fourth identifier indicating the type of the object involved in the resource transfer processing.

[0280] In one scenario, it also includes at least one of the following: in response to a thirteenth trigger, transferring resources to the first account through the second user's second account; displaying a fifth interface of the first account, the fifth interface including at least one of the following: information of the first user, and association information between the first user and the first account.

[0281] The aforementioned information interaction device can execute the information interaction method provided in any embodiment of this document, and has the corresponding functional modules and beneficial effects for executing the information interaction method.

[0282] It is worth noting that the various units and modules included in the above-mentioned information interaction device are only divided according to functional logic, but are not limited to the above division, as long as the corresponding functions can be realized; in addition, the names of each functional unit are only for easy differentiation and are not used to limit the protection scope of the embodiments in this article.

[0283] The following is for reference. Figure 22This document illustrates a schematic diagram of an electronic device (e.g., a terminal device or server) 2200 suitable for implementing the above-described methods. The terminal device referred to herein may include, but is not limited to, mobile terminals such as mobile phones, laptops, digital radio receivers, personal digital assistants (PDAs), tablet computers (PADs), portable multimedia players (PMPs), in-vehicle terminals (e.g., in-vehicle navigation terminals), and fixed terminals such as digital TVs and desktop computers. Figure 22 The electronic device shown is merely an example and should not be construed as limiting the functionality and scope of the embodiments described herein.

[0284] like Figure 22 As shown, electronic device 2200 may include a processing device (e.g., a central processing unit, a graphics processor, etc.) 2201, which can perform various appropriate actions and processes according to a program stored in read-only memory (ROM) 2202 or a program loaded from storage device 2208 into random access memory (RAM) 2203. The RAM 2203 also stores various programs and data required for the operation of electronic device 2200. The processing device 2201, ROM 2202, and RAM 2203 are interconnected via bus 2204. An input / output interface 2205 is also connected to bus 2204.

[0285] Typically, the following devices can be connected to I / O interface 2205: input devices 2206 including, for example, touchscreens, touchpads, keyboards, mice, cameras, microphones, accelerometers, gyroscopes, etc.; output devices 2207 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 2208 including, for example, magnetic tapes, hard disks, etc.; and communication devices 2209. Communication device 2209 allows electronic device 2200 to communicate wirelessly or wiredly with other devices to exchange data. Although Figure 22 An electronic device 2200 with various devices is shown; however, it should be understood that it is not required to implement or possess all of the devices shown. More or fewer devices may be implemented or possessed alternatively.

[0286] In particular, according to embodiments herein, the processes described in the above-referenced flowcharts can be implemented as computer software programs. For example, the solutions provided herein include a computer program product comprising a computer program carried on a non-transitory computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication device 2209, or installed from storage device 2208, or installed from ROM 2202. When the computer program is executed by processing device 2201, it performs the functions defined in the methods of the embodiments herein.

[0287] In some situations, the beneficial effects of the provided electronic devices include: First, they can accurately respond to user operations and locate the target associated account and corresponding permissions, providing an accurate data foundation for subsequent permission configuration and ensuring the directionality of permission management operations. Furthermore, they can intuitively display the permission configuration entry and configurable content, simplifying the configuration operations for associated users by the primary user and improving the usability of permission management. This organic combination of technical features solves the limitations in the flexibility of account permission configuration and the adaptability to payment services in related technologies, as well as the relatively cumbersome permission configuration process. It enables the primary user using the primary account to flexibly configure the account permissions of associated users, achieving refined control over the account permissions of associated users. While ensuring the management permissions of the account's owner, it improves the flexibility and security of associated account permission management.

[0288] The names of messages or information exchanged between multiple devices in this document are for illustrative purposes only and are not intended to limit the scope of these messages or information.

[0289] The electronic device provided in this embodiment and the information interaction method provided in the above-described solution belong to the same inventive concept. Technical details not described in detail herein can be found in the above-described embodiments, and this embodiment has the same beneficial effects as the above-described embodiments.

[0290] This article provides a computer storage medium on which a computer program is stored, which, when executed by a processor, implements the information interaction method provided in the above embodiments.

[0291] It should be noted that the computer-readable medium mentioned above can be a computer-readable signal medium, a computer-readable storage medium, or any combination thereof. A computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. In one instance, a computer-readable storage medium can include, but is not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, a random access memory, a read-only memory, an erasable programmable read-only memory (EPROM, also known as flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In this document, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in connection with an instruction execution system, apparatus, or device. In this document, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. The transmitted data signal can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. The computer-readable signal medium can also be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wires, optical fibers, RF (radio frequency), etc., or any suitable combination thereof.

[0292] Based on one or more scenarios described herein, Example 1 provides an information interaction method, comprising: receiving a first trigger from a first user for a first account, wherein the first account belongs to the first user and is associated with a second user, the first user has a first permission for the first account, and the second user has a second permission for the first account; displaying a first interface of the first account, wherein the first interface is used by the first user to configure at least a portion of the permission content of the second permission.

[0293] Based on one or more scenarios described herein, Example 2 provides the method of Example 1. Optionally, the first permission includes at least one of the following: configuring the second user's information viewing scope for the first account; configuring the second user's information receiving permission for the first account, wherein the configuration information related to the information receiving permission includes at least one of the following: a first condition that must be met to send the notification message to the second user, and the information content sent to the second user after the first condition is met; configuring the second user's second processing permission, wherein the second processing permission is used to process the resource transfer of the first user through the first account.

[0294] According to one or more scenarios in this document, Example 3 provides the method of Example 2, which further includes: optionally, displaying a plurality of first identifiers on the first interface, the first identifiers being used to indicate the scope of information viewing for the first account; receiving a selection operation for the first identifier, and associating the selected first identifier with the second user.

[0295] According to one or more scenarios in this document, Example 4 provides the method of Example 1, which further includes: optionally, displaying the second user associated with the first account, wherein the number of the second user is one or more.

[0296] According to one or more scenarios in this article, Example 5 provides the method of Example 4, which further includes: optionally, receiving a second trigger to adjust the second permission of the second user, wherein the second trigger is used for at least one of the following: modifying the second permission of the second user, configuring the second user associated with the first account, and changing the type label corresponding to the second user; wherein the second permission corresponding to the second user with different type labels is different.

[0297] According to one or more scenarios in this document, Example Six provides the method of Example Four, which optionally further includes: receiving a third trigger from the first user and sending first information to the second user, wherein the third trigger is used to process the resources of the first account, and the first information is used to indicate to the first user that there is a risk in processing the resources of the first account.

[0298] According to one or more scenarios described herein, Example 7 provides the method of Example 1, further comprising: displaying a second interface for a first user to open a first account; wherein, it further comprises at least one of the following: the second interface is displayed via a fourth trigger, the fourth trigger being used by a second user to invite the first user to open the first account; or, the second interface includes a first area displaying information of the second user; and in response to authentication of the first user, displaying the opening status of the first account.

[0299] According to one or more scenarios described herein, Example 8 provides an information interaction method, comprising: displaying a third interface associated with a second user; displaying information of a first account through the third interface, the first account belonging to the first user; wherein, displaying the information of the first account includes: displaying second information of the first account, the second information being associated with resource transfers performed by the first user through the first account, the second user having second permissions to the first account, and the second information being associated with the second permissions.

[0300] According to one or more scenarios described herein, Example Nine provides the method of Example Eight, further comprising: Optionally, displaying the second information of the first account includes at least one of the following: In response to at least a first condition being met, displaying first resource transfer information of the first user through the first account, wherein the first condition includes first configuration information indicating that the second user is allowed to view the first resource transfer information of the first account, the first configuration information being configured by the first user; or, receiving a first notification message indicating that the resource transfer of the first user through the first account meets the second condition or there is a risk; or, displaying a first control for processing the resource transfer performed by the first user through the first account; or, displaying a first processing prompt for prompting the second user whether to input a processing instruction or confirm a processing instruction, the processing instruction being used to process the resource transfer performed by the first user through the first account.

[0301] According to one or more of the scenarios described herein, Example 10 provides the method of Example 8, which further includes: optionally, the third interface is associated with a second user, including at least one of the following: displaying the third interface through a second account belonging to the second user; or displaying the third interface through a device associated with a second identifier, the second identifier being associated with the second user.

[0302] According to one or more scenarios in this document, Example 11 provides the method of Example 8, further comprising: optionally, at least one of the following: the resource transfer information includes at least one of the following: a third identifier, the third identifier being used to indicate the content of the object involved in the resource transfer processing; a fourth identifier, the fourth identifier being used to indicate the type of the object involved in the resource transfer processing; the display of the first resource transfer information of the first user through the first account includes: in response to a fifth trigger of the second user, sending a first request to the first user; in response to the first user allowing the second user to view the first resource transfer information, displaying the first resource transfer information, the fifth trigger being used by the second user to view the first resource transfer information of the first account; displaying the first control, receiving a sixth trigger for the first control, and processing the resource transfer performed by the first user through the first account, wherein the sixth trigger is used for at least one of the following: canceling the resource transfer, interrupting the resource transfer, and performing resource return processing corresponding to the resource transfer processing; in response to displaying the first processing prompt, receiving the processing instruction input by the second user, and processing the resource transfer performed by the first user through the first account, wherein the processing instruction includes at least one of the following: a voice instruction, a text instruction, and an action instruction.

[0303] According to one or more scenarios described herein, Example Twelve provides the method of Example Eight, which further includes: optionally, transferring resources to the first account through a second account belonging to the second user.

[0304] According to one or more scenarios described herein, Example Thirteen provides an information interaction method, comprising: displaying a second interface for a first user to open a first account; wherein, it further comprises at least one of the following: the second interface is displayed via a fourth trigger, the fourth trigger being used by a second user to invite the first user to open the first account; or, the second interface includes a first area displaying information of the second user; and, in response to authentication of the first user, displaying the opening status of the first account; wherein, it further comprises at least one of the following: the first user has a first permission to the first account, the second user has a second permission to the first account, the first permission including configuring at least a portion of the permission content in the second permission; or, the second user has a second permission to the first account, second information of the first account is associated with the second permission, and the second information is associated with resource transfers performed by the first user through the first account.

[0305] According to one or more scenarios described herein, Example Fourteen provides the method of Example Thirteen, further comprising: optionally, at least one of the following: the second permission includes at least one of the following: viewing first resource transfer information of the first user through the first account; receiving a first notification message indicating that the resource transfer of the first user through the first account meets a second condition or is at risk; a second processing permission for processing the resource transfer of the first user through the first account; in response to the second user transferring resources to the first account, displaying resource transfer information, the resource transfer information including at least the information of the second user; receiving an eighth trigger from the first user to associate the first account with a third account, wherein the provider of the first account is different from or the same as the provider of the third account; the second interface includes the information of the second user; the second interface includes the association information between the second user and the first account.

[0306] According to one or more scenarios described herein, Example 15 provides an information interaction method, comprising: responding to a ninth trigger by a second user, displaying third information, wherein the ninth trigger is used for the second user to confirm an invitation to a first user to open a first account, and the third information includes an invitation method that the second user can use when sending the invitation to the first user; responding to a tenth trigger by the second user, displaying fourth information corresponding to the selected invitation method, wherein the fourth information includes at least one of the following: invitation information used by the second user to invite the first user to open the first account; status notification information obtained by the second user after sending the invitation information to the first user; wherein it further includes at least one of the following: the first user has a first permission to the first account, and the second user has a second permission to the first account, wherein the first permission includes configuring at least a portion of the permission content in the second permission; or, the second user has a second permission to the first account, wherein the second permission includes at least one of the following: viewing first resource transfer information of the first user through the first account, wherein the first resource transfer information satisfies a first condition; receiving a first notification message, wherein the first notification message indicates that the resource transfer of the first user through the first account satisfies a second condition or is at risk; and a second processing permission, wherein the second processing permission is used to process the resource transfer of the first user through the first account.

[0307] According to one or more scenarios described herein, Example Sixteen provides the method of Example Fifteen, which further includes: Optionally, the invitation method includes at least one of the following: sending the invitation information to the first user's electronic device via SMS or email; displaying a fifth identifier on a fourth interface, the fourth interface being displayed via an eleventh trigger of the second user, the eleventh trigger being used to generate the fifth identifier, the fifth identifier being used by the first user to obtain the invitation information by scanning the second identifier; sending a session message to the first user through a session interface between the second user and the first user, the session message including the invitation information.

[0308] According to one or more scenarios described herein, Example 17 provides the method of Example 15, which further includes: optionally, viewing the first resource transfer information of the first user through the first account includes: receiving a twelfth trigger, sending a first request to the first user, the twelfth trigger being used by the second user to view the first resource transfer information of the first account; in response to the first user allowing the second user to view the first resource transfer information, displaying the first resource transfer information, wherein the first resource transfer information includes at least one of the following: a third identifier, the third identifier being used to indicate the content of the object involved in the resource transfer processing; a fourth identifier, the fourth identifier being used to indicate the type of the object involved in the resource transfer processing.

[0309] According to one or more scenarios in this document, Example 18 provides the method of Example 15, which further includes: optionally, at least one of the following: in response to a thirteenth trigger, transferring resources to the first account through the second user's second account; displaying a fifth interface of the first account, the fifth interface including at least one of the following: information of the first user, association information between the first user and the first account.

[0310] According to one or more scenarios described herein, Example 19 provides an information interaction device, comprising: a first module for receiving a first trigger from a first user on a first account, wherein the first account belongs to the first user and is associated with a second user, the first user has first permissions on the first account, and the second user has second permissions on the first account; and a second module for displaying a first interface of the first account, wherein the first interface is used by the first user to configure at least a portion of the permission content of the second permissions.

[0311] According to one or more scenarios described herein, Example 20 provides an information interaction device, comprising: a first module for receiving a first trigger from a first user on a first account, wherein the first account belongs to the first user and is associated with a second user, the first user has first permissions on the first account, and the second user has second permissions on the first account; and a second module for displaying a first interface of the first account, wherein the first interface is used by the first user to configure at least a portion of the permission content of the second permissions.

[0312] According to one or more scenarios described herein, Example 21 provides an information interaction device, comprising: a third module for displaying a third interface associated with a second user; and a fourth module for displaying information of a first account through the third interface, the first account belonging to the first user; wherein displaying the information of the first account includes: displaying second information of the first account, the second information being associated with resource transfers performed by the first user through the first account, the second user having second permissions to the first account, and the second information being associated with the second permissions.

[0313] According to one or more scenarios described herein, Example 22 provides an information interaction device, comprising: a fifth module for displaying a second interface for a first user to open a first account; wherein, it further comprises at least one of the following: the second interface is displayed via a fourth trigger, the fourth trigger being used by a second user to invite the first user to open the first account; or, the second interface includes a first area displaying information of the second user; a sixth module for displaying the opening status of the first account in response to authentication of the first user; wherein, it further comprises at least one of the following: the first user has a first permission to the first account, the second user has a second permission to the first account, the first permission including configuring at least a portion of the permission content in the second permission; or, the second user has a second permission to the first account, second information of the first account is associated with the second permission, the second information being associated with resource transfers performed by the first user through the first account.

[0314] According to one or more scenarios described herein, Example 23 provides an information interaction device, comprising: two users confirming an invitation to a first user to open a first account, wherein the third information includes the invitation method that the second user can use when sending the invitation to the first user; an eighth module, configured to respond to a tenth trigger of the second user and display fourth information corresponding to the selected invitation method, wherein the fourth information includes at least one of the following: invitation information for the second user to invite the first user to open the first account; status notification information obtained by the second user after sending the invitation information to the first user; wherein it further includes at least one of the following: the first user has a first permission to the first account, the second user has a second permission to the first account, the first permission includes configuring at least a portion of the permission content in the second permission; or, the second permission includes at least one of the following: viewing first resource transfer information of the first user through the first account, wherein the first resource transfer information satisfies a first condition; receiving a first notification message, wherein the first notification message indicates that the resource transfer of the first user through the first account satisfies the first condition or is at risk; and a second processing permission, wherein the second processing permission is used to process the resource transfer of the first user through the first account.

[0315] In some implementations, clients and servers can communicate using any currently known or future-developed network protocol, such as HTTP (Hypertext Transfer Protocol), and can interconnect with digital data communication (e.g., communication networks) of any form or medium. Examples of communication networks include Local Area Networks (LANs), Wide Area Networks (WANs), the Internet (e.g., the Internet), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future-developed networks.

[0316] The aforementioned computer-readable medium may be included in the aforementioned electronic device; or it may exist independently and not assembled into the electronic device.

[0317] The aforementioned computer-readable medium carries one or more programs that, when executed by the electronic device, cause the electronic device to: receive a first trigger from a first user for a first account, the first account belonging to the first user and associated with a second user, the first user having first permissions for the first account, and the second user having second permissions for the first account; and display a first interface for the first account, the first interface being used by the first user to configure at least a portion of the permissions for the second permissions.

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

[0319] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this document. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0320] The modules or units described herein may be implemented in software or hardware. The names of modules or units do not necessarily limit the module or unit itself; for example, a first module may also be described as "a module for receiving a first trigger from a first user for a first account".

[0321] The functions described above in this document can be performed at least in part by one or more hardware logic components. For example, exemplary types of hardware logic components that can be used, without limitation, include: Field-Programmable Gate Array (FPGA), Application-Specific Integrated Circuit (ASIC), Application-Specific Standard Product (ASSP), System on Chip (SOC), Complex Programmable Logic Device (CPLD), and so on.

[0322] In the context of this document, a machine-readable medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. For example, a machine-readable storage medium may include a wire-based electrical connection, a portable computer disk, a hard disk, random access memory, read-only memory, erasable programmable read-only memory, optical fiber, portable compact disk read-only memory, optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0323] In some cases, the beneficial effects of the provided storage medium include: accurately responding to user operations and locating the target associated account and corresponding permissions, providing an accurate data foundation for subsequent permission configuration, and ensuring the directionality of permission management operations. It can also intuitively display the permission configuration entry and configurable content, simplifying the configuration operations for associated users by the primary user and improving the ease of use of permission management. This organic combination of technical features solves the limitations in the flexibility of account permission configuration and payment service adaptability in related technologies, as well as the relatively cumbersome permission configuration process. It enables the primary user using the primary account to flexibly configure the account permissions of associated users, achieving refined control over the account permissions of associated users. While ensuring the management permissions of the account's owner, it improves the flexibility and security of associated account permission management.

[0324] The above description is merely a preferred embodiment and an explanation of the technical principles employed. Those skilled in the art should understand that the scope of disclosure herein is not limited to the solutions provided by specific combinations of the above-described technical features, but also includes other solutions formed by arbitrary combinations of the above-described technical features or their equivalents without departing from the above-disclosed concept. For example, solutions formed by substituting the above features with (but not limited to) technical features disclosed herein that have similar functions.

[0325] Furthermore, while the operations are described in a specific order, this should not be construed as requiring these operations to be performed in the specific order shown or in a sequential order. In certain circumstances, multitasking and parallel processing may be advantageous. Similarly, while several implementation details are included in the above discussion, these should not be interpreted as limiting the scope of this document. Certain features described in the context of individual implementations may also be implemented in combination in a single implementation. Conversely, various features described in the context of a single implementation may also be implemented individually or in any suitable sub-combination in multiple implementations.

[0326] Although the subject matter has been described using a programming language specific to structural features and / or methodological logic, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are merely illustrative forms of implementing the claims.

Claims

1. An information exchange method, comprising: Receive a first trigger from a first user for a first account, the first account belongs to the first user and is associated with a second user, the first user has first permissions for the first account, and the second user has second permissions for the first account; The first interface of the first account is displayed, and the first interface is used by the first user to configure at least part of the permission content of the second permission.

2. The information interaction method according to claim 1, wherein the first permission includes at least one of the following: Access permissions for the first account; First processing authority, the first processing authority is used to process resource transfers through the first account; The first configuration permission is used to configure at least some information of the first account; The second configuration permission is used to configure at least a portion of the permission content of the second permission.

3. The information interaction method according to claim 2, wherein the second configuration permission is used for at least one of the following: Configure the scope of information viewing for the second user on the first account; Configure the second user's information receiving permissions for the first account. The configuration information related to the information receiving permissions includes at least one of the following: a first condition that must be met to send a notification message to the second user, and the information content to be sent to the second user after the first condition is met. Configure a second processing permission for the second user, which is used to process resource transfers made by the first user through the first account.

4. The information interaction method according to claim 3, wherein configuring the second user's information viewing range for the first account includes: The first interface displays multiple first identifiers, which are used to indicate the scope of information viewing for the first account. Receive a selection operation for the first identifier, and associate the selected first identifier with the second user.

5. The information interaction method according to claim 1, further comprising at least one of the following: Display the second user associated with the first account, and the number of the second user is one or more; receiving a second trigger for at least one of modifying the second permission of the second user, configuring the second user associated with the first account, changing a type label corresponding to the second user, wherein The second user with different tag types has different second permissions.

6. The information interaction method according to claim 1, further comprising: Upon receiving a third trigger from the first user, the system sends a first message to the second user. The third trigger is used to process the resources of the first account, and the first message is used to indicate to the first user that there is a risk in processing the resources of the first account.

7. The information interaction method according to claim 1, further comprising: Displaying a second interface, the second interface being used by a first user to open a first account; wherein, it further includes at least one of the following: the second interface is displayed via a fourth trigger, the fourth trigger being used by a second user to invite the first user to open the first account; or, the second interface includes a first area, the first area displaying the information of the second user; In response to the authentication of the first user, the activation status of the first account is displayed.

8. An information exchange method, comprising: A third interface is displayed, which is associated with the second user; The information of the first account is displayed through the third interface, and the first account belongs to the first user. The display of information about the first account includes: displaying second information about the first account, the second information being associated with resource transfers made by the first user through the first account, the second user having second permissions to the first account, and the second information being associated with the second permissions.

9. The information interaction method according to claim 8, wherein displaying the second information of the first account includes at least one of the following: in response to at least a first condition being met, displaying first resource transfer information by the first user through the first account, wherein, The first condition includes a first configuration information indicating that the second user is allowed to view the first resource transfer information of the first account, wherein the first configuration information is configured by the first user; or, Upon receiving a first notification message, the first notification message indicates that the first user's resource transfer through the first account satisfies the second condition or that a risk exists; or, Display a first control, which is used to process resource transfers made by the first user through the first account; or... The first processing prompt is displayed to prompt the second user whether to enter a processing command or confirm the processing command. The processing command is used to process the resource transfer performed by the first user through the first account.

10. The information interaction method according to claim 8, wherein the third interface is associated with the second user, including at least one of the following: A third interface is displayed through a second account, which belongs to a second user; or... The third interface is displayed via a device associated with a second identifier, which is associated with a second user.

11. The information interaction method according to claim 8, further comprising at least one of the following: The resource transfer information includes at least one of the following: a third identifier, which indicates the content of the object involved in the resource transfer process; and a fourth identifier, which indicates the type of the object involved in the resource transfer process. The step of displaying the first resource transfer information of the first user through the first account includes: in response to a fifth trigger of the second user, sending a first request to the first user; in response to the first user allowing the second user to view the first resource transfer information, displaying the first resource transfer information; wherein the fifth trigger is used for the second user to view the first resource transfer information of the first account. Display a first control, receive a sixth trigger for the first control, and process the resource transfer performed by the first user through the first account, wherein the sixth trigger is used for at least one of the following: canceling the resource transfer, interrupting the resource transfer, or performing resource return processing corresponding to the resource transfer processing; In response to displaying a first processing prompt, the system receives a processing instruction input by the second user and processes the resource transfer performed by the first user through the first account. The processing instruction includes at least one of the following: a voice instruction, a text instruction, or an action instruction.

12. The information interaction method according to claim 8, further comprising: Resources are transferred from the second account to the first account, and the second account belongs to the second user.

13. An information exchange method, comprising: Displaying a second interface, the second interface being used by a first user to open a first account; wherein, it further includes at least one of the following: the second interface is displayed via a fourth trigger, the fourth trigger being used by a second user to invite the first user to open the first account; or, the second interface includes a first area, the first area displaying the information of the second user; In response to the authentication of the first user, the activation status of the first account is displayed; This also includes at least one of the following: The first user has first permissions on the first account, and the second user has second permissions on the first account, wherein the first permissions include configuring at least a portion of the permissions specified in the second permissions; or... The second user has second permissions to the first account, and the second permissions are associated with second information of the first account, which is associated with resource transfers made by the first user through the first account.

14. The information interaction method according to claim 13, further comprising at least one of the following: The second permission comprises at least one of the following: viewing first resource transfer information of the first user through the first account; receiving a first notification message, the first notification message indicating that resource transfer of the first user through the first account meets a second condition or there is a risk. The second processing authority is used to process the resource transfer of the first user through the first account; In response to the second user transferring resources to the first account, resource transfer information is displayed, the resource transfer information including at least the information of the second user; Upon receiving the eighth trigger from the first user, the first account is associated with the third account, wherein the provider of the first account is different from or the same as the provider of the third account; The second interface includes the information of the second user; The second interface includes the association information between the second user and the first account.

15. An information exchange method, comprising: In response to the ninth trigger of the second user, third information is displayed. The ninth trigger is used for the second user to confirm the invitation to the first user to open the first account. The third information includes the invitation method that the second user can use when sending the invitation to the first user. In response to the tenth trigger by the second user, fourth information corresponding to the selected invitation method is displayed, wherein the fourth information includes at least one of the following: invitation information for the second user to invite the first user to open the first account; status notification information obtained by the second user after sending the invitation information to the first user; This also includes at least one of the following: The first user has first permissions on the first account, and the second user has second permissions on the first account, wherein the first permissions include configuring at least a portion of the permissions specified in the second permissions; or... The second user has a second permission to the first account, the second permission including at least one of the following: viewing the first resource transfer information of the first user through the first account, the first resource transfer information satisfying a first condition; receiving a first notification message, the first notification message indicating that the resource transfer of the first user through the first account satisfies a second condition or there is a risk; and a second processing permission, the second processing permission being used to process the resource transfer of the first user through the first account.

16. The information interaction method according to claim 15, wherein the invitation method includes at least one of the following: The invitation information is sent to the first user's electronic device via a telecommunications operator's network or email. The fifth identifier is displayed on the fourth interface, which is displayed through the eleventh trigger of the second user. The eleventh trigger is used to generate the fifth identifier, which is used by the first user to obtain the invitation information by scanning the second identifier. A conversation message is sent to the first user through the conversation interface between the second user and the first user, and the conversation message includes the invitation information.

17. The information interaction method according to claim 15, wherein viewing the first resource transfer information of the first user through the first account includes: Upon receiving the twelfth trigger, a first request is sent to the first user, wherein the twelfth trigger is used by the second user to view the first resource transfer information of the first account; In response to the first user granting permission to the second user to view the first resource transfer information, the first resource transfer information is displayed, wherein the first resource transfer information includes at least one of the following: The third identifier is used to indicate the content of the object involved in the resource transfer process; The fourth identifier is used to indicate the type of object involved in the resource transfer process.

18. The information interaction method according to claim 15, further comprising at least one of the following: In response to the thirteenth trigger, resources are transferred from the second user's second account to the first account; The fifth interface of the first account is displayed, and the fifth interface includes at least one of the following: information of the first user, and association information between the first user and the first account.

19. An electronic device, the electronic device comprising: One or more processors; Storage device for storing one or more programs. When the one or more programs are executed by the one or more processors, the one or more processors implement the information interaction method as described in any one of claims 1-7, 8-12, 13-14 or 15-18.

20. A computer program product comprising a computer program that, when executed by a processor, implements the information interaction method as described in any one of claims 1-7, 8-12, 13-14, or 15-18.

Images