Transaction settlement method, device and equipment, storage medium and computer program product

Abstract

The invention relates to a transaction settlement method, device and equipment, a storage medium and a computer program product. The method comprises the steps of obtaining transaction data of a target object, wherein the transaction data at least comprises a transaction resource amount and an object identifier of the target object; querying a settlement strategy configured for the target object according to the object identifier; determining a target settlement mode matched with the target object according to the settlement mode corresponding to each piece of settlement information based on the settlement information under each settlement dimension in the settlement strategy; and according to the target settlement mode, executing settlement processing for the transaction resource amount to obtain a settlement result of the transaction data. The method can improve the flexibility of transaction settlement.

Description

Technical Field

[0001] This application relates to the field of data processing technology, and in particular to a method, apparatus, device, storage medium, and computer program product for transaction settlement. Background Technology

[0002] With the development of network technology, payment platforms provide transaction processing, fund clearing, and settlement services for merchants, users, and financial institutions. The settlement systems deployed through payment platforms typically employ hard-coded rules, meaning the platform aggregates transaction data at fixed intervals, generates settlement lists based on this data, and then completes resource exchange with merchants through batch payments. However, the widespread adoption of mobile payment and real-time settlement technologies has significantly increased merchants' demands for flexibility. Furthermore, considering the diverse and complex settlement needs of different merchants, the flexibility of aggregating transaction data at fixed intervals is limited. Therefore, ensuring flexibility during transaction settlement remains a pressing issue that needs to be addressed. Summary of the Invention

[0003] Therefore, it is necessary to provide a method, apparatus, device, storage medium, and computer program product for transaction settlement that enhances the flexibility of transaction settlement in response to the aforementioned technical problems.

[0004] Firstly, this application provides a method for transaction settlement. The method includes:

[0005] Obtain the transaction data of the target object. The transaction data shall include at least the amount of transaction resources and the object identifier of the target object.

[0006] Query the settlement strategy configured for the target object based on the object identifier;

[0007] Based on the settlement information under each settlement dimension in the settlement strategy, and according to the settlement method corresponding to each settlement information, the target settlement mode matching the target object is determined.

[0008] According to the target settlement model, settlement processing is performed on the amount of transaction resources to obtain the settlement result of the transaction data.

[0009] Secondly, this application also provides a transaction settlement device. The device includes:

[0010] The data acquisition module is used to acquire the transaction data of the target object. The transaction data includes at least the amount of transaction resources and the object identifier of the target object.

[0011] The strategy query module is used to query the settlement strategy configured for the target object based on the object identifier;

[0012] The settlement mode determination module is used to determine the target settlement mode that matches the target object based on the settlement information under each settlement dimension in the settlement strategy and the settlement method corresponding to each settlement information.

[0013] The settlement processing module is used to perform settlement processing on the amount of transaction resources according to the target settlement mode, and obtain the settlement result of the transaction data.

[0014] Thirdly, this application also provides a computer device. The computer device includes a memory and a processor, the memory storing a computer program, and the processor executing the computer program to perform the following steps:

[0015] Obtain the transaction data of the target object. The transaction data shall include at least the amount of transaction resources and the object identifier of the target object.

[0016] Query the settlement strategy configured for the target object based on the object identifier;

[0017] Based on the settlement information under each settlement dimension in the settlement strategy, and according to the settlement method corresponding to each settlement information, the target settlement mode matching the target object is determined.

[0018] According to the target settlement model, settlement processing is performed on the amount of transaction resources to obtain the settlement result of the transaction data.

[0019] Fourthly, this application also provides a computer-readable storage medium. The computer-readable storage medium stores a computer program thereon, which, when executed by a processor, performs the following steps:

[0020] Obtain the transaction data of the target object. The transaction data shall include at least the amount of transaction resources and the object identifier of the target object.

[0021] Query the settlement strategy configured for the target object based on the object identifier;

[0022] Based on the settlement information under each settlement dimension in the settlement strategy, and according to the settlement method corresponding to each settlement information, the target settlement mode matching the target object is determined.

[0023] According to the target settlement model, settlement processing is performed on the amount of transaction resources to obtain the settlement result of the transaction data.

[0024] Fifthly, this application also provides a computer program product. The computer program product includes a computer program that, when executed by a processor, performs the following steps:

[0025] Obtain the transaction data of the target object. The transaction data shall include at least the amount of transaction resources and the object identifier of the target object.

[0026] Query the settlement strategy configured for the target object based on the object identifier;

[0027] Based on the settlement information under each settlement dimension in the settlement strategy, and according to the settlement method corresponding to each settlement information, the target settlement mode matching the target object is determined.

[0028] According to the target settlement model, settlement processing is performed on the amount of transaction resources to obtain the settlement result of the transaction data.

[0029] The aforementioned transaction settlement method, apparatus, computer equipment, storage medium, and computer program product first acquire the transaction data of the target object. Since the transaction data includes at least the transaction resource amount and the object identifier of the target object, the settlement strategy configured for the target object is queried according to the object identifier. Then, based on the settlement information under each settlement dimension in the settlement strategy, the target settlement mode matching the target object is determined according to the settlement method corresponding to each settlement information. Finally, the settlement processing for the transaction resource amount is executed according to the target settlement mode to obtain the settlement result of the transaction data. This transaction settlement method allows for different configurations of the settlement strategy according to the needs of different objects. That is, the settlement information for each settlement dimension of different objects is flexibly determined based on the object's needs. By querying the settlement strategy through the object identifier in the target object's transaction data, determining the target settlement mode for the target object according to the settlement strategy configured for the target object, and then executing the settlement processing for the transaction resource amount according to the target settlement mode, the method adapts to the personalized settlement needs of the target object, avoiding the poor scalability problem caused by fixed settlement modes, and meeting the diversified and complex settlement needs of different objects, thereby improving the flexibility of transaction settlement. Attached Figure Description

[0030] Figure 1 This is a diagram illustrating the application environment of a transaction settlement method in one embodiment.

[0031] Figure 2 This is a system logic architecture diagram of a transaction settlement system in one embodiment;

[0032] Figure 3 This is a schematic diagram illustrating the correspondence between settlement strategies and settlement methods constituting a settlement model in one embodiment;

[0033] Figure 4 This is a schematic diagram of the transaction settlement and resource interaction process in one embodiment;

[0034] Figure 5 This is a schematic diagram of the information entry interface for entering settlement contracts in one embodiment.

[0035] Figure 6 This is a flowchart illustrating a transaction settlement method in one embodiment;

[0036] Figure 7 This is a schematic diagram of the process of completing transaction settlement through the settlement strategy management stage, transaction stage, data collection stage, settlement stage and resource interaction stage in one embodiment;

[0037] Figure 8 This is a flowchart illustrating the process of obtaining the settlement result of transaction data in one embodiment;

[0038] Figure 9 This is a schematic diagram illustrating the billing strategy implementation logic of a billing method in one embodiment;

[0039] Figure 10 This is a schematic diagram of the interface showing the abnormal information that caused the verification to fail in one embodiment.

[0040] Figure 11 This is a schematic diagram of the interface for handling abnormal information in one embodiment.

[0041] Figure 12 This is a complete flowchart of a transaction settlement method in one embodiment;

[0042] Figure 13 This is a structural block diagram of a transaction settlement device in one embodiment;

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

[0044] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0045] With the development of network technology, payment platforms can provide transaction processing, fund clearing, and settlement services for merchants, users, and financial institutions. The settlement systems deployed through payment platforms typically employ hard-coded rules, meaning the platform aggregates transaction data at fixed intervals, generates settlement lists based on this data, and then completes resource interaction with merchants through batch payments. Alternatively, reconciliation and settlement centers can be pre-built for different merchants, with each center handling transaction settlement independently. However, the widespread adoption of mobile payment and real-time settlement technologies has significantly increased merchants' demands for efficiency and flexibility. Furthermore, considering the diverse and complex settlement needs of different merchants, the flexibility of aggregating transaction data at fixed intervals is limited. Handling transaction settlement separately for different merchants through reconciliation and settlement centers results in high system development and maintenance costs, poor scalability, and reduced transaction processing flexibility. Therefore, ensuring flexibility during transaction settlement remains a pressing issue that needs to be addressed.

[0046] Based on this, and to address the aforementioned technical problems, embodiments of this application provide a transaction settlement method that enhances the flexibility of transaction settlement. The transaction settlement method provided in these embodiments can be applied to, for example... Figure 1 In the application environment shown, terminal 102 communicates with server 104 via a network. A data storage system can store the data that server 104 needs to process. The data storage system can be integrated onto server 104, or it can be located in the cloud or on another server.

[0047] Specifically, taking server 104 as an example, server 104 first obtains the transaction data of the target object. The transaction data includes at least the transaction resource amount and the object identifier of the target object. Then, server 104 queries the settlement strategy configured for the target object according to the object identifier, and determines the target settlement mode matching the target object based on the settlement information under each settlement dimension in the settlement strategy and the settlement method corresponding to each settlement information. Then, according to the target settlement mode, settlement processing for the transaction resource amount is executed to obtain the settlement result of the transaction data. By configuring the settlement strategy differently according to the needs of different objects, that is, the settlement information of different objects under each settlement dimension is flexibly determined based on the object's needs, the settlement strategy is queried through the object identifier in the target object's transaction data. The target settlement mode is determined according to the settlement strategy configured for the target object, and then settlement processing for the transaction resource amount is executed according to the target settlement mode. Since the target settlement mode can adapt to the personalized settlement needs of the target object, it avoids the poor scalability problem caused by a fixed settlement mode and meets the diversified and complex settlement needs of different objects, thereby improving the flexibility of transaction settlement.

[0048] The terminal 102 can be, but is not limited to, various desktop computers, laptops, smartphones, tablets, IoT devices, portable wearable devices, and transaction payment devices. IoT devices can include smart speakers, smart TVs, smart air conditioners, and smart in-vehicle devices. Portable wearable devices can include smartwatches, smart bracelets, and head-mounted devices. The server 104 can be implemented using a standalone server or a server cluster consisting of multiple servers. The transaction settlement method provided in this embodiment can be applied to various scenarios, including but not limited to e-commerce platform transaction settlement, retail transaction settlement, and financial and payment institution transaction settlement, where transaction settlement needs to be conducted based on a transaction platform.

