Resource transfer method and apparatus, computer device, and storage medium

Abstract

Embodiments of the present application disclose a resource transfer method and device, computer equipment and a storage medium, belonging to the technical field of computers. The method comprises: obtaining a first resource transfer request, the first resource transfer request carrying a third-party identifier, a first user identifier and a management identifier; determining a first authorization relationship in an authorization relationship database, the first authorization relationship comprising the first user identifier and the management identifier, and a second authorization relationship, the second authorization relationship comprising the third-party identifier and the management identifier; and performing resource transfer according to the first resource transfer request. The user does not need to input a password or perform other operations, and the user's resources are transferred in real time, thereby simplifying the user's operation process, implementing a resource transfer scheme without a password, improving the convenience and flexibility of resource transfer, and without the user performing an authorization operation for each third party or establishing an authorization relationship between the user and each third party. The application has a wide application range and good applicability, reduces the amount of data of the authorization relationship to be stored, and thereby reduces the pressure on the server.

Description

Technical Field

[0001] This application relates to the field of Internet technology, and in particular to a resource transfer method, apparatus, computer equipment, and storage medium. Background Technology

[0002] With the development of internet technology and the rise of e-commerce, payment applications have become increasingly diversified. Currently, payment applications also offer a password-free deduction function, which can automatically deduct funds when a transaction occurs between the user and the merchant.

[0003] Taking a ride-hailing app as an example, if a user authorizes the ride-hailing app to use the password-free deduction function in the payment app, then after the user takes a ride using the ride-hailing app, the ride-hailing app can initiate a password-free deduction to the payment app and deduct the payment directly without the user having to enter a password or perform other operations.

[0004] However, the above solution only applies to merchants that the user has authorized, and not to other merchants, resulting in a narrow scope of application and poor applicability. Summary of the Invention

[0005] This application provides a resource transfer method, apparatus, computer equipment, and storage medium, which can improve the convenience of resource transfer. The technical solution is as follows:

[0006] On the one hand, a resource transfer method is provided, the method comprising:

[0007] Obtain a first resource transfer request, the first resource transfer request carrying a third-party identifier, a first user identifier, and a management identifier, wherein the third-party identifier refers to a third party, the first user identifier refers to a first user, and the management identifier refers to the administrator;

[0008] The authorization relationship database includes a first authorization relationship between the first user identifier and the management identifier, and a second authorization relationship between the third-party identifier and the management identifier; the first authorization relationship indicates that the resources of the first user identifier are authorized to be transferred to a third party managed by the management party or a user identifier associated with a third party without password verification; the second authorization relationship indicates that the management party is authorized to manage the third party;

[0009] Perform resource transfer according to the first resource transfer request.

[0010] In one possible implementation, the step of transferring resources from the resource account of the first user identifier to the resource account of the second user identifier according to the first resource transfer request includes:

[0011] According to the first resource transfer request, resources are transferred from the resource account of the first user identifier to the first resource account bound to the second user identifier. The resource account of the first user identifier and the first resource account are resource accounts registered on the resource transfer server.

[0012] Resources are transferred from the first resource account to a target resource account identified by the second user, wherein the target resource account is not a resource account registered on the resource transfer server.

[0013] In another possible implementation, the method is applied to a resource transfer server, where the administrator is a management server; obtaining the first resource transfer request includes:

[0014] The system receives the first resource transfer request sent by the management server. The first resource transfer request is sent by the management server when it receives the second resource transfer request triggered by the third party. The second resource transfer request carries the third party identifier and the first user identifier.

[0015] On the other hand, a resource transfer method is provided, the method comprising:

[0016] Receive a second resource transfer request sent by a third-party device. The second resource transfer request carries a first user identifier and a third-party identifier, wherein the third-party identifier refers to the third party and the first user identifier refers to the first user.

[0017] A first resource transfer request is sent to the resource transfer server. The first resource transfer request carries the third-party identifier, the first user identifier, and the management identifier. The management identifier refers to the management party. The resource transfer server receives the first resource transfer request and determines, in the authorization relationship database, a first authorization relationship between the first user identifier and the management identifier, and a second authorization relationship between the third-party identifier and the management identifier. The first authorization relationship indicates that the transfer of the resources of the first user identifier to a third party managed by the management party or a user identifier associated with a third party is authorized without password verification. The second authorization relationship indicates that the management party is authorized to manage the third party. The resource transfer is then performed according to the first resource transfer request.

[0018] In one possible implementation, sending the first resource transfer request to the resource transfer server includes:

[0019] In response to the fact that both the first user identifier and the third-party identifier have a bound resource account on the resource transfer server, the first resource transfer request is sent to the resource transfer server.

[0020] In another possible implementation, sending the first resource transfer request to the resource transfer server includes:

[0021] In response to the failure to find a resource transfer task for the first user identifier, the first resource transfer request is sent to the resource transfer server.

[0022] On the other hand, a resource transfer method is provided, the method comprising:

[0023] Based on the first user identifier that has logged in, an authorization confirmation interface is displayed, which includes a management identifier that requests authorization;

[0024] In response to a confirmation operation detected in the authorization confirmation interface, an authorization request is sent to the resource management server. The authorization request carries the first user identifier and the management identifier. The resource management server is used to receive the authorization request and establish a first authorization relationship between the first user identifier and the management identifier. The first authorization relationship indicates that the resources of the first user identifier are authorized to be transferred to a third party managed by the manager or a user identifier associated with a third party without password verification.

[0025] In one possible implementation, the resource management server is used to receive the authorization request and return an authentication notification. After sending the authorization request to the resource management server, the method further includes:

[0026] In response to receiving the authentication notification, the authentication notification is displayed on the authorization confirmation interface;

[0027] The user obtains the input identity information through the authorization confirmation interface and sends the identity information to the resource management server. The resource management server establishes a first authorization relationship between the first user identifier and the management identifier when the identity information is verified.

[0028] On the other hand, a resource transfer method is provided, the method comprising:

[0029] A third-party device sends a second resource transfer request to the management server. The second resource transfer request carries a first user identifier and a third-party identifier. The third-party identifier refers to the third party, and the first user identifier refers to the first user.

[0030] The management server receives a second resource transfer request sent by the third-party device and sends a first resource transfer request to the resource transfer server. The first resource transfer request carries the third-party identifier, the first user identifier, and the management identifier, where the management identifier refers to the management party.

[0031] The resource transfer server receives the first resource transfer request, determines that the authorization relationship database includes a first authorization relationship between the first user identifier and the management identifier, and a second authorization relationship between the third-party identifier and the management identifier; the first authorization relationship indicates that the resource of the first user identifier has been authorized to be transferred to a third party managed by the management party or a user identifier associated with a third party without password verification; the second authorization relationship indicates that the management party has been authorized to manage the third party; and performs resource transfer according to the first resource transfer request.

[0032] On the other hand, a resource transfer device is provided, the device comprising:

[0033] The first request acquisition module is used to acquire a first resource transfer request. The first resource transfer request carries a third-party identifier, a first user identifier, and a management identifier. The third-party identifier refers to a third party, the first user identifier refers to a first user, and the management identifier refers to a manager.

[0034] The relationship determination module is used to determine, in the authorization relationship database, a first authorization relationship between the first user identifier and the management identifier, and a second authorization relationship between the third-party identifier and the management identifier; the first authorization relationship indicates that the transfer of the resources of the first user identifier to a third party managed by the management party or a user identifier associated with a third party is authorized without password verification; the second authorization relationship indicates that the management party is authorized to manage the third party;

[0035] The first resource transfer module is used to transfer resources according to the first resource transfer request.

[0036] In one possible implementation, the device further includes:

[0037] The request receiving module is used to receive an authorization request sent by a user terminal, wherein the authorization request carries the first user identifier and the management identifier, and the user terminal is a terminal that logs in with the first user identifier;

[0038] The relationship establishment module is used to establish a first authorization relationship between the first user identifier and the management identifier.

[0039] In another possible implementation, the relationship-establishing module includes:

[0040] The notification sending unit is used to send an authentication notification to the user terminal based on the first user identifier, and the user terminal is used to display the authentication notification and obtain the input identity information.

[0041] An identity information receiving unit is used to receive the identity information sent by the user terminal;

[0042] The relationship establishment unit is used to establish a first authorization relationship between the first user identifier and the management identifier when the identity information is verified.

[0043] In another possible implementation, the device further includes:

[0044] The task generation module is used to generate resource transfer tasks, wherein the resource transfer tasks include the first user identifier;

[0045] The second resource transfer module is used to execute the step of transferring resources according to the first resource transfer request when the lifespan of the resource transfer task reaches a preset duration.

[0046] In another possible implementation, the device further includes:

[0047] The task deletion module is used to delete the resource transfer task in response to the fact that the lifespan of the resource transfer task has not reached the preset time and a resource transfer cancellation request has been received. The resource transfer cancellation request carries the first user identifier.

[0048] In another possible implementation, the device further includes:

[0049] The second request acquisition module is used to acquire a resource transfer and recovery request, wherein the resource transfer and recovery request carries the first user identifier;

[0050] The resource recovery module is used to restore resources transferred from the resource account of the first user to the resource account of the first user.

[0051] In another possible implementation, the third party is a third-party server, and the first resource transfer request also carries a second user identifier, which is a user identifier registered with the third-party server;

[0052] The first resource transfer module includes:

[0053] The resource transfer unit is configured to transfer resources from the resource account of the first user identifier to the resource account of the second user identifier according to the first resource transfer request.

[0054] In another possible implementation, the resource transfer unit is configured to, according to the first resource transfer request, transfer resources from the resource account of the first user identifier to the first resource account bound to the second user identifier, wherein the resource account of the first user identifier and the first resource account are resource accounts registered on the resource transfer server; and transfer resources from the first resource account to the target resource account of the second user identifier, wherein the target resource account is not a resource account registered on the resource transfer server.

[0055] In another possible implementation, the apparatus is applied to a resource transfer server, and the manager is a management server; the first request acquisition module includes:

[0056] The request receiving unit is used to receive the first resource transfer request sent by the management server. The first resource transfer request is sent by the management server when it receives the second resource transfer request triggered by the third party. The second resource transfer request carries the third party identifier and the first user identifier.

[0057] On the other hand, a resource transfer device is provided, the device comprising:

[0058] The request receiving module is used to receive a second resource transfer request sent by a third-party device. The second resource transfer request carries a first user identifier and a third-party identifier, wherein the third-party identifier refers to the third party and the first user identifier refers to the first user.

[0059] The request sending module is used to send a first resource transfer request to the resource transfer server. The first resource transfer request carries the third-party identifier, the first user identifier, and the management identifier. The management identifier refers to the management party. The resource transfer server is used to receive the first resource transfer request, determine the authorization relationship database including a first authorization relationship between the first user identifier and the management identifier, and a second authorization relationship between the third-party identifier and the management identifier. The first authorization relationship indicates that the transfer of the resources of the first user identifier to a third party managed by the management party or a user identifier associated with a third party is authorized without password verification. The second authorization relationship indicates that the management party is authorized to manage the third party. The server then performs the resource transfer according to the first resource transfer request.

[0060] In one possible implementation, the request sending module includes:

[0061] The first request sending unit is configured to send the first resource transfer request to the resource transfer server in response to the fact that both the first user identifier and the third-party identifier have a resource account bound to the resource transfer server.

[0062] In another possible implementation, the request sending module includes:

[0063] The second request sending unit is used to send the first resource transfer request to the resource transfer server in response to the failure to find a resource transfer task with the first user identifier.

[0064] On the other hand, a resource transfer device is provided, the device comprising:

[0065] The interface display module is used to display an authorization confirmation interface based on the first user identifier of the login, wherein the authorization confirmation interface includes a management identifier requesting authorization;

[0066] The authorization request sending module is used to send an authorization request to the resource management server in response to a confirmation operation detected in the authorization confirmation interface. The authorization request carries the first user identifier and the management identifier. The resource management server is used to receive the authorization request and establish a first authorization relationship between the first user identifier and the management identifier. The first authorization relationship indicates that the transfer of resources of the first user identifier to a third party managed by the manager or a user identifier associated with a third party is authorized without password verification.

[0067] In one possible implementation, the resource management server is configured to receive the authorization request and return an authentication notification, and the apparatus further includes:

[0068] A notification receiving module is configured to display the authentication notification in the authorization confirmation interface in response to receiving the authentication notification.

[0069] The identity information sending module is used to obtain the input identity information through the authorization confirmation interface and send the identity information to the resource management server. The resource management server is used to establish a first authorization relationship between the first user identifier and the management identifier when the identity information is verified.

[0070] On the other hand, a computer device is provided, the computer device including a processor and a memory, the memory storing at least one piece of program code, the at least one piece of program code being loaded and executed by the processor to implement the resource transfer method as described above.

[0071] On the other hand, a computer-readable storage medium is provided that stores at least one piece of program code, which is loaded and executed by a processor to implement the resource transfer method as described above.

[0072] In another aspect, a computer program product or computer program is provided, the computer program product or computer program including computer program code stored in a computer-readable storage medium. A processor of a computer device reads the computer program code from the computer-readable storage medium, and the processor executes the computer program code, causing the computer device to implement the resource transfer method described above.

[0073] The beneficial effects of the technical solutions provided in this application include at least the following:

[0074] The methods, apparatus, computer devices, and storage media provided in this application, due to the authorization relationship between the user and the administrator, and between the user and a third party and the administrator, enable the transfer of a user's resources to the third party or other users associated with that third party without password verification. This allows for real-time resource transfer without requiring the user to enter a password, simplifying the user's workflow and achieving a passwordless resource transfer solution, thus improving the convenience and flexibility of resource transfer. Furthermore, the administrator, acting as an intermediary, can transfer resources between the user and any third party managed by the administrator, or other users associated with any third party, when the user and the administrator have an authorization relationship. This eliminates the need for the user to authorize each third party or establish an authorization relationship between the user and each third party. It can be applied to resource transfers between users and multiple third parties, has a wide range of applications and good applicability, reduces the amount of authorization relationship data that needs to be stored, and thus reduces the server load. Attached Figure Description

[0075] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0076] Figure 1 This is a schematic diagram of the structure of a resource transfer system provided in an embodiment of this application;

[0077] Figure 2 This is a schematic diagram of the structure of a resource transfer system provided in an embodiment of this application;

[0078] Figure 3 This is a flowchart of a resource transfer method provided in an embodiment of this application;

[0079] Figure 4 This is a flowchart of a resource transfer method provided in an embodiment of this application;

[0080] Figure 5This is a flowchart of a resource transfer method provided in an embodiment of this application;

[0081] Figure 6 This is a flowchart of an authorization method provided in an embodiment of this application;

[0082] Figure 7 This is a schematic diagram of an authorization confirmation interface provided in an embodiment of this application;

[0083] Figure 8 This is a flowchart of a resource transfer method provided in an embodiment of this application;

[0084] Figure 9 This is a flowchart of a resource transfer method provided in an embodiment of this application;

[0085] Figure 10 This is a schematic diagram of a resource transfer completion notification provided in an embodiment of this application;

[0086] Figure 11 This is a flowchart of a resource transfer method provided in an embodiment of this application;

[0087] Figure 12 This is a schematic diagram of a management identifier list provided in an embodiment of this application;

[0088] Figure 13 This is a flowchart of a resource transfer method provided in an embodiment of this application;

[0089] Figure 14 This is a schematic diagram illustrating the relationship between a management identifier, a user identifier, and a third-party identifier, as provided in an embodiment of this application.

[0090] Figure 15 This is a flowchart of a resource transfer method provided in an embodiment of this application;

[0091] Figure 16 This is a schematic diagram of the structure of a resource transfer device provided in an embodiment of this application;

[0092] Figure 17 This is a schematic diagram of the structure of a resource transfer device provided in an embodiment of this application;

[0093] Figure 18 This is a schematic diagram of the structure of a resource transfer device provided in an embodiment of this application;

[0094] Figure 19 This is a schematic diagram of the structure of a resource transfer device provided in an embodiment of this application;

[0095] Figure 20 This is a schematic diagram of the structure of a resource transfer device provided in an embodiment of this application;

[0096] Figure 21 This is a schematic diagram of the structure of a resource transfer device provided in an embodiment of this application;

[0097] Figure 22 This is a schematic diagram of the structure of a terminal provided in an embodiment of this application;

[0098] Figure 23 This is a schematic diagram of the structure of a server provided in an embodiment of this application. Detailed Implementation

[0099] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the implementation methods of this application will be further described in detail below with reference to the accompanying drawings.

[0100] The terms “first,” “second,” etc., used in this application may be used herein to describe various concepts, but unless otherwise stated, these concepts are not limited by these terms. These terms are used only to distinguish one concept from another. For example, without departing from the scope of this application, a first resource transfer request may be referred to as a second resource transfer request, and similarly, a second resource transfer request may be referred to as a first resource transfer request.

[0101] First, the terms used in this application will be introduced as follows:

[0102] 1. Third party, third party identifier, third party server:

[0103] A third party can be an organization that provides third-party services, such as a supermarket or a power company, or it can be a third-party application, such as a ride-hailing app or a shopping app.

[0104] The third-party identifier refers to a third party. Different third parties have different third-party identifiers. The third-party identifier can be the application name, supermarket name, organization code, etc.

[0105] A third-party server is a server configured by a third party to provide services to that third party. For example, if the third party is a third-party application, then the third-party server is the application server for that third-party application; if the third party is a supermarket, then the third-party server is the payment terminal configured for that supermarket.

[0106] 2. Management entity, management identifier, management server:

[0107] A manager is an object that provides management services and can manage objects associated with it, such as a management server or management platform. The objects associated with the manager can be third parties or user identifiers. For example, if the manager is a management server, it can associate with a merchant's terminal and manage that terminal. Alternatively, any terminal can register a user identifier on the management server, which can then manage that user identifier.

[0108] The management identifier refers to the management entity. Different management entities have different management identifiers, which can be the management entity code, the management entity name, or the management entity number, etc.

[0109] The management server is a server configured by the administrator to provide services to the administrator.

[0110] 3. First User Identifier and Second User Identifier:

[0111] Both the first user identifier and the second user identifier are used to identify users. The first user identifier refers to the first user, and the second user identifier refers to the second user. Both the first user identifier and the second user identifier can be user ID numbers, mobile phone numbers, nicknames, etc. The first user identifier can be a user identifier registered on a resource management server or a resource transfer server, while the second user identifier is a user identifier associated with a third party.

[0112] 4. Resource transfer server:

[0113] A resource transfer server is a server that provides resource transfer services. It is used to manage resource accounts identified by third parties or users. Based on the received resource transfer requests, it performs resource transfers between different resource accounts. It can transfer resources from a resource account identified by a first user to a resource account identified by a third party, or it can transfer resources from a resource account identified by a first user to a resource account identified by a user associated with a third party.

[0114] Figure 1 This is a schematic diagram of the structure of a resource transfer system provided in an embodiment of this application, as shown below. Figure 1 As shown, the system includes a third-party device 101, a management server 102, and a resource transfer server 103. A communication connection is established between the third-party device 101 and the management server 102, and a communication connection is established between the management server 102 and the resource transfer server 103. The two parties establishing the communication connection can interact. The third-party device 101 can be a terminal or a server.

[0115] The server can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN (Content Delivery Network), and big data and artificial intelligence platforms. The terminal can be a smartphone, tablet, laptop, desktop computer, smart speaker, smartwatch, etc., but is not limited to these. The terminal and server can be directly or indirectly connected via wired or wireless communication, and this application does not impose any restrictions.

[0116] Third-party device 101 triggers a second resource request by sending a second resource transfer request to management server 102. Management server 102 provides management services and can interact with both third-party device 101 and resource transfer server 103. After receiving the second resource request from third-party device 101, management server 102 sends a first resource transfer request to resource transfer server 103. Resource transfer server 103 performs resource transfer based on the received resource transfer request; that is, resource transfer server 103 can receive the first resource transfer request from management server 102 and execute the resource transfer.

[0117] Figure 2 This is a schematic diagram of the structure of a resource transfer system provided in an embodiment of this application, as shown below. Figure 2 As shown, the system includes a third-party device 201, a management server 202, a resource transfer server 203, a first user terminal 204, and a second user terminal 205. The third-party device 201 establishes a communication connection with the management server 202, the management server 202 establishes a communication connection with the resource transfer server 203, the resource transfer server 203 establishes a communication connection with the first user terminal 204, and the third-party device 201 establishes a communication connection with the second user terminal 205. The two parties with established communication connections can interact. The third-party device 201 can be a server.

[0118] The first user terminal 204 can interact with the resource transfer server 203. The user identifier logged in on the first user terminal 204 can be the user identifier registered on the resource transfer server 203, or the resource transfer server 203 can be a payment application server, and the first user terminal can have the application corresponding to the payment application server installed on it.

[0119] The second user terminal 205 is a terminal associated with the third-party device 201. For example, the user identifier logged into the second user terminal 205 is the user identifier registered on the third-party device 201; or, the third-party device 201 is an application server, and the second user terminal 205 has the application corresponding to that application server installed. The second user terminal 205 obtains the user identifier of the first user terminal 204 and can initiate a resource transfer request to the third-party device 201. Upon receiving the resource transfer request triggered by the second user terminal 205, the third-party device 201 sends the resource transfer request to the management server 202.

[0120] The management server 202 is used to provide management services and can interact with the third-party device 201 and the resource transfer server 203 respectively. After receiving the second resource request sent by the third-party device 201, it sends the first resource transfer request to the resource transfer server 203.

[0121] The resource transfer server 203 is used to perform resource transfer according to the received resource transfer request. That is, the resource transfer server 203 can receive the first resource transfer request sent by the management server 202 and execute the resource transfer. After the resource transfer is completed, it can send a resource transfer completion notification to the first user terminal 204 through communication with the first user terminal 204.

[0122] The method provided in this application can be used in a variety of scenarios.

[0123] For example, in a ride-hailing payment scenario:

[0124] Users can initiate an authorization request with the vehicle owner service management platform through the payment application server. The payment application server establishes an authorization relationship between the user identifier and the vehicle owner service management platform in its authorization relationship database. Furthermore, the payment application server's authorization relationship database also includes the authorization relationship between the ride-hailing application and the vehicle owner service management platform. When a user hails a ride through the ride-hailing application, upon arrival at the destination, the driver obtains the user's identifier through the ride-hailing application and initiates a fare collection request. Using the resource transfer method provided in this application embodiment, the payment application server transfers resources from the user's resource account to the driver's resource account without user intervention, achieving password-free payment.

