Project data processing method, device, equipment, storage medium and program product

Abstract

The application discloses a project data processing method and device, equipment, a storage medium and a program product. The method comprises the following steps: determining a target business category corresponding to a first clearing project; based on clearing control configuration information, determining a pricing rule with a priority satisfying a preset priority condition as a target pricing rule from the pricing rules corresponding to the target business category, matching the target pricing rule with the first clearing project to obtain a matching result; in the case of determining that the target pricing rule is consistent with the first clearing project according to the matching result, clearing the first clearing project by using the target pricing rule; in the case of representing switching to a next priority pricing rule by an action switching instruction corresponding to the target pricing rule, taking the next priority pricing rule as a new target pricing rule, and continuing to perform the step of matching the target pricing rule with the first clearing project, which can meet the demand of business normality change, and improve the processing efficiency of the clearing project.

Description

Technical Field

[0001] The present application relates to the field of data processing, and in particular to a project data processing method, device, equipment, storage medium and program product. Background Art

[0002] Liquidation involves multiple steps, including project confirmation and project resource transfer. Pricing rules are crucial for liquidation, defining the cost standards and calculation methods for project resource transfers.

[0003] Currently, the pricing rules used by the clearing engine to process project data are closely tied to business logic. When business logic changes, pricing rules can only be adjusted to address specific business needs, failing to accommodate regular business changes and impacting the efficiency of processing first-time clearing projects.

[0004] In view of this, how to process project data to meet the needs of normal business changes and improve the processing efficiency of liquidation projects has become an important issue that needs to be solved urgently. Summary of the Invention

[0005] The embodiments of the present application provide a project data processing method, apparatus, device, storage medium, and program product, which can meet the needs of normal business changes and improve the processing efficiency of liquidation projects.

[0006] In a first aspect, an embodiment of the present application provides a project data processing method, including: determining a target business category corresponding to a first liquidation project; based on liquidation control configuration information, determining a pricing rule whose priority satisfies a preset priority condition from the pricing rules corresponding to the target business category as a target pricing rule, the liquidation control configuration information including at least one liquidation rule corresponding to a business category, the liquidation rule including a pricing rule and an action switching indication corresponding to the pricing rule, and the pricing rule is configured with a priority; matching the target pricing rule with the first liquidation project to obtain a matching result; when it is determined according to the matching result that the target pricing rule is consistent with the first liquidation project, using the target pricing rule to liquidate the first liquidation project; when the action switching indication corresponding to the target pricing rule represents switching to a next priority pricing rule, using the next priority pricing rule as the new target pricing rule, and continuing to execute the step of matching the target pricing rule with the first liquidation project.

[0007] In a second aspect, an embodiment of the present application provides a project data processing device, the device comprising: a business type determination module for determining a target business type corresponding to a first liquidation project; a rule determination module for determining, based on liquidation control configuration information, a pricing rule whose priority satisfies a preset priority condition from the pricing rules corresponding to the target business type as a target pricing rule, the liquidation control configuration information including at least one liquidation rule corresponding to a business type, the liquidation rule including a pricing rule and an action switching indication corresponding to the pricing rule, the pricing rule being configured with a priority; a rule matching module for matching the target pricing rule with the first liquidation project to obtain a matching result; a liquidation execution module for liquidating the first liquidation project using the target pricing rule when it is determined according to the matching result that the target pricing rule is consistent with the first liquidation project; a rule switching module for using the next priority pricing rule as the new target pricing rule when the action switching indication corresponding to the target pricing rule represents switching to the next priority pricing rule.

[0008] In a third aspect, an embodiment of the present application provides a project data processing device, comprising: a processor and a memory storing computer program instructions; when the processor executes the computer program instructions, the project data processing method as described in the first aspect is implemented.

[0009] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium having computer program instructions stored thereon, and when the computer program instructions are executed by a processor, the project data processing method as described in the first aspect is implemented.

[0010] In a fifth aspect, an embodiment of the present application provides a computer program product, including a computer program, which, when executed by a processor, implements the project data processing method as described in the first aspect.

[0011] An embodiment of the present application provides a project data processing method, in which the liquidation control configuration information includes a liquidation rule corresponding to at least one business type, the liquidation rule includes a pricing rule and an action switching indication corresponding to the pricing rule, and the pricing rule is configured with a priority, thereby realizing independent configuration of different liquidation rules for different business types. Therefore, after determining the target business type corresponding to the first liquidation project, the method provided by the embodiment of the present application can, based on the liquidation control configuration information, first determine the pricing rule whose priority meets the preset priority condition from the pricing rules corresponding to the target business type as the target pricing rule, match the target pricing rule with the first liquidation project to obtain a matching result, and when it is determined according to the matching result that the target pricing rule is consistent with the first liquidation project, use the target pricing rule to perform the matching. The first liquidation item is then liquidated, and then when the action switching indication corresponding to the target pricing rule indicates switching to the next priority pricing rule, the next priority pricing rule is used as the new target pricing rule, and the step of matching the target pricing rule with the first liquidation item is continued. It can be seen that through the embodiment of the present application, different liquidation rules can be configured for different types of business according to the actual business situation. Specifically, pricing rules and the priorities and action switching indications corresponding to the pricing rules can be configured for different types of business according to the actual business situation, thereby achieving the purpose of flexibly controlling the first liquidation item based on the liquidation control configuration information to flexibly switch liquidations between multiple pricing rules according to the type of business to which it belongs, meeting the needs of normal business changes and improving the processing efficiency of the first liquidation item.

[0012] Furthermore, in the settlement control configuration information of the method, the pricing rule has corresponding element priority control information, and the element priority control information is used to describe the priority order of the elements matched with the pricing rule, so that when the first settlement item is matched with the pricing rule, it can be matched based on the order of element priority, and there is no need to determine the priority of element matching by the sorting position of the element in the element combination, avoiding the risk of errors when personalizing the elements and facilitating flexible personalization of the elements.

[0013] Furthermore, in the clearing control configuration information of the method, the element unique identifier also has a parameter value length field, and the parameter value length field is used to store the length information of the corresponding element parameter value. Therefore, the method can respond to the element sequence adjustment request, adjust the order of the element unique identifiers in the element combination according to the element sequence adjustment request, and adjust the order of the element parameter values ​​in the actual business parameters corresponding to the element combination based on the order and the parameter value length field of the element unique identifier, thereby achieving the purpose of flexible and personalized modification of the elements. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following is a brief introduction to the drawings required for use in the embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0015] Figure 1 This is a schematic diagram of an example of an application scenario of the project data processing method provided in an embodiment of the present application;

[0016] Figure 2 This is a flowchart of a project data processing method provided by an embodiment of the first aspect of the present application;

[0017] Figure 3a This is a schematic diagram of liquidation control configuration information provided by an embodiment of the first aspect of the present application;

[0018] Figure 3b This is a schematic diagram of element arrangement provided by an embodiment of the first aspect of the present application;

[0019] Figure 3c This is a schematic diagram of the element-service correspondence relationship provided by an embodiment of the first aspect of the present application;

[0020] Figure 3d This is a schematic diagram of the combination of elements provided in an embodiment of the first aspect of the present application;

[0021] Figure 3e This is a schematic diagram of an element combination provided by another embodiment of the first aspect of the present application;

[0022] Figure 3f This is a schematic diagram of the service setting interface provided by an embodiment of the first aspect of the present application;

[0023] Figure 4 is a flowchart of a project data processing method provided by another embodiment of the first aspect of the present application;

[0024] Figure 5 is a flowchart of a project data processing method provided by yet another embodiment of the first aspect of the present application;

[0025] Figure 6 is a flowchart of a project data processing method provided by yet another embodiment of the first aspect of the present application;

[0026] Figure 7 is a flowchart of a project data processing method provided by yet another embodiment of the first aspect of the present application;

[0027] Figure 8 is a flowchart of a project data processing method provided by yet another embodiment of the first aspect of the present application;

[0028] Figure 9is a flowchart of a project data processing method provided by yet another embodiment of the first aspect of the present application;

[0029] Figure 10 It is a structural diagram of a project data processing device provided in an embodiment of the second aspect of the present application;

[0030] Figure 11 It is a structural diagram of the project data processing equipment provided in an embodiment of the third aspect of this application. DETAILED DESCRIPTION

[0031] The features and exemplary embodiments of various aspects of the present application will be described in detail below. In order to make the purpose, technical solutions and advantages of the present application clearer, the present application will be further described in detail below in conjunction with the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are only intended to explain the present application, rather than to limit the present application. For those skilled in the art, the present application can be implemented without the need for some of these specific details. The following description of the embodiments is merely to provide a better understanding of the present application by illustrating examples of the present application. It should be noted that the acquisition, storage, use, processing, etc. of information and data in the embodiments of the present application are authorized by the user or relevant agencies and comply with the relevant provisions of national laws and regulations.

[0032] Currently, the pricing rules used by the clearing engine to process project data are closely tied to business logic. When business logic changes, pricing rules can only be adjusted to address specific business needs, failing to accommodate regular business changes and impacting the efficiency of processing first-time clearing projects.

[0033] In view of this, an embodiment of the present application provides a project data processing method, in which the liquidation control configuration information includes a liquidation rule corresponding to at least one business type, the liquidation rule includes a pricing rule and an action switching indication corresponding to the pricing rule, and the pricing rule configuration has a priority, thereby realizing the independent configuration of different liquidation rules for different business types. Therefore, after determining the target business type corresponding to the first liquidation project, the method provided by the embodiment of the present application can, based on the liquidation control configuration information, first determine the pricing rule whose priority meets the preset priority condition from the pricing rules corresponding to the target business type as the target pricing rule, match the target pricing rule with the first liquidation project, and obtain a matching result. When it is determined that the target pricing rule is consistent with the first liquidation project according to the matching result, the target pricing rule is used to match the target pricing rule with the first liquidation project. The pricing rule liquidates the first liquidation item, and then when the action switching indication corresponding to the target pricing rule indicates switching to the next priority pricing rule, the next priority pricing rule is used as the new target pricing rule, and the step of matching the target pricing rule with the first liquidation item is continued. It can be seen that through the embodiment of the present application, different liquidation rules can be configured for different types of business according to the actual business situation. Specifically, pricing rules and the priorities and action switching indications corresponding to the pricing rules can be configured for different types of business according to the actual business situation, thereby achieving the purpose of flexibly controlling the first liquidation item based on the liquidation control configuration information to flexibly switch liquidations between multiple pricing rules according to the type of business to which it belongs, meeting the needs of normal business changes and improving the processing efficiency of the first liquidation item.

[0034] The project data processing methods provided in the embodiments of this application can be used in various project clearing scenarios. For example, clearing card-not-present transactions and credit card transactions. The project data processing methods provided in the embodiments of this application can be applied to clearing platforms for various types of transactions. These clearing platforms can run on servers or any electronic device. The following describes some possible application scenarios for the project data processing methods provided in the embodiments of this application.

[0035] Figure 1 This is a schematic diagram of an example of an application scenario of the project data processing method provided in the embodiment of the present application. Figure 1 As shown, the project data processing method provided in the embodiment of the present application is applied to a clearing platform 10 running on a server. In this application, a first clearing item refers to a transaction that requires resource transfer. The first clearing item includes relevant transaction information, such as the transaction unique identifier, transaction amount, the paying user's user unique identifier, user account number, the receiving merchant's merchant unique identifier and merchant account number, etc. The first clearing item can be any type of transaction, such as a card-not-present transaction.

[0036] Exemplarily, the clearing platform 10 can be used to determine a first clearing item based on a payment request from a user terminal 20, clear the first clearing item, and complete the process of transferring resources to a merchant 30. The user terminal 20 can be a program that provides transaction services to users. The user terminal 20 can be bound to a payment account of at least one financial institution (e.g., various banks, third-party resource trading platforms). Thus, the user terminal 20 can initiate a payment request to the clearing platform 10, which performs clearing based on pricing determined by various parties, such as financial institutions and merchants, deducts the corresponding resources from the payer's account, and transfers the resources to the payee's account.

[0037] The clearing platform 10 may include one or more electronic devices. The electronic devices may include servers, gateways, routers, and other devices. The type and number of electronic devices in the clearing platform 10 are not limited. In some embodiments, the clearing platform 10 may implement a clearing engine according to the methods provided in the embodiments of this application, and clear the clearing items based on the clearing engine.

[0038] In the above application scenario, the clearing platform 10 is provided with clearing control configuration information. The clearing control configuration information includes clearing rules corresponding to at least one business type, and the clearing rules include pricing rules and action switching instructions corresponding to the pricing rules, and the pricing rules are configured with priorities, thereby realizing the independent configuration of different clearing rules for different business types. Therefore, after the clearing platform 10 determines the target business type corresponding to the first clearing project based on the payment request of the user terminal 20, it can, based on the clearing control configuration information, first determine the pricing rule whose priority meets the preset priority conditions from the pricing rules corresponding to the target business type as the target pricing rule, match the target pricing rule with the first clearing project, obtain a matching result, and when it is determined based on the matching result that the target pricing rule is consistent with the first clearing project, use the target pricing rule to clear the first clearing project, and then, when the action switching instruction corresponding to the target pricing rule indicates switching to the next priority pricing rule, use the next priority pricing rule as the new target pricing rule, and continue to perform the step of matching the target pricing rule with the first clearing project.

[0039] It can be seen that in the above application scenario, the clearing platform 10 can configure different clearing rules for different types of business according to the actual business situation. Specifically, the clearing platform 10 can configure pricing rules and the priorities and action switching instructions corresponding to the pricing rules for different types of business according to the actual business situation, thereby achieving the purpose of flexibly controlling the first clearing project to flexibly switch clearing between multiple pricing rules according to its business type based on the clearing control configuration information, meeting the needs of normal business changes and improving the processing efficiency of the first clearing project.

[0040] The project data processing method, device, equipment, computer storage medium and program product in this application are described below.

[0041] A first aspect of the present application provides a project data processing method that can be executed by a clearing platform. Figure 2 This is a flowchart of a project data processing method provided in an embodiment of the first aspect of this application. Figure 2 As shown, the project data processing method may include steps S210-S250.

[0042] S210: Determine the target business type corresponding to the first liquidation item.

[0043] A primary clearing item refers to a transaction requiring resource transfer. It contains transaction-related information, such as the transaction ID, transaction amount, the payer's unique ID and account number, and the payee's unique merchant ID and account number. A primary clearing item can be any type of transaction, such as a card-not-present transaction.

[0044] The target business type refers to the transaction type to which the first clearing item belongs, such as card-not-present transaction type and credit card transaction type.

[0045] In some embodiments of the present application, in S210, in response to a payment request for a card-not-present transaction from a user terminal, it may be determined that the first settlement item is a card-not-present transaction type transaction.

[0046] In some other embodiments of the present application, in S210, in response to a payment request for a credit card transaction from the user end, it can be determined that the first settlement item is a transaction of a credit card transaction type.

[0047] S220: Based on the clearing control configuration information, determine the pricing rule whose priority meets the preset priority condition from the pricing rules corresponding to the target business type as the target pricing rule, the clearing control configuration information includes a clearing rule corresponding to at least one business type, the clearing rule includes a pricing rule and an action switching indication corresponding to the pricing rule, and the pricing rule is configured with a priority.

