Automated testing method and apparatus for payment system reconciliation

Abstract

The application provides a payment system reconciliation automatic test method and device, relates to the technical field of reconciliation test, and comprises the following steps: automatically performing reconciliation participant range checking according to a reconciliation issuing rule, and determining whether there is a reconciliation range error; automatically performing reconciliation message self logic checking according to a message exchange standard and internal business logic, and determining whether there is a message logic error; extracting reconciliation items from the reconciliation message of each participant, automatically comparing the reconciliation items with business data of the corresponding participant in a payment system database, and determining whether there is a reconciliation detail error. The application solves the problems of high test difficulty, low coverage, time-consuming and laborious, and easy human errors in the payment system reconciliation function test, can quickly perform all-round and automatic checking on a large amount of reconciliation messages, can greatly reduce the test cost, improve the test efficiency, and output reliable test results.

Description

Technical Field

[0001] This invention relates to the field of reconciliation testing technology, and in particular to an automated reconciliation testing method and apparatus for payment systems. Background Technology

[0002] With economic and social development, the demand for payment and settlement is increasing. The central bank has established multiple payment systems, such as the Large-Value Payment System, the Small-Value Payment System, the Online Payment Interbank Clearing System, the Domestic and Foreign Currency Payment System, and the Cross-Border Payment System. Participants (generally banks or non-bank financial institutions) use these payment systems to achieve fund clearing and information exchange.

[0003] Reconciliation is a cornerstone of payment systems, ensuring data consistency among all participants and system reliability. Each payment system has its own reconciliation cycle, commonly based on calendar days or business days. Taking daily reconciliation as an example, the reconciliation process between the payment system and participants is briefly described below:

[0004] 1. Summary and Reconciliation. At the end of the day, the payment system sends a summary and reconciliation message to all participants. The message includes the overall situation of each participant's transactions for the day (total number of transactions, total amount, number of reconciliation entries) and the number of transactions and amount for each type of transaction. If all transactions of a participant are consistent, the reconciliation is complete.

[0005] 2. Detailed Verification. After receiving the summary verification message, if there is a discrepancy in the verification of a certain type of business, the participant can apply to the payment system for detailed verification of that type of business. The payment system will issue a detailed verification response message to the participant, which contains a list of messages for that type of business.

[0006] 3. In addition, participants can apply to download the details and download the complete original message of a specific transaction.

[0007] Traditionally, reconciliation function testing has relied on manual testing by testers. This mainly involves selecting a few typical reconciliation messages, manually checking the correctness of the message structure, and then manually verifying each reconciliation item in the message.

[0008] However, manual verification has the following drawbacks:

[0009] First, manual verification places high demands on testers, heavily relying on their business knowledge and technical experience. For example, misunderstandings between testers and developers regarding business aspects can easily lead to errors in the same area; technically, those unable to handle complex SQL queries are unlikely to be promoted. This also makes it difficult to distribute the workload simply by increasing the number of personnel.

[0010] Secondly, it is prone to human error. Due to the characteristics of human visual illusions and abstract illusions, it is difficult to accurately check all the details of a large amount of text content.

[0011] Secondly, manual verification is extremely labor-intensive. For example, summarizing and verifying messages requires counting the number and amount of each original business transaction initiated and received for each reconciliation entry. This necessitates writing and executing numerous complex SQL queries, which is very time-consuming. Some verification methods are so complex that they are practically impossible to implement manually. For instance, manually verifying large messages requires concatenating all signature values ​​or attributes to extract signature elements. If verification fails, it's highly likely due to errors in the manually concatenated signature elements, making it difficult to make a valid judgment. Therefore, smaller messages are often the only option for verification.

[0012] Finally, due to the aforementioned characteristics of manual verification, in practice, it can lead to insufficient test coverage and easily result in missed risks. Summary of the Invention

[0013] In view of this, the present invention provides an automated testing method and apparatus for payment system reconciliation to solve at least one of the aforementioned problems.

[0014] To achieve the above objectives, the present invention adopts the following solution:

[0015] According to a first aspect of the present invention, an automated testing method for reconciliation in a payment system is provided. The method includes: automatically checking the scope of reconciliation participants according to reconciliation distribution rules to determine whether there are any errors in the reconciliation scope; automatically checking the logic of the reconciliation messages themselves according to message exchange standards and internal business logic to determine whether there are any errors in message logic; extracting reconciliation entries from the reconciliation messages of each participant, and automatically comparing the reconciliation entries with the corresponding participant's business data in the payment system database to determine whether there are any errors in the reconciliation details.

