Data processing method and apparatus

Abstract

The embodiment of the present specification provides a data processing method and device, wherein a data processing method comprises: synchronizing to-be-processed data performing a front response action to a data pool of a corresponding first data party; performing resource advance payment processing of at least one to-be-processed data in the data pool according to a resource advance payment application for the at least one to-be-processed data; and allocating a flow resource corresponding to the at least one to-be-processed data to the first data party, so as to perform resource return processing on the advance payment resource obtained by the resource advance payment processing; and the flow resource obtains resource flow processing of a data set with a processing deadline in a combined processing mode.

Description

Technical Field

[0001] This document relates to the field of data processing technology, and in particular to a data processing method and apparatus. Background Technology

[0002] With the development of internet technology, data is stored and processed through the internet. Various types of data are processed through the internet, which places demands on the internet's data processing capabilities. In the process of data processing, data processors process data from data providers according to the processing methods corresponding to different data formats. As data providers process different types of data online, the resource consumption of data processors is also increasing. Summary of the Invention

[0003] This specification provides one or more embodiments of a data processing method. The data processing method includes: synchronizing data to be processed that undergoes a pre-response action to a corresponding first data party's data pool; performing resource pre-payment processing on the at least one piece of data to be processed based on a resource pre-payment request for at least one piece of data to be processed in the data pool; allocating transfer resources corresponding to the at least one piece of data to be processed to the first data party for resource return processing of the pre-paid resources obtained from the resource pre-payment processing; the transfer resources are obtained by performing resource transfer processing on datasets with processing time limits using a merge processing method.

[0004] This specification provides one or more embodiments of an order processing method, including: synchronizing pending payment orders that have executed service response actions to the corresponding merchant's order list; performing loan processing for at least one of the orders in the order list based on the merchant's loan application; and transferring payment funds obtained by merging the order set corresponding to the pending payment orders with combined payment periods to the merchant's merchant account for repayment of the loan funds obtained from the resource lending processing.

[0005] This specification provides one or more embodiments of a data processing apparatus, including: a data synchronization module configured to synchronize data to be processed that has undergone a pre-response action to a data pool of a corresponding first data party; a resource pre-allocation processing module configured to perform resource pre-allocation processing on at least one data to be processed based on a resource pre-allocation request for at least one data to be processed in the data pool; and a resource allocation module configured to allocate circulating resources corresponding to the at least one data to be processed to the first data party for resource return processing of the pre-allocated resources obtained from the resource pre-allocation processing; the circulating resources are obtained by performing resource circulating processing on a dataset with a processing period using a merged processing method.

[0006] This specification provides one or more embodiments of an order processing apparatus, including: an order synchronization module configured to synchronize pending payment orders that have performed service response actions to the corresponding merchant's order list; a fund lending processing module configured to perform fund lending processing for at least one of the orders in the order list based on a loan application from the merchant; and a fund transfer module configured to transfer payment funds obtained by merging the order set corresponding to the pending payment orders with combined payment periods to the merchant's merchant account for repayment of the loan funds obtained from the resource lending processing.

[0007] This specification provides one or more embodiments of a data processing apparatus, including: a processor; and a memory configured to store computer-executable instructions, which, when executed, cause the processor to: synchronize pending data for performing a pre-response action to a data pool of a corresponding first data party; perform resource pre-payment processing for at least one pending data in the data pool based on a resource pre-payment request; allocate transfer resources corresponding to the at least one pending data to the first data party for resource return processing of the pre-paid resources obtained from the resource pre-payment processing; the transfer resources are obtained by performing resource transfer processing on a dataset with a processing period using a merge processing method.

[0008] This specification provides one or more embodiments of an order processing device, including: a processor; and a memory configured to store computer-executable instructions, which, when executed, cause the processor to: synchronize pending payment orders that perform service response actions to the corresponding merchant's order list; perform loan processing for at least one of the orders in the order list based on a loan application from the merchant; and transfer payment funds obtained by merging the order set corresponding to the pending payment orders with combined payment periods to the merchant's merchant account for repayment of the loan funds obtained from the resource loan processing.

[0009] This specification provides one or more embodiments of a storage medium for storing computer-executable instructions, which, when executed by a processor, implement the following process: synchronizing pending data for performing pre-processing actions to a corresponding first data party's data pool; performing resource pre-payment processing on the at least one pending data in the data pool based on a resource pre-payment request; allocating transfer resources corresponding to the at least one pending data to the first data party for resource return processing of the pre-paid resources obtained from the resource pre-payment processing; the transfer resources are obtained by performing resource transfer processing on datasets with processing time limits using a merge processing method.

[0010] This specification provides one or more embodiments of another storage medium for storing computer-executable instructions that, when executed by a processor, implement the following process: synchronizing pending payment orders that perform service response actions to the corresponding merchant's order list; processing loan applications from the merchant for at least one item in the order list; and transferring payment funds obtained by merging the order set corresponding to the pending payment orders with combined payment periods to the merchant's merchant account for repayment of the loan funds obtained from the resource lending process. Attached Figure Description

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

[0012] Figure 1 A data processing method flowchart provided for one or more embodiments of this specification;

[0013] Figure 2 A flowchart illustrating a data processing method applied to an order processing scenario, provided for one or more embodiments of this specification;

[0014] Figure 3 A flowchart illustrating an order processing method provided in one or more embodiments of this specification;

[0015] Figure 4 A flowchart illustrating a data processing method applied in a lending scenario, provided for one or more embodiments of this specification;

[0016] Figure 5 A schematic diagram of a data processing apparatus provided for one or more embodiments of this specification;

[0017] Figure 6 A schematic diagram of an order processing apparatus provided for one or more embodiments of this specification;

[0018] Figure 7 This specification provides a schematic diagram of the structure of a data processing device according to one or more embodiments.

[0019] Figure 8 This is a schematic diagram of the structure of an order processing device provided for one or more embodiments of this specification. Detailed Implementation

[0020] To enable those skilled in the art to better understand the technical solutions in one or more embodiments of this specification, the technical solutions in one or more embodiments of this specification will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this specification, and not all of the embodiments. Based on one or more embodiments of this specification, all other embodiments obtained by those skilled in the art without creative effort should fall within the protection scope of this document.

[0021] This specification provides an example of a data processing method:

[0022] The data processing method provided in this application, after performing a pre-response action on the data to be processed, synchronizes the data to be processed to the corresponding data pool of the first data party, which serves as the basis for the first data party to subsequently apply for resource pre-allocation. Specifically, in the resource pre-allocation application process, the first data party can select at least one data to be processed from the data pool to submit a resource pre-allocation application. After the resource pre-allocation processing, the first data party can obtain the corresponding pre-allocated resources. After the first data party obtains the corresponding pre-allocated resources, the transfer resources obtained by performing resource transfer processing on the dataset to which the data to be processed belongs in a merged processing manner will be allocated to the first data party. The first data party can use this part of the transfer resources to return the pre-allocated resources, thereby forming a complete resource link of resource pre-allocation and resource return for the data to be processed. This improves the convenience of resource use for the first data party while satisfying the flexibility of resource transfer processing.

[0023] Step S102: Synchronize the pending data for which the pre-response action is to be performed to the data pool of the corresponding first data party.

[0024] The data to be processed in this embodiment includes data recording information about at least two data parties involved in the processing and the processing content performed by each data party. Additionally, the data to be processed may also record relevant information identifying the processing, such as submission time. The data to be processed in this embodiment includes orders to be processed. The data to be processed includes orders awaiting resource transfer; that is, data awaiting resource transfer. Correspondingly, subsequent data processing of the data awaiting resource transfer includes resource transfer processing. Optionally, the data to be processed includes order data of orders to be processed that are transferred through online and / or offline channels; wherein, the order data includes order data of orders to be processed with at least one data dimension. The orders to be processed with at least one data dimension refer to orders of different order types; for example, orders to be processed include catering orders, entertainment orders, and transportation orders; wherein catering, entertainment, and transportation are different data dimensions.

[0025] In this embodiment, the data to be processed includes at least two data parties: one data party submits the data to be processed, and the other data party responds to the data to be processed. For example, for an order to be processed, the data party submitting the order submits the order and the data party that executes the response action from the data party that submitted the order performs resource flow. The data party corresponding to the order executes the response action corresponding to the order. In this embodiment, the data party corresponding to the order, that is, the data party that executes the response action for the order, is the first data party; the data party submitting the order is the second data party.

[0026] In practical applications, after the data to be processed is submitted by the second data party and transferred to the first data party for resource transfer, the first data party performs a response action to the second data party based on the data to be processed. However, in this embodiment, the second data party submits the data to be processed first, and the first data party performs a response action to the second data party based on the data to be processed before processing the data. That is, the execution of the response action is placed before the data processing. Therefore, in this embodiment, executing the response action is also executing the pre-response action. The pre-response action refers to the response action of the data to be processed that is executed before the data processing of the data to be processed.

[0027] To enhance the first data party's awareness of the data party executing the response action as the data party to be processed, a data pool of the first data party stores the data to be processed by the data party executing the response action as the first data party. Optionally, the data pool of the first data party consists of target data from the processing period of at least one second data party's dataset; wherein, the target data includes the data to be processed by the first data party among the participants in the resource flow. In other words, the data pool of the first data party consists of the data to be processed by at least one second data party executing a pre-response action; wherein, the data to be processed in the data pool of the first data party includes the data to be processed by the first data party as the recipient of the resource flow.

[0028] In this embodiment, to enhance the awareness of the data party submitting the data to be processed regarding the data processing method provided in this embodiment, a response action for the data to be processed is executed before data processing is performed. That is, the data to be processed is "responded first and then processed." Since a response is required before data processing, and data processing requires resource transfer to the first data party, in order to avoid resource loss caused by the first data party responding to the data to be processed but not receiving the corresponding resources due to the second data party not transferring resources to the first data party, a verification process for the pre-response action of the data to be processed is performed before the pre-response action of the data to be processed. In this way, risk control is performed on the pre-response action of the data to be processed.

[0029] In practical implementation, to improve the effectiveness of verification during the verification process, verification of pre-response actions for the data to be processed can be performed based on the data platform's large amount of metadata, its ability to process large amounts of data, and its risk control capabilities. In one optional implementation of this embodiment, pre-response action verification of the data to be processed is performed in the following manner:

[0030] Determine metadata for at least one dimension, and evaluate the data of the second data party submitting the data to be processed based on the metadata for at least one dimension.

[0031] Based on the data to be processed and the evaluation level of the data party obtained from the data evaluation, the second data party and / or the data to be processed are verified.

[0032] Optionally, the metadata includes at least one of the following: application data of third-party applications connected to the data platform, and service data of data services accessing the data platform.

[0033] Specifically, during the verification process of the data to be processed in the pre-response action, based on the second data party identifier and data platform identifier contained in the data to be processed, the application data of the third-party application connected to the data platform, the service data of the data service accessing the data platform, and the historical processing data of the submitting data party on the data platform are determined. The application data, the service data, and the historical processing data are input into the data evaluation algorithm to evaluate the data submitted by the data party, and the evaluation level of the second data party is obtained. The data to be processed is then verified according to the verification method corresponding to the evaluation level to obtain the verification result.

