Fund settlement processing method and related equipment

Abstract

The invention provides a fund settlement processing method and related equipment. Relates to the technical field of financial science. The method comprises the following steps: receiving a settlement registration request sent by a service system, and determining a sorting parameter according to the service system; checking the settlement service data in the settlement registration request, and generating a settlement detail list when the settlement registration check result is that the check is passed, the settlement detail list comprising the settlement registration request identifier and the settlement service data arranged according to the sorting parameter; when the settlement detail table is successfully generated, generating a settlement registration result indicating successful settlement registration, and sending the settlement registration result to the business system; and if a settlement processing request sent when the settlement registration result indicates that settlement registration succeeds is received, converting a settlement processing request identifier into a settlement registration request identifier, obtaining a settlement detail table, and calling a settlement execution system to perform settlement processing based on the settlement detail table. The settlement processing request is generated only for the settlement registration request with successful settlement registration, so that the correction is reduced, and unilateral accounts are reduced.

Description

Technical Field

[0001] This application relates to the field of financial technology, and in particular to a fund settlement processing method and related equipment. Background Technology

[0002] In the fintech field, fund settlement can be achieved through software systems. Fund settlement can be processed in batches to handle a large number of settlement requests at once. Fund settlement typically involves multiple software systems, including but not limited to: business systems, settlement management systems, and settlement execution systems.

[0003] In the existing technology, the fund settlement process mainly includes the following steps: First, the business system receives the business application and initiates a settlement request to the settlement execution system through the settlement management system, and performs an estimated account; then, when the settlement management system receives the settlement result returned by the settlement execution system, it calls back to the business system to update the status of the business application.

[0004] However, the above scheme has the problem of one-sided accounting. Summary of the Invention

[0005] This application provides a fund settlement processing method and related equipment to solve the problem of one-sided accounts in the prior art.

[0006] Firstly, this application provides a fund settlement processing method, applied to a settlement management system, the method comprising:

[0007] The system receives a settlement registration request sent by a business system and determines sorting parameters based on the business system. The settlement registration request carries a settlement registration request identifier and one or more settlement business data to be settled. The system verifies the settlement business data to obtain a settlement registration verification result. When the settlement registration verification result is successful, a settlement detail table corresponding to the settlement registration request is generated. The settlement detail table includes the settlement registration request identifier and settlement business data arranged according to the sorting parameters. When the settlement detail table is successfully generated, a settlement registration result indicating successful settlement registration is generated and sent to the business system. The system also receives a settlement processing request sent by the business system. The settlement processing request is generated by the business system when the settlement registration result indicates successful settlement registration and carries a settlement processing request identifier. The system converts the settlement processing request identifier into a corresponding settlement registration request identifier and obtains the settlement detail table corresponding to the settlement registration request identifier. Finally, the system calls the settlement execution system to perform settlement processing on the settlement processing request based on the settlement detail table.

[0008] In one possible design, the method further includes:

[0009] The failure stages in the settlement registration process are identified, and a settlement registration failure reason diagram is generated based on these stages. This diagram includes multiple levels of settlement registration failure reasons arranged sequentially. Each subsequent level of failure reason is a refinement of the previous level's failure reason, and the final level is the underlying cause leading to the failure. The first level of failure reasons in the diagram includes: verification failure or failure to generate the settlement details table. The second level of failure reasons includes: verification failure items or failure to generate the details table. A settlement registration result indicating the failure is generated based on the settlement registration failure reason diagram.

[0010] In one possible design, the invocation of the settlement execution system performs settlement processing on the settlement request based on the settlement details table, including:

[0011] Settlement request data is extracted from the settlement processing request and sorted according to the sorting parameters. The sorted settlement request data and the settlement details table corresponding to the settlement registration request identifier are subjected to consistency verification to obtain a settlement request verification result. The settlement request verification result includes the proportion of settlement business data in the settlement details table that is consistent with the settlement request data. When the settlement request verification result indicates that the proportion of settlement business data is greater than or equal to a preset proportion threshold, the settlement execution system is invoked to process the settlement processing request.

[0012] In one possible design, the invocation of the settlement execution system to perform settlement processing on the settlement request includes:

[0013] According to the settlement execution system based on the settlement business data, one or more settlement business data entries in the settlement details table are divided into one or more settlement batches, with each settlement execution system corresponding to one settlement batch; based on the data volume of the settlement batch corresponding to the settlement execution system, the overdue period for the settlement batch is determined, and the overdue period is positively correlated with the data volume of the settlement batch; based on the settlement batch corresponding to the settlement execution system and the overdue period, a batch settlement request is generated for the settlement execution system, and the overdue period is used to instruct the settlement execution system to complete the settlement processing of the settlement batch within the overdue period; the batch settlement request is sent to the settlement execution system for settlement processing.

[0014] In one possible design, generating a batch settlement request for the settlement execution system based on the settlement batch corresponding to the settlement execution system includes:

[0015] Obtain the number of transactions that can be settled in a single transaction from the settlement execution system; based on the number of transactions that can be settled in a single transaction, divide the settlement batch of the settlement execution system into multiple settlement sub-batches, wherein the number of settlement transactions included in each settlement sub-batch is less than or equal to the number of transactions that can be settled in a single transaction, and the difference between the number of settlement transactions included in the settlement sub-batch and the number of transactions that can be settled in a single transaction is less than or equal to a preset quantity threshold; generate a batch settlement request for the settlement execution system based on the settlement sub-batch of the settlement execution system.

[0016] In one possible design, after sending the batch settlement request to the settlement execution system for settlement processing, the method further includes:

[0017] Receive the settlement result returned by the settlement execution system; update the settlement details table of the settlement processing request according to the settlement result of the settlement processing request, and generate settlement summary information according to the updated settlement details table; call the settlement callback interface of the business system to update the settlement record data in the business system according to the settlement details table and the settlement summary information.

[0018] One possible design also includes:

[0019] When the settlement registration result indicates that the settlement registration failed, and / or the settlement result indicates that the settlement failed, and / or the settlement callback interface call failed, a failure message is generated and sent to the client for display. The failure message includes the reason for the failure.

[0020] In one possible design, the method further includes:

[0021] When the settlement callback interface call fails, if the number of failed calls to the settlement callback interface is less than a preset threshold, the step of calling the settlement callback interface of the business system according to the settlement result to update the settlement record data in the business system is returned; when the settlement callback interface call fails, if the number of failed calls to the settlement callback interface is greater than or equal to the preset threshold, the call to the settlement callback interface is stopped.

[0022] Secondly, this application provides a fund settlement processing method applied to a business system, the method comprising:

[0023] A settlement registration request is generated and sent to the settlement management system. The settlement registration request carries a settlement registration request identifier and one or more settlement transaction data to be settled. The settlement registration result returned by the settlement management system for the settlement registration request is received. When the settlement registration result of the settlement registration request indicates that the settlement registration is successful, a settlement processing request is generated for the settlement registration request and sent to the settlement management system. The settlement processing request carries a settlement processing request identifier, which corresponds to the settlement registration request identifier. When the settlement registration result of the settlement registration request indicates that the settlement registration has failed, and the number of retries for the settlement registration request is less than or equal to a preset threshold, the settlement registration request is adjusted according to the settlement registration failure reason diagram carried in the settlement registration result, and the process returns to the step of generating the settlement registration request. The settlement registration failure reason diagram includes multi-level settlement registration failure reasons, where each level of settlement failure reason is a sub-reason of the previous level of settlement registration failure reason.

[0024] In one possible design, the method further includes:

[0025] If the settlement registration result of the settlement registration request indicates that the settlement registration has failed, and / or if the settlement registration result returned by the settlement management system for the settlement registration request is not received within a preset time period, and if the number of retries for the settlement registration request is greater than a preset threshold, then the settlement record data on the business system is cleared. The settlement record data is generated by the business system when the settlement registration request is generated, and the preset time period is positively correlated with the number of settlement transactions in the settlement registration request.

[0026] In one possible design, the method further includes:

[0027] If no settlement registration result is received from the settlement management system for the settlement registration request within a preset time period, and the number of retries for the settlement registration request exceeds a preset threshold, a data cleanup request for the settlement registration request is sent to the settlement management system. The data cleanup request carries the settlement registration request identifier of the settlement registration request, and the data cleanup request is used to clean up the settlement details table of the settlement registration request identifier on the settlement management system.

