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

Abstract

The invention relates to a transaction data processing method and device, equipment, a storage medium and a program product. The method comprises the following steps: in response to a data reconciliation request for a target transaction, obtaining transaction data of the target transaction on each transaction system in a current acquisition time period, and determining the transaction data of the target transaction on each transaction system under the condition that system transaction results contained in each transaction data are not completely the same; according to system transaction results contained in the transaction data and standard transaction result groups corresponding to the target transaction, whether the execution process of the target transaction is abnormal or not is determined, each standard transaction result group comprises standard transaction results of the target transaction under the condition that the transaction systems operate normally, and if not, the target transaction is executed according to the system transaction results. And performing data reconciliation on the transaction data. By adopting the method, the data reconciliation efficiency can be improved.

Description

Technical Field

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

[0002] With the continuous development of trading platforms on the Internet, in order to ensure the reliability of transaction data in the trading platform, the reconciliation system in the financial field can be used to reconcile the transaction data. The existing reconciliation system, for each transaction, needs to first collect the transaction data of the transaction on each transaction end (for example, the deduction end and the transaction end), and then reconcile according to each transaction data.

[0003] However, the existing reconciliation system can only process transaction data in a balanced state, that is, it can only process transaction data with consistent transaction results in each transaction end (for example, the transaction results in each transaction end are successful / failed), which reduces the efficiency of data reconciliation. Summary of the invention

[0004] Based on this, it is necessary to provide a transaction data processing method, device, equipment, storage medium and program product that can improve data reconciliation efficiency in response to the above technical problems.

[0005] In a first aspect, the present application provides a transaction data processing method, comprising:

[0006] In response to a data reconciliation request for a target transaction, acquiring transaction data of the target transaction on each transaction system within a current collection period;

[0007] When it is determined that the system transaction results included in each transaction data are not completely the same, determine whether there is an abnormality in the execution process of the target transaction based on the system transaction results included in each transaction data and the standard transaction result group corresponding to the target transaction; wherein each standard transaction result group includes the standard transaction result of the target transaction when each transaction system is operating normally;

[0008] If not, then the transaction data will be reconciled according to the transaction results of each system.

[0009] In an embodiment of the present application, a standard transaction result group is introduced to determine whether each transaction system is operating normally during the execution of the target transaction, thereby performing data reconciliation on the transaction data generated in the normal operating state, which can improve the efficiency of data reconciliation.

[0010] In one embodiment, determining whether there is an abnormality in the execution process of the target transaction according to the system transaction results included in each transaction data and the standard transaction result group corresponding to the target transaction includes:

[0011] When the system transaction results included in each transaction data match any standard transaction result group corresponding to the target transaction, it is determined that there is no abnormality in the execution process of the target transaction.

[0012] In the embodiment of the present application, by determining whether there is an abnormality in the execution process of the target transaction based on the matching between the transaction results of each system and the standard transaction result group, the reliability of the abnormal situation identification during the transaction execution process can be guaranteed.

[0013] In one embodiment, the method further comprises:

[0014] Obtain a standard acceptance path for the target transaction; wherein the standard acceptance path is determined according to the system acceptance sequence between the transaction systems involved in the target transaction and the internal transaction code of each transaction system; determine a standard transaction result group corresponding to the target transaction according to the system acceptance sequence in the standard acceptance path and the benchmark acceptance system in each transaction system; wherein the benchmark acceptance system is a transaction system whose transaction results in each transaction system can represent the overall transaction result of the target transaction.

[0015] In the embodiment of the present application, by determining the standard transaction result group corresponding to the target transaction according to the system acceptance sequence and the benchmark acceptance system, the rationality of the standard transaction result group can be ensured.

[0016] In one embodiment, data reconciliation is performed on each transaction data according to the transaction results of each system, including:

[0017] Obtain the data processing strategy associated with the standard transaction result group that matches the transaction results of each system; adopt the data processing strategy to perform consistency processing or transaction reversal processing on each transaction data of the system transaction results; and perform data reconciliation on each processed transaction data.

[0018] In the embodiment of the present application, by adopting a data processing strategy, the consistency processing of the system transaction results or the transaction reversal processing is performed on each transaction data, which can ensure the rationality of data processing and thus ensure the reliability of data reconciliation.

[0019] In one embodiment, when it is determined that the system transaction results included in each transaction data are not completely the same, determining whether there is an abnormality in the execution process of the target transaction according to the system transaction results included in each transaction data and the standard transaction result group corresponding to the target transaction includes:

[0020] The data integrity of the target transaction is determined based on the consistency between the transaction system included in the standard transaction flow path corresponding to the target transaction and the transaction system of each acquired transaction data; when the data integrity is data complete and it is determined that the system transaction results included in each transaction data are not completely the same, it is determined whether there is any abnormality in the execution process of the target transaction based on the system transaction results included in each transaction data and the standard transaction result group corresponding to the target transaction.

[0021] In an embodiment of the present application, by determining the data integrity of the target transaction according to the standard transaction flow path, and determining whether there are any abnormalities in the execution process of the target transaction when the transaction data is complete, the rationality of the determination of the abnormal situation in the execution process can be ensured.

[0022] In one embodiment, the method further comprises:

[0023] When the data integrity is incomplete, the data acquisition time is determined according to the data upload cycle of the target transaction system; wherein the target transaction system is a transaction system in the standard transaction flow path except for the transaction system of each acquired transaction data; when the data acquisition time is reached, the transaction data of the target transaction is acquired from the target transaction system, and returned for execution. When it is determined that the system transaction results contained in each transaction data are not completely the same, it is determined whether there is any abnormal operation in the execution process of the target transaction according to the system transaction results contained in each transaction data and the standard transaction result group corresponding to the target transaction.

[0024] In an embodiment of the present application, by reacquiring the transaction data of the target transaction from the target transaction system when the data acquisition time is reached, the transaction data of the target transaction in each transaction system is completed, thereby ensuring the rationality of data reconciliation.

[0025] In a second aspect, the present application further provides a transaction data processing device, comprising:

[0026] A data acquisition module, configured to respond to a data reconciliation request for a target transaction and acquire transaction data of the target transaction on each transaction system within a current collection period;

[0027] The abnormality judgment module is used to determine whether there is an abnormality in the execution process of the target transaction according to the system transaction results contained in each transaction data and the standard transaction result group corresponding to the target transaction when the system transaction results contained in each transaction data are not completely the same; wherein each standard transaction result group includes the standard transaction results of the target transaction when all transaction systems are operating normally;

[0028] The data reconciliation module is used to reconcile the transaction data according to the transaction results of each system.

[0029] In a third aspect, the present application further provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the following steps are implemented:

[0030] In response to a data reconciliation request for a target transaction, acquiring transaction data of the target transaction on each transaction system within a current collection period;

[0031] When it is determined that the system transaction results included in each transaction data are not completely the same, determine whether there is an abnormality in the execution process of the target transaction based on the system transaction results included in each transaction data and the standard transaction result group corresponding to the target transaction; wherein each standard transaction result group includes the standard transaction result of the target transaction when each transaction system is operating normally;

[0032] If not, then the transaction data will be reconciled according to the transaction results of each system.

[0033] In a fourth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor, the following steps are implemented:

[0034] In response to a data reconciliation request for a target transaction, acquiring transaction data of the target transaction on each transaction system within a current collection period;

[0035] When it is determined that the system transaction results included in each transaction data are not completely the same, determine whether there is an abnormality in the execution process of the target transaction based on the system transaction results included in each transaction data and the standard transaction result group corresponding to the target transaction; wherein each standard transaction result group includes the standard transaction result of the target transaction when each transaction system is operating normally;

[0036] If not, then the transaction data will be reconciled according to the transaction results of each system.

[0037] In a fifth aspect, the present application further provides a computer program product, including a computer program, which implements the following steps when executed by a processor:

[0038] In response to a data reconciliation request for a target transaction, acquiring transaction data of the target transaction on each transaction system within a current collection period;

[0039] When it is determined that the system transaction results included in each transaction data are not completely the same, determine whether there is an abnormality in the execution process of the target transaction based on the system transaction results included in each transaction data and the standard transaction result group corresponding to the target transaction; wherein each standard transaction result group includes the standard transaction result of the target transaction when each transaction system is operating normally;

[0040] If not, then the transaction data will be reconciled according to the transaction results of each system.

[0041] The transaction data processing method, device, equipment, storage medium and program product described above obtain the transaction data of the target transaction on each transaction system during the current collection period by responding to the data reconciliation request for the target transaction, and when it is determined that the system transaction results contained in each transaction data are not completely the same, determine whether there is an abnormality in the execution process of the target transaction based on the system transaction results contained in each transaction data and the standard transaction result group corresponding to the target transaction; then, when there is no abnormality in the execution process, perform data reconciliation on each transaction data based on each system transaction result. Compared with the related art, which can only perform data reconciliation on a single balanced transaction data, the above method introduces a standard transaction result group to determine whether each transaction system is operating normally during the execution of the target transaction, thereby performing data reconciliation on the transaction data generated in the normal operating state, which can improve the efficiency of data reconciliation. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] In order to more clearly illustrate the technical solutions in the embodiments of the present application or related technologies, the drawings required for use in the embodiments of the present application or related technical descriptions will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0043] Figure 1 A flowchart of a transaction data processing method in one embodiment;

[0044] Figure 2 A schematic diagram of transaction flow in an embodiment;

[0045] Figure 3 A schematic diagram of a process for determining a standard transaction result group in one embodiment;

[0046] Figure 4 A schematic diagram of a data reconciliation process in an embodiment;

[0047] Figure 5 A flowchart of a transaction data processing method in another embodiment;

[0048] Figure 6 is a structural block diagram of a transaction data processing device in one embodiment;

[0049] Figure 7 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0050] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0051] With the continuous development of trading platforms on the Internet, in order to ensure the reliability of transaction data in the trading platform, the reconciliation system in the financial field can be used to reconcile the transaction data. The existing reconciliation system, for each transaction, needs to first collect the transaction data of the transaction on each transaction end (for example, the deduction end and the transaction end), and then reconcile according to each transaction data.

[0052] However, the existing reconciliation system can only process transaction data in a balanced state, that is, it can only process transaction data with consistent transaction results in each transaction end (for example, the transaction results in each transaction end are successful / failed), which reduces the efficiency of data reconciliation.

[0053] Based on this, in an exemplary embodiment, Figure 1 As shown, a transaction data processing method is provided, which is described by taking the method applied to a data reconciliation device as an example, and specifically includes the following steps:

[0054] S101, in response to a data reconciliation request for a target transaction, obtaining transaction data of the target transaction on each transaction system within a current collection period.

[0055] Among them, the data reconciliation request is a request for reconciliation of the target transaction; the so-called target transaction is any transaction with a reconciliation requirement; the collection period is a period divided based on a preset collection cycle and used to collect transaction data on each transaction system; the current collection period is a sampling period that includes the current collection time.

[0056] Each transaction system is the transaction end involved in the target transaction during the circulation process; transaction data is the data generated when the target transaction is executed on the transaction system. Figure 2 The transaction flow diagram shown in the figure. Among them, sysA is the initiating system in transaction S (for example, the terminal held by the user), sysB is the forwarding system in transaction S, sysC is the deduction core in transaction S (for example, a bank, etc.), and sysD is the account entry core in transaction S (for example, a merchant, etc.). Transaction S is sent from sysA system to sysB, and sysB requests sysC and sysD respectively, thereby completing the execution of transaction S.

[0057] In order to ensure the timeliness of the initiation of the data reconciliation request, a data reconciliation request for the target transaction can be automatically initiated after a preset interval period after the target transaction is generated; or, for the transaction scenario where the target transaction is located, a preset request initiation interval can be used to simultaneously initiate a data reconciliation request for each transaction in the transaction scenario; or, the user can actively initiate a data reconciliation request for the target transaction. In this application, there is no specific restriction on the method of initiating the data reconciliation request.

[0058] After detecting a data reconciliation request for a target transaction, in one possible implementation, the transaction systems associated with the target transaction can be determined based on the standard transaction flow path included in the data reconciliation request; then, based on the transaction identification information of the target transaction, the transaction data generated by the target transaction during the current collection period can be obtained from each transaction system.

[0059] In another possible implementation, in order to improve the efficiency of data acquisition, for each transaction system, the transaction system will upload all transaction data generated in the transaction system to the reconciliation device based on an internal data upload cycle.

[0060] Furthermore, the reconciliation device can divide and process all transaction data based on the transaction identification information of each transaction to obtain the transaction data under each transaction; then, the transaction identification information of the target transaction data in the data reconciliation request can be used as an index to query from the transaction data of each transaction to obtain the transaction data of the target transaction.

[0061] It is understandable that in order to ensure the reliability of transactions, the transaction data may be pre-processed after being obtained. For example, it may include but is not limited to transaction size check, data security check, transaction record number check, and completion of transaction information header. In addition, since the transaction definitions of various components between systems may be inconsistent and may not have unique serial numbers, it is necessary to complete the transaction data between systems.

[0062] S102, when it is determined that the system transaction results included in each transaction data are not completely the same, determine whether there is an abnormality in the execution process of the target transaction according to the system transaction results included in each transaction data and the standard transaction result group corresponding to the target transaction.

[0063] The so-called system transaction result is the transaction result of the transaction in the transaction system, which can be success / failure; the so-called standard transaction result group is the combination of possible transaction results of the target transaction on each transaction system when each transaction system is in normal operation, that is, each standard transaction result group includes the standard transaction results of the target transaction when each transaction system is in normal operation. It can be understood that the transaction result under the normal operation of the transaction system can be success or failure.

[0064] After obtaining the transaction data on each transaction system involved in the target transaction, for each transaction data, the system transaction result of executing the target transaction in the transaction system where the transaction data is located can be obtained from the transaction data.

[0065] When it is determined that the system transaction results contained in each transaction data are exactly the same, it can be proved that the transaction data generated by the target transaction is the balancing data. At this time, each transaction data of the target transaction can be written into the balancing file associated with the balancing data. Subsequently, for each transaction in the balancing file, data reconciliation can be performed based on the transaction flow information in each transaction data of the transaction.

[0066] For example, when the transaction results of the target transaction on each transaction system are all successful or all failed, the transaction data of the target transaction can be written into the reconciliation file; then, the reconciliation device can be used to uniformly reconcile the transaction data under each transaction in the reconciliation file.

[0067] When it is determined that the system transaction results contained in each transaction data are not completely the same, there may be a situation where the system transaction results are not completely the same due to an abnormality in the transaction system, or the system transaction results are not completely the same due to an abnormality in the transaction itself.

[0068] Therefore, in order to determine the reason why the system transaction results are not completely the same, in an optional implementation, the system transaction results contained in each transaction data can be compared with the standard transaction result group generated when the target transaction is operating normally in each transaction system, so as to determine whether there is any abnormality in the execution process of the target transaction.

[0069] In another optional implementation, for the transaction scenario in which the target transaction is located, an anomaly judgment model can be pre-trained based on the standard transaction result group of the target transaction; accordingly, the system transaction results contained in each transaction data can be input into the anomaly judgment model, and the anomaly judgment model outputs whether there is an anomaly in the execution process of the target transaction based on the system transaction results contained in each transaction data and the model parameters.

[0070] S103, if not, then reconcile the transaction data according to the transaction results of each system.

[0071] In one possible implementation, when it is determined that each transaction system is in a normal operating state when executing the target transaction, the abnormal reason for the inconsistent transaction results can be determined based on the transaction results of each system, so as to perform data reconciliation on each transaction data.

