Method and device for preventing repeated transaction

Abstract

The invention provides a repeated transaction prevention method and device, and relates to the technical field of data processing. When the method is executed, a business reference number corresponding to a transaction application is generated in a business system initiating a transaction, the business reference numbers corresponding to transactions generated by the same business are the same, and then the business reference numbers corresponding to the transactions generated by the same business are generated in the business system, an aggregation payment platform and a bank or a non-bank payment institution. And judging whether the transactions corresponding to the service reference numbers are repeated transactions or not by using the service reference numbers, and if the transactions corresponding to the service reference numbers are not repeated transactions in a service system, an aggregation payment platform and a bank or a non-bank payment institution, executing the transactions corresponding to the service reference numbers. Therefore, the business reference number used for identifying the transaction of the unique business is generated, and repeated transaction detection of multiple parties including the business system, the aggregation payment platform and the bank or the non-bank payment institution is performed, so that the accuracy of repeated transaction judgment can be ensured, and the repeated transaction can be accurately prevented.

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and in particular to a method and device for preventing duplicate transactions. Background Art

[0002] In the insurance industry, duplicate payment incidents occur every year, such as a claim being paid to a customer multiple times. If the scale is large, it will not only cause huge losses to the company, but also cause disputes and troubles to related practitioners. In the prior art, when a user submits an order, a unique request ID is generally generated and stored in the cache. If a subsequent submission request is found to have the same ID, it will be rejected to prevent duplicate payments. However, if the ID is only repeatedly verified on the customer service side, and the service provider returns an error in the transaction status due to its own reasons, it will cause a duplicate verification error, which will lead to duplicate payments.

[0003] In summary, how to accurately prevent duplicate transactions is a problem that those skilled in the art need to solve urgently. Summary of the invention

[0004] In view of this, the present application provides a method and device for preventing duplicate transactions, aiming to accurately prevent duplicate transactions.

[0005] In a first aspect, the present application provides a method for preventing duplicate transactions, comprising:

[0006] In the business system that initiates the transaction, a business reference number corresponding to the transaction application is generated; transactions generated by the same business have the same business reference number;

[0007] In the business system, the aggregated payment platform, and the bank or non-bank payment institution, respectively, the business reference number is used to determine whether the transaction corresponding to the business reference number is a duplicate transaction;

[0008] If the transactions corresponding to the business reference number in the business system, the aggregate payment platform, the bank or the non-bank payment institution are not duplicate transactions, the transaction corresponding to the business reference number is executed.

[0009] Optionally, the using the business reference number in the business system, the aggregated payment platform, and the bank or non-bank payment institution to determine whether the transaction corresponding to the business reference number is a duplicate transaction includes:

[0010] In the business system, judging whether the transaction corresponding to the business reference number is a repeated transaction by using the business reference number;

[0011] If, in the business system, the transaction corresponding to the business reference number is not a repeated transaction, the business reference number is transmitted to the aggregate payment platform;

[0012] In the aggregate payment platform, judging whether the transaction corresponding to the business reference number is a repeated transaction by using the business reference number;

[0013] If, in the aggregate payment platform, the transaction corresponding to the business reference number is not a duplicate transaction, the business reference number is transmitted to a bank or a non-bank payment institution;

[0014] In the bank or the non-bank payment institution, the business reference number is used to determine whether the transaction corresponding to the business reference number is a repeated transaction.

[0015] Optionally, in the business system, judging whether the transaction corresponding to the business reference number is a duplicate transaction by using the business reference number includes:

[0016] In the business system, querying the business reference number;

[0017] If it is found that the transaction corresponding to the business reference number is in transit or has been completed, the transaction corresponding to the business reference number is determined to be a duplicate transaction;

[0018] If it is not found that the transaction corresponding to the business reference number is in progress or completed, it is determined that the transaction corresponding to the business reference number is not a duplicate transaction.

[0019] Optionally, in the aggregate payment platform, judging whether the transaction corresponding to the business reference number is a repeated transaction by using the business reference number includes:

[0020] In the aggregate payment platform, query the business reference number;

[0021] If it is found that the transaction corresponding to the business reference number is in transit or has been completed, the transaction corresponding to the business reference number is determined to be a duplicate transaction;

[0022] If it is not found that the transaction corresponding to the business reference number is in progress or completed, it is determined that the transaction corresponding to the business reference number is not a duplicate transaction.

[0023] Optionally, in the bank or the non-bank payment institution, judging whether the transaction corresponding to the business reference number is a duplicate transaction by using the business reference number includes:

[0024] Inquiring the business reference number in the bank or the non-bank payment institution;

[0025] If it is found that the transaction corresponding to the business reference number is in transit or has been completed, the transaction corresponding to the business reference number is determined to be a duplicate transaction;

[0026] If it is not found that the transaction corresponding to the business reference number is in progress or completed, it is determined that the transaction corresponding to the business reference number is not a duplicate transaction.

[0027] Optionally, after using the business reference number to determine whether the transaction corresponding to the business reference number is a duplicate transaction in the business system, the aggregated payment platform, and the bank or non-bank payment institution, the method further includes:

[0028] If the transaction corresponding to the business reference number in the business system, the aggregated payment platform, the bank, or the non-bank payment institution is a duplicate transaction, the transaction application will be rejected.

[0029] In a second aspect, the present application provides a device for preventing duplicate transactions, comprising:

[0030] A generation module is used to generate a business reference number corresponding to the transaction application in the business system initiating the transaction; transactions generated by the same business have the same business reference number;

[0031] A repeated transaction judgment module, used to use the business reference number to judge whether the transaction corresponding to the business reference number is a repeated transaction in the business system, the aggregated payment platform, and the bank or non-bank payment institution respectively;

[0032] A transaction execution module is used to execute the transaction corresponding to the business reference number if the transactions corresponding to the business reference number in the business system, the aggregate payment platform, the bank or the non-bank payment institution are not duplicate transactions.

[0033] Optionally, the repeated transaction determination module includes:

[0034] A first judgment unit is used to judge whether the transaction corresponding to the business reference number is a repeated transaction in the business system according to the business reference number;

[0035] A first transmission unit, configured to transmit the business reference number to the aggregate payment platform if the transaction corresponding to the business reference number is not a repeated transaction in the business system;

[0036] A second judgment unit is used to judge whether the transaction corresponding to the business reference number is a repeated transaction in the aggregate payment platform according to the business reference number;

[0037] A second transmission unit is used to transmit the business reference number to a bank or a non-bank payment institution if the transaction corresponding to the business reference number is not a repeated transaction in the aggregated payment platform;

[0038] The third judgment unit is used to judge whether the transaction corresponding to the business reference number is a repeated transaction in the bank or the non-bank payment institution through the business reference number.

[0039] Optionally, the first judging unit includes:

[0040] A first query subunit, used for querying the service reference number in the service system;

[0041] A first determining unit, configured to determine that the transaction corresponding to the business reference number is a repeated transaction if it is found that the transaction corresponding to the business reference number is in transit or has been completed;

[0042] The second determining subunit is used to determine that the transaction corresponding to the business reference number is not a duplicate transaction if no transaction corresponding to the business reference number is found to be in transit or completed.

[0043] Optionally, the second judging unit includes:

[0044] A second query subunit is used to query the business reference number in the aggregate payment platform;

[0045] A third determining subunit is configured to determine that the transaction corresponding to the business reference number is a repeated transaction if it is found that the transaction corresponding to the business reference number is in transit or has been completed;

[0046] The fourth determining subunit is used to determine that the transaction corresponding to the business reference number is not a duplicate transaction if no transaction corresponding to the business reference number is found to be in transit or completed.

[0047] Optionally, the third judgment unit includes:

[0048] A third query subunit, used for querying the business reference number in the bank or the non-bank payment institution;

[0049] a fifth determining subunit, configured to determine that the transaction corresponding to the business reference number is a repeated transaction if it is found that the transaction corresponding to the business reference number is in transit or has been completed;