[0049] The following describes different scenarios for transaction settlement based on trading platforms: In e-commerce platform transaction settlement and retail transaction settlement scenarios, the transaction settlement method provided in this application embodiment can support complex settlement rules between payment platforms, merchants, and distributors, such as proportional profit sharing, tiered fees, T+1 settlement, etc., or it can also support real-time settlement of commissions for social e-commerce transactions. In the scenario of transaction settlement between financial and payment institutions, the transaction settlement method provided in this application embodiment can support aggregated payment clearing, supply chain finance settlement, etc. Aggregated payment clearing provides third-party payment platforms with multi-channel clearing capabilities, that is, the same merchant performs transaction calculations on different payment platforms according to different settlement strategies. Supply chain finance settlement is based on targeted resource interaction and direct connection with the bank system to ensure compliance. It should be understood that since the transaction settlement method provided in this application embodiment can be applied to scenarios that require transaction settlement based on trading platforms, the above scenario descriptions should not be construed as specific limitations on the applicable scenarios of this application embodiment.

[0050] The following will introduce the relevant technical concepts involved in the transaction settlement method in the embodiments of this application:

[0051] Payment Platform: The payment platform is a central system connecting merchants, consumers, and financial institutions, providing transaction processing, fund clearing, and settlement services. The transaction settlement method provided in this embodiment is specifically executed on the payment platform.

[0052] Merchants: Merchants are entities that sell goods or provide services through payment platforms. Merchants can be e-commerce sellers or offline stores, etc. Merchants need to open a settlement account in the transaction settlement system to separate it from their own funds.

[0053] Consumers: In this embodiment, consumers are those who purchase goods or services from merchants.

[0054] Settlement Cycle: The settlement cycle is the rule for settling relevant transaction resources to merchants after a preset time limit following the occurrence of a transaction. Settlement cycles include, but are not limited to: T+1, D+1, or S0. T+1 is a settlement cycle in which settlement is carried out on the next business day following the transaction date. D+1 is a settlement cycle in which settlement is carried out on the next natural day following the transaction date. S0 is a settlement cycle in which settlement is carried out in near real-time.

[0055] Billing method: The billing method refers to how to calculate the corresponding handling fee for a transaction order, and how to obtain the platform's fee and the merchant's settlement payment. Billing methods include, but are not limited to: fixed amount, percentage, annual tiered percentage calculation, and monthly tiered percentage calculation.

[0056] Message queues: Message queues are an asynchronous communication mechanism used to decouple interactions between system components, achieving efficient and reliable data transmission through storing and forwarding messages. Message queues can be used to transmit payment results to the settlement module, achieving asynchronous decoupling between order status updates and fund transfers.

[0057] Channel orders: When the transaction chain involves external transaction institutions (such as UnionPay or external transaction gateways), the external channel will provide the transaction data order for the previous billing period on the next natural day, or on the next business day. That is, the transaction data in this application embodiment includes the transaction data order provided by the channel order.

[0058] Reconciliation and Error Handling: Considering the existence of external channel orders, discrepancies may arise between channel orders and internally generated transaction data due to system anomalies, order time deviations, and daily cutoff points. These discrepancies may stem from mismatches in key factors (such as inconsistent amounts) between the internal system and the external channel. In such cases, system reconciliation is necessary to identify and address these differences.

[0059] Strategy Pattern: The strategy pattern is a behavioral design pattern that encapsulates algorithms into independent classes in a transaction settlement system, making them dynamically replaceable and avoiding hard-coded conditional branches. For example, in this embodiment, different merchants need to support T+0 real-time settlement, T+1 next-day settlement, or custom period settlement. In this case, the strategy pattern can be used to encapsulate the settlement colors corresponding to different settlement periods, and then the settlement strategy will be switched and matched according to the pre-configured settlement strategy with the merchant during transaction settlement.

[0060] Based on this, such as Figure 2The system logic architecture diagram of the transaction settlement system shown illustrates that, from the perspective of the transaction dimensions required for settlement, different driving modes can exist, including internal transaction-driven and external transaction-driven modes. This means that in practical applications, there can be transaction data generated internally and transaction data corresponding to external orders. Aggregation modes can also differ, such as batch aggregation or single-transaction aggregation. Settlement cycles can also vary, such as T+1, D+1, or S0 as mentioned in the previous examples. Billing methods can also differ, such as fixed amount, percentage, annual tiered percentage, and monthly tiered percentage as mentioned in the previous examples. Furthermore, different resource interaction methods can exist in practical applications, such as object transfers to object account balances and object withdrawals to object bank accounts. Therefore, settlement information can be selected under different settlement dimensions. By combining different settlement information, a fixed settlement mode can be avoided, thus meeting the transaction settlement needs of various objects.

[0061] From the perspective of transaction settlement implementation, transaction settlement actually requires the support of the transaction settlement function of the transaction settlement system. The transaction settlement process is to match the settlement information under each settlement dimension of each merchant's settlement strategy with the settlement mode and the strategy mode in the program. This allows the transaction settlement system to dynamically use the sub-modes under different settlement dimensions in the settlement mode, so as to facilitate the expansion of system functions and maintenance.

[0062] For ease of understanding, such as Figure 3 The diagram illustrates the correspondence between settlement strategies and the settlement methods that constitute the settlement model. Each merchant can configure a settlement strategy, meaning the settlement strategy table can include the settlement strategy matched to each merchant. Each settlement strategy contains multiple settlement dimensions, namely the aggregation mode, billing method, and settlement cycle described earlier. Settlement information under different settlement dimensions corresponds to a settlement information number, and different settlement information numbers point to the settlement method corresponding to the settlement information under that settlement dimension. That is, as shown... Figure 3 As shown, the billing method number can be found in the billing method table to find the billing method corresponding to the billing method number, while the settlement cycle number can be found in the settlement cycle table to find the settlement cycle corresponding to the settlement cycle number.

[0063] For example, aggregation modes include batch aggregation and single-transaction aggregation. Batch aggregation has a settlement information number of A1 under aggregation mode, while single-transaction aggregation has a settlement information number of A2. If a merchant's settlement strategy uses A2 for aggregation mode, it indicates that the merchant requires single-transaction aggregation. Similarly, billing methods include fixed amount, percentage, annual tiered percentage, and monthly tiered percentage. The settlement information number for fixed amount under this calculation method could be B1, for percentage it could be B2, for annual tiered percentage it could be B3, and for monthly tiered percentage it could be B4. If a merchant's settlement strategy uses B1 for billing method, it indicates that the merchant requires fixed amount billing. Similarly, the settlement cycle includes T+1, D+1 and S0. The settlement information number under the settlement cycle for T+1 can be C1, the settlement information number under the settlement cycle for D+1 can be C2, and the settlement information number under the settlement cycle for S0 can be C3. If the settlement information number under the settlement cycle in the merchant's settlement strategy is C2, it means that the settlement cycle required by the merchant is D+1.

[0064] The correspondence between the settlement strategy and the settlement methods constituting the settlement mode provided in this embodiment enables the transaction settlement system to have very high scalability. This means that settlement information under different settlement dimensions can be matched to the needs of different merchants, allowing for free combination of settlement methods within the settlement mode matched to each merchant. It is understood that if a new settlement dimension is identified, or new settlement information is identified under a settlement dimension, information can be added and relationships updated based on the correspondence described in the foregoing embodiment. A detailed settlement information number can be assigned to the new settlement information, and then the settlement information number can be associated with the merchant's settlement strategy to ensure that all associated settlement information can be identified through the merchant's settlement strategy.

[0065] The transaction settlement process described in this embodiment is as follows: Figure 4 The flowchart illustrating transaction settlement and resource interaction is shown below. Figure 4 The flowchart shown includes the settlement contract management stage, transaction stage, data collection stage, billing stage, data verification stage, aggregation stage, clearing stage, and resource interaction stage. Each stage is described below:

[0066] Settlement Contract Management Stage: The settlement contract management stage includes at least three process phases: offline negotiation, settlement contract entry, and settlement contract activation. During the offline negotiation phase, payment platform operators need to negotiate settlement contracts with merchants who need to sign contracts, communicate the cooperation model for the required settlement contracts, and determine the settlement information under each settlement dimension. In other words, the settlement information for each merchant under each settlement dimension needs to be determined during the contract signing stage. Based on this, during the settlement contract entry stage, payment platform operators need to enter the settlement contract information for the merchants signing contracts into the payment platform system. This essentially involves entering the merchant's settlement information under each settlement dimension into the payment platform system and matching this information with the merchant's unique identifier, which can be uniquely identified by the merchant's account information in the payment platform system. The specific interface for operators to enter settlement contract information for merchants signing contracts in the payment platform system is shown below. Figure 5 As shown, Figure 5 The information entry interface shown only displays settlement dimensions such as settlement period, settlement start point, and billing method. For the settlement period dimension, multiple settlement options are displayed, such as N+1, N+2, N+3, etc. However, in actual applications, transaction settlement dimensions can also include, but are not limited to, aggregation mode and resource interaction method. Therefore, Figure 5 The information entry interface shown is only for understanding how to enter settlement contracts, and should not be construed as a specific limitation on the information that can be entered.

[0067] Once the settlement contract is entered, it becomes effective. This means the settlement contract for that merchant is valid and modifiable within its validity period. In other words, the merchant's settlement information for each settlement dimension can be modified based on actual needs. At this point, the payment platform system can store settlement information for the merchant under different settlement dimensions, including settlement cycle, resource interaction method, aggregation mode, daily cutoff point, billing method, and fee rate. This settlement information will serve as part of the input source for subsequent transaction settlement processes, allowing the program to select the appropriate strategy mode based on the settlement information.

[0068] Transaction Stage: The transaction stage includes at least several process phases, such as order placement, system order placement, consumer payment, payment processing, result notification, and channel order provision. Order placement typically occurs between the consumer, merchant, and payment platform. This means the consumer initiates an order by selecting the corresponding goods or services from a merchant on any online transaction system, or by adding the goods or services to their shopping cart. After the consumer initiates an order, the merchant's backend system stores the ordered goods or services information and calculates the corresponding transaction fees to generate a transaction order. The order information then instructs the consumer to place the order on the payment platform. During the consumer's payment phase, the consumer verifies the goods or services information and the corresponding transaction fees for the selected goods or services to complete the payment. Based on this, in the payment processing phase, after the consumer completes payment, the payment platform responds to and processes the consumer's payment request. Upon successful processing, the transaction resource amount is deducted from the consumer's relevant account and temporarily stored on the platform. Therefore, during the result notification phase, the payment platform notifies the merchant to deliver goods or provide corresponding services to the consumer based on the consumer's payment result. The payment system also notifies the transaction settlement system in this embodiment that a transaction has been generated and needs to be settled. It is understandable that in some transaction scenarios, the transaction chain involves external transaction institutions (such as UnionPay or external transaction gateways), and these external channels also need to provide all transaction orders within a specific period (such as D+1 or T+1). Transaction orders provided through external channels can also be used by the transaction settlement system for transaction settlement.