[0048] Pricing rules are rules within clearing rules that specify the fees payable by all parties to a transaction. For example, pricing rules may include rules regarding fee type (such as transaction fees) and fee structure (such as fixed fees, percentage fees, etc.). A clearing rule corresponding to a business type may include one or more pricing rules, each with a priority and action switch indication, and different pricing rules may contain different content. For example, in one scenario, the defined rules for card-not-present transactions include: a fixed fee of 0.5 yuan per transaction; a percentage fee of 0.5% of the transaction amount; a minimum fee of 1 yuan per transaction; and a maximum fee of 200 yuan per transaction. In another scenario, the defined rules for bank card transactions include: a fixed fee of 1 yuan per transaction; a percentage fee of 0.3% of the transaction amount; a minimum fee of 2 yuan per transaction; and a maximum fee of 100 yuan per transaction. It should be understood that these examples are merely illustrative of pricing rules and do not constitute limitations.

[0049] The priority of a pricing rule is used to determine the order in which pricing rules are prioritized when multiple pricing rules coexist. For example, a business type X has three pricing rules: the agreement pricing rule, the back-to-back pricing rule, and the back-to-back card issuance pricing rule. The agreement pricing rule has the highest priority, the back-to-back pricing rule has a medium priority, and the back-to-back card issuance pricing rule has a low priority. The priority information for a pricing rule can be set within or outside of the pricing rule, as long as there is a mapping relationship with the corresponding pricing rule and the priority of the pricing rule can be determined.

[0050] The preset priority condition specifies the priority of the pricing rule to be selected among multiple pricing rules corresponding to the business type. For example, in some application scenarios, the preset priority condition selects the pricing rule with the highest priority as the target pricing rule. Another example is that in some application scenarios, the preset priority condition selects the pricing rule with the highest priority based on the transaction information as the target pricing rule.

[0051] The action switching instruction is instruction information for controlling the processing logic of the liquidation to switch between different pricing rules or to end the liquidation. For example, the action switching instruction may include an instruction indicating switching to the next priority pricing rule or an instruction indicating ending the liquidation.

[0052] by Figure 3a Take the clearing control configuration information shown as an example, Figure 3aAs shown, a certain business type has three pricing rules: the negotiated pricing rule, the back-to-back pricing rule, and the back-to-back card issuance pricing rule. The negotiated pricing rule has a higher priority than the back-to-back pricing rule, which in turn has a higher priority than the back-to-back card issuance pricing rule. In an optional implementation, according to step S220, the pricing rule with the highest priority, the negotiated pricing rule, can be selected as the target pricing rule from among the pricing rules corresponding to the target business type.

[0053] S230: Match the target pricing rule with the first liquidation item to obtain a matching result.

[0054] Matching pricing rules with liquidation items involves obtaining the corresponding element parameter values ​​in the first liquidation item based on the element combination corresponding to the pricing rule, and then matching the element parameter values ​​with the pricing rule. This process aims to determine whether the first liquidation item complies with the pricing rule and, therefore, whether to use the pricing rule for liquidation.

[0055] Specifically, in some embodiments of the present application, matching the target pricing rule with the first liquidation item to obtain a matching result includes:

[0056] Based on the liquidation control configuration information, obtaining a target element combination corresponding to the target pricing rule, wherein the pricing rule in the liquidation control configuration information is configured with a corresponding element combination, and each element in the element combination is represented by an element unique identifier;

[0057] Obtaining the element parameter value corresponding to the element unique identifier of the target element combination in the first liquidation item;

[0058] The factor parameter value is matched with the target pricing rule to obtain a matching result.

[0059] A factor combination is a combination of one or more parameters used to define and apply pricing rules. A factor can be understood as a component within a factor combination. For example, in some application scenarios, the factor combination of a pricing rule may include customer type, transaction type, transaction amount, and so on. Customer type is one factor, and transaction type is another. A target factor combination is the combination of factors used to define and apply target pricing rules.

[0060] Element parameter values, that is, the values ​​corresponding to the elements. For example, the possible values ​​corresponding to the element customer type may include regular customer, new customer, old customer, etc.

[0061] The unique identifier of an element is a unique identifier assigned to each element in the clearing process to ensure that each element (such as the billing entity, lending direction, guarantee party, etc.) can be uniquely identified and matched. The unique identifier can be represented by numbers, letters and / or any other characters. In actual applications, the total size of each clearing transaction is about 10k, and there are hundreds or thousands of transaction information and elements. Each element may become a decisive condition for the institution's personalized clearing. Therefore, in order to facilitate the unified management of these elements in the front and back ends, these elements are given unique identifiers. For example, the unique identifiers of different elements can be expressed as numbers starting from A01 and arranged in sequence. For example: A01 is the unique identifier of the element of the transaction code, A02 is the unique identifier of the element of the code channel, and A03 is the unique identifier of the element of the business type.

[0062] There are no restrictions on how element unique identifiers can be arranged. For example, elements can be arranged in sequence, and the sequence of arrangement can be used to generate element numbers that serve as element unique identifiers. Element unique identifiers are scalable to allow for flexible addition of elements. For example, based on statistical analysis of all business parameters, the most frequently used sequence numbers can be prioritized as element unique identifiers.

[0063] In some embodiments of the present application, a template for arranging element unique identifiers may be provided, and the template is used to arrange the numbers in the element unique identifiers of different elements. Figure 3b The element arrangement diagram shown in the figure shows the numbers to which different types of elements such as institutional information, transaction elements, and transaction characteristics are mapped in the arrangement template. Based on the numbers to which these elements are mapped in the arrangement template, the element unique identifier corresponding to the element is further generated. For example, the elements included in a certain business include product type, transaction code, sending agency code, business type, merchant code, etc. The numbers corresponding to these elements are 001, 002, 003, 004, and 005, respectively. These numbers can be used as the unique identifier of the element. For example: the element combination formed based on these numbers can be expressed as 0040400106003080020300515. It can be understood that the element combination is also called virtual parameter in some application scenarios. The meaning of the virtual parameter is consistent with that of the element combination, which will not be repeated here.

[0064] In the embodiment of the present application, by arranging the elements, the transaction institution information, merchant information, terminal information and clearing party parsed from each domain and other elements have their own numbers and are embedded in the element unique identifier, which facilitates the mapping of the element unique identifier and the element parameter value.

[0065] The number of elements in the liquidation process is usually large, possibly reaching hundreds or thousands of elements. In order to avoid simple accumulation of elements, the number of parameters is reduced. In the embodiment of the present application, the elements are given element unique identifiers, which can be classified into one or more business categories through the element unique identifiers. In other words, an element unique identifier may belong to one business and another business at the same time. In this way, multiple business types can share the same element unique identifier, thereby effectively reducing the number of parameters.

[0066] For example, Figure 3c In the diagram showing the relationship between elements and services, elements can include element 11, element 12, element 13, element 21, element 22, and element 23. These elements can belong to the same service type or different service types. By merging elements by service type, it is possible to freely configure elements for various services.

[0067] According to the clearing control configuration information of the embodiment of the present application, different business types have different clearing rules, and different pricing rules in the clearing rules have different element combinations, so that the clearing of different business types can be flexibly distinguished as needed, and the elements are represented by unique element identifiers, which can greatly reduce the number of elements and reduce storage resources and cache occupancy.

[0068] By obtaining the element parameter value corresponding to the unique element identifier of the target element combination in the first liquidation project and matching the element parameter value with the target pricing rule, it is possible to accurately determine whether the first liquidation project is applicable to liquidation according to the target pricing rule, thereby ensuring the accuracy of liquidation.