[0125] For example, in the scenario of paying electricity bills:

[0126] In the payment application server, the power company establishes an authorization relationship with the utility payment platform, and the user also establishes an authorization relationship with the utility payment platform. When a user needs to pay their electricity bill, the power company's equipment belonging to the utility payment platform initiates a resource transfer request. Using the resource transfer method provided in this application embodiment, the payment application server transfers resources from the user's resource account to the power company's equipment's resource account. This eliminates the need for user intervention, enabling password-free payment and simplifying the user's process.

[0127] Figure 3 This is a flowchart of a resource transfer method provided in an embodiment of this application, applied in a resource management server, such as... Figure 3 As shown, the method includes:

[0128] 301. The resource management server receives the first resource transfer request.

[0129] The first resource transfer request carries a third-party identifier, a first user identifier, and a management identifier. The third-party identifier refers to a third party, which could be a supermarket, a ride-hailing app, etc. The first user identifier refers to the first user, and the management identifier refers to the management entity, which manages the third party and the user. This management entity could be a vehicle owner service recipient, managing multiple ride-hailing apps or parking lot servers; or a utility payment service recipient, managing multiple payment institutions in daily life, such as water, electricity, gas, and telephone bill payment providers.

[0130] The first resource transfer request is a request to transfer resources between the two parties involved in the interaction. The first user is identified as the transferor and the third party is identified as the transferee. Through this resource transfer request, the resource transfer between the transferee and the transferor can be completed subsequently.

[0131] The resource management server can be a payment application server, a social application server, etc. The first resource transfer request can be sent by the management server corresponding to the management identifier, or it can be obtained through other means.

[0132] 302. The resource management server determines the authorization relationship database, which includes the first authorization relationship between the first user identifier and the management identifier, and the second authorization relationship between the third party identifier and the management identifier.

[0133] The first authorization relationship indicates that the administrator is authorized to transfer the resources of the first user identifier to a third party managed by the administrator or a user identifier associated with a third party without verifying the password. The second authorization relationship indicates that the administrator is authorized to manage the third party.

[0134] For example, third-party identifiers with an authorization relationship with the management identifier include: Third-party identifier 1, Third-party identifier 2, and Third-party identifier 3. Third-party identifier 1 refers to Third-party 1, Third-party identifier 2 refers to Third-party 2, and Third-party identifier 3 refers to Third-party 3. If user identifier A has an authorization relationship with this management identifier, it means that without password verification, the resources of user identifier A can be transferred to Third-party 1, Third-party 2, or Third-party 3.

[0135] An authorization relationship database is used to store authorization relationships. This database can include multiple authorization relationships, each with two identifiers. In these multiple authorization relationships, at least one of the two identifiers must be different for each different authorization relationship. For example, in multiple authorization relationships involving user identifiers and management identifiers, different authorization relationships can include different management identifiers, different user identifiers, or both different management and user identifiers. Similarly, in multiple authorization relationships involving third-party identifiers and management identifiers, different authorization relationships can include different management identifiers, different third-party identifiers, or both different management and third-party identifiers.

[0136] Based on the third-party identifier, first user identifier, and management identifier obtained from the first resource transfer request, the resource management server queries multiple authorization relationships stored in the authorization relationship database, thereby determining the first authorization relationship and the second authorization relationship included in the authorization relationship database.

[0137] 303. The resource management server performs resource transfer based on the first resource transfer request.

[0138] If the resource management server determines that the authorization relationship database includes a first authorization relationship and a second authorization relationship, it means that the resources of the first user identifier can be transferred to the third party indicated by the third party identifier without verifying the password. Then the resource management server can perform resource transfer according to the first resource transfer request.

[0139] When the resource management server performs a resource transfer based on the first resource transfer request, if the first resource transfer request includes a third-party identifier, a first user identifier, and a management identifier, then the first user identifier is used as the transferor and the third-party identifier is used as the transferee, and the resources are transferred from the resource account of the first user identifier to the resource account of the third-party identifier; if the first resource transfer request also includes a second user identifier, which is a user identifier registered on the server corresponding to the third-party identifier, then the first user identifier is used as the transferor and the second user identifier is used as the transferee, and the resources are transferred from the resource account of the first user identifier to the resource account of the second user identifier.

[0140] In addition, the resource management server may include two servers: a management server and a resource transfer server. The management server can interact with third parties, and the resource transfer server can interact with the management server and can also transfer resources according to resource transfer requests.

[0141] The method provided in this application, due to the authorization relationship between the user and the administrator, and between the user and a third party and the administrator, enables the transfer of a user's resources to the third party or other users associated with that third party without password verification. This allows for real-time resource transfer without requiring the user to enter a password, simplifying the user's workflow and achieving a passwordless resource transfer solution, thus improving the convenience and flexibility of resource transfer. Furthermore, the administrator, acting as an intermediary, can facilitate resource transfers between the user and any third party managed by the administrator, or other users associated with any third party, when the user and the administrator have an authorization relationship. This eliminates the need for the user to authorize each third party or establish an authorization relationship between the user and each third party. It can be applied to resource transfers between users and multiple third parties, has a wide range of applications and good applicability, reduces the amount of authorization relationship data that needs to be stored, and thus reduces server load.

[0142] Figure 4 This is a flowchart of a resource transfer method provided in an embodiment of this application, applied in a management server, such as... Figure 4 As shown, the method includes:

[0143] 401. The management server receives a second resource transfer request sent by a third-party device.

[0144] The second resource transfer request carries the first user identifier and a third-party identifier. The third-party device can be a terminal or server belonging to a third party, such as a supermarket toll collection terminal or a highway toll collection terminal. For example, after a user purchases items at a supermarket and makes payment, the supermarket toll collection terminal scans the user's resource account QR code, obtains the user's identifier, and sends a second resource transfer request to the management server.

[0145] 402. The management server sends the first resource transfer request to the resource transfer server.

[0146] The first resource transfer request carries a third-party identifier, a first user identifier, and a management identifier, where the management identifier is the identifier of the management server. Based on the third-party identifier and the first user identifier carried in the second resource transfer request, and the management identifier of the management server, the management server generates the first resource transfer request and sends it to the resource transfer server through a communication connection.

[0147] After the management server sends the first resource transfer request to the resource transfer server, the resource transfer server performs resource transfer based on the third-party identifier, the first user identifier, and the management identifier carried in the first resource transfer request, and after determining that the authorization relationship database includes the first authorization relationship between the first user identifier and the management identifier, and the second authorization relationship between the third-party identifier and the management identifier.

[0148] The method provided in this application, due to the authorization relationship between the user and the administrator, and between the user and a third party and the administrator, enables the transfer of a user's resources to the third party or other users associated with that third party without password verification. This allows for real-time resource transfer without requiring the user to enter a password, simplifying the user's workflow and achieving a passwordless resource transfer solution, thus improving the convenience and flexibility of resource transfer. Furthermore, the administrator, acting as an intermediary, can facilitate resource transfers between the user and any third party managed by the administrator, or other users associated with any third party, when the user and the administrator have an authorization relationship. This eliminates the need for the user to authorize each third party or establish an authorization relationship between the user and each third party. It can be applied to resource transfers between users and multiple third parties, has a wide range of applications and good applicability, reduces the amount of authorization relationship data that needs to be stored, and thus reduces server load.

[0149] Figure 5 This is a flowchart of a resource transfer method provided in an embodiment of this application, applied in a user terminal, such as... Figure 5 As shown, the method includes:

[0150] 501. The user terminal displays an authorization confirmation interface based on the first user identifier that has logged in.

[0151] The user terminal is the terminal used by the first user identifier to log in; this user terminal can be a mobile phone, tablet computer, etc. The authorization confirmation interface is the display interface of this user terminal, which can display information for the user to view. This authorization confirmation interface includes a management identifier requesting authorization; this management identifier can be the identifier of any administrator. When the user terminal logged in with the first user identifier displays this authorization confirmation interface, it indicates that the first user identifier is about to establish an authorization relationship with the management identifier.

[0152] The user terminal displays an authorization confirmation interface, indicating that the first user needs to establish an authorization relationship with the management identifier so that subsequent resource transfers can be made directly to a third party managed by the administrator indicated by the management identifier or a user identifier associated with a third party without password verification.

[0153] 502. In response to the confirmation operation detected in the authorization confirmation interface, the user terminal sends an authorization request to the resource management server.

[0154] The confirmation operation indicates that the first user confirms permission to establish an authorization relationship with the management identifier. The authorization request carries the first user identifier and the management identifier so that the resource management server can establish an authorization relationship between the first user identifier and the management identifier. When the user terminal detects the confirmation operation in the authorization confirmation interface, the user terminal sends an authorization request to the resource management server through the communication connection between the user terminal and the resource management server. This allows the resource management server to establish an authorization relationship between the first user identifier and the management identifier based on the authorization request, thereby authorizing the resource management server to transfer resources belonging to the first user identifier to a third party managed by the administrator or a user identifier associated with a third party without verifying the password.

[0155] The method provided in this application embodiment establishes an authorization relationship in the resource management server through interaction between the user terminal and the resource management server. This allows the resource management server to transfer user-identified resources without password verification based on the authorization relationship, thus realizing the function of passwordless resource transfer. No user operation is required, simplifying the user's operation process.

[0156] Figure 6 This is a flowchart of an authorization method provided in an embodiment of this application. The interaction entities include a user terminal and a resource management server, such as... Figure 6 As shown, the method includes:

[0157] 601. The user terminal displays an authorization confirmation interface based on the first user identifier that has logged in.

[0158] The authorization confirmation interface includes a management identifier for which an authorization relationship needs to be established, indicating that the first user identifier needs to establish an authorization relationship with the management identifier.

[0159] In one possible implementation, step 601 may include the following three methods:

[0160] The first method involves the user terminal scanning the graphic code of the management identifier to obtain the management identifier and display an authorization confirmation interface. This graphic code can be a QR code, barcode, etc. For example, if the management entity has a corresponding QR code, the user terminal can scan this QR code to obtain the management entity's management identifier.

[0161] The second method involves installing the target application on the user terminal and logging into the target application based on the first user identifier: The user scans the graphical code of the management identifier using the target application to display the authorization confirmation interface. Here, the target application is the application corresponding to the resource management server. For example, if the target application is a payment application, scanning the QR code of the car owner service identifier using the payment application will display the authorization confirmation interface. Figure 7 As shown, Figure 7The left image shows the authorization confirmation interface displayed after scanning the QR code of the vehicle owner service logo. Upon detecting a user's activation of the "Activate and Authorize" button, the authorization confirmation interface displayed is as follows: Figure 7 As shown in the right figure.

[0162] The third method involves a target application installed on the user terminal, which is the application corresponding to the resource management server. When the user detects a trigger operation on the authorization option in the first application's display interface (based on a third user ID), it obtains a relationship identifier with a second authorization relationship to the first application, calls the target application's interface, and displays the target application's binding interface. This binding interface includes the third user ID and the first user ID logged into the target application. In response to a trigger operation on the confirmation option in the binding interface, it displays the target application's authorization confirmation interface, which includes the management identifier. The authorization option can be an authorization button, an authorization slider, etc. The trigger operation for the authorization button can be a click operation, and the trigger operation for the authorization slider can be a swipe operation. The first application can be another application on the user terminal besides the target application, such as a map application or a shopping application.

