Risk transaction processing method and apparatus, electronic device, and storage medium

Abstract

The application discloses a risk transaction processing method and device, electronic equipment and a storage medium, and the method comprises the following steps: in response to a risk control trigger operation, obtaining to-be-processed risk transaction information; based on a pre-constructed rough scene set, determining at least one target risk scene category corresponding to the to-be-processed risk transaction information; for each target risk scene category, based on the current target risk scene category and the pre-constructed refined scene set, determining at least one target risk transaction scene corresponding to the to-be-processed transaction information; based on the control measures corresponding to each target risk transaction scene, performing risk control on the to-be-processed risk transaction information. The technical scheme of the embodiment of the application realizes automatic control and disposal of risk transaction information, and through rough matching and refined matching, the effect of improving the risk transaction scene matching efficiency is realized, and the risk transaction control efficiency is further improved.

Description

Technical Field

[0001] This invention relates to the field of big data processing technology, and in particular to a risk transaction processing method, apparatus, electronic device, and storage medium. Background Technology

[0002] With the continuous development of network technology and the economy and society, people are increasingly conducting electronic transactions through online banking, mobile banking, and other electronic channels. While electronic transactions bring convenience to individuals and businesses, they also pose significant security risks.

[0003] Currently, in existing risk transaction management systems, the system monitoring model outputs a large number of automatic monitoring records, and the results of these records require further analysis and confirmation by personnel. Under these circumstances, it is difficult for staff to monitor and process large amounts of data, resulting in a heavy workload, low efficiency, and a high risk of misjudgment. Summary of the Invention

[0004] This invention provides a risk transaction processing method, apparatus, electronic device, and storage medium to achieve automatic management and handling of risk transaction information. Furthermore, by first performing a rough matching and then a refined matching, it improves the matching efficiency of risk transaction scenarios, thereby further enhancing the management efficiency of risk transactions.

[0005] According to one aspect of the present invention, a risk transaction processing method is provided, the method comprising:

[0006] In response to risk control triggers, obtain information on pending risk transactions;

[0007] Based on a pre-constructed rough scenario set, at least one target risk scenario category corresponding to the risk transaction information to be processed is determined;

[0008] For each of the target risk scenario categories, based on the current target risk scenario category and the pre-constructed detailed scenario set, at least one target risk transaction scenario corresponding to the transaction information to be processed is determined;

[0009] Based on the control measures corresponding to each of the target risk transaction scenarios, risk control is carried out on the risk transaction information to be processed;

[0010] The rough scenario set includes at least one risk scenario category, and each risk scenario category corresponds to a refined scenario set.

[0011] According to another aspect of the present invention, a risk transaction processing apparatus is provided, the apparatus comprising:

[0012] The pending risk transaction information acquisition module is used to acquire pending risk transaction information in response to risk control trigger operations.

[0013] The target risk scenario category determination module is used to determine at least one target risk scenario category corresponding to the risk transaction information to be processed, based on a pre-constructed coarse scenario set.

[0014] The target risk transaction scenario determination module is used to determine at least one target risk transaction scenario corresponding to the transaction information to be processed, based on the current target risk scenario category and a pre-built detailed scenario set, for each of the target risk scenario categories.

[0015] The pending risk transaction management module is used to manage the pending risk transaction information based on the management measures corresponding to each of the target risk transaction scenarios.

[0016] The rough scenario set includes at least one risk scenario category, and each risk scenario category corresponds to a refined scenario set.

[0017] According to another aspect of the present invention, an electronic device is provided, the electronic device comprising:

[0018] At least one processor; and

[0019] A memory communicatively connected to the at least one processor; wherein,

[0020] The memory stores a computer program that can be executed by the at least one processor, which enables the at least one processor to perform the risk transaction processing method described in any embodiment of the present invention.

[0021] According to another aspect of the present invention, a computer-readable storage medium is provided, the computer-readable storage medium storing computer instructions for causing a processor to execute and implement the risk transaction processing method described in any embodiment of the present invention.

[0022] The technical solution of this invention, in response to a risk control trigger operation, acquires information on risk transactions to be processed. Then, based on a pre-built coarse scenario set, it determines at least one target risk scenario category corresponding to the information on risk transactions to be processed. Further, for each target risk scenario category, based on the current target risk scenario category and a pre-built refined scenario set, it determines at least one target risk transaction scenario corresponding to the information on risk transactions to be processed. Finally, based on the control measures corresponding to each target risk transaction scenario, it performs risk control on the information on risk transactions to be processed. This solves the problems in the prior art, such as difficulty in monitoring and processing large amounts of data, large workload, low efficiency, and easy misjudgment. It realizes automatic control and disposal of risk transaction information, achieving the effect of real-time control of multiple risk transaction scenarios. Furthermore, by first performing coarse matching and then refined matching, it improves the matching efficiency of risk transaction scenarios, further improving the control efficiency of risk transactions.

[0023] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of the present invention, nor is it intended to limit the scope of the invention. Other features of the invention will become readily apparent from the following description. Attached Figure Description

[0024] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0025] Figure 1 This is a flowchart of a risk transaction processing method provided in Embodiment 1 of the present invention;

[0026] Figure 2 This is a flowchart of a risk transaction processing method provided in Embodiment 1 of the present invention;

[0027] Figure 3 This is a flowchart of a risk transaction processing method provided in Embodiment 2 of the present invention;

[0028] Figure 4 This is a flowchart of a method for constructing a coarse scene set and a refined scene set according to Embodiment 2 of the present invention;

[0029] Figure 5 This is a schematic diagram of the structure of a risk transaction processing device according to Embodiment 3 of the present invention;

[0030] Figure 6 This is a schematic diagram of the structure of an electronic device that implements the risk transaction processing method of this invention. Detailed Implementation

[0031] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

[0032] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0033] It is understood that before using the technical solutions disclosed in the various embodiments of this disclosure, users should be informed of the types, scope of use, and usage scenarios of the personal information involved in this invention and their authorization should be obtained in accordance with relevant laws and regulations through appropriate means.

[0034] Example 1

[0035] Figure 1 This is a flowchart of a risk transaction processing method provided in Embodiment 1 of the present invention. This embodiment is applicable to situations where real-time risk management of risk transaction information is performed based on pre-constructed coarse and refined scenario sets. This method can be executed by a risk transaction processing device, which can be implemented in hardware and / or software and can be configured in a terminal and / or server. Figure 1 As shown, the method includes:

[0036] S110, In response to risk control triggering operations, obtain information on risk transactions to be processed.

[0037] It should be noted that the information obtained and its purpose have been disclosed to the user in accordance with the law before using the technical solution of the embodiments of the present invention, and the user's authorization has been obtained.

[0038] In this embodiment, a control for triggering risk management can be pre-set. When a user triggers this control, a risk management trigger operation can be responded to, and pending risk transaction information can be obtained. Alternatively, when risk transaction information is detected in the system, it can be considered that a risk management trigger operation has been triggered. Then, a response can be made to this operation, and pending risk transaction information can be obtained. In this case, the risk transaction information that triggered the risk management trigger operation can be considered pending risk transaction information. Pending risk transaction information can be transaction information that requires further processing due to transaction risk. Optionally, pending risk transaction information can be transaction information where the transaction account is at risk or transaction information where the transaction content is at risk. For example, pending risk transaction information can include short-term cross-regional consumption within China, rapid cross-regional cash withdrawal, and cross-regional credit limit attempts.

[0039] It should be noted that when retrieving pending risk transaction information, the same pending risk transaction may repeatedly trigger risk control actions, causing the system to perform risk control multiple times on the same pending risk transaction. Therefore, risk transaction information can be pre-stored in a database and deduplicated within the database. This ensures that the information can be retrieved from the database when retrieving pending risk transaction information, thus guaranteeing the uniqueness of the pending risk transaction information. The advantage of this setup is that it effectively solves the problem of duplicate risk transaction information, ensuring that the same risk transaction is processed only once.

[0040] Based on this, in addition to the above technical solutions, the method further includes: responding to a risk transaction triggering operation, determining at least one risk transaction information and storing each of the risk transaction information in a target storage space; performing deduplication processing on the risk transaction information stored in the target storage space, so as to determine the risk transaction information to be processed based on the processed target storage space.

[0041] In this embodiment, at least one risk field can be pre-set to trigger a risky transaction. When the transaction system detects that at least one field in any transaction log matches the risk field, the transaction log can be considered a risky transaction log, thus confirming that a risky transaction trigger operation has been triggered. In this embodiment, the risky transaction information can be any content in the transaction log that indicates a risk. The target database can be a data warehouse used in the system to store data information. The target database can be any database capable of information storage; optionally, it can be Redis.

[0042] It should be noted that after obtaining the risk transaction information, this information can be transmitted to the target database via the target queue. The target queue can be any queue, optionally a Kafka queue. The advantage of this configuration is that the Kafka queue transmits data via a real-time data bus, ensuring timely data transmission.

[0043] It should also be noted that when deduplicating the risk transaction information stored in the target database, a pre-set election algorithm in the target database can be used to process each risk transaction information. The election algorithm can be any algorithm that can achieve deduplication; optionally, it can be an algorithm based on sequence number election or a majority algorithm, etc.

[0044] In practice, when a risk transaction trigger operation is detected, the operation can be responded to, at least one risk transaction information can be identified, and each risk transaction information can be sent to the target database through the target queue. Furthermore, the risk transaction information stored in the target database is deduplicated so that all the risk transaction information stored in the target database is unique. Thus, when a risk control trigger operation is detected, the risk transaction information to be processed can be obtained from the processed target database.

[0045] S120. Based on a pre-built coarse scenario set, determine at least one target risk scenario category corresponding to the risk transaction information to be processed.

[0046] In this embodiment, after obtaining the risk transaction information to be processed, risk management can be carried out on it, and the corresponding target risk scenario category can be determined.

[0047] The rough scenario set can be a pre-constructed set of one or more risk scenario categories based on historical risk transaction information. It should be noted that the risk scenario categories included in the rough scenario set can be derived not only from historical risk transaction information but also from common risk scenario categories found in the transaction system; this embodiment does not specifically limit this. A risk scenario category can be a combination of one or more risk transaction scenarios with similar fields; that is, one risk scenario category can correspond to one or more risk transaction scenarios with similar fields. For example, when the risk transaction scenario category is "out-of-town consumption," the corresponding risk transaction scenarios could be short-term out-of-town consumption within China, rapid out-of-town cash withdrawal, and out-of-town credit limit attempts, etc.

[0048] It should be noted that since the risk scenario categories included in the rough scenario set are determined based on historical risk transaction information, the fields included in each risk scenario category may be the same as or similar to the fields in the corresponding historical risk transaction information. Therefore, when determining the target risk transaction category corresponding to the risk transaction information to be processed, the fields in the risk transaction information to be processed can be matched with each risk transaction category, and the successfully matched risk transaction category can be used as the target risk transaction category.

[0049] Optionally, based on a pre-built coarse scenario set, at least one target risk scenario category corresponding to the risk transaction information to be processed is determined, including: determining at least one target risk scenario category from the coarse scenario set based on at least one risk transaction field contained in the risk transaction information to be processed.

[0050] In this embodiment, the risk transaction field can be a field in the transaction information used to characterize transaction risk. It should be noted that the risk transaction field can serve as the basis for determining risk transaction information.

[0051] In practice, after obtaining the risk transaction information to be processed, the risk transaction fields contained in the risk transaction information to be processed can be determined. Then, based on each risk transaction field, the risk scenario categories contained in the rough scenario set are traversed. When it is detected that each risk transaction field matches a field contained in any risk scenario category, this risk scenario category can be used as the target risk scenario category.

[0052] It should be noted that there can be one or more target risk scenario categories, that is, the risk transaction information to be processed can trigger one or more target risk scenario categories at the same time.

[0053] S130. For each target risk scenario category, based on the current target risk scenario category and the pre-built detailed scenario set, determine at least one target risk transaction scenario corresponding to the transaction information to be processed.

[0054] It should be noted that after determining each target risk scenario category, the processing method for each target risk scenario category is the same. Therefore, we can take one of the target risk scenario categories as an example to explain the subsequent processing flow.

[0055] In this embodiment, the refined scenario set can be a collection used to describe the specific risk transaction scenarios included in the risk scenario category; that is, the refined scenario set can be a further refinement of the coarse scenario set. For example, when the risk transaction category in the coarse scenario set is cross-regional consumption, the risk transaction scenarios associated with cross-regional consumption in the corresponding refined rule set can be domestic short-term cross-regional consumption, cross-regional rapid cash withdrawal, and cross-regional credit limit attempts, etc.

[0056] In practice, after determining at least one target risk transaction category, a set of detailed scenarios corresponding to the current risk transaction category can be determined for each target risk transaction category. Furthermore, based on the risk transaction fields contained in the risk transaction information to be processed, each risk transaction scenario contained in the detailed scenario set is traversed. When it is detected that each risk transaction field matches a field contained in any risk transaction scenario, this risk transaction scenario can be taken as the target risk transaction scenario.

[0057] It should be noted that there can be one or more target risk transaction scenarios, that is, the risk transaction information to be processed can trigger one or more target risk transaction scenarios at the same time.

[0058] S140. Based on the control measures corresponding to each target risk transaction scenario, risk control shall be carried out on the risk transaction information to be processed.

[0059] In this embodiment, the control measures can be pre-set risk management and disposal methods based on the risky transaction scenario. For example, control measures may include account locking, account cancellation, and reduction of account limits.

[0060] It should be noted that after the detailed scenario set is constructed, corresponding control measures can be pre-formulated based on the risk transaction scenarios included in the detailed scenario set, and each risk transaction scenario and each control measure can be stored in correspondence. This allows for the rapid determination of the control measures corresponding to each target risk transaction scenario when the target risk transaction scenario is identified, thereby improving the risk control efficiency of the risk transaction information to be processed.

[0061] Optionally, risk management is carried out on the risk transaction information to be processed based on the control measures corresponding to each target risk transaction scenario, including: determining the control measures corresponding to each target risk transaction scenario based on the pre-built mapping relationship between risk transaction scenarios and control measures, so as to carry out risk management on the risk transaction information to be processed based on each control measure.

[0062] In this embodiment, after determining the risk transaction scenarios included in the detailed scenario set, control measures corresponding to each risk transaction scenario can be determined based on relevant risk transaction policies or historical control effects, and a mapping relationship between risk transaction scenarios and corresponding control measures can be established.

[0063] In practice, after identifying each target risk transaction scenario, control measures corresponding to each target risk transaction scenario can be determined based on the pre-built mapping relationship. Then, risk control can be carried out on the risk transaction information to be processed according to each control measure, so as to realize the disposal of the risk transaction information to be processed.

[0064] It should be noted that after risk control is carried out, the control results can also be sent to the user terminal corresponding to the risk transaction information to be processed, so that users can understand the current control status and make timely feedback.

[0065] Based on this, in addition to the above technical solutions, the method further includes: determining the risk level of the risky transaction information to be processed, issuing a risk alarm based on a preset alarm method corresponding to the risk level, and providing feedback on the control results of the risky transaction information to be processed; when receiving feedback information corresponding to the control results, updating the control results based on the feedback information.

[0066] In this embodiment, the risk level can be a warning level set according to the potential harm, urgency, and development trend of the risky transaction information. For example, the risk level can be divided into Level IV (moderate), Level III (relatively severe), Level II (serious), and Level I (extremely serious). The preset alarm method can be a pre-set set of various methods used to inform the user of the risky transaction situation. Optionally, the preset alarm method may include, but is not limited to, SMS, telephone, and email. The feedback information can be the feedback determined by the user based on the received control results and risk alarm information.

[0067] In practice, the risk level corresponding to the risk transaction information to be processed can be determined based on the pre-established mapping relationship between risk transaction information and corresponding risk levels. Furthermore, a corresponding preset alarm method is determined based on the determined risk level to provide risk warnings to users. Simultaneously, the control results of the risk information to be processed are fed back to the user, allowing them to provide feedback after receiving the risk warnings and control results. Upon receiving the feedback, the control results can be updated accordingly. Specifically, if the feedback indicates that the risk transaction information to be processed is a normal transaction, the control results can be adjusted, and the risk control for the risk transaction information to be processed can be lifted; if the feedback indicates that the risk transaction information to be processed is a risky transaction, the control results are not adjusted, and risk control continues for the risk transaction information to be processed.

[0068] For example, it can be combined Figure 2The risk transaction processing flow is explained in detail as follows: 1. Based on the transaction system, identify risk transaction information and send it to Redis via a Kafka queue; 2. Obtain the risk transaction information to be processed; 3. Based on a coarse scenario set, determine the target risk transaction category corresponding to the risk transaction information to be processed; 4. Based on a refined scenario set and the target risk transaction category, determine the target risk transaction scenario corresponding to the risk transaction information to be processed; 5. Based on the control measures corresponding to the target risk transaction scenario, manage and handle the risk transaction information to be processed; 6. Issue a risk warning and send the control results; 7. Receive feedback information and update the control results based on the feedback information.

[0069] The technical solution of this invention, in response to a risk control trigger operation, acquires information on risk transactions to be processed. Then, based on a pre-built coarse scenario set, it determines at least one target risk scenario category corresponding to the information on risk transactions to be processed. Further, for each target risk scenario category, based on the current target risk scenario category and a pre-built refined scenario set, it determines at least one target risk transaction scenario corresponding to the information on risk transactions to be processed. Finally, based on the control measures corresponding to each target risk transaction scenario, it performs risk control on the information on risk transactions to be processed. This solves the problems in the prior art, such as difficulty in monitoring and processing large amounts of data, large workload, low efficiency, and easy misjudgment. It realizes automatic control and disposal of risk transaction information, achieving the effect of real-time control of multiple risk transaction scenarios. Furthermore, by first performing coarse matching and then refined matching, it improves the matching efficiency of risk transaction scenarios, further improving the control efficiency of risk transactions.

[0070] Example 2

[0071] Figure 3 This is a flowchart of a risk transaction processing method provided in Embodiment 2 of the present invention. Based on the foregoing embodiments, a coarse scenario set and a refined scenario set can be pre-constructed, thereby determining the target risk transaction scenario corresponding to the risk transaction information to be processed based on the coarse scenario set and the refined scenario set. Specific implementation methods can be found in the technical solution of this embodiment. Technical terms that are the same as or similar to those in the above embodiments will not be repeated here.

[0072] like Figure 3 As shown, the method includes:

[0073] S210. Obtain historical risk transaction information within a preset time period before the current moment.

[0074] In this embodiment, the preset duration can be one month, two months, or one year, etc. Historical risk transaction information can be transaction information stored in the transaction system that carries a risk transaction identifier. In practical applications, when any transaction information is determined to be risky, a risk transaction identifier can be added to this transaction information and stored before, during, or after risk management, so that data analysis can be performed on the risk transaction information stored in the transaction system later.

[0075] In practical applications, one can first obtain historical risk transaction information within a preset time period before the current moment, so that the risk transaction scenario can be determined by processing the historical risk transaction information.

[0076] It should be noted that there can be one or more historical risk transaction records.

[0077] S220. Based on the predetermined target fields, process the historical risk transaction information to obtain the risk transaction scenario corresponding to the historical risk transaction information.

[0078] In this embodiment, the target field can be a field used to identify risky transaction scenarios.

[0079] In practical applications, after obtaining historical risk transaction information, the information can be traversed according to pre-determined target fields to extract information related to risk transaction scenarios, thereby obtaining the risk transaction scenarios corresponding to the historical risk transaction information.

[0080] S230. Based on the risk transaction scenarios and the pre-received initial risk transaction scenarios, construct a risk transaction scenario set, and based on the risk transaction scenario set, construct a rough scenario set and a refined scenario set.

[0081] In this embodiment, the initial risk trading scenario can be a common risk trading scenario in the trading system, or a risk trading scenario that occurs frequently in the trading system.

[0082] In practical applications, after obtaining the risk transaction scenarios corresponding to historical risk transaction information, these risk transaction scenarios can be combined with the pre-received initial risk transaction scenarios. The resulting dataset can then be deduplicated to remove duplicate risk transaction scenarios, thereby obtaining a risk transaction scenario set. Furthermore, based on the risk transaction scenario set, a coarse scenario set and a refined scenario set can be constructed.

[0083] Optionally, based on the risk transaction scenario set, a coarse scenario set and a refined scenario set are constructed, including: determining at least one risk scenario category corresponding to the risk transaction scenario set based on a preset classification algorithm, and constructing a coarse scenario set based on each risk scenario category; and constructing a refined scenario set based on the risk transaction scenario set and the coarse scenario set.

[0084] In this embodiment, the preset classification algorithm can be any algorithm for classifying information. The preset classification algorithm can be any classification algorithm; optionally, it can be the Rocchio algorithm.

[0085] In practical implementation, after obtaining the risk transaction scenario set, the risk transaction scenarios included in the risk transaction scenario set can be classified according to a preset classification algorithm to determine at least one risk scenario category. Then, a rough scenario set can be constructed based on each risk scenario category. Furthermore, the rough scenario set can be refined based on each risk transaction scenario included in the risk transaction scenario set to determine at least one risk transaction scenario associated with each risk scenario category included in the rough scenario set. Based on at least one risk transaction scenario, a refined scenario set corresponding to the corresponding risk transaction category can be constructed.

[0086] It should be noted that after constructing the coarse scenario set and the refined scenario set, the trading system can automatically perform risk trading scenario analysis on the newly stored historical risk trading information, and thus update the coarse scenario set and the refined scenario set based on the analysis results.

[0087] For example, such as Figure 4 As shown, the construction process of the coarse scenario set and the refined scenario set can be explained as follows: 1. Obtain historical risk transaction information and initial risk transaction scenarios; 2. Based on the historical risk transaction information and initial risk transaction scenarios, construct a risk transaction scenario set; 3. Based on the risk transaction scenario set, construct the coarse scenario set and the refined scenario set.

[0088] S240, In response to risk control triggering operations, obtain information on risk transactions to be processed.

[0089] S250. Based on a pre-built coarse scenario set, determine at least one target risk scenario category corresponding to the risk transaction information to be processed.

[0090] S260. For each target risk scenario category, based on the current target risk scenario category and the pre-built detailed scenario set, determine at least one target risk transaction scenario corresponding to the transaction information to be processed.

[0091] S270. Based on the control measures corresponding to each target risk transaction scenario, risk control shall be carried out on the risk transaction information to be processed.

[0092] The technical solution of this invention constructs a coarse scenario set and a refined scenario set based on historical risk transaction information. Then, in response to a risk control trigger operation, it acquires the risk transaction information to be processed. Furthermore, based on the pre-constructed coarse scenario set, it determines at least one target risk scenario category corresponding to the risk transaction information to be processed. Further, for each target risk scenario category, based on the current target risk scenario category and the pre-constructed refined scenario set, it determines at least one target risk transaction scenario corresponding to the transaction information to be processed. Finally, based on the control measures corresponding to each target risk transaction scenario, it performs risk control on the risk transaction information to be processed. This solves the problems of difficulty in monitoring and processing large amounts of data, high workload, low efficiency, and easy misjudgment in the prior art. It realizes the automatic control and disposal of risk transaction information, achieving the effect of real-time control of multiple risk transaction scenarios. Moreover, by first performing coarse matching and then refined matching, it improves the matching efficiency of risk transaction scenarios, further improving the control efficiency of risk transactions.

[0093] Example 3

[0094] Figure 5 This is a schematic diagram of the structure of a risk transaction processing device provided in Embodiment 3 of the present invention. Figure 5 As shown, the device includes: a pending risk transaction information acquisition module 310, a target risk scenario category determination module 320, a target risk transaction scenario determination module 330, and a pending risk transaction management module 340.

[0095] Among them, the pending risk transaction information acquisition module 310 is used to acquire pending risk transaction information in response to risk control triggering operations.

[0096] The target risk scenario category determination module 320 is used to determine at least one target risk scenario category corresponding to the risk transaction information to be processed based on a pre-constructed coarse scenario set.

[0097] The target risk transaction scenario determination module 330 is used to determine at least one target risk transaction scenario corresponding to the transaction information to be processed, based on the current target risk scenario category and a pre-built detailed scenario set, for each of the target risk scenario categories.

[0098] The pending risk transaction management module 340 is used to manage the pending risk transaction information based on the management measures corresponding to each of the target risk transaction scenarios; wherein, the coarse scenario set includes at least one risk scenario category, and each risk scenario category corresponds to a refined scenario set.

[0099] The technical solution of this invention, in response to a risk control trigger operation, acquires information on risk transactions to be processed. Then, based on a pre-built coarse scenario set, it determines at least one target risk scenario category corresponding to the information on risk transactions to be processed. Further, for each target risk scenario category, based on the current target risk scenario category and a pre-built refined scenario set, it determines at least one target risk transaction scenario corresponding to the information on risk transactions to be processed. Finally, based on the control measures corresponding to each target risk transaction scenario, it performs risk control on the information on risk transactions to be processed. This solves the problems in the prior art, such as difficulty in monitoring and processing large amounts of data, large workload, low efficiency, and easy misjudgment. It realizes automatic control and disposal of risk transaction information, achieving the effect of real-time control of multiple risk transaction scenarios. Furthermore, by first performing coarse matching and then refined matching, it improves the matching efficiency of risk transaction scenarios, further improving the control efficiency of risk transactions.

[0100] Optionally, the device further includes: a historical risk transaction data acquisition module, a historical risk transaction data processing module, and a risk transaction scenario set construction module.

[0101] The historical risk transaction data acquisition module is used to acquire historical risk transaction data within a preset time period before the current moment;

[0102] The historical risk transaction data processing module is used to process the historical risk transaction data based on a predetermined target field to obtain the risk transaction scenario corresponding to the risk transaction data.

[0103] The risk transaction scenario set construction module is used to construct a risk transaction scenario set based on the risk transaction scenario and the pre-received initial risk transaction scenario, and to construct a coarse scenario set and a refined scenario set based on the risk transaction scenario set.

[0104] Optionally, the risk trading scenario set construction module includes: a coarse scenario set construction unit and a refined scenario set construction unit.

[0105] A rough scenario set construction unit is used to determine at least one risk scenario category corresponding to the risk transaction scenario set based on a preset classification algorithm, and to construct the rough scenario set based on each of the risk scenario categories;

[0106] The detailed scenario set construction unit is used to construct the detailed scenario set based on the risk transaction scenario set and the rough scenario set.

[0107] Optionally, the device further includes a risk transaction information determination module and a risk transaction processing module.

[0108] The risk transaction information determination module is used to determine at least one piece of risk transaction information in response to the risk transaction triggering operation, and store each piece of risk transaction information in the target storage space;

[0109] The pending risk transaction information determination unit is used to perform deduplication processing on the risk transaction information stored in the target storage space, so as to determine the pending risk transaction information based on the processed target storage space.

[0110] Optionally, the target risk scenario category determination module 320 is specifically used to determine at least one target risk scenario category from the rough scenario set based on at least one risk transaction field contained in the risk transaction information to be processed.

[0111] Optionally, the pending risk transaction management module 340 is specifically used to determine the management measures corresponding to each of the target risk transaction scenarios based on the pre-built mapping relationship between risk transaction scenarios and management measures, so as to perform risk management on the pending risk transaction information based on each of the management measures.

[0112] Optionally, the device further includes a risk level determination module and a feedback information receiving module.

[0113] The risk level determination module is used to determine the risk level of the risk transaction information to be processed, to issue a risk alarm based on a preset alarm method corresponding to the risk level, and to feed back the control result of the risk transaction information to be processed.

[0114] The feedback information receiving module is used to update the control result based on the feedback information received when the control result is received.

[0115] The risk transaction processing apparatus provided in the embodiments of the present invention can execute the risk transaction processing method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the method execution.

[0116] Example 4

[0117] Figure 6A schematic diagram of an electronic device 10 that can be used to implement embodiments of the present invention is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the invention described and / or claimed herein.

[0118] like Figure 6 As shown, the electronic device 10 includes at least one processor 11 and a memory, such as a read-only memory (ROM) 12 or a random access memory (RAM) 13, communicatively connected to the at least one processor 11. The memory stores computer programs executable by the at least one processor. The processor 11 can perform various appropriate actions and processes based on the computer program stored in the ROM 12 or loaded from storage unit 18 into the RAM 13. The RAM 13 may also store various programs and data required for the operation of the electronic device 10. The processor 11, ROM 12, and RAM 13 are interconnected via a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0119] Multiple components in electronic device 10 are connected to I / O interface 15, including: input unit 16, such as keyboard, mouse, etc.; output unit 17, such as various types of displays, speakers, etc.; storage unit 18, such as disk, optical disk, etc.; and communication unit 19, such as network card, modem, wireless transceiver, etc. Communication unit 19 allows electronic device 10 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0120] Processor 11 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of processor 11 include, but are not limited to, central processing unit (CPU), graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, digital signal processors (DSPs), and any suitable processor, controller, microcontroller, etc. Processor 11 performs the various methods and processes described above, such as risk trading processing methods.

[0121] In some embodiments, the risk transaction processing method may be implemented as a computer program tangibly contained in a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program may be loaded and / or mounted on electronic device 10 via ROM 12 and / or communication unit 19. When the computer program is loaded into RAM 13 and executed by processor 11, one or more steps of the risk transaction processing method described above may be performed. Alternatively, in other embodiments, processor 11 may be configured to perform the risk transaction processing method by any other suitable means (e.g., by means of firmware).

[0122] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), payload-programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0123] Computer programs used to implement the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when executed by the processor, the computer programs cause the functions / operations specified in the flowcharts and / or block diagrams to be performed. The computer programs may be executed entirely on a machine, partially on a machine, or as a standalone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0124] In the context of this invention, a computer-readable storage medium can be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, apparatus, or device. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0125] To provide interaction with a user, the systems and techniques described herein can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the electronic device. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0126] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as data servers), or computing systems that include middleware components (e.g., application servers), or computing systems that include frontend components (e.g., user computers with graphical user interfaces or web browsers through which users can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., communication networks). Examples of communication networks include local area networks (LANs), wide area networks (WANs), blockchain networks, and the Internet.

[0127] A computing system can include clients and servers. Clients and servers are generally located far apart and typically interact through communication networks. The client-server relationship is created by computer programs running on the respective computers and having a client-server relationship with each other. The server can be a cloud server, also known as a cloud computing server or cloud host, which is a hosting product within the cloud computing service system to address the shortcomings of traditional physical hosts and VPS services, such as high management difficulty and weak business scalability.

[0128] It should be understood that the various forms of processes shown above can be used, with steps reordered, added, or deleted. For example, the steps described in this invention can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution of this invention can be achieved, and this is not limited herein.

[0129] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. A method for handling risky transactions, characterized in that, include: In response to risk control triggers, obtain information on pending risk transactions; Based on a pre-constructed rough scenario set, at least one target risk scenario category corresponding to the risk transaction information to be processed is determined; For each of the target risk scenario categories, based on the current target risk scenario category and the pre-constructed detailed scenario set, at least one target risk transaction scenario corresponding to the risk transaction information to be processed is determined; Based on the control measures corresponding to each of the target risk transaction scenarios, risk control is carried out on the risk transaction information to be processed; The rough scenario set includes at least one risk scenario category, and each risk scenario category corresponds to a refined scenario set. The refined scenario set is a collection used to describe the specific risk transaction scenarios contained in the risk scenario category. Also includes: Retrieve historical risk transaction information within a preset time period prior to the current moment; Based on predetermined target fields, the historical risk transaction information is processed to obtain risk transaction scenarios corresponding to the risk transaction data; Based on the risk transaction scenarios and the pre-received initial risk transaction scenarios, a risk transaction scenario set is constructed. Based on a preset classification algorithm, at least one risk scenario category corresponding to the risk transaction scenario set is determined, and based on each risk scenario category, the rough scenario set is constructed. Based on the risk transaction scenario set and the rough scenario set, the refined scenario set is constructed.

2. The method according to claim 1, characterized in that, Also includes: In response to the risk transaction triggering operation, at least one risk transaction information is determined, and each of the risk transaction information is stored in the target storage space; The risk transaction information stored in the target storage space is deduplicated to determine the risk transaction information to be processed based on the processed target storage space.

3. The method according to claim 1, characterized in that, The process of determining at least one target risk scenario category corresponding to the risk transaction information to be processed, based on a pre-constructed coarse scenario set, includes: Based on at least one risk transaction field contained in the risk transaction information to be processed, at least one target risk scenario category is determined from the rough scenario set.

4. The method according to claim 1, characterized in that, The risk management of the pending risk transaction information based on the control measures corresponding to each of the target risk transaction scenarios includes: Based on the pre-constructed mapping relationship between risk transaction scenarios and control measures, control measures corresponding to each target risk transaction scenario are determined, so as to perform risk control on the risk transaction information to be processed based on each control measure.

5. The method according to claim 1, characterized in that, Also includes: Determine the risk level of the pending risk transaction information, issue a risk alarm based on a preset alarm method corresponding to the risk level, and provide feedback on the control results of the pending risk transaction information; When feedback information corresponding to the control result is received, the control result is updated based on the feedback information.

6. A risk transaction processing device, characterized in that, include: The pending risk transaction information acquisition module is used to acquire pending risk transaction information in response to risk control trigger operations. The target risk scenario category determination module is used to determine at least one target risk scenario category corresponding to the risk transaction information to be processed, based on a pre-constructed coarse scenario set. The target risk transaction scenario determination module is used to determine at least one target risk transaction scenario corresponding to the risk transaction information to be processed, based on the current target risk scenario category and a pre-built detailed scenario set, for each of the target risk scenario categories. The pending risk transaction management module is used to manage the pending risk transaction information based on the management measures corresponding to each of the target risk transaction scenarios. The rough scenario set includes at least one risk scenario category, and each risk scenario category corresponds to a refined scenario set. The refined scenario set is a collection used to describe the specific risk transaction scenarios contained in the risk scenario category. Also includes: The historical risk transaction data acquisition module is used to acquire historical risk transaction information within a preset time period before the current moment; The historical risk transaction data processing module is used to process the historical risk transaction information based on a predetermined target field to obtain the risk transaction scenario corresponding to the risk transaction data. The risk transaction scenario set construction module is used to construct a risk transaction scenario set based on the risk transaction scenario and the pre-received initial risk transaction scenario, and to construct a coarse scenario set and a refined scenario set based on the risk transaction scenario set; The risk transaction scenario set construction module includes: A rough scenario set construction unit is used to determine at least one risk scenario category corresponding to the risk transaction scenario set based on a preset classification algorithm, and to construct the rough scenario set based on each of the risk scenario categories; The detailed scenario set construction unit is used to construct the detailed scenario set based on the risk transaction scenario set and the rough scenario set.

7. An electronic device, characterized in that, The electronic device includes: At least one processor; and A memory communicatively connected to the at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to perform the risk transaction processing method according to any one of claims 1-5.

8. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that cause a processor to execute the risk transaction processing method according to any one of claims 1-5.

Images