Transaction verification method and device, electronic device, and storage medium

Abstract

The application discloses a transaction verification method and device, an electronic device and a storage medium. The method comprises the following steps: acquiring verification information of a to-be-verified transaction; wherein the to-be-verified transaction refers to a transaction with an unknown transaction state; the verification information at least comprises a source transaction code of the to-be-verified transaction; determining target transaction information matched with the source transaction code of the to-be-verified transaction from each preset transaction information; wherein the target transaction information at least comprises a transaction message of the to-be-verified transaction and a link configuration; packaging the transaction message to obtain a packaged message; calling a target system by using the packaged message to verify the to-be-verified transaction, and obtaining a verification result of the to-be-verified transaction; wherein the target system refers to a system corresponding to the link configuration. Therefore, a corresponding verification program is no longer developed for each transaction, but the verification of the transaction abnormal condition is realized according to the preset transaction information, so that the development workload is effectively reduced.

Description

Technical Field

[0001] This application relates to the field of transaction processing technology, and in particular to a method and apparatus for verifying transactions, an electronic device, and a storage medium. Background Technology

[0002] In the architecture of a banking system, the business functions of peripheral systems need to call the financial transactions of the core system to complete the business functions. However, during the process of calling financial transactions to complete the business functions, there may be abnormal situations in which the peripheral systems call financial transactions. Therefore, abnormal situations can be investigated by checking the transactions.

[0003] In existing transaction verification technologies, corresponding verification procedures are developed for different types of transactions to be verified, i.e., a complete verification program is developed. When a transaction call exception occurs, the corresponding verification program is invoked to send a verification request to the system based on the type of transaction to be verified, thereby realizing the verification of the transaction call exception.

[0004] However, each type of transaction requires the development of a corresponding verification program to verify abnormal situations, which is obviously too cumbersome and also greatly increases the development workload. Summary of the Invention

[0005] In view of the shortcomings of the prior art, this application provides a method, apparatus, electronic device and storage medium for verifying transactions, so as to solve the problem that the prior art requires the development of a corresponding verification program according to the type of transaction to be verified each time a transaction needs to be verified, which is obviously too cumbersome.

[0006] To achieve the above objectives, this application provides the following technical solution:

[0007] The first aspect of this application provides a method for verifying a transaction, including:

[0008] Obtain verification information for the transaction to be verified; wherein, the transaction to be verified refers to a transaction whose transaction status is unknown; the verification information includes at least the source transaction code of the transaction to be verified;

[0009] The target transaction information that matches the source transaction code of the transaction to be verified is determined from a set of preset transaction information; wherein the target transaction information includes at least the transaction message and link configuration of the transaction to be verified.

[0010] The transaction messages are assembled into packets to obtain assembled packets;

[0011] The target system is invoked using the packet to verify the transaction to be verified, and the verification result of the transaction to be verified is obtained; wherein, the target system refers to the system corresponding to the link configuration.

[0012] Optionally, in the above-described transaction verification method, before assembling the transaction message into a packet to obtain the assembled message, the method further includes:

[0013] Determine whether the target transaction information contains preprocessing rules;

[0014] If the target transaction information contains the preprocessing rules, then the transaction message is processed using the preprocessing rules to obtain a processed message;

[0015] The step of assembling the transaction message into an assembled message includes:

[0016] The processed messages are reassembled to obtain reassembled messages.

[0017] Optionally, in the above-described transaction verification method, the step of using the packet-based message to invoke the target system to verify the transaction to be verified and obtaining the verification result of the transaction to be verified includes:

[0018] The target system is invoked using the packet to verify the transaction to be verified, and a verification message is obtained.

[0019] The verification message is parsed to obtain the verification result of the transaction to be verified.

[0020] Optionally, in the above-described transaction verification method, after using the packet to call the target system to verify the transaction to be verified and obtaining the verification result of the transaction to be verified, the method further includes:

[0021] Determine whether the target transaction information contains post-processing rules;