[0069] Using the previous example, for example, if the first settlement item is a card-not-present transaction, such as Figure 3a The clearing control configuration information shown selects the pricing rule "Agreement Pricing Rule" with the highest priority as the target pricing rule from the pricing rules corresponding to the target business type. Then, according to step S230, the element parameter value corresponding to the element unique identifier in the element combination corresponding to the "Agreement Pricing Rule" in the cardless transaction can be obtained, and the obtained element parameter value is matched with the definition corresponding to the corresponding element unique identifier in the "Agreement Pricing Rule" to determine whether the "Agreement Pricing Rule" is consistent with the first clearing item.

[0070] More specifically, if the first clearing item is a card-not-present transaction, assuming that the highest priority pricing rule corresponding to card-not-present transactions in the clearing control configuration information is the acquiring / issuing agreement pricing rule, then, according to the clearing control configuration information, the element combination corresponding to the acquiring / issuing agreement pricing rule includes: the charging entity element, the debit / credit direction element, the cover party element, and the charging rule element. By searching the business debit / credit direction determination table, the charging entity, debit / credit direction, and cover party for the transaction can be determined. After determining the element parameter values ​​for the charging entity element, debit / credit direction element, and cover party element for the transaction, the element parameter values ​​for the charging entity element, debit / credit direction element, and cover party element for the card-not-present transaction are then matched against the definitions of the relevant elements in the acquiring / issuing agreement pricing rule. If the relevant element definitions are met, the card-not-present transaction complies with the acquiring / issuing agreement pricing rule. If the relevant element definitions are not met, the card-not-present transaction does not comply with the acquiring / issuing agreement pricing rule. For example, the pricing rules of the acquiring / issuing agreement may require that the collection entity is the acquiring and clearing entity, the lending direction is D, and the guarantee party is the issuing and clearing entity, etc.; in the pricing rules of the cardless issuing agreement, which is a supplementary content to the pricing rules of the acquiring / issuing agreement, it may be required that the collection entity is the issuing and clearing entity, the lending direction is C, and the guarantee party is XX, etc.

[0071] In some embodiments of the present application, the pricing rule has corresponding element priority control information, and the element priority control information includes an element priority order corresponding to an element unique identifier of one or more elements.

[0072] Accordingly, step S230 matches the factor parameter value with the target pricing rule to obtain a matching result, including:

[0073] The element parameter values ​​of the elements in the target element combination are matched with the target pricing rules according to the element priority order in the element priority control information to obtain a matching result.

[0074] Among them, there is no limit to the setting method of the element priority control information, and it can be set in any field of the settlement rules. For example, it can be set in the element combination or in the pricing rules. This application does not impose any restrictions on this, as long as the element priority control information has a mapping relationship with the corresponding pricing rules.

[0075] For example, if the element priority control information corresponding to the acquiring / issuing agreement pricing rules includes the priority order of the billing entity element, the lending / borrowing direction element, and the guarantee party element, where the billing entity element has the highest priority, the lending / borrowing direction element has a middle priority, and the guarantee party element has the lowest priority, then the element parameter values ​​of the billing entity element, the lending / borrowing direction element, and the guarantee party element can be matched with the relevant definitions of the acquiring / issuing agreement pricing rules in this order: the billing entity element has the highest priority, the lending / borrowing direction element has a middle priority, and the guarantee party element has the lowest priority.

[0076] In the settlement control configuration information of the method, the pricing rule has corresponding element priority control information, and the element priority control information is used to describe the priority order of the elements matched with the pricing rule, so that when the first settlement item is matched with the pricing rule, it can be matched based on the order of element priority, and there is no need to determine the priority of element matching by the sorting position of the element in the element combination, thereby avoiding the risk of errors when the element is personalized modified and facilitating flexible personalized modification of the element.

[0077] It should be understood that since the pricing rules in the embodiments of the present application have corresponding element priority control information, the element parameter values ​​of key elements can be quickly queried based on the element priority without having to query other unimportant element parameter values, so that the settlement items can be quickly matched with the pricing rules, thereby improving settlement efficiency; and the reduction in the number of elements also reduces the number of element queries; in addition, the action switching indication specifies the pricing rule of the next priority to be switched to, which further reduces the number of parameter queries and improves settlement efficiency.

[0078] Step 240: When it is determined according to the matching result that the target pricing rule is consistent with the first liquidation item, liquidate the first liquidation item using the target pricing rule.

[0079] Continuing with the previous example, if the aforementioned card-not-present transaction is consistent with the pricing rules of the card-not-present issuance agreement, we can further determine the billing rules in the pricing rules of the card-not-present issuance agreement and the elements corresponding to the billing rules, obtain the element parameter values ​​corresponding to the elements corresponding to the billing rules in the card-not-present transaction, perform billing calculations according to the billing rules, and obtain the settlement results of the card-not-present transaction.

[0080] Step 250: When the action switching indication corresponding to the target pricing rule indicates switching to the next priority pricing rule, the next priority pricing rule is used as the new target pricing rule, and the step of matching the target pricing rule with the first liquidation item is continued.

[0081] The action switching instruction is instruction information used to control the processing logic of the settlement to switch between different pricing rules or to end the settlement.

[0082] In some embodiments of the present application, the action switching indication may include:

[0083] a first action switching instruction corresponding to the case where the target pricing rule matches the first settlement item, the first action switching instruction including: an instruction indicating switching to a pricing rule of a first priority, or an instruction indicating terminating settlement, the first priority being lower in priority order than the target pricing rule;

[0084] The second action switching indication corresponding to the case where the target pricing rule does not conform to the first settlement item includes: an indication representing switching to a pricing rule of a second priority, or an indication of ending settlement, and the priority order of the second priority is lower than the priority of the target pricing rule.

[0085] The first priority and the second priority may be the same or different.

[0086] Following the previous example, combined Figure 3a The clearing control configuration information shown, the action switching instructions corresponding to the pricing rules of the cardless issuance agreement may include:

[0087] In the event of a failure to match a transaction, the liquidation is completed and returned;

[0088] In the case of successful matching with card-not-present transactions, after completing the settlement of the pricing rules of the card-not-present issuance agreement, switch to the back-to-back acquiring pricing rules and continue to match the card-not-present transactions with the back-to-back acquiring pricing rules.

[0089] In this embodiment, an action switching indication is given to indicate the next priority pricing rule to be switched or the end of settlement return in the case of successful or unsuccessful matching, thereby enabling the first settlement project to be flexibly controlled based on the settlement control configuration information to flexibly switch settlement between multiple pricing rules according to the type of business to which it belongs, thereby meeting the needs of normal business changes and improving the processing efficiency of the first settlement project.

[0090] Figure 4 This is a flowchart of a project data processing method provided by another embodiment of the first aspect of the present application. Figure 4 As shown, the project data processing method may include steps S210-S260. Figure 2 The difference from the embodiment shown is that the element unique identifier also has a parameter value length field, and the parameter value length field is used to store the length information of the corresponding element parameter value. Figure 2 In the embodiment shown in S230, Figure 4 In the embodiment shown, the specific performance is S2301, S2302 and S2303, and the method further includes step S260.

[0091] S210: Determine the target business type corresponding to the first liquidation item.

[0092] S220: Based on the liquidation control configuration information, determine, from the pricing rules corresponding to the target business type, a pricing rule whose priority meets a preset priority condition as a target pricing rule.

[0093] S2301: Based on the liquidation control configuration information, obtain a target element combination corresponding to the target pricing rule, wherein the pricing rule in the liquidation control configuration information is configured with a corresponding element combination, and a single element in the element combination is represented by an element unique identifier.

[0094] S2302: Obtain the element parameter value corresponding to the element unique identifier of the target element combination in the first liquidation item.

[0095] S2303: Match the factor parameter value with the target pricing rule to obtain a matching result.

[0096] S240: When it is determined according to the matching result that the target pricing rule is consistent with the first liquidation item, liquidate the first liquidation item using the target pricing rule.