[0016] Preferably, in the above method of this embodiment, automatically checking the scope of reconciliation participants according to the reconciliation distribution rules includes: obtaining the set S of participants specified for the reconciliation date according to the reconciliation distribution rules. E Read the objects sent by the payment system to summarize and verify messages to obtain the set of actual participants S. A The difference set S is obtained through set operations. R =S A -S E and difference set S M =S E -S A And determine the difference set S R and S M Check if the set is empty. If any difference set is not empty, then there is a reconciliation range error.

[0017] Preferably, in the above method of this embodiment, automatically performing logical checks on the reconciliation message itself based on the message exchange standard and the inherent business logic includes: establishing a logical check rule base based on the message exchange standard and the inherent business logic; and performing format checks, and / or total-total consistency checks, and / or fragment consistency checks, and / or electronic signature verification on the reconciliation message according to the rules in the logical check rule base.

[0018] Preferably, in this embodiment, the method described above, which involves extracting reconciliation entries from each participant's reconciliation message and automatically performing an error comparison between the reconciliation entries and the corresponding participant's business data in the payment system database, includes: extracting reconciliation entries from each participant's reconciliation message to obtain a reconciliation entry set T. M The payment system database is used to filter and statistically analyze the business data of the corresponding participants to obtain a set T of reconciliation entries for the accounts payable. S Based on the business logic of the reconciliation entries, feature values ​​are extracted and set operations are performed to obtain the difference set T. L =T S -T M and T R =T M -T S For eigenvalues ​​in the difference set T L and T R The reconciliation entries in the system are directly marked as incorrect.

[0019] Preferably, the method described above in this embodiment further includes: setting the reconciliation entry set T... M and T S Performing an intersection operation yields the intersection T. B =T S ∩T M For eigenvalues ​​in the intersection T B The reconciliation entries in the data were processed one by one from T. M and T S The system reads the corresponding complete reconciliation entry and performs a detailed comparison; it determines whether the number of initiating transactions, the amount of initiating transactions, the number of receiving transactions, and the amount of receiving transactions are completely consistent. If they are completely consistent, the transaction passes; otherwise, it is marked as an incorrect account and the reason for the error is recorded.

[0020] According to a second aspect of the present invention, an automated reconciliation testing apparatus for a payment system is provided. The apparatus includes: a range checking unit, configured to automatically perform a range check on reconciliation participants according to reconciliation distribution rules to determine whether there are any reconciliation range errors; a logic checking unit, configured to automatically perform a logic check on the reconciliation messages themselves according to message exchange standards and internal business logic to determine whether there are any message logic errors; and a detail checking unit, configured to extract reconciliation entries from the reconciliation messages of each participant, and automatically compare the reconciliation entries with the corresponding participant's business data in the payment system database to determine whether there are any reconciliation detail errors.

[0021] Preferably, in this embodiment, the aforementioned range checking unit includes: a participant specification module, used to obtain the specified participant set S for the reconciliation date according to the reconciliation issuance rules. E The actual participant module is used to read the objects sent by the payment system to summarize and verify messages, and obtain the actual participant set S. A The set operations module is used to obtain the difference set S through set operations. R =S A -S E and difference set S M =S E -S A The judgment module is used to determine the difference set S. R and S M Check if the set is empty. If any difference set is not empty, then there is a reconciliation range error.

[0022] Preferably, the above-mentioned logical inspection unit in this embodiment includes: a rule base establishment module, used to establish a logical inspection rule base according to the message exchange standard and the inherent logic of the business; and a logical inspection module, used to perform format inspection, and / or total-total consistency inspection, and / or fragment consistency inspection, and / or electronic signature verification on the reconciliation message according to the rules in the logical inspection rule base.

[0023] Preferably, in this embodiment, the detailed inspection unit includes: a first reconciliation item module, used to extract reconciliation items from the reconciliation messages of each participant to obtain a reconciliation item set T. M The second reconciliation item module is used to filter and statistically analyze the set T of reconciliation items that should be reconciled from the business data of the corresponding participants in the payment system database. S The difference set operation module is used to extract feature values ​​based on the business logic of reconciliation entries and perform set operations to obtain the difference set T. L =T S -T M and T R =T M -T S Error marking module, used for eigenvalues ​​in difference set T L and T R The reconciliation entries in the system are directly marked as incorrect.

[0024] Preferably, in this embodiment, the detailed inspection unit further includes: an intersection operation module, used to perform an intersection operation on the reconciliation item set T. M and T S Performing an intersection operation yields the intersection T. B =T S ∩T M The detail comparison module is used to compare feature values ​​in the intersection T. B The reconciliation entries in the data are retrieved one by one from set T.M and T S The system reads the corresponding complete reconciliation entries for detailed comparison; the judgment module is used to determine whether the number of initiating transactions, the amount of initiating transactions, the number of receiving transactions, and the amount of receiving transactions are completely consistent. If they are completely consistent, the transaction passes; otherwise, the error marking module marks it as an erroneous account and records the reason for the error.