[0028] In one possible design, the method further includes:

[0029] The system receives a callback request from the settlement management system to the business system; it calls the settlement callback interface in the business system according to the callback request, and updates the settlement record data according to the settlement result, settlement details table and settlement summary information returned by the settlement management system.

[0030] Thirdly, embodiments of this application provide a fund settlement processing device, applied to a settlement management system, comprising:

[0031] The registration request receiving module is used to receive settlement registration requests sent by the business system and determine sorting parameters according to the business system. The settlement registration request carries a settlement registration request identifier and one or more settlement business data to be settled.

[0032] The registration module is used to verify the settlement business data, obtain the settlement registration verification result, and generate a settlement detail table corresponding to the settlement registration request when the settlement registration verification result is successful. The settlement detail table includes: the settlement registration request identifier and settlement business data arranged according to the sorting parameters.

[0033] The result generation module is used to generate a settlement registration result indicating successful settlement registration when the settlement details table is successfully generated, and to send the settlement registration result to the business system.

[0034] The settlement request receiving module is used to receive a settlement processing request sent by the business system. The settlement processing request is generated by the business system when the settlement registration result indicates that the settlement registration is successful. The settlement processing request carries a settlement processing request identifier.

[0035] The settlement module is used to convert the settlement processing request identifier into a corresponding settlement registration request identifier, and obtain the settlement details table corresponding to the settlement registration request identifier, so as to call the settlement execution system to perform settlement processing on the settlement processing request based on the settlement details table.

[0036] In one possible design, the result generation module is further used for:

[0037] The failure stages in the settlement registration process are identified, and a settlement registration failure reason diagram is generated based on these stages. This diagram includes multiple levels of settlement registration failure reasons arranged sequentially. Each subsequent level of failure reason is a refinement of the previous level's failure reason, and the final level is the underlying cause leading to the failure. The first level of failure reasons in the diagram includes: verification failure or failure to generate the settlement details table. The second level of failure reasons includes: verification failure items or failure to generate the details table. A settlement registration result indicating the failure is generated based on the settlement registration failure reason diagram.

[0038] In one possible design, the settlement module is also used for:

[0039] Settlement request data is extracted from the settlement processing request and sorted according to the sorting parameters. The sorted settlement request data and the settlement details table corresponding to the settlement registration request identifier are subjected to consistency verification to obtain a settlement request verification result. The settlement request verification result includes the proportion of settlement business data in the settlement details table that is consistent with the settlement request data. When the settlement request verification result indicates that the proportion of settlement business data is greater than or equal to a preset proportion threshold, the settlement execution system is invoked to process the settlement processing request.

[0040] In one possible design, the settlement module is also used for:

[0041] According to the settlement execution system based on the settlement business data, one or more settlement business data entries in the settlement details table are divided into one or more settlement batches, with each settlement execution system corresponding to one settlement batch; based on the data volume of the settlement batch corresponding to the settlement execution system, the overdue period for the settlement batch is determined, and the overdue period is positively correlated with the data volume of the settlement batch; based on the settlement batch corresponding to the settlement execution system and the overdue period, a batch settlement request is generated for the settlement execution system, and the overdue period is used to instruct the settlement execution system to complete the settlement processing of the settlement batch within the overdue period; the batch settlement request is sent to the settlement execution system for settlement processing.

[0042] In one possible design, the settlement module is also used for:

[0043] Obtain the number of transactions that can be settled in a single transaction from the settlement execution system; based on the number of transactions that can be settled in a single transaction, divide the settlement batch of the settlement execution system into multiple settlement sub-batches, wherein the number of settlement transactions included in each settlement sub-batch is less than or equal to the number of transactions that can be settled in a single transaction, and the difference between the number of settlement transactions included in the settlement sub-batch and the number of transactions that can be settled in a single transaction is less than or equal to a preset quantity threshold; generate a batch settlement request for the settlement execution system based on the settlement sub-batch of the settlement execution system.

[0044] In one possible design, the settlement module is also used for:

[0045] After sending the batch settlement request to the settlement execution system for settlement processing, the system receives the settlement result returned by the settlement execution system; updates the settlement details table of the settlement processing request according to the settlement result of the settlement processing request, and generates settlement summary information according to the updated settlement details table; and calls the settlement callback interface of the business system to update the settlement record data in the business system according to the settlement details table and the settlement summary information.

[0046] In one possible design, the settlement module is also used for:

[0047] When the settlement registration result indicates that the settlement registration failed, and / or the settlement result indicates that the settlement failed, and / or the settlement callback interface call failed, a failure message is generated and sent to the client for display. The failure message includes the reason for the failure.

[0048] In one possible design, the settlement module is also used for:

[0049] When the settlement callback interface call fails, if the number of failed calls to the settlement callback interface is less than a preset threshold, the step of calling the settlement callback interface of the business system according to the settlement result to update the settlement record data in the business system is returned; when the settlement callback interface call fails, if the number of failed calls to the settlement callback interface is greater than or equal to the preset threshold, the call to the settlement callback interface is stopped.

[0050] Fourthly, embodiments of this application provide a funds settlement processing apparatus, applied to a business system, comprising:

[0051] The registration request sending module is used to generate a settlement registration request and send the settlement registration request to the settlement management system. The settlement registration request carries a settlement registration request identifier and one or more settlement business data to be settled.

[0052] The registration result receiving module is used to receive the settlement registration result returned by the settlement management system in response to the settlement registration request.

[0053] The settlement request sending module is used to generate a settlement processing request for the settlement registration request when the settlement registration result of the settlement registration request indicates that the settlement registration is successful, and send the settlement processing request to the settlement management system. The settlement processing request carries a settlement processing request identifier, and the settlement registration request identifier corresponds to the settlement registration request identifier.

[0054] The cyclic registration module is used to adjust the settlement registration request according to the settlement registration failure diagram carried in the settlement registration result when the settlement registration result of the settlement registration request indicates that the settlement registration has failed, and the number of retries of the settlement registration request is less than or equal to a preset number threshold, and then return to the step of generating the settlement registration request. The settlement registration failure reason diagram includes multiple levels of settlement registration failure reasons, and the subsequent level of settlement failure reason is a sub-reason of the previous level of settlement registration failure reason.

[0055] In one possible design, the device further includes:

[0056] The cleanup module is used to clean up the settlement record data on the business system when the settlement registration result of the settlement registration request indicates that the settlement registration has failed, and / or when no settlement registration result is received from the settlement management system for the settlement registration request within a preset time period, and the number of retries for the settlement registration request is greater than a preset threshold. The settlement record data is generated by the business system when the settlement registration request is generated, and the preset time period is positively correlated with the number of settlement transactions in the settlement registration request.

[0057] In one possible design, the cleaning module is also used for:

[0058] If no settlement registration result is received from the settlement management system for the settlement registration request within a preset time period, and the number of retries for the settlement registration request exceeds a preset threshold, a data cleanup request for the settlement registration request is sent to the settlement management system. The data cleanup request carries the settlement registration request identifier of the settlement registration request, and the data cleanup request is used to clean up the settlement details table of the settlement registration request identifier on the settlement management system.

[0059] In one possible design, the device further includes:

[0060] The update module is used to receive the callback request from the settlement management system to the business system; call the settlement callback interface in the business system according to the callback request; and update the settlement record data according to the settlement result, settlement details table and settlement summary information returned by the settlement management system.

[0061] Fifthly, embodiments of this application provide an electronic device, including: at least one processor and a memory; the memory stores computer-executable instructions; the at least one processor executes the computer-executable instructions stored in the memory, causing the at least one processor to perform the fund settlement processing method as described in the first aspect and various possible designs of the first aspect, or, the fund settlement processing method as described in the second aspect and various possible designs of the second aspect.

[0062] Sixthly, embodiments of this application provide a computer-readable storage medium storing computer-executable instructions. When a processor executes the computer-executable instructions, it implements the fund settlement processing method described in the first aspect and various possible designs of the first aspect, or the fund settlement processing method described in the second aspect and various possible designs of the second aspect.

