Method and device for payment risk control, storage medium and electronic equipment

Abstract

The embodiment of the invention discloses a payment risk control method and device, a storage medium and electronic equipment, and relates to the technical field of computers. The method comprises the following steps: in response to a payment triggering operation executed by a user, obtaining a screen sharing state corresponding to user equipment currently used by the user; and if the screen sharing state indicates that the user equipment is currently in screen sharing, executing risk control operation corresponding to the payment triggering operation according to the screen sharing state. According to the embodiment of the invention, by sensing whether the potential fraudulent person is in the screen sharing environment or not, pre-protection, early warning or timely blocking and interception are carried out, the risk that the user is guided to fraud in the screen sharing state can be obviously reduced, and the risk that the fund of the user is deceived in a payment scene can be greatly reduced.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a method, device, storage medium and electronic device for payment risk control. Background Art

[0002] In the prior art, fraudsters may use screen sharing to commit fraud. Fraudsters often induce victims to download a regular video conferencing software for communication. Since there are many manufacturers of such regular video conferencing software, the market demand is large and it can be applied to various conference scenarios, it is impossible to restrict its functions, and early warning countermeasures through the video conferencing software have little effect. Summary of the invention

[0003] The purpose of the embodiments of this specification is to provide a method, device, storage medium and electronic device for payment risk control.

[0004] The embodiments of this specification provide a method for payment risk control, which identifies whether the user is in a high-risk and vulnerable screen sharing environment according to the screen sharing state of the user device currently used by the user when the user performs a payment trigger operation, and performs a risk control operation corresponding to the payment trigger operation. By sensing whether the potential victim of fraud is in the screen sharing environment, pre-protection, early warning or timely blocking and interception can be performed, which can significantly reduce the risk of the user being led to fraud in the screen sharing state, and can greatly reduce the risk of the user's funds being defrauded in the payment scenario. The method includes:

[0005] In response to a payment triggering operation performed by a user, obtaining a screen sharing state corresponding to a user device currently used by the user;

[0006] If the screen sharing status indicates that the user device is currently in screen sharing, a risk control operation corresponding to the payment triggering operation is performed according to the screen sharing status.

[0007] Further, obtaining the screen sharing state corresponding to the user equipment currently used by the user includes at least one of the following:

[0008] Determining a screen sharing state corresponding to the user device according to screen recording information corresponding to a current screen of the user device currently used by the user;

[0009] Determine the screen sharing status corresponding to the user device according to the projection information corresponding to the current screen of the user device currently used by the user.

[0010] Further, the performing of a risk control operation corresponding to the payment triggering operation according to the screen sharing state includes:

[0011] Determining corresponding risk quantification information according to the screen sharing state;

[0012] According to the risk quantification information, a risk control operation corresponding to the payment triggering operation is performed.

[0013] Furthermore, the screen sharing state includes operation records corresponding to the user equipment during the screen sharing period and screen sharing duration information;

[0014] Wherein, determining corresponding risk quantification information according to the screen sharing state includes:

[0015] Corresponding risk quantification information is determined according to the operation record, the screen sharing duration information, the device risk quantification information corresponding to the user device, and the transaction level quantification information corresponding to the user.

[0016] Further, determining corresponding risk quantification information according to the operation record, the screen sharing duration information, the device risk quantification information corresponding to the user device, and the transaction level quantification information corresponding to the user includes:

[0017] The corresponding risk quantification information is determined based on the operation record, the screen sharing duration information, the device risk quantification information corresponding to the user device, the transaction volume quantification information corresponding to the user, and the social relationship quantification information between the user and the payment object corresponding to the payment trigger operation.

[0018] Further, the screen sharing state includes the screen content shared by the user equipment;

[0019] The performing of the risk control operation corresponding to the payment triggering operation according to the screen sharing state includes:

[0020] According to the shared screen content of the user device, a risk control operation corresponding to the payment triggering operation is performed.

[0021] Further, the performing a risk control operation corresponding to the payment triggering operation according to the screen content shared by the user device includes:

[0022] According to the sensitive information contained in the shared screen content of the user device, a risk control operation corresponding to the payment triggering operation is performed.

[0023] Furthermore, the performing of a risk control operation corresponding to the payment triggering operation according to the sensitive information contained in the shared screen content of the user device includes:

[0024] A risk control operation corresponding to the payment triggering operation is performed based on the association information between the sensitive information contained in the shared screen content of the user device and the screen presentation content of the user device within a preset time range before the screen sharing is started.

[0025] Furthermore, the performing of a risk control operation corresponding to the payment triggering operation according to the sensitive information contained in the shared screen content of the user device includes:

[0026] According to the association information between the sensitive information contained in the shared screen content of the user device and the operation object corresponding to the payment triggering operation, a risk control operation corresponding to the payment triggering operation is performed.

[0027] Furthermore, the screen sharing state includes operation records corresponding to the user equipment during the screen sharing period;

[0028] The performing of the risk control operation corresponding to the payment triggering operation according to the screen sharing state includes:

[0029] According to the operation record corresponding to the user device during the screen sharing period, a risk control operation corresponding to the payment triggering operation is performed.

[0030] Further, the performing of a risk control operation corresponding to the payment triggering operation according to the operation record corresponding to the user device during the screen sharing period includes:

[0031] According to the sensitive operations involved in the operation records corresponding to the user device during screen sharing, a risk control operation corresponding to the payment triggering operation is performed.

[0032] Furthermore, the performing of the risk control operation corresponding to the payment triggering operation according to the sensitive operation involved in the operation record corresponding to the user device during the screen sharing period includes:

[0033] According to the association information between the sensitive operations involved in the operation records corresponding to the user device during screen sharing and the historical operations performed by the user device within a preset time range before the screen sharing is started, a risk control operation corresponding to the payment triggering operation is performed.

[0034] Furthermore, the performing of the risk control operation corresponding to the payment triggering operation according to the sensitive operation involved in the operation record corresponding to the user device during the screen sharing period includes:

[0035] According to the association information between the sensitive operation involved in the operation record corresponding to the user device during screen sharing and the payment triggering operation, a risk control operation corresponding to the payment triggering operation is performed.

[0036] The embodiment of this specification also provides a device for payment risk control, including:

[0037] A screen sharing state obtaining module, configured to obtain, in response to a payment triggering operation performed by a user, a screen sharing state corresponding to a user device currently used by the user;

[0038] The payment risk control module is configured to execute a risk control operation corresponding to the payment triggering operation according to the screen sharing state if the screen sharing state indicates that the user device is currently in screen sharing.

[0039] The embodiments of the present specification also provide a storage medium, wherein the storage medium stores a computer program, and the computer program is suitable for being loaded by a processor and executing the steps of the above method.

[0040] An embodiment of the present specification also provides an electronic device, comprising: 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 steps of the above method.

[0041] In the embodiments of the present specification, when the user executes a payment trigger operation, it is identified whether the user is in a high-risk and vulnerable screen sharing environment based on the screen sharing status corresponding to the user device currently used by the user, and a risk control operation corresponding to the payment trigger operation is performed. By sensing whether the potential victim of defraud is in a screen sharing environment, pre-protection, early warning or timely blocking and interception can be performed, which can significantly reduce the risk of the user being led to fraud in the screen sharing state, and can greatly reduce the risk of the user's funds being defrauded in the payment scenario. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] Figure 1 A flowchart of a method for payment risk control provided in an embodiment of this specification.

[0043] Figure 2 A schematic diagram of the structure of a device for payment risk control provided in an embodiment of this specification.

[0044] Figure 3 A schematic diagram of the structure of an electronic device provided in an embodiment of this specification. DETAILED DESCRIPTION

[0045] In order to make the purpose, technical solutions and advantages of this specification more clear, the technical solutions of this specification will be clearly and completely described below in combination with the specific embodiments of this specification and the corresponding drawings. Obviously, the described embodiments are only part of the embodiments of this specification, not all of them. Based on the embodiments in this specification, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this specification.

[0046] See also Figure 1 , is a flow chart of a method for payment risk control provided in an embodiment of this specification. In the embodiment of this specification, the method for payment risk control is applied to a device for payment risk control (hereinafter referred to as "payment risk control device") or an electronic device equipped with a payment risk control device. Figure 1 The process shown is described in detail, and the method for payment risk control may specifically include the following steps:

[0047] S102: In response to a payment triggering operation performed by a user, obtaining a screen sharing state corresponding to a user device currently used by the user.

[0048] In some embodiments, payment trigger operations include but are not limited to any operations performed by a user to trigger payment behavior, such as operations for triggering the display of a payment code (for example, a user clicks a "payment code" button), operations for triggering a transfer or sending a red envelope (for example, a user clicks a "transfer" button or a "send red envelope" button), operations for triggering entry into a payment page (for example, a user clicks a "pay" button), and operations for triggering the opening or logging into a payment application (for example, a user clicks an icon of a payment application on the desktop of the user device currently being used, or the user clicks a "login" button). It should be noted that the above-mentioned payment trigger operations are only examples and not limitations. Those skilled in the art should understand that any operation for triggering a specific payment behavior may be included within the scope of protection of this specification.

[0049] In some embodiments, in response to a payment trigger operation performed by a user, the screen sharing status corresponding to the user device currently used by the user is obtained, wherein the user device includes but is not limited to any electronic product that can perform human-computer interaction with the user (for example, human-computer interaction through a touchpad), such as a smart phone, a tablet computer, a PC (Personal Computer), etc., and the electronic product can use any operating system, such as an Android operating system, an iOS operating system, a Windows operating system, etc. In some embodiments, in addition to including indication information for indicating whether the user device is currently in screen sharing, the screen sharing status also includes but is not limited to the screen sharing duration, the screen sharing start time, the screen content of the user device being shared, the operation record corresponding to the user device during the screen sharing period, etc., and this specification does not limit the specific content of the screen sharing status. In some embodiments, screen sharing refers to a user sharing the screen content of the user device currently used with others in real time. Through screen sharing, participants can see the desktop, application or specific window of the sharer.