[0034] The above-described verification process for performing pre-response actions on the data to be processed can also be replaced by determining at least one dimension of metadata, performing pre-response action verification on the data to be processed based on the at least one dimension of metadata, and forming a new implementation method with other processing steps provided in this embodiment; or, it can also be replaced by determining at least one dimension of metadata based on the data to be processed, performing pre-response action verification on the data to be processed based on the at least one dimension of metadata, and forming a new implementation method with other processing steps provided in this embodiment.

[0035] In addition to the above-mentioned verification processing method for pre-response actions on the data to be processed, another optional implementation provided in this embodiment can also use the following method to perform pre-response action verification processing on the data to be processed:

[0036] Determine the data flow distribution of the second data party submitting the data to be processed, and verify the second data party and / or the data to be processed according to the data flow distribution;

[0037] The data flow distribution is obtained by calculating the distribution of data flow values ​​among the data parties involved in the data flow processing based on the metadata of the data platform.

[0038] Specifically, based on the data platform identifier contained in the data to be processed, at least one dimension of metadata is determined. Based on the at least one dimension of metadata, the data flow distribution range of the data platform is determined. Then, based on the second data party identifier contained in the data to be processed, the corresponding data flow distribution of the second data party in the data flow distribution range is determined. The second data party and / or the data to be processed are verified according to the verification method corresponding to the data flow distribution to obtain the verification result.

[0039] It should be noted that the two verification processing methods provided above can be used for verification according to the actual configuration during the specific verification process, or the corresponding data can be input into the corresponding verification algorithm for verification. This embodiment does not limit this.

[0040] In one optional implementation of this embodiment, the data to be processed can also be verified using the following method:

[0041] The data party submitting the data to be processed is verified based on the data party identifier contained in the data to be processed, and / or, the amount of the data to be processed is verified based on the amount of resources to be transferred contained in the data to be processed. Optionally, the data party verification of the second data party includes verifying whether the second data party carries a pre-response restriction flag and / or whether the performance level of the data to be processed corresponding to the historical pre-response action of the second data party is a preset level; if yes, the verification is determined to have failed; if no, the verification is determined to have passed; the amount verification of the data to be processed based on the amount of resources to be transferred contained in the data to be processed includes: verifying whether the amount of resources to be transferred is greater than a preset threshold; if yes, the verification is determined to have failed; if no, the verification is determined to have passed.

[0042] After verifying the data to be processed using pre-response actions, if the verification passes, the processing confirmation information of the data to be processed is updated, and the pre-response actions for data processing are executed according to the confirmation instructions in the updated processing confirmation information; if the verification fails, it is determined that the data to be processed does not meet the permission for pre-execution of response actions, the data to be processed is processed, and the response actions for the data to be processed are executed after it is determined that the data processing is successful.

[0043] The processing confirmation information includes the actual amount of resource transfer confirmed for resource transfer; for example, if the amount of resources to be transferred for the pending order is m yuan, then m is the processing confirmation information before the update; optionally, the processing confirmation information includes the transfer value of resource transfer for the pending data; correspondingly, updating the processing confirmation information of the pending data includes: updating the transfer value of resource transfer for the pending data to 0. In order to realize the "use first, then use" processing of the pending data by the data submitter, the processing confirmation information of the pending data is updated to 0.

[0044] In this embodiment, after updating the processing confirmation information of the data to be processed, a pre-processing response action is executed based on the confirmation instruction of the updated processing confirmation information. In one optional implementation of this embodiment, the pre-processing response action is executed in the following manner:

[0045] Generate a processing completion label for the data to be processed;

[0046] Based on the processing completion label, perform the transfer processing of the target object corresponding to the data to be processed, or perform task processing of the processing task corresponding to the data to be processed.

[0047] Specifically, firstly, based on the confirmation instruction, a processing completion tag is generated for the data to be processed. Then, based on the processing completion tag, the target object corresponding to the data to be processed is transferred out, or the processing task corresponding to the data to be processed is executed. In addition, in some scenarios, during the pre-processing response action of the data to be processed, it is only necessary to generate the processing completion tag for the data to be processed.

[0048] In specific implementation, for the first data party, after the data to be processed by the first data party is confirmed, the data to be processed is synchronized to the first data party. If it is detected that the data to be processed by the first data party is the data to be processed that needs to perform a pre-response action, the data to be processed that needs to perform the pre-response action is synchronized to the data pool of the first data party.

[0049] Step S104: Based on the resource pre-allocation request for at least one piece of data to be processed in the data pool, perform resource pre-allocation processing for the at least one piece of data to be processed.

[0050] In this embodiment, since the first data party executes a response action for the data to be processed but does not receive the resources for that data, to avoid distrust of the preceding response action due to resource shortages, a resource pre-allocation permission for the data to be processed in the first data party's data pool is granted. This allows the first data party to pre-allocate resources for the data to be processed from the resource provider. After the first data party pre-allocates resources from the resource provider, and then obtains the data to be processed from the second data party (i.e., the second data party transfers the resources corresponding to the data to be processed to the first data party), the first data party returns the pre-allocated resources. Specifically, the first data party can pre-allocate resources for one piece of data to be processed or for multiple pieces of data to be processed in the data pool, which will not be elaborated further in this embodiment.

[0051] The resource prepayment request is a request submitted by the first data provider to prepay the resources corresponding to the data to be processed in the data pool. The resource prepayment processing is the resource prepayment action performed in response to the resource prepayment request.

[0052] In one optional implementation of this embodiment, the resource pre-allocation processing includes:

[0053] A resource advance request carrying resource information corresponding to at least one piece of data to be processed is submitted to the resource provider, so that the resource provider, after determining the resource advance amount based on the resource information, transfers resources to the first data provider according to the resource advance amount. Optionally, the resource information includes resource flow information of the data to be processed or the data to be processed itself; for example, the resource flow information includes the resource flow amount of the data to be processed, the amount of resources already flowed, and / or the remaining flow amount. The resource advance amount is the maximum amount of resources that the first data provider can advance. The first data provider can advance resources less than or equal to the resource advance amount. Correspondingly, if the target advance amount of the first data provider is less than the resource advance amount, resources are transferred to the first data provider according to the target advance amount.

[0054] Specifically, the first data provider submits a resource advance request to the resource provider, carrying resource information corresponding to at least one piece of data to be processed in the data pool; the resource provider determines the resource advance amount of the first data provider based on the resource information, and transfers the resources corresponding to the resource advance amount in the resource provider's resource account to the resource account of the first data provider.

[0055] Alternatively, the above-described resource advance processing procedure can be replaced by submitting a resource advance request carrying at least one piece of data to be processed to the resource provider, so that the resource provider, after determining the resource advance amount based on the at least one piece of data to be processed, transfers resources to the first data provider according to the resource advance amount.

[0056] Essentially, the first data provider uses the data to be processed in the data pool as collateral to pre-fund resources. During the pre-funding process for the first data provider, since the amount of resources used for processing the data to be processed is fixed, the amount of data processed by the second data provider will not exceed the amount of resources used for processing. To prevent the first data provider from using the amount of resources used for processing as collateral to pre-fund resources exceeding the amount of resources used for processing, thus causing resource losses to the resource provider, the resource provider determines the amount of resources pre-funded by the first data provider based on resource information. In one optional implementation of this embodiment, the amount of resources pre-funded is determined in the following way:

[0057] The resource prepayment amount is calculated based on the resource turnover amount corresponding to the data to be processed in the data pool;

[0058] or,

[0059] The resource prepayment amount is calculated based on the remaining circulation amount corresponding to the first data to be processed and the resource circulation amount corresponding to the second data to be processed in the data pool.

[0060] The first data to be processed includes data that has undergone resource pre-transfer, and the second data to be processed includes data that has not undergone resource pre-transfer.

[0061] Specifically, the amount of resource prepayment is determined based on the remaining transfer amount of at least one piece of data to be processed carried in the resource prepayment application. The remaining transfer amount of the data to be processed includes the resource transfer amount of the data to be processed or the remaining resource transfer amount after the second data party has prepaid a portion of the resource transfer amount.

[0062] In addition, step S104 can also be replaced by providing resource prepayment to the first data party according to the resource prepayment request for at least one data to be processed in the data pool, and forming a new implementation method with other processing steps provided in this embodiment.

[0063] Step S106: Allocate the transfer resources corresponding to the at least one data to be processed to the first data provider for resource return processing of the pre-funded resources obtained from the resource pre-funding process.

[0064] Optionally, the transferred resources are obtained by performing resource transfer processing on the dataset with the processing period in a merged processing manner.

[0065] In this embodiment, the circulation resources corresponding to the data to be processed include resources corresponding to the amount of circulation resources of the data to be processed or resources corresponding to the remaining amount of circulation resources.

[0066] In the specific implementation process, in order to improve the management effectiveness of the pending data of the second data party's execution pre-response actions, the pending data of the second data party's execution pre-response actions is managed through a dataset. In order to ensure the resource security of the first data party of each pending data in the dataset and to avoid resource loss of the first data party of each pending data due to the second data party's failure to process the pending data in the dataset for a long time, in this embodiment, the dataset is managed according to a cycle. The cycle can be a time interval in weeks, months, or longer. That is, a processing period is set for the dataset, and the dataset of each cycle is processed according to the cycle to ensure that the pending data in the dataset is processed at least at the end of the cycle.

[0067] After executing the pre-processing response action for the data to be processed, the data to be processed is written into the corresponding dataset according to the confirmation time of the data to be processed, and the data to be processed in the dataset is merged to obtain merged data. The dataset corresponding to the data to be processed includes the dataset of the time period in which the data time carried in the data to be processed is located; the merged data includes the merged amount obtained by summing the data amounts of all the data to be processed in the dataset.

[0068] In one optional implementation of this embodiment, the dataset corresponding to the data to be processed is determined in the following way:

[0069] Read the data time contained in the data to be processed, and determine the merging processing cycle in which the data time is located;

[0070] The dataset corresponding to the merge processing cycle is determined to be the dataset corresponding to the data to be processed.

[0071] In practice, after determining the dataset corresponding to the data to be processed, the data to be processed is written into the corresponding dataset, and the data to be processed in the dataset is merged based on the writing of the data to be processed in the dataset to obtain merged data.

[0072] Specifically, during the process of merging the data to be processed in the dataset to obtain the merged data, the amount of data in the data to be processed is added to the historical merge amount of the dataset to obtain the merged data. Optionally, the historical merge amount is calculated based on the historical data to be processed in the dataset.

[0073] After obtaining the merged data, the second data provider performs data processing based on the merged data, that is, performs resource transfer processing on the dataset within the processing period based on the merged processing method. Optionally, the resource transfer processing on the dataset within the processing period using the merged processing method is based on the merged data obtained by merging the data to be processed in the dataset within the processing period.

[0074] After obtaining the merged data, in addition to processing the data to be processed in the dataset at the end of the cycle, the merged data can also be preprocessed according to the preprocessing instructions of the second data party for the merged data of the dataset before the end of the cycle.