[0163] A single user terminal typically includes multiple different applications, each of which can log in with a different user ID. Since multiple applications are installed on the same user terminal, the user IDs logged in across these applications can be considered to refer to the same user. Therefore, when two applications interact, the user IDs logged in from the two applications can be bound together.

[0164] For example, the first application is a ride-hailing application, the target application is a payment application, and the resource management server is the server of the payment application. The user registers a first user identifier in the payment application and a third user identifier on the server of the ride-hailing application. The user logs into the ride-hailing application through the third user identifier and obtains a management identifier with a second authorization relationship with the ride-hailing application through the authorization option in the display interface of the ride-hailing application. The user then calls the interface of the payment application to start the payment application and displays a binding interface in the payment application. This binding interface includes the first user identifier, the third user identifier, and a confirmation button. The user can click the confirmation button. When the user terminal detects the click operation of the confirmation button based on the binding interface, it means that the user allows the binding of the first user identifier and the third user identifier. Then, the authorization confirmation interface of the target application is displayed, which includes the management identifier.

[0165] 602. In response to the confirmation operation detected in the authorization confirmation interface, the user terminal sends an authorization request to the resource management server.

[0166] The authorization request carries a first user identifier and a management identifier. When the user terminal detects a confirmation operation on the authorization confirmation interface, indicating that the first user needs to authorize the management identifier, the user terminal sends an authorization request to the resource management server so that the resource management server can establish a first authorization relationship between the first user identifier and the management identifier.

[0167] In one possible implementation, the authorization confirmation interface includes a confirmation option. Step 602 may include: the user terminal detecting a confirmation operation on the confirmation option in the authorization interface and sending an authorization request to the resource management server. The confirmation option may be a confirmation button, a slider, etc. A confirmation operation on a confirmation button is performed by the user clicking the button, and a confirmation operation on a slider is performed by the user sliding the slider. Figure 7 As shown, when the user clicks the "Activate" button in the right image, it indicates that a confirmation operation has been detected.

[0168] 603. The resource management server receives the authorization request sent by the user terminal and sends an authentication notification to the user terminal based on the first user identifier.

[0169] Since the resource management server receives an authorization request from the user terminal, which authorizes the resource management server to transfer resources belonging to the first user without verifying the password, in order to ensure the security of the resources belonging to the first user, the first user needs to be authenticated during the authorization process to prevent impersonation by other user identities, which could lead to resource loss.

[0170] In one possible implementation, the user terminal sends an authorization request to the resource management server through the target application. In this case, step 603 may include: the resource management server receives the authorization request and, based on the first user identifier, sends an authentication notification to the target application that logged in with the first user identifier.

[0171] 604. Upon receiving the authentication notification, the user terminal displays the authentication notification on the authorization confirmation interface.

[0172] After the user terminal receives the authentication notification, it is displayed on the authorization confirmation screen to prompt the user to authenticate. Additionally, the authorization confirmation screen includes authentication instructions to explain the purpose and procedure of authentication.

[0173] 605. The user terminal obtains the entered identity information through the authorization confirmation interface and sends the identity information to the resource management server.

[0174] The identity information refers to the identity information of the first user identifier, which may be the password information of the first user identifier, the facial information of the first user identifier, or the fingerprint information of the first user identifier, etc.

[0175] On the authorization confirmation interface, the user enters their identity information. After the user terminal obtains the identity information through the authorization confirmation interface, it sends the identity information to the resource management server so that the resource management server can subsequently verify the identity of the first user.

[0176] In one possible implementation, the authorization confirmation interface includes a confirmation option. In this case, step 605 may include: the user terminal obtaining the input identity information through the authorization confirmation interface, and sending the identity information to the resource management server in response to detecting a trigger operation on the confirmation option. The confirmation option may be a confirmation button or a confirmation slider, etc.

[0177] In one possible implementation, obtaining the identity information of the first user identifier can include the following three methods:

[0178] The first method: The authorization confirmation interface includes a password input area, and the user terminal obtains the password information entered in this input area.

[0179] The second method: The authorization confirmation interface includes a fingerprint input area, and the user terminal obtains the fingerprint information entered in the input area.

[0180] The third method: The authorization confirmation interface includes a prompt for fingerprint information input, which prompts the user to input fingerprint information. The user terminal obtains the fingerprint information input by the first user identifier through the fingerprint input area of ​​the user terminal.

[0181] The fourth method: The authorization confirmation interface includes a prompt to input facial information. By taking a picture of the first user's face, the facial information identifying the first user can be obtained.

[0182] 606. The resource management server receives the identity information sent by the user terminal. When the identity information is verified, the first authorization relationship between the first user identifier and the management identifier is established.

[0183] After receiving the identity information sent by the user terminal, the resource management server verifies the identity information. If the identity information is verified, the first authorization relationship between the first user identifier and the management identifier is established and stored in the authorization relationship database on the resource management server.

[0184] In one possible implementation, the resource management server includes preset identity information of the first user identifier. This preset identity information can be set when the first user identifier registers a resource account in the resource management server. In this case, step 606 may include: the resource management server receives identity information sent by the user terminal, compares the identity information with the preset identity information of the first user identifier, and obtains a comparison result. If the comparison result indicates that the identity information has been verified, a first authorization relationship is established between the first user identifier and the management identifier.

[0185] It should be noted that the embodiment of this application describes the establishment of the first authorization relationship after the resource management server receives the authorization request and the identity verification of the first user identifier is passed. However, in another embodiment, steps 602-606 do not need to be executed, and other methods can be used to establish the first authorization relationship between the first user identifier and the management identifier.

[0186] It should be noted that the embodiments of this application are described in terms of the interaction between the user terminal and the resource management server. In another embodiment, the resource management server may include a resource transfer server and a management server. In this case, the steps performed by the resource management server can be replaced by the resource transfer server. The user terminal interacts with the resource transfer server, completes the authorization in the resource transfer server, and stores the first authorization relationship in the authorization relationship database on the resource transfer server.

[0187] The method provided in this application establishes a first authorization relationship between a first user identifier and a management identifier through interaction between a user terminal and a resource management server. This allows the resource management server to transfer resources associated with the user identifier without password verification, achieving passwordless resource transfer without user intervention and simplifying the user's workflow. Furthermore, during the authorization process, the identity information of the first user is verified to prevent impersonation by other users and avoid resource loss, thus improving security.

[0188] Figure 8 This is a flowchart of a resource transfer method provided in an embodiment of this application. The interactive entities include a management server and a resource transfer server, such as... Figure 8 As shown, the method includes:

[0189] 801. The management server receives a second resource transfer request sent by a third-party device and sends a first resource transfer request to the resource transfer server.

[0190] The second resource transfer request carries a third-party identifier and a first user identifier.

[0191] A third-party device establishes a communication connection with the management server. When the third-party device needs to transfer resources, it sends a second resource transfer request to the management server. The communication connection between the third-party device and the management server can be set up by the administrator of the third-party device. For example, if the administrator of the third-party device submits a communication connection request to the administrator of the management server, and the administrator of the management server agrees, the third-party device will establish a communication connection with the management server.

[0192] After receiving the second resource transfer request, the management server sends the first resource transfer request to the resource transfer server so that the resource transfer server can perform resource transfer according to the first resource transfer request.

[0193] Additionally, after receiving the second resource transfer request, the resource management server verifies the first user identifier or the third-party identifier. Upon successful verification, it sends the first resource transfer request to the resource transfer server. In one possible implementation, step 801 may include: in response to the fact that both the first user identifier and the third-party identifier have bound resource accounts on the resource transfer server, sending the first resource transfer request to the resource transfer server.

[0194] The management server authenticates the first user identifier and the third-party identifier. Only when both the first user identifier and the third-party identifier have bound resource accounts on the resource transfer server can the resource transfer server perform resource transfer between the first user identifier and the third-party identifier through the resource accounts on the resource transfer server. Therefore, the management server sends a first resource transfer request to the resource transfer server.

[0195] Optionally, the management server stores an identifier database, which includes multiple user identifiers and multiple third-party identifiers. All identifiers in the identifier database have bound resource accounts on the resource transfer server. In response to the identifier database including a first user identifier and a third-party identifier, the verification of the first user identifier and the third-party identifier is successful.

[0196] Optionally, the management server has preset conditions. If both the first user identifier and the third-party identifier meet these preset conditions, the verification of the first user identifier and the third-party identifier is considered successful. These preset conditions can be the format of the first user identifier and the third-party identifier, or both the first user identifier and the third-party identifier may include preset characters. For example, both the first user identifier and the third-party identifier may be 18-digit serial numbers, or both the first user identifier and the third-party identifier may include the preset character 'm'.

[0197] In one possible implementation, step 801 may include: in response to the failure to find a resource transfer task for the first user identifier, sending a first resource transfer request to a resource transfer server. The resource transfer task is the task for which the resource account of the first user identifier needs to transfer resources.

[0198] When transferring resources to the resource account of the first user identifier, a resource transfer-out task is generated for the first user identifier. The completion of the resource transfer-out task indicates that the resources have been transferred out of the first user identifier's resource account. If the resource transfer-out task is incomplete, it indicates that no resources have been transferred out of the first user identifier's resource account. To ensure the accuracy of resource transfers for user identifiers' resource accounts, when a resource transfer is required for the first user identifier's resource account, it is checked whether there are any incomplete resource transfer-out tasks for the first user identifier. If no resource transfer-out tasks are found for the first user identifier, it means that all previous resource transfer tasks for the first user identifier have been completed, or that the current resource transfer for the first user identifier is its first resource transfer. Therefore, a first resource transfer request can be sent to the resource transfer server so that subsequent resource transfer servers can perform resource transfers based on the first resource transfer request.

[0199] In addition, both the second resource transfer request and the first resource transfer request include the quantity of resources to be transferred, so that the resource transfer can be carried out using this quantity of resources later.

[0200] 802. The resource transfer server receives the first resource transfer request sent by the management server.

[0201] It should be noted that the embodiments of this application are described based on the resource transfer server receiving the first resource transfer request sent by the management server. In another embodiment, steps 801-802 do not need to be executed, and other methods can be used to obtain the first resource transfer request.

[0202] 803. The resource transfer server determines the authorization relationship database, which includes the first authorization relationship between the first user identifier and the management identifier, and the second authorization relationship between the third party identifier and the management identifier.

[0203] The authorization relationship database contains multiple authorization relationships, each stored in a format corresponding to an identifier, as shown in Tables 1 and 2. The same management identifier can establish authorization relationships with multiple different user identifiers, and also with multiple third-party identifiers. Furthermore, any user identifier can establish authorization relationships with multiple management identifiers, and any third-party identifier can also establish authorization relationships with multiple management identifiers.

[0204] Table 1

[0205]

[0206] Table 2

[0207]

[0208] In one possible implementation, the resource transfer server queries the authorization relationship database based on the first user identifier, the third party identifier, and the management identifier, and finds the first authorization relationship and the second authorization relationship, thus determining that the authorization relationship database includes the first authorization relationship and the second authorization relationship.

[0209] 804. The resource transfer server performs resource transfer based on the first resource transfer request.

[0210] If the resource transfer server determines that the authorization relationship database includes the first authorization relationship and the second authorization relationship, it means that both parties in the first resource transfer request have authorized the management server to manage them. Therefore, the resource transfer server can directly transfer resources without requiring the first user to perform any operation, thus realizing the password-free payment function.

[0211] In one possible implementation, step 804 may include: the resource transfer server transferring resources from a resource account identified by a first user to a resource account identified by a third party.

[0212] For example, if the third party is a supermarket, the third party identifier is the supermarket's identifier, and the resource account of the third party identifier is the resource account registered by the supermarket in the resource transfer server, then the resource transfer server will transfer resources from the resource account of the first user identifier to the resource account of the supermarket according to the first resource transfer request.

[0213] In one possible implementation, the third party is a third-party server. The second resource transfer request sent by the third server to the management server carries a second user identifier. The first resource transfer request also carries a second user identifier. Step 804 may include: transferring resources from the resource account of the first user identifier to the resource account of the second user identifier according to the first resource transfer request.

[0214] The third-party server can be a ride-hailing application server, a highway toll collection server, a supermarket server, etc. The second user identifier is the user identifier registered on the third-party server. When the third-party server is a ride-hailing application server, the second user identifier refers to the driver of the ride-hailing application; when the third-party server is a highway toll collection server, the second user identifier refers to the toll collection equipment at any highway toll station; when the third-party server is a supermarket server, the second user identifier refers to any supermarket payment device.

[0215] Since a third party can have multiple user identifiers, when a resource transfer request carries a first user identifier and a second user identifier, it indicates that the second user identifier is the recipient and the resources of the first user identifier need to be transferred to the resource account of the second user identifier, rather than the resources of the first user identifier being transferred to the resource account of the third party identifier. Therefore, when performing resource transfer, the resources of the first user identifier are transferred to the resource account of the second user identifier, thereby realizing the function of real-time resource transfer.

[0216] For example, if the third-party server is a ride-hailing application server, and the second user identifier is a user identifier registered on the ride-hailing application server, which could be a car owner, when the car owner delivers the passenger to the destination, a second resource transfer request is initiated through the car owner's third-party device. Then, the resource transfer server transfers the resources of the first user identifier to the resource account of the second user identifier.

[0217] Optionally, based on the first resource transfer request, resources are transferred from the resource account of the first user identifier to the first resource account bound to the second user identifier, and then resources are transferred from the first resource account to the target resource account of the second user identifier. Here, the resource account of the first user identifier and the first resource account are resource accounts registered with the resource transfer server; the target resource account is not a resource account registered with the resource transfer server. Figure 9 As shown, during resource transfer, the funds are transferred from the bank account of the first user identifier to the resource account of the second user identifier on the resource transfer server, and then from the resource account to the bank account of the second user identifier.

[0218] By using the first resource account bound to the second user identifier as a transfer account, resources are transferred from the first user identifier's resource account to the first resource account, and simultaneously transferred from the first resource account to the target account. This synchronous transfer ensures that resources are accurately transferred to the target resource account. Even if the amount of resources in the first user identifier's resource account is less than the amount of resources to be transferred, resources can still be transferred to the target resource account, achieving real-time resource transfer functionality.

[0219] In one possible implementation, after step 804, the method further includes: the resource transfer server sending a resource transfer completion notification to the user terminal that logged in with the first user identifier, and the user terminal displaying the resource transfer completion notification to indicate that the resource transfer of the first user identifier is complete.

[0220] Optionally, the resource transfer completion notification includes the number of resources transferred to indicate to the first user that an equal number of resources have been transferred from the resource account. Figure 10As shown, the resource transfer completion notification may also include deduction details, payment method, and remarks. The deduction details indicate the event that caused the resource transfer, such as taking a bus or shopping at a supermarket; the payment method indicates the account for transferring the resources, such as the bank account of the first user identifier or the resource account on the resource transfer server; the remarks are used to prompt the first user identifier to confirm the resource transfer completion notification.

[0221] In one possible implementation, after step 804, the method further includes: obtaining a resource transfer recovery request to restore resources transferred from the resource account of the first user identifier to the resource account of the first user identifier. The resource transfer recovery request carries the first user identifier, indicating that resources transferred from the resource account of the first user identifier need to be restored; that is, after resources were transferred from the resource account of the first user identifier to another resource account, resources are then transferred from that other resource account to the resource account of the first user identifier.

[0222] Optionally, the third device sends a resource transfer recovery request to the management server, and the management server sends the received resource transfer recovery request to the resource transfer server.

[0223] For example, after a transaction is completed between a supermarket and a user, if the user returns the goods, the supermarket needs to refund the user. Therefore, the supermarket server sends a resource transfer and recovery request to the management server. The management server then sends the received resource transfer and recovery request to the resource transfer server. The resource transfer server then restores the transferred resources to the resource account of the user based on the user's first user identifier.

[0224] In addition, the resource transfer recovery request also carries the identifier of the transferring party. For example, if the first resource transfer request carries a first user identifier and a third-party identifier, that is, the first user identifier is the transferring party identifier and the third-party identifier is the transferring party identifier, then the resource transfer recovery request carries both the first user identifier and the third-party identifier. In this case, the first user identifier is the transferring party identifier and the third-party identifier is the transferring party identifier. If the first resource transfer request carries a first user identifier and a second user identifier, that is, the first user identifier is the transferring party identifier and the second user identifier is the transferring party identifier, then the resource transfer recovery request carries both the first user identifier and the second user identifier. In this case, the first user identifier is the transferring party identifier and the second user identifier is the transferring party identifier.

[0225] It should be noted that the embodiments in this application are described by directly transferring the resources of the first user identifier. In another embodiment, step 804 is not required, and the following alternative steps are performed instead:

[0226] A resource transfer task is generated. In response to the resource transfer task reaching its preset lifespan, the step of transferring resources according to the first resource transfer request is executed. The resource transfer task includes a first user identifier, and the preset lifespan can be any duration, such as 1 second, 0.5 seconds, etc.

[0227] Since the resource transfer server may receive multiple resource transfer requests, in order to ensure the accuracy of resource transfer, a corresponding resource transfer task is generated for each resource transfer request. A preset duration is set for the resource transfer task, and the corresponding resource transfer task is executed according to the lifespan of the resource transfer task. This ensures that the resource transfer task can be executed accurately, thereby ensuring the accuracy of resource transfer.

[0228] In one possible implementation, the method further includes: in response to the resource transfer task's lifetime not reaching a preset duration and receiving a resource transfer revocation request, deleting the resource transfer task according to the resource transfer revocation request. The resource transfer revocation request carries a first user identifier.

[0229] A resource transfer cancellation request indicates that a third-party device has cancelled the resource transfer request. The resource transfer server no longer needs to perform the resource transfer based on the first resource transfer request. Therefore, based on this resource transfer cancellation request, the resource transfer task is deleted, thereby cancelling the resource transfer.

[0230] like Figure 11 As shown, after the resource transfer server receives the resource transfer request, the resource transfer server generates a resource transfer task.

[0231] When the lifespan of a resource transfer task reaches the preset duration, the task is completed, and a reverse check is performed to verify the task and prevent errors. If a resource transfer recovery request is received after a successful transfer, a resource transfer cancellation task is generated to restore the successfully transferred resources.

[0232] If the resource transfer task does not reach the preset duration and a resource transfer cancellation request is received, the resource transfer task is deleted, thereby canceling the resource transfer.

[0233] If the resource transfer task reaches its preset lifespan without completing the resource transfer, it indicates that the resource transfer task has timed out and failed. In this case, the resource transfer server will cancel and delete the resource transfer task, and send a failure notification to the management server. The failure notification carries the first user identifier and is sent by the management server to the third-party device to indicate that the resource transfer of the first user identifier has failed.

[0234] In addition, the resource transfer task also includes the quantity of resources to be transferred. When transferring resources according to the resource transfer task, resources equal to the quantity of resources are transferred out from the resource account of the first user identifier.

[0235] It should be noted that the embodiments of this application are described separately with reference to a resource transfer server and a management server. In another embodiment, the resource management server includes both a resource transfer server and a management server. In this case, the steps performed by the resource transfer server and the management server in the above embodiments can be replaced by the resource management server. Then, the third device interacts with the resource management server to achieve password-free payment.

[0236] Furthermore, this application embodiment only illustrates a single resource transfer process involving only one management server. In another embodiment, the resource transfer server can interact with multiple management servers, receiving resource transfer requests from these servers and performing resource transfers accordingly. Among the multiple management servers, different servers provide different services, meaning they manage different objects. For example, management server A provides car owner services, managing ride-hailing apps, highway toll stations, car rental agencies, etc., while management server B provides utility payment services, managing water, electricity, gas, telephone, and other related institutions. The management identifiers of the multiple management servers can be stored in the resource transfer server as a list, such as... Figure 12 As shown, the list includes the icon, management ID, name of the administrator, status, creator of the administrator, last modified administrator, creation time, and last modification time for each management identifier.

[0237] The method provided in this application, due to the authorization relationship between the user and the administrator, and between the user and a third party and the administrator, enables the transfer of a user's resources to the third party or other users associated with that third party without password verification. This allows for real-time resource transfer without requiring the user to enter a password, simplifying the user's workflow and achieving a passwordless resource transfer solution, thus improving the convenience and flexibility of resource transfer. Furthermore, the administrator, acting as an intermediary, can facilitate resource transfers between the user and any third party managed by the administrator, or other users associated with any third party, when the user and the administrator have an authorization relationship. This eliminates the need for the user to authorize each third party or establish an authorization relationship between the user and each third party. It can be applied to resource transfers between users and multiple third parties, has a wide range of applications and good applicability, reduces the amount of authorization relationship data that needs to be stored, and thus reduces server load.

[0238] Figure 13This is a flowchart of the resource transfer method provided in this application, such as... Figure 13 As shown, the method includes:

[0239] 1. The management server receives the deduction request sent by the merchant terminal and then sends the deduction request to the resource transfer server.

[0240] 2. After receiving the deduction request from the management server, the resource transfer server performs the deduction synchronously according to the request and immediately sends a deduction completion notification to the management server so that the management server can send the deduction completion notification to the merchant terminal.

[0241] 3. After the deduction is completed, the resource transfer server sends a deduction completion notification to the user terminal.

[0242] Figure 14 This is a schematic diagram illustrating the relationship between a management identifier, a user identifier, and a third-party identifier, as provided in an embodiment of this application. Figure 14 As shown, each user ID can establish authorization relationships with multiple management IDs, and each management ID can establish authorization relationships with multiple user IDs. Similarly, each third-party ID can establish authorization relationships with multiple management IDs, and each management ID can establish authorization relationships with multiple third-party IDs.

[0243] For any given management identifier, there may be a corresponding management server. This management server can provide services for multiple application scenarios, such as rental scenarios, travel and transportation scenarios, and accommodation booking scenarios. In this case, the management server can initiate deduction requests to the resource management server from different application scenarios.

[0244] This application also provides a resource transfer scenario, such as... Figure 15 As shown, resource transfer methods include:

[0245] 1. Users select goods in the supermarket and then proceed to the supermarket checkout to settle their purchases.

[0246] 2. Supermarket cashiers enter the product information of the students' selected items into the supermarket terminal equipment. After the entry is completed, they initiate payment to the user through the supermarket terminal equipment.

[0247] 3. The supermarket uses its terminal equipment to perform facial recognition on users and obtain the user identifier corresponding to their faces. The supermarket terminal equipment sends the obtained user identifier to the supermarket server. The supermarket server sends a payment request to the management server and executes step 4. If facial recognition fails, payment is stopped. The supermarket server displays a failure notification, prompting the user that facial recognition failed and prompting the user to try again or use other payment methods.

[0248] 4. After confirming that both the supermarket identifier and the user identifier have a bound resource account on the resource transfer server, the management server sends a payment request to the resource transfer server. Based on this payment request, the resource transfer server generates a deduction request and sends it to the bank server. The bank server then transfers resources from the user's bank account to the supermarket's bank account, completing the purchase of the goods.

[0249] Figure 16 This is a schematic diagram of the structure of a resource transfer device provided in an embodiment of this application, as shown below. Figure 16 As shown, the device includes:

[0250] The first request acquisition module 1601 is used to acquire the first resource transfer request. The first resource transfer request carries a third-party identifier, a first user identifier, and a management identifier. The third-party identifier refers to a third party, the first user identifier refers to a first user, and the management identifier refers to the administrator.

[0251] The relationship determination module 1602 is used to determine the first authorization relationship in the authorization relationship database, which includes a first user identifier and a management identifier, and a second authorization relationship between a third-party identifier and a management identifier. The first authorization relationship indicates that the first user identifier's resources have been authorized to be transferred to a third party managed by the administrator or a user identifier associated with a third party without password verification. The second authorization relationship indicates that the administrator has been authorized to manage the third party.

[0252] The first resource transfer module 1603 is used to transfer resources according to the first resource transfer request.

[0253] In one possible implementation, such as Figure 17 As shown, the device also includes:

[0254] The request receiving module 1604 is used to receive an authorization request sent by a user terminal. The authorization request carries a first user identifier and a management identifier. The user terminal is a terminal that logs in with the first user identifier.

[0255] The relationship establishment module 1605 is used to establish the first authorization relationship between the first user identifier and the management identifier.

[0256] In another possible implementation, such as Figure 17 As shown, the relationship establishment module 1605 includes:

[0257] The notification sending unit 1651 is used to send an authentication notification to the user terminal based on the first user identifier. The user terminal is used to display the authentication notification and obtain the input identity information.

[0258] The identity information receiving unit 1652 is used to receive identity information sent by the user terminal;

[0259] The relationship establishment unit 1653 is used to establish a first authorization relationship between the first user identifier and the management identifier when the identity information is verified.

[0260] In another possible implementation, such as Figure 17 As shown, the device also includes:

[0261] The task generation module 1606 is used to generate resource transfer tasks, and the resource transfer tasks include a first user identifier.

[0262] The second resource transfer module 1607 is used to execute the steps of transferring resources according to the first resource transfer request when the lifespan of the resource transfer task reaches a preset time.

[0263] In another possible implementation, such as Figure 17 As shown, the device also includes:

[0264] The task deletion module 1608 is used to delete the resource transfer task in response to the fact that the lifespan of the resource transfer task has not reached the preset time and a resource transfer cancellation request has been received. The resource transfer cancellation request carries the first user identifier.

[0265] In another possible implementation, such as Figure 17 As shown, the device also includes:

[0266] The second request acquisition module 1609 is used to acquire the resource transfer and recovery request, which carries the first user identifier.

[0267] The resource recovery module 1610 is used to restore resources transferred from the resource account of the first user to the resource account of the first user.

[0268] In another possible implementation, the third party is a third-party server, and the first resource transfer request also carries a second user identifier, which is a user identifier registered with the third-party server;

[0269] like Figure 17 As shown, the first resource transfer module 1603 includes:

[0270] Resource transfer unit 1631 is used to transfer resources from a resource account identified by a first user to a resource account identified by a second user, according to a first resource transfer request.

[0271] In another possible implementation, the resource transfer unit 1631 is used to transfer resources from the resource account of the first user identifier to the first resource account bound to the second user identifier according to the first resource transfer request, wherein the resource account of the first user identifier and the first resource account are resource accounts registered in the resource transfer server; and transfer resources from the first resource account to the target resource account of the second user identifier, wherein the target resource account is not a resource account registered in the resource transfer server.

[0272] In another possible implementation, the device is applied to a resource transfer server, and the manager is a management server; such as Figure 17 As shown, the first request acquisition module 1601 includes:

[0273] The request receiving unit 1611 is used to receive a first resource transfer request sent by the management server. The first resource transfer request is sent by the management server when it receives a second resource transfer request triggered by a third party. The second resource transfer request carries a third party identifier and a first user identifier.

[0274] Figure 18 This is a schematic diagram of the structure of a resource transfer device provided in an embodiment of this application, as shown below. Figure 18 As shown, the device includes:

[0275] The request receiving module 1801 is used to receive a second resource transfer request sent by a third-party device. The second resource transfer request carries a first user identifier and a third-party identifier. The third-party identifier refers to a third party, and the first user identifier refers to a first user.

[0276] The request sending module 1802 is used to send a first resource transfer request to the resource transfer server. The first resource transfer request carries a third-party identifier, a first user identifier, and a management identifier. The management identifier refers to the administrator. The resource transfer server is used to receive the first resource transfer request, determine the first authorization relationship in the authorization relationship database, which includes the first user identifier and the management identifier, and the second authorization relationship between the third-party identifier and the management identifier. The first authorization relationship indicates that the administrator is authorized to transfer the resources of the first user identifier to a third party managed by the administrator or a user identifier associated with a third party without password verification. The second authorization relationship indicates that the administrator is authorized to manage the third party. The server then performs the resource transfer according to the first resource transfer request.

[0277] In one possible implementation, such as Figure 19 As shown, the request sending module 1802 includes:

[0278] The first request sending unit 1821 is used to send a first resource transfer request to the resource transfer server in response to the fact that both the first user identifier and the third party identifier have resource accounts bound to the resource transfer server.

[0279] In another possible implementation, such as Figure 19 As shown, the request sending module 1802 includes:

[0280] The second request sending unit 1822 is used to send a first resource transfer request to the resource transfer server in response to a resource transfer task in which the first user identifier is not found.

[0281] Figure 20 This is a schematic diagram of the structure of a resource transfer device provided in an embodiment of this application, as shown below. Figure 20 As shown, the device includes:

[0282] The interface display module 2001 is used to display an authorization confirmation interface based on the first user identifier of the login, and the authorization confirmation interface includes the management identifier requesting authorization;

[0283] The authorization request sending module 2002 is used to send an authorization request to the resource management server in response to the confirmation operation detected in the authorization confirmation interface. The authorization request carries the first user identifier and the management identifier. The resource management server is used to receive the authorization request and establish a first authorization relationship between the first user identifier and the management identifier. The first authorization relationship indicates that it is authorized to transfer the resources of the first user identifier to a third party managed by the administrator or a user identifier associated with a third party without verifying the password.

[0284] In one possible implementation, the resource management server is used to receive authorization requests and return authentication notifications, such as... Figure 21 As shown, the device also includes:

[0285] The notification receiving module 2003 is used to display the authentication notification in the authorization confirmation interface in response to receiving the authentication notification;

[0286] The identity information sending module 2004 is used to obtain the input identity information through the authorization confirmation interface and send the identity information to the resource management server. When the identity information is verified, the resource management server establishes the first authorization relationship between the first user identifier and the management identifier.

[0287] Figure 22 A schematic diagram of a terminal 2200 provided in an exemplary embodiment of this application is shown. The terminal 2200 is used to execute the steps performed by the terminal in the above-described resource transfer method.

[0288] Typically, terminal 2200 includes a processor 2201 and a memory 2202.

[0289] Processor 2201 may include one or more processing cores, such as a quad-core processor, an octa-core processor, etc. Processor 2201 may be implemented using at least one hardware form selected from DSP (Digital Signal Processing), FPGA (Field-Programmable Gate Array), and PLA (Programmable Logic Array). Processor 2201 may also include a main processor and a coprocessor. The main processor, also known as a CPU (Central Processing Unit), is used to process data in the wake-up state; the coprocessor is a low-power processor used to process data in the standby state. In some embodiments, processor 2201 may integrate a GPU (Graphics Processing Unit), which is responsible for rendering and drawing the content to be displayed on the screen. In some embodiments, processor 2201 may also include an AI (Artificial Intelligence) processor, which is used to handle computational operations related to machine learning.

[0290] The memory 2202 may include one or more computer-readable storage media, which may be non-transitory. The memory 2202 may also include high-speed random access memory and non-volatile memory, such as one or more disk storage devices or flash memory devices. In some embodiments, the non-transitory computer-readable storage media in the memory 2202 are used to store at least one program code, which is used by the processor 2201 to implement the resource transfer method provided in the method embodiments of this application.

[0291] In some embodiments, the terminal 2200 may also optionally include a peripheral device interface 2203 and at least one peripheral device. The processor 2201, memory 2202, and peripheral device interface 2203 can be connected via a bus or signal line. Each peripheral device can be connected to the peripheral device interface 2203 via a bus, signal line, or circuit board. Specifically, the peripheral device includes at least one of the following: radio frequency circuitry 2204, display screen 2205, camera assembly 2206, audio circuitry 2207, and power supply 2209.

[0292] Peripheral device interface 2203 can be used to connect at least one I / O (Input / Output) related peripheral device to processor 2201 and memory 2202. In some embodiments, processor 2201, memory 2202 and peripheral device interface 2203 are integrated on the same chip or circuit board; in some other embodiments, any one or two of processor 2201, memory 2202 and peripheral device interface 2203 can be implemented on separate chips or circuit boards, which is not limited in this embodiment.

[0293] The radio frequency (RF) circuit 2204 is used to receive and transmit RF (Radio Frequency) signals, also known as electromagnetic signals. The RF circuit 2204 communicates with communication networks and other communication devices via electromagnetic signals. The RF circuit 2204 converts electrical signals into electromagnetic signals for transmission, or converts received electromagnetic signals back into electrical signals. Optionally, the RF circuit 2204 includes: an antenna system, an RF transceiver, one or more amplifiers, a tuner, an oscillator, a digital signal processor, a codec chipset, a user identity module card, etc. The RF circuit 2204 can communicate with other terminals through at least one wireless communication protocol. This wireless communication protocol includes, but is not limited to: metropolitan area networks (MANs), various generations of mobile communication networks (2G, 3G, 4G, and 5G), wireless local area networks (WLANs), and / or WiFi (Wireless Fidelity) networks. In some embodiments, the RF circuit 2204 may also include circuitry related to NFC (Near Field Communication), which is not limited in this application.

[0294] Display screen 2205 is used to display a UI (User Interface). This UI may include graphics, text, icons, videos, and any combination thereof. When display screen 2205 is a touch display screen, it also has the ability to collect touch signals on or above its surface. These touch signals can be input as control signals to processor 2201 for processing. In this case, display screen 2205 can also be used to provide virtual buttons and / or a virtual keyboard, also known as soft buttons and / or a soft keyboard. In some embodiments, there may be one display screen 2205, disposed on the front panel of terminal 2200; in other embodiments, there may be at least two display screens, disposed on different surfaces of terminal 2200 or in a folded design; in still other embodiments, display screen 2205 may be a flexible display screen, disposed on a curved or folded surface of terminal 2200. Furthermore, display screen 2205 may be configured as a non-rectangular, irregular shape, i.e., a non-rectangular screen. The display screen 2205 can be made of materials such as LCD (Liquid Crystal Display) and OLED (Organic Light-Emitting Diode).

