A transaction flow reconciliation method, system, device and storage medium

Abstract

The present application discloses a transaction flow reconciliation method, system, device and storage medium, the method comprising: connecting with each transaction channel through an API interface to obtain transaction data in real time; storing the transaction data of each transaction channel in order of transaction time; performing reconciliation processing on each transaction data of each transaction channel, and obtaining the reconciliation result of each transaction data of each transaction channel; the reconciliation processing comprises: extracting key information of each transaction data of each transaction channel respectively, comparing key information of each transaction data of each transaction channel with each transaction data of other transaction channels; performing abnormal verification according to preset transaction business rules for each transaction data of each transaction channel judged to be abnormal. The present application can realize timely, efficient and accurate reconciliation of transaction flow.

Description

Technical Field

[0001] The present application relates to the technical field of transaction flow reconciliation, and specifically to a transaction flow reconciliation method, system, device and storage medium. Background Art

[0002] With the popularity of electronic payment methods, transaction flow data is becoming increasingly large, and the need for reconciliation is becoming stronger. Traditional reconciliation methods, such as manual reconciliation by downloading documents, are not only cumbersome to operate, but also inefficient and error-prone when processing large amounts of data.

[0003] Although the existing reconciliation system has achieved automation to a certain extent, it still needs to be improved in terms of the comprehensiveness and real-time nature of data collection, the rationality of the data storage structure, the intelligence and accuracy of the reconciliation process, and the flexibility of abnormal data processing.

[0004] Therefore, it is particularly important to develop a system and method that can conduct transaction flow reconciliation in a timely, accurate and efficient manner. Summary of the invention

[0005] In order to achieve timely, efficient and accurate reconciliation of transaction flows, the present application provides a transaction flow reconciliation method, system, device and storage medium.

[0006] In a first aspect, the present application provides a transaction flow reconciliation method, comprising:

[0007] Connect with various transaction channels through API interface to obtain transaction data in real time;

[0008] The transaction data of each transaction channel is stored in the order of transaction time;

[0009] Reconciliation processing is performed for each transaction data of each transaction channel, and the reconciliation result of each transaction data of each transaction channel is obtained; the reconciliation processing includes: extracting key information for each transaction data of each transaction channel, and the key information includes: transaction time, transaction user and supplier, transaction type, transaction status, transaction product and service; comparing the key information of each transaction data of each transaction channel with each transaction data of other transaction channels; if the key information of a transaction data of one transaction channel is consistent with the key information of a transaction data of other transaction channels, then it is determined that the reconciliation of the transaction data of the transaction channel is successful, otherwise, it is determined that the transaction data of the transaction channel is abnormal;

[0010] For each transaction data of each transaction channel judged to be abnormal, an abnormality verification is performed according to the preset transaction business rules; the preset transaction business rules include: coupon usage rules, transaction product and service equivalence rules and transaction user and supplier account abnormality rules; the abnormality verification according to the preset transaction rules includes: for each transaction data of each abnormal transaction channel, according to the key information, searching for a transaction data of a transaction channel with the closest key information from each transaction data of the other abnormal transaction channels; judging whether the inconsistent key information between each transaction data of each abnormal transaction channel and a transaction data of a transaction channel with the closest key information can be explained according to the preset transaction rules; if it can be explained, the transaction data of the transaction channel is re-determined to be reconciled successfully; otherwise, an abnormal transaction data mark is generated.

[0011] Adopt real-time data collection method of multiple transaction channels and store them in order in multiple transaction channels, so as to ensure the comprehensiveness, real-time and query efficiency of transaction data, and provide a basis for the subsequent timely and accurate comparison of multiple data sources; adopt automation to reconcile the collected transaction data and conduct reconciliation verification for abnormal transaction data, so as to improve the accuracy and efficiency of reconciliation.

[0012] Preferably, it also includes:

[0013] Determine whether the current time period is a peak time period for acquiring transaction data, where the peak time period for acquiring transaction data refers to a time period when the amount of acquired transaction data is greater than a preset amount of data; if it is a peak time period for acquiring transaction data, reconciliation processing is immediately performed on the real-time acquired transaction data to obtain a reconciliation result; otherwise, reconciliation processing is performed on the transaction data acquired within the preset time period to obtain a reconciliation result.

