Resource transfer method and device, computer equipment, readable storage medium and program product

Abstract

The invention relates to the field of cloud computing, and particularly discloses a resource transfer method and device, computer equipment, a computer readable storage medium and a computer program product. The method comprises the following steps: receiving a resource transfer request initiated by a client, and determining a resource transfer-out party to which a first account belongs and a resource receiver to which the resource transfer request aims; determining the amount of to-be-received resources for the resource transfer-out party from multiple pieces of to-be-received resource information of the resource receiving party; under the condition that the resource transfer-out party has the in-transit resource transfer task corresponding to the resource receiving party, based on the relationship between the resource transfer amount of the in-transit resource transfer task and the to-be-collected resource amount, determining and feeding back an expected transfer amount for the resource transfer request to the client; and under the condition that the client finishes resource transfer according to the expected transfer amount, changing the to-be-received resource information corresponding to the expected transfer amount into a received state. By adopting the method, the resource transfer efficiency can be improved.

Description

Technical Field

[0001] This application relates to the field of cloud computing technology, and in particular to a resource transfer method, apparatus, computer equipment, computer-readable storage medium, and computer program product. Background Technology

[0002] With the development of cloud computing technology, in resource transfer scenarios involving multiple parties, it is not only necessary to complete the transfer of resources from the resource transferor to the resource recipient, but also to ensure that each resource can be accurately matched with specific resource information to be received, so as to achieve closed-loop management of business traceability.

[0003] In traditional technologies, the resource transfer process is highly dependent on manual intervention. Users need to first query the unique identifier related to the resource recipient from the business system, and then manually enter the identifier as the basis for association in the resource transfer operation interface. If the input is incorrect or the identifier format is not correct, it will directly lead to the business data and payment behavior not matching, which will cause the resource transfer process to be abnormal. Therefore, the traditional resource transfer method has the problem of low resource transfer efficiency. Summary of the Invention

[0004] Therefore, it is necessary to provide a resource transfer method, apparatus, computer equipment, computer-readable storage medium, and computer program product that can improve the efficiency of resource transfer in order to address the above-mentioned technical problems.

[0005] Firstly, this application provides a resource transfer method applied to a server, comprising:

[0006] Receive a resource transfer request initiated by a client logged in with a first account, and determine the resource transferor to which the first account belongs, as well as the resource recipient to which the resource transfer request is directed;

[0007] From the multiple pending resource information of the resource recipient, determine the amount of pending resources to be collected for the resource transferor;

[0008] If there is an in-transit resource transfer task corresponding to the resource recipient at the resource transferor, the expected transfer amount for the resource transfer request is determined and fed back to the client based on the relationship between the resource transfer amount of the in-transit resource transfer task and the amount of resources to be received.

[0009] If the client completes the resource transfer according to the expected transfer amount, the resource information to be collected corresponding to the expected transfer amount will be changed to a collected status.

[0010] In one embodiment, the number of resource amounts to be collected is multiple;

[0011] Based on the relationship between the resource transfer amount of the resource transfer task in transit and the resource amount to be received, the expected transfer amount for the resource transfer request is determined, including:

[0012] Determine the amount of resources transferred for the resource transfer task in transit;

[0013] If, among the various amounts of resources to be collected, there exists a candidate resource amount that is not equal to the amount of resources to be transferred, the expected transfer amount for the resource transfer request is determined based on the candidate resource amount.

[0014] In one embodiment, the number of in-transit resource transfer tasks is multiple; determining the expected transfer amount for the resource transfer request based on the relationship between the resource transfer amount of the in-transit resource transfer tasks and the amount of resources to be collected further includes:

[0015] If each of the resource amounts to be collected corresponds to a resource transfer amount of equal value, then for each value, the first number of times the value appears in the resource information to be collected corresponding to the resource transferor, and the second number of times the value appears in each resource transfer task in transit are counted.

[0016] From the given values, determine the target value that the second number is less than the first number;

[0017] The target value is adjusted based on a preset amount to obtain the expected transfer amount for the resource transfer request.

[0018] In one embodiment, the method further includes:

[0019] The selected resource amount is determined from the resource amounts to be collected corresponding to the target value;

[0020] The selected resource amount is adjusted based on the preset amount to obtain an updated amount to be collected that is equal to the expected transfer amount.

[0021] If the client completes the resource transfer according to the expected transfer amount, the preset amount of resources will be returned to the first account.

[0022] In one embodiment, the number of candidate resource amounts is multiple; determining the expected transfer amount for the resource transfer request based on the candidate resource amounts includes:

[0023] Based on the urgency of the information of the resource information to be collected for each of the candidate resource amounts, the processing priority of each of the resource information to be collected is determined.

[0024] Based on the number of candidate resources that meet the priority conditions, the expected transfer amount for the resource transfer request is determined.

[0025] Secondly, this application also provides a resource transfer method applied to a client, the method comprising:

[0026] Initiate a resource transfer request; enable the server to determine the resource transferor to which the first account belongs, and the resource recipient to whom the resource transfer request is directed; determine the amount of resources to be collected for the resource transferor from multiple pending resource information of the resource recipient; if there is an in-transit resource transfer task corresponding to the resource recipient at the resource transferor, determine and feed back the expected transfer amount for the resource transfer request to the client based on the relationship between the resource transfer amount of the in-transit resource transfer task and the amount of resources to be collected; the client logs in with the first account;

[0027] The resource transfer is completed according to the expected transfer amount, so that the server changes the pending resource information corresponding to the expected transfer amount to a received status.

[0028] In one embodiment, the method further includes:

[0029] Obtain the resource transfer operation initiated by the resource transferor based on the resource account;

[0030] If the resource account is not bound to the resource transferor, a binding guide will be displayed so that the resource transferor can bind to the resource account based on the binding guide;

[0031] The resource account is designated as the first account.

[0032] Thirdly, this application also provides a resource transfer device applied to a server, comprising:

[0033] The request receiving module is used to receive resource transfer requests initiated by clients logged in with the first account, and to determine the resource transferor to which the first account belongs, as well as the resource recipient to which the resource transfer request is directed;

