CN111833036A

CN111833036A - Method, device, equipment and computer readable medium for judging repeated transactions

Info

Publication number: CN111833036A
Application number: CN202010604453.0A
Authority: CN
Inventors: 于跃跃; 张永辉
Original assignee: China Construction Bank Corp; CCB Finetech Co Ltd
Current assignee: China Construction Bank Corp
Priority date: 2020-06-29
Filing date: 2020-06-29
Publication date: 2020-10-27
Anticipated expiration: 2040-06-29
Also published as: CN111833036B

Abstract

The invention discloses a method, a device, equipment and a computer readable medium for judging repeated transactions, and relates to the technical field of computers. One embodiment of the method comprises: receiving a transfer application, wherein the transfer application comprises: the system comprises a transaction identifier, a repeated configuration identifier determined according to a use scene, and a field for judging repeated transactions; inserting the field for judging repeated transactions into a repeated judgment rule information table according to the transaction identifier and the repeated configuration identifier; and judging whether the transaction applied for the transfer is a repeated transaction or not according to the insertion result of the field for judging the repeated transaction. The method and the device are suitable for different transfer use scenes, improve the accuracy of judging repeated transactions and increase the safety of client funds.

Description

Method, device, equipment and computer readable medium for judging repeated transactions

Technical Field

The present invention relates to the field of computer technologies, and in particular, to a method, an apparatus, a device, and a computer-readable medium for determining a repeat transaction.

Background

The transfer transaction directly relates to the safety of client funds, and the effective guarantee that the transaction is not repeatedly deducted is an important basis for the reliability of the transfer transaction.

For example, the customer calls the transfer-type transaction interface through the personal system of the customer, and a plurality of transfer applications are continuously sent due to the customer and the time interval is short. Reliable transfer transaction should be able to correctly process the customer's transfer application, and identify subsequent repeated transactions in time, and process the transaction in time and errors, ensuring the safety of the customer's funds.

In the process of implementing the invention, the inventor finds that at least the following problems exist in the prior art: in different transfer use scenes, the schemes for judging repeated transactions are different, and a large number of schemes for judging repeated transactions exist, so that the accuracy for judging the repeated transactions is low, and the safety of the funds of a client is influenced.

Disclosure of Invention

In view of this, embodiments of the present invention provide a method, an apparatus, a device, and a computer readable medium for determining repeat transactions, which are suitable for different usage scenarios of account transfer, improve the accuracy of determining repeat transactions, and increase the security of customer funds.

To achieve the above object, according to an aspect of an embodiment of the present invention, there is provided a method of determining a repeat transaction, including:

receiving a transfer application, wherein the transfer application comprises: the system comprises a transaction identifier, a repeated configuration identifier determined according to a use scene, and a field for judging repeated transactions;

inserting the field for judging repeated transactions into a repeated judgment rule information table according to the transaction identifier and the repeated configuration identifier;

and judging whether the transaction applied for the transfer is a repeated transaction or not according to the insertion result of the field for judging the repeated transaction.

The repeated configuration identifier and the name of the field for judging repeated transactions are preset according to a use scene.

And storing the transaction identification, the repeated configuration identification, the field for judging repeated transaction and the identification of the customer sending the transfer application in a preset field position in the repeated judgment rule information table.

And assigning the unused field in the re-judging rule information table to be null.

Inserting the field for judging the repeated transaction into a repeated judgment rule information table according to the transaction identifier and the repeated configuration identifier, wherein the steps of:

determining the transaction according to the transaction identification in the re-judgment rule information table;

acquiring the position of a preset field of the transaction in the re-judging rule information table based on the repeated configuration identifier;

and inserting the field for judging the repeated transaction into the preset field position.

The step of judging whether the transaction of the transfer application is a repeated transaction according to the insertion result of the field for judging the repeated transaction comprises the following steps:

if the field for judging the repeated transaction is inserted successfully, determining that the transaction applied for the transfer is not the repeated transaction;

and if the field of the repeated transaction is judged to be inserted unsuccessfully, determining that the transaction applied for the transfer is the repeated transaction.