[0025] According to a third aspect of the present invention, an electronic device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of the above-described method.

[0026] According to a fourth aspect of the present invention, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements the steps of the above-described method.

[0027] According to a fifth aspect of the present invention, a computer program product is provided, comprising a computer program / instructions that, when executed by a processor, implement the steps of the above-described method.

[0028] As can be seen from the above technical solutions, the payment system reconciliation automated testing method and device provided in this application solves the problems of high difficulty, low coverage, time-consuming and labor-intensive testing of reconciliation messages, and easy human error in the reconciliation function testing of payment systems. It can quickly perform comprehensive and fully automated checks on a large number of reconciliation messages, greatly reduce testing costs, improve testing efficiency, and output reliable test results. Attached Figure Description

[0029] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort. In the drawings:

[0030] Figure 1 This is a flowchart illustrating an automated reconciliation testing method for a payment system provided in an embodiment of this application;

[0031] Figure 2 This is a flowchart illustrating the reconciliation participant scope check provided in an embodiment of this application;

[0032] Figure 3 This is a flowchart illustrating the process for determining errors in reconciliation details provided in an embodiment of this application;

[0033] Figure 4 This is a flowchart illustrating the process for determining errors in reconciliation details provided in an embodiment of this application;

[0034] Figure 5 This is a schematic diagram of the structure of an automated reconciliation testing device for a payment system provided in an embodiment of this application;

[0035] Figure 6 This is a schematic diagram of the structure of the range checking unit provided in an embodiment of this application;

[0036] Figure 7 This is a schematic diagram of the structure of the logic checking unit provided in the embodiments of this application;

[0037] Figure 8 This is a schematic diagram of the structure of the detail inspection unit provided in the embodiments of this application;

[0038] Figure 9 This is a schematic diagram illustrating the ARTS feedback reconciliation participant scope check results provided in an embodiment of this application;

[0039] Figure 10 This is a schematic diagram of the ARTS inspection process based on the logic of summarizing and verifying the message itself, provided in an embodiment of this application.

[0040] Figure 11 This is a schematic diagram illustrating the result feedback after logical checking of the summary verification message itself, provided in an embodiment of this application.

[0041] Figure 12 This is a schematic diagram illustrating the feedback of the results after comparing the summary verification message reconciliation entries with the business data, as provided in the embodiments of this application.

[0042] Figure 13 This is a flowchart illustrating the logical check of the detail verification response message itself provided in the embodiments of this application;

[0043] Figure 14 This is a schematic block diagram of the system configuration of the electronic device provided in the embodiments of this application. Detailed Implementation

[0044] The acquisition, storage, use, and processing of data in this application all comply with the relevant provisions of national laws and regulations.

[0045] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the embodiments of the present invention will be further described in detail below with reference to the accompanying drawings. Here, the illustrative embodiments of the present invention and their descriptions are used to explain the present invention, but are not intended to limit the present invention.

[0046] The following is a brief introduction to the technical terms used in this application:

[0047] The term "reconciliation" as used in this article specifically refers to the reconciliation between the payment system and the participants, used to ensure consistency between their accounts.

[0048] The term "reconciliation message" refers to the XML text content containing reconciliation data that the payment system sends to participants.

[0049] The term "fragmented message" refers to the process by which a payment system splits the reconciliation data into multiple messages and sends a set of reconciliation messages to a participant when a participant's reconciliation data exceeds a certain threshold within a reconciliation period.

[0050] The term "summary reconciliation" refers to a reconciliation method that uses data statistically analyzed by business type, business status, and session to verify the number and amount of transactions initiated and received for each type of business.

[0051] The term "detailed reconciliation" refers to a reconciliation method where the reconciliation granularity is a specific transaction.

[0052] like Figure 1 The diagram shown is a flowchart illustrating an automated reconciliation testing method for a payment system provided in an embodiment of this application. The method includes:

[0053] Step S101: Automatically check the scope of reconciliation participants according to the reconciliation distribution rules to determine if there are any errors in the reconciliation scope.

[0054] This step is to determine whether there are any incorrect participants when the payment system sends summary reconciliation messages to them. For example, a participant should not participate in the reconciliation, but the payment system sent them a summary reconciliation message, or a participant should participate in the reconciliation, but the payment system did not send them a summary reconciliation message.

[0055] Preferred, such as Figure 2 As shown, in this embodiment, this step can be implemented through the following sub-steps:

[0056] Step S1011: Obtain the set of participants S specified for the reconciliation date according to the reconciliation distribution rules. E .

[0057] The reconciliation distribution rules specify which participants need to receive the summary reconciliation message on the reconciliation date. Therefore, the set of participants S can be obtained from these reconciliation distribution rules. E That is, the set of participants who should participate in the reconciliation.

[0058] Step S1012: Read the objects that send summary verification messages from the payment system to obtain the set of actual participants S. A .

[0059] This step involves reading which participants the tested payment system actually sent summary verification messages to, thereby obtaining the actual participant set S. A .

[0060] Step S1013: Obtain the difference set S through set operations. R =S A -S E and difference set S M =S E -S A And determine the difference set S R and S M Check if the set is empty. If any difference set is not empty, then there is a reconciliation range error.

[0061] The above-mentioned participant set S E and the set of actual participants S A The definition can be used to derive its difference set S R This means that the entity should not participate in the reconciliation, but the actual payment system sends a summary verification message to it, which is the set of participants; similarly, the difference set S M This refers to the set of participants who should have participated in the reconciliation but were not actually sent a summary reconciliation message by the payment system. Therefore, if either of the two difference sets is non-empty, the participants within it are incorrect participants, confirming an error in the reconciliation scope.

[0062] Step S102: Automatically perform a logical check on the reconciliation message itself based on the message exchange standard and the inherent business logic to determine whether there are any message logic errors.

[0063] Logical checks on reconciliation messages refer to checks that can be performed without relying on business data, using only the message text. Examples include format checks, total / total consistency checks, fragment consistency checks, and electronic signature verification.

[0064] Preferably, this step can be achieved by first establishing a logical check rule base based on message exchange standards and the inherent business logic. This rule base records the mapping relationship between rules and corresponding reconciliation messages. In this way, the reconciliation messages can be checked for format, and / or total / total consistency, and / or fragment consistency, and / or electronic signature verification based on the rules in the logical check rule base.

[0065] Step S103: Extract reconciliation entries from each participant's reconciliation message, and automatically compare the reconciliation entries with the corresponding participant's business data in the payment system database to determine whether there are any reconciliation detail errors.

[0066] When a participant's reconciliation data exceeds a certain threshold, the payment system will distribute reconciliation messages in segments. Therefore, on each reconciliation date, each participant will receive a set of reconciliation messages containing one or more messages. For each participant, reconciliation entries can be extracted from the set of messages they receive, and the payment system database can be used to filter and statistically analyze the reconciliation entries corresponding to the participant's business within the corresponding reconciliation period. By comparing the two, it can be determined whether there are any errors in the reconciliation details.

[0067] Preferred, such as Figure 3 As shown, this step may further include the following sub-steps:

[0068] Step S1031: Extract reconciliation entries from each participant's reconciliation message to obtain a reconciliation entry set T. M .

[0069] Step S1032: Extract the set T of reconciliation entries for the corresponding participants from their business data. S .

[0070] Step S1033: Extract feature values ​​based on the business logic of the reconciliation entries and perform set operations to obtain the difference set T. L =T S -T M and T R =T M -T S .

[0071] From the above set of account entries T M and T S As can be seen from the description, the difference set T L This involves summarizing and verifying any missing reconciliation items in the reports, while the difference set T... R This refers to summarizing and verifying redundant reconciliation entries in the report.

[0072] Step S1034: For eigenvalues ​​in the difference set T L and T R The reconciliation entries in the system are directly marked as incorrect.

[0073] Preferred, such as Figure 4 As shown, step S103 above may further include the following sub-steps:

[0074] Step S1035: Set the set T M and T S Performing an intersection operation yields the intersection T. B =T S ∩T M .

[0075] The intersection T here BThis involves summarizing and verifying the reconciliation entries in both the reports and the participants' business databases. The purpose of testing these reconciliation entries is to compare them one by one to check for any erroneous entries and to find the specific reasons for the errors.

[0076] Step S1036: For eigenvalues ​​in intersection T B The reconciliation entries in the data are retrieved one by one from set T. M and T S The corresponding complete reconciliation entries are read and compared in detail.

[0077] Step S1037: Determine whether the number of initiating transactions, the amount of initiating transactions, the number of receiving transactions, and the amount of receiving transactions are completely consistent. If they are completely consistent, pass the error comparison; otherwise, mark it as an erroneous account and record the reason for the error.

[0078] As can be seen from the above technical solution, the automated testing method for payment system reconciliation provided in this application solves the problems of high difficulty, low coverage, time-consuming and labor-intensive testing of reconciliation messages, and easy human error in the reconciliation function testing of payment systems. It can quickly perform comprehensive and fully automated checks on a large number of reconciliation messages, greatly reduce testing costs, improve testing efficiency, and output reliable test results.