[0050] In some embodiments, the screen sharing state corresponding to the user device currently used by the user may be obtained by calling an interface provided by the user device, or the screen sharing state corresponding to the user device may be obtained from the notification message by monitoring the notification message sent by the user device. For example, the user device may send a corresponding notification message when the screen sharing state changes. For another example, the user device may send a corresponding notification message at preset time intervals during screen sharing. Here, this specification does not limit the specific method of obtaining the screen sharing state corresponding to the user device. For example, taking the user device as a mobile phone or tablet computer using the iOS operating system as an example, by calling the API of UIScreen (UIScreen is a class in iOS development, used to represent the screen of the device) to determine whether the current screen of the user device is being recorded, mirrored or sent by Airplay, when UIScreen.isCaptured is true, it indicates whether the current screen of the user device is being recorded, mirrored or sent by Airplay, then it can be determined that the user device is currently in screen sharing, and when UIScreen.isCaptured is false, it can be determined that the user device is not currently in screen sharing. For another example, when the screen recording status changes, UIKit (UIKit is a set of frameworks used to build user interfaces in iOS development) will send a UIScreenCapturedDidChange notification. UIScreenCapturedDidChangeNotification is a notification in the iOS system that informs the application whether the current screen is being recorded. When the recording status of the screen changes, UIKit will send this notification. By listening to this notification, you can know whether the current screen of the user's device is being recorded, and further determine whether the user's device is currently in screen sharing.

[0051] S104: If the screen sharing state indicates that the user device is currently in screen sharing, perform a risk control operation corresponding to the payment triggering operation according to the screen sharing state.

[0052] In some embodiments, if the screen sharing state indicates that the user device is currently in screen sharing, the risk control operation corresponding to the payment trigger operation currently executed by the user is further determined according to the screen sharing state, and the risk control operation is executed, wherein the risk control operation includes but is not limited to any operation for risk control of the payment trigger operation, for example, the risk control operation may be to block the payment behavior triggered by the payment trigger operation, that is, to stop the payment behavior, or it may be to interactively remind the user for the payment trigger operation, and the user determines whether to continue the payment behavior triggered by the payment trigger operation, or it may be to release the payment behavior triggered by the payment trigger operation, that is, to continue the payment behavior. For example, if the payment trigger operation is an operation for triggering the display of the payment code, the risk control operation corresponding to the payment trigger operation may be to prohibit the display of the payment code, and for another example, if the payment trigger operation is an operation for triggering a transfer, the risk control operation corresponding to the payment trigger operation may be to block the transfer, or it may be to interactively remind the user, and the user determines whether to continue the transfer, or it may be to release the transfer.

[0053] In some embodiments, it is necessary to determine the corresponding risk control operation according to the screen sharing state. For example, according to the mapping relationship between the preset screen sharing state and the risk control operation, the risk control operation mapped by the screen sharing state is obtained. For example, according to the screen sharing duration in the screen sharing state, the risk control operation mapped by the screen sharing duration is obtained. For another example, the screen sharing state is input into a trained risk control prediction model to obtain the risk control operation output by the risk control prediction model. Here, this specification does not limit the model structure, model parameters and model training method of the risk control prediction model. For example, the screenshots of the user device obtained at preset time intervals during screen sharing are input into a trained risk control prediction model to obtain the risk control operation output by the risk control prediction model.

[0054] In the embodiments of the present specification, when the user executes a payment trigger operation, it is identified whether the user is in a high-risk and vulnerable screen sharing environment based on the screen sharing status corresponding to the user device currently used by the user, and a risk control operation corresponding to the payment trigger operation is performed. By sensing whether the potential victim of defraud is in a screen sharing environment, pre-protection, early warning or timely blocking and interception can be performed, which can significantly reduce the risk of the user being led to fraud in the screen sharing state, and can greatly reduce the risk of the user's funds being defrauded in the payment scenario.

[0055] In some embodiments, the performing of the risk control operation corresponding to the payment triggering operation according to the screen sharing state includes: determining corresponding risk quantification information according to the screen sharing state; performing the risk control operation corresponding to the payment triggering operation according to the risk quantification information. In some embodiments, the risk quantification information is used to quantify the risk level of the current payment environment of the user device. For example, the risk quantification information may be in numerical form, or may be in string form (for example, high risk, medium risk, low risk, etc.). This specification does not limit the specific form of the risk quantification information. In some embodiments, it is necessary to first determine the corresponding risk quantification information based on the screen sharing state. For example, the screen sharing state is input into a preset functional relationship to obtain the risk quantification information output by the functional relationship. For example, the screen sharing duration in the screen sharing state is input into a preset functional relationship to obtain the risk quantification information output by the functional relationship. For another example, the screen sharing state is input into a trained risk control quantitative model to obtain the risk quantification information output by the risk control quantitative model. Here, this specification does not limit the model structure, model parameters and model training method of the risk control quantitative model. For example, screenshots of the user device obtained at preset time intervals during screen sharing are input into a trained risk control quantitative model to obtain the risk quantification information output by the risk control quantitative model. In some embodiments, it is also necessary to determine the risk control operation corresponding to the payment trigger operation currently performed by the user based on the obtained risk quantification information, and perform the risk control operation. For example, if the risk quantification information is in numerical form, then the risk control operation mapped to the numerical interval in which the risk quantification information falls can be used as the risk control operation corresponding to the payment trigger operation based on the numerical interval in which the risk quantification information falls and the mapping relationship between the preset numerical interval and the risk control operation. For another example, if the risk quantification information is in the form of a string, then the risk control operation mapped to the risk quantification information can be used as the risk control operation corresponding to the payment trigger operation based on the mapping relationship between the preset string and the risk control operation.