The transfer application includes one of inline transfer, cross-line transfer, fund down-transfer and fund collection.

According to a second aspect of the embodiments of the present invention, there is provided an apparatus for determining a repeat transaction, including:

the receiving module is used for receiving a transfer application, and the transfer application comprises: the system comprises a transaction identifier, a repeated configuration identifier determined according to a use scene, and a field for judging repeated transactions;

the inserting module is used for inserting the field for judging the repeated transaction into a repeated judgment rule information table according to the transaction identifier and the repeated configuration identifier;

and the judging module is used for judging whether the transaction of the transfer application is a repeated transaction according to the insertion result of the field for judging the repeated transaction.

According to a third aspect of the embodiments of the present invention, there is provided an electronic device for determining a repeat transaction, including:

one or more processors;

a storage device for storing one or more programs,

when executed by the one or more processors, cause the one or more processors to implement the method as described above.

According to a fourth aspect of embodiments of the present invention, there is provided a computer readable medium, on which a computer program is stored, which when executed by a processor, implements the method as described above.

One embodiment of the above invention has the following advantages or benefits: receiving a transfer application, wherein the transfer application comprises: the system comprises a transaction identifier, a repeated configuration identifier determined according to a use scene, and a field for judging repeated transactions; inserting the field for judging repeated transactions into a repeated judgment rule information table according to the transaction identification and the repeated configuration identification; and judging whether the transaction applied for the transfer is a repeated transaction or not according to the insertion result of the field for judging the repeated transaction. For each usage scenario, there is a corresponding duplicate configuration identification. Even if the use scenes are different, whether the transaction is repeated can be judged, the accuracy of judging the repeated transaction is improved, and the safety of the fund of the customer is improved.

Further effects of the above-mentioned non-conventional alternatives will be described below in connection with the embodiments.

Drawings

The drawings are included to provide a better understanding of the invention and are not to be construed as unduly limiting the invention. Wherein:

FIG. 1 is a schematic diagram of a main flow of a method of determining repeat transactions according to an embodiment of the present invention;

FIG. 2 is a diagram of a re-determination rule information table according to an embodiment of the present invention;

FIG. 3 is a flowchart illustrating a process of inserting a field for determining repeat transactions into a re-determination rule information table according to an embodiment of the present invention;

FIG. 4 is a schematic flow chart illustrating the determination of whether the transaction of the transfer application is a repeat transaction according to an embodiment of the present invention;

FIG. 5 is a schematic diagram of a flow of a method of determining repeat transactions, according to an embodiment of the invention;

fig. 6 is a schematic diagram of the main structure of an apparatus for determining a repeat transaction according to an embodiment of the present invention;

FIG. 7 is an exemplary system architecture diagram in which embodiments of the present invention may be employed;

fig. 8 is a schematic structural diagram of a computer system suitable for implementing a terminal device or a server according to an embodiment of the present invention.

Detailed Description

Exemplary embodiments of the present invention are described below with reference to the accompanying drawings, in which various details of embodiments of the invention are included to assist understanding, and which are to be considered as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.

Under the current technical framework, in order to ensure the fund security of customers, configurable duplication rules can be provided for the customers, the configurability and maintainability of the duplication rules under different service scenes of the customers are realized, the simple requirement change of the customers can be realized through parameter configuration, and the new requirements of the customers are configured to realize rapid development and online.

The current customer account transfer use scenes are various, different customers have different rules for judging repeated transactions, and different account transfer use scenes of unified customers can have different judgment rules. Such as: and the client A performs date range weight judgment on the current day according to the transaction serial number and the transaction date of the client. And the client B judges the full transaction flow range according to other information uploaded by the client. It can be seen that different customers have different personalization requirements.

In the past, the judgment of the repeated transaction is mostly realized by inquiring whether the database has the same transaction information, and if the result is found in the database, the repeated transaction is considered. However, there is no way to make a decision on transactions that do not involve database operations.

Therefore, the scheme for judging the repeated transactions in different transfer use scenes is different, and a plurality of schemes for judging the repeated transactions exist at the same time, so that the accuracy for judging the repeated transactions is low, and the safety of the funds of the customers is influenced.

