Risk detection method and device, storage medium and electronic equipment

Abstract

The invention provides a risk detection method and device, a storage medium and electronic equipment, and the method is applied to the technical field of computers, and comprises the steps: detecting that a risk keyword exists in a social software window of a user and a first object, obtaining a social software account of the first object, and obtaining transaction data registration information of the first object in the transaction database based on the social software account, and if the transaction data registration information does not meet the transaction data exchange condition, outputting risk alarm prompt information. According to the method, the object possibly subjected to transaction data exchange can be determined by detecting the risk keyword, the transaction data registration information of the first object is searched and detected in the transaction data registration library, an alarm is given when the exchange condition is not met, prevention and control are carried out before a potential transaction data exchange event occurs, and the transaction data exchange efficiency is improved. And an unsafe transaction data exchange event is avoided.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and more specifically, to a risk detection method, device, storage medium, and electronic device in the field of computer technology. Background Art

[0002] Enterprises and companies often have many transaction data exchange events such as outgoing and incoming transactions. Not only do exchanges occur between different enterprises and companies, but transaction data exchanges also occur within a company. In order to standardize the management of the company's transaction data-related events, dedicated transaction data management personnel are often set up to manage transaction data exchange events. Such personnel are easy targets for criminals such as fraudsters, who will use rhetoric to trick them into exchanging transaction data. Transaction data management personnel need to face a large number of people with different identities and handle a large number of related events at work, making it difficult to verify the identity of each person. Therefore, a risk detection method for transaction data exchange events is needed. Summary of the Invention

[0003] The embodiments of the present application provide a risk detection method, device, storage medium and electronic device. The method can determine the objects where transaction data exchange may occur by detecting risk keywords, and search and detect the transaction data registration information of the first object in the transaction data registration library. When the exchange conditions are not met, an alarm is issued, and prevention and control are carried out before potential transaction data exchange events occur, thereby avoiding the occurrence of unsafe transaction data exchange events.

[0004] In a first aspect, an embodiment of the present application provides a risk detection method, the method comprising:

[0005] Detecting the presence of risky keywords in the social software window between the user and the first object;

[0006] Acquire the social software account of the first subject, and acquire transaction data registration information of the first subject in a transaction database based on the social software account;

[0007] If the transaction data registration information does not meet the transaction data exchange conditions, a risk warning prompt message is output.

[0008] In a second aspect, an embodiment of the present application provides a risk detection device, the device comprising:

[0009] A keyword detection unit, configured to detect the presence of risky keywords in the social software window between the user and the first object;

[0010] a registration information acquisition unit, configured to acquire a social software account of the first subject, and acquire transaction data registration information of the first subject in a transaction database based on the social software account;

[0011] The risk warning unit is used to output risk warning prompt information if the transaction data registration information does not meet the transaction data exchange condition.

[0012] In a third aspect, an embodiment of the present application provides a computer storage medium, wherein the computer storage medium stores a plurality of instructions, wherein the instructions are suitable for being loaded by a processor and executing the above-mentioned method steps.

[0013] In a fourth aspect, an embodiment of the present application provides an electronic device, which may include: a processor and a memory; wherein the memory stores a computer program, and the computer program is suitable for being loaded by the processor and executing the above-mentioned method steps.

[0014] In one or more embodiments of the present application, a method is used to detect the presence of risk keywords in a social software window between a user and a first object, obtain the social software account of the first object, and obtain the transaction data registration information of the first object from a transaction database based on the social software account. If the transaction data registration information does not meet the transaction data exchange conditions, a risk warning prompt message is output. By detecting the risk keywords, the object with which transaction data exchange may occur is determined, and the transaction data registration information of the first object is searched and detected in the transaction data registry. If the exchange conditions are not met, an alarm is issued, and prevention and control measures are taken before potential transaction data exchange events occur, thereby avoiding the occurrence of unsafe transaction data exchange events. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0016] Figure 1 This is an example diagram of a risk detection provided by an embodiment of the present application;

[0017] Figure 2 This is a flow chart of a risk detection method provided in an embodiment of the present application;

[0018] Figure 3 This is a flowchart of a risk keyword detection process provided by an embodiment of the present application;

[0019] Figure 4 This is a flowchart of transaction data registration provided by an embodiment of the present application;

[0020] Figure 5 This is an example diagram of a transaction data registration interface provided in an embodiment of the present application;

[0021] Figure 6 This is a flowchart of a transaction data exchange condition determination process provided by an embodiment of the present application;

[0022] Figure 7 This is a flowchart of a transaction data exchange request generation process provided by an embodiment of the present application;

[0023] Figure 8 This is an example schematic diagram of a floating ball display state provided in an embodiment of the present application;

[0024] Figure 9 This is an example schematic diagram of a floating ball pop-up window provided in an embodiment of the present application;

[0025] Figure 10 This is a schematic diagram of the structure of a risk detection device provided in an embodiment of the present application;

[0026] Figure 11 This is a schematic diagram of the structure of a risk detection device provided in an embodiment of the present application;

[0027] Figure 12 This is a structural diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0028] The following will be combined with the drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are only part of the embodiments of this application, not all of the embodiments. 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.

[0029] During the normal operation of a company or enterprise, many transaction data exchange events will occur. Among them, transaction data can be assets, tradable goods such as goods, or transferable rights such as bonds and stocks. Companies and enterprises can set up transaction data management personnel to manage transaction data exchange events. However, since transaction data management personnel often need to contact many different people in the course of their work, it is difficult for transaction data management personnel to verify the identities of different people by relying solely on their manual memory. This is especially true when criminals steal identities or use false identities to contact transaction data management personnel. For example, fraudsters can pretend to be company management and ask transaction data management personnel to transfer money to the wrong account. It is difficult for transaction data management personnel to identify their identities, which creates security risks for transaction data exchange events and affects the transaction data security of the company or enterprise. In order to improve the security of transaction data exchange events, the embodiment of the present application provides another risk detection device that can assist transaction data management personnel, which can identify potential transaction data exchange event objects and verify their identities. The risk detection method provided in the embodiment of the present application can be implemented by a computer program and can be run on a risk detection device based on the von Neumann system. The computer program can be integrated into an application or run as an independent tool application. The risk detection device can be a terminal device such as a computer, mobile phone or tablet, or a module or application in the terminal device for implementing the risk detection method, or a server that manages all applications corresponding to the risk detection methods.