[0079] like Figure 5 The diagram shown is a structural schematic of an automated reconciliation testing device for a payment system provided in an embodiment of this application. The device includes a range checking unit 510, a logic checking unit 520, and a detail checking unit 530, wherein the logic checking unit 520 is connected to the range checking unit 510 and the detail checking unit 530, respectively.

[0080] The scope checking unit 510 is used to automatically check the scope of reconciliation participants according to the reconciliation distribution rules to determine whether there are any errors in the reconciliation scope.

[0081] The logic checking unit 520 is used to automatically perform logic checks on the reconciliation message itself based on the message exchange standard and the inherent business logic to determine whether there are any message logic errors.

[0082] The detail checking unit 530 is used to extract reconciliation entries from each participant's reconciliation message, and automatically compare the reconciliation entries with the corresponding participant's business data in the payment system database to determine whether there are any reconciliation detail errors.

[0083] Preferred, such as Figure 6 As shown, the range checking unit 510 may include: a specified participant module 511, an actual participant module 512, a set operation module 513, and a judgment module 514, wherein the set operation module 513 is connected to the specified participant module 511, the actual participant module 512, and the judgment module 514, respectively.

[0084] The participant specification module 511 is used to obtain the specified participant set S for the reconciliation date based on the reconciliation distribution rules. E .

[0085] The actual participant module 512 is used to read the objects sent by the payment system to summarize and verify messages, and obtain the actual participant set S. A .

[0086] Set operation module 513 is used to obtain the difference set S through set operations. R =S A -S E and difference set S M =S E -S A .

[0087] Module 514 is used to determine the difference set S R and S M If any difference set is not empty, and if any difference set has a non-empty set, then it is determined that there is a reconciliation range error.

[0088] Preferred, such as Figure 7 As shown, the above-mentioned logical inspection unit 520 includes: a rule base establishment module 521 and a logical inspection module 522, wherein the rule base establishment module 521 is used to establish a logical inspection rule base according to the message exchange standard and the internal logic of the business; the logical inspection module 522 is used to perform format checks, and / or total-total consistency checks, and / or fragment consistency checks, and / or electronic signature verification on the reconciliation message according to the rules in the logical inspection rule base.

[0089] Preferred, such as Figure 8 As shown, the detailed inspection unit 530 includes: a first reconciliation entry module 531, a second reconciliation entry module 532, a difference operation module 533, and an error marking module 534.

[0090] The first reconciliation entry module 531 is used to extract reconciliation entries from each participant's reconciliation message to obtain a reconciliation entry set T. M .

[0091] The second reconciliation item module 532 is used to filter and statistically analyze the set T of reconciliation items for corresponding participants from the business data of the payment system database. S .

[0092] The difference set operation module 533 is used to extract feature values ​​based on the business logic of reconciliation entries and perform set operations to obtain the difference set T. L =T S -T M and T R =T M -T S ;

[0093] Error marking module 534 is used for the eigenvalues ​​in the difference set T L and T R The reconciliation entries in the system are directly marked as incorrect.

[0094] Preferred, such as Figure 8 As shown, the detail inspection unit 530 may further include: an intersection operation module 535, a detail comparison module 536, and a judgment module 537, wherein:

[0095] Intersection operation module 535 is used to perform intersection operation on the set T M and T S Performing an intersection operation yields the intersection T. B =T S ∩T M .

[0096] Detail comparison module 536 is used for comparing feature values ​​in intersection T B The reconciliation entries in the data are retrieved one by one from set T. M and T S The corresponding complete reconciliation entries are read and compared in detail.

[0097] The judgment module 537 is used to determine whether the number of initiating transactions, the amount of initiating transactions, the number of receiving transactions, and the amount of receiving transactions are completely consistent. If they are completely consistent, the error comparison is passed; otherwise, the error marking module 534 marks it as an erroneous account and records the reason for the error.

[0098] For a detailed description of each of the above units, please refer to the corresponding description in the foregoing method embodiments, which will not be repeated here.

[0099] As can be seen from the above technical solution, the payment system reconciliation automated testing device provided in this application solves the problems of high difficulty, low coverage, time-consuming and labor-intensive testing of reconciliation messages, and easy human error in the reconciliation function testing of payment systems. It can quickly perform comprehensive and fully automated checks on a large number of reconciliation messages, which can greatly reduce testing costs, improve testing efficiency, and output reliable test results.

[0100] The above method and apparatus will be further described below through a specific embodiment:

[0101] Based on the above method, the applicant constructed an Automated Reconciliation Testing System (ARTS). This system can be divided into two functionalities based on the different test objects: summary reconciliation and detailed reconciliation. The summary reconciliation testing function is implemented through steps S101-S103, while the detailed reconciliation testing function is implemented through steps S102-S103. The implementation of these two functions will be described separately below:

[0102] I. Summary and Verification Testing Function

[0103] (1) Conduct a reconciliation participant scope check.

[0104] First, based on the reconciliation date entered by the testers, ARTS reads the database of the payment system under test, obtains its participant information, and calculates which participants should receive the summary verification message on that reconciliation date according to the reconciliation distribution rules, thus obtaining the participant set S. E Then, the summary verification message for that date was actually sent to which participants by the tested payment system, thus obtaining the participant set S. A The difference set S is obtained through set operations. R =S A -S E That is, to obtain the set S of participants who do not have reconciliation obligations but actually sent reconciliation messages to them. R Then, the difference set S is obtained through set operations. M =S E -S A That is, to obtain the set S of participants who did not actually send reconciliation messages to the parties involved in the reconciliation. M If S R or S M If the set is not empty, then there is a reconciliation range error. ARTS provides feedback on the reconciliation participant range check results to testers through the front-end page, such as... Figure 9 As shown.

[0105] (2) Perform a summary and verification of the logical checks of the messages themselves.

[0106] ARTS reads summary reconciliation messages for a specified reconciliation date from the database of the system under test. These messages are grouped by participant, with each group containing one or more fragmented messages. Then, a series of checks are performed on each group of messages based on the logic inherent in the summary reconciliation messages themselves, such as... Figure 10 As shown. In addition, ARTS also verifies the correctness of the electronic signature for each message. Testers can view the inspection results through the ARTS front-end page. When defects are found, ARTS will clearly indicate the error type and cause, such as... Figure 11 As shown.

[0107] (3) Summarize and verify the reconciliation entries in the message and compare them with the business data.

[0108] After each set of summary reconciliation messages has undergone logical checks, ARTS extracts and records the reconciliation entries from this set of messages, thus obtaining the set T of reconciliation entries contained in the summary reconciliation message for a participant and a reconciliation date. M Then, ARTS connects to the original business database, and separately counts the message types, sessions, number of transactions, and amounts initiated and received by the participant on the reconciliation date. It then merges the initiated and received data according to message type and session to obtain the reconciliation item set T from the original business statistics. S The set operation is performed using the message type and session number of each reconciliation entry as feature values, and the difference set T is calculated. L =T S -T M This refers to summarizing and verifying any missing reconciliation items in the reports; difference set T R =T M -T S This refers to summarizing and verifying redundant reconciliation entries in the reports; the intersection T B =T S ∩T M This refers to the reconciliation entries that are present in both the summary and verification messages and the original business statistics results.

[0109] For T L and T R Check the reconciliation entries in the record and end the record. For the characteristic value in T... B The reconciliation entries in the data are then processed one by one from T. M and T S The system reads complete reconciliation entries and compares the number of initiating transactions, initiating amounts, number of receiving transactions, and receiving amounts on both sides to ensure consistency. The check is then complete. Testers can view the check results through the ARTS front-end page. When defects are found, the error type and cause will be clearly indicated, such as... Figure 12 As shown.

[0110] II. Detailed Verification Test Function

[0111] (1) Detailed verification of the logical checks of the response message itself

[0112] Perform a series of checks on a detail verification response message based on the message's own logic, such as... Figure 13 As shown. In addition, the details will be verified to ensure the electronic signature of the response message is correct.

[0113] (2) Comparison of the original business list with the actual business data

[0114] First, the original business list is extracted from the message. Then, ARTS connects to the original business database, verifies the application information in the message according to the details, and organizes SQL queries to obtain the actual business data. From these two sources, the original business initiating and participating organization numbers and message identifiers are extracted as feature values ​​to obtain two sets T. A and T B By calculating the difference set T A -T B Identify the missing business; calculate the difference T B -T A Identify redundant business operations. Then, analyze the eigenvalues ​​at the intersection T. A ∩T B The process involves verifying the consistency of transaction amounts, settlement amounts, third-party fees, and receiving / paying bank receipt flags for each transaction. Testers can view the inspection results through the ARTS front-end page, and when defects are found, the error type and cause will be clearly indicated.

[0115] This invention also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the above-described method.

[0116] This invention also provides a computer program product, including a computer program / instructions, which, when executed by a processor, implement the steps of the above-described method.

[0117] This invention also provides a computer-readable storage medium storing a computer program for performing the above-described methods.