In order to solve the technical problem of low accuracy of judging repeated transactions, the following technical scheme in the embodiment of the invention can be adopted.

Referring to fig. 1, fig. 1 is a schematic diagram of a main flow of a method for determining repeat transactions according to an embodiment of the present invention, where a field for determining repeat transactions is inserted into a repeat determination rule information table according to a repeat configuration identifier determined by a usage scenario, and whether the repeat transactions are repeat transactions is determined based on an insertion result. As shown in fig. 1, the method specifically comprises the following steps:

s101, receiving a transfer application, wherein the transfer application comprises the following steps: the system comprises a transaction identifier, a repeated configuration identifier determined according to a use scene, and a field for judging repeated transactions.

The client can send a transfer application to the server in the transfer transaction process, and the transfer application is sent to aim at transferring. The server is an execution main body for executing the technical scheme of the invention. As one example, the server may be located at a bank.

In one embodiment of the invention, the client may send the transfer application through an Application (APP) of the mobile terminal. That is, the transfer application is sent through the APP of the mobile terminal. In the APP, a customer selects transfer, and when the transfer application is judged not to be a repeated transaction, the transfer is successful; and when the transfer application is judged to be a repeated transaction, the transfer fails.

In one embodiment of the invention, the transfer application includes one of an inline transfer, a cross-line transfer, a downward transfer of funds, and a collection of funds.

Wherein, in-line transfer: which refers to the transfer between two accounts belonging to the same bank. Such as: transfer from bank 1 to bank 1. An out-of-line transfer is a transfer between accounts belonging to two banks, respectively. Such as: transfer from bank 1 to bank 2. The fund is transferred to a plurality of accounts according to the account level setting. The fund collection is to collect the funds of a plurality of accounts into one account according to the account hierarchy.

The transfer application comprises a transaction identifier, a repeated configuration identifier determined according to the use scene and a field for judging repeated transactions.

The transaction identifier is the identifier set by the server for this transaction. As one example, the transaction identification is a123456 AJ. For one transaction, only one transaction identifier is corresponded, and the transaction can be uniquely determined based on the transaction identifier.

The repeated configuration identification is the identification corresponding to the repeated trading scheme. In the embodiment of the present invention, the duplicate configuration identifier may be determined according to a usage scenario. As an example, the usage scenario is: in-line transfer, if the corresponding repeated configuration identifier is 01; the usage scenario is: and if the transfer is carried out across lines, the corresponding repeated configuration identifier is 02. As can be seen, the customer can set the duplicate configuration identifier according to the usage scenario.

The duplicate configuration identifier corresponds to a field that determines duplicate transactions. That is, the field for determining the repeat transaction is known from the repeat configuration identifier.

The field for judging a repeat transaction is a field for judging whether a transaction is repeated. For different duplicate configuration identifiers, the fields for determining duplicate transactions may be the same or different. The field for judging repeated transaction can be set according to actual requirements.

In the embodiment of the invention, the repeated configuration identifier and the name of the field for judging repeated transactions can be preset according to the use scene. That is, the names of the fields for repeatedly configuring the identification and judging the repeated transactions are previously set according to the usage scenario.

For the server, the repeated configuration identifiers may be preset according to the usage scenarios, and each identifier corresponds to one usage scenario. As one example, the duplicate configuration identification may also be personalized for the customer needs. That is, the duplicate configuration identification corresponds to the client identification. Such as: for the client A, under the use scene of inline transfer, the corresponding repeated configuration identifier is 11; in the usage scenario of an out-of-line transfer, the corresponding duplicate configuration identifier is 12.

In addition, the name of a field for judging repeated transactions may be preset according to the usage scenario. The fields for judging repeated transactions can be the same or different in name according to different use scenes.

As one example, in the context of the use of inline transfers, the names of the fields that determine repeat transactions include the electronic banking contract number and the customer side transaction serial number.

As another example, in a usage scenario of an out-of-line transfer, the name of the field that determines the repeat transaction includes an electronic banking contract number and a transaction time.