[0295] The camera assembly 2206 is used to acquire images or videos. Optionally, the camera assembly 2206 includes a front-facing camera and a rear-facing camera. Typically, the front-facing camera is located on the front panel of the terminal 2200, and the rear-facing camera is located on the back of the terminal 2200. In some embodiments, there are at least two rear-facing cameras, which are any one of a main camera, a depth-sensing camera, a wide-angle camera, and a telephoto camera, to achieve background blurring by fusion of the main camera and the depth-sensing camera, panoramic shooting by fusion of the main camera and the wide-angle camera, VR (Virtual Reality) shooting, or other fusion shooting functions. In some embodiments, the camera assembly 2206 may also include a flash. The flash can be a single-color temperature flash or a dual-color temperature flash. A dual-color temperature flash refers to a combination of a warm light flash and a cool light flash, which can be used for light compensation at different color temperatures.

[0296] The audio circuit 2207 may include a microphone and a speaker. The microphone is used to collect sound waves from the user and the environment, converting them into electrical signals that are input to the processor 2201 for processing, or to the radio frequency circuit 2204 for voice communication. For stereo sound acquisition or noise reduction purposes, multiple microphones may be used, each positioned at a different location on the terminal 2200. The microphone may also be an array microphone or an omnidirectional microphone. The speaker is used to convert electrical signals from the processor 2201 or the radio frequency circuit 2204 into sound waves. The speaker may be a conventional diaphragm speaker or a piezoelectric ceramic speaker. When the speaker is a piezoelectric ceramic speaker, it can convert electrical signals not only into audible sound waves but also into inaudible sound waves for purposes such as distance measurement. In some embodiments, the audio circuit 2207 may also include a headphone jack.

[0297] Power supply 2209 is used to power the various components in terminal 2200. Power supply 2209 can be AC ​​power, DC power, a disposable battery, or a rechargeable battery. When power supply 2209 includes a rechargeable battery, the rechargeable battery can support wired or wireless charging. The rechargeable battery can also be used to support fast charging technology.

[0298] In some embodiments, the terminal 2200 further includes one or more sensors 2210. The one or more sensors 2210 include, but are not limited to: an acceleration sensor 2211, a gyroscope sensor 2212, a pressure sensor 2213, an optical sensor 2215, and a proximity sensor 2216.

[0299] Accelerometer 2211 can detect the magnitude of acceleration along the three coordinate axes of a coordinate system established by terminal 2200. For example, accelerometer 2211 can be used to detect the components of gravitational acceleration along the three coordinate axes. Processor 2201 can control display screen 2205 to display the user interface in either a landscape or portrait view based on the gravitational acceleration signal acquired by accelerometer 2211. Accelerometer 2211 can also be used to acquire motion data of applications or users.

[0300] The gyroscope sensor 2212 can detect the orientation and rotation angle of the terminal 2200. The gyroscope sensor 2212 can work in conjunction with the accelerometer sensor 2211 to collect the user's 3D movements on the terminal 2200. Based on the data collected by the gyroscope sensor 2212, the processor 2201 can perform the following functions: motion sensing (e.g., changing the UI based on the user's tilt), image stabilization during shooting, application control, and inertial navigation.

[0301] The pressure sensor 2213 can be disposed on the side bezel of the terminal 2200 and / or on the lower layer of the display screen 2205. When the pressure sensor 2213 is disposed on the side bezel of the terminal 2200, it can detect the user's grip signal on the terminal 2200, and the processor 2201 can perform left / right hand recognition or quick operation based on the grip signal collected by the pressure sensor 2213. When the pressure sensor 2213 is disposed on the lower layer of the display screen 2205, the processor 2201 can control the operable controls on the UI interface based on the user's pressure operation on the display screen 2205. The operable controls include at least one of button controls, scroll bar controls, icon controls, and menu controls.

[0302] Optical sensor 2215 is used to collect ambient light intensity. In one embodiment, processor 2201 can control the display brightness of display screen 2205 based on the ambient light intensity collected by optical sensor 2215. Specifically, when the ambient light intensity is high, the display brightness of display screen 2205 is increased; when the ambient light intensity is low, the display brightness of display screen 2205 is decreased. In another embodiment, processor 2201 can also dynamically adjust the shooting parameters of camera assembly 2206 based on the ambient light intensity collected by optical sensor 2215.

[0303] The proximity sensor 2216, also known as a distance sensor, is typically mounted on the front panel of the terminal 2200. The proximity sensor 2216 is used to detect the distance between the user and the front of the terminal 2200. In one embodiment, when the proximity sensor 2216 detects that the distance between the user and the front of the terminal 2200 is gradually decreasing, the processor 2201 controls the display screen 2205 to switch from a screen-on state to a screen-off state; when the proximity sensor 2216 detects that the distance between the user and the front of the terminal 2200 is gradually increasing, the processor 2201 controls the display screen 2205 to switch from a screen-off state to a screen-on state.

[0304] Those skilled in the art will understand that Figure 22 The structure shown does not constitute a limitation on terminal 2200 and may include more or fewer components than shown, or combine certain components, or use different component arrangements.

[0305] Figure 23This is a schematic diagram of a server structure provided in an embodiment of this application. The server 2300 can vary considerably due to different configurations or performance. It may include one or more Central Processing Units (CPUs) 2301 and one or more memories 2302. The memory 2302 stores at least one line of program code, which is loaded and executed by the processor 2301 to implement the methods provided in the above-described method embodiments. Of course, the server may also have wired or wireless network interfaces, a keyboard, and input / output interfaces for input and output. The server may also include other components for implementing device functions, which will not be elaborated here.

[0306] Server 2300 can be used to execute the above resource transfer method.

[0307] This application also provides a computer device, which includes a processor and a memory. The memory stores at least one piece of program code, which is loaded and executed by the processor to implement the resource transfer method described in the above embodiments.

[0308] This application also provides a computer-readable storage medium storing at least one piece of program code, which is loaded and executed by a processor to implement the resource transfer method described above.

[0309] This application also provides a computer program product or computer program that includes computer program code stored in a computer-readable storage medium. A processor of a computer device reads the computer program code from the computer-readable storage medium and executes the computer program code, causing the computer device to implement the resource transfer method described in the above embodiments.

[0310] Those skilled in the art will understand that all or part of the steps of the above embodiments can be implemented by hardware or by a program instructing related hardware. The program can be stored in a computer-readable storage medium, such as a read-only memory, a disk, or an optical disk.

[0311] The above description is only an optional embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present application should be included within the protection scope of the present application.

Claims

1. A resource transfer method, characterized in that, The method is executed by a resource transfer server, which is either a payment application server or a social application server, and includes: The system receives an authorization request sent by a user terminal in response to a confirmation operation detected in the authorization confirmation interface; establishes a first authorization relationship between a first user identifier and a management identifier based on the authorization request; wherein, the user terminal has a target application corresponding to the resource transfer server installed, the user has registered a first user identifier in the target application, and a third user identifier has registered in the first application, the first application is another application on the user terminal besides the target application, the user logs into the first application through the third user identifier, obtains the management identifier with a second authorization relationship with the first application through the authorization option in the display interface of the first application, calls the interface of the target application, starts the target application, displays a binding interface in the target application, and displays the authorization confirmation interface of the target application based on the user's permission to bind the first user identifier and the third user identifier in the binding interface, the authorization confirmation interface of the target application including the management identifier; Wherein, the first authorization relationship indicates that the transfer of the resources of the first user identifier to a third party managed by the management server or a user identifier associated with a third party is authorized without password verification; the second authorization relationship indicates that the management server is authorized to manage the third party. The system receives a first resource transfer request from any one of a plurality of management servers; the different management servers manage different objects, and the management identifiers of the plurality of management servers are stored in the resource transfer server in the form of a list; wherein, the first resource transfer request carries a third-party identifier, the first user identifier, and the management identifier; Based on the first user identifier, the third-party identifier, and the management identifier, multiple authorization relationships stored in the authorization relationship database are queried to determine that the authorization relationship database includes a first authorization relationship between the first user identifier and the management identifier, and a second authorization relationship between the third-party identifier and the management identifier; Perform resource transfer according to the first resource transfer request.

2. The method according to claim 1, characterized in that, The authorization request carries the first user identifier and the management identifier, and the user terminal is the terminal that logs in with the first user identifier.

3. The method according to claim 2, characterized in that, The establishment of the first authorization relationship between the first user identifier and the management identifier based on the authorization request includes: Based on the first user identifier, an authentication notification is sent to the user terminal, and the user terminal is used to display the authentication notification and obtain the input identity information; Receive the identity information sent by the user terminal; When the identity information is verified, a first authorization relationship is established between the first user identifier and the management identifier.

4. The method according to claim 1, characterized in that, After determining that the authorization relationship database includes a first authorization relationship between the first user identifier and the management identifier, and a second authorization relationship between the third-party identifier and the management identifier, the method further includes: Generate a resource transfer task, wherein the resource transfer task includes the first user identifier; In response to the resource transfer task reaching a preset duration, the step of transferring resources according to the first resource transfer request is executed.

5. The method according to claim 4, characterized in that, After generating the resource transfer task, the method further includes: In response to the fact that the lifespan of the resource transfer task has not reached the preset duration and a resource transfer cancellation request is received, the resource transfer task is deleted according to the resource transfer cancellation request, and the resource transfer cancellation request carries the first user identifier.

6. The method according to claim 1, characterized in that, After performing the resource transfer according to the first resource transfer request, the method further includes: Obtain a resource transfer and recovery request, wherein the resource transfer and recovery request carries the first user identifier; Resources transferred from the resource account of the first user identifier will be restored to the resource account of the first user identifier.

7. The method according to claim 1, characterized in that, The third party is a third-party server, and the first resource transfer request also carries a second user identifier, which is a user identifier registered with the third-party server. The step of transferring resources according to the first resource transfer request includes: Based on the first resource transfer request, resources are transferred from the resource account of the first user identifier to the resource account of the second user identifier.

8. The method according to claim 7, characterized in that, The step of transferring resources from the resource account of the first user identifier to the resource account of the second user identifier according to the first resource transfer request includes: According to the first resource transfer request, resources are transferred from the resource account of the first user identifier to the first resource account bound to the second user identifier. The resource account of the first user identifier and the first resource account are resource accounts registered on the resource transfer server. Resources are transferred from the first resource account to a target resource account identified by the second user, wherein the target resource account is not a resource account registered on the resource transfer server.

9. A resource transfer method, characterized in that, The method, performed by any one of a plurality of management servers, includes: Receive a second resource transfer request sent by a third-party device, the second resource transfer request carrying a first user identifier and a third-party identifier; A first resource transfer request is sent to a resource transfer server. The resource transfer server first queries multiple authorization relationships stored in the authorization relationship database based on the first user identifier, the third-party identifier, and the management identifier. After determining that the authorization relationship database includes a first authorization relationship between the first user identifier and the management identifier, and a second authorization relationship between the third-party identifier and the management identifier, the resource transfer is performed according to the first resource transfer request. The first resource transfer request carries the third-party identifier, the first user identifier, and the management identifier. The first authorization relationship indicates that the transfer of the first user identifier's resources to a third party managed by the management server or a user identifier associated with a third party is authorized without password verification. The second authorization relationship indicates that the management server is authorized to manage the third party. The resource transfer server is either a payment application server or a social application server; among the multiple management servers, different management servers manage different objects, and the management identifiers of the multiple management servers are stored in the resource transfer server in the form of a list; The resource transfer server is used for: The system receives an authorization request sent by a user terminal in response to a confirmation operation detected in the authorization confirmation interface; establishes a first authorization relationship based on the authorization request; wherein, the user terminal has a target application corresponding to the resource transfer server installed, the user has registered a first user identifier in the target application, and a third user identifier in the first application, the first application being an application other than the target application on the user terminal, the user logs into the first application through the third user identifier, obtains the management identifier with a second authorization relationship with the first application through the authorization option in the display interface of the first application, calls the interface of the target application, starts the target application, displays a binding interface in the target application, and displays the authorization confirmation interface of the target application based on the user's permission to bind the first user identifier and the third user identifier in the binding interface, the authorization confirmation interface of the target application including the management identifier.

