Method, device, electronic device and storage medium for identifying risk types of operations

Abstract

The present application discloses a method, device, electronic device, and storage medium for identifying the risk type of an operation, relating to the field of data analysis technology, and is used to identify the risk type of an operation. In an embodiment of the present application, a server receives operation information sent by a terminal, and the operation information includes first identification information of the customer performing the operation and second identification information of the operated object; based on the risk type of each object of each customer stored in advance, the target risk type of the operated object of the first identification information and the second identification information is determined, and the target risk type is sent to the terminal of the customer of the first identification information for display, thereby being able to identify the risk type of the operation information, without the need to develop a customized risk management model for a single product, which is conducive to later expansion and improving the efficiency of risk management.

Description

Technical Field

[0001] The present application relates to the field of data analysis technology, and in particular to a method, device, electronic device, and storage medium for identifying the risk type of an operation. Background Art

[0002] In existing transactions for financial products, it is necessary to send risk control operation information corresponding to different product operations to the risk control component during the transaction process. The risk control component obtains the risk conclusion corresponding to the operation based on the received operation information and the risk control model of the product.

[0003] However, the risk control requirements for operations of some products in the same business field are basically the same. It is costly to develop a customized risk control model for a single product just because the risk control requirements for some operations of individual products are inconsistent, which is not conducive to subsequent expansion and improving risk control efficiency. Summary of the Invention

[0004] The present application provides a method, device, electronic device, and storage medium for identifying the risk type of an operation, which are used to identify the risk type of an operation.

[0005] In a first aspect, the present application provides a method for identifying a risk type of an operation, the method comprising:

[0006] Receiving operation information sent by the terminal, wherein the operation information includes first identification information of the client performing the operation and second identification information of the operated object;

[0007] According to the pre-stored risk type of each object of each customer, a target risk type of the operated object of the second identification information of the customer of the first identification information is determined, and the target risk type is sent to the terminal of the customer of the first identification information for display.

[0008] In a possible implementation, sending the target risk type to a terminal of the client of the first identification information for display includes:

[0009] If the target risk type is a risk type requiring authorization, the risk type requiring authorization and information required for customer authorization are sent to a terminal of the customer of the first identification information for display.

[0010] In a possible implementation, determining, based on the pre-stored risk type of each object of each customer, the target risk type of the operated object of the second identification information of the customer of the first identification information includes:

[0011] According to the pre-saved correspondence between objects and object types, the target object type of the object of the second identification is determined; according to the pre-saved whitelist customer set corresponding to each object type, it is determined whether the whitelist customer set corresponding to the target object type contains the customer with the first identification information; if not, it is determined that the target risk type of the operated object of the second identification information of the customer with the first identification information is a risk type requiring authorization.

[0012] In a possible implementation, determining, based on a pre-stored whitelist customer set corresponding to each object type, whether the whitelist customer set corresponding to the target object type includes the customer with the first identification information includes:

[0013] According to the pre-stored correspondence between object types and customer types, the target customer type corresponding to the target object type is determined; and it is determined whether the pre-stored whitelist customer set corresponding to the target customer type includes the customer with the first identification information.

[0014] In a possible implementation manner, if the whitelist customer set includes the customer with the first identification information, the method further includes:

[0015] Send the first identification information of the customer to the bank server; receive the status of the customer of the first identification information sent by the bank server, and determine the target risk type of the operated object of the second identification information of the customer of the first identification information based on the customer status and the pre-saved correspondence between the customer status and the risk type.

[0016] In a possible implementation, determining, based on the pre-stored risk type of each object of each customer, the target risk type of the operated object of the second identification information of the customer of the first identification information includes:

[0017] Determine whether the pre-saved set of exempted customers contains the customer with the first identification, and determine whether the pre-saved set of exempted objects contains the operated object with the second identification; if any judgment result is yes, determine that the target risk type of the operated object with the second identification information of the customer with the first identification information is the exempted risk type.

[0018] In a second aspect, the present application provides a device for identifying a risk type of an operation, the device comprising:

[0019] A receiving module, configured to receive operation information sent by a terminal, wherein the operation information includes first identification information of a client performing an operation and second identification information of an object being operated;

[0020] A determination module, configured to determine a target risk type of an operated object of the second identification information of the customer of the first identification information based on a pre-stored risk type of each object of each customer;

[0021] A sending module is used to send the target risk type to a terminal of the customer of the first identification information for display.

[0022] In a possible implementation, the sending module is specifically configured to send the authorization-required risk type and information required for customer authorization to a terminal of the customer of the first identification information for display if the target risk type is an authorization-required risk type.

[0023] In a possible implementation, the determination module is specifically used to determine the target object type of the object of the second identification based on a pre-saved correspondence between objects and object types; determine whether the whitelist customer set corresponding to the target object type includes the customer with the first identification information based on a pre-saved whitelist customer set corresponding to each object type; if not, determine that the target risk type of the operated object of the second identification information of the customer with the first identification information is a risk type requiring authorization.

[0024] In a possible implementation, the determination module is specifically used to determine the target customer type corresponding to the target object type based on a pre-saved correspondence between the object type and the customer type; and to determine whether the pre-saved whitelist customer set corresponding to the target customer type includes the customer with the first identification information.