As can be seen, the duplicate configuration identifier and the name of the field for determining duplicate transactions can be set in advance according to the usage scenario.

S102, inserting the field for judging the repeated transaction into a repeated judgment rule information table according to the transaction identifier and the repeated configuration identifier.

The duplication judgment rule information table is a table for judging duplicate transactions. In the embodiment of the present invention, the duplication rule information table may store information related to a plurality of transactions. Whether a plurality of transactions are repeated or not can be judged according to the same judging rule information table.

The duplication judgment rule information table comprises a plurality of preset field positions. Each preset field position is used for storing specified information, so that the information can be quickly found.

In one embodiment of the invention, the re-determination rule information table stores transaction identification at a preset field position, and repeatedly configures the identification, determines fields of repeated transactions and identification of a client sending a transfer application.

Referring to fig. 2, fig. 2 is a schematic diagram of a re-determination rule information table according to an embodiment of the present invention. In fig. 2, the re-determination rule information table includes 6 preset fields.

The transaction identification can be stored in a preset field of the first row; storing a repeated configuration identifier in a preset field of a second row; and storing fields for judging repeated transactions from the first preset field to the fourth preset field.

Illustratively, the identification of the client is stored in a preset field one; storing the transaction serial number of the client side in a preset field two; and storing the electronic banking contract number in a preset field III.

It is understood that preset fields may be reserved in the re-determination rule information table for a plurality of duplicate configuration identifiers to fill in the fields for determining duplicate transactions.

Furthermore, the re-determination rule information table is also applicable to a plurality of customers and/or a plurality of transactions. In the case of multiple customers and/or multiple transactions, multiple duplicate configuration identifiers are involved, each of which reserves a preset field to fill in the field to determine duplicate transactions.

In one embodiment of the present invention, to avoid interfering with the determination of duplicate transactions, a number of unused fields in the re-determination rule information table may be assigned null. In this way, when the field for judging the repeated transaction is inserted into the repeated judgment rule information, the field which is not used does not need to be considered to be inserted.

And in the process of judging repeated transactions, inserting the field for judging repeated transactions into a repeated judgment rule information table according to the transaction identification and the repeated configuration identification. It can be understood that, for each transaction, whether the transaction is a repeated transaction can be judged through the re-judging rule information table, and the scheme of the embodiment of the invention has strong practicability.

Referring to fig. 3, fig. 3 is a schematic flowchart of inserting a field for determining repeated transactions into a re-determination rule information table according to an embodiment of the present invention, which specifically includes:

s301, determining the transaction according to the transaction identification in the re-judging rule information table.

The re-judgment rule information table comprises a plurality of transactions which need to be traded according to transaction identification. As an example, if the transaction id is not searched in the re-judgment rule information table, the transaction id of the current transaction may be filled in the preset field to determine the transaction.

As another example, if the transaction id is searched in the re-determination rule information table, the transaction may be determined according to the transaction id.

S302, acquiring the position of a preset field of the transaction in the re-judging rule information table based on the repeated configuration identifier.

Based on the duplicate configuration identification, a name of a field that determines duplicate transactions may be determined. The field for judging repeated transactions needs to be stored in the preset field position, so that the preset field position of the transactions in the repeated judgment rule information table can be obtained.

As an example, in the usage scenario of inline transfer, if the duplicate configuration flag is 01, it may be determined that the names of the fields for determining duplicate transactions are the electronic banking contract number and the client-side transaction serial number.

With continued reference to fig. 2, the location of the predetermined field of the e-banking contract number is the third predetermined field, and the location of the predetermined field of the customer-side transaction serial number is the second predetermined field.

And S303, inserting the field for judging repeated transaction into a preset field position.

The purpose of knowing the position of the preset field is to insert the field for which a repeat transaction is determined into the position of the preset field. It can be understood that, in the field of the repeated transaction, if the preset field position is successfully inserted, the insertion is successful; and when the field of the repeated transaction is judged, the preset field position cannot be successfully inserted, indicating that the insertion fails.