[0075] In other words, for merged data, that is, in the process of resource transfer processing of datasets with a processing deadline using the merged processing method, this embodiment provides two data processing methods: one is to preprocess the merged data before the processing deadline of the dataset, and the other is to process the merged data after the processing deadline of the dataset. Preprocessing the merged data before the processing deadline will result in a remaining transfer amount of data to be processed. The following will explain these two methods of processing merged data in detail.

[0076] In the first optional implementation provided in this embodiment, during the resource transfer processing of the dataset with a processing period using a merge processing method, the following operations are performed:

[0077] Based on the preprocessed data carrying the merged data detected before the expiration of the processing period, at least one of the datasets is pre-transferred according to the preprocessed data.

[0078] After the processing period expires, the remaining merged data is transferred out from the second data provider to perform a secondary resource transfer of the dataset.

[0079] Specifically, based on the preprocessed data, at least one of the datasets is processed using a preprocessing method according to the preprocessed data; based on the merged data and the preprocessed data, the remaining merged data of the dataset and the remaining transfer amount of each unprocessed data in the dataset are calculated; further, after the processing deadline is detected, if the remaining merged data is not 0, resources are transferred out from the second data party according to the remaining merged data, and based on the transferred resources, secondary resource transfer is performed on each unprocessed data according to the remaining transfer amount of each unprocessed data; if the remaining merged data is 0, no processing is required.

[0080] In this embodiment, the preprocessing method includes: a processing method for at least one resource account of the second data party configured by the second data party and / or a processing method for resource payment on behalf of a third party. In an optional implementation of this embodiment, during the preprocessing process according to the processing method corresponding to the resource account configured by the second data party, the resource transfer-out interface of the target resource account is called to transfer out the transfer-out resources corresponding to the preprocessed data, and the transfer-out data is transferred to the first data party corresponding to the preprocessed data.

[0081] Optionally, the third-party provider may make payments on behalf of the merged data if the second service provider completes the corresponding payment task or if certain conditions are met.

[0082] The following describes the processing procedure for the payment on behalf scenario in this embodiment.

[0083] (1) In one optional implementation of this embodiment, the merged data is processed in the following manner:

[0084] Call the secondary processing interface to generate secondary processed data corresponding to the preprocessed data;

[0085] If the secondary processing of the data is successful, resources are transferred out from the resource account corresponding to the secondary processing data and transferred into the second data account corresponding to the preprocessed data.

[0086] Specifically, the secondary processing interface is called to generate secondary processing data for the secondary processing object corresponding to the preprocessed data carrying the merged data; if the secondary processing data is successfully processed, at least one of the data is processed according to the preprocessed data based on the resource account corresponding to the secondary processing data; if the secondary processing data fails, the data is processed according to the preprocessed data based on the resource account of the first data party.

[0087] (2) In one optional implementation of this embodiment, the merged data is processed in the following manner:

[0088] Call the task generation interface to generate the processing task corresponding to the preprocessed data;

[0089] Resources are transferred out from the resource account of the task provider of the processing task to the second data provider corresponding to the preprocessed data.

[0090] Specifically, the task generation interface is called to generate a processing task for a task provider object corresponding to the preprocessed data. When the second data provider or the task provider object submits the completion result of the processing task by the second data provider, data processing is performed on at least one of the datasets according to the preprocessed data based on the resource account of the task provider object.

[0091] (3) In one optional implementation of this embodiment, the merged data is processed in the following manner:

[0092] If the dataset meets the resource donation conditions, call the resource donation interface to perform resource donation processing on the preprocessed data;

[0093] Data processing is performed on at least one of the data sets obtained from the resource donation process.

[0094] Specifically, after obtaining the merged data, based on the merged data and the data provider identifier of the second data provider, it is verified whether the merged data meets the donation conditions. If so, the data account of the data provider who donated the resources is identified as a third-party data account. According to the resource account of the data provider who donated the resources, at least one of the data sets is processed according to the preprocessed data.

[0095] During preprocessing, either the merged data or a portion of the merged data can be preprocessed. When preprocessing the merged data, after obtaining the resources to be transferred out, resources are transferred to the corresponding first data party according to the resource transfer amount for each piece of data to be processed in the dataset. If only a portion of the merged data is preprocessed, the data to be processed (resource transfer) according to the preprocessed data in the dataset and the determined transfer amount for the data to be processed are first determined. Then, resource transfer is performed on the determined data to be processed according to the transfer amount for the data to be processed.

[0096] In one optional implementation of this embodiment, the dataset is preprocessed in the following manner:

[0097] Calculate the allocated resource amount for each piece of data to be processed in the preprocessed data;

[0098] Based on the allocated resource amount for each data to be processed, data processing is performed on each data to be processed.

[0099] or,

[0100] Identify at least one piece of data in the dataset that needs to be processed based on the preprocessed data;

[0101] Based on the resource transfer amount of the preprocessed data and the preprocessed data, data processing is performed on the at least one piece of data to be processed.

[0102] Specifically, the preprocessed data is evenly or proportionally distributed to each data to be processed in the dataset, and data processing is performed on each data to be processed based on the allocated data; or, the data to be processed is sorted from first to last according to the data time of each data to be processed in the dataset to obtain a queue of data to be processed ordered by time, at least one data to be processed is determined in the queue of data to be processed based on the preprocessed data, and data processing is performed on at least one data to be processed.

[0103] To ensure the data security of the first data party corresponding to each piece of data to be processed in the dataset, and to avoid the first data party being unable to obtain the corresponding data for an extended period of time, the second optional implementation provided in this embodiment performs the following operations during the resource transfer processing of the dataset with a processing period using a merge processing method:

[0104] Upon detection that the processing period has expired, the merged data is transferred from the second data provider to the corresponding first data provider.

[0105] The above describes the execution process of transferring resources to merged data using a merge processing method;

[0106] In specific implementation, after the second data party corresponding to each piece of data to be processed processes the merged data corresponding to each piece of data to be processed, the circulation resources corresponding to each piece of data to be processed are allocated to the first data party; the first data party returns the pre-funded resources obtained from the resource pre-funding process based on the obtained circulation resources.

[0107] Optionally, allocating the transfer resources corresponding to the at least one piece of data to be processed to the first data provider includes: if it is detected that the second data provider corresponding to any piece of data to be processed transfers out the transfer resources corresponding to any piece of data to be processed in a merge processing manner, allocating the transfer resources to the first data provider. That is, the above step S106 can be replaced by: if it is detected that the second data provider corresponding to any piece of data to be processed transfers out the transfer resources corresponding to any piece of data to be processed in a merge processing manner, allocating the transfer resources to the first data provider, and forming a new implementation method with other processing steps provided in this embodiment.

[0108] In the specific execution process, after receiving the circulating resources corresponding to at least one piece of data to be processed, the first data provider performs resource return processing on the pre-funded resources obtained from the resource pre-funding process based on the circulating data corresponding to the at least one piece of data to be processed. In an optional implementation of this embodiment, the resource return processing includes: transferring the resources from the first data provider to the resource provider after the pre-funding period of the pre-funded resources expires.

[0109] The prepayment period includes a preset time after receiving the transfer resources corresponding to at least one piece of data to be processed. Alternatively, no prepayment period may be set; that is, the resource return process includes transferring resources from the first data provider to the resource provider that performed the resource prepayment process.

[0110] To further ensure the effectiveness of the first data party's return of pre-paid resources and prevent the first data party from using the received transfer resources for other transfers, thus making it impossible to return the pre-paid resources, at least one transfer resource corresponding to the pending data is allocated to the first data party and then frozen. After freezing, the transfer resource can only be used for the return of pre-paid resources. Based on this, in an optional implementation of this embodiment, the resources transferred out by the first data party include unfrozen resources obtained by unfreezing the transfer resources that are in a frozen state of the first data party; wherein, the unfrozen resources are obtained by freezing the corresponding resource transfer based on the merged data.

[0111] It should be noted that if there are multiple pieces of data to be processed, the first data provider can return the pre-allocated resources based on the flow resources of one piece of data after acquiring the flow resources for that one piece of data. Alternatively, the first data provider can return the pre-allocated resources based on the flow resources corresponding to multiple pieces of data after allocating them to the first data provider. That is, the first data provider can return the resources in parts or all at once during the resource return process, which is not limited in this embodiment.

[0112] In addition, step S106 can also be replaced by allocating the circulation resources corresponding to the at least one data to be processed to the first data party for resource return processing of the pre-funded resources obtained by the resource pre-funded processing, and forming a new implementation method with other processing steps provided in this embodiment. Alternatively, it can also be replaced by allocating the circulation resources corresponding to the at least one data to be processed to the first data party, and forming a new implementation method with other processing steps provided in this embodiment.

[0113] Alternatively, after the first data provider pre-allocates resources based on the data to be processed, if it detects that resources have been transferred to the dataset with the processing period through a merged processing method, the transferred resources are transferred to the resource provider corresponding to the resource pre-allocation processing; or, after continuously allocating the transferred resources to the first data provider, the pre-allocated resources obtained from the resource pre-allocation processing are returned; that is, step S106 can also be replaced by allocating the transferred resources corresponding to the at least one data to be processed to the resource provider corresponding to the resource pre-allocation processing, and forming a new implementation method with other processing steps provided in this embodiment; or, it can also be replaced by allocating the transferred resources corresponding to the at least one data to be processed to the first data provider, and returning the pre-allocated resources obtained from the resource pre-allocation processing.

[0114] In summary, the data processing method provided in this embodiment summarizes the pending data of the first data party in the execution of pre-response actions and grants the first data party resource pre-allocation permissions for the pending data in the execution of pre-response actions. This allows the first data party to pre-allocate resources using the pending data in the execution of pre-response actions as collateral, thus avoiding resource shortages for the first data party. Specifically, each time pending data in the execution of pre-response actions is acquired, the pending data is synchronized to the corresponding data pool of the first data party. If a resource pre-allocation request for target pending data in the data pool is detected from the first data party, the resource pre-allocation amount is determined based on the target pending data, and the first data party is processed according to the resource pre-allocation amount. The resources transferred from the second data party corresponding to the target pending data are allocated to the first data party for the return of pre-allocated resources. In this way, while ensuring the second data party's pre-response actions are perceived, the resource shortage of the first data party is avoided when it executes response actions but does not receive the transferred resources, which would further affect the first data party's trust in the pre-response actions.

[0115] The following description uses the application of a data processing method provided in this embodiment in an order processing scenario as an example to further illustrate the data processing method provided in this embodiment. (See also...) Figure 2 The data processing method applied to order processing scenarios includes the following steps.

[0116] Step S202: Obtain the data to be processed for executing the pre-response action.

[0117] Step S204: Synchronize the data to be processed to the data pool of the corresponding first data party.

[0118] Step S206: Based on the resource prepayment request from the first data party for at least one data to be processed in the data pool, determine the remaining transfer amount for each data to be processed.

[0119] Step S208: Calculate the resource prepayment amount for at least one piece of data to be processed based on the remaining circulation amount of each piece of data to be processed.