[0025] In a possible embodiment, the determination module is also used to send the first identification information of the customer to a bank server; receive the status of the customer of the first identification information sent by the bank server, and determine the target risk type of the operated object of the second identification information of the customer of the first identification information based on the status of the customer and the pre-saved correspondence between the status of the customer and the risk type.

[0026] In one possible implementation, the determination module is specifically used to determine whether the pre-saved set of exempted customers includes the customer with the first identification, and to determine whether the pre-saved set of exempted objects includes the operated object with the second identification; if any judgment result is yes, it is determined that the target risk type of the operated object with the second identification information of the customer with the first identification information is the exempted risk type.

[0027] In a third aspect, the present application provides an electronic device comprising at least a processor and a memory, wherein the processor is configured to implement the steps of any of the above-described methods for identifying the risk type of an operation when executing a computer program stored in the memory.

[0028] In a fourth aspect, the present application provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps of any of the above-described methods for identifying the risk type of an operation.

[0029] In a fifth aspect, the present application provides a computer program product, comprising: a computer program code, which, when executed on a computer, enables the computer to execute the steps of any of the above-described methods for identifying the risk type of an operation.

[0030] Since in an embodiment of the present application, the server receives operation information sent by the terminal, the operation information includes the first identification information of the customer performing the operation and the second identification information of the operated object; according to the risk type of each object of each customer saved in advance, the target risk type of the operated object of the second identification information of the first identification information is determined, and the target risk type is sent to the terminal of the customer of the first identification information for display, so that the risk type of the operation information can be identified, and there is no need to customize the development of a risk management model for a single product, which is conducive to later expansion and improving the efficiency of risk management. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] In order to more clearly illustrate the implementation methods in the embodiments of the present application or related technologies, the following is a brief introduction to the drawings required for use in the embodiments or related technology descriptions. Obviously, the drawings described below are some embodiments of the present application. For ordinary technicians in this field, other drawings can also be obtained based on these drawings.

[0032] Figure 1 This is one of the schematic diagrams of a process for identifying the risk type of an operation provided in an embodiment of the present application;

[0033] Figure 2 This is a second schematic diagram of a process for identifying the risk type of an operation provided in an embodiment of the present application;

[0034] Figure 3 A schematic diagram of a device structure for risk types of a specific operation provided in an embodiment of the present application;

[0035] Figure 4 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0036] To make the purpose, technical solutions, and advantages of this application more clear, this application will be further described in detail below with reference to the accompanying drawings. Obviously, the embodiments described in this application are only some of the embodiments of this application, not all of them. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0037] It should be noted that the brief descriptions of terms in this application are only for the purpose of facilitating the understanding of the embodiments described below, and are not intended to limit the embodiments of this application. Unless otherwise specified, these terms should be understood according to their ordinary and usual meanings.

[0038] In the specification and claims of this application and the accompanying drawings, the terms "first," "second," "third," etc. are used to distinguish similar or similar objects or entities, and are not necessarily intended to limit a particular order or sequence, unless otherwise noted. It should be understood that the terms used in this manner are interchangeable under appropriate circumstances.

[0039] The terms "comprise," "include," and "have," and any variations thereof, are intended to cover but not exclude inclusion; for example, a product or device comprising a list of components is not necessarily limited to all the components expressly listed but may include other components not expressly listed or inherent to such product or device.

[0040] The term "module" refers to any known or later developed hardware, software, firmware, artificial intelligence, fuzzy logic, or combination of hardware and / or software code that is capable of performing the functionality associated with that element.

[0041] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some or all of the technical features therein. These modifications or replacements do not deviate the essence of the corresponding technical solutions from the scope of the technical solutions of the embodiments of the present application.

[0042] In order to identify the risk type of an operation, the present application provides a method, apparatus, electronic device, and storage medium for identifying the risk type of an operation.

[0043] In an embodiment of the present application, the method includes: receiving operation information sent by a terminal, wherein the operation information includes first identification information of the customer performing the operation and second identification information of the operated object; determining the target risk type of the operated object of the second identification information of the customer of the first identification information based on the risk type of each object of each customer saved in advance, and sending the target risk type to the terminal of the customer of the first identification information for display.

[0044] All implementation methods of this application comply with the relevant provisions of national laws and regulations regarding the acquisition, storage, use, and processing of data.

[0045] Example 1:

[0046] Figure 1 This is one of the process diagrams for identifying the risk type of an operation provided in an embodiment of the present application, such as Figure 1 As shown, the process includes:

[0047] S101: Receive operation information sent by a terminal, where the operation information includes first identification information of a client performing an operation and second identification information of an operated object.

[0048] The method for identifying the risk type of an operation provided in an embodiment of the present application is applied to an electronic device, which may be a PC, mobile terminal, server, or other device in a financial market middle station responsible for financial transaction risk control and management. The following description will be made using the electronic device as a server in a financial market middle station as an example. For simplicity, the following description will be made using a server.