[0022] If the target transaction information has the post-processing rule, then the verification result is processed using the post-processing rule to obtain the processed verification result corresponding to the verification result.

[0023] Optionally, in the above-described method for verifying a transaction, before obtaining the verification information of the transaction to be verified, the method further includes:

[0024] The processing time of each transaction in the financial statements is monitored in real time.

[0025] If the processing time of any of the transactions is found to be longer than the preset processing time, and the transaction status of the transaction in the financial statement is unknown, then the transaction will be identified as a transaction pending verification.

[0026] The acquisition of verification information for the transaction to be verified includes:

[0027] Obtain the verification information for the transaction to be verified from the financial statements.

[0028] Optionally, the above-mentioned methods for verifying transactions may also include:

[0029] The verification results of the transactions to be verified are updated in the financial statements; wherein the verification results of the transactions to be verified include at least the actual transaction status of the transactions to be verified.

[0030] Optionally, in the above-described method for verifying a transaction, after obtaining the verification result of the transaction to be verified, the method further includes:

[0031] Feedback is provided based on the verification results of the transaction to be verified, matched with preset abnormal information.

[0032] A second aspect of this application provides a transaction verification device, comprising:

[0033] An acquisition unit is used to acquire verification information of a transaction to be verified; wherein, the transaction to be verified refers to a transaction whose transaction status is unknown; the verification information includes at least the source transaction code of the transaction to be verified;

[0034] A matching unit is used to determine target transaction information that matches the source transaction code of the transaction to be verified from a set of preset transaction information; wherein, the target transaction information includes at least the transaction message of the verification transaction and the link configuration;

[0035] A packet assembly unit is used to assemble the transaction messages into packetized messages.

[0036] The first verification unit is used to invoke the target system using the packet to verify the transaction to be verified, and obtain the verification result of the transaction to be verified; wherein, the target system refers to the system corresponding to the link configuration.

[0037] Optionally, the aforementioned transaction verification device further includes:

[0038] The first judgment unit is used to determine whether the target transaction information has preprocessing rules;

[0039] The first processing unit is configured to process the transaction message using the preprocessing rule if the target transaction information contains the preprocessing rule, and obtain a processed message.

[0040] The step of assembling the transaction message into an assembled message includes:

[0041] The processed messages are reassembled to obtain reassembled messages.

[0042] Optionally, in the above-mentioned transaction verification device, the first verification unit includes:

[0043] The second verification unit is used to call the target system using the packet message to verify the transaction to be verified, and obtain a verification message.

[0044] The parsing unit is used to parse the verification message to obtain the verification result of the transaction to be verified.

[0045] Optionally, the aforementioned transaction verification device further includes:

[0046] The second judgment unit is used to determine whether the target transaction information has post-processing rules;

[0047] The second processing unit is used to process the verification result using the post-processing rule if the target transaction information has the post-processing rule, so as to obtain the processed verification result corresponding to the verification result.

[0048] Optionally, the aforementioned transaction verification device further includes:

[0049] The monitoring unit is used to monitor the processing time of each transaction in the financial statements in real time.

[0050] The determining unit is used to determine the transaction as a transaction to be verified if the transaction status in the financial table is unknown when the processing time of any of the transactions is detected to be greater than a preset processing time.

[0051] The acquisition of verification information for the transaction to be verified includes:

[0052] Obtain the verification information for the transaction to be verified from the financial statements.

[0053] Optionally, the aforementioned transaction verification device further includes:

[0054] An update unit is used to update the verification results of the transaction to be verified to the financial statements; wherein the verification results of the transaction to be verified include at least the actual transaction status of the transaction to be verified.

[0055] Optionally, the aforementioned transaction verification device further includes:

[0056] The feedback unit is used to provide feedback based on the verification results of the transaction to be verified, matching preset abnormal information.

[0057] A third aspect of this application provides a computer storage medium, comprising:

[0058] Memory and processor;