[0097] S250: When the action switching indication corresponding to the target pricing rule indicates switching to a next priority pricing rule, the next priority pricing rule is used as a new target pricing rule, and the step of matching the target pricing rule with the first liquidation item is continued.

[0098] S260: In response to an element sequence adjustment request, the order of the element unique identifiers in the element combination is adjusted according to the element sequence adjustment request, and the order of the element parameter values ​​in the actual business parameters corresponding to the element combination is adjusted accordingly based on the order and the parameter value length field of the element unique identifier. The element unique identifiers in the element combination and the element parameter values ​​in the actual business parameters are in a one-to-one correspondence.

[0099] The parameter value length field is set in the element unique identifier. It is understandable that the parameter value lengths of different elements may be different. Therefore, this embodiment sets the parameter value length field in the element unique identifier. When relevant operation and maintenance personnel need to adjust parameters, they can quickly and accurately adjust the position of the element parameter value in the element combination based on the parameter value length in the element unique identifier.

[0100] For example, Figure 3d The element combination diagram shown shows the element combination corresponding to a certain business type, including: product type, transaction code, sending institution code, business type, merchant code, and other elements. The corresponding numbers for these elements are 001, 002, 003, 004, and 005, respectively, and the corresponding parameter value length fields are 04, 06, 08, 03, and 15, respectively. The element unique identifiers for these elements are composed of their corresponding numbers and parameter value length fields, resulting in the element combination 0040400106003080020300515. Assume that the actual business parameter value corresponding to this element combination is: F001CPLX0100010054S22ABCDEFGHIJKLMNO. Then, when an element sequence adjustment request is received, requesting to adjust the order of some elements, for example, the element numbered 005 originally at the last position is requested to be adjusted to the second element in front, etc., then according to the element sequence adjustment request, the order of the element unique identifiers is adjusted, and based on the order and the parameter value length field of the element unique identifier, the order of the element parameter values ​​in the actual business parameters corresponding to the element combination is adjusted accordingly, so as to obtain the following Figure 3e For the combination of factors shown, the parameter value of the actual business parameter after adjustment is: F001ABCDEFGHIJKLMNOS2200010054CPLX01.

[0101] It can be seen that, since the clearing control configuration information of this embodiment includes a parameter value length field for the element unique identifier, which is used to store the length information of the corresponding element parameter value, the method can respond to an element sequence adjustment request, adjust the order of the element unique identifiers in the element combination according to the element sequence adjustment request, and adjust the order of the element parameter values ​​in the actual business parameters corresponding to the element combination based on the parameter value length field of the element unique identifier, thereby achieving the purpose of flexible and personalized modification of the elements. Moreover, this modification method can achieve corresponding synchronous modification of the actual business parameters, without parameter modification errors, without the need to test the parameters, and without bringing risks to the business parameters. This simplifies the operation and maintenance of the parameters, while greatly reducing the risk of parameter operation and maintenance.

[0102] It should be noted that this Figure 4 Parts not described in detail in the embodiments shown can be referred to Figure 2 The related descriptions of S210-S250 are not repeated here. In addition, there are multiple optional implementations for the execution order between S260 and other steps, which are determined according to the actual application scenario. For example, S260 can be executed before S210 or after S250.

[0103] Figure 5This is a flowchart of a project data processing method provided by another embodiment of the first aspect of the present application. Figure 5 As shown, the project data processing method may include S201 to S250. Figure 2 The embodiment shown is different in that Figure 2 In the embodiment shown in S230, Figure 5 In the embodiment shown, it is specifically manifested as S2301, S2302 and S2303, and the method further includes steps S201-S204.

[0104] S201: In response to a service setting request, determine a corresponding service type to be set according to the service setting request.

[0105] Among them, the service setting request is a request for setting the element combination corresponding to different types of services. For example, Figure 3f The business settings interface diagram shown here includes the business type name, business priority, and entry for business definition rules. The business definition rules entry can be understood as the entry for initiating a business settings request. When the clearing platform administrator clicks the "Click to View" button, the interface for setting elements is displayed.

[0106] S202: Receive unique element identifiers and element priorities corresponding to one or more elements to be set for the type of service to be set.

[0107] Continuing with the previous example, when entering the feature setting interface, a drop-down menu or text box can be displayed for selecting or manually entering the feature name, feature unique identifier, and feature priority.

[0108] S203: Generate an element combination corresponding to the business type to be set according to the element unique identifier and element priority corresponding to the one or more elements to be set.

[0109] For example, a button such as "Generate Element Combination" or "Confirm Generation" may be displayed in the interface for setting elements, and relevant operation and maintenance personnel may confirm the generation of the element combination by clicking the button.

[0110] S204: Setting the element combination corresponding to the business type to be set into the clearing control configuration information.

[0111] For example, the generated element combination can be saved to Figure 3a In the element combination configuration area of ​​the liquidation control configuration information shown.

[0112] S210: Determine the target business type corresponding to the first liquidation item.

[0113] S220: Based on the clearing control configuration information, determine the pricing rule whose priority meets the preset priority condition from the pricing rules corresponding to the target business type as the target pricing rule, the clearing control configuration information includes a clearing rule corresponding to at least one business type, the clearing rule includes a pricing rule and an action switching indication corresponding to the pricing rule, and the pricing rule is configured with a priority.

[0114] S2301: Based on the liquidation control configuration information, obtain a target element combination corresponding to the target pricing rule, wherein the pricing rule in the liquidation control configuration information is configured with a corresponding element combination, and a single element in the element combination is represented by an element unique identifier.

[0115] S2302: Obtain the element parameter value corresponding to the element unique identifier of the target element combination in the first liquidation item.

[0116] S2303: Match the factor parameter value with the target pricing rule to obtain a matching result.

[0117] S240: When it is determined according to the matching result that the target pricing rule is consistent with the first liquidation item, liquidate the first liquidation item using the target pricing rule.

[0118] S250: When the action switching indication corresponding to the target pricing rule indicates switching to a next priority pricing rule, the next priority pricing rule is used as a new target pricing rule, and the step of matching the target pricing rule with the first liquidation item is continued.

[0119] It should be noted that this Figure 5 Parts not described in detail in the embodiments shown can be referred to Figure 2 The related descriptions of S210-S250 shown are not repeated here. In addition, there are multiple optional implementations for the execution order between S201-S204 and other steps, which can be determined according to the actual application scenario. For example, S201-S204 can be executed before S210 or after S250.

[0120] Through this embodiment, relevant operation and maintenance personnel can initiate business setting requests, and independently and flexibly set the element combination and element priority corresponding to the business type. The elements can be arranged and easily reshaped, and the reshaping is not prone to errors, and there will be no risks caused by the existing parameters, which can meet the increasingly rich personalized needs.

[0121] Figure 6 This is a flowchart of a project data processing method provided in yet another embodiment of the first aspect of this application. Figure 6As shown, the project data processing method further includes steps S205-S207. Among them:

[0122] S205: In response to the pricing rule setting request, determine a corresponding service type to be set according to the pricing rule setting request.

[0123] For example, following the previous example, when the relevant operation and maintenance personnel initiate a service setting request, they will enter the setting element interface, which may include a pricing rule setting entry. The relevant operation and maintenance personnel can initiate a pricing rule setting request through the pricing rule setting entry.

[0124] S206: Receive the pricing rule set for the service type to be set, the priority corresponding to the pricing rule, and / or the action switching instruction corresponding to the pricing rule.

[0125] For example, when entering the pricing rule setting entrance, interface components for selecting pricing rules and setting the corresponding priorities of pricing rules can be displayed, so that relevant operation and maintenance personnel can select pricing rules, the corresponding priorities of pricing rules and / or the action switching instructions corresponding to pricing rules through these interface components.