[0049] Financial product transactions begin with a customer performing an operation in a terminal's financial market application, generating operation information. The terminal then sends this information to a server. The server receives the operation information and identifies the risk type of the operation. This operation information includes, but is not limited to, first identification information of the customer performing the operation and second identification information of the entity being operated. The first identification information of the customer can be information uniquely identifying the customer, such as their name or number; the second identification information of the entity being operated can be information uniquely identifying the entity, such as their name or number.

[0050] S102: Determine a target risk type of the operated object of the second identification information of the customer of the first identification information based on the pre-stored risk type of each object of each customer, and send the target risk type to a terminal of the customer of the first identification information for display.

[0051] In this embodiment of the present application, in order to identify the risk type of operation information, the risk type of each object of each customer is pre-stored. After receiving the operation information sent by the terminal, the server determines the target risk type of the operated object of the second identification information of the customer with the first identification information based on the pre-stored risk type of each object of each customer, and sends the target risk type to the terminal of the customer with the first identification information for display.

[0052] Specifically, the pre-saved risk type of each object of each customer includes but is not limited to the authorization-required risk type and the inspection-exempt risk type. The authorization-required risk type indicates that the operation is high-risk and requires the customer's authorization to complete the operation; the inspection-exempt risk type indicates that the operation is low-risk and does not require the customer's authorization and can be directly passed.

[0053] In an embodiment of the present application, the server receives operation information sent by the terminal, which operation information includes first identification information of the customer performing the operation and second identification information of the operated object; based on the risk type of each object of each customer saved in advance, the target risk type of the operated object of the second identification information of the first identification information is determined, and the target risk type is sent to the terminal of the customer of the first identification information for display, so that the risk type of the operation information can be identified, and there is no need to customize the development of a risk management model for a single product, which is conducive to later expansion and improving the efficiency of risk management.

[0054] To facilitate smooth completion of the operation, based on the above embodiment, in the embodiment of the present application, sending the target risk type to the terminal of the client of the first identification information for display includes:

[0055] If the target risk type is a risk type requiring authorization, the risk type requiring authorization and information required for customer authorization are sent to a terminal of the customer of the first identification information for display.

[0056] In an embodiment of the present application, if the risk type of an operation is identified as requiring authorization, the customer's authorization is required to complete the operation. To ensure the smooth completion of the operation, the risk type requiring authorization and the information required for customer authorization are sent to the terminal of the customer with the first identification information for display. Specifically, an input box for the risk type requiring authorization and customer authorization information or an authorization button can be displayed on the customer's terminal. The customer can authorize by entering the corresponding authorization information or clicking the authorization button. This ensures that operations requiring authorization for risk types can be authorized and completed in a timely manner.

[0057] Example 2:

[0058] To facilitate identification of risk types for operations on similar objects, based on the above embodiments, in an embodiment of the present application, determining the target risk type of the operated object of the second identification information of the first identification information based on the pre-stored risk type of each object of each customer includes:

[0059] determining the target object type of the object of the second identification according to a pre-stored correspondence between objects and object types;

[0060] Determining, based on a pre-stored whitelist customer set corresponding to each object type, whether the whitelist customer set corresponding to the target object type includes the customer with the first identification information;

[0061] If not, it is determined that the target risk type of the operated object of the second identification information of the customer of the first identification information is a risk type requiring authorization.

[0062] In this embodiment of the present application, to facilitate the identification of risk types for operations on similar objects, a whitelist client set corresponding to each object type is pre-stored. Operations on similar objects are operations on the same object type as the operated object, and the whitelist client set corresponding to an object type is the set of clients that can perform operations on the corresponding object type.

[0063] The whitelist customer set corresponding to each object type may contain identification information of the same customer, but is generally not exactly the same.

[0064] Based on the pre-saved whitelist customer set corresponding to each object type, it can be determined whether the whitelist customer set corresponding to the target object type contains the customer with the first identification information. If not, it means that the customer with the first identification information cannot directly operate the operated object with the second identification information, and needs to obtain authorization from the customer with the first identification information to complete the operation. Therefore, it is determined that the target risk type of the operated object with the second identification information of the customer with the first identification information is an authorization-required risk type.

[0065] In one possible implementation, according to whether the object meets the non-credit rule, the object type may include the following categories: if the object meets the non-credit rule, the object type is non-credit business or only low-risk business; if the object does not meet the non-credit rule, the object type is all business. Each object type corresponds to a whitelist customer set. Therefore, according to the different object types, the whitelist customer set also includes multiple types, specifically: if the object type is all business, the corresponding whitelist customer set is the all-business whitelist customer set; if the object type is non-credit business or only low-risk business, the corresponding whitelist customer set is the non-credit or only low-risk business whitelist customer set. Among them, the all-business whitelist customer set includes customers of businesses that occupy the credit line, customers of businesses that only occupy the low credit risk line, and customers of businesses that do not occupy the credit line. That is to say, if the customer is in the all-business customer set, operations can be performed on objects of all object types. The whitelist customer set for those who do not occupy credit or those who occupy low-risk businesses includes customers who occupy only low-credit-risk businesses or customers who do not occupy credit lines. In other words, if a customer is in the whitelist customer set for those who do not occupy credit or those who occupy only low-risk businesses, operations can only be performed on objects of the type that do not occupy credit or those that occupy only low-risk businesses.