[0050] The sixth query subunit is used to determine that the transaction corresponding to the business reference number is not a duplicate transaction if no transaction corresponding to the business reference number is found to be in transit or completed.

[0051] Optionally, after using the business reference number to determine whether the transaction corresponding to the business reference number is a duplicate transaction in the business system, the aggregated payment platform, and the bank or non-bank payment institution, the method further includes:

[0052] The rejection module is used to reject the transaction application if the transaction corresponding to the business reference number is a duplicate transaction in the business system, the aggregate payment platform, the bank, or the non-bank payment institution.

[0053] The present application provides a method for preventing duplicate transactions. When executing the method, a business reference number corresponding to the transaction application is generated in the business system that initiates the transaction, wherein the business reference numbers corresponding to transactions generated by the same business are the same. Then, the business reference number is used to determine whether the transaction corresponding to the business reference number is a duplicate transaction in the business system, the aggregate payment platform, and the bank or non-bank payment institution. If the transactions corresponding to the business reference number are not duplicate transactions in the business system, the aggregate payment platform, and the bank or non-bank payment institution, the transaction corresponding to the business reference number is executed. In this way, a business reference number for a transaction that identifies a unique business is generated, and then repeated transaction detection by multiple parties including the business system, the aggregate payment platform, and the bank or non-bank payment institution can ensure the accuracy of repeated transaction judgment, thereby accurately preventing repeated transactions. BRIEF DESCRIPTION OF THE DRAWINGS

[0054] In order to more clearly illustrate the technical solutions in this embodiment or 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.

[0055] Figure 1 A method flow chart of a method for preventing duplicate transactions provided in an embodiment of the present application;

[0056] Figure 2 A flowchart of another method for preventing duplicate transactions provided in an embodiment of the present application;

[0057] Figure 3 A schematic diagram of the structure of a device for preventing duplicate transactions provided in an embodiment of the present application. DETAILED DESCRIPTION

[0058] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. The present application provides a method and device for preventing duplicate transactions, which are used in the field of data processing technology. The above is only an example and does not limit the application field of the method and device provided by the present application.

[0059] In the insurance industry, duplicate payment incidents occur every year, such as a claim being paid to a customer multiple times. If the scale is large, it will not only cause huge losses to the company, but also cause disputes and troubles to related practitioners. In the prior art, when a user submits an order, a unique request ID is generally generated and stored in the cache. If a subsequent submission request is found to have the same ID, it will be rejected to prevent duplicate payments. However, if the ID is only repeatedly verified on the customer service side, and the service provider returns an error in the transaction status due to its own reasons, it will cause a duplicate verification error, which will lead to duplicate payments.

[0060] After research, the inventor proposed the technical solution of the present application. In the business system that initiates the transaction, a business reference number corresponding to the transaction application is generated, wherein the business reference numbers corresponding to the transactions generated by the same business are the same. Then, in the business system, the aggregated payment platform, and the bank or non-bank payment institution, the business reference number is used to determine whether the transaction corresponding to the business reference number is a repeated transaction. If the transactions corresponding to the business reference number are not repeated transactions in the business system, the aggregated payment platform, and the bank or non-bank payment institution, the transaction corresponding to the business reference number is executed. In this way, a business reference number for a transaction that identifies a unique business is generated, and then repeated transaction detection by multiple parties of the business system, the aggregated payment platform, and the bank or non-bank payment institution can ensure the accuracy of repeated transaction judgment, thereby accurately preventing repeated transactions. In order to enable personnel in the technical field to better understand the present application solution, the present application is further described in detail below in conjunction with the accompanying drawings and specific implementation methods. 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 the field without creative work are within the scope of protection of the present application. It should be noted that, for the convenience of description, only the parts related to the relevant invention are shown in the drawings. In the absence of conflict, the embodiments and features in the embodiments of the present application can be combined with each other.

[0061] See also Figure 1 , Figure 1 A method flow chart of a method for preventing duplicate transactions provided in an embodiment of the present application includes:

[0062] S101: In the business system that initiates the transaction, a business reference number corresponding to the transaction application is generated.

[0063] First, when initiating a transaction application, you need to select the business reference number of the transaction corresponding to the transaction application. The business reference number needs to be able to uniquely identify the business attribute value of a transaction. If multiple business attribute values ​​can objectively and uniquely mark a transaction, then a message summary can be generated by splicing multiple business attribute values ​​as the business reference number. Transactions generated by the same business have the same business reference number. If a transaction fails and you initiate a transaction again, the business reference number will not change.

[0064] In some implementations, for example, in a reimbursement system, the reimbursement form number and the payment plan number are objective business numbers, and when combined, they can uniquely represent the business payment. Then, an information summary can be calculated by concatenating the reimbursement form number and the payment plan number, and the information summary can be used as the business reference number. For another example, in a core business system, the actual payment number is an objective business number and uniquely represents the business payment, so the actual payment number can be used as the business reference number.

[0065] S102: Using the business reference number in the business system, the aggregated payment platform, and the bank or non-bank payment institution, determine whether the transaction corresponding to the business reference number is a duplicate transaction.

[0066] The business reference number corresponding to the transaction applied for the transaction is identified in the business system, the aggregated payment platform, and the bank or non-bank payment institution respectively to determine whether the transaction corresponding to the business reference number is a duplicate transaction.

[0067] In some implementations, it is possible to first determine whether a transaction corresponding to a business reference number is a repeated transaction in the business system by using the business reference number. Specifically, the business reference number is queried in the business system. If the transaction corresponding to the business reference number is found to be in transit or completed, the transaction corresponding to the business reference number is determined to be a repeated transaction; if the transaction corresponding to the business reference number is not found to be in transit or completed, the transaction corresponding to the business reference number is determined not to be a repeated transaction. If the transaction corresponding to the business reference number is not a repeated transaction in the business system, the business reference number is transmitted to the aggregated payment platform.

[0068] In the aggregated payment platform, the business reference number is used to determine whether the transaction corresponding to the business reference number is a repeated transaction. Specifically, in the aggregated payment platform, the business reference number is queried. If the transaction corresponding to the business reference number is found to be in transit or completed, the transaction corresponding to the business reference number is determined to be a repeated transaction; if the transaction corresponding to the business reference number is not found to be in transit or completed, the transaction corresponding to the business reference number is determined not to be a repeated transaction. If in the aggregated payment platform, the transaction corresponding to the business reference number is not a repeated transaction, the business reference number is transmitted to the bank or non-bank payment institution.

[0069] In a bank or non-bank payment institution, the business reference number is used to determine whether the transaction corresponding to the business reference number is a duplicate transaction. Specifically, in a bank or non-bank payment institution, the business reference number is queried. If the transaction corresponding to the business reference number is found to be in transit or completed, the transaction corresponding to the business reference number is determined to be a duplicate transaction; if the transaction corresponding to the business reference number is not found to be in transit or completed, the transaction corresponding to the business reference number is determined not to be a duplicate transaction.

[0070] If the transaction corresponding to the business reference number is a duplicate transaction in the business system, aggregated payment platform, bank or non-bank payment institution, the transaction application will be rejected.

[0071] S103: If the transactions corresponding to the business reference number in the business system, the aggregated payment platform, and the bank or non-bank payment institution are not duplicate transactions, the transaction corresponding to the business reference number is executed.

[0072] If the transactions corresponding to the business reference number in the business system, aggregated payment platform, and bank or non-bank payment institutions are not duplicate transactions, it can be accurately proved that the transactions corresponding to the business reference number are not duplicate transactions, and the transactions corresponding to the business reference number can be executed.

[0073] In an embodiment of the present application, in the business system that initiates the transaction, a business reference number corresponding to the transaction application is generated, wherein the business reference numbers corresponding to the transactions generated by the same business are the same, and then, in the business system, the aggregated payment platform, and the bank or non-bank payment institution, the business reference number is used to determine whether the transaction corresponding to the business reference number is a repeated transaction. If the transactions corresponding to the business reference number are not repeated transactions in the business system, the aggregated payment platform, and the bank or non-bank payment institution, the transaction corresponding to the business reference number is executed. In this way, a business reference number for identifying a transaction of a unique business is generated, and then repeated transaction detection by multiple parties including the business system, the aggregated payment platform, and the bank or non-bank payment institution can ensure the accuracy of repeated transaction judgment, thereby accurately preventing repeated transactions.

[0074] The above introduces the method for preventing duplicate transactions provided by the embodiment of the present application. The following is an exemplary description of the method for preventing duplicate transactions in combination with a specific application scenario.

[0075] like Figure 2 As shown, Figure 2 A flowchart of another method for preventing duplicate transactions provided in an embodiment of the present application includes:

[0076] S201: When a transaction application is received, a business reference number corresponding to the transaction is generated.

[0077] When the business system receives the transaction application, it generates a business reference number corresponding to the transaction. The specific generation method is the same as step S101 and will not be repeated here. After the business reference number corresponding to the transaction is generated, the business reference number and business data corresponding to the transaction can be used to generate a data pool to be paid, and the transaction data pool can be used to perform repeated transaction verification on the transaction.

[0078] S202: Determine whether there is a successful or in-progress transaction based on the business reference number.

[0079] The business system determines whether there is a successful or in-progress transaction for the transaction based on the business reference number. If so, step S203 is executed; if not, step S204 is executed.

[0080] S203: Determine that the transaction is a duplicate transaction and the verification fails.

[0081] The business system determines that the transaction is a duplicate transaction, fails the verification, and does not execute the transaction corresponding to the business reference number.

[0082] S204: Determine that the transaction is not a duplicate transaction, if the verification is successful, send the transaction data and the corresponding business reference number of the transaction to the aggregate payment platform.

[0083] The business system determines that the transaction is not a duplicate transaction, passes the verification, and sends the transaction data of the transaction and the corresponding business reference number to the aggregate payment platform. In addition, the transaction data of the transaction and the corresponding business reference number can also be used to generate an outbound data pool, and the transaction data of the transaction and the corresponding business reference number can be sent to the aggregate payment platform using the outbound data pool.

[0084] S205: Receive the transaction data of the transaction and the corresponding business reference number sent by the business system.

[0085] The aggregate payment platform receives the transaction data and the corresponding business reference number of the transaction sent by the business system.

[0086] S206: Determine whether there is a successful or in-progress transaction based on the business reference number.

[0087] The aggregate payment platform determines whether there is a successful or in-progress transaction based on the business reference number. If so, execute step S207; if not, execute step S208.

[0088] S207: Determine that the transaction is a duplicate transaction and the verification fails.

[0089] The aggregate payment platform determines that the transaction is a duplicate transaction, fails the verification, and does not execute the transaction corresponding to the business reference number.

[0090] S208: Determine that the transaction is not a duplicate transaction, if the verification is passed, send the transaction data and the corresponding business reference number of the transaction to a bank or non-bank payment institution.

[0091] The aggregate payment platform determines that the transaction is not a duplicate transaction, passes the verification, and sends the transaction data and the corresponding business reference number of the transaction to the bank or non-bank payment institution. In addition, the transaction data and the corresponding business reference number of the transaction can also be used to generate a transaction order to be paid, and the transaction data and the corresponding business reference number of the transaction can be sent to the bank or non-bank payment institution using the transaction order to be paid.

[0092] S209: Receive the transaction data and corresponding business reference number of the transaction sent by the aggregate payment platform.

[0093] The bank or non-bank payment institution receives the transaction data and the corresponding business reference number of the transaction sent by the aggregated payment platform.

[0094] S210: Determine whether there is a successful or in-progress transaction based on the business reference number.

[0095] The bank or non-bank payment institution determines whether there is a successful or in-progress transaction based on the business reference number. If so, execute step S211; if not, execute step S212.