[0030] Please also see Figure 1 , an example schematic diagram of risk detection is provided for an embodiment of the present application, and the object currently communicating with the user using social software can be determined as the first object. Social software is an application developed based on the Internet platform, which can enable users to communicate and exchange with others conveniently by providing functions such as chatting, sharing, and interacting. The user can be the holder of the current terminal device or the transaction data manager established by the company. The risk detection device can determine the social software window used by the user on the terminal interface of the terminal device, and detect whether there are risk keywords therein. The risk keywords are used to determine whether the first object is a potential transaction data exchange event object, that is, to determine whether a transaction data exchange event may occur between the first object and the user, so the risk keywords can be words related to physical data exchange events, such as "transfer", "remittance", etc. As Figure 1The figure shows a social software window captured by a risk detection device. A first subject may send a message to a user containing the risk keyword "transfer." The risk detection device can then verify the first subject's identity based on the first subject's social software account and transaction database. The transaction database may contain transaction data registration information for numerous subjects. This transaction data registration information is used to verify the subject's identity and transaction data, and may include, for example, the subject's name, device information for the subject's terminal device, information about the subject's organization, the subject's mobile phone number, and the subject's social software account. If there is a problem with the first subject's transaction data registration information, a risk warning can be issued to the user to prevent the user from exchanging transaction data with the first subject, thereby achieving risk control.

[0031] The risk detection method provided in this application is described in detail below with reference to specific embodiments.

[0032] See Figure 2 , provides a flow chart of a risk detection method according to an embodiment of the present application. Figure 2 As shown, the method of the embodiment of the present application may include the following steps S101-S103.

[0033] S101: Detecting the presence of risky keywords in a social software window between a user and a first object.

[0034] Specifically, a social software window between the user and the first object can be determined on the terminal interface of the terminal device. The first object can be the object with which the user is currently communicating using social software. Then, the conversation content between the user and the first object in the social software window is obtained, and whether there are risk keywords in the conversation content can be detected. The risk keywords can be words related to physical data exchange events, such as "transfer", "remittance", etc., which are used to determine whether the first object is a potential transaction data exchange event object.

[0035] S102: Obtain a social software account of the first object, and obtain transaction data registration information of the first object in a transaction database based on the social software account.

[0036] Specifically, the transaction database may contain transaction data registration information for numerous subjects. This transaction data registration information is used to verify the subject's identity and transaction data. For example, it may include the subject's name, device information of the subject's terminal device, information about the subject's organization, the subject's mobile phone number, the subject's social software account, etc. Therefore, the corresponding social software can be determined based on the social software window, and the social software account of the first subject in the social software can be obtained. Based on the social software account, the transaction data registration information of the first subject can be obtained from the transaction data.

[0037] S103: If the transaction data registration information does not meet the transaction data exchange conditions, a risk warning prompt message is output.

[0038] Specifically, the risk detection device can determine whether there is a risk in conducting a transaction data exchange event with the first object based on the transaction data exchange conditions. The transaction data exchange conditions can be the initial settings of the risk detection device, or can be set by the user or relevant staff. The identity of the object of the transaction data exchange event can be restricted at the level of transaction data registration information. For example, restrictions can be placed on the device information of the terminal device used, the unit information of the object, the mobile phone number of the object, or the social software account of the object. If the transaction data registration information of the first object does not meet the transaction data exchange conditions, it is determined that there will be a security risk if a transaction data exchange event occurs with the first object. A risk warning prompt message can be output to prompt the user that a transaction data risk has been detected and that a transaction data exchange event with the first object should be avoided. The risk warning prompt message can be output in the form of a pop-up window. For example, the risk warning prompt message can be "The other party's account is abnormal. Please beware of corporate fraud!"

[0039] In an embodiment of the present application, the presence of a risk keyword is detected in a social software window between a user and a first subject, the social software account of the first subject is obtained, and based on the social software account, the transaction data registration information of the first subject is obtained from a transaction database. If the transaction data registration information does not meet the transaction data exchange conditions, a risk warning prompt message is output. By detecting the risk keyword, the subject with whom transaction data exchange may occur is determined, and the transaction data registration information of the first subject is searched and detected in the transaction data registry. If the exchange conditions are not met, an alarm is issued, and prevention and control measures are taken before a potential transaction data exchange event occurs, thereby avoiding the occurrence of unsafe transaction data exchange events.

[0040] In order to avoid frequent detection of window content causing terminal device freezes and affecting the user's normal work, and to avoid excessive capture of user privacy content, users or relevant staff can pre-set risk detection strategies. The risk detection strategy can be used to instruct the risk detection device on how to perform risk keyword detection. For example, the time and range of risk keyword detection by the risk detection device can be determined.

[0041] See Figure 3 , provides a flow chart of risk keyword detection for the embodiment of this application. Figure 3 As shown, in one or more embodiments of the present application, step S101 may include the following steps S201-S203.

[0042] S201: Determine the social software to be detected based on a pre-set risk detection strategy.

[0043] Specifically, to prevent the risk detection device from detecting irrelevant social software, or even social software used privately by users, the user or relevant staff can specify the social software to be detected in the risk detection strategy. For example, the social software to be detected could be social software frequently used by users in transactional data management. The risk detection device can then determine the social software to be detected based on pre-defined risk detection measures and perform risk keyword detection on the social software to be detected, thus avoiding terminal device lag caused by detecting irrelevant software and excessive capture of users' private content.

[0044] Optionally, the risk detection strategy can not only determine the social software to be detected, that is, determine the scope of social software covered by risk keyword detection, but also determine the time of risk keyword detection. The risk detection device can be applied to the work scenario of transaction data management personnel. When the transaction data management personnel are off work, the company can prohibit the transaction data management personnel from performing transaction data exchange operations, thereby further ensuring the company's transaction data security. Therefore, the risk detection strategy can be set to set the risk detection device to only perform risk keyword detection within a preset time period. The preset time period can be the working hours of the transaction data management personnel. For example, if the working hours of the transaction data management personnel are 8:00-17:00, the preset time period can also be 8:00-17:00. That is, the risk detection device can determine the social software to be detected and the preset time period based on the preset risk detection strategy, thereby performing risk keyword detection on the social software to be detected within the preset time period.

[0045] S202: Capture and process the conversation content between the user and the first object in the social software window of the social software to be detected.

[0046] Specifically, when it is detected that the social software to be detected is started in the terminal device, the social software window of the social software to be detected can be determined on the terminal interface, and the conversation content between the user and the first object in the social software to be detected can be captured and processed, wherein the conversation content may include information sent by the user to the first object, and may also include information sent by the first object to the user.

[0047] Optionally, the conversation content may include text information appearing in the social software window, but existing social software often supports sending pictures. In order to prevent criminals from sending pictures to evade the detection of risk keywords, the risk detection device may also capture the picture information in the social software window, and perform text recognition processing on the picture information to obtain text content, and use the text content as the conversation content in the social software window. Therefore, the conversation content includes not only the text information appearing in the social software window, but also the text content in the picture information appearing in the social software window.