[0059] The memory is used to store programs;

[0060] The processor is used to execute the program, which, when executed, is specifically used to implement the transaction verification method as described in any of the above.

[0061] The fourth aspect of this application provides an electronic device for storing a computer program, which, when executed, implements the transaction verification method as described in any of the preceding claims.

[0062] This application provides a transaction verification method that pre-configures transaction information for each transaction to verify abnormal transaction conditions. The method involves acquiring verification information for the transaction to be verified (i.e., transactions with unknown status), including at least the source transaction code. Then, it identifies target transaction information matching the source transaction code from the pre-configured transaction information. This target transaction information includes at least the transaction message and link configuration of the transaction to be verified. The transaction message is then assembled into a packet, and finally, the packet is used to call the target system to verify the transaction, yielding the verification result. The target system refers to the system corresponding to the link configuration. This eliminates the need to develop a separate verification program for each transaction; instead, it uses pre-configured transaction information to verify abnormal transaction conditions, effectively reducing development workload. Attached Figure Description

[0063] To more clearly illustrate the technical solutions in the embodiments of this application 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 embodiments of this application. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.

[0064] Figure 1 A flowchart illustrating a transaction verification method provided in this application embodiment;

[0065] Figure 2 A flowchart illustrating a method for obtaining verification results provided in this application embodiment;

[0066] Figure 3 A flowchart illustrating another transaction verification method provided in this application embodiment;

[0067] Figure 4 A schematic diagram of a transaction verification device provided in another embodiment of this application;

[0068] Figure 5 This is a schematic diagram of the structure of an electronic device provided in another embodiment of this application. Detailed Implementation

[0069] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0070] In this application, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0071] This application provides a method for verifying transactions, such as... Figure 1 As shown, the specific steps include:

[0072] S101. Obtain verification information for the transaction to be verified.

[0073] Among them, transactions pending verification refer to transactions whose transaction status is unknown, and the verification information includes at least the source transaction code of the transaction pending verification.

[0074] It should be noted that the verification information of the transaction to be verified is used to find the target transaction information that matches the verification information from various preset transaction information, i.e., step S102.

[0075] Optionally, under normal transaction conditions, after a transaction is invoked for processing, the transaction result will be obtained within a certain transaction time. Therefore, under normal transaction conditions, the transaction status is known within a certain transaction time. If the transaction status is still unknown after a certain transaction time, it indicates that the transaction is abnormal, and verification is required. Therefore, in another embodiment of this application, before executing step S101, the following may be further included:

[0076] The processing time of each transaction in the financial statements is monitored in real time. If the processing time of any transaction is found to be longer than the preset processing time, and the transaction status in the financial statements is unknown, then the transaction is identified as a transaction pending investigation.

[0077] Optionally, each transaction can be treated as a task, and the information of the corresponding task for each transaction can be recorded in a task table. The information in the task table can include the transaction's execution time, task name, and task status, allowing for real-time monitoring of transactions based on this information. It should be noted that the task status in the task table is the same as the transaction status.

[0078] Optionally, monitoring the processing time of transactions in the financial statements first, and then determining the transaction status, is only one possible monitoring method. Of course, it is also possible to monitor the processing time and transaction status of each transaction in the financial statements simultaneously.

[0079] It should be noted that in this application, each transaction is recorded in the financial table. For ease of management, the verification information of each transaction can also be recorded in the financial table. Therefore, in this embodiment, the specific implementation of step S101 is as follows:

[0080] Obtain verification information for the transactions to be investigated from the financial statements.

[0081] S102. Determine the target transaction information that matches the source transaction code of the transaction to be verified from the preset transaction information.

[0082] The target transaction information includes at least the transaction message for verifying the transaction and the link configuration.

[0083] It should be noted that, in this embodiment, a corresponding verification program is not developed for each transaction. Instead, transaction information corresponding to the transaction is pre-configured based on the verification information, so that when a transaction needs to be verified, the transaction information of that transaction can be used for verification. The transaction information includes at least the transaction message for the verification transaction and the link configuration. The transaction message can be used to call a third-party system to verify the transaction to be verified, and the link configuration is used to instruct the corresponding third-party system.