[0034] The pending resource amount determination module is used to determine the pending resource amount for the resource transferor from multiple pending resource information of the resource recipient.

[0035] The expected transfer amount determination module is used to determine and feed back the expected transfer amount for the resource transfer request to the client based on the relationship between the resource transfer amount of the in-transit resource transfer task and the amount of resources to be received, when there is an in-transit resource transfer task corresponding to the resource recipient at the resource transferor.

[0036] The status change module is used to change the pending resource information corresponding to the expected transfer amount to a received status when the client completes the resource transfer according to the expected transfer amount.

[0037] In one embodiment, the number of resources to be collected is multiple; the expected transfer amount determination module includes:

[0038] A resource transfer amount determination unit is used to determine the resource transfer amount of the in-transit resource transfer task;

[0039] The expected transfer amount determination unit is used to determine the expected transfer amount for the resource transfer request based on the candidate resource amount when there is a candidate resource amount that is not equal to the resource transfer amount among the various resource amounts to be collected.

[0040] In one embodiment, the number of in-transit resource transfer tasks is multiple; the expected transfer amount determination module is further configured to:

[0041] If each of the resource amounts to be collected corresponds to a resource transfer amount of equal value, then for each value, the first number of times the value appears in the resource information to be collected corresponding to the resource transferor, and the second number of times the value appears in each resource transfer task in transit are counted.

[0042] From the given values, determine the target value that the second number is less than the first number;

[0043] The target value is adjusted based on a preset amount to obtain the expected transfer amount for the resource transfer request.

[0044] In one embodiment, the resource transfer device further includes a selected resource amount adjustment module, specifically used for:

[0045] The selected resource amount is determined from the resource amounts to be collected corresponding to the target value;

[0046] The selected resource amount is adjusted based on the preset amount to obtain an updated amount to be collected that is equal to the expected transfer amount.

[0047] If the client completes the resource transfer according to the expected transfer amount, the preset amount of resources will be returned to the first account.

[0048] In one embodiment, the number of candidate resource amounts is multiple; the expected transfer amount determination unit is specifically used for:

[0049] Based on the urgency of the information of the resource information to be collected for each of the candidate resource amounts, the processing priority of each of the resource information to be collected is determined.

[0050] Based on the number of candidate resources that meet the priority conditions, the expected transfer amount for the resource transfer request is determined.

[0051] Fourthly, this application also provides a resource transfer device applied to a client, the device comprising:

[0052] A resource transfer request initiation module is used to initiate a resource transfer request; to enable the server to determine the resource transferor to which the first account belongs, and the resource recipient to which the resource transfer request is targeted; to determine the amount of resources to be collected for the resource transferor from multiple pending resource information of the resource recipient; if there is an in-transit resource transfer task corresponding to the resource recipient at the resource transferor, to determine and feed back the expected transfer amount for the resource transfer request to the client based on the relationship between the resource transfer amount of the in-transit resource transfer task and the amount of resources to be collected; the client logs in with the first account;

[0053] The resource transfer module is used to complete the resource transfer according to the expected transfer amount, so that the server changes the pending resource information corresponding to the expected transfer amount to the received status.

[0054] In one embodiment, the device further includes an account binding module, specifically used for:

[0055] Obtain the resource transfer operation initiated by the resource transferor based on the resource account;

[0056] If the resource account is not bound to the resource transferor, a binding guide will be displayed so that the resource transferor can bind to the resource account based on the binding guide;

[0057] The resource account is designated as the first account.

[0058] Fifthly, this application also provides a computer device. The computer device includes a memory and a processor, the memory storing a computer program, and the processor executing the computer program to implement the steps of the method described above.

[0059] Sixthly, this application also provides a computer-readable storage medium. The computer-readable storage medium stores a computer program thereon, which, when executed by a processor, implements the steps of the method described above.

[0060] In a seventh aspect, this application also provides a computer program product. The computer program product includes a computer program that, when executed by a processor, implements the steps of the method described above.

[0061] When a user initiates a resource transfer request through a client, the aforementioned resource transfer method, apparatus, computer equipment, computer-readable storage medium, and computer program product identify the identities of the resource transferor and the resource recipient, and extract the amount of resources to be collected for the transferor from the resource recipient's uncollected resource information. If there are resource transfer tasks in transit, the server will determine and feed back the expected transfer amount for the resource transfer request to the client based on the relationship between the resource transfer amount of the in-transit resource transfer task and the amount of resources to be collected. The user only needs to complete the operation according to this expected transfer amount to achieve automatic association of business data without manually entering any business identifiers, which greatly improves the efficiency of resource transfer. Attached Figure Description

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

[0063] Figure 1 This is a diagram illustrating the application environment of a resource transfer method in one embodiment;

[0064] Figure 2 This is a flowchart illustrating a resource transfer method in one embodiment;

[0065] Figure 3 This is a flowchart illustrating the steps for determining the expected transfer amount in one embodiment;

[0066] Figure 4 This is a flowchart illustrating the step of determining the expected transfer amount in another embodiment;

[0067] Figure 5 This is a flowchart illustrating the resource return step in one embodiment;

[0068] Figure 6 This is a flowchart illustrating the priority determination step in one embodiment;

[0069] Figure 7 This is a flowchart illustrating the state change steps in one embodiment;

[0070] Figure 8 This is a flowchart illustrating the account binding steps in one embodiment;

[0071] Figure 9 This is a schematic diagram of the interface for the resource transfer process in one embodiment;

[0072] Figure 10 This is a flowchart illustrating the resource transfer method in another embodiment;

[0073] Figure 11 This is a flowchart illustrating the resource transfer method in yet another embodiment;

[0074] Figure 12 This is a structural block diagram of a resource transfer device in one embodiment;

[0075] Figure 13 This is a structural block diagram of the resource transfer device in another embodiment;

[0076] Figure 14 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation

[0077] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application. It should be noted that existing industry solutions such as software, components, and models may be mentioned in the embodiments of this application. These should be considered exemplary and are intended only to illustrate the feasibility of implementing the technical solutions of this application, but do not imply that the applicant has already used or necessarily used such solutions.

[0078] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of related data must comply with relevant regulations. The acquisition, storage, use and processing of data in the technical solution of this application all comply with the relevant provisions of national laws and regulations.

[0079] The resource transfer method provided in this application embodiment can be applied to, for example, Figure 1The application environment shown is as follows. Server 102 communicates with client 104 via a network. A data storage system stores the data that client 102 needs to process. The data storage system can be integrated onto server 102 or located in the cloud or on other network servers. Client 104 can be, but is not limited to, various personal computers, laptops, smartphones, tablets, IoT devices, and portable wearable devices. IoT devices can include smart speakers, smart TVs, smart air conditioners, smart in-vehicle devices, projection devices, etc. Portable wearable devices can include smartwatches, smart bracelets, head-mounted devices, etc. Head-mounted devices can be virtual reality (VR) devices, augmented reality (AR) devices, smart glasses, etc. Server 102 can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing cloud computing services. Specifically, when the resource transfer method is applied to server 102, server 102 receives a resource transfer request initiated by client 104 logged in with a first account, determines the resource transferor to which the first account belongs, and the resource recipient to which the resource transfer request is directed; determines the amount of resources to be collected for the resource transferor from multiple pending resource information of the resource recipient; if there is an in-transit resource transfer task corresponding to the resource recipient for the resource transferor, determines and feeds back the expected transfer amount for the resource transfer request to client 104 based on the relationship between the resource transfer amount of the in-transit resource transfer task and the amount of resources to be collected; if client 104 completes the resource transfer according to the expected transfer amount, changes the pending resource information corresponding to the expected transfer amount to the collected status. When the resource transfer method is applied to client 104, client 104 initiates a resource transfer request; so that server 102 can determine the resource transferor to which the first account belongs, and the resource recipient to which the resource transfer request is directed; determine the amount of resources to be collected for the resource transferor from multiple pending resource information of the resource recipient; if there is an in-transit resource transfer task corresponding to the resource recipient for the resource transferor, determine and feed back the expected transfer amount for the resource transfer request to client 104 based on the relationship between the resource transfer amount of the in-transit resource transfer task and the amount of resources to be collected; client 104 logs in with the first account; completes the resource transfer according to the expected transfer amount, so that server 102 changes the pending resource information corresponding to the expected transfer amount to the collected status.

[0080] In one exemplary embodiment, such as Figure 2 As shown, a resource transfer method is provided, which can be applied to... Figure 1 Taking server 102 as an example, the explanation includes the following steps S202 to S208. Wherein:

[0081] Step S202: Receive a resource transfer request initiated by a client logged in with the first account, and determine the resource transferor to which the first account belongs, and the resource recipient to which the resource transfer request is directed.

[0082] The primary account is a unique identifier registered by the user within the enterprise system or service platform, used to log in to the client and initiate operations. For example, the primary account could be the enterprise account of Company A. A resource transfer request is an instruction initiated by the user through the client to transfer resources from one party to another. It does not include a specific amount, only the direction of the transfer. The resource transferor is the entity to which the request initiator belongs, i.e., the source of the resource transfer. The resource recipient is the target entity of the resource transfer.

[0083] Specifically, when a user logs in with a primary account through the client and initiates a resource transfer request, they do not need to fill in the amount; they only need to select or enter the resource recipient. After receiving the resource transfer request, the server parses the ownership information of the primary account to determine the resource transferor. At the same time, it extracts the resource recipient's identifier from the resource transfer request to clarify the target of this transfer. For example, if an employee of company A selects "Pay to recipient B" in the client, the server automatically identifies company A as the resource transferor and recipient B as the resource recipient.

[0084] Step S204: Determine the amount of resources to be collected from the multiple resource information to be collected by the resource recipient for the resource transferor.

[0085] The "resources to be collected" information refers to resource items recorded by the resource recipient that have not yet been collected. Each item may include information such as the resource transferor, resource type, and resource amount. The "resources to be collected" amount is the specific amount of resources that the resource recipient has not yet collected from the resource transferor.

[0086] Specifically, based on the resource recipient determined in step S202, the server queries all pending resource information, filters out entries related to the resource sender from this pending resource information, and extracts the corresponding pending resource amount. For example, if resource recipient B's system has 3 unsettled orders, one of which is from resource sender A with an amount of 300, then the pending resource amount for resource sender A is 300.

[0087] Step S206: If there is an in-transit resource transfer task corresponding to the resource recipient on the resource transferor side, the expected transfer amount for the resource transfer request is determined and fed back to the client based on the relationship between the resource transfer amount of the in-transit resource transfer task and the amount of resources to be received.

[0088] In this context, a "transfer-in-transit" resource transfer task refers to a resource transfer operation initiated by the resource transferor but not yet completed. That is, the expected transfer amount has been determined, and the resource transferor has already transferred the resources, but the resource recipient has not yet changed the status of the transfer-in-transit task to "received." The expected transfer amount is the recommended transfer amount calculated by the server based on the relationship between the transfer-in task and the amount of resources to be received.

[0089] Specifically, the server checks whether the resource transferor has an in-transit resource transfer task for the resource recipient. If so, the server needs to further analyze the relationship between the resource transfer amount of the in-transit resource transfer task and the amount of resources to be collected determined in step S204, and then determine and feed back the expected transfer amount for the resource transfer request to the client.

[0090] Optionally, the server can determine the resource transfer amount for in-transit resource transfer tasks; if there are candidate resource amounts among the resource amounts to be collected that are not equal to the resource transfer amount, the expected transfer amount for the resource transfer request is determined based on the candidate resource amounts. Optionally, if each resource amount to be collected corresponds to a resource transfer amount of equal value, then for each value, the server counts the first occurrence of the value in the resource information to be collected corresponding to the resource transferor, and the second occurrence of the value in each in-transit resource transfer task; from each value, a target value is determined where the second occurrence is less than the first occurrence; the target value is adjusted based on a preset amount to obtain the expected transfer amount for the resource transfer request.