[0014] By adopting the above solution, considering that there are peak periods for transaction data acquisition, real-time reconciliation processing is carried out during peak periods to reduce the pressure of subsequent transaction data reconciliation processing. Intermittent reconciliation processing can be carried out for the remaining periods to reduce the calculation, operation and maintenance costs of reconciliation processing.

[0015] Preferably, it also includes: before comparing the key information of each transaction data of each transaction channel with that of each transaction data of the remaining transaction channels, pre-querying a preset comparison rule based on the transaction type of each transaction data of each transaction channel; wherein, corresponding comparison rules are preset for comparing the key information of transaction data of different transaction types; and according to the preset comparison rules, completing the comparison of the key information of each transaction data of each transaction channel with that of each transaction data of the remaining transaction channels.

[0016] By adopting the above solution, different transaction types are taken into consideration. For example, transaction data with relatively large amounts require more detailed comparison. Based on preset comparison rules for different transaction types, the reconciliation processing of each transaction data of each transaction channel is completed to improve the accuracy of the reconciliation results.

[0017] Preferably, it also includes: each transaction data obtained from each transaction channel has a unique verification code when the transaction data is generated; when comparing the key information of each transaction data of each transaction channel with the key information of each transaction data of the remaining transaction channels, it is simultaneously judged whether the verification codes of each transaction data of the two transaction channels are consistent; if the key information of a transaction data of one transaction channel is consistent with the key information of a transaction data of the remaining transaction channels and the verification codes of the corresponding two transaction data are consistent, then it is determined that the transaction data of the transaction channel is reconciled successfully, otherwise, it is determined that there is an abnormality in the transaction data of the transaction channel.

[0018] By adopting the above solution, taking into account the possibility that the acquired transaction data is tampered with, in order to prevent the correctness of the reconciliation result from being affected by the tampered transaction data, a verification code is designed and the verification code matching is performed, thereby ensuring the accuracy of the reconciliation result.

[0019] Preferably, the method of connecting with various transaction channels through the API interface to obtain transaction data in real time includes: active acquisition and push from the other party; when the transaction data is obtained based on active acquisition and push from the other party at the same time, query the reconciliation result corresponding to the transaction data pushed by the other party within a historically adjacent period of time; if the reconciliation result is a successful reconciliation and the proportion of successful reconciliation in all reconciliation results is less than a preset proportion, the transaction data obtained based on the active acquisition method is given priority, otherwise, the transaction data is obtained based on a combination of active acquisition and push from the other party.

[0020] By adopting the above solution, taking into account the various ways of obtaining transaction data, a combination of multiple methods is used to ensure that the obtained transaction data is more comprehensive. However, considering that the content pushed by the other party may have the risk of data tampering, the reconciliation result of the obtained transaction data is combined to determine whether there is a problem with the other party's push method, so as to further decide whether to conduct comprehensive transaction data, thereby ensuring the accuracy of the transaction data while ensuring the comprehensiveness of the transaction data.

[0021] Preferably, a distributed computing method is used to reconcile each transaction data of each transaction channel.

[0022] By adopting the above solution, in order to improve the reconciliation processing speed of transaction data, a distributed computing method is chosen to synchronously reconcile multiple transaction data.

[0023] Preferably, it also includes:

[0024] Obtain the transaction data reconciliation result acquisition request sent by the user terminal or the supplier terminal, and determine whether the current user account is an authorized account; if it is an authorized account, match the security level of the requested transaction data reconciliation result according to the transaction type of the requested transaction data, and different transaction types are matched with corresponding transaction data reconciliation result security levels;

[0025] If the security level of the requested transaction data reconciliation result is a low security level, the transaction data reconciliation result is directly sent to the corresponding user terminal or supplier terminal; if the security level of the requested transaction data reconciliation result is a high security level, the transaction data reconciliation result request confirmation information is sent to the corresponding user terminal or supplier terminal again, and after the corresponding user terminal or supplier terminal receives the confirmation information feedback, the encrypted transaction data reconciliation result and the dynamic password are sent to the corresponding user terminal or supplier terminal.

[0026] By adopting the above solution, users are authorized to view the reconciliation results of corresponding transaction data, and query steps are set based on the security levels of transaction data of different transaction types to further ensure the security of the reconciliation results of transaction data authorized by users.

[0027] In a second aspect, the present application provides a transaction flow reconciliation system, comprising:

[0028] The transaction data acquisition module is used to connect with various transaction channels through the API interface to obtain transaction data in real time;