[0126] The setting of the action switching instruction includes the setting of specific instruction contents, such as the pricing rule of the next priority to be switched, the conditions to be met for switching, and the like.

[0127] S207: Setting the pricing rule of the business type to be set, the priority corresponding to the pricing rule and / or the action switching indication corresponding to the pricing rule into the clearing control configuration information.

[0128] For example, the pricing rules and corresponding priorities can be saved in Figure 3a The Clearing Control configuration information is shown in the Pricing Rules Configuration area.

[0129] Through this embodiment, relevant operation and maintenance personnel can initiate a pricing rule setting request, and independently and flexibly set the pricing rules corresponding to the business type, the priority corresponding to the pricing rule and / or the action switching indication corresponding to the pricing rule, thereby achieving the purpose of flexibly controlling the first clearing project to flexibly switch clearing between multiple pricing rules according to its business type based on the clearing control configuration information, meeting the needs of normal business changes and improving the processing efficiency of the first clearing project.

[0130] It should be noted that this Figure 6 Parts not described in detail in the embodiments shown can be referred to Figure 2The related descriptions of S210-S250 shown are not repeated here. In addition, there are multiple optional implementations for the execution order between S205-S207 and other steps, which can be determined according to the actual application scenario. For example, S205-S207 can be executed before S210 or after S250.

[0131] Figure 7 This is a flowchart of a project data processing method provided in yet another embodiment of the first aspect of this application. Figure 7 As shown, the project data processing method may include S210 to S250. Figure 2 The embodiment shown is different in that Figure 2 In the embodiment shown in S210, Figure 7 In the embodiment shown, it is specifically manifested as S2101 and S2102.

[0132] S2101: Match multiple business types with the first settlement item according to the business priority order of the multiple business types to obtain a business matching result.

[0133] For example, Figure 3f The business setting interface diagram shown in the figure includes: the name of the business type and the business priority. The business priority can be set by the relevant operation and maintenance personnel. Figure 3f As shown in the business priority, when the first settlement item is received, the first settlement item can be matched with the large merchant agreement pricing business in the order of business priority to determine whether the first settlement item belongs to the large merchant agreement pricing business. If so, the first settlement item belongs to the large merchant agreement pricing business. If not, continue to match it with the card-not-present business, and so on.

[0134] The business matching result may include a match or a mismatch.

[0135] S2102: Determine the target business type corresponding to the first liquidation item according to the business matching result.

[0136] S220: Based on the clearing control configuration information, determine the pricing rule whose priority meets the preset priority condition from the pricing rules corresponding to the target business type as the target pricing rule, the clearing control configuration information includes a clearing rule corresponding to at least one business type, the clearing rule includes a pricing rule and an action switching indication corresponding to the pricing rule, and the pricing rule is configured with a priority.

[0137] S230: Match the target pricing rule with the first liquidation item to obtain a matching result.

[0138] S240: When it is determined according to the matching result that the target pricing rule is consistent with the first liquidation item, liquidate the first liquidation item using the target pricing rule.

[0139] S250: When the action switching indication corresponding to the target pricing rule indicates switching to a next priority pricing rule, the next priority pricing rule is used as a new target pricing rule, and the step of matching the target pricing rule with the first liquidation item is continued.

[0140] In this embodiment, by setting business priorities corresponding to different business types and performing business matching based on the order of business priorities, it is possible to more accurately determine the business to which the liquidation project belongs and perform liquidation more accurately.

[0141] Figure 8 This is a flowchart of a project data processing method provided in yet another embodiment of the first aspect of this application. Figure 8 As shown, the data processing method of the project includes S2001-S2803. Figure 2 The embodiment shown is different in that Figure 8 The project data processing method shown may further include step S2001 before step S210. The method may also include steps S2801 to S2803.

[0142] S2001: In response to receiving a transaction request, distinguishing between a first settlement item and a second settlement item corresponding to the transaction request, wherein the second settlement item corresponds to a preset traditional settlement rule.

[0143] In some application scenarios, a transaction request may require different clearing methods for different roles. To address the varying clearing methods employed by different roles, such as institutions and merchants, in these scenarios, this embodiment enables role-based compatibility within the clearing engine. Specifically, one clearing method may be a pre-set traditional clearing rule, while another may be a back-to-back pricing clearing rule implemented based on the clearing control configuration information in this embodiment.

[0144] Based on this, a transaction request may be divided into multiple clearing items. Some clearing items (e.g., clearing on the acquiring side) can be cleared using pre-set traditional clearing rules, while other clearing items (e.g., clearing on the issuing side) can be cleared using the back-to-back pricing clearing rules implemented by the clearing control configuration information in the embodiments of this application.

[0145] S2801: Performing liquidation on the second liquidation item based on the preset traditional liquidation rule.

[0146] In this embodiment, when the action switch in step S250 indicates the end of clearing, the process proceeds to S2802.

[0147] S2802: Obtain a first liquidation result of the first liquidation project and a second liquidation result of the second liquidation project.

[0148] S2803: Summarize the first settlement result and the second settlement result to obtain a settlement result of the transaction request.

[0149] The aggregation method is not limited and can be set based on actual application needs. For example, aggregation can be achieved through concatenation, merging, and saving. The aggregated liquidation results can be stored in a liquidation platform, server, or database. For example, the liquidation results can be recorded in a detailed table in a database.

[0150] Taking the first liquidation project as a back-to-back liquidation project and the second liquidation project as a traditional liquidation project as an example, Figure 9 FIG. 1 is a flowchart of a project data processing method provided by another embodiment of the first aspect of the present application. Figure 9 As shown, the data processing method of this project includes S910-S970. Among them:

[0151] S910: Transaction preprocessing.

[0152] The transaction pre-processing step may include extracting any information required for settlement, and distinguishing items of different settlement methods.

[0153] S920: Settlement using the default traditional settlement method.

[0154] The default traditional liquidation method can be Figure 2-Figure 8 The settlement method in any embodiment is different from other traditional settlement methods that cannot personalize the elements and pricing rules. For example, in some preset traditional settlement methods, the element combination can be constant and cannot be programmed, and the pricing rules can require matching according to the order of the element combination from left to right.

[0155] S930: Settlement using back-to-back settlement method.

[0156] The back-to-back liquidation method can be understood as the liquidation of this application. Figure 2-Figure 8 The clearing and processing method of the personalized arrangement elements and pricing rules of any embodiment shown.

[0157] S940: Extraction of clearing information on the acquiring side.

[0158] This step can be understood as the settlement of the acquiring party's role in a transaction.

[0159] S950: Card issuance and settlement information extraction.

[0160] This step can be understood as the settlement of the card issuer's role in a transaction.

[0161] S960: Processing of liquidation results.

[0162] This step can be understood as the summary processing of the settlement results of two different settlement methods.

[0163] S970: Liquidation completed.

[0164] This embodiment, by supporting different clearing methods for different roles, can flexibly control the first clearing item to switch between multiple pricing rules according to its business type based on the clearing control configuration information, thereby meeting the needs of normal business changes and taking into account the lack of perception of certain roles.

[0165] A second aspect of the present application provides a project data processing device. Figure 10 This is a schematic diagram of the structure of a project data processing device provided in an embodiment of the second aspect of this application. Figure 10 As shown, the project data processing device 1000 may include a business type determination module 1010, a rule determination module 1020, a rule matching module 1030, a liquidation execution module 1040 and a rule switching module 1050. Among them:

[0166] A business type determination module 1010 is configured to determine a target business type corresponding to the first liquidation project;