[0120] Optionally, the remaining transaction amounts of each piece of data to be processed can be summed to obtain the resource prepayment amount.

[0121] Step S210: Transfer the resources corresponding to the prepaid amount from the resource provider's resource account to the first service provider.

[0122] Step S212: If a transfer resource corresponding to any one of the pending data is detected, the transfer resource is allocated to the first service provider.

[0123] Step S214: Based on the first service provider's request to return the transferred resource, the transferred resource is allocated to the resource provider's resource account.

[0124] This specification provides an example of an order processing method:

[0125] The order processing method provided in this application, after performing a pre-response action on an order to be paid, synchronizes the order to be paid to the corresponding merchant's order list as the basis for the merchant to make subsequent loan applications. Specifically, during the loan application process, the merchant can select at least one order to be paid from the order list to submit a loan application. After the loan is processed, the merchant can obtain the corresponding loan funds. After the merchant obtains the corresponding loan funds, the payment funds obtained by processing the order set to which the order to be paid belongs in a merged processing manner will be allocated to the merchant. The merchant can use this part of the payment funds to repay the loan funds, thus forming a complete fund chain for the loan and repayment of orders to be paid. This improves the convenience of the merchant's use of funds while satisfying the flexibility of payment processing.

[0126] Step S302: Synchronize the pending payment orders that have performed service response actions to the corresponding merchant's order list.

[0127] The pending payment orders include orders that are paid for after a user confirms payment based on product or service information following a purchase of goods or service; the pending payment orders also include pending payment orders generated through online and / or offline channels.

[0128] Optionally, the pending payment order includes at least one of the following: a pending payment order generated by initiating payment through an online channel, a pending payment order generated by initiating payment through an offline channel, a pending payment order generated by making a payment call through a third-party application, or a pending payment order generated by making order payment through a subroutine.

[0129] In practical applications, after a pending payment order is generated and paid for, the merchant corresponding to the pending payment order needs to perform corresponding service response actions. For example, in e-commerce transactions, after a pending payment order for a target product is generated and the user pays for the pending payment order, the merchant needs to ship the goods to the user. Another example is in offline entertainment scenarios, where a user purchases tickets to an entertainment venue; after the pending payment order is paid for, the merchant grants access to the user. In both examples above, shipping the goods to the user and granting access to the user are the service response actions corresponding to the pending payment order.

[0130] In other words, the service response action includes the merchant or service provider corresponding to the order to be paid providing services to the user or transferring goods.

[0131] To improve merchants' awareness of pending orders from merchants who have performed response actions, a merchant's order list stores these pending orders. Optionally, the merchant's order list consists of target orders from at least one user's consolidated payment period order set; wherein, the target orders include pending orders from merchants whose order participants include the merchant. In other words, the merchant's order list consists of pending orders from at least one user who have performed pre-response actions; wherein, the pending orders in the merchant's order list include pending orders from merchants whose fund transfer recipients are the merchant.

[0132] In practice, due to the "respond first, pay later" principle, there are situations where users do not pay or pay insufficient amounts. Merchants may not receive the corresponding funds after already performing the service response action for the pending payment order, which can lead to distrust and negatively impact the merchant experience. To avoid financial losses to merchants due to non-payment or insufficient payments, it is necessary to verify users and / or pending payment orders during the "respond first, pay later" process for risk control.

[0133] In practical applications, data gaps or insufficient data can lead to ineffective risk control during the verification of users and / or pending payment orders. However, in this embodiment, verification of users and / or pending payment orders is based on a large amount of metadata and user service data, thereby improving the effectiveness of risk control for users and / or pending payment orders. Consequently, with more effective risk control for users and / or pending payment orders, the order amount for pending payment orders where users can respond first and then pay can be increased accordingly.

[0134] In practice, before synchronizing the pending payment orders that require service response actions to the corresponding merchant's order list for execution, the following steps are also included:

[0135] The users corresponding to the pending payment orders are rated based on user data;

[0136] Based on the user rating obtained from the rating process, pre-order access verification is performed on the pending payment orders and / or corresponding users;

[0137] The user data includes at least one of the following: application data of third-party applications connected to the data platform, and service data of data services accessed by the data platform.

[0138] Optionally, the pre-order response access verification refers to verifying whether the pending payment order and / or the corresponding user can perform a service response action on the user before the pending payment amount of the pending payment order is paid. In other words, performing pre-order response access verification on the pending payment order and / or the corresponding user includes: verifying whether the pending payment order and / or the corresponding user meet the access conditions for performing the service response action in advance; in advance means before the pending payment amount of the pending payment order is paid, or that is, verifying whether the pending payment order and / or the corresponding user meet the access conditions of "enjoy now, pay later".

[0139] Specifically, during the verification process of pending payment orders, based on the user identifier and data platform identifier contained in the pending payment order, the application data of the third-party applications connected to the data platform, the service data of the data services accessing the data platform, and the user's historical pending payment data on the data platform are determined. The application data, service data, and historical pending payment data are input into a data rating algorithm to assign a data rating to the user, obtaining the user's rating level. The pending payment order is then verified according to the verification method corresponding to the rating level to obtain the verification result. Optionally, historical pending payment data includes payment information for users' combined payment periods in the past.

[0140] In addition to the verification processing methods for pending payment orders and / or corresponding users provided above, another optional implementation method provided in this embodiment can also be used to verify pending payment orders in the following manner:

[0141] Based on the payment amount distribution of the users corresponding to the pending payment orders, pre-order access verification is performed on the pending payment orders and / or the corresponding users;

[0142] The payment amount distribution is obtained by calculating the distribution of payment amounts among users participating in the payment based on user data from the data platform.

[0143] Optionally, the payment amount distribution includes fund intervals divided according to different fund amounts; for example, [1, 1000], (1000, 5000], and (5000, 10000] are different payment amount distributions. In addition to the three provided payment amount distributions, upward increments are also possible. It should be noted that, to ensure the effectiveness of risk control, the amount division of the payment amount distribution can be configured based on needs. For example, for smaller amounts, the difference in the payment amount distribution can be appropriately reduced, such as using 1000 as the interval difference as mentioned above; for medium amounts, the payment amount distribution can be appropriately increased, such as using 4000 and 5000 as the interval difference as mentioned above; for higher amounts, the payment amount distribution can be determined using millions or hundreds of millions as the interval difference. In this embodiment, the user's payment amount distribution includes the fund intervals where all of the user's funds are located, or it includes the fund intervals where the user's paid amounts on the data platform are divided according to different fund amounts.

[0144] Specifically, the system reads the user's financial information and / or paid amount on the data platform based on the user's identifier, determines the distribution of payment amounts based on the application data and service data of the data platform, identifies the payment amount distribution that matches the financial information and / or paid amount in the payment amount distribution, and verifies the pending payment order and / or the corresponding user according to the verification method corresponding to the payment amount distribution to obtain the verification result.

[0145] It should be noted that the two verification processing methods provided above can be used for verification according to the actual configuration during the specific verification process, or the corresponding data can be input into the corresponding verification algorithm for verification. This embodiment does not limit this.

[0146] In addition, this embodiment also provides an optional implementation method in which the payment order can be verified in the following way:

[0147] The system reads the corresponding user's credit rating and verifies whether the credit rating meets the rating conditions before order response, and / or verifies whether the order payment amount of the pending order meets the amount access conditions before order response; if yes, the verification is deemed successful; if no, the verification is deemed unsuccessful. The rating conditions include a credit rating of a preset rating and / or an order payment amount (pending payment amount) less than a preset threshold.

[0148] If the verification passes, the payment processing amount for the order to be paid will be updated to 0; if the verification fails, no action will be taken.

[0149] The payment processing amount includes the actual amount of funds confirmed for payment; for example, if the amount to be paid for an order is m yuan, then m is the payment processing amount before the update; optionally, the payment processing amount includes the payment amount for the order to be paid; correspondingly, updating the payment processing amount of the order to be paid to 0 includes: updating the payment amount for the order to be paid to 0. To enable users to use their orders after payment, the payment processing amount of the order to be paid is updated to 0.

[0150] In this embodiment, after updating the payment processing amount of the pending payment order, a service response action for the pending payment order is executed based on the confirmation instruction of the updated processing confirmation information. In one optional implementation of this embodiment, the service response action is executed in the following manner:

[0151] Generate the pre-payment tag for the order to be paid;

[0152] Based on the pre-payment tag of the pending payment order, the goods corresponding to the pending payment order are shipped, or the payment service corresponding to the pending payment order is processed.

[0153] Specifically, during the execution of the service response action corresponding to the pending payment order, a pre-payment tag for the pending payment order is generated according to the confirmation instruction, and / or, based on the pre-payment tag of the pending payment order, the payment goods corresponding to the pending payment order are shipped or the payment service corresponding to the pending payment order is processed.

[0154] The system generates a pre-payment tag for the pending payment order based on the confirmation instruction and sends the pre-payment tag to the merchant so that the merchant can ship the payment goods corresponding to the payment order based on the pre-payment tag, or process the payment service corresponding to the pending payment order.

[0155] In the specific execution process, after the corresponding pending payment order of the merchant is confirmed, the pending payment order is synchronized with the merchant. If it is detected that the pending payment order of the merchant is a pending payment order with a payment processing amount of 0 and a pending payment order that has executed a service response action, then the pending payment order with a payment processing amount of 0 and a pending payment order that has executed a service response action is synchronized to the merchant's order list.

[0156] Step S304: Based on the loan application submitted by the merchant to at least one of the order list participants, process the loan application for at least one of the order list participants.

[0157] In this embodiment, since the merchant has executed a service response action for pending payment orders but has not received the corresponding funds, to avoid distrust of prematurely executed service response actions in the event of a merchant's cash shortage, a lending permission for pending payment orders is granted to the merchant. This allows the merchant to borrow funds from the funding provider based on these pending payment orders. After borrowing funds from the funding provider, and upon receiving payment processing for the corresponding user's pending payment order (i.e., after the user pays the merchant the funds corresponding to the pending payment order), the merchant repays the borrowed funds. Specifically, the merchant can borrow funds for one pending payment order or multiple pending payment orders in the order list during the lending process; this will not be elaborated further in this embodiment.

[0158] The loan application is a request submitted by the merchant to borrow funds corresponding to the pending orders in the order list. The loan processing is the loan action performed in response to the loan application.

[0159] In one optional implementation of this embodiment, the fund lending process includes:

[0160] A loan request carrying order information and account identifier is submitted to the target institution, so that the target institution, after determining the loan amount based on the order information, transfers the loan funds to the merchant account corresponding to the account identifier according to the loan amount. Optionally, the target institution includes a fund provider that provides the funds corresponding to the loan. The order information includes data such as the order identifier recorded in the pending payment order and / or the fund flow information corresponding to the pending payment order; for example, the fund flow information includes the pending payment amount, the paid amount, and / or the remaining pending payment amount of the pending payment order. The loan amount is the maximum amount of funds that the merchant can borrow, and the merchant can borrow funds less than or equal to the loan amount; correspondingly, if the target loan amount borrowed by the merchant is less than the loan amount, the loan funds are transferred to the merchant account corresponding to the account identifier according to the target loan amount.