[0091] Step S208: If the client completes the resource transfer according to the expected transfer amount, change the pending resource information corresponding to the expected transfer amount to the received status.

[0092] The "received" status is the state in which the resource recipient marks a certain resource information to be received as "received" in the system, indicating that the corresponding resource has actually been received or cashed out.

[0093] Specifically, after the client completes the resource transfer according to the expected transfer amount reported in step S206, the server verifies the transfer result. After successful verification, the server finds the resource information to be collected that matches the current transfer from the resource recipient's pending resource information, updates the status of the pending resource information from "pending collection" to "collected", and records the actual amount of resources collected, time, operator, and other information.

[0094] In the above resource transfer method, when a user initiates a resource transfer request through the client, the server identifies the identities of the resource transferor and the resource recipient, and extracts the amount of resources to be collected for the transferor from the resource recipient's uncollected resource information. If there are resource transfer tasks in transit, the server will determine and feed back the expected transfer amount for the resource transfer request to the client based on the relationship between the resource transfer amount of the in-transit resource transfer task and the amount of resources to be collected. The user only needs to complete the operation according to this expected transfer amount to achieve automatic association of business data, without having to manually enter any business identifiers, which greatly improves the efficiency of resource transfer.

[0095] In one exemplary embodiment, such as Figure 3 As shown, there are multiple amounts of resources to be collected; based on the relationship between the resource transfer amount of in-transit resource transfer tasks and the amount of resources to be collected, the expected transfer amount for the resource transfer request is determined, including:

[0096] Step S302: Determine the amount of resources transferred for the resource transfer task in transit.

[0097] Among them, the amount of resource transfer refers to the quantity of resources that need to be transferred in a resource transfer task that is in transit.

[0098] Specifically, the server can query the in-transit resource transfer tasks of the resource transferor to the resource recipient and extract the resource transfer amount of the in-transit resource transfer tasks.

[0099] Step S304: If there are candidate resource amounts among the resource amounts to be collected that are not equal to the resource transfer amount, determine the expected transfer amount for the resource transfer request based on the candidate resource amounts.

[0100] In this context, the candidate resource amount refers to a resource item among multiple pending resource amounts that is not equal to the amount of resource transfers in transit. It can be understood that the existence of a candidate resource amount that is not equal to the resource transfer amount indicates that the candidate resource amount has not yet been transferred, the expected transfer amount has not yet been determined, and it differs from the previously identified pending resource amounts with determined expected transfer amounts. There will be no situation where the amounts are the same, making it impossible to determine the corresponding pending resource information. Therefore, the expected transfer amount for the resource transfer request can be directly determined based on the candidate resource amount. For example, if the pending resource amounts include 100 and 200, and the resource transfer amount for the in-transit resource transfer task is 100, then the "200 amount" is a candidate resource amount that is not equal to the resource transfer amount. Therefore, the expected transfer amount for the resource transfer request can be determined as "200 amount" based on this "200 amount".

[0101] The method of this embodiment can improve resource transfer efficiency when the information of the resources to be collected cannot be determined due to the same amount of resources being transferred.

[0102] In one exemplary embodiment, such as Figure 4 As shown, there are multiple resource transfer tasks in transit; based on the relationship between the resource transfer amount of the resource transfer tasks in transit and the amount of resources to be received, the expected transfer amount for the resource transfer request is determined, which also includes:

[0103] Step S402: If each amount of resources to be collected corresponds to an equal amount of resources to be transferred, then for each value, count the first number of times the value appears in the information of the resources to be collected corresponding to the resource transferor, and the second number of times the value appears in each resource transfer task in transit.

[0104] The first count represents the number of times each value appears in the resource transferor's pending resource information. The second count represents the number of times each value appears in all ongoing resource transfer tasks.

[0105] Specifically, if all pending resource amounts have corresponding resource transfer amounts of equal value, it is necessary to count the first occurrence of each value in the pending resource information corresponding to the resource transferor and the second occurrence in each in-transit resource transfer task. For example, if the pending resource amounts are 100, 200, 300, and 300, and the resource transfer amounts are 100, 200, and 300, respectively, meaning each pending resource amount corresponds to a corresponding resource transfer amount of equal value, for the value 100, the first occurrence of this value in the pending resource information corresponding to the resource transferor is 1, and the second occurrence in each in-transit resource transfer task is 1. For the value 200, the first occurrence of this value in the pending resource information corresponding to the resource transferor is 1, and the second occurrence in each in-transit resource transfer task is 1. For the value 300, the first occurrence of this value in the pending resource information corresponding to the resource transferor is 2, and the second occurrence in each in-transit resource transfer task is 1.

[0106] Step S404: Determine the target value from which the second number is less than the first number.

[0107] The target value is the value where the second number is less than the first number.

[0108] Specifically, as in the example above, the value 300 appears twice in the resource information to be collected by the resource transferor and once in each in-transit resource transfer task. Therefore, the value 300 is the target value where the second number is less than the first number.

[0109] Step S406: Adjust the target value based on the preset amount to obtain the expected transfer amount for the resource transfer request.

[0110] The preset amount is a system-preset adjustment baseline value, which is generally a random value. For example, the preset amount can be a random value such as 0.5, 0.1, or 0.142.

[0111] Specifically, if the second number is less than the first number, it indicates that there are two pending resource information entries corresponding to that value, but only one resource transfer amount. This means the resource recipient needs to receive the same resource amount twice. If the expected transfer amount is determined by the same amount, the resource recipient will receive two identical resource transfer amounts, making it impossible to identify which pending resource information it belongs to. Therefore, the target value can be adjusted based on a preset amount to obtain the expected transfer amount for the resource transfer request. For example, for the value 300 in the example above, a preset amount of 0.5 can be randomly determined. Adjusting the target value based on this preset amount yields 300.5, which is the expected transfer amount for the resource transfer request.

[0112] In this embodiment, the expected transfer amount is dynamically calculated by statistically analyzing the differences in the number of transfers, thus avoiding duplicate overwriting of the amount of resources to be collected by tasks in transit and ensuring the efficiency of resource allocation.