[0063] Seventhly, embodiments of this application provide a computer program product, including a computer program, which, when executed by a processor, implements the fund settlement processing method described in the first aspect and various possible designs of the first aspect, or the fund settlement processing method described in the second aspect and various possible designs of the second aspect.

[0064] Eighthly, embodiments of this application provide a fund settlement processing system, including a business system and a settlement management system, wherein the settlement management system is used to execute the fund settlement processing method described in the first aspect and various possible designs of the first aspect, and the business system is used to execute the fund settlement processing method described in the second aspect and various possible designs of the second aspect.

[0065] The fund settlement processing method and related equipment provided in this application split the settlement process into a settlement registration process and a settlement processing process. The business system will only initiate the settlement processing process when the settlement registration is successful; if the settlement registration fails, the business system will not initiate the settlement processing process, and therefore there is no need to initiate a reversal. In this way, the occurrence of one-sided accounts can be reduced. Attached Figure Description

[0066] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0067] Figure 1 This is a schematic diagram of the fund settlement process in some related technologies provided in this application;

[0068] Figure 2 This is a flowchart illustrating the steps of a fund settlement processing method provided in an embodiment of this application;

[0069] Figure 3 This is a flowchart of another fund settlement processing method provided in the embodiments of this application;

[0070] Figure 4 This is a schematic diagram illustrating the interaction process between a business system, a settlement management system, and a settlement execution system, provided in an embodiment of this application.

[0071] Figure 5 This is a schematic diagram of the structure of a fund settlement processing device provided in an embodiment of this application;

[0072] Figure 6 This is a schematic diagram of the structure of a fund settlement processing device provided in an embodiment of this application;

[0073] Figure 7 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application.

[0074] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0075] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0076] The collection, storage, use, processing, transmission, provision, and disclosure of financial data or user data involved in the technical solution of this application all comply with the provisions of relevant laws and regulations and do not violate public order and good morals.

[0077] It should be noted that in the embodiments of this application, certain software, components, models and other existing solutions in the industry may be mentioned. These should be regarded as exemplary and are only intended to illustrate the feasibility of implementing the technical solution of this application. However, it does not mean that the applicant has used or necessarily used the solution.

[0078] The embodiments of this application are applicable to fund settlement scenarios based on software systems, including but not limited to: housing provident fund settlement, salary settlement, and ordinary transaction settlement. Figure 1 This is a schematic diagram of the fund settlement process in some related technologies provided in this application, for reference. Figure 1 As shown, the fund settlement process mainly includes the following steps: First, the business system receives the business application and initiates a settlement request to the settlement execution system through the settlement management system, and performs an estimated account; then, when the settlement management system receives the settlement result returned by the settlement execution system, it calls back to the business system to update the status of the business application.

[0079] In the housing provident fund settlement scenario, the aforementioned business system can be the housing provident fund system, the aforementioned settlement execution system can be the bank system, and the settlement management system can serve as a scheduling system between the housing provident fund system and the bank system to manage the settlement.

[0080] However, regardless of the settlement scenario, the settlement execution system typically requires a certain amount of time to process the settlement. Therefore, the business system may not receive a callback from the settlement management system within a certain period after sending the settlement request. In this case, the business system will initiate a reversal to cancel the settlement. However, a reversal may result in inconsistencies between the settlement status in the business system and the settlement execution system. For example, the settlement execution system may record it as a successful settlement, but the business system may determine it as a failed settlement, resulting in a one-sided account situation.

[0081] To address the aforementioned technical issues, this application's embodiments divide the settlement process into a settlement registration process and a settlement processing process. The business system only initiates the settlement processing process when settlement registration is successful; if settlement registration fails, the business system does not initiate the settlement processing process, thus eliminating the need for reversal. This reduces the occurrence of one-sided accounts.

[0082] Figure 2 This is a flowchart illustrating the steps of a fund settlement processing method provided in an embodiment of this application, applied to a settlement management system. In other words, the steps of the above fund settlement processing method are executed by the settlement management system. (Refer to...) Figure 2 As shown, the above-mentioned fund settlement processing methods include:

[0083] S101. Receive the settlement registration request sent by the business system, and determine the sorting parameters according to the business system. The settlement registration request carries a settlement registration request identifier and one or more settlement business data to be settled.

[0084] The settlement registration request is generated by the business system after processing a transaction. The business system sends this request to the settlement management system. Upon receiving the request, the settlement management system preprocesses the settlement business data and then records it in the system. This settlement business data includes relevant information about the transaction requiring settlement registration, such as the transaction identifier, transaction type, settlement amount, the initiating business system, the settlement execution system, and the settlement method.

[0085] It should be noted that a settlement registration request can carry one or more settlement transaction data.

[0086] The sorting parameters mentioned above are related to the business system. Different business systems can support different sorting parameters to achieve different sorting methods. Specifically, the corresponding sorting parameters can be obtained from a preset mapping table based on the business system identifier. The sorting parameters here can be one or more data items in the settlement business data, such as the settlement initiating user, the settlement target user, the settlement amount, the number of settlement transactions, etc.

[0087] S102. Verify the settlement business data to obtain the settlement registration verification result. When the settlement registration verification result is passed, generate the settlement details table corresponding to the settlement registration request. The settlement details table includes: the settlement registration request identifier and the settlement business data arranged according to the sorting parameters.

[0088] Settlement registration may include, but is not limited to: verifying settlement business data, determining settlement methods, and recording settlement business data.

[0089] Among them, the verification of settlement business data is used to verify whether the settlement business data meets the settlement success conditions, including but not limited to: whether the settlement business data is complete, whether each sub-data in the settlement business data meets its predefined value range, and whether the total data and each sub-data are consistent.

[0090] The settlement management system verifies the completeness of settlement business data through the following process: First, the settlement management system extracts the settlement business identifier from the settlement registration request. Then, it extracts the target data item corresponding to the settlement business identifier from the settlement management system. Finally, the settlement management system determines whether the settlement business data includes all of the above target data items. If all are included, the settlement management system determines that the settlement business data is complete; otherwise, the settlement management system determines that the settlement business data is incomplete.

[0091] The aforementioned predefined value range can be carried in the settlement registration request or stored in the settlement management system; this application embodiment does not impose any restrictions on it. The settlement management system can determine whether each sub-data in the settlement business data is within the corresponding value range. If all sub-data are within the corresponding value range, the settlement management system can determine that the value verification is successful; if at least one sub-data is not within the corresponding value range, the settlement management system can determine that the value verification has failed.

[0092] Verifying the consistency between the total data and the data of each sub-item may include the following steps: First, determine the total data and the corresponding sub-item data for each item in the settlement business data. Then, perform statistical analysis on the sub-item data of the total data to obtain the total statistical data. Finally, determine whether the total data and the total statistical data are consistent. If they are consistent, the consistency verification is successful; if they are inconsistent, the consistency verification fails.

[0093] Understandably, if the aforementioned settlement business data is complete, all sub-data within the settlement business data meets its predefined value range, and the total data and each sub-data are consistent, then the settlement business data is deemed to meet the settlement success conditions. When all settlement business data in the settlement registration request meets the settlement success conditions, the settlement method for each settlement business data can be determined, and the settlement business data can be registered. At this point, the returned settlement registration result is "settlement registration successful."

[0094] The settlement method mentioned above can be extracted from the settlement registration request. If the settlement registration request does not include the settlement method, the settlement method of the above settlement business identifier in the historical settlement process can be obtained from the settlement management system. If there is no historical settlement process, the default settlement method will be used as the settlement method.

[0095] If the aforementioned settlement business data is complete, and / or at least one sub-data item in the settlement business data does not meet its predefined value range, and / or the total data and the sub-data are inconsistent, the settlement business data is determined to not meet the settlement success conditions. If at least one settlement business data item in the settlement registration request does not meet the settlement success conditions, the settlement method is not determined, and the settlement business data is not registered. In this case, the returned settlement registration result is settlement registration failure.

[0096] When the business system receives the settlement registration result, it determines whether to initiate a settlement processing request based on the result. Specifically, if the settlement registration result indicates successful settlement registration, the business system generates a settlement processing request and sends it to the settlement management system; if the settlement registration result indicates failed settlement registration, the business system does not generate a settlement processing request, and the settlement fails.