[0072] Exemplarily, the cause of the exception can be used as an index to query each candidate cause of the exception and the solution strategy corresponding to the cause of the exception, so as to determine the target solution strategy; then, the target solution strategy can be used to process each transaction data, and the processed transaction data can be reconciled to obtain the data reconciliation result.

[0073] It is understandable that in order to improve the efficiency of reconciliation, when there are no abnormalities in the execution process of the target transaction, the transaction data whose system transaction results are not completely the same can be written into a normal inconsistent file; then, a reconciliation device is used to uniformly reconcile the transaction data in the normal inconsistent file.

[0074] After obtaining the data reconciliation results of each transaction, the abnormal transactions with abnormal data reconciliation results can be fed back to the audit end to prompt the audit end to process the abnormal transactions, thereby ensuring the security and reliability of each transaction.

[0075] In the above transaction data processing method, by responding to the data reconciliation request for the target transaction, the transaction data of the target transaction on each transaction system in the current collection period is obtained, and when it is determined that the system transaction results contained in each transaction data are not completely the same, it is determined whether there is an abnormality in the execution process of the target transaction according to the system transaction results contained in each transaction data and the standard transaction result group corresponding to the target transaction; then, when there is no abnormality in the execution process, data reconciliation is performed on each transaction data according to each system transaction result. Compared with the related art, which can only perform data reconciliation on a single balanced transaction data, the above method introduces a standard transaction result group to determine whether each transaction system is operating normally during the execution of the target transaction, thereby performing data reconciliation on the transaction data generated in the normal operating state, which can improve the efficiency of data reconciliation.

[0076] In order to ensure the accuracy of determining abnormal situations in the execution process, based on the above embodiments, in an embodiment of the present application, an optional method for determining whether there are abnormalities in the execution process of the target transaction is provided. Specifically, when the system transaction results contained in each transaction data match any standard transaction result group corresponding to the target transaction, it is determined that there are no abnormalities in the execution process of the target transaction.

[0077] It is understandable that in order to ensure the standardization of the standard transaction result group, the standard transaction result group is generally generated according to the acceptance order of transactions between various transaction systems.

[0078] Based on this, in an optional implementation, the system transaction results of the target transaction on each transaction system can be combined based on the acceptance order of the target transaction to obtain a transaction result group to be verified; then, the transaction result group to be verified can be compared for consistency with each standard transaction result group.

[0079] If any standard transaction result group is consistent with the transaction result group to be verified, it proves that the problem of inconsistent system transaction results in the target transaction is caused by the transaction itself, that is, there is no abnormality in the execution process of the target transaction; if all standard transaction result groups are inconsistent with the transaction result group to be verified, it proves that the problem of inconsistent system transaction results in the target transaction is caused by system abnormalities, that is, there are abnormalities in the execution process of the target transaction.

[0080] In the embodiment of the present application, by determining whether there is an abnormality in the execution process of the target transaction based on the matching between the transaction results of each system and the standard transaction result group, the reliability of the abnormal situation identification during the transaction execution process can be guaranteed.

[0081] In order to ensure the rationality of the standard transaction result group, based on the above embodiment, in the embodiment of the present application, an optional method for determining the standard transaction result group is provided, such as Figure 3 As shown, the specific steps include:

[0082] S301, obtaining the standard acceptance path of the target transaction.

[0083] The standard acceptance path is determined based on the system acceptance sequence between the transaction systems involved in the target transaction and the internal transaction code of each transaction system. The so-called internal transaction code is the unique identification information of each transaction system; the so-called system acceptance sequence is the flow sequence of resources in the transaction system. For example, the order of deduction of accounts receivable.

[0084] Understandably, in existing reconciliation systems, forked transactions (i.e., multiple systems processing different parts of the same transaction at the same time) are common. However, the processing path of forked transactions is difficult to track and reconcile using unified rules, which may cause some transaction status to be lost or unable to be updated correctly. For example, refer to Figure 2 As shown in the transaction flow diagram, transaction S is sent from sysB to sysC and sysD at the same time, but the existing system often cannot accurately reflect this complex flow path.

[0085] Based on this, in order to more accurately reflect the transaction flow path, an internal transaction code can be added to each system. For example, a unified format can be used to add the internal transaction code of the transaction system to the transaction data. For example, [source system number: internal transaction code] -> [destination system number: internal transaction code].

[0086] For example, refer to Figure 2 As shown in the transaction flow diagram, the standard transaction flow path of transaction S is [sysA:Txn1]->[sysB:Txn2], [sysB:Txn2]->[sysC:Txn3], [sysB:Txn2]->[sysD:Txn4].

[0087] Correspondingly, the acceptance order of transaction S is sysC->sysD->sysB->sysA; further, based on the acceptance order, the internal transaction code of each transaction system is added to generate the standard acceptance path of transaction S [sysC:Txn3]->[sysD:Txn4]->[sysB:Txn2]->[sysA:Txn1].

[0088] In an optional implementation, the standard acceptance path of the target transaction may be directly generated based on the acceptance sequence between the transaction systems of the target transaction and the internal transaction code of each transaction system.

[0089] In another optional implementation, a standard acceptance path associated with each transaction scenario may be pre-configured based on the acceptance sequence of each transaction scenario and the internal transaction code of the transaction system involved in each transaction scenario.

