A method and device for preventing duplicate entry of collection and payment transactions
By strengthening the active prevention and control and monitoring mechanism in the core banking system, we can judge and block the repeated account of collection and payment transactions, and solve the problem of the inability to discover and block the repeated account before the transaction is submitted in the existing technology, effectively reducing duplication Accounting risks improve the security and reliability of the system.
Patent Information
- Application Number
- CN202011642277.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2020-12-31
- Publication Date
- 2024-12-17
- Estimated Expiration
- 2040-12-31
AI Technical Summary
The existing bank core system lacks a positive anti-release design when recording collection and payment transactions, and cannot detect and block duplicate account before the transaction is submitted, resulting in the inability to effectively reduce the risk of duplicate account.
By strengthening active prevention and control in application logic, we can judge whether the sub-transactions of collection and payment transactions are repeated and monitored before submission. If the number of repeated sub-transactions reaches or exceeds the preset threshold, the submission of transactions will be terminated, combining post-event monitoring and Disposal to reduce the risk of repeated accounts.
It realizes discovery and blocking repeated accounts before the transaction is submitted, avoids repeated accounts, improves the security and reliability of the accounting process, and reduces the risk of repeated accounts.
Smart Images
Figure CN112634049B_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the banking field, and in particular to a method and device for preventing duplicate entry of collection and payment transactions. Background Art
[0002] At present, when the bank's core system records payment and collection transactions, in order to prevent duplicate entries, there are usually certain post-event monitoring measures, that is, an alarm is only issued after the duplicate entry has occurred. There is a lack of positive anti-duplicate design in the positive business logic, and it is impossible to detect and block duplicates before the transaction is submitted.
[0003] Application Contents
[0004] In order to solve the above technical problems, the present application provides a method and device for preventing duplicate entries in collection and payment transactions. By strengthening active prevention and control in the application logic and increasing monitoring and disposal during batch entries, the combination of the two effectively blocks and reduces the risk of duplicate entries.
[0005] The embodiments of the present application disclose the following technical solutions:
[0006] In a first aspect, an embodiment of the present application provides a method for preventing duplicate entry of a collection and payment transaction, wherein the transaction includes several sub-transactions, including:
[0007] Determine whether the collection and payment file corresponding to the collection and payment transaction received by the collection and payment system, the details obtained by parsing the file by the collection and payment system, the details received by the collection and payment system, the details submitted by the collection and payment system, or the file submitted by the collection and payment system are repeated;
[0008] If repeated, the transaction is terminated and an alarm is issued;
[0009] Before submitting the transaction, the transaction is monitored, and if it is found that the number of repeated sub-transactions in the transaction is greater than or equal to a first preset threshold, submission of the transaction is terminated.
[0010] Optionally, the repeated details submitted by the payment collection system include the same details being submitted to multiple different sub-transactions, or the same details being submitted to the same sub-transaction multiple times.
[0011] Optionally, the details obtained by the collection and payment system from parsing the file repeatedly include parsing the same detail into multiple different sub-transactions, or the same detail being parsed into the same sub-transaction multiple times.
[0012] Optionally, the method further includes:
[0013] When the file transmission times out, the order of transaction processing contained in the file is disordered, the information reconciliation of the previous transaction contained in the file fails, the detail submission times out, the file submission times out or the communication is abnormal, an alarm is issued.
[0014] Optionally, the method further includes:
[0015] After the agency collection and payment transaction is completed, an execution report of the agency collection and payment transaction is generated.
[0016] In a second aspect, an embodiment of the present application provides a device for preventing duplicate entry of a collection and payment transaction, wherein the transaction includes a plurality of sub-transactions, and the device includes:
[0017] A judgment unit, used to judge whether the collection and payment file corresponding to the collection and payment transaction received by the collection and payment system, the details obtained by parsing the file by the collection and payment system, the details received by the collection and payment system, the details submitted by the collection and payment system, or the file submitted by the collection and payment system are repeated;
[0018] A first alarm unit, used for terminating the transaction and issuing an alarm if the transaction is repeated;
[0019] The transaction termination unit is used to monitor the transaction before submitting the transaction, and terminate the submission of the transaction if it is found that the number of repeated sub-transactions in the transaction is greater than or equal to a first preset threshold.
[0020] Optionally, the repeated details submitted by the payment collection system include the same details being submitted to multiple different sub-transactions, or the same details being submitted to the same sub-transaction multiple times.
[0021] Optionally, the details obtained by the collection and payment system from parsing the file repeatedly include parsing the same detail into multiple different sub-transactions, or the same detail being parsed into the same sub-transaction multiple times.
[0022] Optionally, the device further comprises:
[0023] The second alarm unit is used to issue an alarm when the file transmission times out, the order of transaction processing contained in the file is disordered, the information reconciliation of the previous transaction contained in the file fails, the detail submission times out, the file submission times out, or the communication is abnormal.
[0024] Optionally, the device further comprises:
[0025] The execution report generating unit is used to generate an execution report of the agency collection and payment transaction after completing the agency collection and payment transaction.
[0026] It can be seen from the above technical solution that compared with the prior art, the embodiment of the present application has the following advantages:
[0027] It can be seen from the above technical scheme that the embodiment of the present application provides a method and device for preventing duplicate entry of collection and payment transactions. The transaction contains several sub-transactions, and it can be determined whether the key business steps of the collection and payment transaction are repeated. If repeated, the transaction is terminated and an alarm is issued. That is, the present application designs an internal anti-duplicate mechanism to issue an alarm for the duplication that may occur during the entry process so that it can be handled in a timely manner. In addition, before submitting the transaction, the transaction is monitored. If it is found that the number of repeated sub-transactions is greater than or equal to the first preset threshold, the submission of the transaction is terminated. The monitoring of the transaction before submitting the transaction can achieve pre-blocking, and the corresponding transaction is blocked and terminated before it is entered into the account, avoiding duplicate entries. That is, the present application strengthens active prevention and control in the application logic, and increases monitoring and disposal during batch entry. The combination of the two effectively blocks and reduces the risk of duplicate entries. BRIEF DESCRIPTION OF THE DRAWINGS
[0028] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.
[0029] Figure 1 A flowchart of a method for preventing duplicate entry of collection and payment transactions provided in an embodiment of the present application;
[0030] Figure 2 A schematic diagram of setting different states for details in different steps provided in an embodiment of the present application;
[0031] Figure 3 A specific overall processing flow of a collection and payment transaction provided in an embodiment of the present application;
[0032] Figure 4 A schematic diagram of a process for monitoring a collection and payment transaction provided in an embodiment of the present application;
[0033] Figure 5 A schematic diagram of a device for preventing duplicate entries in collection and payment transactions provided in an embodiment of the present application. DETAILED DESCRIPTION
[0034] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.
[0035] At present, when the bank's core system records payment and collection transactions, in order to prevent duplicate entries, there are usually certain post-event monitoring measures, that is, an alarm is only issued after the duplicate entry has occurred. There is a lack of positive anti-duplicate design in the positive business logic, and it is impossible to detect and block duplicates before the transaction is submitted.
[0036] In order to solve the above technical problems, the embodiment of the present application provides a method and device for preventing duplicate entry of collection and payment transactions. The transaction contains several sub-transactions, and it can be determined whether the key business steps of the collection and payment transaction are repeated. If repeated, the transaction is terminated and an alarm is issued. That is, the present application designs an internal anti-duplicate mechanism to issue an alarm for the duplication that may occur during the entry process so that it can be handled in time. In addition, before submitting the transaction, the transaction is monitored. If it is found that the number of repeated sub-transactions is greater than or equal to the first preset threshold, the submission of the transaction is terminated. The monitoring of the transaction before submitting the transaction can achieve pre-blocking, and the corresponding transaction is blocked and terminated before it is entered into the account, avoiding duplicate entries. That is, the present application strengthens active prevention and control in the application logic, and increases monitoring and disposal during batch entry. The combination of the two effectively blocks and reduces the risk of duplicate entries.
[0037] Various non-limiting implementations of the present application are described in detail below in conjunction with the accompanying drawings.
[0038] Exemplary Methods
[0039] See also Figure 1 , which is a flow chart of a method for preventing duplicate entry of collection and payment transactions provided by an embodiment of the present application, and the method may include:
[0040] S101, determining whether the collection and payment file corresponding to the collection and payment transaction received by the collection and payment system, the details obtained by parsing the file by the collection and payment system, the details received by the collection and payment system, the details submitted by the collection and payment system or the file submitted by the collection and payment system are repeated.
[0041] In the embodiments of the present application, for various banking systems involved in batch account processing business with third parties, combined with the business scenarios, risk points, risk prevention, inspection rules, and exception handling mechanisms of existing banking business, the current common risk points, inspection rules, monitoring, and disposal methods are analyzed and summarized.
[0042] Regarding the issue of duplicate entries, we can determine whether the key business steps before entry are repeated, and whether the collection and payment files corresponding to the collection and payment transactions received by the collection and payment system are repeated. That is, the collection and payment files may have received multiple identical collection and payment files. In order to determine whether the collection and payment files are repeated, the file name and MD5 value can be used to verify whether the files are repeated.
[0043] Determine whether the details obtained by the collection and payment system from the file parsing are repeated. The repeated details obtained by the file parsing may include the same detail being parsed into multiple different sub-transactions, or the same detail being parsed into the same sub-transaction multiple times. Set a unique index for the details to distinguish whether each entry detail is repeated (for example, the message identification number + transaction type can be used as the unique index).
[0044] Determine whether the details received by the collection and payment system are repeated, that is, the collection and payment system may send the parsed details to the collection and payment system multiple times. Similarly, the unique index set for the details can be used to distinguish each entry detail.
[0045] Determine whether the details submitted by the collection and payment system are repeated, that is, the same detail may be submitted to multiple different sub-transactions, or the same detail may be submitted to the same sub-transaction multiple times. For example, the detail of employee A's salary of 5,000 yuan is submitted to both the sub-transaction of employee A's salary payment and other sub-transactions, that is, the same detail is submitted to multiple different sub-transactions; the detail of salary of 5,000 yuan has been submitted to the sub-transaction of employee A's salary payment, and it is submitted to the sub-transaction of employee A's salary payment, that is, the same detail is submitted to the same sub-transaction multiple times.
[0046] Determine whether the files submitted by the collection and payment system are duplicates. Similarly, the same file may be submitted to multiple different sub-transactions, or the same file may be submitted to the same sub-transaction multiple times.
[0047] In addition, see Table 1 and Figure 2 , different statuses can be set for details according to the business steps in the collection and payment transaction. The detail status can include "initial status, called up, successful, failed". The details received by the collection and payment system can only be the details in the initial status. This can prevent details in other status from being sent to the collection and payment system, and prevent details in the status of called up, successful or failed from being sent to the collection and payment system repeatedly.
[0048] When the core system submits the details, the status of the details is "already called up", which means that the details are being processed. At this time, other sub-transactions will not be able to submit the details repeatedly. For example, the detail of employee A's salary of 5,000 yuan is being submitted to the sub-transaction of employee A's salary payment. At this time, the status of "already called up" is assigned to this detail. If the sub-transaction of employee B's salary payment wants to call up the detail of employee A's salary of 5,000 yuan, at this time, because the status of "already called up" has been assigned to this detail, it cannot be called up by other transactions repeatedly.
[0049] Similarly, when the detail status is failed or successful, the detail cannot be called by other transactions.
[0050]
[0051]
[0052] Table 1
[0053] S102: If repeated, terminate the transaction and issue an alarm.
[0054] In the embodiment of the present application, if any repetition in S101 occurs, the agency payment transaction is terminated and an alarm is issued. After the alarm is issued, the transaction can be transferred to manual processing.
[0055] In addition, when the contemporary payment system fails to receive the file within the specified time, that is, when the file transmission times out, an alarm will be issued, and the system can be transferred to manual processing after the alarm.
[0056] When the order of transaction processing contained in the file is out of order, for example, the order of transaction processing contained in the file should be AB, that is, A is processed first and then B. If it becomes BA due to the disorder, it can be determined that the order of transaction processing contained in the file is out of order. At this time, an alarm is also required, and manual processing can be performed after the alarm.
[0057] When the reconciliation of the information of the previous transaction contained in the file fails, for example, before each transaction is recorded, the information of the previous transaction is reconciled first to determine whether the previous transaction was successfully recorded. Only when the previous transaction was successfully recorded, the current transaction is recorded. If the reconciliation of the previous transaction fails, an alarm is required to recheck the previous transaction.
[0058] If this transaction is still recorded when the previous transaction reconciliation fails, it may result in missed accounts, that is, the previous transaction was not successfully recorded, and recording this transaction at this time is equivalent to the recording operation of the previous transaction being omitted.
[0059] When the submission of details times out, that is, no feedback indicating successful submission of details is received within the specified time, an alarm is required and the process can be transferred to manual processing to determine the reason for the timeout of the submission of details.
[0060] When communication is abnormal, such as when communication is interrupted during file transfer, it is easy to cause the loss of transmission content and other impacts. Therefore, when communication abnormalities occur, an alarm is also required and it can be transferred to manual processing.
[0061] refer to Figure 3 The figure shows the overall specific processing flow of the collection and payment transaction.
[0062] S103, before submitting the transaction, monitoring the transaction, if it is found that the number of repeated sub-transactions in the transaction is greater than or equal to a first preset threshold, terminating submission of the transaction.
[0063] In the examples of this application, refer to Figure 4 As shown, before submitting a transaction, you can first call the monitoring program, and the real-time monitoring program can be used to locally query whether there is a successful entry record for each sub-transaction in the transaction, so as to determine whether each sub-transaction is submitted repeatedly.
[0064] If it is found that the number of repeated sub-transactions in a transaction is greater than or equal to a first preset threshold, the transaction submission is terminated and an alarm is issued.
[0065] For example, if user A should transfer 5,000 yuan to user B, and if user A transfers two payments of 5,000 yuan to user B, the second payment of 5,000 yuan needs to be intercepted, and the submission of the entire transaction needs to be terminated. An alarm can also be issued, and the alarm level at this time is high.
[0066] In addition, when the alarm level is high, it can be transferred to manual processing, and humans can determine whether it is necessary to activate the script or online interface pre-configured in Nebula to freeze or wipe accounts for subsequent emergency disposal.
[0067] It should be noted that in the embodiments of the present application, a certain monitoring time period can be set for monitoring, and the monitoring time period can be determined by those skilled in the art based on the application scenario, and the present application does not make any specific limitation thereto.
[0068] In addition, after completing the collection and payment transaction, an execution report of the collection and payment transaction can be generated. The execution report may include, for example, the processing time of the collection and payment transaction, the total number of collection and payment transactions, the number of successful collection and payment transactions, the number of failed collection and payment transactions, the number of abnormal collection and payment transactions, the number of manual transfers, etc.
[0069] The embodiment of the present application provides a method for preventing duplicate entry of collection and payment transactions. The transaction contains several sub-transactions, and it can be determined whether the key business steps of the collection and payment transaction are repeated. If repeated, the transaction is terminated and an alarm is issued. That is, the present application designs an internal anti-duplicate mechanism to issue an alarm for possible duplications during the entry process so that it can be handled in a timely manner. In addition, before submitting the transaction, the transaction is monitored. If it is found that the number of repeated sub-transactions is greater than or equal to the first preset threshold, the submission of the transaction is terminated. The monitoring of the transaction before submitting the transaction can achieve pre-blocking, and the corresponding transaction is blocked and terminated before it is entered into the account, avoiding duplicate entries. That is, the present application strengthens active prevention and control in the application logic, and increases monitoring and disposal during batch entry. The combination of the two effectively blocks and reduces the risk of duplicate entries.
[0070] Exemplary Devices
[0071] See also Figure 5 , which is a schematic diagram of a device for preventing duplicate entry of collection and payment transactions provided in an embodiment of the present application, may include:
[0072] The judgment unit 201 is used to judge whether the collection and payment file corresponding to the collection and payment transaction received by the collection and payment system, the details obtained by parsing the file by the collection and payment system, the details received by the collection and payment system, the details submitted by the collection and payment system, or the file submitted by the collection and payment system are repeated;
[0073] A first alarm unit 202, used to terminate the transaction and issue an alarm if the transaction is repeated;
[0074] The transaction termination unit 203 is used to monitor the transaction before submitting the transaction, and terminate the submission of the transaction if it is found that the number of repeated sub-transactions in the transaction is greater than or equal to a first preset threshold.
[0075] Optionally, the repeated details submitted by the payment collection system include the same detail being submitted to multiple different sub-transactions, or the same detail being submitted to the same sub-transaction multiple times.
[0076] Optionally, the details obtained by the collection and payment system from parsing the file repeatedly include parsing the same detail into multiple different sub-transactions, or the same detail being parsed into the same sub-transaction multiple times.
[0077] Optionally, the device further comprises:
[0078] The second alarm unit is used to issue an alarm when the file transmission times out, the order of transaction processing contained in the file is disordered, the information reconciliation of the previous transaction contained in the file fails, the detail submission times out, the file submission times out, or the communication is abnormal.
[0079] Optionally, the device further comprises:
[0080] The execution report generating unit is used to generate an execution report of the agency collection and payment transaction after completing the agency collection and payment transaction.
[0081] The configuration of each unit or module of the device of the present application can refer to Figure 1 The method shown in the figure is implemented and will not be described in detail here.
[0082] The embodiment of the present application provides a device for preventing duplicate entry of collection and payment transactions. The transaction contains several sub-transactions, and it can determine whether the key business steps of the collection and payment transaction are repeated. If repeated, the transaction is terminated and an alarm is issued. That is, the present application designs an internal anti-duplicate mechanism to issue an alarm for duplicates that may occur during the entry process so that they can be handled in a timely manner. In addition, before submitting the transaction, the transaction is monitored. If it is found that the number of repeated sub-transactions is greater than or equal to the first preset threshold, the submission of the transaction is terminated. The monitoring of the transaction before submitting the transaction can achieve pre-blocking, and the corresponding transaction is blocked and terminated before it is entered into the account, avoiding duplicate entries. That is, the present application strengthens active prevention and control in the application logic, and increases monitoring and disposal during batch entry. The combination of the two effectively blocks and reduces the risk of duplicate entries.
[0083] It should be noted that each embodiment in this specification is described in a progressive manner, and the same and similar parts between the embodiments can refer to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device and system embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can refer to the partial description of the method embodiments. The device and system embodiments described above are merely schematic, in which the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the scheme of this embodiment. Ordinary technicians in this field can understand and implement it without paying creative work.
[0084] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any changes or substitutions that can be easily thought of by a person skilled in the art within the technical scope disclosed in the present application should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.
Claims
1. A method for preventing duplicate entry of collection and payment transactions, characterized in that: The transaction includes a plurality of sub-transactions, and the method includes: Determine whether the agency collection and payment file corresponding to the agency collection and payment transaction received by the agency collection and payment system, the details obtained by parsing the file by the agency collection and payment system, the details received by the agency collection and payment system, the details submitted by the agency collection and payment system, or the file submitted by the agency collection and payment system are repeated; wherein the status of the details includes: an initial status or a called-up status, the details in the initial status are in a status that can be submitted, the called-up status is in a status that cannot be submitted, before the details are submitted, the status of the details is the initial status, and after the details are submitted, the status of the details is the called-up status; If repeated, the transaction is terminated and an alarm is issued; Before submitting the transaction, the transaction is monitored, and if it is found that the number of repeated sub-transactions in the transaction is greater than or equal to a first preset threshold, submission of the transaction is terminated.
2. The method according to claim 1, characterized in that The details submitted by the payment collection system are repeated, including: The same detail is submitted to multiple different sub-transactions; or the same detail is submitted to the same sub-transaction multiple times.
3. The method according to claim 1, characterized in that The details obtained by the collection and payment system from parsing the file are repeated, including: The same detail is parsed into multiple different sub-transactions; or the same detail is parsed into the same sub-transaction multiple times.
4. The method according to claim 1, characterized in that: The method further comprises: When the file transmission times out, the order of transaction processing contained in the file is disordered, the information reconciliation of the previous transaction contained in the file fails, the detail submission times out, the file submission times out or the communication is abnormal, an alarm is issued.
5. The method according to claim 1, characterized in that The method further comprises: After the agency collection and payment transaction is completed, an execution report of the agency collection and payment transaction is generated.
6. A device for preventing duplicate entry of payment and collection transactions, characterized in that: The transaction includes a plurality of sub-transactions, and the device includes: A judgment unit is used to judge whether the agency collection and payment file corresponding to the agency collection and payment transaction received by the agency collection and payment system, the details obtained by parsing the file by the agency collection and payment system, the details received by the agency collection and payment system, the details submitted by the agency collection and payment system, or the file submitted by the agency collection and payment system are repeated; wherein the status of the details includes: an initial status or a called-up status, the details in the initial status are in a status that can be submitted, the called-up status is in a status that cannot be submitted, before the details are submitted, the status of the details is the initial status, and after the details are submitted, the status of the details is the called-up status; A first alarm unit, used for terminating the transaction and issuing an alarm if the transaction is repeated; The transaction termination unit is used to monitor the transaction before submitting the transaction, and terminate the submission of the transaction if it is found that the number of repeated sub-transactions in the transaction is greater than or equal to a first preset threshold.
7. The device according to claim 6, characterized in that The details submitted by the payment collection system are repeated, including: The same detail is submitted to multiple different sub-transactions; or the same detail is submitted to the same sub-transaction multiple times.
8. The device according to claim 6, characterized in that The details obtained by the collection and payment system from parsing the file are repeated, including: The same detail is parsed into multiple different sub-transactions; or the same detail is parsed into the same sub-transaction multiple times.
9. The device according to claim 6, characterized in that The device also includes: The second alarm unit is used to issue an alarm when the file transmission times out, the order of transaction processing contained in the file is disordered, the information reconciliation of the previous transaction contained in the file fails, the detail submission times out, the file submission times out, or the communication is abnormal.
10. The device according to claim 6, characterized in that The device also includes: The execution report generating unit is used to generate an execution report of the agency collection and payment transaction after completing the agency collection and payment transaction.