[0066] For example, based on a pre-stored correspondence between objects and object types, it is determined that the target object type of the object with the second identification is a full-service object type. Then, based on the full-service customer set corresponding to the full-service object type, it is determined whether the full-service customer set includes the customer with the first identification information. If not, the customer with the first identification information cannot perform operations on the full-service object type. The target risk type of the operated object with the second identification information of the customer with the first identification information is determined to be an authorization-required risk type. This means that the operation requires the customer's authorization to complete.

[0067] In an embodiment of the present application, based on a pre-saved set of whitelist customers corresponding to each object type, the target risk type of the operated object of the second identification information of the customer with the first identification information is determined to be a risk type requiring authorization, thereby facilitating the identification of risk types for operations on similar objects.

[0068] In order to identify the risk type of operations of similar customers for similar operations, based on the above embodiments, in an embodiment of the present application, determining whether the whitelist customer set corresponding to the target object type contains the customer with the first identification information based on the pre-stored whitelist customer set corresponding to each object type includes:

[0069] Determining the target customer category corresponding to the target object category based on the pre-stored correspondence between the object category and the customer category;

[0070] And determine whether the customer with the first identification information is included in the pre-stored whitelist customer set corresponding to the target customer type.

[0071] In this embodiment of the present application, in order to identify the risk types of operations performed by similar customers on similar objects, a pre-stored correspondence between object types and customer types, as well as a whitelist of customers corresponding to each customer type, is stored. Based on this pre-stored correspondence between object types and customer types, the target customer type corresponding to the target object type can be determined. The whitelist of customers corresponding to each customer type may contain the same customer identification information, but generally, it is not completely identical.

[0072] According to the pre-stored whitelist customer set corresponding to each customer type, it can be determined whether the whitelist customer set corresponding to the target customer type contains the customer with the first identification information.

[0073] Specifically, customers can be divided into at least two types, for example, legal person customers and non-legal person customers, and the customer identification information is the customer number. If the customer is a legal person customer, the customer number is also associated with the legal person number, and the numbers of multiple legal person customers may be associated with the same legal person number.

[0074] In an embodiment of the present application, in order to identify the risks of operations on similar customers of similar objects, a correspondence between object types and customer types is pre-saved. If the risk of the object type is high, the corresponding target customer type is the customer type that can operate on high-risk objects; if the risk of the object type is low, the corresponding target customer type is all customer types. Based on the pre-saved correspondence between the object type and the customer type, the target customer type corresponding to the target object type of the operated object of the second identification information can be determined. In a possible implementation, the target object type may include the following categories: if the object meets the non-credit rule, the target object type is non-credit business or only low-risk business; if the object does not meet the non-credit rule, the target object type is all business. Among them, the risk of the target object type "non-credit business or only low-risk business" is low, and the corresponding target customer type is all customer types, that is, corporate customers and non-corporate customers; the risk of the target object type "all business" is high, and the corresponding target customer type is corporate customers.

[0075] Each customer type has multiple whitelist customer sets. If the target customer type is a corporate customer, the corresponding whitelist customer sets are the full-service whitelist customer set and the whitelist customer set for no credit and only low-risk business. If the target customer type is a non-corporate customer, the corresponding whitelist customer sets are the whitelist customer set for no credit and only low-risk business.

[0076] Determine whether the whitelist customer set corresponding to the pre-saved target customer type contains the customer with the first identification information, that is, determine whether the full-business whitelist customer set and the whitelist customer set that does not occupy credit and only occupies low-risk business corresponding to the legal person customer contain the customer with the first identification information; or whether the whitelist customer set that does not occupy credit and only occupies low-risk business corresponding to the non-legal person customer contains the non-legal person customer with the first identification information.

[0077] Specifically, it is possible to determine whether the legal person number associated with the legal person customer with the first identification information is included in the full-service whitelist customer set and the whitelist customer set that does not account for credit and only accounts for low-risk business corresponding to the legal person customer; or to determine whether the first identification information, that is, the number of the non-legal person customer, is included in the whitelist customer set that does not account for credit and only accounts for low-risk business corresponding to the non-legal person customer. If not, it means that the customer with the first identification information cannot directly complete the operation and requires authorization from the customer with the first identification information. In this case, the target risk type of the object being operated on for the second identification information of the customer with the first identification information is determined to be a risk type requiring authorization.

[0078] Example 3:

[0079] In order to more accurately identify the risk types of operations on similar objects or similar customers, based on the above embodiments, in an embodiment of the present application, if the whitelist customer set includes customers with the first identification information, the method further includes:

[0080] Sending the first identification information of the customer to the bank server;

[0081] Receive the status of the customer of the first identification information sent by the bank server, and determine the target risk type of the operated object of the second identification information of the customer of the first identification information based on the customer status and the pre-saved correspondence between the customer status and the risk type.