[0113] In one exemplary embodiment, such as Figure 5 As shown, the method also includes:

[0114] Step S502: Determine the selected resource amount from the resource amounts to be collected corresponding to the target value.

[0115] The selected resource amount is a specific item chosen from the resource amount to be collected corresponding to the target value.

[0116] Specifically, to ensure consistency in resource transfer between the client and server, the server needs to first determine the selected resource amount from the various pending resource amounts corresponding to the target value. That is, continuing from the example above, the selected resource amount determined by the server should be the last pending resource amount in the order of the pending resource amounts corresponding to the target value.

[0117] Step S504: Adjust the selected resource amount based on the preset amount to obtain the updated amount to be collected, which is equal to the expected transfer amount.

[0118] The amount to be collected and updated is the adjusted amount of resources to be collected, specifically for updating the amount on the server-side system.

[0119] Specifically, the server also needs to adjust the selected resource amount based on the preset amount to obtain an updated amount to be collected that is equal to the expected transfer amount, thereby aligning the resource transfer process between the server and the client and ensuring the stable progress of the subsequent status verification process.

[0120] Step S506: If the client completes the resource transfer according to the expected transfer amount, the preset amount of resources will be returned to the first account.

[0121] Specifically, if the client completes the resource transfer according to the expected amount, since the amount of resources the client should have transferred is actually the target amount, the server also needs to return the preset amount of resources to the first account.

[0122] In this embodiment, by dynamically adjusting the amount to be collected and returning excess resources, the consistency of resource transfer between the client and the server can be guaranteed.

[0123] In one exemplary embodiment, such as Figure 6 As shown, there are multiple candidate resource amounts; the expected transfer amount for the resource transfer request is determined based on the candidate resource amounts, including:

[0124] Step S602: Based on the urgency of the information to be collected for each candidate resource amount, determine the processing priority of each piece of information to be collected.

[0125] The urgency level of the information is a priority indicator for the resource information to be collected. For example, "high priority" indicates that it needs to be processed as soon as possible, while "low priority" indicates that it can be processed later. The processing priority is the order of the items to be collected after being sorted according to their urgency. The priority condition is the priority threshold preset by the server.

[0126] Specifically, to improve the flexibility and efficiency of resource transfer, the server can first determine the urgency of the resource information to be collected, and then assign a processing priority to each candidate resource amount based on the urgency level. For example, the server can prioritize resource information with a very urgent urgency level as high priority, and prioritize resource information with a moderate urgency level as low priority.

[0127] Step S604: Based on the number of candidate resources that meet the priority conditions for processing priority, determine the expected transfer amount for the resource transfer request.

[0128] Specifically, priority conditions refer to pre-set priority thresholds. In order to improve the flexibility of the resource transfer process and avoid inefficient operations, the server can first determine the expected transfer amount for the resource transfer request based on the number of candidate resources that meet the priority conditions in terms of processing priority.

[0129] In this embodiment, a priority mechanism is used to ensure that critical resource items are processed first, thereby improving business response speed and avoiding inefficient operations. At the same time, it supports flexible priority sorting rules to adapt to different business scenarios.

[0130] In one exemplary embodiment, such as Figure 7 As shown, a resource transfer method is also provided, applied to the client, including:

[0131] Step S702: Initiate a resource transfer request; so that the server can determine the resource transferor to which the first account belongs, and the resource recipient to which the resource transfer request is directed; determine the amount of resources to be collected for the resource transferor from multiple resource information to be collected by the resource recipient; if there is an in-transit resource transfer task corresponding to the resource recipient for the resource transferor, determine and feed back the expected transfer amount for the resource transfer request to the client based on the relationship between the resource transfer amount of the in-transit resource transfer task and the amount of resources to be collected; the client logs in with the first account.

[0132] Specifically, after logging in with a primary account through the client, the user clicks the "Transfer Resources" button on the interface, fills in the resource recipient's identifier, and submits a resource transfer request. Upon receiving the request, the server first parses the primary account's ownership information to determine the resource transferor. Simultaneously, it queries the recipient's account information using the resource recipient's identifier to determine the resource recipient. The server further examines the pending resource information, filters out pending resource information related to the resource transferor, and extracts the pending resource amount. If the resource transferor already has an ongoing resource transfer task for the resource recipient, the server compares the resource transfer amount of the ongoing task with the pending resource amount. Based on the relationship between the ongoing task's resource transfer amount and the pending resource amount, the server determines and sends the expected transfer amount for the resource transfer request back to the client.

[0133] Step S704: Complete the resource transfer according to the expected transfer amount, so that the server changes the pending resource information corresponding to the expected transfer amount to the received status.

[0134] Specifically, after the client receives the expected transfer amount from the server, the user confirms the amount and clicks the "Confirm Transfer" button, indicating that the resource transfer is completed according to the expected transfer amount. After the server verifies this, it can change the pending resource information corresponding to the expected transfer amount to the received status.

[0135] In one exemplary embodiment, such as Figure 8 As shown, resource transfer methods also include:

[0136] Step S802: Obtain the resource transfer operation initiated by the resource transferor based on the resource account.

[0137] Among them, a resource account is an external account that stores resources and must be bound to the client's primary account before it can be used. A resource transfer operation is a resource transfer request initiated by the user through the client that involves the resource account.

[0138] Specifically, the resource transferor can initiate a resource transfer operation based on the resource account. Only after the client obtains the resource transfer operation can it proceed with the subsequent confirmation and binding operation.

[0139] Step S804: If the resource account and the resource transferor are not bound together, display the binding instructions so that the resource transferor can bind the resource account based on the binding instructions.

[0140] The binding guide is displayed on the client and guides users through the steps to associate the resource account with the primary account.

[0141] Specifically, if the client query finds that the resource account is not bound to the resource transferor, a binding guide needs to be displayed on the operation interface. For example, a prompt box "Please bind the resource account first" can pop up so that the resource transferor can bind the resource account based on the binding guide.

[0142] Step S806: Designate the resource account as the first account.