[0161] Specifically, the merchant submits a loan request to the funding provider, which includes at least one pending order or order information and an account identifier from the order list. The funding provider determines the merchant's loan limit based on the funding information and transfers the funds corresponding to the loan limit from the funding provider's funding account to the merchant's funding account, that is, to the merchant's account corresponding to the account identifier.

[0162] Alternatively, the above process of fund lending processing can also be replaced by submitting a fund lending request carrying at least one pending payment order to the fund provider, so that after the fund provider determines the lending amount based on the at least one pending payment order, it transfers funds to the merchant according to the lending amount.

[0163] Equivalently, the merchant uses the pending payment orders in the order list as a guarantee for fund lending. During the process of fund lending processing for the merchant, since the pending payment amount of the pending payment order is fixed and the amount for the corresponding user's payment processing will not exceed the pending payment amount, in order to avoid the merchant using the pending payment amount of the pending payment order as a guarantee and being unable to repay after borrowing funds exceeding the pending payment amount, resulting in losses to the funds of the fund provider, the fund provider determines the merchant's lending amount based on the order information of the pending payment order; in an optional implementation manner provided in this embodiment, the lending amount is determined in the following manner:

[0164] Calculate the lending amount according to the pending payment amount of the pending payment orders in the order list;

[0165] Or,

[0166] Calculate the lending amount according to the remaining payment amount of the first pending payment order and the pending payment amount of the second pending payment order in the order list;

[0167] Among them, the first pending payment order includes a pending payment order with partial payment through prepayment, and the second pending payment order includes a pending payment order without prepayment.

[0168] Specifically, the lending amount is determined according to the remaining amount of at least one pending payment order carried in the lending application. The remaining amount of the pending payment order includes the pending payment amount of the pending payment order or the remaining pending payment amount after the corresponding user prepays a part of the resources for the pending payment amount.

[0169] For example, the merchant selects two pending payment orders in the order list. The pending payment amount of one pending payment order is m1, and the pending payment amount of the other pending payment order is m2. The combined information of the combined payment period corresponding to these two pending payment orders has not been prepaid, then calculate m1 + m2 = m as the merchant's lending amount.

[0170] For another example, the merchant selects two pending payment orders in the order list. The pending payment amount of pending payment order A1 is m1, and the pending payment amount of pending payment order A2 is m2. The combined information of the combined payment period corresponding to pending payment order A1 has been prepaid. In this case, pending payment order A1 has been prepaid m3 (m3 < m1). After obtaining the merchant's lending application for these two pending payment orders, calculate m1 - m3 + m2 = m4 as the merchant's lending amount.

[0171] In addition, step S304 can also be replaced by lending resources to the merchant according to the loan application of the merchant for at least one of the order list, and combining it with other processing steps provided in this embodiment to form a new implementation method.

[0172] Step S306: The payment funds obtained by merging the order set corresponding to the order to be paid for the combined payment period are transferred to the merchant's merchant account for the purpose of repaying the loan funds obtained from the resource lending process.

[0173] Optionally, the payment funds are obtained by consolidating the payment for the order set with the consolidated payment period using a consolidated payment method; the consolidated payment is based on the consolidation information obtained by merging the order to be paid and the related orders in the order set.

[0174] In this embodiment, the payment funds corresponding to the pending payment order include resources corresponding to the pending payment amount of the pending payment order or funds corresponding to the remaining pending payment amount.

[0175] To improve the effectiveness of managing users' pending payment orders, these orders are managed periodically. To ensure the financial security of merchants across all pending payment orders in the order set and prevent financial losses due to prolonged periods of non-payment by users, this embodiment manages pending payment orders periodically, on a weekly, monthly, or quarterly basis. This means setting a payment deadline for each order set and processing payments according to the cycle, ensuring that all pending payment orders are paid by the end of the cycle. Each defined cycle is a consolidated payment period. To enhance the convenience of managing pending payment orders within a consolidated payment period, these orders are managed through the order set of that consolidated payment period. The order set of a consolidated payment period consists of the pending payment orders within that period.

[0176] From the user's perspective, after executing the service response action for an order pending payment, the order is written into the corresponding order set based on its confirmation time. Then, the orders in the order set are merged to obtain merged information. The order set corresponding to the order pending payment includes the order set within the time period of the order time carried by the order. The merged information includes the merged amount obtained by summing the pending payment amounts of all the orders in the order set.

[0177] In practical implementation, to ensure the accuracy and validity of the determined consolidated payment period for orders to be paid, this embodiment provides an optional implementation method in which the consolidated payment period for orders to be paid is determined in the following way:

[0178] Read the order confirmation time contained in the order to be paid, and determine the corresponding consolidated payment period based on the order confirmation time.

[0179] Specifically, based on the order confirmation time contained in the order to be paid, the combined payment period corresponding to the time interval in which the order confirmation time is located is determined as the combined payment period corresponding to the order to be paid; that is, the combined payment period corresponding to the order to be paid is determined based on the order confirmation time contained in the order to be paid.

[0180] In practice, after determining the order set corresponding to the order to be paid, the order to be paid is written into the corresponding order set, and the order to be paid and the associated orders in the order set are merged to obtain merge information.

[0181] Specifically, during the process of merging the pending payment orders and related orders in the order set to obtain merge information, the pending payment amount in the pending payment orders is added to the historical merged amount in the order set to obtain the merged amount. Optionally, the historical merged amount is calculated based on the pending payment amount of related orders in the order set.

[0182] After obtaining the merged information, the user processes the payment based on the merged information, that is, processes the payment for the order set with merged payment periods based on the merged processing method. Optionally, the process of processing the payment for the order set with merged payment periods using the merged processing method is based on the merged information obtained by merging each order to be paid in the order set with merged payment periods.

[0183] After obtaining the merge information, in addition to processing the payment for the pending orders in the order set after the merge payment period expires, the merge information can also be prepaid according to the user's prepayment instruction for the merge information of the order set before the merge payment period expires.

[0184] In other words, for consolidated information, that is, in the process of processing payments for a set of orders with consolidated payment periods using a consolidated processing method, this embodiment provides two consolidated payment processing methods: one is to prepay the consolidated information before the end of the consolidated payment period, and the other is to process payments for the orders in the order set that are yet to be paid after the end of the consolidated payment period. Prepaying the consolidated information before the end of the consolidated payment period will result in remaining unpaid amounts and remaining consolidated information for the orders and the consolidated payment period. The following sections will explain these two payment methods for consolidated information in detail.

[0185] In the first optional implementation provided in this embodiment, during the payment processing of a set of orders with combined payment periods using a combined processing method, the following operations are performed:

[0186] Based on the prepayment request carrying merger information detected before the expiration of the merged payment period, the payment channel is invoked to process payment for at least one of the orders in the order set according to the prepayment amount carried in the prepayment request;

[0187] After the expiration of the consolidated payment period, a second payment will be made to the order set according to the remaining consolidated information and fund account.

[0188] The merged information is obtained by merging the pending orders and related orders in the order set; the remaining merged information is calculated based on the merged information and the pre-payment amount.

[0189] Specifically, based on prepayment requests carrying consolidation information detected before the expiration of the consolidated payment period, payment is processed for at least one of the order sets according to the target payment channel and prepayment amount carried in the prepayment request. The remaining consolidation information of the order set and the remaining unpaid amount for each order in the order set are calculated based on the consolidation information and the prepayment amount. After the expiration of the consolidated payment period is detected, if the remaining consolidation information of the order set is not 0, payment is processed based on the remaining consolidation information of the order set according to the user-configured list of funds accounts. If the remaining consolidation information of the order set is 0, no processing is performed. Optionally, during the process of processing payment based on the remaining consolidation information of the order set according to the user-configured list of funds accounts, payment is also processed for the corresponding unpaid orders according to the remaining unpaid amount of each unpaid order in the order set, based on the list of funds accounts.

[0190] In a specific implementation process, one optional implementation of this embodiment uses the following method to determine the apportionment amount of at least one of the orders in the order set during the payment processing according to the target payment channel and prepayment amount carried in the preprocessing request:

[0191] Based on the prepayment request, calculate the average amount of the prepayment amount allocated to each of the pending payment orders;

[0192] or,

[0193] Based on the prepayment request, calculate the ratio of the outstanding payment amount for each order to be paid;

[0194] Calculate the apportioned amount for each order pending payment based on the ratio of the amount to be paid and the amount of prepayment;

[0195] or,

[0196] Based on the payment request, the orders to be paid are sorted according to the order confirmation time to obtain an order queue;

[0197] The target order is determined in the order queue based on the prepayment amount, and the apportionment amount of each pending payment order is calculated according to the prepayment amount and the pending payment amount of the target order.

[0198] For example, if the merged information is M and the prepayment amount is m (m≤M), and if m=M, then payment is processed for each order in the order set according to the target fund account carried in the prepayment request; if m<M, the average amount of the prepayment amount allocated to each order in the order set is determined, and payment is processed for each order according to the target fund account corresponding to the average amount allocated to the order set. After payment processing, the remaining merged information for the merged payment period is M-m. After detecting the expiration of the merged payment period, if the remaining merged information M-m≠0, then the user-configured fund account list is read, and payment is processed for M-m according to the fund account with the first priority in the fund account list. If the account balance of the first priority fund account is insufficient to pay M-m, then payment is processed for M-m according to the fund account account with the second priority in the fund account list, and so on, until payment for M-m is successful. It should also be noted that if the account balance of all fund accounts in the fund account list is insufficient to pay M-m, then payment is processed for M-m based on multiple fund accounts in the fund account list.

[0199] In addition, when a portion is prepaid, the process of merging payments for the order set based on the merged payment period and merged information can be replaced by: determining the target orders in the order set for payment processing based on the prepayment amount in the prepayment request carrying merged information detected before the expiration of the merged payment period, and the order prepayment amount of each target order; processing the payment for each target order according to the order prepayment amount of each target order based on the target fund account carried in the prepayment request; optionally, it also includes: calculating the remaining merged amount of the merged payment period based on the merged information and the prepayment amount, and calculating the remaining amount of each pending payment order based on the order payment amount and the order prepayment amount of each pending payment order in the order set; if the expiration of the merged payment period is detected, processing the payment for each pending payment order according to the remaining amount of each pending payment order based on the fund account configured by the user.

[0200] It should be noted that during the prepayment process, users can select a target payment channel from the candidate payment channels. Optionally, the candidate payment channels include at least one of the following: a pre-configured first channel type fund account, a payment account bound to the payment channel to obtain channel payment rights, a third channel type fund account for executing channel tasks to perform payment processing, and a fourth channel type fund account for resource donation.

[0201] The following sections provide a detailed explanation of the process for prepaying the merged information using the four types of fund accounts mentioned above.

[0202] (1) Funds account of the first channel type

[0203] In one optional implementation of this embodiment, based on a prepayment request carrying consolidation information detected before the expiration of the consolidated payment period, a payment channel is invoked to process payment for at least one of the orders in the order set according to the prepayment amount carried in the prepayment request, including:

[0204] Based on the prepayment request obtained before the expiration of the consolidated payment period, funds are transferred out from the fund account corresponding to the target payment channel according to the prepayment amount carried in the prepayment request;

[0205] The prepayment amount will be paid based on the transferred funds.

[0206] Specifically, based on the fund account corresponding to the pre-configured fund account identifier carried in the prepayment request, the merged information is prepaid according to the prepayment amount.

[0207] (2) Funds accounts of the second channel type

[0208] In practical applications, some users open a fund account on a third-party account platform but do not bind the fund account to the data platform. Since the data platform provides various payment methods, in order to increase the usage rate of the fund account opened by the user, the third-party account platform may issue certain benefits to the user, so that the user will bind the fund account opened on the third-party account platform to the data platform and transfer funds based on the fund account opened on the third-party account platform during the payment processing through the data platform.

[0209] In one optional implementation of this embodiment, during the process of determining the user's payment channel list, the binding benefits opened by each third-party account platform can be read, and the third-party account platform and the opened binding benefits can also be included as part of the payment channel list.

[0210] For example, the card binding activity area on the list display page shows the bank cards or credit cards to be bound. It displays bank cards from the first account platform and credit cards from the second account platform. The display area for bank cards from the first account platform also shows the benefits that can be enjoyed when making payments based on the bank card, such as "30 off for purchases over 300". The display area for credit cards from the second account platform also shows the benefits that can be enjoyed when making payments based on the credit card, such as "20 off for purchases over 200".

[0211] Furthermore, users can link their bank cards or credit cards to process payments based on the linked funds account and corresponding payment rights.

[0212] In one optional implementation of this embodiment, the data platform processes payment for at least one of the orders in the order set according to the payment channel of the second channel type in the following manner:

[0213] Based on the fund account identifier of the second channel type carried in the preprocessing request, the channel payment rights associated with the fund account identifier are determined; the channel payment rights are associated with the user identifier and / or the fund account identifier after the binding relationship between the user identifier and the fund account identifier is established.

[0214] Based on the preprocessing amount carried in the preprocessing request and the channel payment rights, calculate the transfer amount of the fund account corresponding to the fund account identifier and the transfer amount of the rights of the account provider of the fund account.

[0215] The funds corresponding to the transfer amount are transferred out from the fund account, and the funds corresponding to the equity transfer amount are transferred out from the provider's fund account corresponding to the account provider;

[0216] The funds obtained from the fund transfer are used to make payment to at least one of the orders in the order set.

[0217] For example, the account provider and the data platform sign an agreement stipulating that after a user binds their funds account opened by the account provider to the data platform, the user will receive a 30 RMB discount for purchases over 300 RMB. When the user makes a payment for a combined amount of 400 RMB based on this funds account, the transfer amount from the funds account is calculated to be 370 RMB, and the transfer amount from the account provider is 30 RMB, based on the combined amount and the 30 RMB discount. The corresponding transfer amounts are then transferred from the funds account and the funds account of the account provider, respectively, and the funds obtained from the transfer are used to process payment for at least one of the orders in the combined amount order set.

[0218] Furthermore, the account provider can also agree with the data platform that the benefits are jointly provided by the account provider and the data platform; that is, of the 30 yuan discount for purchases over 300 yuan, the account provider and the data platform will each transfer a portion. Specifically, the method of processing payment for at least one of the orders when the account provider and the data platform jointly provide the benefits is similar to the method described above when the account provider provides the benefits, and can be referred to the above description. This embodiment will not be repeated here.

[0219] (3) Funds accounts of the third channel type

[0220] In practical applications, service providers connected to the data platform can, to improve their service efficiency, interact with the data platform to confirm that after a user completes their service request, the service provider will process the payment on behalf of the user's merged information. In specific implementation scenarios, the service provider can be a provider of goods or services; specifically, the service provider can set up payment processing on behalf of the user's merged information after the user purchases a specified product or a product of a specified amount from the service provider. Furthermore, if a service provider faces a shortage of staff due to high service demand, to supplement its manpower and ensure service efficiency, the service provider can set up payment processing on behalf of the user's merged information after the user provides the corresponding service.

[0221] Based on this, the channel tasks in this embodiment include purchasing goods or performing payment on behalf of others. It should be noted that whether a user has the authority to purchase goods or perform payment on behalf of others so that the service provider can process the payment on their behalf requires verification of the user and the merged information; specifically, it verifies whether the user and / or the order to be paid meets the payment access criteria of the service provider corresponding to the third-channel type of fund account. Optionally, the service provider's payment access criteria include: the merged information is less than the price of the specified goods or a preset percentage of the specified amount.

[0222] a. Purchase of goods

[0223] In one optional implementation of this embodiment, during the process of merging payment for an order set based on the merged payment period and merged information, the following operations are performed:

[0224] Based on the prepayment request obtained before the expiration of the consolidated payment period, a recommended order corresponding to the prepayment amount carried in the prepayment request is generated;

[0225] If the recommended order is successfully paid, funds will be transferred from the corresponding fund account to pay the pre-payment amount.

[0226] Specifically, if the target payment channel of the prepayment request obtained before the expiration of the consolidated payment period is the payment channel of the consumer payment service provider, a recommended order of the service provider will be generated. If the recommended order is successfully paid, the service provider's funds account will be transferred out to process the prepayment data carried by the prepayment request.

[0227] Optionally, the product and / or service information in the recommended order can be configured by the service provider or submitted by the user.

[0228] b. Service Provision

[0229] In one optional implementation of this embodiment, during the process of merging payment for an order set based on the merged payment period and merged information, the following operations are performed:

[0230] Based on the prepayment request obtained before the expiration of the consolidated payment period, a payment task corresponding to the prepayment amount carried by the prepayment request is created;

[0231] Funds are transferred from the payment provider's account to pay the prepayment amount.

[0232] Specifically, if the target payment channel of the prepayment request obtained before the expiration of the consolidated payment period is the payment channel of the service provider that handles the payment, then a payment task is created for the service provider. When the user completes the payment task, funds are transferred from the service provider's funds account to process the prepayment data carried in the prepayment request.

[0233] For example, after a user selects a service provider to pay on their behalf and a second service provider to pay the merged information, the user needs to perform a pre-set work service with the second service provider. After the work is completed, the second service provider can then process the payment for the merged information.

[0234] Optionally, the task information in the service task can be configured by the service provider or selected and submitted by the user. Furthermore, the prepayment amount can also be determined based on the service time selected by the user.

[0235] (4) Funds accounts of the fourth channel type

[0236] In practical applications, there are situations where users participate in public welfare services or meet the eligibility criteria for public welfare services. In such cases, if the user's combined information is less than the eligibility threshold for payment through the public welfare service, the public welfare service can process the payment on behalf of the user's combined information.

[0237] In one optional implementation of this embodiment, during the process of merging payment for an order set based on the merged payment period and merged information, the following operations are performed:

[0238] If the order set meets the conditions for fund donation, the fund donation interface is called to process the fund donation of the prepayment request;

[0239] The prepayment amount is paid using the donated funds obtained through the donation process.

[0240] Specifically, a prepayment request carrying merged information is obtained. If the target payment channel carried in the prepayment request is a payment channel for public welfare services, the funds for the prepayment amount are transferred out based on the public welfare service's fund account, and payment processing is performed on at least one of the order sets based on the transferred funds.

[0241] The process of prepaying for merged information through the different payment channels mentioned above can be referred to each other, and will not be repeated here in this embodiment.

[0242] To ensure the data security of merchants corresponding to each pending payment order in the order set, and to prevent merchants from being unable to access funds for their respective pending payment orders for extended periods, the second optional implementation provided in this embodiment performs the following operations during the payment processing of the order set with merged payment periods using a merged processing method:

[0243] Upon detection that the combined payment period has expired, payment processing is performed on the order set according to the combined information and at least one user account;

[0244] The user account includes the funds account in the funds account queue configured by the user who submitted the order to be paid for in relation to the merged information.

[0245] In practice, after each user in at least one pending payment order processes the payment for the combined information corresponding to each pending payment order, the payment funds corresponding to each pending payment order are transferred to the merchant; the merchant then uses the obtained payment funds to repay the loan funds obtained from the loan processing.

[0246] Optionally, the step of transferring the payment funds corresponding to the at least one pending payment order to the merchant includes: if it is detected that a user corresponding to any pending payment order in the at least one pending payment order transfers the payment funds corresponding to any pending payment order out in a merged processing manner, the payment funds are transferred to the merchant.

[0247] In the specific execution process, after receiving payment funds corresponding to at least one pending payment order, the merchant performs fund repayment processing on the loan funds obtained from the fund lending process based on the flow data corresponding to at least one pending payment order. In an optional implementation of this embodiment, the fund repayment processing includes: transferring funds from the merchant's account to the target institution after the loan term of the loan funds expires.

[0248] The loan period includes a preset timeframe after receiving payment funds for at least one pending order. Alternatively, no loan period may be set; that is, the fund repayment process includes transferring funds from the merchant to the target institution for the loan processing.

[0249] To further ensure the effectiveness of merchants' repayment of loan funds and prevent merchants from using received payment funds for other purposes, thus making it impossible to repay loan funds, payment funds corresponding to at least one pending payment order are transferred to the merchant and then frozen. After freezing, the payment funds can only be used for the repayment of loan funds. Based on this, in an optional implementation of this embodiment, the funds transferred from the merchant's account include payment funds obtained by unfreezing payment funds in the merchant's account; wherein, the payment funds in the frozen state are obtained by merging and paying the payment funds transferred to the merchant's account for at least one user's combined payment period and then freezing them.

[0250] It should be noted that if there are multiple pending orders, after receiving payment funds for one pending order, the merchant can either return the loan funds based on those single payment funds, or return the loan funds based on payment funds for multiple pending orders after all such payments have been transferred to the merchant. In other words, the merchant can return funds in installments or in a lump sum during the return process; this embodiment does not impose any limitations on this.

[0251] In addition, step S306 can also be replaced by transferring the payment funds obtained by merging the order set corresponding to the order to be paid for to the merchant's merchant account, which together with other processing steps provided in this embodiment forms a new implementation method.

[0252] In addition, the payment funds obtained from the consolidated payment of the order set corresponding to the pending payment order are directly used to repay the loan funds; that is, step S306 can also be replaced by transferring the payment funds obtained from the consolidated payment of the order set corresponding to the pending payment order to the target institution corresponding to the loan processing, and forming a new implementation method with other processing steps provided in this embodiment; or, it can also be replaced by transferring the payment funds obtained from the consolidated payment of the order set corresponding to the pending payment order to the merchant's superior account, and repaying the loan funds obtained from the resource loan processing, and forming a new implementation method with other processing steps provided in this embodiment. In this embodiment, step S306 can also be replaced by transferring the payment funds obtained from the payment processing of the pending payment order to the merchant's merchant account, and forming a new implementation method with other processing steps provided in this embodiment; optionally, the payment processing of the pending payment order includes consolidating the payment of the order set corresponding to the pending payment order, or making a single payment for the pending payment order.