[0167] A rule determination module 1020 is configured to determine, based on the clearing control configuration information, a pricing rule whose priority satisfies a preset priority condition from pricing rules corresponding to the target business type, as a target pricing rule, wherein the clearing control configuration information includes a clearing rule corresponding to at least one business type, the clearing rule including a pricing rule and an action switching indication corresponding to the pricing rule, and the pricing rule is configured with a priority;

[0168] A rule matching module 1030 is configured to match the target pricing rule with the first liquidation item to obtain a matching result;

[0169] a liquidation execution module 1040 configured to, if it is determined according to the matching result that the target pricing rule is consistent with the first liquidation item, liquidate the first liquidation item using the target pricing rule;

[0170] The rule switching module 1050 is configured to, when the action switching indication corresponding to the target pricing rule indicates switching to the next priority pricing rule, use the next priority pricing rule as the new target pricing rule and continue to perform the step of matching the target pricing rule with the first liquidation item.

[0171] Optionally, the rule matching module may include:

[0172] a combination acquisition submodule, configured to acquire, based on the liquidation control configuration information, a target element combination corresponding to the target pricing rule, wherein the pricing rule in the liquidation control configuration information is configured with a corresponding element combination, and a single element in the element combination is represented by an element unique identifier;

[0173] A parameter value acquisition submodule, configured to acquire an element parameter value corresponding to the element unique identifier of the target element combination in the first liquidation item;

[0174] The matching submodule is used to match the factor parameter value with the target pricing rule to obtain a matching result.

[0175] Optionally, the pricing rule has corresponding element priority control information, wherein the element priority control information includes an element priority order corresponding to an element unique identifier of one or more elements. The matching submodule is configured to match the element parameter values ​​of the elements in the target element combination with the target pricing rule according to the element priority order in the element priority control information to obtain a matching result.

[0176] Optionally, the element unique identifier further comprises a parameter value length field, wherein the parameter value length field is used to store the length information of the corresponding element parameter value.

[0177] An element adjustment module is used to respond to an element sequence adjustment request, adjust the order of the element unique identifiers in the element combination according to the element sequence adjustment request, and adjust the order of the element parameter values ​​in the actual business parameters corresponding to the element combination based on the order and the parameter value length field of the element unique identifier. The element unique identifier in the element combination and the element parameter value in the actual business parameter are in a one-to-one correspondence.

[0178] Optionally, the device further comprises:

[0179] A service setting response module, configured to respond to a service setting request and determine a corresponding service type to be set according to the service setting request;

[0180] An element receiving and setting module, configured to receive element unique identifiers and element priorities corresponding to one or more elements to be set for the type of service to be set;

[0181] An element generation module, configured to generate an element combination corresponding to the type of service to be set according to the element unique identifier and element priority corresponding to the one or more elements to be set;

[0182] The element configuration module is used to set the element combination corresponding to the business type to be set into the liquidation control configuration information.

[0183] Optionally, the device further comprises:

[0184] A rule setting response module, configured to respond to a pricing rule setting request and determine a corresponding business type to be set according to the pricing rule setting request;

[0185] A rule setting receiving module, configured to receive a pricing rule set for the service type to be set, a priority corresponding to the pricing rule, and / or an action switching instruction corresponding to the pricing rule;

[0186] The rule configuration module is used to set the pricing rule of the business type to be set, the priority corresponding to the pricing rule and / or the action switching indication corresponding to the pricing rule into the liquidation control configuration information.

[0187] Optionally, the business category determination module is configured to match multiple business categories with the first liquidation project in order of their business priorities to obtain a business matching result, and determine a target business category corresponding to the first liquidation project based on the business matching result.

[0188] Optionally, the device further comprises:

[0189] The role distinguishing module is configured to, in response to receiving a transaction request, distinguish between a first settlement item and a second settlement item corresponding to the transaction request, wherein the second settlement item corresponds to a preset traditional settlement rule.

[0190] The traditional liquidation module is configured to perform liquidation on the second liquidation item based on the preset traditional liquidation rules.

[0191] The result aggregation module is configured to obtain a first settlement result of the first settlement item and a second settlement result of the second settlement item, and aggregate the first settlement result and the second settlement result to obtain a settlement result of the transaction request.

[0192] Through the device provided in the embodiment of the present application, different clearing rules can be configured for different types of business according to the actual business situation. Specifically, pricing rules and the priorities and action switching instructions corresponding to the pricing rules can be configured for different types of business according to the actual business situation, thereby achieving the purpose of flexibly controlling the first clearing project to flexibly switch clearing between multiple pricing rules according to the business type to which it belongs based on the clearing control configuration information, meeting the needs of normal business changes and improving the processing efficiency of the first clearing project.

[0193] The third aspect of the present application also provides a project data processing device. Figure 11 This is a schematic diagram of the structure of a project data processing device provided in one embodiment of the present application. Figure 11 As shown, the project data processing device 1100 includes a memory 1101 , a processor 1102 , and a computer program stored in the memory 1101 and executable on the processor 1102 .

[0194] In some examples, the processor 1102 may include a central processing unit (CPU), or an application-specific integrated circuit (ASIC), or may be configured to implement one or more integrated circuits of the embodiments of the present application.

[0195] The memory 1101 may include a large-capacity memory for data or instructions. By way of example and not limitation, the memory 1101 may include a hard disk drive (HDD), a floppy disk drive, a flash memory, an optical disk, a magneto-optical disk, a magnetic tape, or a universal serial bus (USB) drive, or a combination of two or more of these.

[0196] The memory 1101 may include a read-only memory (ROM), a random access memory (RAM), a magnetic disk storage medium device, an optical storage medium device, a flash memory device, an electrical, optical or other physical / tangible memory storage device. Therefore, generally, the memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., a memory device) encoded with software including computer-executable instructions, and when the software is executed (e.g., by one or more processors), it is operable to perform the operations described with reference to the project data processing method according to the embodiments of the present application.

[0197] The processor 1102 reads the executable program code stored in the memory 1101 to run a computer program corresponding to the executable program code, so as to implement the project data processing method in the above embodiment.

[0198] In some examples, the project data processing device 1100 may further include a communication interface 1103 and a bus 1104. Figure 11 As shown, the memory 1101 , the processor 1102 , and the communication interface 1103 are connected via a bus 1104 and communicate with each other.

[0199] The communication interface 1103 is mainly used to implement communication between the modules, devices, units and / or equipment in the embodiment of the present application. Input devices and / or output devices can also be connected through the communication interface 1103.

[0200] The bus 1104 includes hardware, software, or both that couples the components of the project data processing device 1100 to each other. By way of example, and not limitation, the bus 1104 may include an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), a HyperTransport (HT) interconnect, an Industry Standard Architecture (ISA) bus, an InfiniBand interconnect, a Low Pin Count (LPC) bus, a memory bus, a Micro Channel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-E) bus, a Serial Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association Local Bus (VLB) bus, or other suitable buses, or a combination of two or more of the above. Where appropriate, the bus 1104 may include one or more buses. Although embodiments herein describe and illustrate a particular bus, this application contemplates any suitable bus or interconnect.

[0201] In a fourth aspect, the present application provides a computer-readable storage medium having computer program instructions stored thereon. When the computer program instructions are executed by a processor, the project data processing method in the above-mentioned embodiment can be implemented, and the same technical effect can be achieved. To avoid repetition, the above-mentioned computer-readable storage medium may include a non-transitory computer-readable storage medium, such as a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, etc., which is not limited here.

[0202] The present application provides a computer program product, which includes a computer program. When the computer program is executed by a processor, it implements the project data processing method in the above embodiment and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0203] It should be understood that the various embodiments in this specification are described in a progressive manner, and the same or similar parts between the various embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. For device embodiments, equipment embodiments, and computer-readable storage medium embodiments, the relevant parts can be referred to the description part of the method embodiment. This application is not limited to the specific steps and structures described above and shown in the figures. Those skilled in the art can make various changes, modifications and additions, or change the order between the steps after understanding the spirit of this application. In addition, for the sake of brevity, a detailed description of known method technologies is omitted here.