[0143] The primary account is the one the user uses to log in to the client, serving as the initiator of the resource transfer. After the resource transferor binds the resource account according to the binding instructions, the client can then use the resource account as the primary account.

[0144] In this embodiment, by forcibly binding resource accounts, the resource transfer operation is ensured to be based on an authorized account, thereby improving security. At the same time, clear binding instructions are provided to lower the barrier to entry for users, avoid operation failures due to lack of binding, and improve user experience.

[0145] In one specific embodiment, a resource transfer method is also provided. Users only need to input a specific resource transfer amount generated by the system into the resource recipient's account via a client to complete the resource transfer. The system includes a client and a server. The client responds to user operations, displays the resource transfer information to the user, and after verifying the information, selects a first account for payment. If the resource account and the resource transferor are not bound together, binding instructions are displayed to enable the resource transferor to bind itself to the resource account based on these instructions.

[0146] After initiating a resource transfer request, the server queries multiple pending resource information for the resource recipient to determine the amount of pending resources for the resource transferor. If the resource transferor has an ongoing resource transfer task corresponding to the resource recipient, the server determines the resource transfer amount for that ongoing task. Among the pending resource amounts, there are candidate resource amounts that are not equal to the actual transfer amount. Based on these candidate amounts, the server determines the expected transfer amount for the resource transfer request. If each pending resource amount corresponds to a matching transfer amount, for each value, the server counts the first occurrence of that value in the pending resource information for the resource transferor and the second occurrence of that value in each ongoing resource transfer task. From these counts, a target value is determined where the second occurrence is less than the first occurrence. Based on this target value, the server adjusts the target value to obtain the expected transfer amount for the resource transfer request. Afterward, the server associates and stores all types of resource transfer information in the database and returns the generated expected transfer amount to the client. The user opens the client interface, enters the expected transfer amount and resource transfer information, and submits the request. Figure 9 If the client completes the resource transfer according to the expected transfer amount, the pending resource information corresponding to the expected transfer amount will be changed to a received status, and finally the resource transfer information will be deleted from the database.

[0147] In a specific embodiment, such as Figure 10 As shown, a resource transfer method is also provided, applied to the server side, including:

[0148] Step S1001: Receive a resource transfer request initiated by a client logged in with the first account, and determine the resource transferor to which the first account belongs, and the resource recipient to which the resource transfer request is directed;

[0149] Step S1002: Determine the amount of resources to be collected from the multiple resource information to be collected from the resource recipient for the resource transferor.

[0150] The number of resources to be collected is multiple;

[0151] Step S1003: If there is an in-transit resource transfer task corresponding to the resource recipient at the resource transferor, determine the resource transfer amount of the in-transit resource transfer task.

[0152] Step S1004: If there are candidate resource amounts that are not equal to the resource transfer amount among the various resource amounts to be collected, determine the processing priority of each resource information to be collected based on the information urgency of the resource information to be collected for each candidate resource amount.

[0153] Step S1005: Based on the number of candidate resources that meet the priority conditions for processing priority, determine the expected transfer amount for the resource transfer request.

[0154] Step S1006: If each amount of resources to be collected corresponds to a resource transfer amount of equal value, then for each value, count the first number of times the value appears in the resource information to be collected corresponding to the resource transferor, and the second number of times the value appears in each resource transfer task in transit.

[0155] Step S1007: Determine the target value from which the second number is less than the first number;

[0156] Step S1008: Adjust the target value based on the preset amount to obtain the expected transfer amount for the resource transfer request;

[0157] Step S1009: Determine the selected resource amount from the resource amounts to be collected corresponding to the target value;

[0158] Step S1010: Adjust the selected resource amount based on the preset amount to obtain the updated amount to be collected that is equal to the expected transfer amount.

[0159] Step S1011: If the client completes the resource transfer according to the expected transfer amount, the preset amount of resources will be returned to the first account.

[0160] Step S1012: If the client completes the resource transfer according to the expected transfer amount, change the pending resource information corresponding to the expected transfer amount to the received status.

[0161] In a specific embodiment, such as Figure 11 As shown, a resource transfer method is also provided, applied to the client, including:

[0162] Step S1101: Obtain the resource transfer operation initiated by the resource transferor based on the resource account;

[0163] Step S1102: If the resource account and the resource transferor are not bound together, display the binding instructions so that the resource transferor can bind the resource account based on the binding instructions;

[0164] Step S1103: Designate the resource account as the first account;

[0165] Step S1104: Initiate a resource transfer request;

[0166] This allows the server to determine the resource transferor to which the first account belongs, and the resource recipient to whom the resource transfer request is directed; from multiple pending resource information of the resource recipient, the amount of resources to be collected for the resource transferor is determined; if there is an in-transit resource transfer task corresponding to the resource recipient for the resource transferor, the expected transfer amount for the resource transfer request is determined and fed back to the client based on the relationship between the resource transfer amount of the in-transit resource transfer task and the amount of resources to be collected; the client logs in with the first account;

[0167] Step S1105: Complete the resource transfer according to the expected transfer amount, so that the server changes the pending resource information corresponding to the expected transfer amount to the received status.

[0168] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0169] Based on the same inventive concept, this application also provides a resource transfer apparatus for implementing the resource transfer method described above. The solution provided by this apparatus is similar to the implementation described in the above method; therefore, the specific limitations in one or more resource transfer apparatus embodiments provided below can be found in the limitations of the resource transfer method described above, and will not be repeated here.

[0170] In one exemplary embodiment, such as Figure 12 As shown, a resource transfer device 1200 is provided, including: a request receiving module 1202, a resource amount to be received determination module 1204, a desired transfer amount determination module 1206, and a status change module 1208, wherein:

[0171] The request receiving module 1202 is used to receive a resource transfer request initiated by a client logged in with a first account, and to determine the resource transferor to which the first account belongs, and the resource recipient to which the resource transfer request is directed;

[0172] The pending resource amount determination module 1204 is used to determine the pending resource amount for the resource transferor from multiple pending resource information of the resource recipient.