[0118] like Figure 14 As shown, the electronic device 600 may also include: a communication module 110, an input unit 120, an audio processor 130, a display 160, and a power supply 170. It is worth noting that the electronic device 600 does not necessarily need to include these components. Figure 14 All components shown; in addition, the electronic device 600 may also include Figure 14 For components not shown, please refer to existing technologies.

[0119] like Figure 14 As shown, the central processing unit 100, sometimes also referred to as a controller or operating control, may include a microprocessor or other processor device and / or logic device. The central processing unit 100 receives inputs and controls the operation of various components of the electronic device 600.

[0120] The memory 140 may be, for example, one or more of a cache, flash memory, hard drive, removable media, volatile memory, non-volatile memory, or other suitable devices. It may store the aforementioned failure-related information, and also store a program for executing that information. The central processing unit 100 may execute the program stored in the memory 140 to perform information storage or processing, etc.

[0121] Input unit 120 provides input to central processing unit 100. Input unit 120 may be, for example, a keypad or touch input device. Power supply 170 provides power to electronic device 600. Display 160 displays images and text. Display may be, for example, an LCD display, but is not limited thereto.

[0122] The memory 140 can be a solid-state memory, such as a read-only memory (ROM), random access memory (RAM), a SIM card, etc. It can also be a memory that retains information even when power is off, can be selectively erased, and contains more data; examples of this type of memory are sometimes referred to as EPROMs. The memory 140 can also be some other type of device. The memory 140 includes a buffer memory 141 (sometimes referred to as a buffer). The memory 140 may include an application / function storage unit 142 for storing application programs and function programs or processes for executing the operation of the electronic device 600 via the central processing unit 100.

[0123] The memory 140 may also include a data storage unit 143 for storing data, such as contacts, digital data, pictures, sounds, and / or any other data used by the electronic device. The driver storage unit 144 of the memory 140 may include various drivers for the electronic device's communication functions and / or for performing other functions of the electronic device (such as messaging applications, address book applications, etc.).

[0124] The communication module 110 is a transmitter / receiver 110 that transmits and receives signals via antenna 111. The communication module (transmitter / receiver) 110 is coupled to the central processing unit 100 to provide input signals and receive output signals, which can be the same as in a conventional mobile communication terminal.

[0125] Based on different communication technologies, multiple communication modules 110 can be configured in the same electronic device, such as cellular network modules, Bluetooth modules, and / or wireless LAN modules. The communication module (transmitter / receiver) 110 is also coupled to a speaker 131 and a microphone 132 via an audio processor 130 to provide audio output via the speaker 131 and receive audio input from the microphone 132, thereby enabling typical telecommunications functions. The audio processor 130 may include any suitable buffer, decoder, amplifier, etc. Additionally, the audio processor 130 is coupled to a central processing unit 100, enabling on-device recording via the microphone 132 and on-device playback of stored audio via the speaker 131.

[0126] Those skilled in the art will understand that embodiments of the present invention can be provided as methods, systems, or computer program products. Therefore, the present invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0127] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0128] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0129] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0130] Specific embodiments have been used to illustrate the principles and implementation methods of this invention. The descriptions of the embodiments above are only for the purpose of helping to understand the method and core ideas of this invention. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this invention. Therefore, the content of this specification should not be construed as a limitation of this invention.

Claims

1. An automated testing method for payment system reconciliation, characterized in that, The method includes: The system automatically checks the scope of reconciliation participants based on the reconciliation distribution rules to determine if there are any errors in the reconciliation scope. Based on the message exchange standard and the inherent business logic, the system automatically performs a logical check on the reconciliation message itself to determine whether there are any message logic errors. Reconciliation entries are extracted from each participant's reconciliation message, and these entries are automatically compared with the corresponding participant's business data in the payment system database to determine whether there are any reconciliation details errors. The step of extracting reconciliation entries from each participant's reconciliation message and automatically comparing these entries with the corresponding participant's business data in the payment system database to determine if there are any reconciliation detail errors includes: The reconciliation entries are extracted from each participant's reconciliation message to obtain a reconciliation entry set T. M ; Connect to the database of the original business, and separately count the message types, sessions, number of transactions, and amounts initiated and received by each participant on the reconciliation date. Then, merge the initiated and received data according to message type and session to obtain the set T of reconciliation entries from the original business statistics. S ; Set of reconciliation entries T M and T S The message type and session number are used as feature values ​​to perform an intersection operation to obtain the intersection T. B = T S ∩T M ; For eigenvalues ​​in the intersection T B The reconciliation entries in the data were processed one by one from T. S and T M The corresponding complete reconciliation entries are read and compared in detail. Determine if the number of initiated transactions, the amount initiated, the number of received transactions, and the amount received are completely consistent. If they are completely consistent, pass the error comparison; otherwise, mark it as an erroneous account and record the reason for the error. The automatic check of the reconciliation participant scope based on the reconciliation distribution rules includes: Based on the reconciliation distribution rules, the set of participants S specified for the reconciliation date is determined. E ; Read the objects that send summary verification messages from the payment system to obtain the set of actual participants S. A ; The difference set S is obtained through set operations. R =S A -S E and difference set S M =S E -S A And determine the difference set S R and S M Check if the set is empty. If any difference set is not empty, then there is a reconciliation range error.