[0253] In summary, the order processing method provided in this embodiment aggregates the pending payment orders of merchants who have performed service response actions and grants merchants the authority to lend funds for these pending payment orders. This allows merchants to use the pending payment orders with performed service response actions as collateral for lending, preventing merchants from experiencing fund shortages when users "enjoy first and then pay later." Specifically, each pending payment order with a performed service response action is synchronized to the corresponding merchant's order set. If a merchant's lending application for a target pending payment order in the order set is detected, the lending amount is determined based on the target pending payment order, and the amount is allocated according to the merchant's preference for orders less than or equal to the target pending payment order. The system processes loans to merchants based on the target loan amount. It transfers the payment funds obtained by users from processing target pending orders to the merchant for loan repayment. This ensures users receive advance notice of service response while preventing merchants from experiencing financial losses due to not receiving payment, thus protecting their trust in early service responses. In other words, while offering users "enjoy now, pay later" options, the system provides merchants with loan access to orders already enjoyed (pending payment), allowing them priority access to corresponding payment funds.

[0254] The following uses the application of an order processing method provided in this embodiment in a lending scenario as an example to further illustrate the data processing method provided in this embodiment. See [link to relevant documentation]. Figure 4 The data processing method applied to lending scenarios includes the following steps.

[0255] Step S402: Obtain the pending payment order for the execution of the service response action.

[0256] Step S404: Synchronize the orders to be paid to the corresponding merchant's order list.

[0257] Step S406: Determine the remaining unpaid funds for each unpaid order based on the merchant's loan application for at least one unpaid order in the order list.

[0258] Step S408: Calculate the loan amount for at least one pending payment order based on the remaining pending payment funds for each pending payment order.

[0259] Step S410: Based on the merchant's target lending amount, which is less than or equal to the loan amount, transfer the funds corresponding to the target lending amount from the target institution to the merchant's account.

[0260] Step S412: If payment funds corresponding to any pending payment order in the pending payment order corresponding to the target loan funds are detected, the payment funds are transferred to the merchant's merchant account.

[0261] Step S414: Transfer the payment funds corresponding to any pending order in the merchant's account to the target institution.

[0262] The following is an embodiment of a data processing device provided in this specification:

[0263] In the above embodiments, a data processing method is provided, and correspondingly, a data processing device is also provided, which will be described below with reference to the accompanying drawings.

[0264] Reference Figure 5 The diagram shows a data processing apparatus provided in this embodiment.

[0265] Since the apparatus embodiments correspond to the method embodiments, the descriptions are relatively simple. For relevant parts, please refer to the corresponding descriptions of the method embodiments provided above. The apparatus embodiments described below are merely illustrative.

[0266] This embodiment provides a data processing apparatus, including:

[0267] The data synchronization module 502 is configured to synchronize the pending data that performs the pre-response action to the data pool of the corresponding first data party;

[0268] Resource pre-allocation processing module 504 is configured to perform resource pre-allocation processing on at least one pending data in the data pool based on a resource pre-allocation request for at least one pending data.

[0269] The resource allocation module 506 is configured to allocate the circulating resources corresponding to the at least one data to be processed to the first data party for resource return processing of the pre-funded resources obtained by the resource pre-funded processing; the circulating resources are obtained by performing resource circulating processing on the dataset with the processing period in a merged processing manner.

[0270] This specification provides an example of an order processing device as follows:

[0271] In the above embodiments, another order processing method is provided, and correspondingly, another order processing device is also provided, which will be described below with reference to the accompanying drawings.

[0272] Reference Figure 6 The diagram shows a schematic of an order processing device provided in this embodiment.

[0273] Since the apparatus embodiments correspond to the method embodiments, the descriptions are relatively simple. For relevant parts, please refer to the corresponding descriptions of the method embodiments provided above. The apparatus embodiments described below are merely illustrative.

[0274] This embodiment provides an order processing device, including:

[0275] The order synchronization module 602 is configured to synchronize pending payment orders that have performed service response actions to the corresponding merchant's order list;

[0276] The fund lending processing module 604 is configured to perform fund lending processing for at least one of the order list based on the merchant's loan application for at least one of the order list.

[0277] The funds transfer module 606 is configured to transfer the payment funds obtained by merging the order set corresponding to the order to be paid to the merchant's account, so as to repay the loan funds obtained by the resource lending process.

[0278] The following is an embodiment of a data processing device provided in this specification:

[0279] Corresponding to the data processing method described above, based on the same technical concept, one or more embodiments of this specification also provide a data processing apparatus for performing the data processing method provided above. Figure 7 This is a schematic diagram of the structure of a data processing device provided for one or more embodiments of this specification.

[0280] This embodiment provides a data processing device, including:

[0281] like Figure 7As shown, data processing devices can vary considerably due to differences in configuration or performance. They may include one or more processors 701 and memory 702, with memory 702 storing one or more application programs or data. Memory 702 can be temporary or persistent storage. The application programs stored in memory 702 may include one or more modules (not shown), each module including a series of computer-executable instructions from the data processing device. Furthermore, processor 701 may be configured to communicate with memory 702, executing the series of computer-executable instructions stored in memory 702 on the data processing device. The data processing device may also include one or more power supplies 703, one or more wired or wireless network interfaces 704, one or more input / output interfaces 705, one or more keyboards 706, etc.

[0282] In one specific embodiment, the data processing device includes a memory and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer-executable instructions for the data processing device, and is configured to be executed by one or more processors. The one or more programs include computer-executable instructions for performing the following:

[0283] The pending data for executing the pre-response action will be synchronized to the data pool of the corresponding first data party;

[0284] Based on the resource advance request for at least one piece of data to be processed in the data pool, the resource advance processing for the at least one piece of data to be processed is performed.

[0285] The transfer resources corresponding to the at least one data to be processed are allocated to the first data party for resource return processing of the pre-funded resources obtained from the resource pre-funding process; the transfer resources are obtained by performing resource transfer processing on the dataset with the processing period in a merged processing manner.

[0286] The following is an example of an order processing device provided in this specification:

[0287] Corresponding to the order processing method described above, based on the same technical concept, one or more embodiments of this specification also provide an order processing device for executing the order processing method provided above. Figure 8 This is a schematic diagram of another order processing device provided in one or more embodiments of this specification.

[0288] This embodiment provides an order processing device, including:

[0289] like Figure 8 As shown, order processing devices can vary significantly due to differences in configuration or performance. They may include one or more processors 801 and a memory 802, where one or more applications or orders may be stored. The memory 802 can be temporary or persistent storage. The applications stored in the memory 802 may include one or more modules (not shown), each module including a series of computer-executable instructions within the order processing device. Furthermore, the processor 801 may be configured to communicate with the memory 802, executing the series of computer-executable instructions stored in the memory 802 on the order processing device. The order processing device may also include one or more power supplies 803, one or more wired or wireless network interfaces 804, one or more input / output interfaces 805, one or more keyboards 806, etc.

[0290] In one specific embodiment, the order processing device includes a memory and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer-executable instructions for the order processing device, and is configured to be executed by one or more processors. The one or more programs include computer-executable instructions for performing the following:

[0291] The pending payment orders that have completed the service response action will be synchronized to the corresponding merchant's order list;

[0292] Based on the loan application submitted by the merchant for at least one of the orders in the order list, process the loan application for at least one of the orders in the order list.

[0293] The payment funds obtained by merging the order set corresponding to the pending payment order into a single payment period are transferred to the merchant's merchant account for repayment of the loan funds obtained from the resource lending process.

[0294] This specification provides an example of a storage medium as follows:

[0295] Corresponding to the data processing method described above, and based on the same technical concept, one or more embodiments of this specification also provide a storage medium.

[0296] The storage medium provided in this embodiment is used to store computer-executable instructions, which, when executed by a processor, implement the following process:

[0297] The pending data for executing the pre-response action will be synchronized to the data pool of the corresponding first data party;

[0298] Based on the resource advance request for at least one piece of data to be processed in the data pool, the resource advance processing for the at least one piece of data to be processed is performed.

[0299] The transfer resources corresponding to the at least one data to be processed are allocated to the first data party for resource return processing of the pre-funded resources obtained from the resource pre-funding process; the transfer resources are obtained by performing resource transfer processing on the dataset with the processing period in a merged processing manner.

[0300] It should be noted that the embodiments of a storage medium and the embodiments of a data processing method in this specification are based on the same inventive concept. Therefore, the specific implementation of this embodiment can be referred to the implementation of the corresponding method described above, and the repeated parts will not be described again.

[0301] Another embodiment of the storage medium provided in this specification is as follows:

[0302] Corresponding to the order processing method described above, based on the same technical concept, one or more embodiments of this specification also provide another storage medium.

[0303] The storage medium provided in this embodiment is used to store computer-executable instructions, which, when executed by a processor, implement the following process:

[0304] The pending payment orders that have completed the service response action will be synchronized to the corresponding merchant's order list;

[0305] Based on the loan application submitted by the merchant for at least one of the orders in the order list, process the loan application for at least one of the orders in the order list.

[0306] The payment funds obtained by merging the order set corresponding to the pending payment order into a single payment period are transferred to the merchant's merchant account for repayment of the loan funds obtained from the resource lending process.

[0307] It should be noted that the embodiment of another storage medium in this specification and the embodiment of an order processing method in this specification are based on the same inventive concept. Therefore, the specific implementation of this embodiment can be referred to the implementation of the corresponding method described above, and the repeated parts will not be described again.

[0308] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.

[0309] In the 1930s, improvements to a technology could be clearly distinguished as either hardware improvements (e.g., improvements to the circuit structure of diodes, transistors, switches, etc.) or software improvements (improvements to the methodology). However, with technological advancements, many improvements to the methodology today can be considered direct improvements to the hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved methodology into the hardware circuit. Therefore, it cannot be said that an improvement to the methodology cannot be implemented using a hardware physical module. For example, a Programmable Logic Device (PLD) (e.g., a Field Programmable Gate Array (FPGA)) is such an integrated circuit whose logic function is determined by the user programming the device. Designers can program a digital system themselves to "integrate" it onto a PLD, without needing chip manufacturers to design and manufacture dedicated integrated circuit chips. Furthermore, nowadays, instead of manually manufacturing integrated circuit chips, this programming is mostly implemented using "logic compiler" software. Similar to the software compiler used in program development, the original code before compilation must be written in a specific programming language, called a Hardware Description Language (HDL). There are many HDLs, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, and RHDL (Ruby Hardware Description Language). Currently, the most commonly used are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should understand that by simply performing some logic programming on the method flow using one of these hardware description languages ​​and programming it into an integrated circuit, the hardware circuit implementing the logical method flow can be easily obtained.

[0310] The controller can be implemented in any suitable manner. For example, it can take the form of a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro)processor, logic gates, switches, application-specific integrated circuits (ASICs), programmable logic controllers, and embedded microcontrollers. Examples of controllers include, but are not limited to, the following microcontrollers: ARC625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicon Labs C8051F320. A memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art will also recognize that, in addition to implementing the controller in purely computer-readable program code form, the same functionality can be achieved by logically programming the method steps to make the controller take the form of logic gates, switches, ASICs, programmable logic controllers, and embedded microcontrollers. Therefore, such a controller can be considered a hardware component, and the means included therein for implementing various functions can also be considered as structures within the hardware component. Alternatively, the means for implementing various functions can be considered as both software modules implementing the method and structures within the hardware component.