[0084] It should also be noted that a transaction information can also include the source transaction code and the verification transaction code of the transaction to be verified. Therefore, the verification transaction code that matches the source transaction code of the transaction to be verified can be found, thereby finding the target transaction information that matches the verification information of the transaction to be verified.

[0085] Optionally, the pre-configured transaction information can be stored in the form of a transaction configuration table, where each record in the transaction configuration table refers to a specific transaction.

[0086] S103. Assemble the transaction messages into a packet to obtain the assembled message.

[0087] It should be noted that the transaction message needs to be sent to the third-party system, but before sending the transaction message to the third-party system, the transaction message needs to be packaged first. Therefore, in this embodiment of the application, step S103 is executed first, and then step S104 is executed.

[0088] S104. Use the packet assembly message to call the target system to verify the transaction to be verified and obtain the verification result of the transaction to be verified.

[0089] Here, the target system refers to the system corresponding to the link configuration.

[0090] Specifically, the packet is sent to the target system indicated by the link configuration, triggering the target system to verify the transaction to be verified, and then returning the verification result of the transaction to be verified, thereby obtaining the verification result of the transaction to be verified.

[0091] Optionally, in another embodiment of this application, one specific implementation of step S104 is as follows: Figure 2 As shown, it includes:

[0092] S201. Use the packet assembly message to call the target system to verify the transaction to be verified and obtain the verification message.

[0093] Optionally, a verification request can be sent to the target system in the form of a packet. The target system will also provide feedback on the verification results in the form of a packet. Therefore, the packet needs to be parsed to obtain the corresponding verification results, i.e., step S202 is executed.

[0094] S202. Parse the verification message to obtain the verification results of the transaction to be verified.

[0095] Optionally, since the verification result of the transaction to be verified returned by the target system is in the form of a message, in order to obtain the verification result, it is necessary to parse the message in order to successfully obtain the transaction result of the transaction to be verified.

[0096] Optionally, when step S101 is specifically implemented as obtaining verification information of the transaction to be verified from the financial statements, the verification information of the transaction to be verified is recorded in the financial statements. Therefore, in this embodiment, after executing step S104, it may further include:

[0097] Update the financial statements with the verification results of the transactions pending verification.

[0098] The verification results for a transaction pending verification include at least its actual transaction status. The actual transaction status is set to "successful" if the transaction is successfully processed, and "failed" if it is not successfully processed. If the actual transaction status of a transaction pending verification is still unknown, the transaction will be verified again until its status is shown as either "successful" or "failed" in the financial statements.

[0099] Of course, the verification results may also include other information, such as processing time, transaction type, and the system that called the verification.

[0100] This application provides a transaction verification method that pre-configures transaction information for each transaction to verify abnormal transaction conditions. The method involves acquiring verification information for the transaction to be verified (i.e., transactions with unknown status), including at least the source transaction code. Then, it identifies target transaction information matching the source transaction code from the pre-configured transaction information. This target transaction information includes at least the transaction message and link configuration of the transaction to be verified. The transaction message is then assembled into a packet, and finally, the packet is used to call the target system to verify the transaction, yielding the verification result. The target system refers to the system corresponding to the link configuration. This eliminates the need to develop a separate verification program for each transaction; instead, it uses pre-configured transaction information to verify abnormal transaction conditions, effectively reducing development workload.

[0101] Another embodiment of this application provides another method for processing online files, such as... Figure 3 As shown, it includes:

[0102] S301. Obtain verification information for the transaction to be verified.

[0103] Among them, transactions pending verification refer to transactions whose status is unknown, and the verification information may include the source transaction code of the transaction pending verification.

[0104] It should be noted that the specific implementation of step S301 can be referred to step S101 in the above method embodiment, and will not be repeated here.