[0082] In an embodiment of the present application, in order to more accurately identify the risk types of operations on similar objects or similar customers, it is also possible to interact with the bank server to determine the status of the customer of the first identification information, and determine the target risk type of the operated object of the second identification information of the customer of the first identification information based on the pre-saved correspondence between the customer's status and the risk type.

[0083] Specifically, the server sends the client's first identification information to the bank server, receives the client's status sent by the bank server, and determines the target risk type of the object being operated on for the client's second identification information, based on a pre-stored correspondence between the client's status and the risk type. Client statuses include, but are not limited to, normal, concern, and prohibited. Risk types include, but are not limited to, approved risk type, authorization-required risk type, and prohibited risk type. A "normal" status indicates that the client's risk is low, and the corresponding risk type is a "passed risk type," meaning the operation can be completed directly without the client's authorization. A "concern" status indicates that the client's risk type is high and requires special attention. The corresponding risk type is an "authorization-required risk type," meaning the operation requires the client's authorization. A "prohibited" status indicates that the client's risk type is extremely high and the operation is prohibited. The corresponding risk type is either an "authorization-required risk type" or a "prohibited risk type," meaning the operation is either directly prohibited or can be completed with the client's authorization.

[0084] The correspondence between the customer's status and risk type can be freely set and saved according to actual needs, and this application does not limit this.

[0085] In the embodiment of the present application, the target risk type of the operated object of the second identification information of the customer of the first identification information is determined based on the interaction with the bank server, which further ensures the accuracy of risk type identification.

[0086] In one possible implementation, after receiving the status of the customer with the first identification information from the bank server, the status of the customer with the first identification information may be added to the whitelist of customers to which the customer with the first identification information belongs. Specifically, the whitelist includes the customer's identification information and status, where the customer's identification information is the customer's ID or the legal entity ID corresponding to the customer, and the status includes, but is not limited to, normal, concern, and prohibited.

[0087] If the whitelist customer set includes a customer with the first identification information, the target risk type of the operated object with the second identification information of the customer with the first identification information is determined directly based on the status of the customer with the first identification information and the pre-saved correspondence between the customer status and the risk type.

[0088] Example 4:

[0089] To improve the efficiency of risk type identification, based on the above embodiments, in an embodiment of the present application, determining the target risk type of the operated object of the second identification information of the customer of the first identification information based on the pre-stored risk type of each object of each customer includes:

[0090] Determine whether the pre-saved set of exempted customers contains the customer with the first identification, and determine whether the pre-saved set of exempted objects contains the operated object with the second identification; if any judgment result is yes, determine that the target risk type of the operated object with the second identification information of the customer with the first identification information is the exempted risk type.

[0091] In this embodiment of the present application, in order to improve the efficiency of risk type identification, a set of exempted customers and a set of exempted objects are pre-stored. The exempted customers set is a set of customers whose risk types are extremely low and do not require further risk type identification, and the exempted objects set is a set of objects whose risk types are extremely low and do not require further risk type identification.

[0092] Specifically, based on the first identification information of the customer and the second identification information of the operated object contained in the operation information, it is possible to determine whether the customer with the first identification is included in a pre-stored set of exempt customers, and whether the operated object with the second identification is included in a pre-stored set of exempt objects. If either determination is yes, the target risk type of the operated object with the second identification information of the customer with the first identification information is determined to be an exempt risk type, and no further risk type identification is required.

[0093] In an embodiment of the present application, based on a pre-saved set of exempted customers and a set of exempted objects, the target risk type of the operated object of the second identification information of the customer with the first identification information is determined to be an exempted risk type, thereby improving the efficiency of identifying risk types.

[0094] In a possible implementation, the above embodiments may be combined to identify the risk type of an operation, which is described below with a specific example.

[0095] Figure 2 This is a second schematic diagram of a process for identifying the risk type of an operation provided in an embodiment of the present application; Figure 2 As shown, the process includes the following steps:

[0096] S201: Receive operation information sent by a terminal, where the operation information includes first identification information of a client performing an operation and second identification information of an operated object.

[0097] S202: Determine whether a pre-stored set of exempted customers contains the customer with the first identifier, and determine whether a pre-stored set of exempted objects contains the operated object with the second identifier.

[0098] S203a: If any judgment result is yes, determine that the target risk type of the operated object of the second identification information of the customer of the first identification information is an inspection-exempt risk type.

[0099] S203b: If the judgment results are all negative, then the target object category of the object of the second identification is determined according to the pre-stored correspondence between objects and object categories.

[0100] S204: Determine the target customer type corresponding to the target object type based on the pre-stored correspondence between the object type and the customer type; and determine whether the pre-stored whitelist customer set corresponding to the target customer type includes the customer with the first identification information.

[0101] S205a: If not, determine that the target risk type of the operated object of the second identification information of the customer of the first identification information is a risk type requiring authorization.

[0102] S205b: If the whitelist customer set includes the customer with the first identification information, send the first identification information of the customer to the bank server; receive the status of the customer with the first identification information sent by the bank server, and determine the target risk type of the operated object of the second identification information of the customer with the first identification information based on the status of the customer and the pre-saved correspondence between the status of the customer and the risk type.

[0103] For specific implementations, please refer to the above embodiments, and the repeated parts will not be repeated here.