[0056] In some embodiments, the screen sharing state includes the operation record and screen sharing duration information corresponding to the user device during screen sharing; wherein, the determining the corresponding risk quantification information according to the screen sharing state includes: determining the corresponding risk quantification information according to the operation record, the screen sharing duration information, the device risk quantification information corresponding to the user device, and the transaction level quantification information corresponding to the user. In some embodiments, the operation record includes operation information related to at least one operation performed by the user device during screen sharing, and the operation information includes but is not limited to operation time, operation target, operation object, operation content, operation type, operation result, etc., and this specification does not limit this. In some embodiments, the at least one operation can be classified according to the operation information of at least one operation in the operation record, such as page access class, fund operation class, account operation class, etc., and each classification corresponds to a preset variable, so that the variable corresponding to the operation record can be obtained. In some embodiments, the device risk quantification information can be formed by a preset algorithm according to the device information of the user device, such as the model, operating system version, whether the device has been changed, whether it is a commonly used device, etc., and the device risk quantification information is used to characterize the risk level of the user device in the form of a variable (for example, trustworthy, medium risk, high risk, etc.). In some embodiments, the user's historical transactions are segmented according to the time dimension to dynamically monitor the user's transaction volume. The user's transaction volume quantitative information is obtained, and the transaction volume quantitative information is used to characterize the user's transaction risk level in the form of variables. In some embodiments, the variables corresponding to the operation record, the screen sharing duration information, the device risk quantitative information, and the transaction volume quantitative information can be weighted and summed after being multiplied by the custom weights corresponding to each variable, and the corresponding risk quantitative information is determined according to the calculated result. The calculation result can be directly used as the risk quantitative information, or the calculation result can be multiplied by a preset custom weight to obtain the risk quantitative information, or the calculation result can be obtained according to the preset mapping relationship. The risk quantitative information mapped by the calculation result or the risk quantitative information mapped by the numerical interval in which the calculation result falls, or the calculation result can be input into a trained risk quantitative model to obtain the risk quantitative information output by the model. Here, this specification does not limit the specific method of obtaining the risk quantitative information according to the calculation result obtained by weighted summation.

[0057] In some embodiments, the determining of the corresponding risk quantification information according to the operation record, the screen sharing duration information, the device risk quantification information corresponding to the user device, and the transaction volume quantification information corresponding to the user includes: determining the corresponding risk quantification information according to the operation record, the screen sharing duration information, the device risk quantification information corresponding to the user device, the transaction volume quantification information corresponding to the user, and the social relationship quantification information between the user and the payment object corresponding to the payment trigger operation. In some embodiments, if there is a corresponding payment object for the payment trigger operation, for example, if the payment trigger operation is an operation for triggering a transfer or sending a red envelope, at this time, the payment object corresponding to the payment trigger operation is a transfer object or a red envelope sending object. In this case, it is necessary to quantify the social relationship between the user and the payment object to obtain the corresponding social relationship quantification information, and the social relationship quantification information is used to characterize the risk level of the social relationship between the user and the payment object in the form of a variable. For example, the corresponding social relationship quantification information can be generated according to whether the payment object is a friend of the user, the historical transaction record between the user and the payment object, the transaction content of this payment, and the user's message notes on this payment. This specification does not limit this. In some embodiments, the variables corresponding to the operation records, screen sharing time information, device risk quantification information, transaction volume quantification information, and social relationship quantification information can be multiplied by the custom weights corresponding to each variable and then summed up. The corresponding risk quantification information is determined based on the calculated results. The specific method for obtaining the risk quantification information based on the calculation results obtained by weighted summation has been described in detail in the previous text and will not be repeated here.

[0058] In some embodiments, the screen sharing state includes the screen content shared by the user device; wherein, executing the risk control operation corresponding to the payment triggering operation according to the screen sharing state includes: executing the risk control operation corresponding to the payment triggering operation according to the screen content shared by the user device. In some embodiments, the screen sharing state includes the screen content shared by the user device, and the screen content includes but is not limited to the page identification, page name, page type, page presentation content (e.g., text or image), page sharing duration, page start sharing time, page end sharing time, etc. of the current display page of the user device during screen sharing, and this specification does not limit this. In some embodiments, the risk control operation corresponding to the payment trigger operation currently performed by the user can be determined based on the screen content shared by the user device, and the risk control operation can be performed. For example, the sensitivity level corresponding to the currently displayed page is determined based on the page identifier of the currently displayed page of the user device during screen sharing in the screen content, and then based on the mapping relationship between the preset sensitivity level and the risk control operation, the risk control operation mapped to the sensitivity level is used as the risk control operation corresponding to the payment trigger operation. For another example, based on the page type of the currently displayed page of the user device during screen sharing in the screen content, it is first determined whether the currently displayed page is a sensitive page. If so, based on the time interval into which the page sharing time of the sensitive page in the screen content falls, and based on the mapping relationship between the preset time interval and the risk control operation, the risk control operation mapped to the time interval is used as the risk control operation corresponding to the payment trigger operation.