In an embodiment of the present invention, if the field for determining the repeat transaction is not stored in the preset field position, the field for determining the repeat transaction may be successfully inserted into the preset field position; correspondingly, if the field for judging the repeated transaction is stored in the preset field position, the field for judging the repeated transaction cannot be successfully inserted into the preset field position, and the insertion fails.

In the embodiment of fig. 3, the field for judging the repeated transaction may be tried to be inserted into the re-judging rule information table according to the transaction identifier and the repeated configuration identifier, so as to judge the repeated transaction through the re-judging rule information table.

S103, judging whether the transaction applied for the transfer is the repeated transaction or not according to the insertion result of the field for judging the repeated transaction.

Whether the transaction of the transfer application is the repeated transaction can be judged according to the insertion result of the field of the repeated transaction, namely whether the field of the repeated transaction is successfully inserted into the repeated judgment rule information table.

Referring to fig. 4, fig. 4 is a schematic flow chart of determining whether the transaction of the transfer application is a repeat transaction according to the embodiment of the present invention, which specifically includes:

s401, whether the field of the repeated transaction is inserted successfully is judged.

And inserting the field for judging repeated transactions into a repeated judgment rule information table. If the field for judging the repeated transaction can be inserted into the repeated-transaction-judging rule information, determining that the field for the repeated transaction is successfully inserted, and executing S402; if the field for judging the repeated transaction is not inserted into the repeated judgment rule information, it is determined that the field for judging the repeated transaction fails to be inserted, and S403 is executed.

S402, if the field of the repeated transaction is judged to be inserted successfully, the transaction applied for the transfer is determined not to be the repeated transaction.

And if the field of the repeated transaction is successfully inserted, the fact that the field of the repeated transaction is not inserted in the field of the repeated transaction judged before the field of the repeated transaction judged is inserted means that the field of the repeated transaction judged in other transfer application is not inserted, and the transaction of the transfer application is determined not to be the repeated transaction.

And S403, judging that the field of the repeated transaction fails to be inserted, and determining that the transaction applied for the transfer is the repeated transaction.

And if the field for judging the repeated transaction fails to be inserted, the fact that the field for judging the repeated transaction in other transfer applications is inserted before the field for judging the repeated transaction is inserted indicates that the transaction for judging the repeated transaction is determined to be the repeated transaction.

In the embodiment of fig. 4, the result is inserted according to a field for judging a repeat transaction to determine whether the transaction of the transfer application is a repeat transaction.

In the above embodiment, the transfer application is received, and the transfer application includes: the system comprises a transaction identifier, a repeated configuration identifier determined according to a use scene, and a field for judging repeated transactions; inserting the field for judging repeated transactions into a repeated judgment rule information table according to the transaction identification and the repeated configuration identification; and judging whether the transaction applied for the transfer is a repeated transaction or not according to the insertion result of the field for judging the repeated transaction. For each usage scenario, there is a corresponding duplicate configuration identification. Even if the use scenes are different, whether the transaction is repeated can be judged, the accuracy of judging the repeated transaction is improved, and the safety of the fund of the customer is improved.

The technical solution in the embodiment of the present invention is exemplarily described below with reference to fig. 5.

Referring to fig. 5, fig. 5 is a schematic diagram of a flow of a method for determining a repeat transaction according to an embodiment of the present invention, which specifically includes:

s501, presetting repeated configuration identification and judging fields of repeated transactions.

Presetting a use scene: the inline transfer repeat configuration is marked as 01, and the use scene is as follows: the field for judging repeated transactions of inline transfer is as follows: the client side transaction serial number and transaction date.

And S502, receiving a transfer application.

And if the customer needs inline transfer, calling a transfer transaction interface through a personal system and sending a transfer application. The transfer application comprises the following steps: identification of the customer, identification of the transaction: a058161AJ, duplicate configuration identification: 01. and determining a field of the repeat transaction: 123456, and 20101005. Where 123456 is the customer-side transaction serial number and 20101005 is the transaction date.

As an example, the information in the transfer application may be obtained directly from a message sent by the customer.

And S503, disassembling the field for judging the repeated transaction into a repeated judgment rule information table.