[0104] Example 5:

[0105] Based on the same technical concept, the present application also provides a device for identifying the risk type of an operation. Figure 3 A schematic diagram of a device structure for identifying risk types of operations provided in an embodiment of the present application is shown as follows: Figure 3 As shown, the device includes:

[0106] Receiving module 301, configured to receive operation information sent by a terminal, wherein the operation information includes first identification information of a client performing an operation and second identification information of an operated object;

[0107] A determination module 302 is configured to determine a target risk type of an object to be operated on for the second identification information of the customer of the first identification information based on a pre-stored risk type of each object of each customer;

[0108] The sending module 303 is configured to send the target risk type to a terminal of the client of the first identification information for display.

[0109] In a possible implementation, the sending module 303 is specifically configured to send the authorization-required risk type and information required for customer authorization to a terminal of the customer of the first identification information for display if the target risk type is an authorization-required risk type.

[0110] In a possible implementation, the determination module 302 is specifically used to determine the target object type of the object of the second identification based on a pre-saved correspondence between objects and object types; determine whether the whitelist customer set corresponding to the target object type includes the customer with the first identification information based on a pre-saved whitelist customer set corresponding to each object type; if not, determine that the target risk type of the operated object of the second identification information of the customer with the first identification information is a risk type requiring authorization.

[0111] In a possible implementation, the determination module 302 is specifically used to determine the target customer type corresponding to the target object type based on a pre-saved correspondence between the object type and the customer type; and to determine whether the pre-saved whitelist customer set corresponding to the target customer type contains the customer with the first identification information.

[0112] In one possible implementation, the determination module 302 is also used to send the first identification information of the customer to a bank server; receive the status of the customer of the first identification information sent by the bank server, and determine the target risk type of the operated object of the second identification information of the customer of the first identification information based on the status of the customer and the pre-saved correspondence between the status of the customer and the risk type.

[0113] In one possible implementation, the determination module 302 is specifically used to determine whether the pre-saved set of exempted customers includes the customer with the first identification, and to determine whether the pre-saved set of exempted objects includes the operated object with the second identification; if any judgment result is yes, it is determined that the target risk type of the operated object with the second identification information of the customer with the first identification information is the exempted risk type.

[0114] Example 6:

[0115] Based on the same technical concept, the present application also provides an electronic device, Figure 4 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application is shown in FIG. Figure 4 As shown, the electronic device includes: a processor 41, a communication interface 42, a memory 43 and a communication bus 44, wherein the processor 41, the communication interface 42, and the memory 43 communicate with each other through the communication bus 44;

[0116] The memory 43 stores a computer program. When the program is executed by the processor 41, the processor 41 performs the following steps:

[0117] Receiving operation information sent by the terminal, wherein the operation information includes first identification information of the client performing the operation and second identification information of the operated object;

[0118] According to the pre-stored risk type of each object of each customer, a target risk type of the operated object of the second identification information of the customer of the first identification information is determined, and the target risk type is sent to the terminal of the customer of the first identification information for display.

[0119] In a possible implementation, the processor 41 is further configured to:

[0120] If the target risk type is a risk type requiring authorization, the risk type requiring authorization and information required for customer authorization are sent to a terminal of the customer of the first identification information for display.

[0121] In a possible implementation, the processor 41 is specifically configured to:

[0122] According to the pre-saved correspondence between objects and object types, the target object type of the object of the second identification is determined; according to the pre-saved whitelist customer set corresponding to each object type, it is determined whether the whitelist customer set corresponding to the target object type contains the customer with the first identification information; if not, it is determined that the target risk type of the operated object of the second identification information of the customer with the first identification information is a risk type requiring authorization.

[0123] In a possible implementation, the processor 41 is specifically configured to:

[0124] According to the pre-stored correspondence between object types and customer types, the target customer type corresponding to the target object type is determined; and it is determined whether the pre-stored whitelist customer set corresponding to the target customer type includes the customer with the first identification information.

[0125] In a possible implementation, the processor 41 is further configured to:

[0126] Send the first identification information of the customer to the bank server; receive the status of the customer of the first identification information sent by the bank server, and determine the target risk type of the operated object of the second identification information of the customer of the first identification information based on the customer status and the pre-saved correspondence between the customer status and the risk type.

[0127] In a possible implementation, the processor 41 is specifically configured to:

[0128] Determine whether the pre-saved set of exempted customers contains the customer with the first identification, and determine whether the pre-saved set of exempted objects contains the operated object with the second identification; if any judgment result is yes, determine that the target risk type of the operated object with the second identification information of the customer with the first identification information is the exempted risk type.

[0129] Since the principle of the electronic device for solving the problem is similar to the method for identifying the risk type of an operation, the implementation of the electronic device can refer to the implementation of the method, and the repeated parts will not be repeated.

[0130] The communication bus mentioned in the electronic device mentioned above may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. This communication bus can be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is used in the figure, but this does not mean that there is only one bus or only one type of bus.

[0131] The communication interface 42 is used for communication between the electronic device and other devices.