[0096] S211: The transaction is determined to be a duplicate transaction and the verification fails.

[0097] The bank or non-bank payment institution determines that the transaction is a duplicate transaction, fails the verification, and does not execute the transaction corresponding to the transaction reference number.

[0098] S212: Determine that the transaction is not a duplicate transaction, and if the verification is successful, send the transaction data and the corresponding business reference number of the transaction to the clearing platform for transaction execution.

[0099] The bank or non-bank payment institution determines that the transaction is not a duplicate transaction, and if it passes the verification, the transaction data and the corresponding business reference number of the transaction are sent to the clearing platform for transaction execution.

[0100] In some embodiments, if the business system generates a claim data, the actual payment number is selected as the business reference number to initiate payment. The business system, the aggregated trading platform, the bank or the non-bank payment institution are all verified and released, and the payment is made. Finally, the bank fails the transaction due to network reasons, and returns the payment failure to the payment platform, and the payment platform returns the payment failure to the business system. However, an exception occurs in the internal processing of the bank, and the payment caused by the network failure is resent, and it is finally successful. Because the business system data is in a payment failure state, a second payment action will be initiated. The business reference number remains unchanged during payment, triggering the duplicate judgment logic of the business system and the aggregated trading platform. Because the data is in a failed state in the business system and the payment platform, it is released after passing the verification. When the duplicate judgment logic of the bank or non-bank payment institution is triggered, it is found that the business reference number has been successfully paid on the bank side and is blocked. Duplicate payments caused by inconsistent interactive data status between systems are avoided.

[0101] The above are some specific implementations of the method for preventing duplicate transactions provided by the embodiment of the present application. Based on this, the present application also provides a corresponding device. The device provided by the embodiment of the present application will be introduced from the perspective of functional modularization.

[0102] See also Figure 3 , Figure 3 A schematic diagram of a structure of a device for preventing duplicate transactions provided in an embodiment of the present application, the device for preventing duplicate transactions 300 comprises:

[0103] A generating module 310 is used to generate a business reference number corresponding to the transaction application in the business system initiating the transaction; transactions generated by the same business have the same business reference number;

[0104] A repeated transaction determination module 320 is used to determine whether a transaction corresponding to the business reference number is a repeated transaction by using the business reference number in the business system, the aggregated payment platform, and the bank or non-bank payment institution respectively;

[0105] The transaction execution module 330 is used to execute the transaction corresponding to the business reference number if the transactions corresponding to the business reference number in the business system, the aggregate payment platform, the bank or the non-bank payment institution are not duplicate transactions.

[0106] Optionally, the repeated transaction determination module 320 includes:

[0107] A first judgment unit is used to judge whether the transaction corresponding to the business reference number is a repeated transaction in the business system according to the business reference number;

[0108] A first transmission unit, configured to transmit the business reference number to the aggregate payment platform if the transaction corresponding to the business reference number is not a duplicate transaction in the business system;

[0109] A second judgment unit is used to judge whether the transaction corresponding to the business reference number is a repeated transaction in the aggregate payment platform according to the business reference number;

[0110] A second transmission unit is used to transmit the business reference number to a bank or a non-bank payment institution if the transaction corresponding to the business reference number is not a repeated transaction in the aggregated payment platform;

[0111] The third judgment unit is used to judge whether the transaction corresponding to the business reference number is a repeated transaction in the bank or the non-bank payment institution through the business reference number.

[0112] Optionally, the first judging unit includes:

[0113] A first query subunit, used for querying the service reference number in the service system;

[0114] A first determining unit, configured to determine that the transaction corresponding to the business reference number is a repeated transaction if it is found that the transaction corresponding to the business reference number is in transit or has been completed;

[0115] The second determining subunit is used to determine that the transaction corresponding to the business reference number is not a duplicate transaction if no transaction corresponding to the business reference number is found to be in transit or completed.

[0116] Optionally, the second judging unit includes:

[0117] A second query subunit is used to query the business reference number in the aggregate payment platform;

[0118] A third determining subunit is configured to determine that the transaction corresponding to the business reference number is a repeated transaction if it is found that the transaction corresponding to the business reference number is in transit or has been completed;

[0119] The fourth determining subunit is used to determine that the transaction corresponding to the business reference number is not a duplicate transaction if no transaction corresponding to the business reference number is found to be in transit or completed.

[0120] Optionally, the third judgment unit includes:

[0121] A third query subunit, used for querying the business reference number in the bank or the non-bank payment institution;

[0122] a fifth determining subunit, configured to determine that the transaction corresponding to the business reference number is a repeated transaction if it is found that the transaction corresponding to the business reference number is in transit or has been completed;

[0123] The sixth query subunit is used to determine that the transaction corresponding to the business reference number is not a duplicate transaction if no transaction corresponding to the business reference number is found to be in transit or completed.

[0124] Optionally, after using the business reference number to determine whether the transaction corresponding to the business reference number is a duplicate transaction in the business system, the aggregated payment platform, and the bank or non-bank payment institution, the method further includes:

[0125] The rejection module is used to reject the transaction application if the transaction corresponding to the business reference number is a duplicate transaction in the business system, the aggregate payment platform, the bank, or the non-bank payment institution.

[0126] The embodiments of the present application also provide corresponding devices and computer storage media for implementing the solutions provided by the embodiments of the present application.

[0127] The device includes a memory and a processor, the memory is used to store instructions or codes, and the processor is used to execute the instructions or codes so that the device executes the method described in any embodiment of the present application.

[0128] The computer storage medium stores codes, and when the codes are executed, a device executing the codes implements the method described in any embodiment of the present application.

[0129] Through the description of the above implementation methods, it can be known that those skilled in the art can clearly understand that all or part of the steps in the above-mentioned embodiment method can be implemented by means of software plus a general hardware platform. Based on such an understanding, the technical solution of the present application can be embodied in the form of a software product, which can be stored in a storage medium, such as a read-only memory (ROM) / RAM, a magnetic disk, an optical disk, etc., including a number of instructions for a computer device (which can be a personal computer, a server, or a network communication device such as a router) to execute the methods described in each embodiment of the present application or some parts of the embodiments.

[0130] It should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

[0131] It should also be noted that the various embodiments in this specification are described in a progressive manner, and the same and similar parts between the various embodiments can refer to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the equipment and device 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 embodiment. The device embodiments described above are merely schematic, in which the units described as separate components may or may not be physically separated, and the components prompted 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 labor.

[0132] 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 transactions, characterized in that: include: In the business system that initiates the transaction, a business reference number corresponding to the transaction application is generated; transactions generated by the same business have the same business reference number; In the business system, the aggregated payment platform, and the bank or non-bank payment institution, respectively, the business reference number is used to determine whether the transaction corresponding to the business reference number is a duplicate transaction; If the transactions corresponding to the business reference number in the business system, the aggregate payment platform, the bank or the non-bank payment institution are not duplicate transactions, the transaction corresponding to the business reference number is executed.

2. The method according to claim 1, characterized in that The determining, in the business system, the aggregated payment platform, and the bank or non-bank payment institution, respectively, using the business reference number to determine whether the transaction corresponding to the business reference number is a duplicate transaction includes: In the business system, judging whether the transaction corresponding to the business reference number is a repeated transaction by using the business reference number; If, in the business system, the transaction corresponding to the business reference number is not a repeated transaction, the business reference number is transmitted to the aggregate payment platform; In the aggregate payment platform, judging whether the transaction corresponding to the business reference number is a repeated transaction by using the business reference number; If, in the aggregate payment platform, the transaction corresponding to the business reference number is not a duplicate transaction, the business reference number is transmitted to a bank or a non-bank payment institution; In the bank or the non-bank payment institution, the business reference number is used to determine whether the transaction corresponding to the business reference number is a repeated transaction.