[0105] S302. Determine the target transaction information that matches the source transaction code of the transaction to be verified from the preset transaction information.

[0106] The target transaction information may include the transaction message for verifying the transaction and the link configuration.

[0107] It should be noted that the specific implementation of step S302 can be referred to step S102 in the above method embodiment, and will not be repeated here.

[0108] S303. Determine whether the target transaction information has preprocessing rules.

[0109] It should be noted that the pre-configured transaction message in step S302 may not meet the requirements for sending the transaction message to the third-party system, and further processing of the transaction message is required. Therefore, the pre-processing rules for the transaction message are pre-configured in the target transaction information. After the target transaction information is matched, it is determined whether the target transaction information has pre-processing rules. If the target transaction information has pre-processing rules, it means that the transaction message needs to be processed, and the transaction message is processed using the pre-processing rules, i.e., step S304. If the target transaction information does not have pre-processing rules, it means that the transaction message meets the requirements for sending it to the third-party system, and step S306 is executed.

[0110] S304. Process the transaction message using the preprocessing rules to obtain the processed message.

[0111] S305. Reassemble the processed messages to obtain the reassembled messages.

[0112] It should be noted that the specific implementation of step S305 can be referred to step S103 in the above method embodiment, and will not be repeated here.

[0113] S306. Assemble the transaction messages into a packet to obtain the assembled message.

[0114] It should be noted that the specific implementation of step S306 can be referred to step S103 in the above method embodiment, and will not be repeated here.

[0115] S307. Use the packet assembly message to call the target system to verify the transaction to be verified and obtain the verification result of the transaction to be verified.

[0116] It should be noted that the specific implementation of step S307 can be referred to step S104 in the above method embodiment, and will not be repeated here.

[0117] Here, the target system refers to the system corresponding to the link configuration.

[0118] S308, Post-processing rules for determining whether target transaction information exists.

[0119] It should be noted that the verification result of the transaction to be verified obtained in step S307 may not be the final verification result desired by the relevant maintenance contact person. Therefore, after obtaining the verification result, it is necessary to process the verification result using the corresponding processing rules. In this embodiment, the post-processing rules are pre-configured in the transaction information. Of course, post-processing rules can also be configured separately, without storing the post-processing rules in the transaction information. Therefore, if the target transaction information has post-processing rules, it means that the verification result needs to be processed, and the verification result is processed using the post-processing rules, i.e., step S309. If the target transaction information does not have post-processing rules, it means that the verification result does not need to be processed, and step S310 is executed.

[0120] S309. Process the verification results using post-processing rules to obtain the processed verification results corresponding to the verification results.

[0121] S310. Match the pre-set abnormal information with the verification results of the transaction to be verified and provide feedback.

[0122] The abnormal information includes at least the abnormal type, the abnormal handling level, and the abnormal notification method.

[0123] Optionally, the pre-configured exception information can be stored in the form of an exception alert configuration table, where each record in the exception alert configuration table refers to each exception information.

[0124] Optionally, if the verification result of the transaction to be verified fails to match the preset abnormal information, the verification result will be directly reported to the relevant operation and maintenance contact person.

[0125] If the verification result of the transaction to be verified is successfully matched with the preset abnormal information, the abnormality handling level is determined according to the abnormality type matched by the verification result, and the verification result is fed back to the relevant operation and maintenance contact person in the notification method of the abnormality handling level.

[0126] Another embodiment of this application provides a transaction verification device, such as... Figure 4 As shown, it includes:

[0127] The acquisition unit 401 is used to acquire the verification information of the transaction to be verified.

[0128] Among them, transactions pending verification refer to transactions whose transaction status is unknown, and the verification information includes at least the source transaction code of the transaction pending verification.

[0129] The matching unit 402 is used to determine the target transaction information that matches the source transaction code of the transaction to be verified from the preset transaction information.

[0130] The target transaction information includes at least the transaction message for verifying the transaction and the link configuration.