[0132] The memory may include random access memory (RAM) or non-volatile memory (NVM), such as at least one disk memory. Alternatively, the memory may be at least one storage device located away from the processor.

[0133] The above-mentioned processor can be a general-purpose processor, including a central processing unit, a network processor (NP), etc.; it can also be a digital signal processing processor (DSP), an application-specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, etc.

[0134] Example 7:

[0135] Based on the same technical concept, an embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program executable by an electronic device. When the program is executed on the electronic device, the electronic device implements the following steps:

[0136] Receiving operation information sent by the terminal, wherein the operation information includes first identification information of the client performing the operation and second identification information of the operated object;

[0137] According to the pre-stored risk type of each object of each customer, a target risk type of the operated object of the second identification information of the customer of the first identification information is determined, and the target risk type is sent to the terminal of the customer of the first identification information for display.

[0138] In a possible implementation, sending the target risk type to a terminal of the client of the first identification information for display includes:

[0139] If the target risk type is a risk type requiring authorization, the risk type requiring authorization and information required for customer authorization are sent to a terminal of the customer of the first identification information for display.

[0140] In a possible implementation, determining, based on the pre-stored risk type of each object of each customer, the target risk type of the operated object of the second identification information of the customer of the first identification information includes:

[0141] According to the pre-saved correspondence between objects and object types, the target object type of the object of the second identification is determined; according to the pre-saved whitelist customer set corresponding to each object type, it is determined whether the whitelist customer set corresponding to the target object type contains the customer with the first identification information; if not, it is determined that the target risk type of the operated object of the second identification information of the customer with the first identification information is a risk type requiring authorization.

[0142] In a possible implementation, determining, based on a pre-stored whitelist customer set corresponding to each object type, whether the whitelist customer set corresponding to the target object type includes the customer with the first identification information includes:

[0143] According to the pre-stored correspondence between object types and customer types, the target customer type corresponding to the target object type is determined; and it is determined whether the pre-stored whitelist customer set corresponding to the target customer type includes the customer with the first identification information.

[0144] In a possible implementation manner, if the whitelist customer set includes the customer with the first identification information, the method further includes:

[0145] Send the first identification information of the customer to the bank server; receive the status of the customer of the first identification information sent by the bank server, and determine the target risk type of the operated object of the second identification information of the customer of the first identification information based on the customer status and the pre-saved correspondence between the customer status and the risk type.

[0146] In a possible implementation, determining, based on the pre-stored risk type of each object of each customer, the target risk type of the operated object of the second identification information of the customer of the first identification information includes:

[0147] Determine whether the pre-saved set of exempted customers contains the customer with the first identification, and determine whether the pre-saved set of exempted objects contains the operated object with the second identification; if any judgment result is yes, determine that the target risk type of the operated object with the second identification information of the customer with the first identification information is the exempted risk type.

[0148] The above-mentioned computer-readable storage medium can be any available medium or data storage device that can be accessed by the processor in the electronic device, including but not limited to magnetic storage such as floppy disks, hard disks, magnetic tapes, magneto-optical disks (MO), etc., optical storage such as CDs, DVDs, BDs, HVDs, etc., and semiconductor storage such as ROMs, EPROMs, EEPROMs, non-volatile memories (NANDFLASH), solid-state drives (SSDs), etc.

[0149] Example 8:

[0150] Based on the same technical concept, the present application provides a computer program product, which includes: computer program code, which, when running on a computer, enables the computer to implement the above-mentioned method for identifying the risk type of any operation applied to an electronic device.

[0151] The above embodiments may be implemented in whole or in part through software, hardware, firmware, or any combination thereof, and may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions that, when loaded and executed on a computer, fully or partially generate the processes or functions described in the embodiments of the present application.

[0152] Those skilled in the art will appreciate that the embodiments of the present application can be provided as methods, systems, or computer program products. Therefore, the present application can adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application can adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.

[0153] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the present application. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 a process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0154] These computer program instructions may also be stored in a computer readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 a process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.

[0155] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing the instructions executed on the computer or other programmable device for implementing the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0156] Obviously, those skilled in the art may make various changes and modifications to this application without departing from the spirit and scope of this application. Thus, if these modifications and variations of this application fall within the scope of the claims of this application and their equivalents, this application is intended to include these modifications and variations.

Claims

1. A method for identifying the risk type of an operation, characterized in that: The method comprises: Receiving operation information sent by the terminal, wherein the operation information includes first identification information of the client performing the operation and second identification information of the operated object; determining a target risk type of the object being operated on by the second identification information of the customer of the first identification information based on a pre-stored risk type of each object of each customer, and sending the target risk type to a terminal of the customer of the first identification information for display; The step of determining the target risk type of the operated object of the second identification information of the customer of the first identification information based on the pre-stored risk type of each object of each customer includes: Determine a target risk type of an object to be operated on by the second identification information of a customer of the first identification information according to at least one of the following; the target risk type includes an inspection-exempt risk type and an authorization-required risk type; the at least one of the following includes: whether the whitelist customer set corresponding to the target object type of the operated object of the second identification information includes the customer of the first identification information; Whether the pre-stored set of exempted customers contains the customer with the first identification information; Whether the pre-stored set of exempted objects contains the operated object with the second identification information.