[0048] S203: Detecting the presence of risky keywords in the conversation content.

[0049] Specifically, the risk keyword can be an initial setting of the risk detection device, or can be set by the user or relevant staff. The risk detection device can detect whether there is a risk keyword in the conversation content. If it exists, it indicates that the identity of the first object is abnormal and the user should not conduct transaction data exchange events with the first object.

[0050] Optionally, the risk detection device may be configured to detect a risk keyword lexicon, which stores multiple risk keywords. The risk keyword lexicon then matches the conversation content against the risk keyword lexicon. If a word from the risk keyword lexicon is present in the conversation content, it indicates that the risk keyword has been detected. For example, a brute force matching algorithm may be employed, whereby the conversation content is compared against the risk keywords in the risk keyword lexicon, one by one, starting from the first character of the conversation content. If a mismatch is found, the comparison position in the text is shifted back one position, and the comparison continues until a matching risk keyword is found or the entire conversation content is traversed.

[0051] Optionally, the risk detection device can also use a large language model to detect whether there are risk keywords in the conversation content. The risk keyword vocabulary and the conversation content can be input into the large language model. The large language model can match the conversation content with the risk keywords in the risk keyword vocabulary, thereby detecting whether there are risk keywords in the conversation content.

[0052] In this embodiment, based on a pre-defined risk detection strategy, social software to be detected is identified. The conversation content between a user and a first subject in the social software window within the social software to be detected is captured and processed, and the presence of risky keywords in the conversation content is detected. By using the risk detection strategy to determine the scope of risky keyword detection, terminal device lag caused by detecting irrelevant software is avoided, and the efficiency of risky keyword detection is improved.

[0053] The transaction database may contain transaction data registration information of numerous objects. The transaction data registration information is used to verify the identity and transaction data status of the objects. The transaction data registration information needs to be reviewed and its authenticity confirmed before it can be saved in the transaction database. The risk detection device can be displayed in the terminal device as an application to facilitate user operation. The application corresponding to the risk detection device may include a management terminal and a client terminal. Among them, company employees and company customers, such as the first object, can use the client terminal. The client terminal can be used to upload transaction data registration information and request transaction data exchange events from the management terminal through the client terminal. Transaction data management personnel can use the management terminal. The management terminal can be used to review transaction data registration information and manage transaction data exchange events. It can also split and restrict the permissions of different applications to prevent non-transaction data management personnel from erroneously performing transaction data exchange operations.

[0054] See Figure 4 , provides a flow chart of transaction data registration for the embodiment of this application. Figure 4 As shown, in one or more embodiments of the present application, the following steps S301-S303 may be included before step S101.

[0055] S301: Acquire transaction data registration information input by a first object, and generate a transaction data registration request based on the transaction data registration information.

[0056] Specifically, the first object can use the client application to input transaction data registration information, the risk detection device obtains the transaction data registration information input by the first object, and then generates a transaction data registration request based on the transaction data registration information. The transaction data registration request is used to request the transaction data management personnel corresponding to the first object to review the transaction data registration information.

[0057] Optionally, the client application can be applied to terminal devices such as computers, or mobile terminals such as mobile phones, so that the subject can quickly fill in the transaction data registration information and request review, thereby speeding up the collection of transaction data registration information. Figure 5 , provides an example diagram of a transaction data registration interface for the embodiment of the present application. The risk detection device can provide a transaction data registration interface for the object on the client application, further facilitating the object to fill in the transaction data registration information, avoiding filling in irrelevant information and missing key information, thereby improving the efficiency of transaction data registration. Figure 5As shown, the transaction data registration interface can prompt the user to fill in the "user", "affiliated unit", "position", "mobile phone number", "social software A account" and "social software B account", among which "user" can be used to fill in the name of the object, "affiliated unit" and "position" can be used to fill in the object's affiliated unit information, "mobile phone number" can be used to fill in the object's mobile phone number, and "social software A account" and "social software B account" can be used to fill in the user's social software accounts on social software A and social software B respectively, among which social software A and social software B can be different social software.

[0058] S302: Send a transaction data registration request to the user, and obtain registration permission information sent by the user in response to the transaction data registration request.

[0059] Specifically, the first object may be an object with which a transaction data exchange event may occur with the user. For example, the first object may belong to the same unit as the user, and a transaction data exchange event may occur between the unit to which the first object belongs and the unit to which the user belongs. The risk detection device may send a transaction data registration request to the user. For example, the transaction data registration request may be displayed on a control-end application used by the user. If the user reviews the transaction data registration information filled in by the first object and determines that the first object's information is true, registration permission information for the transaction data registration request may be sent through the control-end application. The risk detection device can then obtain the registration permission information sent by the user in response to the transaction data registration request. The registration permission information is used to indicate that the transaction data registration information of the first object is true.

[0060] Optionally, the risk detection device can obtain the unit information in the transaction data registration request, and determine the transaction data manager with the same unit information as the first object, send the transaction data registration request of the first object to the transaction data manager, and obtain the registration permission information sent by the transaction data manager in response to the transaction data registration request, so that the transaction data manager of the same unit can review the transaction data registration information, thereby improving the accuracy of the review, wherein the transaction data manager can also be a user.

[0061] S303: Based on the registration permission information, the transaction data registration information is saved in the transaction database.

[0062] Specifically, the risk detection device can save the transaction data registration information in the transaction data based on the registration permission information, so as to facilitate the verification of the identity of the first object based on the transaction data registration information in the transaction database when detecting risk keywords in the work of users or other transaction data managers.

[0063] In an embodiment of the present application, transaction data registration information input by a first subject is obtained, a transaction data registration request is generated based on the transaction data registration information, the transaction data registration request is sent to a user, registration permission information sent by the user in response to the transaction data registration request is obtained, and the transaction data registration information is stored in a transaction database based on the registration permission information. By storing transaction data registration information reviewed by a transaction data management staff member in the transaction database, the accuracy of the transaction data registration information is improved, and it is also convenient to subsequently call the big data in the transaction database to perform identity verification on the subject, further improving the security of the transaction data.

[0064] If the risk detection device obtains the transaction data registration information corresponding to the first object in the transaction database, it can determine whether the transaction data registration information meets the transaction data exchange conditions. However, the social software account used by the first object is a fake account. For example, the first object can modify the nickname corresponding to the social software account to an object nickname familiar to the user in order to deceive and confuse the user. However, the social software account itself has not been registered for transaction data, and the corresponding transaction data registration information cannot be found in the transaction database.