[0173] The expected transfer amount determination module 1206 is used to determine and feed back the expected transfer amount for the resource transfer request to the client based on the relationship between the resource transfer amount of the in-transit resource transfer task and the amount of resources to be received, when there is an in-transit resource transfer task corresponding to the resource recipient at the resource transferor.

[0174] The status change module 1208 is used to change the pending resource information corresponding to the expected transfer amount to a received status when the client completes the resource transfer according to the expected transfer amount.

[0175] In one exemplary embodiment, the number of resources to be collected is multiple. In this embodiment, the expected transfer amount determination module 1206 includes:

[0176] A resource transfer amount determination unit is used to determine the resource transfer amount of the in-transit resource transfer task;

[0177] The expected transfer amount determination unit is used to determine the expected transfer amount for the resource transfer request based on the candidate resource amount when there is a candidate resource amount that is not equal to the resource transfer amount among the various resource amounts to be collected.

[0178] In one exemplary embodiment, the number of in-transit resource transfer tasks is multiple. In this embodiment, the expected transfer amount determination module 1206 is further configured to:

[0179] If each of the resource amounts to be collected corresponds to a resource transfer amount of equal value, then for each value, the first number of times the value appears in the resource information to be collected corresponding to the resource transferor, and the second number of times the value appears in each resource transfer task in transit are counted.

[0180] From the given values, determine the target value that the second number is less than the first number;

[0181] The target value is adjusted based on a preset amount to obtain the expected transfer amount for the resource transfer request.

[0182] In an exemplary embodiment, the resource transfer device 1200 further includes a selected resource amount adjustment module, specifically used for:

[0183] The selected resource amount is determined from the resource amounts to be collected corresponding to the target value;

[0184] The selected resource amount is adjusted based on the preset amount to obtain an updated amount to be collected that is equal to the expected transfer amount.

[0185] If the client completes the resource transfer according to the expected transfer amount, the preset amount of resources will be returned to the first account.

[0186] In one exemplary embodiment, the number of candidate resource amounts is multiple. In this embodiment, the expected transfer amount determination unit is specifically used for:

[0187] Based on the urgency of the information of the resource information to be collected for each of the candidate resource amounts, the processing priority of each of the resource information to be collected is determined.

[0188] Based on the number of candidate resources that meet the priority conditions, the expected transfer amount for the resource transfer request is determined.

[0189] In one exemplary embodiment, such as Figure 13 As shown, a resource transfer device 1300 is also provided, the device comprising:

[0190] The resource transfer request initiation module 1302 is used to initiate a resource transfer request; to enable the server to determine the resource transferor to which the first account belongs, and the resource recipient to which the resource transfer request is targeted; to determine the amount of resources to be collected for the resource transferor from multiple pending resource information of the resource recipient; if there is an in-transit resource transfer task corresponding to the resource recipient at the resource transferor, to determine and feed back the expected transfer amount for the resource transfer request to the client based on the relationship between the resource transfer amount of the in-transit resource transfer task and the amount of resources to be collected; and the client logs in with the first account.

[0191] The resource transfer module 1304 is used to complete the resource transfer according to the expected transfer amount, so that the server changes the pending resource information corresponding to the expected transfer amount to the received status.

[0192] In one exemplary embodiment, the resource transfer device 1300 further includes an account binding module, specifically used for:

[0193] Obtain the resource transfer operation initiated by the resource transferor based on the resource account;

[0194] If the resource account is not bound to the resource transferor, a binding guide will be displayed so that the resource transferor can bind to the resource account based on the binding guide;

[0195] The resource account is designated as the first account.

[0196] Each module in the aforementioned resource transfer device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device, or stored in the memory of a computer device as software, so that the processor can call and execute the operations corresponding to each module.

[0197] In one exemplary embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram may be as follows: Figure 14 As shown, the computer device includes a processor, memory, input / output interfaces, a communication interface, a display unit, and an input device. The processor, memory, and input / output interfaces are connected via a system bus, and the communication interface, display unit, and input device are also connected to the system bus via the input / output interfaces. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The input / output interfaces are used for exchanging information between the processor and external devices. The communication interface is used for wired or wireless communication with external terminals; wireless communication can be achieved through Wi-Fi, mobile cellular networks, Near Field Communication (NFC), or other technologies. When the computer program is executed by the processor, it implements a resource transfer method. The display unit is used to form a visually visible image and can be a display screen, a projection device, or a virtual reality imaging device. The display screen can be an LCD screen or an e-ink screen. The input device of the computer device can be a touch layer covering the display screen, or buttons, trackballs, or touchpads set on the casing of the computer device, or external keyboards, touchpads, or mice, etc.

[0198] Those skilled in the art will understand that Figure 14 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0199] In one embodiment, a computer device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps of the method described above.

[0200] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements the steps of the above-described method.

[0201] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps of the method described above.

[0202] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, artificial intelligence (AI) processors, etc., and are not limited to these.

[0203] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0204] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A resource transfer method, characterized in that, Applied to the server side, the method includes: Receive a resource transfer request initiated by a client logged in with a first account, and determine the resource transferor to which the first account belongs, as well as the resource recipient to which the resource transfer request is directed; From the multiple pending resource information of the resource recipient, determine the amount of pending resources to be collected for the resource transferor; If there is an in-transit resource transfer task corresponding to the resource recipient at the resource transferor, the expected transfer amount for the resource transfer request is determined and fed back to the client based on the relationship between the resource transfer amount of the in-transit resource transfer task and the amount of resources to be received. If the client completes the resource transfer according to the expected transfer amount, the resource information to be collected corresponding to the expected transfer amount will be changed to a collected status.

2. The method according to claim 1, characterized in that, The number of resources to be collected is multiple; Based on the relationship between the resource transfer amount of the resource transfer task in transit and the resource amount to be received, the expected transfer amount for the resource transfer request is determined, including: Determine the amount of resources transferred for the resource transfer task in transit; If, among the various amounts of resources to be collected, there exists a candidate resource amount that is not equal to the amount of resources to be transferred, the expected transfer amount for the resource transfer request is determined based on the candidate resource amount.