2. The automated reconciliation testing method for a payment system as described in claim 1, characterized in that, The automatic logical check of the reconciliation message itself based on the message exchange standard and the inherent business logic includes: Establish a logical check rule base based on message exchange standards and the inherent business logic; The reconciliation message is checked for format, and / or total / total consistency, and / or fragment consistency, and / or electronic signature verification according to the rules in the logical check rule base.

3. The automated reconciliation testing method for a payment system as described in claim 1, characterized in that, The step of extracting reconciliation entries from each participant's reconciliation message and automatically performing an error comparison between the reconciliation entries and the corresponding participant's business data in the payment system database also includes: Based on the business logic of the reconciliation entries, feature values ​​are extracted and set operations are performed to obtain the difference set T. L = T S -T M and T R = T M -T S ; For eigenvalues ​​in the difference set T L and T R The reconciliation entries in the system are directly marked as incorrect.

4. An automated testing device for payment system reconciliation, characterized in that, The device includes: The scope check unit is used to automatically check the scope of reconciliation participants according to the reconciliation rules to determine whether there are any reconciliation scope errors. The logic checking unit is used to automatically perform logic checks on the reconciliation messages themselves based on the message exchange standards and the inherent business logic to determine whether there are any message logic errors. The detailed inspection unit is used to extract reconciliation entries from each participant's reconciliation message, and automatically compare the reconciliation entries with the corresponding participant's business data in the payment system database to determine whether there are any reconciliation detail errors. The detailed inspection unit includes: The first reconciliation entry module is used to extract reconciliation entries from each participant's reconciliation message to obtain a reconciliation entry set T. M ; The second reconciliation entry module connects to the database of the original business transactions. It statistically analyzes the message types, sessions, number of transactions, and amounts initiated and received by each participant on the reconciliation date. Then, it merges the initiated and received data according to message type and session to obtain the reconciliation entry set T of the original business statistics. S ; The intersection operation module is used to perform the intersection operation on the set T of reconciliation entries. M and T S The message type and session number are used as feature values ​​to perform an intersection operation to obtain the intersection T. B = T S ∩T M ; The detail comparison module is used to compare feature values ​​in the intersection T. B The reconciliation entries in the data were processed one by one from T. S and T M The corresponding complete reconciliation entries are read and compared in detail. The judgment module is used to determine whether the number of initiating transactions, the amount of initiating transactions, the number of receiving transactions, and the amount of receiving transactions are completely consistent. If they are completely consistent, the error is corrected; otherwise, it is marked as an erroneous account and the reason for the error is recorded. The range checking unit includes: The participant specification module is used to obtain the specified participant set S for the reconciliation date based on the reconciliation distribution rules. E ; The actual participant module is used to read the objects sent by the payment system to summarize and verify messages, and obtain the actual participant set S. A ; The set operations module is used to obtain the difference set S through set operations. R =S A -S E and difference set S M =S E -S A ; The judgment module is used to determine the difference set S. R and S M Check if the set is empty. If any difference set is not empty, then there is a reconciliation range error.

5. The automated payment system reconciliation testing device as described in claim 4, characterized in that, The logic checking unit includes: The rule base establishment module is used to establish a logical inspection rule base based on message exchange standards and the inherent business logic; The logic check module is used to perform format checks, and / or total-total consistency checks, and / or fragment consistency checks, and / or electronic signature verification on reconciliation messages according to the rules in the logic check rule base.

6. The automated reconciliation testing device for a payment system as described in claim 4, characterized in that, The detailed inspection unit also includes: The difference set operation module is used to extract feature values ​​based on the business logic of reconciliation entries and perform set operations to obtain the difference set T. L =T S -T M and T R = T M -T S ; Error marking module, used for eigenvalues ​​in difference set T L and T R The reconciliation entries in the system are directly marked as incorrect.

7. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 3.

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

9. A computer program product comprising a computer program / instructions, characterized in that, When the computer program / instructions are executed by the processor, they implement the steps of the method according to any one of claims 1 to 3.

Images