[0131] Packet assembly unit 403 is used to assemble transaction messages into packetized messages.

[0132] The first verification unit 404 is used to call the target system using the packet assembly message to verify the transaction to be verified and obtain the verification result of the transaction to be verified.

[0133] Here, the target system refers to the system corresponding to the link configuration.

[0134] It should be noted that the specific working process of the above-mentioned units in the embodiments of this application can be referred to steps S101 to S104 in the above method embodiments, and will not be repeated here.

[0135] Optionally, in another embodiment of this application, the following units are also included:

[0136] The first judgment unit is used to determine whether the target transaction information has preprocessing rules.

[0137] The first processing unit is used to process the transaction message using the preprocessing rules if there are preprocessing rules for the target transaction information, and obtain the processed message.

[0138] This involves assembling transaction messages into packets to obtain assembled packets, including:

[0139] The processed messages are reassembled into a single packet to obtain the reassembled message.

[0140] It should be noted that the specific working process of each unit provided in the above embodiments of this application can be referred to the corresponding steps in the above method embodiments, and will not be repeated here.

[0141] Optionally, in another embodiment of this application, the first verification unit 404 includes:

[0142] The second verification unit is used to call the target system using the packet assembly message to verify the transaction to be verified and obtain the verification message.

[0143] The parsing unit is used to parse the verification message to obtain the verification result of the transaction to be verified.

[0144] It should be noted that the specific working process of each unit provided in the above embodiments of this application can be referred to the corresponding steps in the above method embodiments, and will not be repeated here.

[0145] Optionally, in another embodiment of this application, the following units are also included:

[0146] The second judgment unit is used to determine whether the target transaction information has post-processing rules.

[0147] The second processing unit is used to process the verification results using the post-processing rules if there are post-processing rules for the target transaction information, so as to obtain the processed verification results corresponding to the verification results.

[0148] It should be noted that the specific working process of each unit provided in the above embodiments of this application can be referred to the corresponding steps in the above method embodiments, and will not be repeated here.

[0149] Optionally, in another embodiment of this application, the following units are also included:

[0150] The monitoring unit is used to monitor the processing time of each transaction in the financial statements in real time.

[0151] The determination unit is used to determine a transaction as a transaction to be investigated if the processing time of any transaction is greater than the preset processing time and the transaction status in the financial statement is unknown.

[0152] This includes obtaining verification information for the transaction to be verified, including:

[0153] Obtain verification information for the transactions to be investigated from the financial statements.

[0154] It should be noted that the specific working process of each unit provided in the above embodiments of this application can be referred to the corresponding steps in the above method embodiments, and will not be repeated here.

[0155] Optionally, in another embodiment of this application, the following units are also included:

[0156] The update unit is used to update the financial statements with the verification results of the transactions to be verified.

[0157] The verification results of the transactions to be verified shall include at least the actual transaction status of the transactions to be verified.

[0158] It should be noted that the specific working process of each unit provided in the above embodiments of this application can be referred to the corresponding steps in the above method embodiments, and will not be repeated here.

[0159] Optionally, in another embodiment of this application, the following units are also included:

[0160] The feedback unit is used to provide feedback based on the verification results of the transaction to be verified, matching preset abnormal information.

[0161] It should be noted that the specific working process of each unit provided in the above embodiments of this application can be referred to the corresponding steps in the above method embodiments, and will not be repeated here.

[0162] Another embodiment of this application provides an electronic device, such as... Figure 5 As shown, it includes:

[0163] Memory 501 and processor 502.

[0164] The memory 501 is used to store the program.

[0165] The processor 502 is used to execute a program, which, when executed, is specifically used to implement the transaction verification method provided in any of the above embodiments.

[0166] Another embodiment of this application provides a computer storage medium for storing a computer program, which, when executed, implements the transaction verification method provided in any of the above embodiments.