[0065] In one or more embodiments of the present application, the following steps may be included before step S103:

[0066] If the transaction data registration information corresponding to the social software account does not exist in the transaction database, it is determined that the transaction data registration information does not meet the transaction data exchange condition.

[0067] Specifically, if the risk detection device detects that the transaction data registration information corresponding to the social software account does not exist in the transaction database, it means that the social software account used by the first object has not been registered for transaction data and has not been reviewed by the transaction data management personnel. The subsequent steps of comparing the transaction data exchange conditions can be omitted, and it is directly determined that there is an abnormality in the identity of the first object, and it is determined that the transaction data registration information must not meet the transaction data exchange conditions, and a risk warning prompt information is output.

[0068] If transaction data registration information corresponding to the first subject's social software account exists in the transaction database, the transaction data level information is compared with the transaction data exchange conditions to determine whether the first subject can conduct a transaction data exchange event with the user. The transaction data exchange conditions can restrict transaction data exchange events based on the device information of the corresponding terminal device used, the subject's unit information, the subject's mobile phone number, or the subject's social software account. Because the risk detection device can be applied to the work scenarios of transaction data management personnel in corporate units, transaction data exchange events can be restricted based on the first subject's unit information based on the business needs of the user's unit.

[0069] See Figure 6 , provides a flow chart of determining transaction data exchange conditions for the embodiment of the present application. Figure 6 As shown, in one or more embodiments of the present application, the following steps S401-S402 may be included before step S103.

[0070] S401, obtaining the affiliated unit information in the transaction data registration information.

[0071] Specifically, the risk detection device obtains the transaction data registration information of the first object in the transaction database, and then can obtain the unit information in the transaction data registration information, where the unit information may include the name of the unit where the first object is employed, the unified social credit code and the position of the first object. The unified social credit code is a unique and lifelong legal identity identification code issued by each legal entity and other organization nationwide, which is used to standardize and unify the identity identification of various organizations.

[0072] S402: If the affiliated unit information is not in the preset transaction data exchange whitelist, it is determined that the transaction data registration information does not meet the transaction data exchange condition.

[0073] Specifically, a user or relevant staff member may set a preset transaction data exchange whitelist based on the business needs of the user's unit. The preset transaction data exchange whitelist may include information about one or more different units. For example, the preset transaction data exchange whitelist may include information about units that have transaction data exchanges and business collaborations with the user's unit. If the first subject's unit information is not on the preset transaction data exchange whitelist, it indicates that the first subject's unit should not have transaction data exchanges with the user's unit, and it can be determined that the transaction data registration information does not meet the transaction data exchange conditions.

[0074] In this embodiment of the present application, the affiliation information in the transaction data registration information is obtained. If the affiliation information is not in the preset transaction data exchange whitelist, it is determined that the transaction data registration information does not meet the transaction data exchange conditions. By restricting the affiliation information of the object, transaction data exchange incidents between the user and the wrong unit are avoided, further ensuring the security of transaction data.

[0075] If the transaction data registration information of the first object meets the transaction data exchange conditions, it means that the user can exchange transaction data with the first object. However, for the transaction data security of the unit to which the user belongs and for the compliance of the workflow, the user cannot directly input the transaction data into the first object or the unit to which the first object belongs. The transaction data needs to be approved by the second object. The second object can be the same as the unit to which the user belongs. For example, the second object can be the boss of the unit to which the user belongs.

[0076] See Figure 7 , provides a flow chart of generating a transaction data exchange request for an embodiment of the present application. Figure 7 As shown, in one or more embodiments of the present application, the method may further include the following steps S501-S503.

[0077] S501: If the transaction data registration information meets the transaction data exchange condition, obtain a transaction data exchange request for a first object input by a user.

[0078] Specifically, after the user has determined the details of the transaction data exchange event with the first object on the social software, the user can use the management and control application to input a transaction data exchange request for the first object. If the transaction data registration information of the first object meets the transaction data exchange conditions, there is no need to output the risk warning prompt information, and the transaction data exchange request input by the user can be obtained. The transaction data exchange request is used to request the second object to approve the transaction data exchange event between the second object and the first object. It can include the object of the transaction data exchange event, that is, the first object or the unit to which the first object belongs, etc., and can also include the transaction data value that needs to be exchanged.

[0079] S502: Send the transaction data exchange request to the second object, and obtain permission information for the transaction data exchange request input by the second object.

[0080] Specifically, the risk detection device can send a transaction data exchange request to the second object, where the second object can also use the management and control application. When the second object reviews the transaction data exchange request and confirms that it is correct, it can enter the permission information for the transaction data exchange request, and the risk detection device can obtain the permission information entered by the second object.

[0081] S503: Output permission information to enable the user to complete the transaction data exchange process for the first object.

[0082] Specifically, the risk detection device may input permission information to the user through the control-end application, so that the user completes the transaction data exchange processing for the first object and realizes the transaction data exchange event with the first object or the unit to which the first object belongs.

[0083] In this embodiment of the present application, if the transaction data registration information satisfies the transaction data exchange conditions, a transaction data exchange request input by the user for the first object is obtained, the transaction data exchange request is sent to the second object, permission information for the transaction data exchange request input by the second object is obtained, and permission information is output, allowing the user to complete the transaction data exchange process for the first object. By requiring that the transaction data registration information be verified by the second object before the transaction data exchange can proceed, transaction data security is further ensured.

[0084] To ensure that normal user work is not affected and to leave sufficient terminal interface space for the user, the user can minimize the control-side application. Even when minimized, the risk detection device will continue to perform risk detection tasks such as risk keyword detection, ensuring the security of transaction data while freeing up terminal interface space. Because the risk detection device not only performs risk detection but also assists users with approval operations related to transaction data exchange events, it needs to provide feedback to users awaiting second-party review while being minimized.

[0085] In one or more embodiments of the present application, the method may further include the following steps:

[0086] If the user receives an application minimize instruction, the application window is closed and a floating ball is displayed on the terminal interface.

[0087] Specifically, if the user does not want the window of the control-side application to block the terminal interface, he or she can send an application minimize instruction based on the control-side application. The risk detection device can then close the application window and display a floating ball on the terminal interface, where the floating ball can be spherical or in other shapes.

[0088] The step S502 may further include the following steps:

[0089] A transaction data exchange request is sent to a second object; if permission information or prohibition information for the transaction data exchange request is not received from the second object, the floating ball is displayed in a first state; if permission information for the transaction data exchange request is received from the second object, the floating ball is displayed in a second state; if prohibition information for the transaction data exchange request is received from the second object, the floating ball is displayed in a third state.