[0090] After obtaining the scenario identifier of the transaction scenario corresponding to the target transaction from the data reconciliation request, the scenario identifier can be used as an index to query from the standard acceptance paths associated with each transaction scenario to obtain the standard acceptance path of the target transaction.

[0091] S302, determining a standard transaction result group corresponding to the target transaction according to the system acceptance sequence in the standard acceptance path and the benchmark acceptance system in each transaction system.

[0092] The benchmark acceptance system is a trading system in which the transaction results of each trading system can represent the overall transaction results of the target transaction. For example, the deduction transaction system in the target transaction can be used as the benchmark acceptance system of the target transaction. That is, if the deduction is successful, it can be regarded as the overall success of the target transaction.

[0093] It is understandable that, since the system acceptance sequence in the standard acceptance path can reflect the deduction progress to a certain extent, the standard transaction result group corresponding to the target transaction can be determined based on the system acceptance sequence and the benchmark acceptance system.

[0094] For example, for the system acceptance sequence sysC->sysD->sysB->sysA, if the system transaction result in sysB is successful, then if the system runs normally, the system transaction results in sysC and sysD should also be successful.

[0095] In an optional implementation, the system transaction results in the benchmark acceptance system can be set to success, and the system transaction results of other transaction systems can be set to failure as a starting point. According to the system acceptance order, the system transaction results of other transaction systems can be set to success in turn, and the standard transaction result group corresponding to the target transaction can be obtained.

[0096] For example, refer to Figure 2 In the transaction flow diagram shown, the system acceptance order of transaction S is sysC-> sysD-> sysB-> sysA, and the base acceptance system is sysC. The standard transaction result group of transaction S can be presented in the following transaction result table. The transaction result table refers to the following Table 1.

[0097] Table 1 Transaction results table

[0098]

[0099] Each row of information in the transaction result table is a standard transaction result group. The first standard transaction result group is {[sysC: success]; [sysD: failure]; [sysB: failure]; [sysA: failure]}; the second standard transaction result group is {[sysC: success]; [sysD: success]; [sysB: failure]; [sysA: failure]}; the third standard transaction result group is {[sysC: success]; [sysD: success]; [sysB: success]; [sysA: failure]}.

[0100] In the embodiment of the present application, by determining the standard transaction result group corresponding to the target transaction according to the system acceptance sequence and the benchmark acceptance system, the rationality of the standard transaction result group can be ensured.

[0101] In order to ensure the reliability of data reconciliation, based on the above embodiments, an optional method of data reconciliation is provided in the embodiments of the present application, such as Figure 4 As shown, the specific steps include:

[0102] S401, obtaining a data processing strategy associated with a standard transaction result group matching each system transaction result.

[0103] Among them, the data processing strategy is the way to process transaction data.

[0104] It is understandable that in order to improve the efficiency of data processing, in an optional implementation, the data processing strategy corresponding to each standard transaction result group can be pre-configured. Then, each system transaction result of the target transaction is used as an index to search the data processing strategy corresponding to each standard transaction result group to obtain the data processing strategy associated with the standard transaction result group matching each system transaction result.

[0105] For example, refer to Figure 2 As shown in the transaction flow diagram, the data processing strategies associated with each standard transaction result group of transaction S can be presented in the form of a processing strategy table. The processing strategy table refers to the following Table 2.

[0106] Table 2 Processing strategy table parameters

[0107]

[0108] S402, adopting a data processing strategy to perform consistency processing of system transaction results or transaction reversal processing on each transaction data.

[0109] Among them, the so-called consistency processing is to modify the transaction results of each system to be consistent; the transaction reversal processing is that when it is uncertain whether the transaction is completed, in order to ensure the interests of the user, it is necessary to cancel the transaction flow. If the benchmark acceptance system has successfully completed the transaction, the transaction will be rolled back. If the benchmark acceptance system transaction fails, it will not be processed.

[0110] In an optional implementation, after determining the data processing strategy corresponding to the target transaction, the data processing strategy can be used to perform consistency processing on the system transaction results of the transaction data with failed system transaction results; or, transaction reversal processing can be performed on the benchmark transaction system.

[0111] For example, referring to Table 2 above, when the system transaction results of the target transaction are {[sysC: success]; [sysD: failure]; [sysB: failure]; [sysA: failure]}, there are too many failed transaction nodes. Therefore, in order to ensure the interests of the user, sysC can be reversed, that is, the flow of the target transaction on sysC is canceled, and the target transaction is re-initiated.

[0112] When the system transaction results of the target transaction are {[sysC: success]; [sysD: success]; [sysB: failure]; [sysA: failure]}, since the target transaction has been successful on the next transaction system of the benchmark acceptance system, the system transaction results of sysA and sysB can be directly set to success.

[0113] Similarly, when the system transaction results of the target transaction are {[sysC: success]; [sysD: success]; [sysB: success]; [sysA: failure]}, the system transaction result of sysA can be directly set to success.

[0114] S403, reconciling the processed transaction data.

[0115] After the transaction data is processed, in an optional implementation, a preset data reconciliation device may be used to perform data reconciliation on each processed transaction data according to the flow information in each transaction data to obtain a data reconciliation result.