[0204] Aspects of the present application have been described above with reference to the flowcharts and / or block diagrams of the methods, devices (systems) and computer program products according to the embodiments of the present application. It should be understood that each box in the flowchart and / or block diagram and the combination of each box in the flowchart and / or block diagram can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer or other programmable data processing device to produce a machine so that these instructions executed via the processor of the computer or other programmable data processing device enable the implementation of the function / action specified in one or more boxes of the flowchart and / or block diagram. This processor can be, but is not limited to, a general-purpose processor, a special-purpose processor, a special application processor or a field programmable logic circuit. It is also understood that each box in the block diagram and / or the flowchart and the combination of the boxes in the block diagram and / or the flowchart can also be implemented by the dedicated hardware that performs the specified function or action, or can be implemented by the combination of dedicated hardware and computer instructions.

[0205] Those skilled in the art should understand that the above embodiments are illustrative rather than restrictive. Different technical features appearing in different embodiments can be combined to achieve beneficial effects. Based on a study of the drawings, the specification and the claims, those skilled in the art should be able to understand and implement other variations of the disclosed embodiments. In the claims, the term "comprising" does not exclude other devices or steps; the quantifier "one" does not exclude a plurality; the terms "first" and "second" are used to identify names rather than to indicate any specific order. Any figure marks in the claims should not be understood as limiting the scope of protection. The functions of multiple parts appearing in the claims can be implemented by a separate hardware or software module. The fact that certain technical features appear in different dependent claims does not mean that these technical features cannot be combined to achieve beneficial effects.

Claims

1. A project data processing method, characterized in that: include: Determine the target business type corresponding to the first liquidation project; determining, based on the clearing control configuration information, from pricing rules corresponding to the target business type, a pricing rule whose priority satisfies a preset priority condition as a target pricing rule, wherein the clearing control configuration information includes a clearing rule corresponding to at least one business type, the clearing rule including a pricing rule and an action switching indication corresponding to the pricing rule, and the pricing rule is configured with a priority; Matching the target pricing rule with the first liquidation item to obtain a matching result; If it is determined according to the matching result that the target pricing rule is consistent with the first liquidation item, liquidating the first liquidation item using the target pricing rule; When the action switching indication corresponding to the target pricing rule indicates switching to the next priority pricing rule, the next priority pricing rule is used as a new target pricing rule, and the step of matching the target pricing rule with the first liquidation item is continued.

2. The method according to claim 1, characterized in that The matching of the target pricing rule with the first liquidation item to obtain a matching result includes: Based on the liquidation control configuration information, obtaining a target element combination corresponding to the target pricing rule, wherein the pricing rule in the liquidation control configuration information is configured with a corresponding element combination, and each element in the element combination is represented by an element unique identifier; Obtaining the element parameter value corresponding to the element unique identifier of the target element combination in the first liquidation item; The factor parameter value is matched with the target pricing rule to obtain a matching result.

3. The method according to claim 2, characterized in that The pricing rule has corresponding element priority control information, wherein the element priority control information includes an element priority order corresponding to an element unique identifier of one or more elements; The matching of the factor parameter value with the target pricing rule to obtain a matching result includes: The element parameter values ​​of the elements in the target element combination are matched with the target pricing rules according to the element priority order in the element priority control information to obtain a matching result.

4. The method according to claim 3, characterized in that The element unique identifier also has a parameter value length field, and the parameter value length field is used to store the length information of the corresponding element parameter value; The method further comprises: In response to an element sequence adjustment request, the order of the element unique identifiers in the element combination is adjusted according to the element sequence adjustment request, and the order of the element parameter values ​​in the actual business parameters corresponding to the element combination is adjusted accordingly based on the order and the parameter value length field of the element unique identifier. The element unique identifiers in the element combination and the element parameter values ​​in the actual business parameters are in a one-to-one correspondence.

5. The method according to claim 3, characterized in that The method further comprises: In response to the service setting request, determining a corresponding service type to be set according to the service setting request; Receive unique element identifiers and element priorities corresponding to one or more elements to be set for the type of service to be set; generating, according to the element unique identifiers and element priorities corresponding to the one or more elements to be set, an element combination corresponding to the type of service to be set; The element combination corresponding to the business type to be set is set into the liquidation control configuration information.

6. The method according to any one of claims 1 to 5, characterized in that The action switching instruction includes: a first action switching instruction corresponding to the case where the target pricing rule matches the first settlement item, the first action switching instruction including: an instruction indicating switching to a pricing rule of a first priority, or an instruction indicating terminating settlement, the first priority being lower in priority order than the target pricing rule; The second action switching indication corresponding to the case where the target pricing rule is inconsistent with the first settlement item includes: an indication representing switching to a pricing rule of a second priority, or an indication of ending settlement, and the priority order of the second priority is lower than the priority of the target pricing rule.

7. The method according to any one of claims 1 to 5, characterized in that The method further comprises: In response to a pricing rule setting request, determining a corresponding business type to be set according to the pricing rule setting request; receiving a pricing rule set for the service type to be set, a priority corresponding to the pricing rule, and an action switching instruction corresponding to the pricing rule; The pricing rule of the business type to be set, the priority corresponding to the pricing rule, and the action switching indication corresponding to the pricing rule are set in the clearing control configuration information.

8. The method according to any one of claims 1 to 5, characterized in that Determining the target business type corresponding to the first liquidation project includes: matching the multiple business types with the first clearing item according to a business priority order of the multiple business types to obtain a business matching result; According to the business matching result, a target business type corresponding to the first liquidation item is determined.

9. The method according to any one of claims 1 to 5, characterized in that Before determining the target business type corresponding to the first liquidation item, the method further includes: in response to receiving a transaction request, distinguishing between a first liquidation item and a second liquidation item corresponding to the transaction request, wherein the second liquidation item corresponds to a preset traditional liquidation rule; The method further comprises: performing liquidation on the second liquidation item based on the preset traditional liquidation rules; Obtaining a first liquidation result of the first liquidation project and a second liquidation result of the second liquidation project; The first settlement result and the second settlement result are aggregated to obtain a settlement result of the transaction request.

10. A project data processing device, characterized in that: The device comprises: A business category determination module, configured to determine a target business category corresponding to the first liquidation project; a rule determination module configured to determine, based on the clearing control configuration information, a pricing rule whose priority satisfies a preset priority condition from pricing rules corresponding to the target business type as a target pricing rule, wherein the clearing control configuration information includes a clearing rule corresponding to at least one business type, the clearing rule including a pricing rule and an action switching indication corresponding to the pricing rule, and the pricing rule is configured with a priority; a rule matching module, configured to match the target pricing rule with the first liquidation item to obtain a matching result; a liquidation execution module, configured to, if it is determined according to the matching result that the target pricing rule is consistent with the first liquidation item, liquidate the first liquidation item using the target pricing rule; The rule switching module is configured to, when the action switching indication corresponding to the target pricing rule indicates switching to the next priority pricing rule, use the next priority pricing rule as the new target pricing rule and continue to perform the step of matching the target pricing rule with the first liquidation item.

11. A project data processing device, characterized in that: include: a processor and a memory storing computer program instructions; When the processor executes the computer program instructions, the project data processing method according to any one of claims 1 to 9 is implemented.

12. A computer-readable storage medium, characterized in that The computer-readable storage medium stores computer program instructions, which, when executed by a processor, implement the project data processing method according to any one of claims 1 to 9.

13. A computer program product, characterized in that The invention comprises a computer program, which, when executed by a processor, implements the project data processing method according to any one of claims 1 to 9.

Images