[0090] Specifically, the risk detection device can send the user's transaction data exchange request to the second object, and then display the floating ball in different states according to the different stages of the transaction data exchange request approval. If the permission information or prohibition information for the transaction data exchange request input by the second object has not been received, that is, it is still in the process of waiting for the second object to approve it, the floating ball can be displayed in the first state. If the permission information for the transaction data exchange request input by the second object is received, it means that the transaction data exchange request is approved, and the floating ball can be displayed in the second state. If the prohibition information for the transaction data exchange request input by the second object is received, it means that the transaction data exchange request is not approved, and the floating ball can be displayed in the third state. Among them, the first state, the second state and the third state are all different.

[0091] Please also see Figure 8 , an example schematic diagram of the display states of a floating ball is provided for an embodiment of the present application. The text information and patterns displayed on the floating ball in different states can be different. For example, in the first state, the floating ball can pop up a prompt bar and display the text message "Request pending approval", in the second state, the floating ball can pop up a prompt bar and display the text message "Request approved", and in the third state, the floating ball can pop up a prompt bar and display the text message "Request not approved". Based on the differences in text information and patterns, the floating ball can be displayed in different colors in different states. For example, in the first state, the floating ball is orange, in the second state, the floating ball is green, and in the third state, the floating ball is red.

[0092] On this basis, some dynamic guidance can also be added to improve the feedback perception of the terminal interface, making the floating ball more vivid and attractive. For example, in the first state, when no operation is performed on the floating ball, the floating ball can rotate automatically, and the lightning pattern in the shield can zoom and flash. When the user hovers over the floating ball with the mouse, the automatic rotation and zoom and flashing actions stop and a prompt bar pops up. In the second state, when no operation is performed on the floating ball, the floating ball sphere can rotate automatically, and the lightning pattern in the shield can rotate in three dimensions. When the user hovers over the floating ball with the mouse, the automatic rotation and three-dimensional rotation actions can stop and a prompt bar pops up. In the third state, when no operation is performed on the floating ball, the floating ball can rotate automatically, and the lightning pattern in the shield can flash quickly to reflect a warning. When the user hovers over the floating ball with the mouse, the automatic rotation and fast flashing actions stop and a prompt bar pops up.

[0093] Optionally, when it is detected that the transaction data registration information does not meet the transaction data exchange conditions, in addition to outputting risk warning prompt information, a floating ball can also be displayed in a third state. The prompt bar of the floating ball can display risk warning prompt information, such as "Verify identity, contact leadership directly, protect assets, stay away from fraud risks" and other text information.

[0094] Optionally, if a click instruction on the floating ball is detected, an anti-fraud information window can be popped up based on the floating ball, and anti-fraud knowledge information can be displayed in the anti-fraud information window, wherein the anti-fraud knowledge information can be edited by the user or relevant staff, or obtained from the Internet.

[0095] Optionally, if a click instruction on the floating ball is detected, an approval process window can be popped up based on the floating ball, and the transaction data exchange request record can be displayed in the approval process window, for example, including transaction data exchange requests that have been approved and transaction data exchange requests that are waiting for approval.

[0096] Optionally, if a click instruction on the floating ball is detected, the anti-fraud information window and the approval process window can be popped up based on the floating ball. The anti-fraud information window and the approval process window can be displayed in the form of a TAB page form. The TAB page form is an interface design component, usually composed of a group of tabs and corresponding windows. Users can switch to display different windows by clicking different tabs. Please refer to Figure 9 , an example schematic diagram of a floating ball pop-up window is provided for an embodiment of the present application. The risk detection device can display a first label and a second label in the TAB page window. The user clicks the first label "Transfer Process" to jump to the approval process window, and the user clicks the second label "Anti-fraud Knowledge" to jump to the anti-fraud information window.

[0097] In an embodiment of the present application, if a user's application minimize instruction is received, the application window is closed and a floating ball is displayed on the terminal interface, and the transaction data exchange request is sent to the second object; if the permission information or prohibition information for the transaction data exchange request input by the second object is not received, the floating ball is displayed in a first state; if the permission information for the transaction data exchange request input by the second object is received, the floating ball is displayed in a second state; if the prohibition information for the transaction data exchange request input by the second object is received, the floating ball is displayed in a third state. The floating ball is displayed in different states according to different stages of the approval process of the transaction data exchange request, which can promptly remind the user of the progress and status of the transaction data exchange request while freeing up sufficient terminal interface space for the user to work.

[0098] The following will be combined with the Figure 10 -Attached Figure 11, the risk detection device provided by the embodiment of the present application is introduced in detail. Figure 10 -Attached Figure 11 The risk detection device in the present application is used to execute Figures 1-9 For the convenience of explanation, only the part related to the embodiment of the present application is shown. For the specific technical details not disclosed, please refer to the present application. Figures 1-9 The embodiment shown.

[0099] See Figure 10 , which shows a schematic diagram of the structure of a risk detection device provided by an exemplary embodiment of the present application. The risk detection device can be implemented as all or part of the device through software, hardware, or a combination of both. The device 1 includes a keyword detection unit 11, a registration information acquisition unit 12, and a risk warning unit 13.

[0100] A keyword detection unit 11 is configured to detect the presence of risky keywords in the social software window between the user and the first object;

[0101] A registration information acquisition unit 12 is configured to acquire a social software account of the first subject, and acquire transaction data registration information of the first subject in a transaction database based on the social software account;

[0102] The risk warning unit 13 is configured to output risk warning information if the transaction data registration information does not meet the transaction data exchange condition.

[0103] In this embodiment, the presence of risk keywords is detected in a social software window between a user and a first party, the first party's social software account is obtained, and the first party's transaction data registration information is retrieved from a transaction database based on the social software account. If the transaction data registration information does not meet the transaction data exchange conditions, a risk warning prompt message is output. By detecting risk keywords, the party with whom transaction data exchange may occur is determined, and the transaction data registration information of the first party is searched and checked in the transaction data registry. If the exchange conditions are not met, an alarm is issued, and prevention and control measures are taken before potential transaction data exchange events occur, thereby avoiding unsafe transaction data exchange events.

[0104] See Figure 11 , which shows a schematic diagram of the structure of a risk detection device provided by an exemplary embodiment of the present application. The risk detection device can be implemented as all or part of the device through software, hardware, or a combination of both. The device 1 includes a transaction data registration unit 14, a keyword detection unit 11, a registration information acquisition unit 12, a first condition judgment unit 15, a second condition judgment unit 16, a risk warning unit 13, a request approval unit 17, and a floating ball display unit 18.

[0105] The transaction data registration unit 14 is configured to obtain transaction data registration information input by the first object and generate a transaction data registration request based on the transaction data registration information;