[0116] In the embodiment of the present application, by adopting a data processing strategy, the consistency processing of the system transaction results or the transaction reversal processing is performed on each transaction data, which can ensure the rationality of data processing and thus ensure the reliability of data reconciliation.

[0117] In order to ensure the rationality of determining abnormal situations in the execution process, based on the above embodiments, in the embodiments of the present application, another optional method for determining whether there are abnormalities in the execution process of the target transaction is provided, specifically, the data integrity of the target transaction is determined based on the consistency between the transaction system included in the standard transaction flow path corresponding to the target transaction and the transaction system of each acquired transaction data; when the data integrity is data complete and it is determined that the system transaction results included in each transaction data are not exactly the same, it is determined whether there are abnormalities in the execution process of the target transaction based on the system transaction results included in each transaction data and the standard transaction result group corresponding to the target transaction.

[0118] It is understandable that, due to the inconsistency of data upload cycles of various transaction systems, the collected transaction data of a certain transaction may be incomplete. At this time, it is impossible to perform subsequent operations to determine whether there are abnormalities in the execution process of the target transaction. Based on this, after obtaining the transaction data of the target transaction on each transaction system during the current collection period, it is necessary to verify the integrity of each transaction data.

[0119] In one possible implementation, the standard transaction flow path corresponding to the target transaction can be extracted from the data reconciliation request, and the transaction systems involved in the target transaction can be determined based on the standard transaction flow path; then, the transaction systems involved in the target transaction can be compared one by one with the transaction systems corresponding to the acquired transaction data.

[0120] If the transaction systems involved in the target transaction are consistent with the transaction systems corresponding to the acquired transaction data, it proves that the acquired transaction data of the target transaction is complete. At this time, refer to the above step S102. When it is determined that the system transaction results contained in the transaction data are not exactly the same, determine whether there is any abnormality in the execution process of the target transaction based on the system transaction results contained in the transaction data and the standard transaction result group corresponding to the target transaction.

[0121] If the trading systems involved in the target transaction are inconsistent with the trading systems corresponding to the acquired trading data, it proves that the acquired trading data of the target transaction is incomplete. At this time, the trading data of the target transaction can be written into the data missing file. After the subsequent missing trading data is obtained, subsequent operations can be performed to determine whether there are any abnormalities in the execution process of the target transaction.

[0122] In an embodiment of the present application, by determining the data integrity of the target transaction according to the standard transaction flow path, and determining whether there are any abnormalities in the execution process of the target transaction when the transaction data is complete, the rationality of the determination of the abnormal situation in the execution process can be ensured.

[0123] In order to further ensure the rationality of data reconciliation, on the basis of the above embodiments, in the embodiments of the present application, an optional method of processing transaction data is provided for the case where transaction data is incomplete. Specifically, when the data integrity is incomplete, the data acquisition time is determined according to the data upload cycle of the target transaction system; when the data acquisition time is reached, the transaction data of the target transaction is obtained from the target transaction system, and the execution is returned to determine that the system transaction results contained in each transaction data are not exactly the same. According to the system transaction results contained in each transaction data and the standard transaction result group corresponding to the target transaction, it is determined whether there is any abnormal operation in the execution process of the target transaction.

[0124] The target transaction system is a transaction system other than the transaction system of each acquired transaction data in the standard transaction circulation path; the so-called data upload cycle is a preset cycle for the target transaction system to upload transaction data in batches.

[0125] It is understandable that when part of the transaction data is missing, it may be caused by the data upload time being later than the data acquisition time, or it may be caused by the loss of transaction data. If it is caused by the data upload time being later than the data acquisition time, the missing transaction data can be re-acquired at the next data acquisition time; if it is caused by the loss of transaction data, the transaction data cannot be reconciled.

[0126] Based on this, in an optional implementation, when it is determined that the data integrity of the transaction data is incomplete, the target transaction system that has not acquired the transaction data can be determined from the various transaction systems involved in the standard transaction flow path; then, the data acquisition time of the missing transaction data of the target exchange can be determined according to the data upload cycle configured by the target transaction system.

[0127] For example, the current acquisition time of the transaction data in the current collection period may be added to the data upload period configured by the target transaction system to obtain the data acquisition time for reacquiring the missing transaction data.

[0128] When the data acquisition time is reached, the transaction data uploaded by the target transaction system may be queried based on the transaction identifier of the target transaction to obtain the transaction data of the target transaction on the target transaction system.

[0129] If the transaction data of the target transaction can be obtained from the target transaction system, the transaction data of the target transaction can be obtained from the target transaction system and aggregated with other transaction data of the target transaction written into the data missing file; then, for the aggregated transaction data, reference can be made to the above-mentioned step S102. When it is determined that the system transaction results contained in each aggregated transaction data are not completely the same, it can be determined whether there is an abnormality in the execution process of the target transaction based on the system transaction results contained in each transaction data and the standard transaction result group corresponding to the target transaction.

[0130] If the transaction data of the target transaction cannot be obtained from the target transaction system, it proves that the transaction is missing some transaction data due to the loss of transaction data. At this time, the transaction data of the target transaction can be written into the legacy file. The audit end will uniformly process the transaction data of each transaction in the legacy file.

[0131] In an embodiment of the present application, by reacquiring the transaction data of the target transaction from the target transaction system when the data acquisition time is reached, the transaction data of the target transaction in each transaction system is completed, thereby ensuring the rationality of data reconciliation.

[0132] Figure 5 FIG. 2 is a flow chart of a transaction data processing method in another embodiment. Based on the above embodiment, this embodiment provides an optional example of a transaction data processing method. Figure 5 The specific implementation process is as follows:

[0133] S501, obtaining the standard acceptance path of the target transaction.

[0134] Among them, the standard acceptance path is determined according to the system acceptance sequence between the transaction systems involved in the target transaction and the internal transaction code of each transaction system.

[0135] S502, determining a standard transaction result group corresponding to the target transaction according to the system acceptance sequence in the standard acceptance path and the benchmark acceptance system in each transaction system.

[0136] Among them, the benchmark acceptance system is a trading system in which the transaction results in each trading system can represent the overall transaction results of the target transaction; each standard transaction result group includes the standard transaction results of the target transaction when all trading systems operate normally.

[0137] S503, in response to a data reconciliation request for a target transaction, obtaining transaction data of the target transaction on each transaction system within a current collection period.

[0138] S504, judging whether the transaction data of the target transaction is complete based on the consistency between the transaction system included in the standard transaction flow path corresponding to the target transaction and the transaction system of each acquired transaction data, if so, executing S507; if not, executing S505.

[0139] S505: Determine the data acquisition time according to the data upload cycle of the target transaction system.

[0140] The target transaction system is a transaction system other than the transaction system of each acquired transaction data in the standard transaction flow path.

[0141] S506, when the data acquisition time is reached, the transaction data of the target transaction is acquired from the target transaction system, and the process returns to execute S504.

[0142] S507, determine whether the system transaction results included in each transaction data are completely the same, if so, execute S511; if not, execute S508.

[0143] S508, judging whether there is any abnormality in the execution process of the target transaction according to the system transaction results contained in each transaction data and the standard transaction result group corresponding to the target transaction, if so, executing S509; if not, executing S510.

[0144] Optionally, when the system transaction result included in each transaction data matches any standard transaction result group corresponding to the target transaction, it is determined that there is no abnormality in the execution process of the target transaction.

[0145] S509, writing each transaction data of the target transaction into the abnormal inconsistency file.

[0146] S510, obtaining a data processing strategy associated with a standard transaction result group that matches each system transaction result, and using the data processing strategy to perform consistency processing of the system transaction result or transaction reversal processing on each transaction data.

[0147] S511, reconcile the transaction data.

[0148] The specific process of S501-S511 can refer to the description of the above method embodiment, and its implementation principle and technical effect are similar, which will not be repeated here.

[0149] It should be understood that, although the various steps in the flowcharts involved in the above-mentioned embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-mentioned embodiments can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0150] Based on the same inventive concept, the embodiment of the present application also provides a transaction data processing device for implementing the transaction data processing method involved above. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the above method, so the specific limitations in the one or more transaction data processing device embodiments provided below can refer to the limitations of the transaction data processing method above, and will not be repeated here.

[0151] In an exemplary embodiment, Figure 6 As shown, a transaction data processing device 1 is provided, comprising: a data acquisition module 10, an abnormality judgment module 20 and a data reconciliation module 30, wherein:

[0152] The data acquisition module 10 is used to respond to the data reconciliation request for the target transaction and acquire the transaction data of the target transaction on each transaction system during the current collection period;

[0153] The abnormality judgment module 20 is used to determine whether there is an abnormality in the execution process of the target transaction according to the system transaction results contained in each transaction data and the standard transaction result group corresponding to the target transaction when the system transaction results contained in each transaction data are not completely the same; wherein each standard transaction result group includes the standard transaction results of the target transaction when all transaction systems are operating normally;

[0154] The data reconciliation module 30 is used to reconcile the transaction data according to the transaction results of each system if no.

[0155] In an exemplary embodiment, the abnormality determination module 20 is specifically used to:

[0156] When the system transaction results included in each transaction data match any standard transaction result group corresponding to the target transaction, it is determined that there is no abnormality in the execution process of the target transaction.

[0157] In an exemplary embodiment, the transaction data processing device 1 further includes a result group generating module, wherein the result group generating module is specifically used to:

[0158] Obtain a standard acceptance path for the target transaction; wherein the standard acceptance path is determined according to the system acceptance sequence between the transaction systems involved in the target transaction and the internal transaction code of each transaction system; determine a standard transaction result group corresponding to the target transaction according to the system acceptance sequence in the standard acceptance path and the benchmark acceptance system in each transaction system; wherein the benchmark acceptance system is a transaction system whose transaction results in each transaction system can represent the overall transaction result of the target transaction.

[0159] In an exemplary embodiment, the data reconciliation module 30 is specifically used to:

[0160] Obtain the data processing strategy associated with the standard transaction result group that matches the transaction results of each system; adopt the data processing strategy to perform consistency processing or transaction reversal processing on each transaction data of the system transaction results; and perform data reconciliation on each processed transaction data.

[0161] In an exemplary embodiment, the abnormality determination module 20 is further configured to:

[0162] The data integrity of the target transaction is determined based on the consistency between the transaction system included in the standard transaction flow path corresponding to the target transaction and the transaction system of each acquired transaction data; when the data integrity is data complete and it is determined that the system transaction results included in each transaction data are not completely the same, it is determined whether there is any abnormality in the execution process of the target transaction based on the system transaction results included in each transaction data and the standard transaction result group corresponding to the target transaction.