[0097] S103. Upon successful generation of the settlement details table, generate a settlement registration result indicating successful settlement registration, and send the settlement registration result to the business system.

[0098] Understandably, the successful generation of the details table signifies successful settlement registration.

[0099] S104. Receive a settlement processing request sent by the business system. The settlement processing request is generated by the business system when the settlement registration result indicates that the settlement registration is successful. The settlement processing request carries a settlement processing request identifier.

[0100] When the settlement management system receives a settlement processing request, it needs to process the request. This settlement processing request refers to a settlement transaction that meets the conditions for successful settlement.

[0101] S105. Convert the settlement processing request identifier into the corresponding settlement registration request identifier, and obtain the settlement details table corresponding to the settlement registration request identifier, so as to call the settlement execution system to perform settlement processing on the settlement processing request based on the settlement details table.

[0102] In one implementation, the settlement management system extracts the settlement execution system identifier from the settlement processing request, and calls the corresponding settlement execution system to perform settlement processing on the settlement processing request.

[0103] In another implementation, the settlement management system extracts the settlement processing interface of the settlement execution system from the settlement processing request, and calls the settlement processing interface to perform settlement processing on the settlement processing request.

[0104] As can be seen, the settlement management system of this application embodiment can be connected to multiple settlement execution systems for business systems to choose from, thereby improving settlement diversity and success rate.

[0105] As can be seen, the embodiments of this application perform some preprocessing during settlement registration to ensure that the settlement request meets the preset conditions for settlement success. This ensures that the settlement success rate can be improved when a settlement request is directly initiated later.

[0106] In some implementations, the aforementioned settlement registration in the settlement management system based on the settlement registration request, and obtaining the settlement registration result, includes: determining the failure stage in the settlement registration process, and generating a settlement registration failure reason diagram based on the failure stage. The settlement registration failure reason diagram includes multiple levels of settlement registration failure reasons arranged in sequence. Each subsequent level of settlement registration failure reason is a refinement of the previous level's failure reason, and the final level is the underlying reason causing the settlement registration failure. The first level of settlement failure reasons in the diagram includes: verification failure or failure to generate the settlement details table; the second level includes: verification failure items or failure to generate the details table; and a settlement registration result indicating the settlement registration failure is generated based on the settlement registration failure reason diagram. Thus, when settlement registration fails, the reason for the failure can be indicated to assist the business system in updating the settlement business data to resubmit the settlement registration request, which helps improve the settlement registration success rate and the settlement processing success rate.

[0107] Upon successful settlement registration verification, the settlement business data is recorded in the settlement details table corresponding to the settlement registration request. This record is used to verify subsequent settlement processing requests to ensure their accuracy. The settlement processing request carries a corresponding settlement registration request identifier, indicating the settlement registration request it targets.

[0108] In some possible implementations, when the business system receives the settlement registration result, it displays the result on the client side. This allows users to adjust the settlement data corresponding to the failed settlement requests based on the reasons for the failure. Specifically, settlement data can be displayed in groups according to the reasons for settlement registration failure, facilitating batch modification of settlement data and reducing the complexity of data modification for users.

[0109] In addition, the client can provide an option box for the reasons for settlement registration failure. When a user selects a reason for settlement registration failure, the corresponding adjustment plan will be displayed by default in the modification input box. The user can modify the adjustment plan or directly use the adjustment plan to batch modify all settlement business data corresponding to the settlement registration failure reason. The user only needs to enter the adjustment plan once, and does not need to enter the adjustment plan for each settlement business data for each settlement registration failure reason.

[0110] Of course, after users batch input adjustment schemes for various settlement business data for a certain reason for settlement registration failure, the client also supports personalized adjustments for each settlement business data to ensure that all settlement business data are correct.

[0111] After the user inputs the adjustment plan, the client can also operate the submission control to adjust the settlement business data according to the adjustment plan, generate a settlement verification request based on the adjusted settlement business data, and send it to the settlement management system through the business system.

[0112] In some possible implementations, the aforementioned invocation of the settlement execution system to process the settlement request includes: First, extracting the settlement request data and the corresponding settlement registration request identifier from the settlement request, and sorting the settlement request data according to sorting parameters; then, performing a consistency check between the sorted settlement request data and the settlement detail table corresponding to the settlement registration request identifier to obtain the settlement request check result, which includes the proportion of settlement business data in the settlement detail table that matches the settlement request data; then, if the settlement request check result indicates that the proportion of settlement business data is greater than or equal to a preset proportion threshold, it means that the settlement request data and the settlement detail table corresponding to the settlement registration request identifier are consistent, and at this time, the settlement execution system is invoked to process the settlement request. If the settlement request check result indicates that the settlement request data and the settlement detail table corresponding to the settlement registration request are inconsistent, no settlement processing is performed on the settlement request. In this way, the settlement management system can further ensure that the settlement processing request corresponds to a settlement business that has been successfully settled and registered, avoiding initiating settlement processing requests for settlement businesses that have failed to be registered, thus helping to further improve the settlement success rate. In addition, the settlement request data and the settlement business data in the settlement details table are sorted in the same way. Both are sorted in ascending order according to the sorting parameters, or in descending order, which can improve matching efficiency.

[0113] The settlement request verification result includes the percentage of settlement transaction data in the settlement details table that matches the settlement request data. For example, if there are 100 settlement transaction records in the settlement details table, and 98 of them successfully match the settlement request data, then the percentage of settlement transaction data in the settlement details table that matches the settlement request data is 98%.

[0114] In some implementations, when the settlement request verification result indicates that the proportion of settlement business data consistent with the settlement request data in the settlement details table is less than a preset proportion threshold, it indicates that the settlement request data and the settlement details table corresponding to the settlement registration request are inconsistent. The settlement management system can also return the settlement failure reason to the business system, so that the user can adjust the settlement request data according to the settlement failure reason and re-initiate the settlement processing request. The settlement failure reason may include the difference information between the settlement request data and the settlement details table.

[0115] If a settlement processing request fails to complete after multiple retries, the settlement management system can delete the settlement transaction data corresponding to that settlement registration request from the settlement details table. This avoids re-processing the settlement transaction corresponding to the settlement registration request. Alternatively, the business system can re-register the settlement transaction data corresponding to the settlement registration request, and initiate a settlement processing request only after the re-registration is successful.

[0116] In some possible implementations, the settlement execution system is invoked to process settlement requests. This includes: First, based on the settlement business data, the settlement execution system divides one or more settlement business data entries in the settlement details table into one or more settlement batches, with each settlement execution system corresponding to one settlement batch. Based on the data volume of the settlement batch corresponding to each settlement execution system, the overdue period for each settlement batch is determined. The overdue period is positively correlated with the data volume of the settlement batch. Based on the settlement batch and the overdue period, a batch settlement request is generated for the settlement execution system. The overdue period instructs the settlement execution system to complete the settlement processing of the batch within the overdue period. Then, the batch settlement request is sent to the corresponding settlement execution system for settlement processing. Since different batch settlement requests correspond to different settlement execution systems, the settlement management system can distribute batch settlement requests to the corresponding settlement execution systems in parallel. Compared to serial settlement execution, this application can improve settlement processing efficiency.

[0117] It is understandable that the data volume of a settlement batch is the number of settlement transactions included in the settlement batch. The larger the number of settlement transactions, the longer the settlement processing time. Therefore, a higher overdue period is set to avoid incomplete settlement processing. Conversely, the smaller the number of settlement transactions, the shorter the settlement processing time. Therefore, a smaller overdue period is set to avoid waiting and save time.

[0118] In some possible implementations, generating a batch settlement request for the settlement execution system based on the settlement batch corresponding to the settlement execution system includes: first, obtaining the number of transactions that can be settled in a single transaction by the settlement execution system; then, dividing the settlement batch of the settlement execution system into multiple settlement sub-batches based on the number of transactions that can be settled in a single transaction, where the number of settlement transactions included in each settlement sub-batch is less than or equal to the number of transactions that can be settled in a single transaction, and the difference between the number of settlement transactions included in the settlement sub-batch and the number of transactions that can be settled in a single transaction is less than or equal to a preset quantity threshold; finally, generating a batch settlement request for the settlement execution system based on the settlement sub-batches of the settlement execution system. Thus, this embodiment of the application achieves further segmentation of settlement business data, making the batch settlement request conform to the settlement processing capacity of the settlement execution system, which helps to improve the settlement processing success rate.