[0311] The systems, devices, modules, or units described in the above embodiments can be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, a computer can be, for example, a personal computer, laptop computer, cellular phone, camera phone, smartphone, personal digital assistant, media player, navigation device, email device, game console, tablet computer, wearable device, or any combination of these devices.

[0312] For ease of description, the above apparatus is described by dividing it into various functional units. Of course, when implementing the embodiments of this specification, the functions of each unit can be implemented in one or more software and / or hardware.

[0313] Those skilled in the art will understand that one or more embodiments of this specification can be provided as a method, system, or computer program product. Therefore, one or more embodiments of this specification may take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this specification may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0314] This specification is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this specification. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create a machine for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0315] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0316] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0317] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0318] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0319] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0320] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0321] One or more embodiments of this specification can be described in the general context of computer-executable instructions, such as program modules, that are executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform a particular task or implement a particular abstract data type. One or more embodiments of this specification can also be practiced in distributed computing environments where tasks are performed by remote processing devices connected via a communication network. In distributed computing environments, program modules can reside in local and remote computer storage media, including storage devices.

[0322] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the system embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions in the method embodiments.

[0323] The above description is merely an embodiment of this document and is not intended to limit the scope of this document. Various modifications and variations can be made to this document by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this document should be included within the scope of the claims of this document.

Claims

1. A data processing method, comprising: Based on the data platform identifier contained in the data to be processed, at least one dimension of metadata is determined. Based on the metadata, the data flow distribution range of the data platform is determined. Based on the second data party identifier contained in the data to be processed, the data flow distribution of the second data party in the data flow distribution range is determined. The data to be processed is verified according to the verification method corresponding to the data flow distribution. If the verification is successful, the pre-processing action of the data to be processed is executed according to the confirmation instruction of the updated processing confirmation information of the data to be processed, and the data to be processed that has executed the pre-processing action is synchronized to the data pool of the corresponding first data party. Based on the resource advance request from the first data party for at least one data to be processed in the data pool, the resource advance processing for the at least one data to be processed is performed. The resource prepayment amount of the first data party is calculated based on the remaining circulation amount corresponding to the first data to be processed in the data pool and the resource circulation amount corresponding to the second data to be processed. Read the data time contained in the data to be processed, determine the merging processing cycle in which the data time is located, write the data to be processed into the dataset of the merging processing cycle, and merge the data of each data to be processed in the dataset to obtain merged data. Allocate the transferred resources obtained by processing the dataset based on the merged data to the first data party for resource return processing of the pre-funded resources obtained by the resource pre-funded processing.

2. The data processing method according to claim 1, wherein the resource pre-allocation processing includes: A resource advance request carrying resource information corresponding to at least one piece of data to be processed is submitted to the resource provider, so that the resource provider, after determining the resource advance amount based on the resource information, transfers resources to the first data provider according to the resource advance amount.

3. The data processing method according to claim 2, wherein the first data to be processed includes data to be processed that has undergone resource pre-transfer, and the second data to be processed includes data to be processed that has not undergone resource pre-transfer.

4. The data processing method according to claim 2, wherein the resource return processing includes: After the pre-payment period for the pre-paid resources expires, the resources are transferred from the first data provider to the resource provider.

5. The data processing method according to claim 4, wherein the resources transferred out by the first data party include unfrozen resources obtained by unfreezing the circulating resources of the first data party that are in a frozen state; in, The unfrozen resources are obtained by freezing the corresponding resource transfer based on the merged data.

6. The data processing method according to claim 1, wherein the data pool of the first data party consists of target data in the data set of at least one second data party with a processing period; in, The target data includes the data to be processed by the participants in the resource flow, including the data from the first data provider.

7. The data processing method according to claim 1, wherein allocating the transferred resources obtained by performing resource transfer processing on the dataset based on the merged data to the first data provider includes: Upon detection that the merging process period has expired, resources are transferred from the second data provider to the corresponding first data provider for the dataset according to the merged data.

8. The data processing method according to claim 1, wherein the step of performing resource transfer processing on the dataset based on the merged data includes: Based on the preprocessed data carrying the merged data detected before the expiration of the merged processing cycle, at least one of the datasets is pre-transferred according to the preprocessed data. After the merging process cycle is detected to be over, the remaining merged data is transferred out from the second data provider to perform a secondary resource transfer of the dataset.

9. The data processing method according to claim 1, wherein the pre-response action is performed in the following manner: Generate a processing completion label for the data to be processed; Based on the processing completion label, perform the transfer processing of the target object corresponding to the data to be processed, or perform task processing of the processing task corresponding to the data to be processed.

10. The data processing method according to claim 1, wherein the data to be processed includes orders to be paid, and the orders to be paid include at least one of the following: order data of orders to be processed that are transferred through online channels and / or offline channels; in, The order data includes order data for orders to be processed in at least one data dimension.

11. An order processing method, comprising: The user's financial information on the data platform is read based on the user identifier, and the distribution of payment amounts is determined based on the application data and service data of the data platform. The payment amount distribution that the financial information matches in the payment amount distribution is determined, and the payment order is verified according to the verification method corresponding to the payment amount distribution. If the verification is successful, the service response action for the pending payment order will be executed according to the confirmation instruction for the payment processing amount of the updated pending payment order, and the pending payment order for which the service response action has been executed will be synchronized to the order list of the corresponding merchant. Based on the loan application submitted by the merchant to at least one of the orders in the order list, the merchant's loan amount is processed for at least one of the orders in the order list; the merchant's loan amount is calculated based on the remaining payment amount of the first pending payment order and the pending payment amount of the second pending payment order in the order list. The system reads the order confirmation time of the order to be paid and determines the corresponding consolidated payment period based on the order confirmation time. The order to be paid is written into the order set of the consolidated payment period. The system performs a consolidation process on each order to be paid in the order set to obtain consolidation information. The payment funds obtained by the user through consolidation payment of the order set of the consolidated payment period based on the consolidation information are transferred to the merchant's merchant account for repayment of the loan funds obtained from the loan processing.

12. The order processing method according to claim 11, wherein the order list consists of target orders from a set of orders with combined payment periods for at least one user; in, The target order includes unpaid orders in which the merchant is a participating party.

13. The order processing method according to claim 11, wherein the fund lending process includes: Submit a loan request to the target institution, carrying order information and account identifier, so that the target institution, after determining the loan amount based on the order information, transfers the loan funds to the merchant account corresponding to the account identifier according to the loan amount.

14. The order processing method according to claim 13, wherein the first pending payment order includes pending payment orders that have been partially paid through prepayment, and the second pending payment order includes pending payment orders that have not been prepaid.

15. The order processing method according to claim 13, wherein the fund return processing includes: After the loan term expires, the funds are transferred from the merchant's account to the target institution.

16. The order processing method according to claim 15, wherein the funds transferred from the merchant account include payment funds obtained by unfreezing payment funds that are frozen in the merchant account; in, The frozen payment funds are obtained by merging and paying the payment funds transferred to the merchant's account for the combined payment period of at least one user's order set and then freezing them.

17. The order processing method according to claim 11, wherein the consolidated payment is implemented in the following manner: Upon detection that the combined payment period has expired, payment processing is performed on the order set according to the combined information and at least one user account; in, The user account includes the funds account in the funds account queue configured for the merged information by the user who submitted the order to be paid.

18. The order processing method according to claim 11, wherein the consolidated payment is implemented in the following manner: Based on the prepayment request carrying merger information detected before the expiration of the merged payment period, the payment channel is invoked to process payment for at least one of the orders in the order set according to the prepayment amount carried in the prepayment request; After the expiration of the consolidated payment period, a second payment will be made to the order set according to the remaining consolidated information and fund account.

19. The order processing method according to claim 11, wherein the order to be paid comprises at least one of the following: Orders pending payment can be generated through online payment channels, offline payment channels, third-party applications, or subroutines.

20. A data processing apparatus, comprising: The data synchronization module is configured to determine at least one dimension of metadata based on the data platform identifier contained in the data to be processed, determine the data flow distribution range of the data platform based on the metadata, determine the data flow distribution of the second data party in the data flow distribution range based on the second data party identifier contained in the data to be processed, and perform verification processing on the data to be processed according to the verification method corresponding to the data flow distribution. If the verification is successful, the pre-processing action of the data to be processed is executed according to the confirmation instruction of the updated processing confirmation information of the data to be processed, and the data to be processed that has executed the pre-processing action is synchronized to the data pool of the corresponding first data party. The resource pre-allocation processing module is configured to perform resource pre-allocation processing on the at least one data to be processed based on the resource pre-allocation request from the first data party for at least one data to be processed in the data pool. The resource prepayment amount of the first data party is calculated based on the remaining circulation amount corresponding to the first data to be processed in the data pool and the resource circulation amount corresponding to the second data to be processed. The resource allocation module is configured to read the data time contained in the at least one data to be processed, determine the merging processing cycle in which the data time is located, write the at least one data to be processed into the dataset of the merging processing cycle, merge the data to be processed in the dataset to obtain merged data, and allocate the transferred resources obtained by performing resource transfer processing on the dataset based on the merged data to the first data party for resource return processing on the pre-funded resources obtained by the resource pre-funded processing.

21. An order processing apparatus, comprising: The order synchronization module is configured to read the user's financial information on the data platform based on the user identifier and determine the payment amount distribution based on the application data and service data of the data platform, determine the payment amount distribution that the financial information matches in the payment amount distribution, and verify the payment order according to the verification method corresponding to the payment amount distribution. If the verification is successful, the service response action for the pending payment order will be executed according to the confirmation instruction for the payment processing amount of the updated pending payment order, and the pending payment order for which the service response action has been executed will be synchronized to the order list of the corresponding merchant. The fund lending processing module is configured to process fund lending for at least one of the orders in the order list based on the merchant's loan application for at least one of the orders in the order list; the merchant's loan limit is calculated based on the remaining payment amount of the first pending payment order and the pending payment amount of the second pending payment order in the order list; The funds transfer module is configured to read the order confirmation time of at least one of the orders in the order list, determine the corresponding consolidated payment period based on the order confirmation time, write at least one of the orders in the order list into the order set of the consolidated payment period, perform consolidation processing on each order to be paid in the order set to obtain consolidation information, and transfer the payment funds obtained by the user to the order set of the consolidated payment period based on the consolidation information to the merchant's merchant account for use in repaying the loan funds obtained from the fund lending processing.

22. A computer processing device, comprising: processor; And a memory configured to store computer-executable instructions, which, when executed, cause the processor to implement the data processing method of any one of claims 1 to 10 or the order processing method of any one of claims 11 to 19.

23. A storage medium for storing computer-executable instructions, which, when executed by a processor, implement the data processing method of any one of claims 1 to 10 or the order processing method of any one of claims 11 to 19.

Images