[0163] In an exemplary embodiment, the abnormality determination module 20 is further configured to:

[0164] When the data integrity is incomplete, the data acquisition time is determined according to the data upload cycle of the target transaction system; wherein the target transaction system is a transaction system in the standard transaction flow path except for the transaction system of each acquired transaction data; when the data acquisition time is reached, the transaction data of the target transaction is acquired from the target transaction system, and returned for execution. When it is determined that the system transaction results contained in each transaction data are not completely the same, it is determined whether there is any abnormal operation in the execution process of the target transaction according to the system transaction results contained in each transaction data and the standard transaction result group corresponding to the target transaction.

[0165] Each module in the transaction data processing device can be implemented in whole or in part by software, hardware, or a combination thereof. Each module can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in a computer device in the form of software, so that the processor can call and execute operations corresponding to each module.

[0166] In an exemplary embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as shown in FIG. Figure 7 As shown. The computer device includes a processor, a memory, an input / output interface (Input / Output, referred to as I / O) and a communication interface. The processor, the memory and the input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store transaction data. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a transaction data processing method is implemented.

[0167] Those skilled in the art will understand that Figure 7 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0168] In one embodiment, a computer device is further provided, including a memory and a processor, wherein a computer program is stored in the memory, and the processor implements the steps in the above method embodiments when executing the computer program.

[0169] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments are implemented.

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

[0171] It should be noted that the data involved in this application (including but not limited to transaction data, etc.) are all authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant regulations.

[0172] A person of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment method can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, an artificial intelligence (AI) processor, etc., but are not limited to this.

[0173] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0174] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A transaction data processing method, characterized in that: The method comprises: In response to a data reconciliation request for a target transaction, acquiring transaction data of the target transaction on each transaction system within a current collection period; When it is determined that the system transaction results included in each transaction data are not completely the same, it is determined whether there is an abnormality in the execution process of the target transaction according to the system transaction results included in each transaction data and the standard transaction result group corresponding to the target transaction; wherein each standard transaction result group includes the standard transaction result of the target transaction when each transaction system is operating normally; If not, then the transaction data will be reconciled according to the transaction results of each system.

2. The method according to claim 1, characterized in that The determining whether there is an abnormality in the execution process of the target transaction according to the system transaction results included in each transaction data and the standard transaction result group corresponding to the target transaction includes: When the system transaction result included in each transaction data matches any standard transaction result group corresponding to the target transaction, it is determined that there is no abnormality in the execution process of the target transaction.

3. The method according to claim 1 or 2, characterized in that: The method further comprises: Acquire a standard acceptance path for the target transaction; wherein the standard acceptance path is determined according to a system acceptance sequence between various transaction systems involved in the target transaction and an internal transaction code of each transaction system; According to the system acceptance sequence in the standard acceptance path and the benchmark acceptance system in each transaction system, the standard transaction result group corresponding to the target transaction is determined; wherein the benchmark acceptance system is a transaction system whose transaction results in each transaction system can represent the overall transaction results of the target transaction.

4. The method according to claim 1, characterized in that According to the transaction results of each system, the transaction data is reconciled, including: Obtaining data processing strategies associated with a standard transaction result group that matches each system transaction result; Adopting the data processing strategy, the consistency processing of system transaction results or transaction reversal processing is performed on each transaction data; Perform data reconciliation on each processed transaction data.

5. The method according to claim 1 or 2, characterized in that: When it is determined that the system transaction results included in each transaction data are not completely the same, determining whether there is an abnormality in the execution process of the target transaction according to the system transaction results included in each transaction data and the standard transaction result group corresponding to the target transaction includes: Determining the data integrity of the target transaction based on the consistency between the transaction system included in the standard transaction flow path corresponding to the target transaction and the transaction system of each acquired transaction data; When the data integrity is complete and it is determined that the system transaction results included in each transaction data are not completely the same, it is determined whether there is an abnormality in the execution process of the target transaction based on the system transaction results included in each transaction data and the standard transaction result group corresponding to the target transaction.

6. The method according to claim 5, characterized in that The method further comprises: In the case where the data integrity is incomplete, the data acquisition time is determined according to the data upload cycle of the target transaction system; wherein the target transaction system is a transaction system other than the transaction system of each acquired transaction data in the standard transaction flow path; When the data acquisition time is reached, the transaction data of the target transaction is acquired from the target transaction system, and when it is determined that the system transaction results included in each transaction data are not completely the same, it is determined whether there is any abnormal operation in the execution process of the target transaction based on the system transaction results included in each transaction data and the standard transaction result group corresponding to the target transaction.

7. A transaction data processing device, characterized in that: The device comprises: A data acquisition module, configured to respond to a data reconciliation request for a target transaction and acquire transaction data of the target transaction on each transaction system within a current collection period; an abnormality judgment module, used to determine whether there is an abnormality in the execution process of the target transaction according to the system transaction results contained in each transaction data and the standard transaction result group corresponding to the target transaction when the system transaction results contained in each transaction data are not completely the same; wherein each standard transaction result group includes the standard transaction result of the target transaction when each transaction system is operating normally; The data reconciliation module is used to reconcile the transaction data according to the transaction results of each system.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 6 are implemented.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

Images