[0119] The number of transactions that can be settled in a single transaction describes the settlement processing capacity of the settlement execution coefficient. A higher number of transactions that can be settled in a single transaction indicates a better settlement processing capacity of the settlement execution system, allowing for more settlement transactions in each settlement batch. Conversely, a lower number of transactions that can be settled in a single transaction indicates a worse settlement processing capacity of the settlement execution system, allowing for fewer settlement transactions in each settlement batch. The number of settlement transactions can refer to the number of settlement transaction data items.

[0120] In one implementation, the number of transactions that can be settled in a single transaction can be set by the user in the settlement execution system and sent by the settlement execution system to the settlement management system for recording.

[0121] In another implementation, the number of transactions that can be settled in a single transaction can be calculated by the settlement management system based on the hardware configuration of the settlement execution system. For example, it can be calculated based on the number of processors, memory size, and number of threads in the settlement execution system. The number of transactions that can be settled in a single transaction is positively correlated with the number of processors, memory size, and number of threads. That is, the larger the number of processors, the larger the memory size, and the larger the number of threads, the larger the number of transactions that can be settled in a single transaction.

[0122] In the third implementation method, the number of transactions that can be settled in a single transaction can be determined based on the historical settlement data of the settlement management system. Specifically, the processing time for different numbers of transactions per transaction can be extracted from historical settlement data, and the corresponding number of transactions per transaction can be selected as the number of transactions that can be settled in a single transaction based on the target processing time. Here, the target processing time is used to indicate the maximum acceptable settlement processing time.

[0123] After obtaining the number of settlement transactions that can be settled in a single transaction, the settlement execution system can split multiple settlement transaction data according to this number, so that the number of settlement transactions included in each settlement sub-batch is roughly the same and close to the number of settlement transactions that can be settled in a single transaction. For example, if a settlement batch includes 100 settlement transaction data and the number of settlement transactions that can be settled in a single transaction is 40, then the settlement batch can be split into 3 settlement sub-batches, each including 33, 33, and 34 settlement transaction data respectively.

[0124] Each of the above settlement sub-batch corresponds to a batch settlement request, which is executed by the corresponding settlement execution system.

[0125] In some possible implementations, after sending the batch settlement request to the settlement execution system for settlement processing, the above method further includes: first, receiving the settlement result returned by the settlement execution system, updating the settlement detail table corresponding to the settlement processing request based on the settlement result, and generating settlement summary information based on the updated settlement detail table; then, calling the settlement callback interface of the business system to update the settlement record data in the business system based on the settlement result, the settlement detail table, and the settlement summary information. Thus, this embodiment of the application can combine information from both the settlement detail table and the settlement summary information to update the settlement record data in the business system, improving the accuracy and comprehensiveness of the settlement record data.

[0126] Specifically, the status of each settlement transaction in the settlement details table can be set to either "settlement successful" or "settlement failed." Therefore, settlement summary information can be generated based on the settlement details table. This summary information can include statistical information on the settlement transaction data in the settlement processing request, used to monitor the processing results of the settlement request. The settlement summary information may include, but is not limited to: total number of settlement transactions, total settlement transaction amount, number of successful settlement transactions, number of failed settlement transactions, amount of successful settlement transactions, and amount of failed settlement transactions.

[0127] Settlement record data includes: settlement business status, settlement details, and settlement summary information. Initially, the business system sets the settlement business status to pending settlement registration. After receiving a settlement registration result indicating successful settlement registration, the settlement business status is changed to successful settlement registration. After receiving a settlement registration result indicating failed settlement registration, the settlement business status is changed to failed settlement registration. When the received settlement result indicates successful settlement, the settlement business status is changed to successful settlement. When the received settlement result indicates failed settlement, the settlement business status is changed to failed settlement registration.

[0128] In some possible implementations, the above method further includes: generating a failure message and sending it to the client for display when the settlement registration result indicates settlement registration failure, and / or the settlement result indicates settlement failure, and / or the settlement callback interface call fails. The failure message includes the reason for the failure. In this way, the failure message can indicate the reason for the failure, allowing users to adjust their settlement registration and processing requests to improve the settlement success rate.

[0129] The reasons for the aforementioned settlement registration failures can be further categorized into settlement registration verification failures and settlement business data recording failures. Settlement registration verification failures can be further subdivided into: incomplete settlement business data, sub-data in the settlement business data not meeting their predefined value ranges, and inconsistencies between the total data and the data of each sub-item. Settlement business data recording failures indicate that the recording of settlement business data in the settlement details table failed, which may be caused by insufficient storage space or system shutdown.

[0130] If the above settlement callback interface call fails, the failure reason returned by the settlement callback interface can be used as the failure reason information.

[0131] In some possible implementations, the above method further includes: if the number of failed calls to the settlement callback interface is less than a preset threshold, then return to the step of calling the settlement callback interface of the business system based on the settlement result to update the settlement record data in the business system; if the number of failed calls to the settlement callback interface is greater than or equal to the preset threshold, then stop calling the settlement callback interface. In this way, the success rate of settlement callbacks can be improved by retrying the callback multiple times, thereby improving the success rate of settlement processing.

[0132] The aforementioned preset number of attempts threshold can be related to the business system. After setting the preset number of attempts threshold on the business system, it is sent to the settlement management system to realize different number of retries for different business systems and meet the different retries requirements of different business systems.

[0133] Figure 3 This is a flowchart illustrating another fund settlement processing method provided in this application embodiment, applied to a business system. In other words, the above fund settlement processing method is executed by the aforementioned business system. (Refer to...) Figure 3 As shown, the above method includes:

[0134] S201. Generate a settlement registration request and send the settlement registration request to the settlement management system. The settlement registration request carries a settlement registration request identifier and one or more settlement transaction data to be settled.

[0135] After processing a settlement transaction, the business system can generate a settlement registration request, which can be used to register one or more settlement transaction data.

[0136] S202. Receive the settlement registration result returned by the settlement management system in response to the above settlement registration request.

[0137] The settlement registration result indicates whether the settlement registration was successful. The process of settlement registration by the settlement management system can be found in the detailed explanation of S102, and will not be repeated here.

[0138] S203. When the settlement registration result indicates that the settlement registration is successful, a settlement processing request is generated for the settlement registration request and sent to the settlement management system. The settlement processing request carries a settlement processing request identifier, and the settlement registration request identifier corresponds to the settlement registration request identifier.

[0139] The settlement processing request is used to process one or more settlement business data in the settlement registration request. The settlement processing request and the settlement registration request correspond to the same settlement business data, but the request types are different.

[0140] S204. When the settlement registration result of the settlement registration request indicates that the settlement registration has failed, and the number of retries for the settlement registration request is less than or equal to a preset threshold, the settlement registration request is adjusted according to the settlement registration failure reason diagram carried in the settlement registration result, and the step of generating the settlement registration request is returned. The settlement registration failure reason diagram includes multiple levels of settlement registration failure reasons, and the later level of settlement failure reason is a sub-reason of the previous level of settlement registration failure reason.

[0141] When a settlement registration request is generated for the first time, its corresponding settlement registration request identifier and retry count are recorded as 0. Therefore, each subsequent retry of the settlement registration request increments the retry count by 1, until the retry count exceeds a preset threshold. This embodiment of the application can generate settlement registration requests multiple times in a loop to maximize the settlement registration success rate.

[0142] The business system in this application embodiment only generates settlement processing requests for successfully registered settlement requests to perform settlement processing, while not generating settlement processing requests for failed settlement registration requests, thus eliminating the need to initiate reversals. This reduces the occurrence of one-sided accounts.

[0143] Among some possible implementations, the above method also includes:

[0144] If the settlement registration request fails to register the settlement registration, and / or if no settlement registration result is received from the settlement management system within a preset time period, and if the number of retries for the settlement registration request exceeds a preset threshold, then the settlement registration is determined to have failed and further retries are not possible. In this case, settlement record data on the business system is cleared. This settlement record data is generated by the business system when the settlement registration request is generated, and the preset time period is positively correlated with the number of settlement transactions in the settlement registration request. Thus, clearing settlement record data upon settlement registration failure avoids initiating a settlement processing request and eliminates the need for reversal, effectively reducing the complexity of the reversal process.