[0029] A transaction data storage module is used to store the transaction data of each transaction channel in order of transaction time;

[0030] The transaction data reconciliation processing module is used to perform reconciliation processing on each transaction data of each transaction channel and obtain the reconciliation result of each transaction data of each transaction channel; the reconciliation processing includes: extracting key information of each transaction data of each transaction channel, and the key information includes: transaction time, transaction user and supplier, transaction type, transaction status, transaction product and service; comparing the key information of each transaction data of each transaction channel with each transaction data of other transaction channels; if the key information of a transaction data of one transaction channel is consistent with the key information of a transaction data of other transaction channels, then it is determined that the transaction data of the transaction channel is successfully reconciled, otherwise, it is determined that the transaction data of the transaction channel is abnormal;

[0031] The transaction data reconciliation result verification module is used to perform anomaly verification according to preset transaction business rules for each transaction data of each transaction channel judged to be abnormal; the preset transaction business rules include: coupon usage rules, transaction product and service equivalence rules and transaction user and supplier account abnormality rules; the anomaly verification according to the preset transaction rules includes: for each transaction data of each abnormal transaction channel, according to the key information, search for a transaction data of a transaction channel with the closest key information from the transaction data of the remaining abnormal transaction channels; determine whether the inconsistent key information between each transaction data of each abnormal transaction channel and the transaction data of a transaction channel with the closest key information can be explained according to the preset transaction rules. If it can be explained, the reconciliation of the transaction data of the transaction channel is re-determined to be successful, otherwise, an abnormal transaction data mark is generated.

[0032] By adopting the above solution, efficient and accurate transaction flow reconciliation is achieved, the problem of cumbersome and inefficient traditional reconciliation methods is solved, and the efficiency and accuracy of reconciliation work are improved.

[0033] In a third aspect, the present application provides a computer-readable storage medium, wherein the computer-readable storage medium includes a stored computer program, wherein when the computer program is executed, the device where the computer-readable storage medium is located is controlled to execute the method as described above.

[0034] In a fourth aspect, the present application provides a computer device, comprising a memory, a processor, and a program stored and executable on the memory, wherein the program implements the steps of the above method when executed by the processor.

[0035] In summary, the present application has the following beneficial effects: 1. It adopts a real-time data collection method for multiple transaction channels and optimizes the storage of multiple transaction channels in an orderly manner, ensuring the comprehensiveness, real-time nature and query efficiency of transaction data, and providing a basis for the subsequent timely and accurate comparison of multiple data sources; it adopts automation to reconcile the collected transaction data and conduct reconciliation verification processing for abnormal transaction data, thereby improving the accuracy and efficiency of reconciliation;

[0036] 2. Based on whether the acquisition period of transaction data is during the peak period, timely or periodic reconciliation of transaction data should be completed to achieve timely and low-cost reconciliation of transaction data;

[0037] 3. According to the transaction type of transaction data, the reconciliation of transaction data is completed according to the preset comparison rules, so as to further improve the accuracy and efficiency of reconciliation. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] Figure 1It is a flow chart of a transaction flow reconciliation method described in a specific embodiment;

[0039] Figure 2 It is a structural diagram of a transaction flow reconciliation system described in a specific embodiment. DETAILED DESCRIPTION

[0040] 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.

[0041] Example 1

[0042] like Figure 1 As shown, the embodiment of the present application discloses a transaction flow reconciliation method, which is applicable to various fields with frequent transactions such as finance and e-commerce; the specific steps are as follows:

[0043] S1. Obtain transaction data from multiple channels in real time.

[0044] Specifically, the transaction data of each transaction channel is obtained by connecting with each transaction channel through the API interface. This embodiment is an e-commerce transaction scenario, and each transaction channel can come from multiple user apps, multiple supplier platforms, etc. Among them, the transaction data of each transaction channel can be obtained by actively obtaining and pushing from the other party.

[0045] S2. Store the transaction data of each transaction channel in order of transaction time.

[0046] Specifically, in order to improve the efficiency of reconciliation, the transaction data is stored in the order of transaction time. For each transaction data, its key fields can be selected for subsequent query using index technology. These key fields correspond to the key information of the transaction data; the key information includes: transaction time, transaction user and supplier (such as user ID or name, supplier ID or nickname, etc.), transaction amount, transaction type (such as purchase type, refund type, trial type, exchange type, etc.), transaction status (such as completed, paid on behalf of, canceled, etc.), transaction products and services (such as product name or service type, etc.), etc.