[0167] Computer storage media, including both permanent and non-permanent, removable and non-removable media, can store information using any method or technology. Information can be computer-readable instructions, data structures, program modules, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0168] Those skilled in the art will further recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0169] The above description of the disclosed embodiments enables those skilled in the art to make or use this application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method of verifying a transaction, characterized by, The method comprises the following steps: respectively monitoring the processing time of each transaction in a financial statement in real time; when the processing time of any one of the transactions is greater than a preset processing time, if the transaction state of the transaction in the financial statement is unknown, determining the transaction as a transaction to be verified; obtaining verification information of the transaction to be verified; wherein the verification information at least includes a source transaction code of the transaction to be verified; determining target transaction information matching the source transaction code of the transaction to be verified from preset transaction information; wherein the target transaction information at least includes transaction message of the transaction to be verified and link configuration; packaging the transaction message to obtain packaged message; calling a target system to verify the transaction to be verified by using the packaged message, and obtaining verification result of the transaction to be verified; wherein the target system refers to a system corresponding to the link configuration.

2. The method of claim 1, wherein, Before the step of packaging the transaction message to obtain packaged message, the method further comprises the following steps: determining whether the target transaction information exists pre-processing rule; if the target transaction information exists the pre-processing rule, processing the transaction message by using the pre-processing rule to obtain processed message; wherein the step of packaging the transaction message to obtain packaged message comprises the following step: packaging the processed message to obtain packaged message.

3. The method of claim 1, wherein, The step of calling a target system to verify the transaction to be verified by using the packaged message, and obtaining verification result of the transaction to be verified, comprises the following steps: calling the target system to verify the transaction to be verified by using the packaged message, and obtaining verification message; analyzing the verification message to obtain the verification result of the transaction to be verified.

4. The method of claim 1, wherein, After the step of calling a target system to verify the transaction to be verified by using the packaged message, and obtaining verification result of the transaction to be verified, the method further comprises the following steps: determining whether the target transaction information exists post-processing rule; if the target transaction information exists the post-processing rule, processing the verification result by using the post-processing rule to obtain processed verification result corresponding to the verification result.

5. The method of claim 1, wherein, The step of obtaining verification information of the transaction to be verified comprises the following step: obtaining the verification information of the transaction to be verified from the financial statement.

6. The method of claim 5, wherein, The method further comprises the following steps: updating the verification result of the transaction to be verified to the financial statement; wherein the verification result of the transaction to be verified at least includes actual transaction state of the transaction to be verified.

7. The method of claim 1, wherein, After the step of obtaining the verification result of the transaction to be verified, the method further comprises the following step: matching preset abnormal information according to the verification result of the transaction to be verified to perform feedback.

8. An apparatus for verifying a transaction, characterized by The method comprises the following steps: a monitoring unit, configured to monitor the processing time of each transaction in a financial statement in real time; a determining unit, configured to, when the processing time of any one of the transactions is greater than a preset processing time, if the transaction state of the transaction in the financial statement is unknown, determine the transaction as a transaction to be verified; an obtaining unit, configured to obtain verification information of the transaction to be verified; wherein the verification information at least includes a source transaction code of the transaction to be verified; A matching unit is configured to determine target transaction information matching a source transaction code of the to-be-verified transaction from preset respective transaction information, wherein the target transaction information at least includes a transaction message of a verification transaction and a link configuration. A packet assembling unit is configured to assemble the transaction message to obtain an assembled message. A first verification unit is configured to call a target system to verify the to-be-verified transaction by using the assembled message, and obtain a verification result of the to-be-verified transaction, wherein the target system refers to a system corresponding to the link configuration.

9. An electronic device, comprising: Comprise: A memory and a processor; The memory is configured to store a program; The processor is configured to execute the program, and the program is configured to implement the transaction verification method in any one of claims 1 to 7 when executed.

10. A computer storage medium, characterized in that, A computer program is stored, and the computer program is configured to implement the transaction verification method in any one of claims 1 to 7 when executed.

Images