And after receiving the transfer application, disassembling the field for judging the repeated transaction into a re-judging rule information table. As an example, the following information may be inserted into the re-judgment rule information table:

# transaction identification: a, 058161AJ, and the method is that,

# Compound logo 01

Reserved field one identification of client

The # reserved field two is the transaction serial number of the client side

# reserved field three transaction date

And S504, judging whether the transaction is a repeated transaction according to the insertion result.

If the field of the repeated transaction is successfully inserted into the re-judgment rule information table, the transaction is not the repeated transaction; if the field of the repeated transaction is not successfully inserted into the repeated-transaction-judging rule information table, the transaction is the repeated transaction.

As an example, when two A058161AJ transactions with the same transaction identification are received by the same client continuously in one day, and the same repeated configuration identification and the field for judging repeated transactions are adopted, an error is inserted, and then the repeated transactions of the transaction can be judged.

Referring to fig. 6, fig. 6 is a schematic diagram of a main structure of an apparatus for determining repeat transactions according to an embodiment of the present invention, where the apparatus for determining repeat transactions can implement a method for determining repeat transactions, and as shown in fig. 6, the apparatus for determining repeat transactions specifically includes:

the receiving module 601 is configured to receive a transfer application, where the transfer application includes: the system comprises a transaction identifier, a repeated configuration identifier determined according to a use scene, and a field for judging repeated transactions.

And the inserting module 602 is configured to insert the field for determining the repeated transaction into the re-determination rule information table according to the transaction identifier and the repeated configuration identifier.

The judging module 603 is configured to judge whether the transaction of the transfer application is a repeat transaction according to an insertion result of the field for judging the repeat transaction.

In one embodiment of the invention, the names of the fields for repeatedly configuring the identifier and judging the repeated transaction are preset according to the use scene.

In one embodiment of the present invention, the unused fields in the re-rule information table are assigned null.

In an embodiment of the present invention, the inserting module 602 is specifically configured to determine a transaction according to a transaction identifier in the re-determination rule information table;

acquiring the position of a preset field of the transaction in a re-judging rule information table based on the repeated configuration identifier;

and inserting the field for judging the repeated transaction into a preset field position.

In an embodiment of the present invention, the determining module 603 is specifically configured to determine that the field of the repeat transaction is successfully inserted, and determine that the transaction of the transfer application is not a repeat transaction;

and judging that the field of the repeated transaction fails to be inserted, and determining that the transaction applied for the transfer is the repeated transaction.

Fig. 7 illustrates an exemplary system architecture 700 of a method of determining repeat transactions or a device for determining repeat transactions to which embodiments of the present invention may be applied.

As shown in fig. 7, the system architecture 700 may include

terminal devices

701, 702, 703, a network 704, and a server 705. The network 704 serves to provide a medium for communication links between the

terminal devices

701, 702, 703 and the server 705. Network 704 may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few.

A user may use the

terminal devices

701, 702, 703 to interact with a server 705 over a network 704, to receive or send messages or the like. The

terminal devices

701, 702, 703 may have installed thereon various communication client applications, such as a shopping-like application, a web browser application, a search-like application, an instant messaging tool, a mailbox client, social platform software, etc. (by way of example only).

The

terminal devices

701, 702, 703 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, and the like.

The server 705 may be a server providing various services, such as a background management server (for example only) providing support for shopping websites browsed by users using the

terminal devices

701, 702, 703. The backend management server may analyze and perform other processing on the received data such as the product information query request, and feed back a processing result (for example, target push information, product information — just an example) to the terminal device.

It should be noted that the method for determining repeat transactions provided by the embodiment of the present invention is generally executed by the server 705, and accordingly, the device for determining repeat transactions is generally disposed in the server 705.

It should be understood that the number of terminal devices, networks, and servers in fig. 7 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.

Referring now to FIG. 8, shown is a block diagram of a computer system 800 suitable for use with a terminal device implementing an embodiment of the present invention. The terminal device shown in fig. 8 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present invention.