[0047] S3. Perform reconciliation processing on each transaction data of each transaction channel, and obtain the reconciliation result of each transaction data of each transaction channel.

[0048] Specifically, the reconciliation process for each transaction data obtained from transaction channels such as user APP or supplier platform includes:

[0049] Key information is extracted for each transaction data of each transaction channel respectively; if the key information of the key field has been recorded in the process of storing each transaction data, the key information of each transaction data is directly indexed and obtained; if the key field is not recorded in the process of storing each transaction data, the key information recognition technology based on machine learning is selected, such as: using a neural network trained and generated by historical transaction data marked with key information to identify and obtain the key information of each transaction data.

[0050] Preprocessing is performed on the key information extracted from each transaction data of each transaction channel; the preprocessing includes: cleaning and deduplication, modification of data format, and sorting according to preset sorting rules, etc.; wherein the preset sorting rules include: transaction time, transaction user and supplier, transaction amount, transaction type, transaction status, transaction products and services, etc.

[0051] For each transaction data of each transaction channel, key information of each transaction data of the remaining transaction channels is compared in pairs; where, under the condition of abundant computing resources, a distributed computing method can be used to independently compare key information of each transaction data of multiple transaction channels. For example: obtain three transaction channels (user APP1, supplier platform 1 and supplier platform 2), two transaction data of user APP1, one transaction data of supplier platform 1 and two transaction data of supplier platform 2; compare one transaction data of user APP1 with one transaction data of supplier platform 1 and two transaction data of supplier platform 2, compare one transaction data of supplier platform 1 with one transaction data of user APP1 and two transaction data of supplier platform 2, and compare each transaction data of supplier platform 2 with one transaction data of user APP1 and one transaction data of supplier platform 1.

[0052] If the key information of a transaction data of a transaction channel is consistent with the key information of a transaction data of other transaction channels, the transaction data of the transaction channel is deemed to be reconciled successfully, otherwise, the transaction data of the transaction channel is deemed to be abnormal. For example: the key information of a transaction data of user APP1 includes: 9:13, user ID 1010 and supplier ID 2563, purchase type, 256 yuan, completed, tennis racket; if the same key information is found in a transaction data of supplier platform 1, the transaction data of user APP1 is deemed to be reconciled successfully.

[0053] S4. For each transaction data of each transaction channel judged to be abnormal, an abnormality verification is performed according to the preset transaction business rules.

[0054] Specifically, the preset transaction business rules include: coupon usage rules, transaction product and service equivalence rules, and transaction user and supplier account abnormality rules; wherein each preset transaction business rule includes rules that may lead to inconsistency in key information between users and suppliers. Among them, the coupon usage rules include rules that may lead to inconsistency in transaction amounts between users and suppliers, such as: the rule that there is a difference of 50 yuan in transaction amounts between users and suppliers when using a coupon that reduces 50 yuan for every 200 yuan of purchase amount; the transaction product and service equivalence rules include rules that may lead to different names of transaction products and services between users and suppliers, such as: the rules that the names of transaction products between users and suppliers are common names and scientific names respectively; the transaction user and supplier account abnormality rules include rules that may lead to inconsistency in transaction status between users and suppliers; such as: the supplier account is temporarily frozen, resulting in the transaction status between users and suppliers being paid and pending payment respectively, and the transaction status is inconsistent.

[0055] The abnormal verification according to the preset transaction rules includes:

[0056] For each transaction data of each abnormal transaction channel, search for a transaction data of a transaction channel with the closest key information (highest key information similarity) from the transaction data of the other abnormal transaction channels based on the key information; determine whether the inconsistent key information between each transaction data of each abnormal transaction channel and the transaction data of a transaction channel with the closest key information can be explained according to the preset transaction rules; if it can be explained, reconcile the transaction data of the transaction channel successfully; otherwise, generate an abnormal transaction data mark.

[0057] In addition, for each transaction data marked as abnormal, a transaction data of a transaction channel that is closest to the key information being searched is input into the abnormal cause analysis model to obtain an output abnormal cause analysis result; the abnormal cause analysis model adopts a neural network model and is trained and generated using two historical transaction data marked with cause analysis results and inconsistent key information.

[0058] S5. Generate a reconciliation report for each transaction channel based on the reconciliation result of each transaction data of each transaction channel.