[0069] Data Acquisition Phase: The data acquisition phase includes at least the transaction acquisition and order processing stages. During the transaction acquisition phase, the data acquisition program in the transaction settlement system runs continuously to ensure that all transaction orders generated within the payment system are collected without duplication or omission. These transaction orders include, but are not limited to, e-commerce transaction orders and utility payment orders. The data acquisition program also interfaces with all external transaction institutions, meaning it can connect to the respective external order program interfaces (APIs) of each channel. In this stage, the data acquisition program downloads orders for the corresponding dates from external transaction institutions and parses the external transaction orders provided by these institutions to verify their data format. Therefore, in the order processing stage, it is necessary to consider that the data structure of transaction orders provided by external channels may differ from that of transaction orders generated directly through the payment system. In other words, transaction orders from external channels and those generated by the payment system are heterogeneous data sources. Therefore, when the data formats of external transaction orders differ, format conversion is required, and the converted external transaction orders are stored in the standard data structure within the transaction settlement system.

[0070] Billing Phase: The billing phase includes at least the processes of acquiring billing information and calculating fees. In the acquiring phase, the billing program needs to query the merchant's corresponding settlement contract based on the merchant's identifier in the transaction order. As mentioned earlier, in the settlement contract management phase, the transaction settlement system can store the merchant's settlement information for each settlement dimension, including the billing method. Therefore, by using the settlement information for the billing method (such as percentage, fixed amount, or tiered billing) in the merchant's corresponding settlement contract, the merchant's billing information (i.e., the billing method) can be determined. Based on this, in the fee calculation phase, according to the billing method and the transaction resource amount in the transaction order, the platform's billing resource amount (i.e., the platform handling fee charged by the transaction platform) and the interactive resource amount (the merchant's actual settlement amount) are calculated, thereby generating a billing statement (i.e., the billing result). This billing result clearly identifies the actual transaction amount, the platform handling fee charged by the transaction platform, and the merchant's actual settlement amount in a single transaction.

[0071] Data verification phase: The data verification phase includes at least the data verification, error recording, and error handling stages, and is typically only performed in transaction settlement scenarios involving external orders. During the data verification phase, billing results generated from internally generated transaction orders originating from external channels are compared bilaterally with the external channel transaction orders to ensure order matching. Therefore, during the error recording stage, if a one-sided order (i.e., only the payment platform's order or an external channel's order exists) or if key transaction order data is inconsistent, the data verification program will save the corresponding error record and display it on the relevant interface of the transaction settlement system. In the event of an error, the reconciliation discrepancy needs to be addressed promptly during the error handling stage. This involves confirming the cause of the anomaly through the error record (e.g., abnormal order number, abnormal amount, and type of discrepancy), and ultimately determining the appropriate handling method matching the cause of the anomaly. For example, calling a backend interface to cancel the corresponding erroneous order, or initiating a refund for the erroneous order to return the transaction amount to the consumer's payment account.

[0072] The aggregation phase follows the billing phase. That is, after a billing invoice is generated during the billing phase, its status is "Pending Aggregation." As mentioned earlier, for transaction settlement scenarios involving external orders, a data verification phase is required, and the aggregation phase only proceeds after the data verification is successful. Therefore, the aggregation program in the transaction settlement system scans the status of billing invoices, identifies those in the "Pending Aggregation" state, and then aggregates these invoices to obtain the aggregation result for each settlement batch. After each billing invoice completes the aggregation process, its status is updated from "Pending Aggregation" to "Aggregated" to prevent duplicate aggregation.

[0073] Clearing Phase: The clearing phase is executed after the aggregation phase. That is, after the aggregation phase generates the aggregation results, the status of each settlement batch is aggregated, and the status of each settlement batch is "Pending Clearing". The clearing phase includes the process of obtaining clearing rules and generating settlement instances. In the process of obtaining clearing rules, the clearing program in the transaction settlement system needs to query the clearing rules in the settlement contract corresponding to the merchant in each settlement batch based on the merchant identifier. This determines the settlement cycle (e.g., T+1 settlement or D+1 settlement) and clearing information (e.g., settlement start point information). Then, in the process of generating settlement instances, the clearing program in the transaction settlement system scans the status of each settlement batch and identifies the settlement batches in the "Pending Clearing" status. It then performs clearing processing on these "Pending Clearing" batches to obtain the clearing result for each batch. After each settlement batch completes the clearing processing, the status is updated from "Pending Clearing" to "Cleared". The specific implementation process is as follows: 1. The clearing program scans the settlement batches in the "Pending Clearing" status. 2. Determine if the settlement batch in the "Pending Clearing" status has reached its settlement period. 3. If the settlement period has not been reached, do not clear the settlement batch; if the settlement period has been reached, determine if the total amount of all settlement batches that have reached the settlement period has been accumulated to determine if the settlement start point has been reached. 4. If the settlement start point has not been reached, do not clear the settlement batches that have reached the settlement period; if the settlement start point has been reached, generate a settlement instance based on the obtained total amount, confirm the settlement result, and then update the status from "Pending Clearing" to "Cleared".

[0074] Resource Interaction Phase: The resource interaction phase is executed after the clearing phase. That is, after the clearing phase generates the settlement result (i.e., the settlement instance), the settlement instance's status is "Pending Resource Interaction." Therefore, the resource interaction phase includes the process of obtaining resource interaction rules and the resource interaction operation process. In the process of obtaining resource interaction rules, the resource interaction program in the transaction settlement system needs to query the resource interaction rules in the settlement contract corresponding to the merchant based on the merchant identifier of the merchant in the settlement instance. These resource interaction rules are the resource interaction methods, such as transferring funds to the target account balance or withdrawing funds to the target bank account. Based on this, after determining the resource interaction method for the merchant, in the resource interaction operation process, the resource interaction program in the transaction settlement system needs to scan the status of the settlement instance and identify those in the "Pending Resource Interaction" state. Then, the resource interaction method calls the corresponding resource interaction interface of the resource interaction system to perform resource interaction. After completing the resource interaction, the status of the settlement instance is updated from "Pending Resource Interaction" to "Resource Interaction Completed."

[0075] The above section introduced the application scenarios, corresponding system structure, and interface. The following examples will provide a detailed explanation of how transaction settlement is performed: In one example, as... Figure 6 As shown, a transaction settlement method is provided, which is applied to... Figure 1 Taking server 104 as an example, this method can be used to illustrate the concept. Specifically, server 104 may deploy a transaction settlement system and a payment system. It is understood that this method can also be applied to a system including terminal 102 and server 104, and implemented through the interaction between terminal 102 and server 104. In this embodiment, the method includes the following steps:

[0076] Step 602: Obtain the transaction data of the target object. The transaction data includes at least the transaction resource amount and the object identifier of the target object.

[0077] The target object is a merchant, meaning an entity that can provide goods or services. These goods can be real or virtual. Therefore, transaction data is generated after a consumer places an order for goods or services offered by the target object. Thus, transaction data includes at least the transaction resource amount corresponding to the goods or services offered by the target object selected by the consumer, and the object identifier of the target object selected by the consumer. This object identifier can be a merchant account or a unique identifier indicating the target object; no specific limitation is made here.

[0078] It is understandable that transaction data can be internal data generated by the transaction system after placing a transaction order for a target object, or external data generated by placing a transaction order for a target object from an external data source. Furthermore, transaction data can also be the transaction data corresponding to multiple transaction orders initiated against a target object. These multiple transaction data will have corresponding transaction times, which can be the order placement time initiated by the consumer object, or the order time when the transaction data is generated after the order is initiated; no limitation is made here.

[0079] Specifically, server 104 acquires transaction data of the target object. This means that transaction data is generated after any transaction order is placed targeting the target object. Specifically, the data acquisition program in the transaction settlement system deployed on server 104 collects transaction orders generated within the payment system. These transaction orders include, but are not limited to, e-commerce transaction orders and utility payment orders. The transaction orders for the target object collected by the data acquisition program are identified as transaction data. The data acquisition program can collect transaction orders generated within the payment system, or it can collect transaction orders generated within the payment system at preset time intervals. The timing and method of collecting transaction orders generated within the payment system are not limited here.

[0080] Whether a transaction order is generated within the payment system or through an external transaction institution, it requires the consumer to place the order. The following is a brief overview of how transaction data is generated when a consumer places an order: First, the consumer initiates an order by selecting the corresponding goods or services on any internet transaction system and placing an order, or by adding the goods or services to their shopping cart. After the consumer places the order, the transaction system's backend stores the ordered goods or services information and calculates the corresponding transaction fees to generate the order. The order information then instructs the consumer to proceed to the payment platform to place the order. After verifying the goods or services information, the consumer makes the payment. Upon payment, the transaction resource amount is obtained, representing the amount paid by the consumer to the target institution. Therefore, after the consumer completes the payment, the payment platform responds to and processes the payment request. Upon successful processing, the transaction resource amount is deducted from the consumer's account and temporarily stored on the platform. Therefore, the payment platform can notify the target to deliver goods or provide corresponding services to the consumer based on the payment result. The payment system will also notify the transaction settlement system in this embodiment that a transaction has been generated and needs to be settled. It is understandable that in some transaction scenarios, the transaction chain involves external transaction institutions, and external channels also need to provide all transaction orders within a specific period. Transaction orders provided through external channels can also be used by the transaction settlement system for transaction settlement.

[0081] As described above, in practical applications, there may be situations where the transaction chain involves external trading institutions. In such cases, the data acquisition program also needs to connect with these external trading institutions. Specifically, the data acquisition program needs to connect with the respective external order APIs of these external channels to obtain the transaction data generated by the external channels for the target object. This ensures that transaction data can be obtained from both the internal trading system and external channels, thereby guaranteeing the integrity of the acquired data. Based on this, the following section details how to collect transaction data when the transaction chain involves external trading institutions:

[0082] In one specific embodiment, obtaining the transaction data of the target object specifically includes: for each external data source, obtaining the external transaction data generated by initiating an exchange with the target object under the external data source; and converting the external transaction data of each external data source according to a preset format to obtain the transaction data of the target object.

[0083] Specifically, when a transaction link involves an external transaction institution, the data acquisition program in the transaction settlement system deployed in server 104 collects the transaction orders generated within the payment system. The internal transaction orders obtained at this time are part of the transaction data. As described above, the transaction data may include the object identifier of the target object, the amount of transaction resources, and the transaction time. In practical applications, the transaction data may also include the object identifier of the consumer object, the order number, and the type of transaction resource amount, that is, the currency type of the consumer object's transaction. Thus, in the transaction settlement process of the transaction settlement system, more accurate transaction settlement can be carried out based on the aforementioned multi-dimensional information of the transaction data.

[0084] Considering the possibility of external trading institutions involved in the transaction chain, the external transaction data generated when a transaction is initiated against the target object through the external data source of the involved external trading institution is obtained. This means that external transaction data is generated when the consumer initiates a transaction against the target object through the external trading institution. In this case, the external order API of the external channel can transmit the external transaction data to the data acquisition program in real time through communication with the data acquisition program in the transaction settlement system, enabling the data acquisition program to obtain the external transaction data. Alternatively, the generated external transaction data may be stored in the storage system of the external trading institution. When transaction settlement is required, the external order API retrieves the external transaction data with the settlement date from the storage system of the external trading institution. Alternatively, the external order API of the external channel can also proactively transmit external transaction data to the data acquisition program at preset time intervals. Therefore, the method of obtaining external transaction data is not limited here. The obtained external transaction data may also include the target object's object identifier, transaction resource amount, transaction time, consumer object's object identifier, order number, and transaction resource amount type. Since the external transaction data comes from different external channels, it may also include channel order number, channel transaction time, resource interaction status, and channel billing resource amount, etc.

[0085] Furthermore, considering that the data structure of external transaction data provided by external channels may differ from that of transaction data generated directly through the payment system, format conversion is required to ensure consistency in data processing. The converted external transaction data is then used as the transaction data suitable for processing. Therefore, for each external data source, the external transaction data is converted according to the preset format of the transaction settlement system to obtain the converted external transaction data. Specifically, the format conversion may involve parsing the external transaction data and then performing format matching processing on the parsed external transaction data according to the preset format of the transaction settlement system, ensuring that the converted external transaction data can be processed by the transaction settlement system.

[0086] Furthermore, considering the possibility that the data structures of external transaction data and transaction data generated by the payment system are consistent, format conversion is unnecessary to avoid data redundancy. Therefore, it is necessary to first determine the data structure of the external transaction data. This involves parsing the external transaction data and then validating its format to determine if it conforms to the default format of the transaction settlement system. If it does, no format conversion is needed, and the external transaction data can be directly included as part of the transaction data. Conversely, if not, a data conversion step is performed. That is, if the external transaction data format does not conform to the default format, the external transaction data from each external data source is converted according to the default format to obtain the target object's transaction data. Thus, the obtained target object's transaction data includes the converted external transaction data and the transaction orders generated within the payment system (i.e., internal transaction data). The specific data structure of the target object's transaction data can be the settlement snapshot structure within the transaction settlement system.

[0087] Step 604: Query the settlement strategy configured for the target object according to the object identifier.

[0088] The object identifier can be a merchant account or a unique identifier indicating the target object. The settlement strategy is a pre-agreed strategy between the target object and the payment platform before providing goods or services. Specifically, as in the settlement contract management stage of the aforementioned embodiment, this involves the payment platform's operations personnel negotiating a settlement contract with the target object to which the settlement contract needs to be signed. This includes communicating the cooperation model for the required settlement contract and determining the settlement information for each settlement dimension. In other words, the settlement information for the target object under each settlement dimension needs to be determined during the settlement contract signing stage. After determining the settlement information for the target object under each settlement dimension, the payment platform's operations personnel enter the settlement contract information for the target object in the payment platform system. This essentially involves entering the settlement information for the target object under each settlement dimension into the payment platform system and matching this information with the object identifier corresponding to the target object signing the settlement contract.

[0089] Therefore, the settlement contract signed between the target object and the payment platform constitutes the settlement strategy in the actual transaction settlement process, and the settlement strategy can include settlement information under each settlement dimension. The payment platform stores the association between object identifiers and settlement strategies. For example, if object D1 matches settlement strategy E1, then there is an association between object identifier F1 of object D1 and settlement strategy E1. If object D2 matches settlement strategy E2, then there is an association between object identifier F2 of object D2 and settlement strategy E2. If object D3 matches settlement strategy E3, then there is an association between object identifier F3 of object D3 and settlement strategy E3.

[0090] Specifically, after acquiring the transaction data of the target object, the object identifier of the target object is extracted from the transaction data. Then, based on the stored association between the object identifier and the settlement strategy, the settlement strategy associated with the object identifier of the target object is determined, and this associated settlement strategy is designated as the settlement strategy configured for the target object. For example, if the target object is object D2, its object identifier is specifically object identifier F2. Since object identifier F2 is associated with settlement strategy E2, the settlement strategy configured for the target object is settlement strategy E2.

[0091] Step 606: Based on the settlement information under each settlement dimension in the settlement strategy, determine the target settlement mode that matches the target object according to the settlement method corresponding to each settlement information.

[0092] The settlement dimensions include, but are not limited to, billing methods, aggregation modes, settlement cycles, and resource interaction methods. Settlement information is information specific to each settlement dimension; that is, the settlement information differs depending on the settlement dimension. For example, settlement information under billing methods includes, but is not limited to, fixed amounts, percentages, annual tiered percentages, and monthly tiered percentages. Settlement information under aggregation modes includes, but is not limited to, single-transaction aggregation and batch aggregation. Settlement information under settlement cycles includes, but is not limited to, T+1, D+1, and S0. Settlement information under resource interaction methods includes, but is not limited to, transfers to the target account balance and withdrawals to the target bank account. In practical applications, settlement dimensions may also include daily cutoff points and fee rates, but these are not specified here.

[0093] Specifically, since the settlement strategy essentially includes the settlement information of the matched object under each settlement dimension, the target settlement pattern matching the target object can be determined by using the settlement methods of the settlement information under each settlement dimension. Furthermore, the target settlement pattern specifically includes the settlement methods matched under each different settlement dimension. For ease of understanding, the determination of the settlement pattern is described below using settlement information from multiple settlement dimensions:

[0094] In one specific embodiment, the target settlement mode includes at least a billing method, an aggregation mode, and a settlement period. That is, as described above, the settlement information for the target object can be the same or different under each settlement dimension; in other words, the settlement strategy essentially includes the settlement information of the matched object under each settlement dimension. The target settlement mode specifically includes the settlement methods matched under each different settlement dimension. Therefore, based on the settlement strategy including the billing method, the aggregation mode, and the settlement period, the target settlement mode includes the settlement method for the billing method, the settlement method for the aggregation mode, and the settlement method for the settlement period.

[0095] For example, taking multiple settlement dimensions, including billing method, aggregation mode, and settlement period, as an example, settlement strategy E1 can include settlement information under each settlement dimension, such as a fixed amount billing method, batch aggregation mode, and settlement period, and a settlement period of D+1. Similarly, settlement strategy E2 could have a percentage billing method, batch aggregation mode, and a settlement period of T+1. And settlement strategy E3 could have an annual tiered percentage billing method, single-transaction aggregation mode, and a settlement period of S0. The resulting target settlement mode can include settlement methods matching settlement information under different settlement dimensions. Taking settlement strategy E2 as an example, where settlement strategy E2 has a percentage billing method, batch aggregation mode, and a settlement period of T+1, the target settlement mode is specifically: a settlement method with a "percentage" billing method, a "batch aggregation" aggregation mode, and a settlement period of "T+1". In other words, the settlement process will be carried out according to the settlement methods under each settlement dimension in the target settlement model.

[0096] In an optional embodiment, the target settlement mode further includes a resource interaction method. As described above, the settlement strategy essentially includes settlement information for the matched object under each settlement dimension, while the target settlement mode specifically includes the settlement methods matched under different settlement dimensions. Therefore, since the settlement strategy includes a resource interaction method, the target settlement mode includes a settlement method based on the resource interaction method, and the resource interaction specifically occurs during the process of resource interaction with the target object after settlement is completed.

[0097] For example, let's take multiple settlement dimensions, including billing method, aggregation mode, settlement cycle, and resource interaction method, as an example. In this case, settlement strategy E1 uses a fixed amount as the billing method, batch aggregation as the aggregation mode, D+1 as the settlement cycle, and transfer to the target account balance as the resource interaction method. Similarly, settlement strategy E2 uses a percentage-based billing method, batch aggregation as the aggregation mode, T+1 as the settlement cycle, and transfer to the target account balance as the resource interaction method. And settlement strategy E3 uses an annual tiered percentage billing method, single-transaction aggregation as the aggregation mode, S0 as the settlement cycle, and withdrawal to the target's bank account as the resource interaction method.

[0098] The resulting target settlement model can include settlement methods matching settlement information under different settlement dimensions. Taking settlement strategy E2 as an example, where the billing method in settlement strategy E2 is percentage, the aggregation mode is batch aggregation, the settlement cycle is T+1, and the source interaction method is withdrawal to the object's bank account, the target settlement model specifically includes: a settlement method with a "percentage" billing method, a settlement method with a "batch aggregation" aggregation mode, a settlement cycle of "T+1," and a settlement method with "withdrawal to the object's bank account." In other words, during the settlement process, settlement processing and resource interaction will be performed according to the settlement methods under each settlement dimension of the target settlement model.

[0099] Step 608: Perform settlement processing on the amount of transaction resources according to the target settlement model to obtain the settlement result of the transaction data.

[0100] Specifically, settlement processing for the transaction resource amount is performed according to the target settlement model to obtain the settlement result of the transaction data. As mentioned above, the specific target settlement model includes settlement methods matched under different settlement dimensions. That is, settlement processing for the transaction resource amount is performed according to the settlement methods matched under different settlement dimensions to obtain the settlement result of the transaction data. The settlement result is specifically a settlement instance of the transaction data. Furthermore, considering that the target settlement model also includes resource interaction methods, that is, the resource interaction process with the target object after settlement needs to be performed according to the resource interaction methods, which will be described in detail below:

[0101] In an optional embodiment, the transaction settlement method further includes: for transaction data in the pending interaction state, performing resource processing on the settlement resources in the settlement result to obtain the amount of interactive resources matching the settlement resources; and transferring the amount of interactive resources to the resource receiving account of the target object according to the resource interaction method.

[0102] As explained above, the resource interaction phase executes after the clearing phase. That is, after the settlement results are generated in the clearing phase, the settlement instance's status is "pending resource interaction." Therefore, transaction data in the "pending interaction" state is actually the settlement instance of transaction data in the "pending resource interaction" state. Based on this, settlement resources are the resources in the settlement results that can be settled against the target object. Considering that the trading platform needs to charge a platform-billed resource amount, the platform-billed resource amount needs to be deducted from the transaction resource amount. Therefore, the difference between the transaction resource amount and the platform-billed resource amount is the amount of interactive resources.

[0103] Specifically, for transaction data in the pending interaction state, resource processing is performed on the settlement resources in the settlement result to obtain the amount of interactive resources matching the settlement resources. In reality, the settlement process includes a billing process, during which a platform billing resource amount is obtained. At this point, the platform billing resource amount matching the settlement resources is extracted from the settlement result. Then, the difference between the settlement resources and the platform billing resource amount is determined as the interactive resource amount. For example, if the settlement resources are 100 and the platform billing resource amount is 5, the interactive resource amount is 95 (i.e., 100 - 5 = 95).

[0104] Based on this, the resource interaction program in the transaction settlement system queries the resource interaction rules in the settlement contract corresponding to the target object based on the object identifier of the target object in the settlement instance. The aforementioned resource interaction rules are the required resource interaction methods. That is, in this embodiment, the resource interaction method in the target settlement mode can also be determined before resource interaction, and the specific timing of determining the resource interaction method is not limited here. Therefore, according to the resource interaction method, the amount of interactive resources is transferred to the resource receiving account of the target object. For example, the resource interaction method can be a transfer to the target account balance or a withdrawal to the target's bank account. Therefore, if the resource interaction method is a transfer to the target account balance, the resource receiving account of the target object is the target object's object account balance, and the amount of interactive resources can be transferred to the target object's object account balance. Alternatively, if the resource interaction method is a withdrawal to the target's bank account, the resource receiving account of the target object is the target object's bank account, and the amount of interactive resources can be transferred to the target object's bank account.

[0105] In one specific embodiment, the transaction settlement method further includes: after transferring the amount of interactive resources to the resource receiving account of the target object, updating the data status of the transaction data from the pending interaction state to the interacted state. Considering that after transferring the amount of interactive resources to the resource receiving account of the target object, the transaction settlement and transaction resource interaction process for the transaction data has actually been completed, to avoid repeated transaction resource interactions for the same transaction data, the data status of the transaction data should be updated from the pending interaction state to the interacted state. That is, as described in the previous embodiments, resource interaction is performed by calling the resource interaction interface of the corresponding resource interaction system through resource interaction methods, and after completing the resource interaction, the status of the settlement instance is updated from "pending resource interaction" to "resource interaction completed".

[0106] For ease of understanding, such as Figure 7The diagram illustrates the transaction settlement process, which involves four stages: settlement strategy management, transaction, data acquisition, settlement, and resource interaction. The settlement strategy management stage primarily involves configuring settlement strategies for the target object, specifically determining the settlement information for each settlement dimension within the configured settlement strategy. Then, in the transaction stage, a transaction order is sent to the target object, generating a transaction order that is then obtained at the data acquisition node. Therefore, before the settlement stage, the settlement strategy configured for the target object can be queried using the object identifier in the transaction data. Based on the settlement information for each settlement dimension within the settlement strategy, and according to the settlement method corresponding to each settlement information, a target settlement mode matching the target object is determined. In the settlement stage, settlement processing for the transaction resource amount is executed according to the target settlement mode, resulting in the settlement result of the transaction data. Finally, resource processing is performed on the settlement resources in the settlement result to obtain the interactive resource amount matching the settlement resources. This interactive resource amount is then transferred to the target object's resource receiving account according to the resource interaction method. In other words, the interactive resource amount is transferred to the target object's account balance through a transfer procedure, and the interactive resource amount is transferred to the target object's bank account through a withdrawal procedure.

[0107] It is understood that the foregoing examples are for the purpose of understanding this solution and should not be construed as specific limitations on this solution.

[0108] In the above-mentioned transaction settlement method, the settlement strategy is configured differently according to the needs of different objects. That is, the settlement information of different objects in each settlement dimension is flexibly determined based on the needs of the objects. Then, the settlement strategy is queried by the object identifier in the transaction data of the target object. The target settlement mode is determined according to the settlement strategy configured for the target object. Then, the settlement processing for the transaction resource amount is executed according to the target settlement mode. Since the target settlement mode can adapt to the personalized settlement needs of the target object, it avoids the problem of poor scalability caused by the fixed settlement mode and meets the diversified and complex settlement needs of different objects, thereby improving the flexibility of transaction settlement.

[0109] As described above, the target settlement model includes at least a billing method, an aggregation model, and a settlement period. Therefore, the settlement process for transaction resource amounts actually includes billing processing, aggregation processing, and clearing processing according to the billing method, aggregation model, and settlement period, respectively. This will be described in detail below: In one embodiment, as... Figure 8 As shown, the target settlement model includes at least the billing method, aggregation model, and settlement cycle.

[0110] Based on this, according to the target settlement model, settlement processing is performed on the transaction resource amount to obtain the settlement results of the transaction data, specifically including:

[0111] Step 802: Perform billing processing on the amount of transaction resources according to the billing method to obtain the billing result of the transaction data.

[0112] The billing method includes at least one of fixed billing, percentage billing, and tiered billing. Specifically, the billing process calculates the platform-charged resource amount collected by the trading platform for the amount of transaction resources. This platform-charged resource amount is the platform service fee collected by the trading platform for the amount of transaction resources. The billing process also yields the interactive resource amount remaining after deducting the platform-charged resource amount from the transaction resource amount. As described above, the interactive resource amount is the amount of resources exchanged between the payment platform and the target account during resource interaction after transaction settlement.

[0113] Specifically, during the billing phase, billing processing needs to be performed based on the billing methods included in the target settlement model. The billing procedure needs to determine the billing method, which can be extracted from the billing methods included in the settlement model, or it can be based on the fact that the target object's transaction data structure is a settlement snapshot structure in the transaction settlement system. In this case, the billing procedure queries the billing method in real time based on the object identifier of the transaction data to obtain the pre-signed billing method for the target object; there is no limitation here. Based on this, the billing procedure performs billing processing for the transaction resource amount according to the determined billing method, obtaining the billing result for the transaction data.

[0114] Therefore, in actual implementation, the billing program needs to perform billing processing based on the billing method and the transaction resource amount in the transaction data. During the operation, it dynamically uses the billing strategy corresponding to the billing method to perform billing processing on the transaction resource amount, in order to calculate the platform billing resource amount charged by the transaction platform for the transaction resource amount, as well as the interactive resource amount after removing the platform billing resource amount. This generates the billing result of the transaction data. The aforementioned billing result of the transaction data is specifically the billing bill of the transaction data. The billing bill can uniquely identify the actual transaction amount, the platform's receivable handling fee, and the merchant settlement amount in a single order transaction initiated by the consumer to the target object. The actual transaction amount is the transaction resource amount in the transaction data, the platform's receivable handling fee is the obtained platform billing resource amount, and the merchant settlement amount is the interactive resource amount for the target object.

[0115] The following details the real-time billing method for obtaining billing results: In a specific embodiment, the billing result includes the platform billing resource amount and the interactive resource amount. The aforementioned platform billing resource amount is the platform's receivable handling fee in a single order transaction initiated by the consumer to the target object, and the interactive resource amount is the merchant's settlement amount in a single order transaction initiated by the consumer to the target object. In other words, the interactive resource amount is the settlement amount that the transaction platform allocates to the target object for a single order transaction after completing the transaction settlement.

[0116] Based on this, billing processing for the transaction resource amount is performed according to the billing method to obtain the billing result of the transaction data. Specifically, this includes: performing platform billing processing for the transaction resource amount according to the platform billing method to obtain the platform billed resource amount; calculating the difference between the transaction resource amount and the platform billed resource amount, and determining the obtained difference result as the interactive resource amount.

[0117] Specifically, the billing process performs platform billing on the transaction resource amount according to the billing strategy matched by the platform billing method, thus obtaining the platform billed resource amount. Since the billing process cannot directly identify the platform billing method, it needs to query according to different billing strategies and corresponding labels for different billing methods. Based on this, the following details how to obtain the platform billed resource amount through fixed billing, percentage billing, and tiered billing:

[0118] In one specific embodiment, the platform billing method includes at least one of fixed billing, percentage billing, and tiered billing. Fixed billing, also known as "uniform billing," results in a fixed platform billing resource amount regardless of the transaction amount. Therefore, fixed billing has a pre-defined platform billing resource amount. Percentage billing, on the other hand, charges according to a percentage of the transaction amount. This means percentage billing has a pre-defined platform billing rate, and the platform billing resource amount is obtained by multiplying the transaction amount by the pre-defined platform billing rate.

[0119] Tiered billing divides transactions into different tiers based on the amount of resources involved, with each tier corresponding to a different platform billing amount. Tiered billing is typically divided into "increasing tiered billing" and "decreasing tiered billing." For "increasing tiered billing," the larger the transaction amount, the higher the corresponding platform billing amount. Conversely, for "decreasing tiered billing," the larger the transaction amount, the lower the corresponding platform billing amount. Specific limitations on tiered platform billing methods are not specified here.

[0120] Secondly, since the billing process cannot directly identify the platform's billing method, each platform billing method has a matching platform billing number, and these platform billing numbers correspond one-to-one with the billing policies. For example, platform billing methods include fixed billing, percentage billing, and tiered billing. Fixed billing is matched with platform billing number G1, percentage billing with platform billing number G2, and tiered billing with platform billing number G3. Therefore, platform billing number G1 can be matched with a fixed billing policy, platform billing number G2 can be matched with a percentage billing policy, and platform billing number G3 can be matched with a tiered billing policy.

[0121] Based on this, according to the platform billing method in the billing method, platform billing processing is performed on the transaction resource amount to obtain the platform billing resource amount. Specifically, this includes: determining the billing strategy corresponding to the platform billing number according to the platform billing method in the billing method; and performing platform billing processing on the transaction resource amount according to the billing strategy corresponding to the platform billing number to obtain the platform billing resource amount.

[0122] Specifically, considering that each platform billing method has a matching platform billing number, and that each platform billing number corresponds one-to-one with a billing strategy, the billing procedure determines the billing strategy corresponding to the platform billing number based on the platform billing number matched by the platform billing method. Based on this, the platform billing process for the transaction resource amount is then executed according to the billing strategy corresponding to the platform billing number, thereby obtaining the platform billed resource amount for the transaction resource amount.

[0123] To facilitate understanding, let's further illustrate with the aforementioned example. If the platform billing method matches a platform billing number of G1, then the billing strategy corresponding to G1 is a fixed-fee strategy. In this case, the platform billing processing for the transaction resource amount is executed according to the fixed-fee strategy. If the preset platform billing resource amount matched by the fixed-fee strategy is 3, then there's no need to consider the specific amount of the transaction resource; simply determine the platform billing resource amount as the preset platform billing resource amount, resulting in a platform billing resource amount of 3. Alternatively, if the platform billing method matches a platform billing number of G2, then the billing strategy corresponding to G2 is a percentage-based billing strategy. In this case, the platform billing processing for the transaction resource amount is executed according to the percentage-based billing strategy. If the preset platform billing rate matched by the percentage-based billing strategy is 5%, and the transaction resource amount is 100, then the resulting platform billing resource amount is 5 (i.e., 100 * 5%).

[0124] Furthermore, since the platform's billing resource amount represents the platform's receivable fees for a single order transaction initiated by the consumer against the target, subtracting the platform's receivable fees from the transaction resource amount for this order yields the settlement amount available to the target. This involves calculating the difference between the transaction resource amount and the platform's billing resource amount, and determining this difference as the interactive resource amount. For clarity, let's use the aforementioned example: if the transaction resource amount is 100, and the platform's billing resource amount obtained under a fixed billing method is 3, then the interactive resource amount is 97 (100-3). Alternatively, if the transaction resource amount is 100, and the platform's billing resource amount obtained under a percentage billing method is 5, then the interactive resource amount is 95 (100-5).

[0125] For ease of understanding, such as Figure 9 The diagram illustrates the implementation logic of the billing strategy for each billing method. It shows the call to a strategy interface named "Billing Strategy," where the corresponding billing strategy is used to output the platform's billable resource amount based on the input transaction resource amount and billing method. The specific billing method called by the strategy interface calculates the platform's billable resource amount based on the transaction resource amount and billing method. Considering that platform billing methods include fixed billing, percentage billing, and tiered billing, there exist billing strategies of type fixed billing, percentage billing, and tiered billing. Therefore, Figure 9 The document outlines methods for calculating the platform's billable resource amount under different billing strategy types. In actual operation, it explains that the billing strategy type must be selected based on the settlement strategy to execute billing according to the transaction resource amount and billing method. This process involves calling the billing strategy method to obtain and return the platform's billable resource amount.

[0126] As described above, in the process of obtaining transaction data of the target object, it is possible to consider the situation where the transaction chain involves external transaction institutions. That is, it is possible to obtain external transaction data generated by transactions initiated against the target object under external data sources. When considering external data sources, it is necessary to consider whether the billing bill (i.e. billing result) generated based on the external transaction data of the external data source can match the external billing data in the external transaction data. In other words, regardless of whether it goes through an external transaction institution, the transaction data that the payment platform can obtain must be generated by placing a transaction order for the target object. Therefore, the payment platform must have the corresponding transaction order. Because some transactions involve external transaction institutions, introducing other participants (i.e., external transaction institutions) into the transaction process can lead to discrepancies between the order status of the transaction data generated by the external transaction institution and the order status of the transaction data obtained by the payment platform. For example, if an external transaction institution places an order on the payment platform on behalf of a consumer, but the order times out, the external transaction institution can determine that the order has failed and may not be able to obtain the external transaction data for that order. However, the payment platform will generate the transaction data for that order upon completing the payment. In this case, the transaction data obtained by the external transaction institution and the transaction data of the payment platform will be inconsistent. Therefore, it is necessary to use the external transaction data as the data benchmark for settlement, which also requires data verification based on the external transaction data to ensure data consistency between the external transaction institution and the transaction platform. This will be explained in detail below:

[0127] In an optional embodiment, the transaction settlement method further includes: when the transaction data includes external transaction data from an external data source, extracting external billing data from the external transaction data of the external data source, and extracting key billing data from the billing results; performing data verification between the external billing data and the key billing data to obtain a data verification result; and if the data verification result is successful, performing aggregation processing on the billing results of the transaction data according to the aggregation mode to obtain an aggregation result of the transaction data.

[0128] Specifically, when the transaction data includes external transaction data from external data sources (meaning external transaction data is obtained from external trading institutions), to ensure data consistency between the external trading institution and the trading platform, a data verification program is needed to perform a two-way verification between the billing results generated by the trading platform for the external transaction data and the external transaction data provided by the external trading institution. Specifically, the data verification program needs to extract external billing data from the external transaction data from the external data source, and extract key billing data from the billing results of the external transaction data. The aforementioned external billing data includes, but is not limited to, the transaction resource amount and transaction order number, while the key billing data includes the transaction resource amount and billing order number. Based on this, a data verification is performed on the external billing data and the key billing data to obtain a data verification result. That is, the external billing data and the key billing data are matched to determine if they are consistent. If they are inconsistent, the determined data verification result indicates a verification failure; if they are consistent, the determined data verification result indicates a successful verification.

[0129] Understandably, due to the possibility of one-sided orders—that is, situations where the payment platform generates billing results, or where external transaction institutions generate external billing data but do not report it back to the payment platform—if the external billing data cannot be matched with consistent key billing data, it indicates that the external transaction institution has one-sided accounting, and vice versa, indicating that the payment platform has one-sided accounting. In such cases, the determined data verification result will also indicate verification failure. Therefore, when the data verification result is successful, the step of aggregating the billing results of the transaction data according to the aggregation mode is performed to obtain the aggregated result of the transaction data. That is, while ensuring the consistency of the transaction data between the external transaction institution and the transaction platform, aggregation processing is then performed based on the billing results to ensure the reliability of the aggregated result.

[0130] In an optional embodiment, the transaction settlement method further includes: if the data verification result is a verification failure, determining the abnormal information that caused the verification failure, and determining the abnormal handling method that matches the abnormal information; and performing abnormal handling on the transaction data according to the abnormal handling method.

[0131] Specifically, if the data verification result is a failure, it indicates that the transaction data is inconsistent between the external trading institution and the trading platform. In this case, it's necessary to identify the anomaly causing the verification failure, specifically the discrepancy between the transaction resource amount in the external billing data and the transaction resource amount in the key billing data. In this case, the anomaly causing the verification failure is an abnormal transaction resource amount. Similarly, if the transaction order number in the external billing data is inconsistent with the billing order number in the key billing data, the anomaly causing the verification failure is an abnormal order number. For ease of understanding, as follows... Figure 10The diagram shown illustrates the interface that displays the error message that caused the verification to fail. Figure 10 For order information with a refund transaction type, the number of successful transactions through the channel is 3, while the number of successful transactions through the system is 2. This means that there is an order information where the channel succeeded but the system failed. In addition, the successful amount through the system is 0.02, while the successful amount through the channel is 0.03. This means that the transaction resource amounts are also different. At this time, it can be determined that the data verification result of this order information is a verification failure.

[0132] Based on this, after identifying the abnormal information causing the verification failure, since there is no longer a need to process transaction settlement for the abnormal transaction data, but rather to perform corresponding exception handling, it is necessary to determine the exception handling method matching the abnormal information and process the transaction data accordingly. For example, in the case of an abnormal transaction resource amount, a data refund can be issued to the consumer who initiated the order. In the case of an abnormal order number, it can be checked whether the order number was entered incorrectly. If so, the order number discrepancies can be cleared and then aggregated. If not, a data refund can also be issued to the consumer who initiated the order. For ease of understanding, as follows... Figure 11 The diagram shown illustrates the interface for handling abnormal information. In practical applications, abnormal handling can include, but is not limited to, refund processing, direct processing, and manual processing. No specific method is specified here.

[0133] Step 804: Aggregate the billing results of the transaction data according to the aggregation mode to obtain the aggregated result of the transaction data.

[0134] As explained above, the billing result of the obtained transaction data is specifically a billing statement for the transaction data. This billing statement uniquely identifies the actual transaction amount, platform fees, and merchant settlement amount for a single order placed by a consumer against a target object. During transaction settlement, aggregation can typically be performed on a single order or on the billing results of multiple transactions placed against the same target object. Specifically, the billing results of the transaction data are aggregated according to the aggregation model to obtain the aggregated transaction data result. In the case of single-transaction aggregation, the billing result of the transaction data can be directly used as input data for subsequent clearing processing. Therefore, single-transaction aggregation does not require considering the aggregation of billing results from multiple transactions.

[0135] Secondly, when the aggregation mode is batch aggregation, it is necessary to divide the billing results of transaction data containing the object identifier of the same target object into batches. Then, the billing results of the transaction data in each batch are aggregated to obtain the aggregation result for each batch. In other words, the aggregation result includes the billing results of multiple transaction data. The following details how to obtain the aggregation result through data batching and data aggregation:

[0136] In one specific embodiment, the transaction data consists of the transaction data corresponding to each of the multiple transaction orders initiated against the target object, and the transaction data also includes the transaction time.

[0137] The transaction data consists of the transaction data corresponding to multiple transaction orders initiated for the same target object. In other words, the transaction data includes the individual transaction data of multiple consumers placing orders for the same target object at different times. Furthermore, different transaction data have corresponding transaction times; for example, transaction data H1 corresponds to transaction time I1, transaction data H2 corresponds to transaction time I2, transaction data H3 corresponds to transaction time I3, transaction data H4 corresponds to transaction time I4, and transaction data H5 corresponds to transaction time I5.

[0138] Based on this, the billing results of the transaction data are aggregated according to the aggregation mode to obtain the aggregated results of the transaction data. Specifically, for the transaction data whose billing results are in the pending aggregation state, the data is divided into batches according to the transaction time to obtain multiple settlement batches of transaction datasets; among them, the transaction time of the transaction data belonging to the same transaction dataset meets the aggregation time condition; for each transaction dataset, the billing results of the transaction data within the same transaction dataset are aggregated to obtain the respective aggregation results of each transaction dataset.

[0139] In this context, the "pending aggregation" status refers to billing results that have completed billing processing but have not yet been aggregated (i.e., billing slips). Therefore, the "aggregated" status refers to billing results that have already undergone aggregation. Specifically, the aggregation program in the transaction settlement system scans the aggregation status of billing results and identifies those billing results in the "pending aggregation" status, meaning it identifies transaction data whose aggregation status is pending aggregation (i.e., "pending aggregation"). Then, the data is batched according to the transaction time matched by the transaction data, resulting in multiple settlement batches of transaction datasets. Transaction times within the same settlement batch of transaction datasets must meet the aggregation time condition, which can be the same day, the same week, etc. For example, if the aggregation time condition is the same day, then transaction data with transaction times belonging to the same day are divided into the same settlement batch, and a transaction dataset is constructed based on the transaction data divided into the same settlement batch.

[0140] For ease of understanding, let's assume transaction data H1 corresponds to transaction time I1, transaction data H2 corresponds to transaction time I2, transaction data H3 corresponds to transaction time I3, transaction data H4 corresponds to transaction time I4, and transaction data H5 corresponds to transaction time I5. If transaction times I1, I2, and I3 belong to the same day, and transaction times I4 and I5 belong to the same day, then transaction data H1 corresponding to transaction time I1, transaction data H2 corresponding to transaction time I2, and transaction data H3 corresponding to transaction time I3 will be classified into the same settlement batch, resulting in a transaction dataset J1 that includes transaction data H1, transaction data H2, and transaction data H3. Similarly, transaction data H4 corresponding to transaction time I4 and transaction data H5 corresponding to transaction time I5 will be classified into the same settlement batch, resulting in a transaction dataset J2 that includes transaction data H4 and transaction data H5.

[0141] Finally, for each settlement-matched transaction dataset, the billing results of transactions belonging to the same dataset are aggregated to obtain the aggregated result for each transaction dataset. For ease of understanding, taking transaction dataset J1, which includes transaction data H1, H2, and H3 in the previous example, aggregating the billing results of H1, H2, and H3 yields the aggregated result for transaction dataset J1. Similarly, for transaction dataset J2, which includes transaction data H4 and H5, aggregating the billing results of H4 and H5 yields the aggregated result for transaction dataset J2.

[0142] Furthermore, after completing the aggregation processing of the transaction dataset, it is necessary to update the aggregation status of each transaction data in the transaction dataset from the pending aggregation state to the aggregated state to prevent repeated aggregation and accumulation of the same transaction data.

[0143] Step 806: Perform clearing and sorting processing on the aggregated transaction data within the settlement period to obtain the settlement result of the transaction data.

[0144] The settlement cycle refers to the rule that the relevant transaction resources are settled to the merchant after a preset time period following the transaction. Settlement cycles include, but are not limited to, T+1, D+1, or S0. T+1 is a settlement cycle where settlement occurs on the next business day after the transaction date (i.e., the business day following the date the order was placed). D+1 is a settlement cycle where settlement occurs on the next calendar day after the transaction date (i.e., the calendar day following the date the order was placed). S0 is a near real-time settlement cycle, where settlement occurs on the date the order was placed.

[0145] Specifically, the clearing process performs clearing on the aggregated transaction data within the settlement period to obtain the settlement result. That is, the clearing process first determines whether the transaction time of the transaction data is eligible for clearing within the settlement period. If so, the aggregated transaction data is cleared to obtain the settlement result. If not, clearing will be performed on a later date when clearing is possible. For example, if the settlement period is T+1 and the transaction time is Friday, the aggregated transaction data can only be cleared on Monday of the following week. If the settlement period is S0, the aggregated transaction data can be cleared on any day the transaction time is.

[0146] Understandably, in practical applications, the amount to be cleared can also be considered. This involves clearing transaction data that reaches the settlement start point within the settlement period. Specifically, if the transaction time of the transaction data meets the time interval of the settlement period, it's necessary to determine whether the total aggregated amount in the aggregated result of the transaction data has reached the settlement start point. If it hasn't, no clearing is performed on the transaction data that has reached the settlement period until the settlement start point is reached. Then, the aggregated result of the transaction data is cleared to obtain the settlement result. As mentioned above, during the aggregation process, data is batched according to the transaction time matched with the transaction data, resulting in multiple settlement batches of transaction datasets. The resulting aggregation result is actually the aggregation result of each settlement batch after data allocation. The clearing stage is executed after the aggregation stage. That is, after the aggregation stage generates the aggregation result of each settlement batch, the status is summarized according to different settlement batches. At this point, the status of the settlement batch is "pending clearing." Therefore, the status of the settlement batch after clearing is "cleared." This will be explained below:

[0147] In one specific embodiment, the settlement result of the transaction data is obtained by clearing the aggregated results of the transaction data within the settlement period. Specifically, this includes: for the transaction dataset whose billing result is in the pending clearing state, determining the time difference between the transaction time of each transaction data in the transaction dataset and the settlement period; and when the time difference indicates that the settlement period has been reached, clearing the aggregated results of the transaction dataset to obtain the settlement result of the transaction dataset.

[0148] Specifically, the clearing program in the transaction settlement system scans the clearing status of each settlement batch, that is, determines the clearing status of the transaction dataset of each settlement batch, and identifies the settlement batches in the pending clearing state (i.e., the transaction dataset of the settlement batch). Then, it performs clearing processing on the settlement batches in the pending clearing state to obtain the clearing result for each settlement batch. After the clearing processing of each settlement batch is completed, the clearing status is updated from pending clearing to cleared. The specific implementation method is as follows: the clearing program scans the transaction dataset of the settlement batches in the pending clearing state and determines the time difference between the transaction time and the settlement period for each transaction data, determining whether the transaction time of the transaction data has reached the settlement period. If the settlement period has not been reached, the transaction data under that settlement batch is not cleared. Conversely, if the settlement period has been reached, the program judges whether the total aggregated amount in the aggregated result of the transaction data under the settlement batch has reached the settlement start point. If the settlement start point has not been reached, the transaction data under that settlement batch is not cleared. Conversely, if the settlement start point is reached, a settlement instance is generated based on the total aggregated amount in the aggregated result of the transaction data, and the settlement result is determined. Then, the clearing status of the transaction dataset is updated from the pending clearing status to the cleared status to avoid duplicate clearing processing.

[0149] It is understood that the foregoing examples are for the purpose of understanding this solution and should not be construed as specific limitations on this solution.

[0150] In this embodiment, a single system can support different settlement needs. This means that different billing methods are used to process different settlement needs, and different aggregation modes are applied to aggregate transactions. Final settlement is then performed for different settlement cycles, avoiding the need for transaction settlement through multiple systems for different needs, thus ensuring the flexibility of transaction settlement. Furthermore, by selecting and combining different processing steps according to different modes in the standard transaction settlement process, the system can flexibly support various settlement scenarios, further enhancing the flexibility of transaction settlement.

[0151] Based on the detailed description of the foregoing embodiments, the complete process of the transaction settlement method in the embodiments of this application will be described below. In one embodiment, such as Figure 12 As shown, a transaction settlement method is provided, which is applied to... Figure 1 Taking server 104 as an example, it can be understood that this method can also be applied to a system including terminal 102 and server 104, and implemented through the interaction between terminal 102 and server 104. In this embodiment, the method includes the following steps:

[0152] Step 1201: For each external data source, obtain the external transaction data generated by the transaction initiated against the target object under the external data source; convert the external transaction data of each external data source according to the preset format to obtain the transaction data of the target object; the transaction data includes at least the transaction resource amount and the object identifier of the target object.

[0153] Step 1202: Query the settlement strategy configured for the target object according to the object identifier.

[0154] Step 1203: Based on the settlement information under each settlement dimension in the settlement strategy, determine the target settlement mode that matches the target object according to the settlement method corresponding to each settlement information; the target settlement mode includes at least the billing method, aggregation mode, settlement cycle, and resource interaction method.

[0155] Step 1204: Determine the billing strategy corresponding to the platform billing number according to the platform billing method in the billing method; perform platform billing processing on the transaction resource amount according to the billing strategy corresponding to the platform billing number to obtain the platform billed resource amount.

[0156] Step 1205: Calculate the difference between the transaction resource amount and the platform billing resource amount, and determine the obtained difference result as the interactive resource amount; the billing result includes the platform billing resource amount and the interactive resource amount.

[0157] Step 1206: Extract external billing data from external transaction data of external data sources, and extract key billing data from billing results; perform data verification between external billing data and key billing data to obtain data verification results.

[0158] Step 1207: If the data verification result is a verification failure, determine the abnormal information that caused the verification failure and determine the abnormal handling method that matches the abnormal information; perform abnormal handling on the transaction data according to the abnormal handling method.

[0159] Step 1208: If the data verification result is successful, for the transaction data whose billing result aggregation status is in the pending aggregation state, the data is divided into batches according to the transaction time of the transaction data to obtain multiple settlement batches of transaction datasets; among them, the transaction time of the transaction data belonging to the same transaction dataset meets the aggregation time condition; for each transaction dataset, the billing results of the transaction data within the same transaction dataset are aggregated to obtain the aggregation result of each transaction dataset.

[0160] Step 1209: For transaction datasets whose billing results are in the pending clearing state, determine the time difference between the transaction time and the settlement period for each transaction in the transaction dataset; if the time difference indicates that the settlement period has been reached, perform clearing processing on the aggregated results of the transaction dataset to obtain the settlement result of the transaction dataset.

[0161] Step 1210: For transaction data in the pending interaction state, process the settlement resources in the settlement result to obtain the amount of interactive resources that match the settlement resources; and transfer the amount of interactive resources to the resource receiving account of the target object according to the resource interaction method.

[0162] Step 1211: After transferring the amount of interactive resources to the target object's resource receiving account, update the data status of the transaction data from the pending interaction state to the interacted state.

[0163] It should be understood that the specific implementation methods of steps 1201 to 1211 are similar to those of the aforementioned embodiments, and will not be repeated here.

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

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

[0166] In one embodiment, such as Figure 13 As shown, a transaction settlement device is provided, including: a data acquisition module 1302, a strategy query module 1304, a settlement mode determination module 1306, and a settlement processing module 1308, wherein:

[0167] The data acquisition module 1302 is used to acquire the transaction data of the target object. The transaction data includes at least the transaction resource amount and the object identifier of the target object.

[0168] The strategy query module 1304 is used to query the settlement strategy configured for the target object according to the object identifier;

[0169] The settlement mode determination module 1306 is used to determine the target settlement mode that matches the target object based on the settlement information under each settlement dimension in the settlement strategy and according to the settlement method corresponding to each settlement information.

[0170] The settlement processing module 1308 is used to perform settlement processing on the amount of transaction resources according to the target settlement mode, and obtain the settlement result of the transaction data.

[0171] In one embodiment, the target settlement model includes at least a billing method, an aggregation model, and a settlement cycle;

[0172] The settlement processing module is specifically used to perform billing processing on the amount of transaction resources according to the billing method to obtain the billing result of the transaction data; to aggregate the billing result of the transaction data according to the aggregation mode to obtain the aggregated result of the transaction data; and to perform clearing processing on the aggregated result of the transaction data according to the settlement period to obtain the settlement result of the transaction data.

[0173] In one embodiment, the billing result includes the amount of platform-billed resources and the amount of interactive resources;

[0174] The settlement processing module is specifically used to perform platform billing processing on the transaction resource amount according to the platform billing method in the billing method, and obtain the platform billed resource amount; calculate the difference between the transaction resource amount and the platform billed resource amount, and determine the obtained difference result as the interactive resource amount.

[0175] In one embodiment, the platform billing method includes at least one of fixed billing, percentage billing, and tiered billing, and each platform billing method has a matching platform billing number, with each platform billing number corresponding to a billing policy.

[0176] The settlement processing module is specifically used to determine the billing strategy corresponding to the platform billing number according to the platform billing method in the billing method; and to perform platform billing processing on the transaction resource amount according to the billing strategy corresponding to the platform billing number to obtain the platform billed resource amount.

[0177] In one embodiment, the transaction data consists of the transaction data corresponding to each of the multiple transaction orders initiated against the target object, and the transaction data also includes the transaction time;

[0178] The settlement processing module is specifically used to batch transaction data in the pending aggregation state of billing results according to the transaction time of the transaction data to obtain multiple settlement batches of transaction datasets; among them, the transaction time of transaction data belonging to the same transaction dataset meets the aggregation time condition; for each transaction dataset, the billing results of the transaction data within the same transaction dataset are aggregated to obtain the aggregation result of each transaction dataset.

[0179] In one embodiment, the settlement processing module is specifically used to determine the time difference between the transaction time and the settlement period for each transaction data in the transaction dataset whose billing result is in the pending settlement state; when the time difference indicates that the settlement period has been reached, the module performs settlement processing on the aggregated result of the transaction dataset to obtain the settlement result of the transaction dataset.

[0180] In one embodiment, the transaction settlement device further includes a data verification module;

[0181] The data verification module is used to extract external billing data from external transaction data sources when the transaction data includes external transaction data from external data sources, and to extract key billing data from the billing results; it then performs data verification between the external billing data and the key billing data to obtain the data verification results.

[0182] The settlement processing module is specifically used to perform the step of aggregating the billing results of the transaction data according to the aggregation mode when the data verification result is successful, so as to obtain the aggregated result of the transaction data.

[0183] In one embodiment, the transaction settlement device further includes an exception handling module;

[0184] The exception handling module is used to determine the exception information that caused the data verification failure when the data verification result is a failure, and to determine the exception handling method that matches the exception information; and to perform exception handling on the transaction data according to the exception handling method.

[0185] In one embodiment, the transaction settlement device further includes a resource interaction module;

[0186] The target settlement model also includes resource interaction methods;

[0187] The resource interaction module is used to process the settlement resources in the settlement results for transaction data that is in the pending interaction state, and obtain the amount of interactive resources that match the settlement resources; according to the resource interaction method, the amount of interactive resources is transferred to the resource receiving account of the target object.

[0188] In one embodiment, the resource interaction module is further configured to update the data status of the transaction data from the pending interaction state to the interacted state after transferring the amount of interactive resources to the resource receiving account of the target object.

[0189] In one embodiment, the data acquisition module is specifically used to acquire, for each external data source, the external transaction data generated by the transaction initiated against the target object under the external data source; and to convert the external transaction data of each external data source according to a preset format to obtain the transaction data of the target object.

[0190] In one embodiment, a computer device is provided, which can be a server or a terminal. This embodiment uses a server as an example for description, and its internal structure diagram is as follows: Figure 14 As shown, the computer device includes a processor, memory, input / output (I / O) interfaces, and a communication interface. The processor, memory, and I / O interfaces are connected via a system bus, and the communication interface is also connected to the system bus via the I / O interfaces. The processor provides computing and control capabilities. The memory includes a non-volatile storage medium and internal memory. The non-volatile storage medium stores an operating system, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage medium. The database stores transaction data, settlement strategies, settlement models, and other data related to the embodiments of this application. The I / O interfaces are used for exchanging information between the processor and external devices. The communication interface is used for communicating with external terminals via a network connection. When the computer program is executed by the processor, it implements a transaction settlement method.

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

[0192] In one embodiment, a computer device is also provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps in the above method embodiments.

[0193] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon that, when executed by a processor, implements the steps in the above method embodiments.

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

[0195] It should be noted that the transaction settlements (including but not limited to object device information, object personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the object or fully authorized by all parties, and the collection, use and processing of related data must comply with the relevant laws, regulations and standards of the relevant countries and regions.

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

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

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

Claims

1. A method for transaction settlement, characterized in that, The method includes: Obtain transaction data of the target object, wherein the transaction data includes at least the amount of transaction resources and the object identifier of the target object; Based on the object identifier, query the settlement strategy configured for the target object; Based on the settlement information under each settlement dimension in the settlement strategy, and according to the settlement method corresponding to each of the settlement information, a target settlement mode matching the target object is determined; According to the target settlement model, settlement processing is performed on the amount of the transaction resources to obtain the settlement result of the transaction data.

2. The method according to claim 1, characterized in that, The target settlement model includes at least a billing method, an aggregation model, and a settlement cycle; The step of performing settlement processing on the amount of the transaction resources according to the target settlement mode to obtain the settlement result of the transaction data includes: The billing process for the transaction resource amount is executed according to the billing method described above, and the billing result of the transaction data is obtained. The billing results of the transaction data are aggregated according to the aggregation mode to obtain the aggregated result of the transaction data; The settlement result of the transaction data is obtained by clearing the aggregated results of the transaction data within the settlement period.

3. The method according to claim 2, characterized in that, The billing results include the amount of platform-billed resources and the amount of interactive resources; The step of performing billing processing on the amount of the transaction resources according to the billing method to obtain the billing result of the transaction data includes: According to the platform billing method in the billing method, perform platform billing processing for the transaction resource amount to obtain the platform billed resource amount; Calculate the difference between the transaction resource amount and the platform billing resource amount, and determine the obtained difference result as the interactive resource amount.

4. The method according to claim 3, characterized in that, The platform billing method includes at least one of fixed billing, percentage billing, and tiered billing, and each of the platform billing methods has a matching platform billing number, which corresponds one-to-one with the billing strategy. The step of performing platform billing processing on the transaction resource amount according to the platform billing method in the billing method to obtain the platform billing resource amount includes: Determine the billing strategy corresponding to the platform billing number according to the platform billing method matched in the billing method; The platform billing process for the transaction resource amount is executed according to the billing policy corresponding to the platform billing number to obtain the platform billing resource amount.

5. The method according to claim 2, characterized in that, The transaction data consists of the transaction data corresponding to each of the multiple transaction orders initiated against the target object, and the transaction data also includes the transaction time; The billing results of the transaction data are aggregated according to the aggregation mode to obtain the aggregated result of the transaction data, including: For transaction data whose billing results are in the pending aggregation state, the data is divided into batches according to the transaction time of the transaction data to obtain multiple settlement batches of transaction datasets; wherein, the transaction time of transaction data belonging to the same transaction dataset meets the aggregation time condition. For each of the transaction datasets, the billing results of the transaction data within the same transaction dataset are aggregated to obtain the respective aggregation result for each transaction dataset.

6. The method according to claim 5, characterized in that, The step of clearing the aggregated transaction data according to the settlement period to obtain the settlement result of the transaction data includes: For transaction datasets whose billing results are pending clearing status, determine the time difference between the transaction time and the settlement period for each transaction in the transaction dataset. When the time difference indicator has reached the settlement period, the aggregated results of the transaction dataset are cleared to obtain the settlement result of the transaction dataset.

7. The method according to claim 2, characterized in that, The method further includes: If the transaction data includes external transaction data from an external data source, extract the external billing data from the external transaction data of the external data source, and extract the key billing data from the billing results; The external billing data is compared with the key billing data to obtain the data comparison results. If the data verification result is successful, the step of aggregating the billing results of the transaction data according to the aggregation mode to obtain the aggregated result of the transaction data is performed.

8. The method according to claim 7, characterized in that, The method further includes: If the data verification result is a verification failure, determine the abnormal information that caused the verification failure, and determine the abnormal handling method that matches the abnormal information; The transaction data is processed according to the aforementioned exception handling method.

9. The method according to claim 1, characterized in that, The target settlement model also includes resource interaction methods; The method further includes: For transaction data in the pending interaction state, resource processing is performed on the settlement resources in the settlement result to obtain the amount of interactive resources matching the settlement resources; According to the resource interaction method, the amount of interactive resources is transferred to the resource receiving account of the target object.

10. The method according to claim 9, characterized in that, The method further includes: After the amount of interactive resources is transferred to the resource receiving account of the target object, the data status of the transaction data is updated from the pending interaction status to the interacted status.

11. The method according to claim 1, characterized in that, The acquisition of the target object's transaction data includes: For each external data source, obtain the external transaction data generated by initiating an exchange with the target object under the external data source; The external transaction data of each external data source is converted according to a preset format to obtain the transaction data of the target object.

12. A transaction settlement device, characterized in that, The device includes: The data acquisition module is used to acquire transaction data of the target object, wherein the transaction data includes at least the amount of transaction resources and the object identifier of the target object; The strategy query module is used to query the settlement strategy configured for the target object according to the object identifier; The settlement mode determination module is used to determine the target settlement mode that matches the target object based on the settlement information under each settlement dimension in the settlement strategy and according to the settlement method corresponding to each of the settlement information. The settlement processing module is used to perform settlement processing on the amount of the transaction resources according to the target settlement mode, and obtain the settlement result of the transaction data.

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

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

15. A computer program product, comprising a computer program, characterized in that, When executed by a processor, the computer program implements the steps of the method described in any one of claims 1 to 11.

Images