[0059] In some embodiments, the performing of the risk control operation corresponding to the payment triggering operation according to the screen content shared by the user device includes: performing the risk control operation corresponding to the payment triggering operation according to the sensitive information contained in the screen content shared by the user device. In some embodiments, the sensitive information contained in the page presentation content can be obtained based on the page presentation content of the current display page of the user device during the screen sharing in the screen content. The specific method can be to obtain the sensitive information contained in the page presentation content by performing keyword recognition on the text information in the page presentation content, or to obtain the sensitive information contained in the page presentation content by performing image content recognition on the image information in the page presentation content. This specification does not limit the method of obtaining sensitive information from the page presentation content. In some embodiments, after obtaining sensitive information contained in the screen content shared by the user device, the risk control operation corresponding to the payment trigger operation currently performed by the user can be determined based on the sensitive information, and the risk control operation can be performed. For example, based on the sensitivity level corresponding to the sensitive information and based on the mapping relationship between the preset sensitivity level and the risk control operation, the risk control operation mapped by the sensitivity level is used as the risk control operation corresponding to the payment trigger operation. For another example, the sensitive information is directly input into a trained risk control prediction model, and the risk control operation output by the model is used as the risk control operation corresponding to the payment trigger operation.

[0060] In some embodiments, the performing of the risk control operation corresponding to the payment triggering operation according to the sensitive information contained in the screen content shared by the user device includes: performing the risk control operation corresponding to the payment triggering operation according to the association information between the sensitive information contained in the screen content shared by the user device and the screen presentation content of the user device within the preset time range before the screen sharing start time. In some embodiments, the preset time range can be a time range of a predetermined time from the screen sharing start time, or it can also be a time range from the last boot time or the last unlock time of the user device to the screen sharing start time, and this specification does not limit this. In some embodiments, the screen presentation content of the user device within the preset time range before the screen sharing start time includes but is not limited to the page identification, page name, page type, page presentation content (for example, text or image), page sharing duration, page start sharing time, page end sharing time, etc. of the current display page of the user device within the preset time range before the screen sharing is started, and this specification does not limit this. In some embodiments, based on the association information between the sensitive information contained in the screen content shared by the user device and the screen content presented by the user device within a preset time range before the screen sharing is started, the risk control operation corresponding to the payment trigger operation currently performed by the user is determined and the risk control operation is performed. The association information may refer to the degree of association between the sensitive information and the screen content, and the corresponding risk control operation is determined based on the degree of association. For example, based on the numerical interval into which the numerical value corresponding to the degree of association falls, and based on the mapping relationship between the preset numerical interval and the risk control operation, the risk control operation mapped by the numerical interval is used as the risk control operation corresponding to the payment trigger operation. Alternatively, the association information may also refer to the degree of guidance between the sensitive information and the screen content in semantic logic. The guidance degree is used to characterize the degree of guidance that the screen content plays on the sensitive information in semantic logic. Then, the corresponding risk control operation is determined based on the guidance degree. For example, based on the mapping relationship between the preset guidance degree and the risk control operation, the mapped risk control operation is used as the risk control operation corresponding to the payment trigger operation.

[0061] In some embodiments, the performing of the risk control operation corresponding to the payment trigger operation according to the sensitive information contained in the screen content shared by the user device includes: performing the risk control operation corresponding to the payment trigger operation according to the association information between the sensitive information contained in the screen content shared by the user device and the operation object corresponding to the payment trigger operation. In some embodiments, if the payment trigger operation is an operation for triggering the display of a payment code, the corresponding operation object is the payment code; if the payment trigger operation is an operation for triggering the entry into a payment page, the corresponding operation object is the payment page; if the payment trigger operation is an operation for triggering the opening or logging into a payment application, the corresponding operation object is the payment application; if the payment trigger operation is an operation for triggering a transfer or sending a red envelope, the corresponding operation object is a transfer object or a red envelope sending object. In some embodiments, based on the association information between the sensitive information contained in the shared screen content of the user device and the operation object corresponding to the payment trigger operation, the risk control operation corresponding to the payment trigger operation currently performed by the user is determined and the risk control operation is performed. The association information may refer to the degree of association between the sensitive information and the operation object, and the corresponding risk control operation is determined based on the degree of association. For example, based on the mapping relationship between the preset degree of association and the risk control operation, the mapped risk control operation is used as the risk control operation corresponding to the payment trigger operation. Alternatively, the association information may also refer to the degree of semantically logical guidance between the sensitive information and the operation object. The guidance degree is used to characterize the degree of semantically logical guidance of the sensitive information on the operation object. Then, the corresponding risk control operation is determined based on the guidance degree. For example, based on the numerical interval into which the numerical value corresponding to the guidance degree falls, and based on the mapping relationship between the preset numerical interval and the risk control operation, the risk control operation mapped by the numerical interval is used as the risk control operation corresponding to the payment trigger operation.

[0062] In some embodiments, the screen sharing state includes the operation record corresponding to the user device during the screen sharing period; wherein, the performing the risk control operation corresponding to the payment triggering operation according to the screen sharing state includes: performing the risk control operation corresponding to the payment triggering operation according to the operation record corresponding to the user device during the screen sharing period. In some embodiments, the operation record includes operation information related to at least one operation performed by the user device during the screen sharing period, and the operation information includes but is not limited to the operation time, operation target, operation object, operation content, operation type, operation result, etc., and this specification does not limit this. In some embodiments, the risk control operation corresponding to the payment triggering operation currently performed by the user can be determined according to the operation record corresponding to the user device during the screen sharing period, and the risk control operation is performed, for example, the operation record is input into a trained risk control prediction model, and the risk control operation output by the model is used as the risk control operation corresponding to the payment triggering operation, and for another example, according to the operation type of at least one operation in the operation record, and based on the preset mapping relationship between the operation type and the risk control operation, the risk control operation mapped by the operation type is used as the risk control operation corresponding to the payment triggering operation.

[0063] In some embodiments, the performing of the risk control operation corresponding to the payment trigger operation according to the operation record corresponding to the user device during screen sharing includes: performing the risk control operation corresponding to the payment trigger operation according to the sensitive operation involved in the operation record corresponding to the user device during screen sharing. In some embodiments, the sensitive operation involved in at least one operation can be determined based on the operation information of at least one operation in the operation record, and then the risk control operation corresponding to the payment trigger operation currently performed by the user can be determined based on the sensitive operation, and the risk control operation can be performed. For example, the risk control operation mapped by the sensitive level information can be used as the risk control operation corresponding to the payment trigger operation based on the mapping relationship between the preset sensitive level information and the risk control operation. For another example, the operation content of the sensitive operation can be input into a trained risk control prediction model, and the risk control operation output by the model can be used as the risk control operation corresponding to the payment trigger operation.

[0064] In some embodiments, the performing of the risk control operation corresponding to the payment triggering operation according to the sensitive operation involved in the operation record corresponding to the user device during the screen sharing period includes: performing the risk control operation corresponding to the payment triggering operation according to the association information between the sensitive operation involved in the operation record corresponding to the user device during the screen sharing period and the historical operation performed by the user device within a preset time range before the screen sharing start time. In some embodiments, the preset time range can be a time range of a predetermined time from the screen sharing start time, or it can also be a time range from the last boot time or the last unlock time of the user device to the screen sharing start time, and this specification does not limit this. In some embodiments, the risk control operation corresponding to the payment triggering operation currently performed by the user can be determined according to the association information between the operation information of at least one operation in the operation record corresponding to the user device during the screen sharing period and the operation information of the historical operation performed by the user device within the preset time range before the screen sharing start time, and the risk control operation is performed, wherein the operation information includes but is not limited to the operation time, operation target, operation object, operation content, operation type, operation result, etc., and this specification does not limit this. In some embodiments, the association information may refer to the degree of association between the sensitive operation and the historical operation, and the corresponding risk control operation is determined based on the degree of association. For example, based on the numerical interval into which the numerical value corresponding to the degree of association falls, and based on the mapping relationship between the preset numerical interval and the risk control operation, the risk control operation mapped by the numerical interval is used as the risk control operation corresponding to the payment trigger operation. Alternatively, the association information may also refer to the degree of guidance of the historical operation for the sensitive operation, and the guidance degree is used to characterize the degree of guidance of the historical operation on the sensitive operation, and then the corresponding risk control operation is determined based on the guidance degree. For example, based on the mapping relationship between the preset guidance degree and the risk control operation, the mapped risk control operation is used as the risk control operation corresponding to the payment trigger operation.

[0065] In some embodiments, the performing of the risk control operation corresponding to the payment trigger operation according to the sensitive operation involved in the operation record corresponding to the user device during screen sharing includes: performing the risk control operation corresponding to the payment trigger operation according to the association information between the sensitive operation involved in the operation record corresponding to the user device during screen sharing and the payment trigger operation. In some embodiments, the risk control operation corresponding to the payment trigger operation currently performed by the user can be determined and performed based on the operation information of the sensitive operation involved in the corresponding operation record of the user device during screen sharing and the association information between the payment trigger operation, wherein the association information may refer to the degree of association between the sensitive operation and the payment trigger operation, and the corresponding risk control operation is determined based on the degree of association. For example, based on the mapping relationship between the preset degree of association and the risk control operation, the risk control operation mapped by the degree of association is used as the risk control operation corresponding to the payment trigger operation. Alternatively, the association information may also refer to the degree of guidance of the sensitive operation for the payment trigger operation, and the guidance degree is used to characterize the degree of guidance of the sensitive operation on the payment trigger operation. Then, the corresponding risk control operation is determined based on the guidance degree. For example, based on the numerical range into which the guidance degree falls and based on the mapping relationship between the preset numerical range and the risk control operation, the risk control operation mapped by the numerical range is used as the risk control operation corresponding to the payment trigger operation.

[0066] Figure 2 A schematic diagram of a device for payment risk control provided in an embodiment of this specification, the device for payment risk control (hereinafter referred to as "payment risk control device 1") can be implemented as all or part of an electronic device through software, hardware or a combination of both. According to some embodiments, the payment risk control device 1 includes a screen sharing state acquisition module 11 and a payment risk control module 12.

[0067] A screen sharing state obtaining module, configured to obtain, in response to a payment triggering operation performed by a user, a screen sharing state corresponding to a user device currently used by the user;

[0068] The payment risk control module is configured to execute a risk control operation corresponding to the payment triggering operation according to the screen sharing state if the screen sharing state indicates that the user device is currently in screen sharing.

[0069] In some embodiments, performing a risk control operation corresponding to the payment triggering operation according to the screen sharing state includes: determining corresponding risk quantification information according to the screen sharing state; and performing a risk control operation corresponding to the payment triggering operation according to the risk quantification information.

[0070] In some embodiments, the screen sharing status includes the operation records corresponding to the user device during screen sharing and the screen sharing duration information; wherein, determining the corresponding risk quantification information based on the screen sharing status includes: determining the corresponding risk quantification information based on the operation records, the screen sharing duration information, the device risk quantification information corresponding to the user device, and the transaction level quantification information corresponding to the user.

[0071] In some embodiments, the corresponding risk quantification information is determined based on the operation record, the screen sharing duration information, the device risk quantification information corresponding to the user device, and the transaction level quantification information corresponding to the user, including: determining the corresponding risk quantification information based on the operation record, the screen sharing duration information, the device risk quantification information corresponding to the user device, the transaction level quantification information corresponding to the user, and the social relationship quantification information between the user and the payment object corresponding to the payment trigger operation.

[0072] In some embodiments, the screen sharing status includes the screen content shared by the user device; wherein, executing the risk control operation corresponding to the payment triggering operation according to the screen sharing status includes: executing the risk control operation corresponding to the payment triggering operation according to the screen content shared by the user device.

[0073] In some embodiments, performing a risk control operation corresponding to the payment triggering operation based on the screen content shared by the user device includes: performing a risk control operation corresponding to the payment triggering operation based on sensitive information contained in the screen content shared by the user device.

[0074] In some embodiments, the risk control operation corresponding to the payment trigger operation is performed based on the sensitive information contained in the screen content shared by the user device, including: performing the risk control operation corresponding to the payment trigger operation based on the association information between the sensitive information contained in the screen content shared by the user device and the screen presentation content of the user device within a preset time range before the screen sharing is started.

[0075] In some embodiments, the performing of the risk control operation corresponding to the payment trigger operation based on the sensitive information contained in the screen content shared by the user device includes: performing the risk control operation corresponding to the payment trigger operation based on the association information between the sensitive information contained in the screen content shared by the user device and the operation object corresponding to the payment trigger operation.

[0076] In some embodiments, the screen sharing status includes the operation record corresponding to the user device during the screen sharing period; wherein, executing the risk control operation corresponding to the payment trigger operation according to the screen sharing status includes: executing the risk control operation corresponding to the payment trigger operation according to the operation record corresponding to the user device during the screen sharing period.

[0077] In some embodiments, performing a risk control operation corresponding to the payment trigger operation based on the operation record corresponding to the user device during screen sharing includes: performing a risk control operation corresponding to the payment trigger operation based on sensitive operations involved in the operation record corresponding to the user device during screen sharing.

[0078] In some embodiments, the performing of the risk control operation corresponding to the payment triggering operation based on the sensitive operations involved in the operation records corresponding to the user device during screen sharing includes: performing the risk control operation corresponding to the payment triggering operation based on the association information between the sensitive operations involved in the operation records corresponding to the user device during screen sharing and the historical operations performed by the user device within a preset time range before the screen sharing is started.

[0079] In some embodiments, the performing of the risk control operation corresponding to the payment trigger operation according to the sensitive operation involved in the operation record corresponding to the user device during screen sharing includes: performing the risk control operation corresponding to the payment trigger operation according to the association information between the sensitive operation involved in the operation record corresponding to the user device during screen sharing and the payment trigger operation.

[0080] The above device embodiments correspond to the method embodiments. For specific descriptions, please refer to the description of the method embodiments, which will not be repeated here. The device embodiments are obtained based on the corresponding method embodiments and have the same technical effects as the corresponding method embodiments. For specific descriptions, please refer to the corresponding method embodiments.

[0081] The embodiment of the present specification also provides a computer storage medium, which can store multiple instructions, and the instructions are suitable for being loaded by a processor to execute the method of the embodiment of the present specification.

[0082] The embodiments of the present specification also provide a computer program product, which stores at least one instruction, and the at least one instruction is loaded by the processor to execute the method of the embodiments of the present specification.

[0083] The embodiments of this specification also provide Figure 3 The structural diagram of the electronic device shown in FIG. Figure 3At the hardware level, the electronic device includes a processor, an internal bus, a network interface, a memory, and a non-volatile memory, and may also include hardware required for other services. The processor reads the corresponding computer program from the non-volatile memory into the memory and then runs it to implement the method of the embodiment of this specification.

[0084] The systems, devices, modules or units described in the above embodiments may be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

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

[0086] This specification is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of this specification. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes 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.

[0087] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate 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 A function specified in one or more boxes.

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

[0089] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0090] This specification may be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. This specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected through a communication network. In a distributed computing environment, program modules may be located in local and remote computer storage media, including storage devices.

[0091] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0092] The above description is only an embodiment of the present specification and is not intended to limit the present specification. For those skilled in the art, the present specification may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present specification shall be included in the scope of the claims of the present specification.

Claims

1. A method for payment risk control, comprising: In response to a payment triggering operation performed by a user, obtaining a screen sharing state corresponding to a user device currently used by the user; If the screen sharing status indicates that the user device is currently in screen sharing, a risk control operation corresponding to the payment triggering operation is performed according to the screen sharing status.

2. The method according to claim 1, wherein the step of executing a risk control operation corresponding to the payment triggering operation according to the screen sharing state comprises: Determining corresponding risk quantification information according to the screen sharing state; According to the risk quantification information, a risk control operation corresponding to the payment triggering operation is performed.

3. According to the method of claim 2, the screen sharing state includes the operation record corresponding to the user equipment during the screen sharing period and the screen sharing duration information; in, The determining corresponding risk quantification information according to the screen sharing state includes: Corresponding risk quantification information is determined according to the operation record, the screen sharing duration information, the device risk quantification information corresponding to the user device, and the transaction level quantification information corresponding to the user.

4. The method according to claim 3, wherein determining the corresponding risk quantification information according to the operation record, the screen sharing duration information, the device risk quantification information corresponding to the user device, and the transaction level quantification information corresponding to the user comprises: The corresponding risk quantification information is determined based on the operation record, the screen sharing duration information, the device risk quantification information corresponding to the user device, the transaction volume quantification information corresponding to the user, and the social relationship quantification information between the user and the payment object corresponding to the payment trigger operation.

5. The method according to claim 1, wherein the screen sharing state comprises a screen content of the user device being shared; in, The performing a risk control operation corresponding to the payment triggering operation according to the screen sharing state includes: According to the shared screen content of the user device, a risk control operation corresponding to the payment triggering operation is performed.

6. The method according to claim 5, wherein the step of performing a risk control operation corresponding to the payment triggering operation according to the shared screen content of the user device comprises: According to the sensitive information contained in the shared screen content of the user device, a risk control operation corresponding to the payment triggering operation is performed.

7. The method according to claim 6, wherein the step of performing a risk control operation corresponding to the payment triggering operation according to sensitive information contained in the shared screen content of the user device comprises: A risk control operation corresponding to the payment triggering operation is performed based on the association information between the sensitive information contained in the shared screen content of the user device and the screen presentation content of the user device within a preset time range before the screen sharing is started.

8. The method according to claim 6, wherein the step of performing a risk control operation corresponding to the payment triggering operation according to sensitive information contained in the shared screen content of the user device comprises: According to the association information between the sensitive information contained in the shared screen content of the user device and the operation object corresponding to the payment triggering operation, a risk control operation corresponding to the payment triggering operation is performed.

9. The method according to claim 1, wherein the screen sharing state comprises an operation record corresponding to the user device during screen sharing; in, The performing a risk control operation corresponding to the payment triggering operation according to the screen sharing state includes: According to the operation record corresponding to the user device during the screen sharing period, a risk control operation corresponding to the payment triggering operation is performed.

10. The method according to claim 9, wherein the step of performing a risk control operation corresponding to the payment triggering operation according to the operation record corresponding to the user device during screen sharing comprises: According to the sensitive operations involved in the operation records corresponding to the user device during screen sharing, a risk control operation corresponding to the payment triggering operation is performed.

11. The method according to claim 10, wherein the step of performing a risk control operation corresponding to the payment triggering operation according to the sensitive operation involved in the operation record corresponding to the user device during screen sharing comprises: According to the association information between the sensitive operations involved in the operation records corresponding to the user device during screen sharing and the historical operations performed by the user device within a preset time range before the screen sharing is started, a risk control operation corresponding to the payment triggering operation is performed.

12. The method according to claim 10, wherein the step of performing a risk control operation corresponding to the payment triggering operation according to the sensitive operation involved in the operation record corresponding to the user device during screen sharing comprises: According to the association information between the sensitive operation involved in the operation record corresponding to the user device during screen sharing and the payment triggering operation, a risk control operation corresponding to the payment triggering operation is performed.

13. A device for payment risk control, comprising: A screen sharing state obtaining module, configured to obtain, in response to a payment triggering operation performed by a user, a screen sharing state corresponding to a user device currently used by the user; The payment risk control module is configured to execute a risk control operation corresponding to the payment triggering operation according to the screen sharing state if the screen sharing state indicates that the user device is currently in screen sharing.

14. A storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 12 are implemented.

15. 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 steps of the method as claimed in any one of claims 1 to 12.

16. A computer program product having at least one instruction stored thereon, characterized in that: When the at least one instruction is executed by the processor, the steps of the method described in any one of claims 1 to 12 are implemented.

Images