[0059] Specifically, the reconciliation report of each transaction channel distinguishes between transaction data that has been reconciled successfully and transaction data that has been marked as abnormal. Considering the security of users and suppliers obtaining reconciliation reports of corresponding transaction data, a request for obtaining transaction data reconciliation results sent by a user terminal or a supplier terminal can be obtained to determine whether the current user terminal or supplier terminal is an authorized terminal; if it is an authorized terminal, the reconciliation report of the transaction channel corresponding to the requested transaction data is sent to the user terminal or the supplier terminal.

[0060] In addition, the abnormal reasons for the abnormally marked transaction data can be analyzed, and the processing strategies used when querying the historical transaction data that caused the abnormalities due to the same abnormal reasons can be used to generate the abnormal processing strategies corresponding to the most used processing strategies. For example, if the transaction amount difference between the user and the supplier is doubled, and the abnormal reason is that the user paid repeatedly, the corresponding abnormal processing strategy for refund is generated.

[0061] By adopting the method described in this embodiment, timely, efficient and accurate transaction flow reconciliation is achieved.

[0062] Example 2

[0063] The difference from Example 1 is that this embodiment further considers the amount of acquired transaction data and adaptively decides to adopt real-time reconciliation processing or periodic reconciliation processing to reduce the pressure of subsequent transaction data reconciliation processing and reduce the calculation, operation and maintenance costs of reconciliation processing. The method also includes:

[0064] Determine whether the current time period is a peak time period for acquiring transaction data, wherein the peak time period for acquiring transaction data refers to a time period when the amount of transaction data currently acquired is greater than a preset amount of data; the preset amount of data is artificially set according to current computing resources.

[0065] If it is the peak period for acquiring transaction data, the use of periodic reconciliation processing may face the problem of insufficient computing power. Immediately perform reconciliation processing on the real-time acquired transaction data to obtain the reconciliation results;

[0066] Otherwise, the transaction data acquired within the preset time period is acquired for reconciliation processing to obtain the reconciliation result. In this embodiment, the preset time period is set to one day, one week or one month.

[0067] Example 3

[0068] The difference from Example 1 is that, in order to further ensure the accuracy of account reconciliation, the method of this embodiment further includes:

[0069] Before comparing the key information of each transaction data of each transaction channel with that of each transaction data of other transaction channels, preset comparison rules are queried in advance according to the transaction type of each transaction data of each transaction channel; wherein, corresponding comparison rules are preset for comparing the key information of transaction data of different transaction types.

[0070] In this embodiment, considering that the number of key information of transaction data of different transaction types is different or the degree of confidentiality is different, the complexity of the corresponding comparison process is different. Therefore, a comparison rule corresponding to the number of comparisons can be preset for the comparison of key information of transaction data of different transaction types. For example, a multiple comparison rule is preset for the comparison of key information of purchase type transaction data, and a single comparison rule is preset for the comparison of key information of refund type transaction data.

[0071] According to the preset comparison rules obtained by the query, key information of each transaction data of each transaction channel is compared with each transaction data of other transaction channels.

[0072] Example 4

[0073] The difference from Example 1 is that, in order to further ensure the accuracy of account reconciliation, the method of this embodiment further includes:

[0074] Each transaction data obtained from each transaction channel has a unique verification code when the transaction data is generated; that is, the verification codes corresponding to a transaction data generated based on the same group of users and suppliers are consistent. For example: when the transaction data of tennis purchase generated between user APP1 and supplier platform 1 is generated, a verification code userX1-applyY1 is generated accordingly, that is, the verification code userX1-applyY1 of the transaction data obtained from the transaction channel of user APP1 matches the verification code userX1-applyY1 of the transaction data obtained from the transaction channel of supplier platform 1.

[0075] When comparing the key information of each transaction data of each transaction channel with each transaction data of other transaction channels, it is simultaneously determined whether the verification codes of each transaction data of each transaction channel are consistent.

[0076] If the key information of a transaction data of a transaction channel is consistent with the key information of a transaction data of other transaction channels and the corresponding verification codes of the two transaction data are consistent, then the transaction data of the transaction channel is deemed to be reconciled successfully, otherwise, the transaction data of the transaction channel is deemed to be abnormal. For example: the key information of a transaction data of user APP1 includes: 9:13, user ID 1010 and supplier ID 2563, purchase type, 256 yuan, completed, tennis racket; compare the same key information of a transaction data of supplier platform 1, and both have the same verification code userX1-applyY1, then the transaction data of user APP1 is deemed to be reconciled successfully.