2. The method according to claim 1, characterized in that The sending the target risk type to a terminal of the client of the first identification information for display includes: If the target risk type is a risk type requiring authorization, the risk type requiring authorization and information required for customer authorization are sent to a terminal of the customer of the first identification information for display.

3. The method according to claim 1, characterized in that The determining, based on the pre-stored risk type of each object of each customer, the target risk type of the operated object of the second identification information of the customer of the first identification information includes: determining the target object type of the operated object of the second identification information according to a pre-stored correspondence between objects and object types; Determining, based on a pre-stored whitelist customer set corresponding to each object type, whether the whitelist customer set corresponding to the target object type includes the customer with the first identification information; If not, it is determined that the target risk type of the operated object of the second identification information of the customer of the first identification information is a risk type requiring authorization.

4. The method according to claim 3, characterized in that The determining, based on the pre-stored whitelist customer set corresponding to each object type, whether the whitelist customer set corresponding to the target object type includes the customer with the first identification information includes: Determining the target customer category corresponding to the target object category based on the pre-stored correspondence between the object category and the customer category; And determine whether the customer with the first identification information is included in the pre-stored whitelist customer set corresponding to the target customer type.

5. The method according to claim 3 or 4, characterized in that If the whitelist client set includes the client with the first identification information, the method further includes: Sending the first identification information of the customer to the bank server; Receive the status of the customer of the first identification information sent by the bank server, and determine the target risk type of the operated object of the second identification information of the customer of the first identification information based on the customer status and the pre-saved correspondence between the customer status and the risk type.

6. The method according to claim 1, characterized in that The determining, based on the pre-stored risk type of each object of each customer, the target risk type of the operated object of the second identification information of the customer of the first identification information includes: Determine whether the pre-saved set of exempted customers includes the customer with the first identification information, and determine whether the pre-saved set of exempted objects includes the operated object with the second identification information; if any judgment result is yes, determine that the target risk type of the operated object with the second identification information of the customer with the first identification information is the exempted risk type.

7. A device for identifying the risk type of an operation, characterized in that: The device comprises: A receiving module, configured to receive operation information sent by a terminal, wherein the operation information includes first identification information of a client performing an operation and second identification information of an object being operated; A determination module, configured to determine a target risk type of an operated object of the second identification information of the customer of the first identification information based on a pre-stored risk type of each object of each customer; The determining module is specifically configured to determine a target risk type of an object to be operated on by the second identification information of a customer of the first identification information according to at least one of the following: the target risk type includes an inspection-exempt risk type and an authorization-required risk type; the at least one item includes: whether the whitelist customer set corresponding to the target object type of the operated object of the second identification information includes the customer of the first identification information; According to whether the pre-stored set of exempted customers contains the customer with the first identification information; whether the pre-stored set of exempted objects contains the operated object with the second identification information; A sending module is used to send the target risk type to a terminal of the customer of the first identification information for display.

8. The device according to claim 7, characterized in that The sending module is specifically configured to send the risk type requiring authorization and information required for customer authorization to a terminal of the customer of the first identification information for display if the target risk type is a risk type requiring authorization.

9. The device according to claim 7, characterized in that The determination module is specifically used to determine the target object type of the operated object of the second identification information based on the pre-saved correspondence between objects and object types; determine whether the whitelist customer set corresponding to the target object type contains the customer of the first identification information based on the pre-saved whitelist customer set corresponding to each object type; if not, determine that the target risk type of the operated object of the second identification information of the customer of the first identification information is a risk type requiring authorization.

10. The device according to claim 9, characterized in that The determination module is specifically configured to determine the target customer type corresponding to the target object type based on a pre-stored correspondence between object types and customer types; and determine whether the pre-stored whitelist customer set corresponding to the target customer type includes the customer with the first identification information.

11. The device according to claim 9 or 10, characterized in that The determination module is also used to send the first identification information of the customer to a bank server; receive the status of the customer of the first identification information sent by the bank server, and determine the target risk type of the operated object of the second identification information of the customer of the first identification information based on the customer status and the pre-saved correspondence between the customer status and the risk type.

12. The device according to claim 7, characterized in that The determination module is specifically used to determine whether the pre-saved set of exempted customers includes the customer with the first identification information, and to determine whether the pre-saved set of exempted objects includes the operated object with the second identification information; if any judgment result is yes, it is determined that the target risk type of the operated object with the second identification information of the customer with the first identification information is the exempted risk type.

13. An electronic device, characterized in that: The electronic device comprises at least a processor and a memory, and the processor is configured to implement the steps of the method for identifying the risk type of an operation according to any one of claims 1 to 6 when executing a computer program stored in the memory.

14. A computer-readable storage medium, characterized in that It stores a computer program, which, when executed by a processor, implements the steps of the method for identifying the risk type of an operation according to any one of claims 1 to 6.

15. A computer program product, characterized in that The computer program product comprises: a computer program code, which, when executed on a computer, enables the computer to execute the steps of the method for identifying the risk type of an operation according to any one of claims 1 to 6.

Images