10. The method according to claim 9, characterized in that, Sending the first resource transfer request to the resource transfer server includes: In response to the fact that both the first user identifier and the third-party identifier have a bound resource account on the resource transfer server, the first resource transfer request is sent to the resource transfer server.

11. The method according to claim 9, characterized in that, Sending the first resource transfer request to the resource transfer server includes: In response to the failure to find a resource transfer task for the first user identifier, the first resource transfer request is sent to the resource transfer server.

12. A resource transfer method, characterized in that, The method includes: Based on the first user identifier logged in, an authorization confirmation interface for the target application is displayed. This interface includes a management identifier requesting authorization. In response to a confirmation operation detected on the authorization confirmation interface, an authorization request is sent to a resource transfer server. This authorization request carries the first user identifier and the management identifier. The resource transfer server receives the authorization request and establishes a first authorization relationship between the first user identifier and the management identifier. This first authorization relationship indicates that the transfer of resources belonging to the first user identifier to a third party managed by the management server or a user identifier associated with a third party is authorized without password verification. The user terminal has the target application corresponding to the resource transfer server installed. A first user identifier is registered in the target application, and a third user identifier is registered on the first application. The first application is an application on the user terminal other than the target application. The user logs into the first application using the third user identifier, obtains a management identifier with a second authorization relationship with the first application through the authorization option in the first application's display interface, calls the interface of the target application, starts the target application, and displays a binding interface in the target application. Based on the user's permission to bind the first user identifier and the third user identifier in the binding interface, the authorization confirmation interface is displayed. The second authorization relationship indicates that the management server has been authorized to manage the third party. The resource transfer server is either a payment application server or a social application server; the resource transfer server is used for: The system receives a first resource transfer request from any one of a plurality of management servers; the different management servers manage different objects, and the management identifiers of the plurality of management servers are stored in the resource transfer server in the form of a list; the first resource transfer request carries a third-party identifier, a first user identifier, and a management identifier; Based on the first user identifier, the third-party identifier, and the management identifier, multiple authorization relationships stored in the authorization relationship database are queried to determine that the authorization relationship database includes the first authorization relationship and the second authorization relationship; Perform resource transfer according to the first resource transfer request.

13. The method according to claim 12, characterized in that, The resource transfer server is used to receive the authorization request and return an authentication notification; After sending the authorization request to the resource transfer server, the method further includes: In response to receiving the authentication notification, the authentication notification is displayed on the authorization confirmation interface; The user obtains the input identity information through the authorization confirmation interface and sends the identity information to the resource transfer server. When the identity information is verified, the resource transfer server establishes a first authorization relationship between the first user identifier and the management identifier and stores the first authorization relationship in the authorization relationship database on the resource transfer server.

14. A resource transfer method, characterized in that, The method includes: The resource transfer server receives an authorization request sent by a user terminal in response to a confirmation operation detected in the authorization confirmation interface of the target application; establishes a first authorization relationship between a first user identifier and a management identifier based on the authorization request; wherein, the user terminal has the target application corresponding to the resource transfer server installed, the user has registered a first user identifier in the target application, and a third user identifier has registered in the first application, the first application is another application on the user terminal besides the target application, the user logs into the first application through the third user identifier, obtains the management identifier with a second authorization relationship with the first application through the authorization option in the display interface of the first application, calls the interface of the target application, starts the target application, displays a binding interface in the target application, and displays the authorization confirmation interface based on the user's operation of allowing the binding of the first user identifier and the third user identifier in the binding interface, the authorization confirmation interface includes the management identifier; The resource transfer server is either a payment application server or a social application server; the first authorization relationship indicates that the resources of the first user identifier have been authorized to be transferred to a third party managed by the management server or a user identifier associated with a third party without password verification; the second authorization relationship indicates that the management server has been authorized to manage the third party. The third-party device sends a second resource transfer request to the management server, which carries the first user identifier and the third-party identifier. The management server receives the second resource transfer request and sends a first resource transfer request to the resource transfer server, which carries the third-party identifier, the first user identifier, and the management identifier. The resource transfer server receives the first resource transfer request sent by any one of the multiple management servers, and queries multiple authorization relationships stored in the authorization relationship database based on the first user identifier, the third party identifier, and the management identifier. It determines that the authorization relationship database includes the first authorization relationship and the second authorization relationship between the third party identifier and the management identifier; and performs resource transfer according to the first resource transfer request. Among the multiple management servers, different management servers manage different objects, and the management identifiers of the multiple management servers are stored in the resource transfer server in the form of a list.

15. A resource transfer device, characterized in that, The device, used in a resource transfer server, which is a payment application server or a social application server, includes: The request receiving module is used to receive the authorization request sent by the user terminal in response to the confirmation operation detected in the authorization confirmation interface; The relationship establishment module is used to establish a first authorization relationship between the first user identifier and the management identifier based on the authorization request; The user terminal has a target application corresponding to the resource transfer server installed on it. The user has registered a first user identifier in the target application and a third user identifier in the first application. The first application is an application on the user terminal other than the target application. The user logs into the first application through the third user identifier, obtains the management identifier with a second authorization relationship with the first application through the authorization option in the display interface of the first application, calls the interface of the target application, starts the target application, displays a binding interface in the target application, and displays the authorization confirmation interface of the target application based on the user's permission to bind the first user identifier and the third user identifier in the binding interface. The authorization confirmation interface includes the management identifier. Wherein, the first authorization relationship indicates that the transfer of the resources of the first user identifier to a third party managed by the management server or a user identifier associated with a third party is authorized without password verification; the second authorization relationship indicates that the management server is authorized to manage the third party. The first request acquisition module is used to receive a first resource transfer request sent by any one of a plurality of management servers; among the plurality of management servers, different management servers manage different objects, and the management identifiers of the plurality of management servers are stored in the resource transfer server in the form of a list; wherein, the first resource transfer request carries a third-party identifier, the first user identifier, and the management identifier; The relationship determination module is used to query multiple authorization relationships stored in the authorization relationship database based on the first user identifier, the third party identifier, and the management identifier, and determine the first authorization relationship between the first user identifier and the management identifier, and the second authorization relationship between the third party identifier and the management identifier in the authorization relationship database; The second resource transfer module is used to transfer resources according to the first resource transfer request.

16. A resource transfer device, characterized in that, The device includes: The request receiving module is used to receive a second resource transfer request sent by a third-party device, wherein the second resource transfer request carries a first user identifier and a third-party identifier; The request sending module is used to send a first resource transfer request to the resource transfer server. The resource transfer server first queries multiple authorization relationships stored in the authorization relationship database based on the first user identifier, the third-party identifier, and the management identifier. After determining that the authorization relationship database includes a first authorization relationship between the first user identifier and the management identifier, and a second authorization relationship between the third-party identifier and the management identifier, the resource transfer is performed according to the first resource transfer request. The first resource transfer request carries the third-party identifier, the first user identifier, and the management identifier. The first authorization relationship indicates that the transfer of the first user identifier's resources to a third party managed by the management server or a user identifier associated with a third party is authorized without password verification. The second authorization relationship indicates that the management server is authorized to manage the third party. The resource transfer server is either a payment application server or a social application server; among the multiple management servers, different management servers manage different objects, and the management identifiers of the multiple management servers are stored in the resource transfer server in the form of a list; The resource transfer server is used for: The system receives an authorization request sent by a user terminal in response to a confirmation operation detected in the authorization confirmation interface; establishes a first authorization relationship based on the authorization request; wherein, the user terminal has a target application corresponding to the resource transfer server installed, the user has registered a first user identifier in the target application, and a third user identifier in the first application, the first application being an application other than the target application on the user terminal, the user logs into the first application through the third user identifier, obtains the management identifier with a second authorization relationship with the first application through the authorization option in the display interface of the first application, calls the interface of the target application, starts the target application, displays a binding interface in the target application, and displays the authorization confirmation interface of the target application based on the user's permission to bind the first user identifier and the third user identifier in the binding interface, the authorization confirmation interface of the target application including the management identifier.

17. A resource transfer device, characterized in that, The device includes: The interface display module is used to display the authorization confirmation interface of the target application based on the first user identifier of the login, wherein the authorization confirmation interface includes a management identifier requesting authorization; An authorization request sending module is used to send an authorization request to a resource transfer server in response to a confirmation operation detected in the authorization confirmation interface. The authorization request carries the first user identifier and the management identifier. The resource transfer server is used to receive the authorization request and establish a first authorization relationship between the first user identifier and the management identifier. The first authorization relationship indicates that the transfer of resources belonging to the first user identifier to a third party managed by the management server or a user identifier associated with a third party is authorized without password verification. The user terminal has a target application corresponding to the resource transfer server installed. The user has registered the first user identifier in the target application and a third user identifier in the first application. The first application is an application other than the target application on the user terminal. The user logs into the first application using the third user identifier, obtains a management identifier with a second authorization relationship with the first application through the authorization option in the first application's display interface, calls the target application's interface, starts the target application, displays a binding interface in the target application, and displays the authorization confirmation interface based on the user's permission to bind the first user identifier and the third user identifier in the binding interface. The second authorization relationship indicates that the management server is authorized to manage the third party. The resource transfer server is either a payment application server or a social application server; the resource transfer server is used for: The system receives a first resource transfer request from any one of a plurality of management servers; the different management servers manage different objects, and the management identifiers of the plurality of management servers are stored in the resource transfer server in the form of a list; the first resource transfer request carries a third-party identifier, a first user identifier, and a management identifier; Based on the first user identifier, the third-party identifier, and the management identifier, multiple authorization relationships stored in the authorization relationship database are queried to determine that the authorization relationship database includes the first authorization relationship and the second authorization relationship; Perform resource transfer according to the first resource transfer request.

18. A computer device, characterized in that, The computer device includes a processor and a memory, the memory storing at least one piece of program code, the at least one piece of program code being loaded and executed by the processor to implement the resource transfer method as described in any one of claims 1 to 8; or to implement the resource transfer method as described in any one of claims 9 to 11; or to implement the resource transfer method as described in claim 12 or 13.

19. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores at least one piece of program code, which is loaded and executed by a processor to implement the resource transfer method as described in any one of claims 1 to 8; or to implement the resource transfer method as described in any one of claims 9 to 11; or to implement the resource transfer method as described in claim 12 or 13.

20. A computer program product, characterized in that, The computer program product includes computer program code stored in a computer-readable storage medium. A processor of a computer device reads the computer program code from the computer-readable storage medium and executes the computer program code to implement the resource transfer method as described in any one of claims 1 to 8; or to implement the resource transfer method as described in any one of claims 9 to 11; or to implement the resource transfer method as described in claim 12 or 13.

Images