[0077] Example 5

[0078] The difference from Example 1 is that, in order to ensure the comprehensiveness and security of transaction data collection and the accuracy of account reconciliation, the method of this embodiment further includes:

[0079] The method of obtaining transaction data of each transaction channel is as follows: when obtaining transaction data based on active acquisition and other party push at the same time, query the reconciliation results corresponding to the transaction data pushed by the other party within a historical adjacent period of time. In this embodiment, the historical adjacent period of time is one month.

[0080] If the reconciliation result is a successful reconciliation and the proportion of successful reconciliation is less than the preset proportion, the proportion of successful reconciliation is: the proportion of successful reconciliation results to all reconciliation results, then it indicates that there is a problem with the accuracy of the transaction data pushed by the other party, and the transaction data obtained based on the active acquisition method is given priority. Otherwise, choose to use active acquisition and the other party's push method to obtain multi-channel transaction data in real time, that is, choose the transaction data obtained based on the other party's push method and the transaction data obtained comprehensively based on the active acquisition method, such as merging and deleting duplicate transaction data.

[0081] Example 6

[0082] The difference from Example 1 is that, in order to further ensure the security of obtaining the transaction data reconciliation result, the method of this embodiment further includes:

[0083] Obtain the transaction data reconciliation result acquisition request sent by the user terminal or supplier terminal, and determine whether the current user terminal or supplier terminal is an authorized terminal; if it is an authorized terminal, match the security level of the requested transaction data reconciliation result according to the transaction type of the requested transaction data, and different transaction types have corresponding security levels of transaction data reconciliation results; for example: the security level of the transaction data reconciliation result corresponding to the purchase type and the refund type is a high security level; the security level of the transaction data reconciliation result corresponding to the trial type and the exchange type is a low security level.

[0084] If the security level of the requested transaction data reconciliation result is a low security level, the transaction data reconciliation result is directly sent to the corresponding user terminal or supplier terminal; if the security level of the requested transaction data reconciliation result is a high security level, the transaction data reconciliation result request confirmation information is sent to the corresponding user terminal or supplier terminal again, and after receiving the confirmation information fed back by the corresponding user terminal or supplier terminal, the encrypted transaction data reconciliation result and the dynamic password are sent to the user terminal or supplier terminal for viewing.

[0085] In addition, for some transaction data, the user terminal and the supplier terminal may have a priority processing requirement. To meet the corresponding requirement, the method described in this embodiment further includes:

[0086] To obtain the request for priority reconciliation of transaction data uploaded by the user terminal or supplier terminal through the API interface, query whether the user terminal or supplier terminal has the priority reconciliation authority. If the query result shows that the priority reconciliation authority exists, the transaction data of the corresponding user terminal or supplier terminal will be reconciled in priority according to the order of the received priority reconciliation requests.

[0087] like Figure 2 As shown, the embodiment of the present application discloses a transaction flow reconciliation system, which specifically includes:

[0088] The transaction data acquisition module 101 is used to connect with various transaction channels through an API interface to obtain transaction data in real time;

[0089] The transaction data storage module 102 is used to store the transaction data of each transaction channel in order of transaction time;

[0090] The transaction data reconciliation processing module 103 is used to perform reconciliation processing on each transaction data of each transaction channel and obtain the reconciliation result of each transaction data of each transaction channel; the reconciliation processing includes: extracting key information of each transaction data of each transaction channel, and the key information includes: transaction time, transaction user and supplier, transaction type, transaction status, transaction product and service; comparing the key information of each transaction data of each transaction channel with each transaction data of other transaction channels; if the key information of a transaction data of one transaction channel is consistent with the key information of a transaction data of other transaction channels, then it is determined that the transaction data of the transaction channel is successfully reconciled, otherwise, it is determined that the transaction data of the transaction channel is abnormal;

[0091] The transaction data reconciliation result verification module 104 is used to perform anomaly verification according to preset transaction business rules for each transaction data of each transaction channel judged to be abnormal; the preset transaction business rules include: coupon usage rules, transaction product and service equivalence rules and transaction user and supplier account abnormality rules; the anomaly verification according to the preset transaction rules includes: for each transaction data of each abnormal transaction channel, according to the key information, searching for a transaction data of a transaction channel with the closest key information from each transaction data of the other abnormal transaction channels; judging whether the inconsistent key information between each transaction data of each abnormal transaction channel and a transaction data of a transaction channel with the closest key information can be explained according to the preset transaction rules, if it can be explained, then re-determining that the reconciliation of the transaction data of the transaction channel is successful, otherwise, generating an abnormal transaction data mark.

[0092] The transaction data reconciliation report generating module 105 is used to generate a reconciliation report for each transaction channel according to the reconciliation result of each transaction data of each transaction channel.

[0093] The embodiment of the present application also discloses a computer-readable storage medium.

[0094] Specifically, the computer-readable storage medium stores a computer program that can be loaded by a processor and execute the transaction flow reconciliation method as described above. The computer-readable storage medium includes, for example: a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and other media that can store program codes.

[0095] The embodiment of the present application also discloses a computer device.

[0096] Specifically, the computer device includes a memory and a processor, and the memory stores a computer program that can be loaded by the processor and execute the above-mentioned transaction flow reconciliation method.

[0097] The above are all preferred embodiments of the present application, and are not intended to limit the protection scope of the present application. Any feature disclosed in this specification (including the abstract and drawings), unless otherwise stated, can be replaced by other equivalent or alternative features with similar purposes. That is, unless otherwise stated, each feature is only an example of a series of equivalent or similar features.

Claims

1. A transaction flow reconciliation method, characterized in that: include: Connect with various transaction channels through API interface to obtain transaction data in real time; The method of connecting with each transaction channel through the API interface to obtain transaction data in real time includes: active acquisition and push from the other party; when the transaction data is obtained based on active acquisition and push from the other party at the same time, query the reconciliation result corresponding to the transaction data pushed by the other party within a period of time in history; if the reconciliation result is a successful reconciliation and the proportion of successful reconciliation to all reconciliation results is less than a preset proportion, the transaction data obtained based on the active acquisition method is preferred, otherwise, the transaction data is obtained based on the active acquisition and push from the other party in combination; The transaction data of each transaction channel is stored in the order of transaction time; Reconciliation processing is performed for each transaction data of each transaction channel, and the reconciliation result of each transaction data of each transaction channel is obtained; the reconciliation processing includes: extracting key information for each transaction data of each transaction channel, and the key information includes: transaction time, transaction user and supplier, transaction type, transaction status, transaction product and service; comparing the key information of each transaction data of each transaction channel with each transaction data of other transaction channels; if the key information of a transaction data of one transaction channel is consistent with the key information of a transaction data of other transaction channels, then it is determined that the reconciliation of the transaction data of the transaction channel is successful, otherwise, it is determined that the transaction data of the transaction channel is abnormal; For each transaction data of each transaction channel judged to be abnormal, an abnormality verification is performed according to the preset transaction business rules; the preset transaction business rules include: coupon usage rules, transaction product and service equivalence rules and transaction user and supplier account abnormality rules; the abnormality verification according to the preset transaction business rules includes: for each transaction data of each abnormal transaction channel, according to the key information, searching for a transaction data of a transaction channel with the closest key information from each transaction data of the other abnormal transaction channels; judging whether the inconsistent key information between each transaction data of each abnormal transaction channel and a transaction data of a transaction channel with the closest key information can be explained according to the preset transaction business rules; if it can be explained, the transaction data of the transaction channel is re-determined to be reconciled successfully, otherwise, an abnormal transaction data mark is generated.

2. The transaction flow reconciliation method according to claim 1, characterized in that: Also includes: Determine whether the current time period is a peak time period for acquiring transaction data, where the peak time period for acquiring transaction data refers to a time period when the amount of acquired transaction data is greater than a preset amount of data; If it is a peak period for acquiring transaction data, reconciliation processing is immediately performed on the real-time acquired transaction data to obtain a reconciliation result; otherwise, reconciliation processing is performed on the transaction data acquired within a preset time period to obtain a reconciliation result.

3. The transaction flow reconciliation method according to claim 1, characterized in that: Also includes: Before comparing the key information of each transaction data of each transaction channel with each transaction data of other transaction channels, a preset comparison rule is queried in advance according to the transaction type of each transaction data of each transaction channel; wherein, the key information comparison of transaction data of different transaction types has corresponding preset comparison rules; According to the preset comparison rules of the query, key information of each transaction data of each transaction channel is compared with each transaction data of other transaction channels.