3. The method according to claim 2, characterized in that The determining, in the business system, whether the transaction corresponding to the business reference number is a repeated transaction by using the business reference number includes: In the business system, querying the business reference number; If it is found that the transaction corresponding to the business reference number is in transit or has been completed, the transaction corresponding to the business reference number is determined to be a duplicate transaction; If it is not found that the transaction corresponding to the business reference number is in progress or completed, it is determined that the transaction corresponding to the business reference number is not a duplicate transaction.

4. The method according to claim 2, characterized in that: In the aggregate payment platform, judging whether the transaction corresponding to the business reference number is a repeated transaction by using the business reference number includes: In the aggregate payment platform, query the business reference number; If it is found that the transaction corresponding to the business reference number is in transit or has been completed, the transaction corresponding to the business reference number is determined to be a duplicate transaction; If it is not found that the transaction corresponding to the business reference number is in progress or completed, it is determined that the transaction corresponding to the business reference number is not a duplicate transaction.

5. The method according to claim 2, characterized in that: The step of determining, in the bank or the non-bank payment institution, whether the transaction corresponding to the business reference number is a repeated transaction by using the business reference number includes: Inquiring the business reference number in the bank or the non-bank payment institution; If it is found that the transaction corresponding to the business reference number is in transit or has been completed, the transaction corresponding to the business reference number is determined to be a duplicate transaction; If it is not found that the transaction corresponding to the business reference number is in progress or completed, it is determined that the transaction corresponding to the business reference number is not a duplicate transaction.

6. The method according to claim 1, characterized in that After using the business reference number to determine whether the transaction corresponding to the business reference number is a repeated transaction in the business system, the aggregated payment platform, and the bank or non-bank payment institution, the method further includes: If the transaction corresponding to the business reference number in the business system, the aggregated payment platform, the bank, or the non-bank payment institution is a duplicate transaction, the transaction application will be rejected.

7. A device for preventing duplicate transactions, characterized in that: include: A generation module is used to generate a business reference number corresponding to a transaction application in a business system that initiates a transaction; transactions generated by the same business have the same business reference number; A repeated transaction judgment module, used to use the business reference number to judge whether the transaction corresponding to the business reference number is a repeated transaction in the business system, the aggregated payment platform, and the bank or non-bank payment institution respectively; A transaction execution module is used to execute the transaction corresponding to the business reference number if the transactions corresponding to the business reference number in the business system, the aggregate payment platform, the bank or the non-bank payment institution are not duplicate transactions.

8. The device according to claim 7, characterized in that The repeated transaction judgment module includes: A first judgment unit is used to judge whether the transaction corresponding to the business reference number is a repeated transaction in the business system according to the business reference number; A first transmission unit, configured to transmit the business reference number to the aggregate payment platform if the transaction corresponding to the business reference number is not a duplicate transaction in the business system; A second judgment unit is used to judge whether the transaction corresponding to the business reference number is a repeated transaction in the aggregate payment platform according to the business reference number; A second transmission unit is used to transmit the business reference number to a bank or a non-bank payment institution if the transaction corresponding to the business reference number is not a repeated transaction in the aggregated payment platform; The third judgment unit is used to judge whether the transaction corresponding to the business reference number is a repeated transaction in the bank or the non-bank payment institution through the business reference number.

9. The device according to claim 8, characterized in that The first judging unit includes: A first query subunit, used for querying the service reference number in the service system; A first determining unit, configured to determine that the transaction corresponding to the business reference number is a repeated transaction if it is found that the transaction corresponding to the business reference number is in transit or has been completed; The second determining subunit is used to determine that the transaction corresponding to the business reference number is not a duplicate transaction if no transaction corresponding to the business reference number is found to be in transit or completed.

10. The device according to claim 8, characterized in that The second judging unit includes: A second query subunit is used to query the business reference number in the aggregate payment platform; A third determining subunit is configured to determine that the transaction corresponding to the business reference number is a repeated transaction if it is found that the transaction corresponding to the business reference number is in transit or has been completed; The fourth determining subunit is used to determine that the transaction corresponding to the business reference number is not a duplicate transaction if no transaction corresponding to the business reference number is found to be in transit or completed.

Images