[0106] Sending the transaction data registration request to the user, and obtaining registration permission information sent by the user in response to the transaction data registration request;

[0107] Based on the registration permission information, the transaction data registration information is stored in a transaction database.

[0108] A keyword detection unit 11 is configured to detect the presence of risky keywords in the social software window between the user and the first object;

[0109] Optionally, the keyword detection unit 11 is specifically configured to determine the social software to be detected based on a pre-set risk detection strategy;

[0110] Capturing and processing the conversation content between the user and the first object in the social software window to be detected;

[0111] Risky keywords are detected in the conversation content.

[0112] A registration information acquisition unit 12 is configured to acquire a social software account of the first subject, and acquire transaction data registration information of the first subject in a transaction database based on the social software account;

[0113] The first condition judgment unit 15 is configured to determine that the transaction data registration information does not meet the transaction data exchange condition if the transaction data registration information corresponding to the social software account does not exist in the transaction database.

[0114] The second condition judgment unit 16 is used to obtain the unit information in the transaction data registration information;

[0115] If the affiliated unit information is not in the preset transaction data exchange whitelist, it is determined that the transaction data registration information does not meet the transaction data exchange condition.

[0116] The risk warning unit 13 is configured to output risk warning information if the transaction data registration information does not meet the transaction data exchange condition.

[0117] a request approval unit 17 configured to obtain a transaction data exchange request for the first object input by the user if the transaction data registration information satisfies the transaction data exchange condition;

[0118] Sending the transaction data exchange request to the second object, and obtaining permission information for the transaction data exchange request input by the second object;

[0119] The permission information is output to enable the user to complete the transaction data exchange process for the first object.

[0120] The floating ball display unit 18 is used to close the application window and display the floating ball on the terminal interface if the user's application minimize instruction is received.

[0121] Optionally, the request approval unit 17 is specifically configured to send the transaction data exchange request to the second object;

[0122] If no permission information or prohibition information input by the second object for the transaction data exchange request is received, displaying the floating ball in a first state;

[0123] If permission information for the transaction data exchange request input by the second object is received, displaying the floating ball in a second state;

[0124] If prohibition information input by the second object for the transaction data exchange request is received, the floating ball is displayed in a third state.

[0125] In this embodiment, transaction data registration information input by a first subject is obtained, a transaction data registration request is generated based on the transaction data registration information, the transaction data registration request is sent to a user, registration permission information sent by the user in response to the transaction data registration request is obtained, and the transaction data registration information is stored in a transaction database based on the registration permission information. By storing the transaction data registration information, which has been reviewed by a transaction data management staff member, in the transaction database, the accuracy of the transaction data registration information is improved, and subsequent use of the big data in the transaction database for subject identity verification is facilitated, further enhancing transaction data security. Based on a pre-set risk detection strategy, a social software to be detected is identified, and the conversation content between the user and the first subject in the social software window of the social software to be detected is captured and processed to detect the presence of risk keywords in the conversation content. The risk detection strategy determines the scope of risk keyword detection, avoids terminal device lag caused by detecting irrelevant software, and improves the efficiency of risk keyword detection. If the transaction data registration information corresponding to the social software account does not exist in the transaction database, it is determined that the transaction data registration information does not meet the transaction data exchange conditions. The social software account of the first subject is obtained, and the transaction data registration information of the first subject is retrieved from the transaction database based on the social software account. If the transaction data registration information does not meet the transaction data exchange conditions, a risk warning prompt message is output. The unit information in the transaction data registration information can be obtained. If the unit information is not in the preset transaction data exchange whitelist, it is determined that the transaction data registration information does not meet the transaction data exchange conditions. By restricting the unit information of the object, transaction data exchange incidents between users and the wrong unit are avoided, further ensuring the security of transaction data. By detecting risk keywords, the objects that may undergo transaction data exchange are determined, and the transaction data registration information of the first object is searched and detected in the transaction data registration library. An alarm is issued when the exchange conditions are not met, and prevention and control are carried out before potential transaction data exchange incidents occur, avoiding the occurrence of unsafe transaction data exchange incidents.

[0126] If the transaction data registration information satisfies the transaction data exchange conditions, the system obtains a transaction data exchange request for the first object input by the user, sends the transaction data exchange request to the second object, obtains permission information for the transaction data exchange request input by the second object, and outputs the permission information, allowing the user to complete the transaction data exchange process for the first object. By allowing the transaction data exchange to proceed only after re-verification by the second object if the transaction data registration information is correct, transaction data security is further ensured. If a user minimizes an application, the application window is closed, a floating ball is displayed on the terminal interface, and the transaction data exchange request is sent to the second object. If no permission or prohibition information for the transaction data exchange request is received from the second object, the floating ball is displayed in a first state. If permission information for the transaction data exchange request is received from the second object, the floating ball is displayed in a second state. If prohibition information for the transaction data exchange request is received from the second object, the floating ball is displayed in a third state. Displaying the floating ball in different states at different stages of the transaction data exchange request approval process allows the user to work on the terminal interface while providing timely notification of the progress and status of the transaction data exchange request.

[0127] It should be noted that the risk detection device provided in the above embodiment, when executing the risk detection method, only uses the division of the above-mentioned functional modules as an example. In actual applications, the above-mentioned functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. In addition, the risk detection device provided in the above embodiment and the risk detection method embodiment are based on the same concept. The implementation process is detailed in the method embodiment and will not be repeated here.

[0128] The serial numbers of the above embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0129] The present application also provides a computer storage medium that can store multiple instructions, which are suitable for being loaded and executed by a processor as described above. Figures 1-9 The risk detection method of the embodiment shown, the specific execution process can be found in Figures 1-9 The detailed description of the illustrated embodiment will not be repeated here.

[0130] The present application also provides a computer program product, which stores at least one instruction, and the at least one instruction is loaded and executed by the processor as described above. Figures 1-9 The risk detection method of the embodiment shown, the specific execution process can be found in Figures 1-9 The detailed description of the illustrated embodiment will not be repeated here.

[0131] Please refer to Figure 12 , which shows a block diagram of the structure of an electronic device provided by an exemplary embodiment of the present application. The electronic device in the present application may include one or more of the following components: a processor 110, a memory 120, an input device 130, an output device 140, and a bus 150. The processor 110, the memory 120, the input device 130, and the output device 140 may be connected via the bus 150.

[0132] The processor 110 may include one or more processing cores. The processor 110 utilizes various interfaces and circuits to connect various components within the electronic device. It executes instructions, programs, code sets, or instruction sets stored in the memory 120, as well as accesses data stored in the memory 120, to perform various functions and process data for the terminal 100. Optionally, the processor 110 may be implemented using at least one of the following hardware forms: a digital signal processing (DSP), a field-programmable gate array (FPGA), or a programmable logic array (PLA). The processor 110 may integrate one or a combination of a central processing unit (CPU), a graphics processing unit (GPU), and a modem. The CPU primarily processes the operating system, user interfaces, and applications; the GPU is responsible for rendering and drawing display content; and the modem handles wireless communications. It is understood that the modem may not be integrated into the processor 110 and may be implemented separately via a communication chip.

[0133] The memory 120 may include a random access memory (RAM) or a read-only memory (ROM). Optionally, the memory 120 includes a non-transitory computer-readable storage medium. The memory 120 may be used to store instructions, programs, codes, code sets or instruction sets. The memory 120 may include a program storage area and a data storage area, wherein the program storage area may store instructions for implementing an operating system, instructions for implementing at least one function (such as a touch function, a sound playback function, an image playback function, etc.), instructions for implementing the above-mentioned various method embodiments, etc. The operating system may be an Android system, including a system deeply developed based on the Android system, an iOS system developed by Apple, including a system deeply developed based on the iOS system or other systems.

[0134] The memory 120 can be divided into an operating system space and a user space. The operating system runs in the operating system space, and native and third-party applications run in the user space. In order to ensure that different third-party applications can achieve better operating results, the operating system allocates corresponding system resources to different third-party applications. However, the requirements for system resources in different application scenarios in the same third-party application are also different. For example, in the local resource loading scenario, the third-party application has higher requirements for disk reading speed; in the animation rendering scenario, the third-party application has higher requirements for GPU performance. The operating system and the third-party application are independent of each other, and the operating system often cannot perceive the current application scenario of the third-party application in a timely manner, resulting in the operating system being unable to perform targeted system resource adaptation according to the specific application scenario of the third-party application.

[0135] In order for the operating system to distinguish the specific application scenarios of third-party applications, it is necessary to open up data communication between third-party applications and the operating system so that the operating system can obtain the current scenario information of third-party applications at any time, and then perform targeted system resource adaptation based on the current scenario.

[0136] The input device 130 is used to receive input commands or data and includes, but is not limited to, a keyboard, a mouse, a camera, a microphone, or a touch-sensitive device. The output device 140 is used to output commands or data and includes, but is not limited to, a display device and a speaker. In one example, the input device 130 and the output device 140 may be combined, and the input device 130 and the output device 140 may be a touch-sensitive display.

[0137] The touch display screen can be designed as a full screen, a curved screen or a special-shaped screen. The touch display screen can also be designed as a combination of a full screen and a curved screen, or a combination of a special-shaped screen and a curved screen, which is not limited in the present embodiment.

[0138] In addition, those skilled in the art will understand that the structures of the electronic devices shown in the above figures do not limit the electronic devices. The electronic devices may include more or fewer components than shown, or may combine certain components, or arrange the components differently. For example, the electronic devices may also include radio frequency circuits, input units, sensors, audio circuits, wireless fidelity (WiFi) modules, power supplies, Bluetooth modules, and other components, which will not be described in detail here.

[0139] exist Figure 12 In the electronic device shown, the processor 110 may be configured to call the risk detection application stored in the memory 120 and specifically perform the following operations:

[0140] Detecting the presence of risky keywords in the social software window between the user and the first object;

[0141] Acquire the social software account of the first subject, and acquire transaction data registration information of the first subject in a transaction database based on the social software account;

[0142] If the transaction data registration information does not meet the transaction data exchange conditions, a risk warning prompt message is output.

[0143] In one embodiment, when detecting the presence of risky keywords in the social software window between the user and the first object, the processor 110 specifically performs the following operations:

[0144] Based on the pre-set risk detection strategy, determine the social software to be detected;

[0145] Capturing and processing the conversation content between the user and the first object in the social software window to be detected;

[0146] Risky keywords are detected in the conversation content.

[0147] In one embodiment, before detecting the presence of risk keywords in the social software window between the user and the first object, the processor 110 further performs the following operations:

[0148] Acquire transaction data registration information input by the first object, and generate a transaction data registration request based on the transaction data registration information;

[0149] Sending the transaction data registration request to the user, and obtaining registration permission information sent by the user in response to the transaction data registration request;

[0150] Based on the registration permission information, the transaction data registration information is stored in a transaction database.

[0151] In one embodiment, before outputting the risk warning prompt information if the transaction data registration information does not meet the transaction data exchange condition, the processor 110 further performs the following operations:

[0152] If the transaction data registration information corresponding to the social software account does not exist in the transaction database, it is determined that the transaction data registration information does not meet the transaction data exchange condition.

[0153] In one embodiment, before outputting the risk warning prompt information if the transaction data registration information does not meet the transaction data exchange condition, the processor 110 further performs the following operations:

[0154] Obtaining the affiliated unit information in the transaction data registration information;

[0155] If the affiliated unit information is not in the preset transaction data exchange whitelist, it is determined that the transaction data registration information does not meet the transaction data exchange condition.

[0156] In one embodiment, when executing the risk detection method, the processor 110 further performs the following operations:

[0157] If the transaction data registration information satisfies the transaction data exchange condition, obtaining a transaction data exchange request for the first object input by the user;

[0158] Sending the transaction data exchange request to the second object, and obtaining permission information for the transaction data exchange request input by the second object;

[0159] The permission information is output to enable the user to complete the transaction data exchange process for the first object.

[0160] In one embodiment, when executing the risk detection method, the processor 110 further performs the following operations:

[0161] If an application minimization instruction is received from the user, the application window is closed and a floating ball is displayed on the terminal interface;

[0162] When sending the transaction data exchange request to the second object and obtaining permission information input by the second object for the transaction data exchange request, the following operations are specifically performed:

[0163] sending the transaction data exchange request to a second object;

[0164] If no permission information or prohibition information input by the second object for the transaction data exchange request is received, displaying the floating ball in a first state;

[0165] If permission information for the transaction data exchange request input by the second object is received, displaying the floating ball in a second state;

[0166] If prohibition information input by the second object for the transaction data exchange request is received, the floating ball is displayed in a third state.

[0167] In this embodiment, transaction data registration information input by a first subject is obtained, a transaction data registration request is generated based on the transaction data registration information, the transaction data registration request is sent to a user, registration permission information sent by the user in response to the transaction data registration request is obtained, and the transaction data registration information is stored in a transaction database based on the registration permission information. By storing the transaction data registration information, which has been reviewed by a transaction data management staff member, in the transaction database, the accuracy of the transaction data registration information is improved, and subsequent use of the big data in the transaction database for subject identity verification is facilitated, further enhancing transaction data security. Based on a pre-set risk detection strategy, a social software to be detected is identified, and the conversation content between the user and the first subject in the social software window of the social software to be detected is captured and processed to detect the presence of risk keywords in the conversation content. The risk detection strategy determines the scope of risk keyword detection, avoids terminal device lag caused by detecting irrelevant software, and improves the efficiency of risk keyword detection. If the transaction data registration information corresponding to the social software account does not exist in the transaction database, it is determined that the transaction data registration information does not meet the transaction data exchange conditions. The social software account of the first subject is obtained, and the transaction data registration information of the first subject is retrieved from the transaction database based on the social software account. If the transaction data registration information does not meet the transaction data exchange conditions, a risk warning prompt message is output. The unit information in the transaction data registration information can be obtained. If the unit information is not in the preset transaction data exchange whitelist, it is determined that the transaction data registration information does not meet the transaction data exchange conditions. By restricting the unit information of the object, transaction data exchange incidents between users and the wrong unit are avoided, further ensuring the security of transaction data. By detecting risk keywords, the objects that may undergo transaction data exchange are determined, and the transaction data registration information of the first object is searched and detected in the transaction data registration library. An alarm is issued when the exchange conditions are not met, and prevention and control are carried out before potential transaction data exchange incidents occur, avoiding the occurrence of unsafe transaction data exchange incidents.

[0168] If the transaction data registration information satisfies the transaction data exchange conditions, the system obtains a transaction data exchange request for the first object input by the user, sends the transaction data exchange request to the second object, obtains permission information for the transaction data exchange request input by the second object, and outputs the permission information, allowing the user to complete the transaction data exchange process for the first object. By allowing the transaction data exchange to proceed only after re-verification by the second object if the transaction data registration information is correct, transaction data security is further ensured. If a user minimizes an application, the application window is closed, a floating ball is displayed on the terminal interface, and the transaction data exchange request is sent to the second object. If no permission or prohibition information for the transaction data exchange request is received from the second object, the floating ball is displayed in a first state. If permission information for the transaction data exchange request is received from the second object, the floating ball is displayed in a second state. If prohibition information for the transaction data exchange request is received from the second object, the floating ball is displayed in a third state. Displaying the floating ball in different states at different stages of the transaction data exchange request approval process allows the user to work on the terminal interface while providing timely notification of the progress and status of the transaction data exchange request.

[0169] Those skilled in the art will appreciate that all or part of the processes in the above-described method embodiments can be implemented by instructing related hardware through a computer program. The program can be stored in a computer-readable storage medium, and when executed, the program can include the processes in the above-described method embodiments. The storage medium can be a magnetic disk, an optical disk, a read-only memory, or a random access memory.

[0170] The above disclosure is only a preferred embodiment of the present application, and certainly cannot be used to limit the scope of rights of the present application. Therefore, equivalent changes made according to the claims of the present application are still within the scope covered by the present application.

[0171] It should be noted that the information (including but not limited to user device information, user personal information, etc.), data (including but not limited to data used for analysis, stored data, displayed data, etc.), and signals involved in the embodiments of this specification are all authorized by the user or fully authorized by all parties, and the collection, use, and processing of relevant data must comply with the relevant laws, regulations, and standards of the relevant countries and regions. For example, the conversation content and transaction data registration information involved in this specification are all obtained with full authorization.

Claims

1. A risk detection method, characterized in that: The method comprises: Detecting the presence of risky keywords in the social software window between the user and the first object; Acquire the social software account of the first subject, and acquire transaction data registration information of the first subject in a transaction database based on the social software account; If the transaction data registration information does not meet the transaction data exchange conditions, a risk warning prompt message is output.

2. The method according to claim 1, characterized in that The detecting that risk keywords exist in the social software window between the user and the first object includes: Based on the pre-set risk detection strategy, determine the social software to be detected; Capturing and processing the conversation content between the user and the first object in the social software window to be detected; Risky keywords are detected in the conversation content.

3. The method according to claim 1, characterized in that Before detecting the presence of risky keywords in the social software window between the user and the first object, the method further includes: Acquire transaction data registration information input by the first object, and generate a transaction data registration request based on the transaction data registration information; Sending the transaction data registration request to the user, and obtaining registration permission information sent by the user in response to the transaction data registration request; Based on the registration permission information, the transaction data registration information is stored in a transaction database.

4. The method according to claim 1, wherein If the transaction data registration information does not meet the transaction data exchange condition, before outputting the risk warning prompt information, the method further includes: If the transaction data registration information corresponding to the social software account does not exist in the transaction database, it is determined that the transaction data registration information does not meet the transaction data exchange condition.

5. The method according to claim 3, characterized in that If the transaction data registration information does not meet the transaction data exchange condition, before outputting the risk warning prompt information, the method further includes: Obtaining the affiliated unit information in the transaction data registration information; If the affiliated unit information is not in the preset transaction data exchange whitelist, it is determined that the transaction data registration information does not meet the transaction data exchange condition.

6. The method according to claim 1, characterized in that The method further comprises: If the transaction data registration information satisfies the transaction data exchange condition, obtaining a transaction data exchange request for the first object input by the user; Sending the transaction data exchange request to the second object, and obtaining permission information for the transaction data exchange request input by the second object; The permission information is output to enable the user to complete the transaction data exchange process for the first object.

7. The method according to claim 6, characterized in that The method further comprises: If an application minimization instruction is received from the user, the application window is closed and a floating ball is displayed on the terminal interface; The sending the transaction data exchange request to the second object and obtaining permission information input by the second object for the transaction data exchange request includes: sending the transaction data exchange request to a second object; If no permission information or prohibition information input by the second object for the transaction data exchange request is received, displaying the floating ball in a first state; If permission information for the transaction data exchange request input by the second object is received, displaying the floating ball in a second state; If prohibition information input by the second object for the transaction data exchange request is received, the floating ball is displayed in a third state.

8. A risk detection device, characterized in that: The device comprises: A keyword detection unit, configured to detect the presence of risky keywords in the social software window between the user and the first object; a registration information acquisition unit, configured to acquire a social software account of the first subject, and acquire transaction data registration information of the first subject in a transaction database based on the social software account; The risk warning unit is used to output risk warning prompt information if the transaction data registration information does not meet the transaction data exchange condition.

9. A computer storage medium, characterized in that The computer storage medium stores a plurality of instructions, which are suitable for being loaded by a processor and executing the method steps according to any one of claims 1 to 7.

10. An electronic device, characterized in that: include: A processor and a memory; wherein the memory stores a computer program, and the computer program is suitable for being loaded by the processor and executing the method steps according to any one of claims 1 to 7.

Images