3. The method according to claim 1, characterized in that, The number of in-transit resource transfer tasks is multiple; determining the expected transfer amount for the resource transfer request based on the relationship between the resource transfer amount of the in-transit resource transfer tasks and the amount of resources to be received further includes: If each of the resource amounts to be collected corresponds to a resource transfer amount of equal value, then for each value, the first number of times the value appears in the resource information to be collected corresponding to the resource transferor, and the second number of times the value appears in each resource transfer task in transit are counted. From the given values, determine the target value that the second number is less than the first number; The target value is adjusted based on a preset amount to obtain the expected transfer amount for the resource transfer request.

4. The method according to claim 3, characterized in that, The method further includes: The selected resource amount is determined from the resource amounts to be collected corresponding to the target value; The selected resource amount is adjusted based on the preset amount to obtain an updated amount to be collected that is equal to the expected transfer amount. If the client completes the resource transfer according to the expected transfer amount, the preset amount of resources will be returned to the first account.

5. The method according to claim 2, characterized in that, The number of candidate resource amounts is multiple; determining the expected transfer amount for the resource transfer request based on the candidate resource amounts includes: Based on the urgency of the information of the resource information to be collected for each of the candidate resource amounts, the processing priority of each of the resource information to be collected is determined. Based on the number of candidate resources that meet the priority conditions, the expected transfer amount for the resource transfer request is determined.

6. A resource transfer method, characterized in that, Applied to a client, the method includes: Initiate a resource transfer request; enable the server to determine the resource transferor to which the first account belongs, and the resource recipient to whom the resource transfer request is directed; determine the amount of resources to be collected for the resource transferor from multiple pending resource information of the resource recipient; if there is an in-transit resource transfer task corresponding to the resource recipient at the resource transferor, determine and feed back the expected transfer amount for the resource transfer request to the client based on the relationship between the resource transfer amount of the in-transit resource transfer task and the amount of resources to be collected; the client logs in with the first account; The resource transfer is completed according to the expected transfer amount, so that the server changes the pending resource information corresponding to the expected transfer amount to a received status.

7. The method according to claim 6, characterized in that, The method further includes: Obtain the resource transfer operation initiated by the resource transferor based on the resource account; If the resource account is not bound to the resource transferor, a binding guide will be displayed so that the resource transferor can bind to the resource account based on the binding guide; The resource account is designated as the first account.

8. A resource transfer device, characterized in that, Applied to the server side, the device includes: The request receiving module is used to receive resource transfer requests initiated by clients logged in with the first account, and to determine the resource transferor to which the first account belongs, as well as the resource recipient to which the resource transfer request is directed; The pending resource amount determination module is used to determine the pending resource amount for the resource transferor from multiple pending resource information of the resource recipient. The expected transfer amount determination module is used to determine and feed back the expected transfer amount for the resource transfer request to the client based on the relationship between the resource transfer amount of the in-transit resource transfer task and the amount of resources to be received, when there is an in-transit resource transfer task corresponding to the resource recipient at the resource transferor. The status change module is used to change the pending resource information corresponding to the expected transfer amount to a received status when the client completes the resource transfer according to the expected transfer amount.

9. The apparatus according to claim 8, characterized in that, The number of resources to be collected is multiple; the expected transfer amount determination module includes: A resource transfer amount determination unit is used to determine the resource transfer amount of the in-transit resource transfer task; The expected transfer amount determination unit is used to determine the expected transfer amount for the resource transfer request based on the candidate resource amount when there is a candidate resource amount that is not equal to the resource transfer amount among the various resource amounts to be collected.

10. The apparatus according to claim 8, characterized in that, The number of in-transit resource transfer tasks is multiple; the expected transfer amount determination module is further used for: If each of the resource amounts to be collected corresponds to a resource transfer amount of equal value, then for each value, the first number of times the value appears in the resource information to be collected corresponding to the resource transferor, and the second number of times the value appears in each resource transfer task in transit are counted. From the given values, determine the target value that the second number is less than the first number; The target value is adjusted based on a preset amount to obtain the expected transfer amount for the resource transfer request.

11. The apparatus according to claim 10, characterized in that, The resource transfer device further includes a selected resource amount adjustment module, specifically used for: The selected resource amount is determined from the resource amounts to be collected corresponding to the target value; The selected resource amount is adjusted based on the preset amount to obtain an updated amount to be collected that is equal to the expected transfer amount. If the client completes the resource transfer according to the expected transfer amount, the preset amount of resources will be returned to the first account.

12. The apparatus according to claim 9, characterized in that, The number of candidate resource amounts is multiple; the expected transfer amount determination unit is specifically used for: Based on the urgency of the information of the resource information to be collected for each of the candidate resource amounts, the processing priority of each of the resource information to be collected is determined. Based on the number of candidate resources that meet the priority conditions, the expected transfer amount for the resource transfer request is determined.

13. A resource transfer device, characterized in that, Applied to a client, the device includes: A resource transfer request initiation module is used to initiate a resource transfer request; to enable the server to determine the resource transferor to which the first account belongs, and the resource recipient to which the resource transfer request is targeted; to determine the amount of resources to be collected for the resource transferor from multiple pending resource information of the resource recipient; if there is an in-transit resource transfer task corresponding to the resource recipient at the resource transferor, to determine and feed back the expected transfer amount for the resource transfer request to the client based on the relationship between the resource transfer amount of the in-transit resource transfer task and the amount of resources to be collected; the client logs in with the first account; The resource transfer module is used to complete the resource transfer according to the expected transfer amount, so that the server changes the pending resource information corresponding to the expected transfer amount to the received status.

14. The apparatus according to claim 13, characterized in that, The device also includes an account binding module, specifically used for: Obtain the resource transfer operation initiated by the resource transferor based on the resource account; If the resource account is not bound to the resource transferor, a binding guide will be displayed so that the resource transferor can bind to the resource account based on the binding guide; The resource account is designated as the first account.

15. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 7.

16. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 7.

17. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 7.

Images