[0145] The aforementioned preset duration is positively correlated with the number of settlement transactions in the settlement registration request, meaning that the larger the number of settlement transactions in the settlement registration request, the longer the preset duration; conversely, the smaller the number of settlement transactions in the settlement registration request, the shorter the preset duration.

[0146] Among some possible implementations, the above method also includes:

[0147] If no settlement registration result is received from the settlement management system within a preset time period, and the number of retries for the settlement registration request exceeds a preset threshold, the settlement registration is determined to have failed and further retries are not permitted. A data cleanup request for the settlement registration request is then sent to the settlement management system. This data cleanup request carries the settlement registration request identifier and is used to clean up the settlement details table in the settlement management system that contains the settlement registration request identifier. This saves storage space in the settlement management system and improves the complexity of searching the settlement details table when subsequent settlement processing requests are received.

[0148] The aforementioned data cleanup request carries a settlement registration request identifier in order to clean up the settlement details table corresponding to the settlement registration request identifier.

[0149] Among some possible implementations, the above method also includes:

[0150] Receive callback requests from the settlement management system to the business system; invoke the settlement callback interface in the business system according to the callback requests; and update the settlement record data based on the settlement results, settlement details, and settlement summary information returned by the settlement management system.

[0151] Specifically, the above updates include: updating the settlement business status and updating the settlement details table and settlement summary information into the settlement record data.

[0152] The aforementioned update of settlement business status includes: initially setting the settlement business status to pending settlement registration; after receiving a settlement registration result indicating successful settlement registration, changing the settlement business status to successful settlement registration; after receiving a settlement registration result indicating failed settlement registration, changing the settlement business status to failed settlement registration; when receiving a settlement result indicating successful settlement, changing the settlement business status to successful settlement; and when receiving a settlement result indicating failed settlement, changing the settlement business status to failed settlement.

[0153] In summary, the business system in this application embodiment only generates settlement processing requests for successfully registered settlement requests to perform settlement processing, while not generating settlement processing requests for failed settlement registration requests, thus eliminating the need to initiate reversals. This reduces the occurrence of one-sided accounts.

[0154] In summary Figure 2 The method shown and Figure 3 The method shown, Figure 4 This is a schematic diagram illustrating the interaction flow between a business system, a settlement management system, and a settlement execution system, as provided in an embodiment of this application. (Refer to...) Figure 4 As shown, the interaction flow includes:

[0155] S301. The business system receives the business processing, generates a settlement registration request based on the processed settlement business, and sends the settlement registration request to the settlement management system.

[0156] S302. The settlement management system performs settlement registration based on the settlement registration request, obtains the settlement registration result, and sends the settlement registration result to the aforementioned business system.

[0157] S303. When the settlement registration result indicates that the settlement registration is successful, the business system sends the settlement processing request corresponding to the settlement registration request to the settlement management system.

[0158] S304. The settlement management system calls the settlement execution system to process the settlement request, and the settlement execution system returns the settlement result to the settlement management system.

[0159] S305. The settlement management system calls the settlement callback interface of the business system to update the settlement record data in the business system.

[0160] For detailed explanations of S301 to S305 above, please refer to the foregoing. Figure 2 or Figure 3 The corresponding steps are explained in detail below, and will not be repeated here. It can be seen that... Figure 1Compared to the fund settlement process shown, the difference in this embodiment is that settlement registration is performed first during each settlement, and settlement processing is carried out only when settlement registration is successful. Thus, if settlement registration fails, no further settlement processing is required, which not only reduces the occurrence of one-sided accounts but also reduces the processing pressure on the settlement execution system.

[0161] Figure 5 This is a schematic diagram of a fund settlement processing device provided in an embodiment of this application, applied to a settlement management system. Figure 5 As shown, the funds settlement processing device 400 includes:

[0162] The registration request receiving module 401 is used to receive a settlement registration request sent by the business system and determine sorting parameters according to the business system. The settlement registration request carries a settlement registration request identifier and one or more settlement business data to be settled.

[0163] The registration module 402 is used to verify the settlement business data, obtain the settlement registration verification result, and generate a settlement detail table corresponding to the settlement registration request when the settlement registration verification result is passed. The settlement detail table includes: the settlement registration request identifier and settlement business data arranged according to the sorting parameters.

[0164] The result generation module 403 is used to generate a settlement registration result indicating successful settlement registration when the settlement details table is successfully generated, and to send the settlement registration result to the business system.

[0165] The settlement request receiving module 404 is used to receive a settlement processing request sent by the business system. The settlement processing request is generated by the business system when the settlement registration result indicates that the settlement registration is successful. The settlement processing request carries a settlement processing request identifier.

[0166] The settlement module 405 is used to convert the settlement processing request identifier into a corresponding settlement registration request identifier and obtain the settlement details table corresponding to the settlement registration request identifier, so as to call the settlement execution system to perform settlement processing on the settlement processing request based on the settlement details table.

[0167] In one possible design, the result generation module 403 is further configured to:

[0168] The failure stages in the settlement registration process are identified, and a settlement registration failure reason diagram is generated based on these stages. This diagram includes multiple levels of settlement registration failure reasons arranged sequentially. Each subsequent level of failure reason is a refinement of the previous level's failure reason, and the final level is the underlying cause leading to the failure. The first level of failure reasons in the diagram includes: verification failure or failure to generate the settlement details table. The second level of failure reasons includes: verification failure items or failure to generate the details table. A settlement registration result indicating the failure is generated based on the settlement registration failure reason diagram.

[0169] In one possible design, the settlement module 405 is further used for:

[0170] Settlement request data is extracted from the settlement processing request and sorted according to the sorting parameters. The sorted settlement request data and the settlement details table corresponding to the settlement registration request identifier are subjected to consistency verification to obtain a settlement request verification result. The settlement request verification result includes the proportion of settlement business data in the settlement details table that is consistent with the settlement request data. When the settlement request verification result indicates that the proportion of settlement business data is greater than or equal to a preset proportion threshold, the settlement execution system is invoked to process the settlement processing request.

[0171] In one possible design, the settlement module 405 is further used for:

[0172] According to the settlement execution system based on the settlement business data, one or more settlement business data entries in the settlement details table are divided into one or more settlement batches, with each settlement execution system corresponding to one settlement batch; based on the data volume of the settlement batch corresponding to the settlement execution system, the overdue period for the settlement batch is determined, and the overdue period is positively correlated with the data volume of the settlement batch; based on the settlement batch corresponding to the settlement execution system and the overdue period, a batch settlement request is generated for the settlement execution system, and the overdue period is used to instruct the settlement execution system to complete the settlement processing of the settlement batch within the overdue period; the batch settlement request is sent to the settlement execution system for settlement processing.

[0173] In one possible design, the settlement module 405 is further used for:

[0174] Obtain the number of transactions that can be settled in a single transaction from the settlement execution system; based on the number of transactions that can be settled in a single transaction, divide the settlement batch of the settlement execution system into multiple settlement sub-batches, wherein the number of settlement transactions included in each settlement sub-batch is less than or equal to the number of transactions that can be settled in a single transaction, and the difference between the number of settlement transactions included in the settlement sub-batch and the number of transactions that can be settled in a single transaction is less than or equal to a preset quantity threshold; generate a batch settlement request for the settlement execution system based on the settlement sub-batch of the settlement execution system.

[0175] In one possible design, the settlement module 405 is further used for:

[0176] After sending the batch settlement request to the settlement execution system for settlement processing, the system receives the settlement result returned by the settlement execution system; updates the settlement details table of the settlement processing request according to the settlement result of the settlement processing request, and generates settlement summary information according to the updated settlement details table; and calls the settlement callback interface of the business system to update the settlement record data in the business system according to the settlement details table and the settlement summary information.

[0177] In one possible design, the settlement module 405 is further used for:

[0178] When the settlement registration result indicates that the settlement registration failed, and / or the settlement result indicates that the settlement failed, and / or the settlement callback interface call failed, a failure message is generated and sent to the client for display. The failure message includes the reason for the failure.