As shown in fig. 8, the computer system 800 includes a Central Processing Unit (CPU)801 that can perform various appropriate actions and processes in accordance with a program stored in a Read Only Memory (ROM)802 or a program loaded from a storage section 808 into a Random Access Memory (RAM) 803. In the RAM 803, various programs and data necessary for the operation of the system 800 are also stored. The CPU 801, ROM 802, and RAM 803 are connected to each other via a bus 804. An input/output (I/O) interface 805 is also connected to bus 804.

The following components are connected to the I/O interface 805: an input portion 806 including a keyboard, a mouse, and the like; an output section 807 including a signal such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage portion 808 including a hard disk and the like; and a communication section 809 including a network interface card such as a LAN card, a modem, or the like. The communication section 809 performs communication processing via a network such as the internet. A drive 810 is also connected to the I/O interface 805 as necessary. A removable medium 811 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 810 as necessary, so that a computer program read out therefrom is mounted on the storage section 808 as necessary.

In particular, according to the embodiments of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In such an embodiment, the computer program can be downloaded and installed from a network through the communication section 809 and/or installed from the removable medium 811. The computer program executes the above-described functions defined in the system of the present invention when executed by the Central Processing Unit (CPU) 801.

It should be noted that the computer readable medium shown in the present invention can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present invention, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present invention, however, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The modules described in the embodiments of the present invention may be implemented by software or hardware. The described modules may also be provided in a processor, which may be described as: a processor includes a transmitting unit, an obtaining unit, a determining unit, and a first processing unit. The names of these units do not in some cases constitute a limitation to the unit itself, and for example, the sending unit may also be described as a "unit sending a picture acquisition request to a connected server".

As another aspect, the present invention also provides a computer-readable medium that may be contained in the apparatus described in the above embodiments; or may be separate and not incorporated into the device. The computer readable medium carries one or more programs which, when executed by a device, cause the device to comprise:

According to the technical scheme of the embodiment of the invention, a transfer application is received, and the transfer application comprises the following steps: the system comprises a transaction identifier, a repeated configuration identifier determined according to a use scene, and a field for judging repeated transactions; inserting the field for judging repeated transactions into a repeated judgment rule information table according to the transaction identification and the repeated configuration identification; and judging whether the transaction applied for the transfer is a repeated transaction or not according to the insertion result of the field for judging the repeated transaction. For each usage scenario, there is a corresponding duplicate configuration identification. Even if the use scenes are different, whether the transaction is repeated can be judged, the accuracy of judging the repeated transaction is improved, and the safety of the fund of the customer is improved.

The above-described embodiments should not be construed as limiting the scope of the invention. Those skilled in the art will appreciate that various modifications, combinations, sub-combinations, and substitutions can occur, depending on design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A method for determining repeat transactions, comprising:

2. The method for judging repeat transaction as claimed in claim 1, wherein the name of the repeat configuration flag and the field for judging repeat transaction are preset according to usage scenario.

3. The method for judging repeat transaction according to claim 1 or 2, wherein the transaction identification, the repeat configuration identification, the field for judging repeat transaction, and the identification of the customer who sent the transfer application are stored in a preset field position in the repeat judgment rule information table.

4. The method for judging repeat transaction according to claim 1, wherein the value of the unused field in the re-judgment rule information table is null.

5. The method for determining repeat transaction according to claim 1 or 2, wherein the inserting the field for determining repeat transaction into a repeat determination rule information table according to the transaction identifier and the repeat configuration identifier comprises:

6. The method for judging repeat transaction according to claim 1, wherein said judging whether the transaction of the transfer application is a repeat transaction according to the insertion result of the field for judging repeat transaction comprises:

7. The method of determining repeat transactions of claim 1 wherein said transfer application includes one of inline transfer, cross-line transfer, funds transfer and funds collection.

8. An apparatus for determining repeat transactions, comprising:

9. An electronic device for determining repeat transactions, comprising:

one or more processors;

a storage device for storing one or more programs,

when executed by the one or more processors, cause the one or more processors to implement the method of any one of claims 1-7.

10. A computer-readable medium, on which a computer program is stored, which, when being executed by a processor, carries out the method according to any one of claims 1-7.