4. The transaction flow reconciliation method according to claim 1, characterized in that: Also includes: Each transaction data obtained from each transaction channel has a unique verification code when the transaction data is generated; when the key information of each transaction data of each transaction channel is compared with the key information of each transaction data of other transaction channels, it is simultaneously judged whether the verification codes of each transaction data of two transaction channels are consistent; if the key information of a transaction data of one transaction channel is consistent with the key information of a transaction data of other transaction channels and the verification codes of the corresponding two transaction data are consistent, then it is determined that the transaction data of the transaction channel is reconciled successfully, otherwise, it is determined that there is an abnormality in the transaction data of the transaction channel.

5. The transaction flow reconciliation method according to claim 1, characterized in that: Also includes: Distributed computing is used to reconcile each transaction data of each transaction channel.

6. The transaction flow reconciliation method according to claim 1, characterized in that: Also includes: Obtain the transaction data reconciliation result acquisition request sent by the user terminal or supplier terminal, and determine whether the current user account is an authorized account; If it is an authorized account, the security level of the requested transaction data reconciliation result is matched according to the transaction type of the requested transaction data. Different transaction types are matched with corresponding security levels of transaction data reconciliation results. If the security level of the requested transaction data reconciliation result is a low security level, the transaction data reconciliation result is directly sent to the corresponding user terminal or supplier terminal; if the security level of the requested transaction data reconciliation result is a high security level, the transaction data reconciliation result request confirmation information is sent to the corresponding user terminal or supplier terminal again, and after the corresponding user terminal or supplier terminal receives the confirmation information feedback, the encrypted transaction data reconciliation result and the dynamic password are sent to the corresponding user terminal or supplier terminal.

7. A transaction flow reconciliation system, characterized in that: include: The transaction data acquisition module is used to connect with various transaction channels through the API interface to obtain transaction data in real time; The method of connecting with each transaction channel through the API interface to obtain transaction data in real time includes: active acquisition and push from the other party; when the transaction data is obtained based on active acquisition and push from the other party at the same time, query the reconciliation result corresponding to the transaction data pushed by the other party within a period of time in history; if the reconciliation result is a successful reconciliation and the proportion of successful reconciliation to all reconciliation results is less than a preset proportion, the transaction data obtained based on the active acquisition method is preferred, otherwise, the transaction data is obtained based on the active acquisition and push from the other party in combination; A transaction data storage module is used to store the transaction data of each transaction channel in order of transaction time; The transaction data reconciliation processing module is used to perform reconciliation processing on each transaction data of each transaction channel and obtain the reconciliation result of each transaction data of each transaction channel; the reconciliation processing includes: extracting key information of each transaction data of each transaction channel, and the key information includes: transaction time, transaction user and supplier, transaction type, transaction status, transaction product and service; comparing the key information of each transaction data of each transaction channel with each transaction data of other transaction channels; if the key information of a transaction data of one transaction channel is consistent with the key information of a transaction data of other transaction channels, then it is determined that the transaction data of the transaction channel is successfully reconciled, otherwise, it is determined that the transaction data of the transaction channel is abnormal; The transaction data reconciliation result verification module is used to perform anomaly verification according to preset transaction business rules for each transaction data of each transaction channel judged to be abnormal; the preset transaction business rules include: coupon usage rules, transaction product and service equivalence rules and transaction user and supplier account abnormality rules; the anomaly verification according to the preset transaction business rules includes: for each transaction data of each abnormal transaction channel, according to the key information, search for a transaction data of a transaction channel with the closest key information from each transaction data of the other abnormal transaction channels; determine whether the inconsistent key information between each transaction data of each abnormal transaction channel and the transaction data of a transaction channel with the closest key information can be explained according to the preset transaction business rules; if it can be explained, then re-determine that the reconciliation of the transaction data of the transaction channel is successful; otherwise, generate an abnormal transaction data mark.

8. A computer-readable storage medium, characterized in that: The computer-readable storage medium includes a stored computer program, wherein when the computer program is executed, the device where the computer-readable storage medium is located is controlled to execute the method according to any one of claims 1 to 6.

9. A computer device, characterized in that: The computer device comprises a memory, a processor and a program stored and executable on the memory, and the program implements the steps of the method according to any one of claims 1 to 6 when executed by the processor.

Images