[0179] In one possible design, the settlement module 405 is further used for:

[0180] When the settlement callback interface call fails, if the number of failed calls to the settlement callback interface is less than a preset threshold, the step of calling the settlement callback interface of the business system according to the settlement result to update the settlement record data in the business system is returned; when the settlement callback interface call fails, if the number of failed calls to the settlement callback interface is greater than or equal to the preset threshold, the call to the settlement callback interface is stopped.

[0181] The fund settlement processing device provided in this application embodiment can be used to execute the fund settlement processing method executed by the settlement management system in the above embodiment. Its implementation principle and technical effect are similar, and will not be repeated here.

[0182] Figure 6 This is a schematic diagram of a fund settlement processing device provided in an embodiment of this application, applied to a business system. For example... Figure 6 As shown, the funds settlement processing device 500 includes:

[0183] The registration request sending module 501 is used to generate a settlement registration request and send the settlement registration request to the settlement management system. The settlement registration request carries a settlement registration request identifier and one or more settlement business data to be settled.

[0184] The registration result receiving module 502 is used to receive the settlement registration result returned by the settlement management system in response to the settlement registration request.

[0185] The settlement request sending module 503 is used to generate a settlement processing request for the settlement registration request when the settlement registration result of the settlement registration request indicates that the settlement registration is successful, and send the settlement processing request to the settlement management system. The settlement processing request carries a settlement processing request identifier, and the settlement registration request identifier corresponds to the settlement registration request identifier.

[0186] The loop registration module 504 is used to adjust the settlement registration request according to the settlement registration failure diagram carried in the settlement registration result when the settlement registration result of the settlement registration request indicates that the settlement registration has failed, and the number of retries of the settlement registration request is less than or equal to a preset number threshold, and return to the step of generating the settlement registration request. The settlement registration failure reason diagram includes multiple levels of settlement registration failure reasons, and the subsequent level of settlement failure reason is a sub-reason of the previous level of settlement registration failure reason.

[0187] In one possible design, the device further includes:

[0188] The cleanup module is used to clean up the settlement record data on the business system when the settlement registration result of the settlement registration request indicates that the settlement registration has failed, and / or when no settlement registration result is received from the settlement management system for the settlement registration request within a preset time period, and the number of retries for the settlement registration request is greater than a preset threshold. The settlement record data is generated by the business system when the settlement registration request is generated, and the preset time period is positively correlated with the number of settlement transactions in the settlement registration request.

[0189] In one possible design, the cleaning module is also used for:

[0190] If no settlement registration result is received from the settlement management system for the settlement registration request within a preset time period, and the number of retries for the settlement registration request exceeds a preset threshold, a data cleanup request for the settlement registration request is sent to the settlement management system. The data cleanup request carries the settlement registration request identifier of the settlement registration request, and the data cleanup request is used to clean up the settlement details table of the settlement registration request identifier on the settlement management system.

[0191] In one possible design, the device further includes:

[0192] The update module is used to receive callback requests from the settlement management system to the business system; to call the settlement callback interface in the business system according to the callback request; and to update the settlement record data according to the settlement results, settlement details, and settlement summary information returned by the settlement management system. The fund settlement processing apparatus provided in this application embodiment can be used to execute the technical solution of the fund settlement processing method executed by the business system in the above embodiments. Its implementation principle and technical effects are similar and will not be described again here.

[0193] It should be noted that the division of the various modules in the above device is merely a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, these modules can be implemented entirely in software through processing element calls; they can be implemented entirely in hardware; or some modules can be implemented by processing element calls to software, while others are implemented in hardware.

[0194] Figure 7 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Figure 7 As shown, the electronic device may include a transceiver 121, a processor 122, and a memory 123.

[0195] Processor 122 executes computer execution instructions stored in memory, causing processor 122 to perform the scheme in the above embodiments. Processor 122 may be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it may also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components.

[0196] The memory 123 is connected to the processor 122 via the system bus and completes communication between them. The memory 123 is used to store computer program instructions.

[0197] Transceiver 121 can be used to obtain the task to be run and its configuration information.

[0198] The system bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, the buses shown in the accompanying drawings are not limited to a single bus or a single type of bus. The system bus can be categorized as an address bus, data bus, control bus, etc. For ease of illustration, only one thick line is used to represent it in the figures, but this does not indicate that there is only one bus or a single type of bus. Transceivers are used to enable communication between database access devices and other computers (e.g., clients, read-write databases, and read-only databases).

[0199] The memory may include random access memory (RAM) and may also include non-volatile memory (VNM).

[0200] This application also provides a chip for executing instructions, which is used to execute the technical solution of the fund settlement processing method in the above embodiments.

[0201] This application also provides a computer-readable storage medium storing computer instructions. When the computer instructions are executed on a computer, the computer performs the technical solution of the fund settlement processing method described in the above embodiments.

[0202] This application also provides a computer program product, which includes a computer program stored in a computer-readable storage medium. At least one processor can read the computer program from the computer-readable storage medium, and when the at least one processor executes the computer program, it can implement the technical solution of the fund settlement processing method in the above embodiments.

[0203] This application provides a fund settlement processing system, including a business system and a settlement management system, wherein the settlement management system is used to perform the above-mentioned... Figure 2 The fund settlement processing method shown above is used by the business system to execute the above. Figure 3 The fund settlement processing method is shown.

[0204] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative; for instance, the division of modules is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple modules may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be indirect coupling or communication connection through some interfaces, devices, or modules, and may be electrical, mechanical, or other forms.

[0205] The modules described as separate components may or may not be physically separate. The components shown as modules may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to implement the solution of this embodiment according to actual needs.

[0206] Furthermore, the functional modules in the various embodiments of this application can be integrated into one processing unit, or each module can exist physically separately, or two or more modules can be integrated into one unit. The unit composed of the above modules can be implemented in hardware or in the form of hardware plus software functional units.

[0207] The integrated modules described above, implemented as software functional modules, can be stored in a computer-readable storage medium. These software functional modules, stored in a storage medium, include several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute some steps of the methods of the various embodiments of this application.

[0208] The aforementioned storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. The storage medium can be any available medium that can be accessed by a general-purpose or special-purpose computer.

[0209] An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Alternatively, the storage medium can be an integral part of the processor. The processor and storage medium can reside in an Application Specific Integrated Circuit (ASIC). Alternatively, the processor and storage medium can exist as discrete components in an electronic control unit or main control device.

[0210] Those skilled in the art will understand that all or part of the steps of the above-described method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When executed, the program performs the steps of the above-described method embodiments; and the aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disks, or optical disks.

[0211] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features therein. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.

Claims

1. A fund settlement processing method, characterized in that, Applied to a settlement management system, the method includes: The system receives a settlement registration request sent by the business system and determines sorting parameters according to the business system. The settlement registration request carries a settlement registration request identifier and one or more settlement business data to be settled. The settlement business data is verified to obtain a settlement registration verification result. When the settlement registration verification result is passed, a settlement detail table corresponding to the settlement registration request is generated. The settlement detail table includes: the settlement registration request identifier and settlement business data arranged according to the sorting parameters. Upon successful generation of the settlement details table, a settlement registration result indicating successful settlement registration is generated and sent to the business system. The system receives a settlement processing request sent by the business system. The settlement processing request is generated by the business system when the settlement registration result indicates that the settlement registration is successful. The settlement processing request carries a settlement processing request identifier. The settlement processing request identifier is converted into the corresponding settlement registration request identifier, and the settlement details table corresponding to the settlement registration request identifier is obtained, so as to call the settlement execution system to perform settlement processing on the settlement processing request based on the settlement details table.

2. The method according to claim 1, characterized in that, The method further includes: The failure stages in the settlement registration process are identified, and a settlement registration failure reason diagram is generated based on the failure stages. The settlement registration failure reason diagram includes multi-level settlement registration failure reasons arranged in sequence. The subsequent level of settlement registration failure reason is a refinement of the previous level of settlement registration failure reason, and the last level of settlement registration failure reason is the underlying reason that leads to the settlement registration failure. The first level of settlement failure reasons in the settlement registration failure reason diagram includes: verification failure or settlement detail table generation failure. The second level of settlement failure reasons in the settlement registration failure reason diagram includes: verification failure items or details table generation failure reasons. Based on the settlement registration failure reason diagram, a settlement registration result indicating settlement registration failure is generated.

3. The method according to claim 2, characterized in that, The invocation of the settlement execution system to perform settlement processing on the settlement request based on the settlement details table includes: Extract settlement request data from the settlement processing request, and sort the settlement request data according to the sorting parameters; The sorted settlement request data and the settlement detail table corresponding to the settlement registration request identifier are subjected to consistency verification to obtain the settlement request verification result. The settlement request verification result includes the proportion of settlement business data in the settlement detail table that is consistent with the settlement request data. When the settlement request verification result indicates that the proportion of the settlement business data is greater than or equal to a preset proportion threshold, the settlement execution system is invoked to process the settlement processing request.

4. The method according to claim 3, characterized in that, The invocation of the settlement execution system to process the settlement request includes: According to the settlement execution system based on the settlement business data, one or more settlement business data in the settlement details table are divided into one or more settlement batches, and each settlement execution system corresponds to one settlement batch; Based on the amount of settlement batch data corresponding to the settlement execution system, the overdue period for the settlement batch is determined by the settlement execution system, and the overdue period is positively correlated with the amount of settlement batch data; Based on the settlement batch corresponding to the settlement execution system and the overdue period, a batch settlement request for the settlement execution system is generated. The overdue period is used to instruct the settlement execution system to complete the settlement processing of the settlement batch within the overdue period. The batch settlement request is sent to the settlement execution system for settlement processing.

5. The method according to claim 4, characterized in that, The step of generating a batch settlement request for the settlement execution system based on the settlement batch corresponding to the settlement execution system includes: Obtain the number of transactions that can be settled in a single transaction by the settlement execution system; Based on the number of transactions that can be settled in a single transaction, the settlement batch of the settlement execution system is divided into multiple settlement sub-batches. The number of settlement transactions included in each settlement sub-batch is less than or equal to the number of transactions that can be settled in a single transaction, and the difference between the number of settlement transactions included in the settlement sub-batch and the number of transactions that can be settled in a single transaction is less than or equal to a preset quantity threshold. The settlement execution system generates a batch settlement request based on the settlement sub-batch of the settlement execution system.

6. The method according to claim 4, characterized in that, After sending the batch settlement request to the settlement execution system for settlement processing, the method further includes: Receive the settlement result returned by the settlement execution system; Update the settlement details table of the settlement processing request according to the settlement result of the settlement processing request, and generate settlement summary information according to the updated settlement details table; The settlement callback interface of the business system is invoked to update the settlement record data in the business system based on the settlement details table and the settlement summary information.

7. The method according to claim 6, characterized in that, Also includes: When the settlement registration result indicates that the settlement registration failed, and / or the settlement result indicates that the settlement failed, and / or the settlement callback interface call failed, a failure message is generated and sent to the client for display. The failure message includes the reason for the failure.

8. The method according to claim 6, characterized in that, The method further includes: If the settlement callback interface call fails, and the number of failed calls to the settlement callback interface is less than a preset threshold, then the step of calling the settlement callback interface of the business system according to the settlement result to update the settlement record data in the business system is returned. If the number of failed calls to the settlement callback interface is greater than or equal to a preset threshold, then the call to the settlement callback interface will be stopped.

9. A method for processing fund settlement, characterized in that, Applied to a business system, the method includes: A settlement registration request is generated and sent to the settlement management system. The settlement registration request carries a settlement registration request identifier and one or more settlement transaction data to be settled. Receive the settlement registration result returned by the settlement management system in response to the settlement registration request; When the settlement registration result of the settlement registration request indicates that the settlement registration is successful, a settlement processing request is generated for the settlement registration request and sent to the settlement management system. The settlement processing request carries a settlement processing request identifier, and the settlement registration request identifier corresponds to the settlement registration request identifier. When the settlement registration result of the settlement registration request indicates that the settlement registration has failed, and the number of retries for the settlement registration request is less than or equal to a preset threshold, the settlement registration request is adjusted according to the settlement registration failure reason diagram carried in the settlement registration result, and the step of generating the settlement registration request is returned. The settlement registration failure reason diagram includes multiple levels of settlement registration failure reasons, and the subsequent level of settlement failure reason is a sub-reason of the previous level of settlement registration failure reason.

10. The method according to claim 9, characterized in that, Also includes: If the settlement registration result of the settlement registration request indicates that the settlement registration has failed, and / or if the settlement registration result returned by the settlement management system for the settlement registration request is not received within a preset time period, and if the number of retries for the settlement registration request is greater than a preset threshold, then the settlement record data on the business system is cleared. The settlement record data is generated by the business system when the settlement registration request is generated, and the preset time period is positively correlated with the number of settlement transactions in the settlement registration request.

11. The method according to claim 10, characterized in that, The method further includes: If no settlement registration result is received from the settlement management system for the settlement registration request within a preset time period, and the number of retries for the settlement registration request exceeds a preset threshold, a data cleanup request for the settlement registration request is sent to the settlement management system. The data cleanup request carries the settlement registration request identifier of the settlement registration request, and the data cleanup request is used to clean up the settlement details table of the settlement registration request identifier on the settlement management system.

12. The method according to claim 9, characterized in that, The method further includes: Receive callback requests from the settlement management system to the business system; The settlement callback interface in the business system is invoked according to the callback request, and the settlement record data is updated according to the settlement results, settlement details and settlement summary information returned by the settlement management system.

13. A fund settlement processing device, characterized in that, Applied to settlement management systems, including: The registration request receiving module is used to receive settlement registration requests sent by the business system and determine sorting parameters according to the business system. The settlement registration request carries a settlement registration request identifier and one or more settlement business data to be settled and registered. The registration module is used to verify the settlement business data, obtain the settlement registration verification result, and generate a settlement detail table corresponding to the settlement registration request when the settlement registration verification result is successful. The settlement detail table includes: the settlement registration request identifier and settlement business data arranged according to the sorting parameters. The result generation module is used to generate a settlement registration result indicating successful settlement registration when the settlement details table is successfully generated, and to send the settlement registration result to the business system. The settlement request receiving module is used to receive a settlement processing request sent by the business system. The settlement processing request is generated by the business system when the settlement registration result indicates that the settlement registration is successful. The settlement processing request carries a settlement processing request identifier. The settlement module is used to convert the settlement processing request identifier into a corresponding settlement registration request identifier, and obtain the settlement details table corresponding to the settlement registration request identifier, so as to call the settlement execution system to perform settlement processing on the settlement processing request based on the settlement details table.

14. A fund settlement processing device, characterized in that, Applied to business systems, including: The registration request sending module is used to generate a settlement registration request and send the settlement registration request to the settlement management system. The settlement registration request carries a settlement registration request identifier and one or more settlement business data to be settled and registered. The registration result receiving module is used to receive the settlement registration result returned by the settlement management system in response to the settlement registration request; A settlement request sending module is configured to generate a settlement processing request for the settlement registration request when the settlement registration result of the settlement registration request indicates that the settlement registration is successful, and send the settlement processing request to the settlement management system. The settlement processing request carries a settlement processing request identifier, and the settlement registration request identifier corresponds to the settlement registration request identifier. The cyclic registration module is used to adjust the settlement registration request according to the settlement registration failure diagram carried in the settlement registration result when the settlement registration result of the settlement registration request indicates that the settlement registration has failed, and the number of retries of the settlement registration request is less than or equal to a preset number threshold, and then return to the step of generating the settlement registration request. The settlement registration failure reason diagram includes multiple levels of settlement registration failure reasons, and the subsequent level of settlement failure reason is a sub-reason of the previous level of settlement registration failure reason.

15. An electronic device, characterized in that, include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory to implement the method as described in any one of claims 1 to 8, or 9 to 12.

16. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the method as described in any one of claims 1 to 8 or 9 to 12.

17. A computer program product, characterized in that, Includes a computer program that, when executed by a processor, implements the method of any one of claims 1 to 8 or 9 to 12.

18. A funds settlement processing system, characterized in that, It includes a business system and a settlement management system, wherein the settlement management system is used to perform the method as described in any one of claims 1 to 8, and the settlement management system is used to perform the method as described in any one of claims 9 to 12.

Images