CN111833036B - Method, apparatus, device and computer readable medium for judging repeat transaction - Google Patents
Method, apparatus, device and computer readable medium for judging repeat transaction Download PDFInfo
- Publication number
- CN111833036B CN111833036B CN202010604453.0A CN202010604453A CN111833036B CN 111833036 B CN111833036 B CN 111833036B CN 202010604453 A CN202010604453 A CN 202010604453A CN 111833036 B CN111833036 B CN 111833036B
- Authority
- CN
- China
- Prior art keywords
- transaction
- repeated
- field
- judging
- identification
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 39
- 238000012546 transfer Methods 0.000 claims abstract description 116
- 238000003780 insertion Methods 0.000 claims abstract description 38
- 230000037431 insertion Effects 0.000 claims abstract description 38
- 238000004590 computer program Methods 0.000 claims description 9
- 238000010586 diagram Methods 0.000 description 15
- 230000008569 process Effects 0.000 description 8
- 238000004891 communication Methods 0.000 description 7
- 230000006870 function Effects 0.000 description 6
- 238000012545 processing Methods 0.000 description 5
- 230000003287 optical effect Effects 0.000 description 4
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 230000008901 benefit Effects 0.000 description 2
- 239000000835 fiber Substances 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 239000004065 semiconductor Substances 0.000 description 2
- 230000008859 change Effects 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- XLYOFNOQVPJJNP-UHFFFAOYSA-N water Substances O XLYOFNOQVPJJNP-UHFFFAOYSA-N 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/08—Payment architectures
- G06Q20/10—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
- G06Q20/102—Bill distribution or payments
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- G06Q20/405—Establishing or using transaction specific rules
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 the following steps: receiving a transfer application, the transfer application comprising: transaction identification, repeated configuration identification determined according to the use scene, and a field for judging repeated transaction; inserting the field for judging repeated transaction into a duplication judgment rule information table according to the transaction identifier and the repeated configuration identifier; and judging whether the transaction of the transfer application is the repeated transaction or not according to the insertion result of the field for judging the repeated transaction. The embodiment is suitable for different account transfer use scenes, improves the accuracy of judging repeated transactions, and increases the safety of customer funds.
Description
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 fund safety of clients, and the effective guarantee that the transaction does not repeatedly deduct money is an important basis for the reliability of the transfer transaction.
For example, the customer calls the transfer type transaction interface through his own personal system, and the transfer applications are continuously transmitted for a plurality of times due to the customer's own cause, and the time interval is short. The reliable transfer transaction can correctly process the transfer application of the customer, timely identify the subsequent repeated transaction, timely report the error and process, and ensure the fund safety of the customer.
In the process of implementing the present invention, the inventor finds that at least the following problems exist in the prior art: in different account transfer use scenes, the schemes for judging the repeated transactions are different, and a large number of schemes for judging the repeated transactions exist, so that the accuracy for judging the repeated transactions is low, and the safety of the funds of the customers is influenced.
Disclosure of Invention
In view of this, embodiments of the present invention provide a method, apparatus, device, and computer readable medium for determining repeat transactions, which are applicable to different account transfer usage scenarios, and improve accuracy of determining repeat transactions and security of customer funds.
To achieve the above object, according to one aspect of the embodiments of the present invention, there is provided a method of determining a repeat transaction, including:
receiving a transfer application, the transfer application comprising: transaction identification, repeated configuration identification determined according to the use scene, and a field for judging repeated transaction;
inserting the field for judging repeated transaction into a duplication judgment rule information table according to the transaction identifier and the repeated configuration identifier;
and judging whether the transaction of the transfer application is the repeated transaction or not according to the insertion result of the field for judging the repeated transaction.
The repeated configuration identification and the names of the fields for judging repeated transactions are preset according to the use scene.
And storing the transaction identifier, the repeated configuration identifier, the repeated transaction judgment field and the identifier of the client sending the transfer application in a preset field position in the duplication judgment rule information table.
And assigning unused fields in the weight judging rule information table to be null.
The step of inserting the field for judging the repeated transaction into a duplication judgment rule information table according to the transaction identifier and the repeated configuration identifier comprises the following steps:
determining the transaction according to the transaction identification in the weight judging rule information table;
based on the repeated configuration identifier, acquiring a preset field position of the transaction in the weight judging rule information table;
and inserting the field for judging the repeated transaction into the preset field position.
And 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, wherein the method comprises the following steps:
if the field insertion of the repeated transaction is judged to be successful, determining that the transaction of the transfer application is not the repeated transaction;
and if the field insertion of the repeated transaction is failed, determining that the transaction of the transfer application is the repeated transaction.
The transfer application includes one of an inline transfer, a cross-line transfer, a transfer of funds, and a collection of funds.
According to a second aspect of an embodiment 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: transaction identification, repeated configuration identification determined according to the use scene, and a field for judging repeated transaction;
the inserting module is used for inserting the field for judging the repeated transaction into a duplication 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 the repeated transaction according to the insertion result of the field for judging the repeated transaction.
According to a third aspect of an embodiment of the present invention, there is provided an electronic device that determines a repeat transaction, including:
one or more processors;
storage means for storing one or more programs,
the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the methods as described above.
According to a fourth aspect of embodiments of the present invention, there is provided a computer readable medium having stored thereon a computer program which when executed by a processor implements a 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: transaction identification, repeated configuration identification determined according to the use scene, and a field for judging repeated transaction; inserting the field for judging the repeated transaction into a duplication judgment rule information table according to the transaction identifier and the repeated configuration identifier; and judging whether the transaction of the transfer application is the repeated transaction 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 repeated transaction is the repeated transaction can be judged, the accuracy of judging the repeated transaction is improved, and the safety of the funds of the clients is improved.
Further effects of the above-described non-conventional alternatives are 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 the main flow of a method of determining repeat transactions according to an embodiment of the present invention;
FIG. 2 is a schematic diagram of a weight rule information table according to an embodiment of the present invention;
FIG. 3 is a flow chart of inserting fields for determining repeat transactions into a repeat rule information table according to an embodiment of the present invention;
FIG. 4 is a flow chart of determining 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 present invention;
FIG. 6 is a schematic diagram of the main structure of an apparatus for judging repeat transactions 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 applied;
fig. 8 is a schematic diagram of a computer system suitable for use in implementing an embodiment of the invention.
Detailed Description
Exemplary embodiments of the present invention will now be described with reference to the accompanying drawings, in which various details of the embodiments of the present invention are included to facilitate understanding, and are to be considered 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 safety of the client, a configurable weight judging rule can be provided for the client, the configurability and maintainability of the weight judging rule under different service scenes of the client are realized, the simple requirement change of the client can be realized through parameter configuration, and the new requirement of the client can be rapidly developed and online through configuration.
The current customer transfer use scenes are various, different customers have different rules for judging repeated transactions, and unified customer different transfer use scenes can also have different judgment rules. Such as: and the client A judges the date range of the current day according to the transaction serial number and the transaction date of the client. And B, judging the full-volume transaction running water range according to other information uploaded by the client. It can be seen that different customers have different personalization requirements.
In the past, the repeated transaction is mostly realized by inquiring whether the same transaction information exists in the database, and if the result is found in the database, the repeated transaction is considered. However, no decision can be made regarding transactions that do not involve database operations.
Therefore, the schemes for judging the repeated transaction in different account transfer use scenes are different, and meanwhile, a plurality of schemes for judging the repeated transaction exist, so that the accuracy for judging the repeated transaction is low, and the safety of the funds of the customer is influenced.
In order to solve the technical problem of low accuracy in 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 a repeat transaction according to an embodiment of the present invention, a field for determining a repeat transaction is inserted into a repeat rule information table according to a repeat configuration identifier determined by a usage scenario, and whether the repeat transaction is a repeat transaction 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: transaction identification, duplicate configuration identification determined according to a usage scenario, and a field for judging duplicate transactions.
In the process of the transfer type transaction, the client can send a transfer application to the server, and the purpose of the transfer application is to transfer accounts. 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 customer may send the transfer application through an Application (APP) of the mobile terminal. That is, the transfer request is transmitted through the APP of the mobile terminal. In APP, customer selects transfer, and if the transfer application is judged not to repeat transaction, the transfer is successful; when the transfer application is judged to be a repeat transaction, the transfer fails.
In one embodiment of the invention, the transfer application includes one of inline transfers, cross-line transfers, funds transfer down and funds collection.
Wherein, in-line transfer: refers to transferring money between two accounts belonging to the same bank. Such as: from bank 1 to bank 1. The off-line transfer refers to transfer between accounts belonging to two banks, respectively. Such as: from bank 1 to bank 2. Funds transfer is to transfer funds from one account to multiple accounts according to an account level setting. Funds collection is to collect multiple account funds into one account according to an account level setting.
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 an identifier set by the server for the transaction. As one example, the transaction identifier is A123456AJ. For one transaction, only one transaction identifier is corresponding, based on which the transaction can be uniquely determined.
The duplicate configuration identifier is an identifier corresponding to the duplicate transaction scheme. In the embodiment of the invention, the repeated configuration identification can be determined according to the use scene. As one example, the usage scenario is: transferring accounts in the line, and setting the corresponding repeated configuration identifier to be 01; the use scene is: and transferring the cross-line transfer, and setting the corresponding repeated configuration identifier to be 02. It can be seen that the customer can repeatedly configure the identification according to the usage scenario set.
The duplicate configuration identifier corresponds to a field that determines duplicate transactions. That is, the repeat configuration identifier can be used to determine the repeat transaction field.
The field for judging whether or not the transaction is repeated is a field for judging whether or not the transaction is repeated. For different duplicate configuration identifiers, the fields for determining duplicate transactions may or may not be the same. The field for judging repeated transactions can be set according to actual requirements.
In the embodiment of the invention, the repeated configuration identification and the name of the field for judging repeated transactions can be preset according to the use scene. That is, the name of the repeated configuration identification and judgment repeated transaction field is preset according to the use scenario.
For the server, repeated configuration identifiers can 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 customer needs. That is, the duplicate configuration identification corresponds to the customer identification. Such as: for the client A, in the use scene of the in-line transfer, the corresponding repeated configuration identifier is 11; in the use scenario of off-line transfer, the corresponding duplicate configuration identification is 12.
In addition, the names of the fields for judging the repeated transactions can be preset according to the use scenes. The fields for judging the repeated transactions can be the same or different in name according to different usage scenes.
As one example, in the use scenario of in-line transfer, the names of the fields that determine repeat transactions include electronic banking contract numbers and customer side transaction serial numbers.
As another example, in the use scenario of off-line transfers, the names of the fields that determine repeat transactions include electronic banking contract numbers and transaction times.
It can be seen that the duplicate configuration identification and the name of the field for judging duplicate transactions can be preset according to the usage scenario.
S102, inserting the field for judging the repeated transaction into the duplication judgment rule information table according to the transaction identifier and the repeated configuration identifier.
The weight judgment rule information table is a table for judging repeated transactions. In the embodiment of the invention, the weight judging rule information table can store information related to a plurality of transactions. Whether a plurality of transactions are repeated or not can be judged according to the same weight judging rule information table.
The weight judging 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 searched.
In one embodiment of the present invention, transaction identifications are stored in a preset field position in a duplication judgment rule information table, and the identifications of the fields for repeated transactions and the customers who send transfer applications are repeatedly configured.
Referring to fig. 2, fig. 2 is a schematic diagram of a weight rule information table according to an embodiment of the present invention. In fig. 2, the weight rule information table includes 6 preset fields.
The transaction identification may be stored in a preset field of the first row; storing the repeated configuration identification in a preset field of the second row; and storing the fields for judging the repeated transaction from the preset field I to the preset field IV.
Illustratively, the identity of the customer is stored in a preset field; storing a client transaction serial number in a preset field II; and storing the electronic bank contract number in a preset field III.
It may be appreciated that, for a plurality of duplicate configuration identifiers, a preset field may be reserved in the duplicate determination rule information table to fill in a field for determining duplicate transactions.
Moreover, the duplication decision rule information table is also applicable to the case of a plurality of clients and/or a plurality of transactions. In the case of multiple customers and/or multiple transactions, multiple duplicate configuration identifiers are involved, each reserving a preset field to fill out the field that determines duplicate transactions.
In one embodiment of the present invention, to avoid interfering with the determination of duplicate transactions, a null may be assigned to a plurality of unused fields in the determination rule information table. In this way, when the field for judging the repeat transaction is inserted into the duplication judgment rule information, it is unnecessary to consider insertion into an unused field.
In the process of judging repeated transaction, according to the transaction identification and the repeated configuration identification, inserting the field for judging repeated transaction into the repeated rule information table. It can be understood that for each transaction, whether the transaction is a repeated transaction can be judged through the weight 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 flow chart of inserting a field for determining a repeat transaction into a weight determining rule information table according to an embodiment of the present invention, specifically including:
s301, determining a transaction according to the transaction identification in the duplication judgment rule information table.
The duplication judgment rule information table comprises a plurality of transactions, and the transactions need to be identified according to the transactions. As an example, if the transaction identifier is not searched in the duplication rule information table, the transaction identifier of the current transaction may be filled in a preset field to determine the transaction.
As another example, if the transaction identifier is searched in the duplication rule information table, the transaction may be determined according to the transaction identifier.
S302, based on the repeated configuration identification, acquiring the preset field position of the transaction in the duplication judgment rule information table.
Based on the duplicate configuration identification, the name of the field that determines the duplicate transaction may be determined. Because the fields for judging repeated transactions need to be stored in the preset field positions, the preset field positions of the transactions in the judging repeated rule information table can be obtained.
As one example, in the use scenario of in-line transfer, the duplicate configuration identifier is 01, and it may be determined that the name of the field for determining duplicate transactions is an electronic bank contract number and a client side transaction serial number.
With continued reference to fig. 2, the preset field location of the electronic banking contract number is the preset field three, and the preset field location of the client side transaction serial number is the preset field two.
S303, inserting the field for judging the repeated transaction into a preset field position.
The purpose of knowing the location of the preset field is to insert the field of the repeat transaction into the preset field location. It can be understood that, when the field of the repeated transaction is judged and the preset field position is successfully inserted, the successful insertion is indicated; and if the field of the repeated transaction is judged and the preset field position can not be successfully inserted, the insertion failure is indicated.
In one embodiment of the present invention, if the field for judging the repeat transaction is not stored in the preset field position, the field for judging the repeat transaction can be successfully inserted into the preset field position, and the insertion is successful; accordingly, if the field for judging the repeat transaction is stored in the preset field position, the field for judging the repeat transaction cannot be successfully inserted into the preset field position, and the insertion fails.
In the embodiment of fig. 3, an attempt may be made to insert a field for judging a repeat transaction into the repeat rule information table according to the transaction identification and the repeat configuration identification to judge the repeat transaction through the repeat rule information table.
S103, judging whether the transaction of the transfer application is the repeated transaction 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 for judging the repeated transaction, namely whether the field for judging the repeated transaction is successfully inserted into the duplication 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 an embodiment of the present invention, specifically including:
s401, judging whether the field of the repeated transaction is successfully inserted.
And inserting the field for judging the repeated transaction into the duplication judgment rule information table. If the field for judging the repeated transaction can be inserted into the duplication judging rule information, determining that the field for judging the repeated transaction is successfully inserted, and executing S402; if the field for determining the repeat transaction is not inserted into the repeat rule information, it is determined that the field for determining the repeat transaction fails to be inserted, and S403 is executed.
S402, judging that the field insertion of the repeated transaction is successful, and determining that the transaction of the transfer application is not the repeated transaction.
If the field insertion of the repeat transaction is judged to be successful, the fact that the field insertion of the repeat transaction is not judged in other transfer applications is not judged before the field insertion of the repeat transaction is judged, and then the fact that the transaction of the transfer application is not the repeat transaction is confirmed.
S403, judging that the field insertion of the repeated transaction fails, and determining that the transaction of the transfer application is the repeated transaction.
If the field insertion of the repeat transaction is judged to be failed, the fact that the field insertion of the repeat transaction is judged in other transfer applications is already carried out before the field insertion of the repeat transaction is judged is indicated, and then the transaction of the transfer application is confirmed to be the repeat transaction.
In the embodiment of fig. 4, the determination of whether the transaction of the transfer application is a repeat transaction is made based on the field insertion result of the repeat transaction.
In the above embodiment, the transfer application is received, and the transfer application includes: transaction identification, repeated configuration identification determined according to the use scene, and a field for judging repeated transaction; inserting the field for judging the repeated transaction into a duplication judgment rule information table according to the transaction identifier and the repeated configuration identifier; and judging whether the transaction of the transfer application is the repeated transaction 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 repeated transaction is the repeated transaction can be judged, the accuracy of judging the repeated transaction is improved, and the safety of the funds of the clients is improved.
The following is an exemplary description of the technical solution in the embodiment of the present invention 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 a repeated configuration identifier and judging a repeated transaction field.
The method comprises the following steps of presetting a use scene: the repeated configuration mark of the in-line account is 01, and the use scene is as follows: the fields of the judgment repeat transaction of the in-line transfer are: client transaction serial number and transaction date.
S502, receiving a transfer application.
And if the customer needs to transfer accounts in a row, calling an account transfer transaction interface through a personal system, and sending an account transfer application. The transfer application comprises the following steps: customer identification, transaction identification: a058161AJ, repeated configuration identification: 01. judging a field of the repeated transaction: 123456 and 20101005. Where 123456 is the customer 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.
S503, the field for judging the repeated transaction is disassembled into a judging re-rule information table.
And after receiving the transfer application, the field for judging the repeated transaction is disassembled into the duplicate judgment rule information table. As one example, the following information may be inserted into the weight rule information table:
transaction identification #: a058161AJ,
# complex configuration identifier 01
# reserved field one customer identification
# reserved field two-customer transaction serial number
# reserved field three, transaction date
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 duplication judgment rule information table, the transaction is not the repeated transaction; if the repeated transaction field is not successfully inserted into the duplication judgment rule information table, the transaction is repeated.
As an example, when two a058161AJ transactions with the same transaction identifier are continuously received by the same client in one day, and the same repeated configuration identifier and the field for judging the repeated transaction are adopted, an error is inserted, so that the repeated transaction 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 a repeat transaction according to an embodiment of the present invention, the apparatus for determining a repeat transaction may implement a method for determining a repeat transaction, and as shown in fig. 6, the apparatus for determining a repeat transaction specifically includes:
the receiving module 601 is configured to receive a transfer application, where the transfer application includes: transaction identification, duplicate configuration identification determined according to a usage scenario, and a field for judging duplicate transactions.
The inserting module 602 is configured to insert a field for determining the repeated transaction into the duplication determining rule information table according to the transaction identifier and the duplication configuration identifier.
The judging module 603 is configured to judge whether the transaction of the transfer application is a repeat transaction according to the insertion result of the field for judging the repeat transaction.
In one embodiment of the invention, the duplicate configuration identification and the name of the field for determining duplicate transactions are preset according to the usage scenario.
In one embodiment of the present invention, transaction identifications are stored in a preset field position in a duplication judgment rule information table, and the identifications of the fields for repeated transactions and the customers who send transfer applications are repeatedly configured.
In one embodiment of the present invention, unused fields in the weight rule information table are assigned a null value.
In one embodiment of the present invention, the inserting module 602 is specifically configured to determine a transaction according to the transaction identifier in the duplication judgment rule information table;
based on the repeated configuration identification, acquiring a preset field position of the transaction in the duplication judgment rule information table;
and inserting the field for judging the repeated transaction into a preset field position.
In one embodiment of the present invention, the judging module 603 is specifically configured to judge that the field insertion of the repeat transaction is successful, and determine that the transaction of the transfer application is not the repeat transaction;
if the field insertion of the repeat transaction is judged to fail, the fact that the transaction of the transfer application is the repeat transaction is determined.
In one embodiment of the invention, the transfer application includes one of inline transfers, cross-line transfers, funds transfer down and funds collection.
Fig. 7 illustrates an exemplary system architecture 700 to which the method of determining a repeat transaction or the apparatus of determining a repeat transaction of an embodiment of the present invention may be applied.
As shown in fig. 7, a system architecture 700 may include terminal devices 701, 702, 703, a network 704, and a server 705. The network 704 is the medium used to provide communication links between the terminal devices 701, 702, 703 and the server 705. The network 704 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.
A user may interact with the server 705 via the network 704 using the terminal devices 701, 702, 703 to receive or send messages or the like. Various communication client applications such as shopping class applications, web browser applications, search class applications, instant messaging tools, mailbox clients, social platform software, etc. (by way of example only) may be installed on the terminal devices 701, 702, 703.
The terminal devices 701, 702, 703 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smartphones, tablets, laptop and desktop computers, and the like.
The server 705 may be a server providing various services, such as a background management server (by way of example only) providing support for shopping-type websites browsed by users using the terminal devices 701, 702, 703. The background management server may analyze and process the received data such as the product information query request, and feedback the processing result (e.g., the target push information, the product information—only an example) to the terminal device.
It should be noted that, the method for determining the repeat transaction according to the embodiment of the present invention is generally executed by the server 705, and accordingly, the device for determining the repeat transaction 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, there is illustrated a schematic diagram of a computer system 800 suitable for use in implementing an embodiment of the present invention. The terminal device shown in fig. 8 is only an example, and should not impose any limitation on the functions and the scope of use of the embodiment 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 according to 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 required for the operation of the system 800 are also stored. The CPU 801, ROM 802, and RAM 803 are connected to each other by a bus 804. An input/output (I/O) interface 805 is also connected to the bus 804.
The following components are connected to the I/O interface 805: an input portion 806 including a keyboard, mouse, etc.; an output portion 807 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and a speaker; a storage section 808 including a hard disk or 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. The drive 810 is also connected to the I/O interface 805 as needed. 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 needed so that a computer program read out therefrom is mounted into the storage section 808 as needed.
In particular, according to embodiments of the present disclosure, the processes described above with reference to 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 shown in the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network via the communication section 809, and/or installed from the removable media 811. The above-described functions defined in the system of the present invention are performed when the computer program is executed by a Central Processing Unit (CPU) 801.
The computer readable medium shown in the present invention may be a computer readable signal medium or a computer readable storage medium, or any combination of the two. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any 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 context of this document, 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, the computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, with the computer-readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. 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 flowcharts 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 involved in the embodiments of the present invention may be implemented in software or in hardware. The described modules may also be provided in a processor, for example, as: a processor includes a transmitting unit, an acquiring unit, a determining unit, and a first processing unit. The names of these units do not constitute a limitation on the unit itself in some cases, and for example, the transmitting unit may also be described as "a unit that transmits 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 present alone without being fitted into the device. The computer readable medium carries one or more programs which, when executed by a device, cause the device to include:
receiving a transfer application, the transfer application comprising: transaction identification, repeated configuration identification determined according to the use scene, and a field for judging repeated transaction;
inserting the field for judging repeated transaction into a duplication judgment rule information table according to the transaction identifier and the repeated configuration identifier;
and judging whether the transaction of the transfer application is the repeated transaction or not according to the insertion result of the field for judging the repeated transaction.
According to the technical scheme of the embodiment of the invention, the transfer application is received, and the transfer application comprises: transaction identification, repeated configuration identification determined according to the use scene, and a field for judging repeated transaction; inserting the field for judging the repeated transaction into a duplication judgment rule information table according to the transaction identifier and the repeated configuration identifier; and judging whether the transaction of the transfer application is the repeated transaction 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 repeated transaction is the repeated transaction can be judged, the accuracy of judging the repeated transaction is improved, and the safety of the funds of the clients is improved.
The above embodiments do not limit the scope of the present invention. It will be apparent to those skilled in the art that various modifications, combinations, sub-combinations and alternatives can occur depending upon design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention should be included in the scope of the present invention.
Claims (8)
1. A method of determining repeat transactions, comprising:
receiving a transfer application, the transfer application comprising: the method comprises the steps of transaction identification, repeated configuration identification determined according to a use scene and a repeated transaction judgment field, wherein the repeated configuration identification is identification corresponding to a repeated transaction scheme, and the repeated configuration identification corresponds to the repeated transaction judgment field;
inserting the field for judging repeated transaction into a duplication judgment rule information table according to the transaction identifier and the repeated configuration identifier;
judging whether the transaction of the transfer application is a repeated transaction or not according to the insertion result of the field for judging the repeated transaction;
the step of inserting the field for judging the repeated transaction into a duplication judgment rule information table according to the transaction identifier and the repeated configuration identifier comprises the following steps:
determining the transaction according to the transaction identification in the weight judging rule information table;
based on the repeated configuration identifier, acquiring a preset field position of the transaction in the weight judging rule information table;
inserting the field for judging the repeated transaction into the preset field position;
and 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, wherein the method comprises the following steps:
if the field insertion of the repeated transaction is judged to be successful, determining that the transaction of the transfer application is not the repeated transaction;
and if the field insertion of the repeated transaction is failed, determining that the transaction of the transfer application is the repeated transaction.
2. The method of claim 1, wherein the repeat configuration identifier and the name of the field for determining repeat transactions are preset according to a usage scenario.
3. The method according to claim 1 or 2, wherein the transaction identification, the repeat configuration identification, the repeat transaction judgment field, and the identification of the customer who sent the transfer application are stored in a preset field position in the repeat rule information table.
4. The method of claim 1, wherein unused fields in the duplication decision rule information table are assigned a null value.
5. The method of determining repeat transactions as recited in claim 1, wherein said transfer application includes one of inline transfer, cross-line transfer, funds transfer and funds collection.
6. An apparatus for determining repeat transactions, comprising:
the receiving module is used for receiving a transfer application, and the transfer application comprises: the method comprises the steps of transaction identification, repeated configuration identification determined according to a use scene and a repeated transaction judgment field, wherein the repeated configuration identification is identification corresponding to a repeated transaction scheme, and the repeated configuration identification corresponds to the repeated transaction judgment field;
the inserting module is used for inserting the field for judging the repeated transaction into a duplication judgment rule information table according to the transaction identifier and the repeated configuration identifier; and determining the transaction according to the transaction identification in the weight judging rule information table; based on the repeated configuration identifier, acquiring a preset field position of the transaction in the weight judging rule information table; inserting the field for judging the repeated transaction into the preset field position;
the judging module is used for judging whether the transaction of the transfer application is the repeated transaction according to the insertion result of the field for judging the repeated transaction; and if the field insertion of the repeated transaction is judged to be successful, determining that the transaction of the transfer application is not the repeated transaction; and if the field insertion of the repeated transaction is failed, determining that the transaction of the transfer application is the repeated transaction.
7. An electronic device for determining repeat transactions, comprising:
one or more processors;
storage means for storing one or more programs,
when executed by the one or more processors, causes the one or more processors to implement the method of any of claims 1-5.
8. A computer readable medium, on which a computer program is stored, characterized in that the program, when being executed by a processor, implements the method according to any of claims 1-5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010604453.0A CN111833036B (en) | 2020-06-29 | 2020-06-29 | Method, apparatus, device and computer readable medium for judging repeat transaction |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010604453.0A CN111833036B (en) | 2020-06-29 | 2020-06-29 | Method, apparatus, device and computer readable medium for judging repeat transaction |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111833036A CN111833036A (en) | 2020-10-27 |
| CN111833036B true CN111833036B (en) | 2024-02-13 |
Family
ID=72898315
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010604453.0A Active CN111833036B (en) | 2020-06-29 | 2020-06-29 | Method, apparatus, device and computer readable medium for judging repeat transaction |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111833036B (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2006350626A (en) * | 2005-06-15 | 2006-12-28 | Hitachi Omron Terminal Solutions Corp | Restriction on the number of transactions |
| CN109559106A (en) * | 2018-11-29 | 2019-04-02 | 银联商务股份有限公司 | Fund, which is drawn, pays method, apparatus and realization device |
| CN110111095A (en) * | 2019-04-25 | 2019-08-09 | 银清科技(北京)有限公司 | Payment transaction judging method and payment system |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20130013491A1 (en) * | 2011-04-19 | 2013-01-10 | Early Warning Sevices, LLC | System and method for detecting and mitigating duplicate transaction fraud |
-
2020
- 2020-06-29 CN CN202010604453.0A patent/CN111833036B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2006350626A (en) * | 2005-06-15 | 2006-12-28 | Hitachi Omron Terminal Solutions Corp | Restriction on the number of transactions |
| CN109559106A (en) * | 2018-11-29 | 2019-04-02 | 银联商务股份有限公司 | Fund, which is drawn, pays method, apparatus and realization device |
| CN110111095A (en) * | 2019-04-25 | 2019-08-09 | 银清科技(北京)有限公司 | Payment transaction judging method and payment system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111833036A (en) | 2020-10-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111460129B (en) | Method, device, electronic equipment and storage medium for generating identification | |
| CN109597643A (en) | Using gray scale dissemination method, device, electronic equipment and storage medium | |
| CN108897854A (en) | A kind of monitoring method and device of overtime task | |
| CN111552942B (en) | Identity authentication method, system, device and computer storage medium | |
| CN111881329A (en) | Account balance management method and system | |
| CN110324384A (en) | The method and apparatus of data-pushing | |
| CN111833036B (en) | Method, apparatus, device and computer readable medium for judging repeat transaction | |
| CN112948138A (en) | Method and device for processing message | |
| CN111259032A (en) | Service processing method and device | |
| CN116414628A (en) | Transaction request processing method and device in new and old system switching process | |
| CN111341039B (en) | Card-retaining processing method and system, client and server | |
| CN111210349B (en) | Method and device for transferring and supporting virtual asset, electronic equipment and storage medium | |
| CN113326333A (en) | Data processing method, system, computer device and computer storage medium | |
| CN114417318A (en) | Third-party page jumping method and device and electronic equipment | |
| CN114169863A (en) | Signing method, signing device, electronic equipment and computer readable medium | |
| CN109246686B (en) | Multi-card user address book updating method and device based on cloud technology | |
| CN112836201A (en) | Method, device, equipment and computer readable medium for multi-platform information intercommunication | |
| CN112559646A (en) | Report downloading method and device | |
| CN111338642A (en) | Method, device, terminal and storage medium for determining application downloading path | |
| CN111415245A (en) | Account opening method and device | |
| CN113766437B (en) | Short message sending method and device | |
| CN112950380B (en) | Block chain-based transaction consistency processing method and device | |
| CN108830441B (en) | Resource query method and device | |
| CN115695288A (en) | Login control method and device, electronic equipment and storage medium | |
| CN109656519B (en) | Method and device for automatically accessing service data |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20220920 Address after: 25 Financial Street, Xicheng District, Beijing 100033 Applicant after: CHINA CONSTRUCTION BANK Corp. Address before: 25 Financial Street, Xicheng District, Beijing 100033 Applicant before: CHINA CONSTRUCTION BANK Corp. Applicant before: Jianxin Financial Science and Technology Co.,Ltd. |
|
| TA01 | Transfer of patent application right | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |