Risk Identification Method and Device

Abstract

The present disclosure provides a risk identification method and apparatus. The method is applied to an e-wallet client. The e-wallet belongs to a first service provider. An operation interface provided by the e-wallet client includes an operation position of a second service provider. The method includes: receiving login information of a user logging in to the operation position; in response to the login information, sending a trigger message to a risk control system of the first service provider, where the trigger message is used to trigger the risk control system of the first service provider to collect user information and send the user information to a risk control system of the second service provider, so that the risk control system of the second service provider performs risk identification on an operation behavior of the user at the operation position.

Description

Technical Field

[0001] The present disclosure relates to the technical field of risk identification, and more particularly, to a risk identification method and apparatus. Background Art

[0002] An electronic wallet is a commonly used payment tool in e-commerce shopping activities. The emergence of the electronic wallet has enabled users to enjoy more convenient and efficient services. Therefore, more and more users have registered and used the electronic wallet.

[0003] Many service providers, in order to utilize the user resources of the electronic wallet, embed their own operation positions on the electronic wallet to publish some marketing activities on this operation position. Since marketing activities usually have great benefits, in order to prevent users from cheating during the participation in the activities, a risk control system is required to identify the risks of the user's operation behavior.

[0004] However, for the case where the service provider publishing the marketing activity and the service provider of the electronic wallet are different service providers, since the user information belongs to the service provider of the electronic wallet, and the information of the user's participation in the activity belongs to the service provider publishing the marketing activity, when identifying the risks of the user's operation behavior, due to the data being distributed among different service providers, neither of these two service providers can perform effective risk prevention and control. Summary of the Invention

[0005] Embodiments of the present disclosure provide a risk identification method and apparatus to solve the above technical problems.

[0006] In a first aspect, a risk identification method is provided. The method is applied to an electronic wallet client. The electronic wallet belongs to a first service provider, and an operation interface provided by the electronic wallet client includes an operation position of a second service provider. The method includes: receiving login information of a user logging in to the operation position; in response to the login information, sending a trigger message to the risk control system of the first service provider, where the trigger message is used to trigger the risk control system of the first service provider to collect user information, and sending the user information to the risk control system of the second service provider, so that the risk control system of the second service provider can identify the risks of the user's operation behavior on the operation position.

[0007] In some embodiments, the user information includes one or more of the following information: account information, device information used, operation environment information, risk labels.

[0008] In some embodiments, the first service provider and the second service provider are service providers from different countries.

[0009] Second aspect, a risk identification method is provided. The method is applied to the risk control system of a first service provider, and the method includes: receiving trigger information sent by an e-wallet client. An operation interface provided by the e-wallet client includes an operation position of a second service provider. The trigger information is generated when a user logs in to the operation position. The e-wallet belongs to the first service provider, and the operation position belongs to the second service provider; in response to the trigger information, collecting user information; sending the user information to the risk control system of the second service provider, so that the risk control system of the second service provider can perform risk identification on the operation behavior of the user at the operation position according to the user information.

[0010] In some embodiments, the user information includes one or more of the following information: account information, device information used, operation environment information, risk labels.

[0011] In some embodiments, the first service provider and the second service provider are service providers from different countries.

[0012] Third aspect, a risk identification method is provided. The method is applied to the risk control system of a second service provider, and the method includes: receiving user information sent by the risk control system of a first service provider. The user information is collected by the risk control system of the first service provider under the trigger of trigger information. The trigger information is generated when a user logs in to an operation position provided on an operation interface of an e-wallet client. The operation position belongs to the second service provider, and the e-wallet belongs to the first service provider; based on the user information, performing risk identification on the operation behavior of the user at the operation position.

[0013] In some embodiments, the user information includes one or more of the following information: account information, device information used, operation environment information, risk labels.

[0014] In some embodiments, the first service provider and the second service provider are service providers from different countries.

[0015] Fourth aspect, a risk identification device is provided. An e-wallet client is provided on the device. The e-wallet belongs to a first service provider. An operation interface provided by the e-wallet client includes an operation position of a second service provider. The device includes: a receiving unit, configured to receive login information of a user logging in to the operation position; a sending unit, configured to, in response to the login information, send trigger information to the risk control system of the first service provider. The trigger information is used to trigger the risk control system of the first service provider to collect user information and send the user information to the risk control system of the second service provider, so that the risk control system of the second service provider can perform risk identification on the operation behavior of the user at the operation position.

[0016] In some embodiments, the user information includes one or more of the following information: account information, device information used, operating environment information, risk labels.

[0017] In some embodiments, the first service provider and the second service provider are service providers from different countries.

[0018] In a fifth aspect, a risk identification device is provided. The device is a risk control system of a first service provider, and the device includes: a receiving unit, configured to receive a trigger message sent by an e-wallet client. An operation interface provided by the e-wallet client includes an operation position of a second service provider, and the trigger message is generated when a user logs in to the operation position. The e-wallet belongs to the first service provider, and the operation position belongs to the second service provider; a collection unit, configured to collect user information in response to the trigger message; a sending unit, configured to send the user information to the risk control system of the second service provider, so that the risk control system of the second service provider can perform risk identification on the operation behavior of the user at the operation position according to the user information.

[0019] In some embodiments, the user information includes one or more of the following information: account information, device information used, operating environment information, risk labels.

[0020] In some embodiments, the first service provider and the second service provider are service providers from different countries.

[0021] In a sixth aspect, a device is provided as the risk control system of the second service provider. The device includes: a receiving unit, configured to receive user information sent by the risk control system of the first service provider. The user information is collected by the risk control system of the first service provider under the trigger of a trigger message, and the trigger message is generated when a user logs in to an operation position provided on an operation interface of an e-wallet client. The operation position belongs to the second service provider, and the e-wallet belongs to the first service provider; a risk identification unit, configured to perform risk identification on the operation behavior of the user at the operation position based on the user information.

[0022] In some embodiments, the user information includes one or more of the following information: account information, device information used, operating environment information, risk labels.

[0023] In some embodiments, the first service provider and the second service provider are service providers from different countries.

[0024] In a seventh aspect, a risk identification device is provided, including a memory and a processor. An executable code is stored in the memory, and the processor is configured to execute the executable code to implement the method as described in the first aspect, the second aspect, or the third aspect.

[0025] In an eighth aspect, a computer-readable storage medium is provided. An executable code is stored on the computer-readable storage medium, and when the executable code is executed, the method as described in the first aspect, the second aspect, or the third aspect can be implemented.

[0026] In a ninth aspect, a computer program product is provided, including an executable code. When the executable code is executed, the method as described in the first aspect, the second aspect, or the third aspect can be implemented.

[0027] In the embodiments of the present disclosure, the login information of the user logging in to the operation position is used as a trigger condition to trigger the risk control system of the first service provider to collect user information. Thus, the risk control system of the first service provider can collect user information in real time and send the user information to the risk control system of the second service provider in real time. The risk control system of the second service provider can obtain the user information in real time, and thus can perform real-time risk identification on the operation behavior of the user. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] Figure 1 FIG. is a schematic structural diagram of a risk control joint defense system provided by the embodiments of the present disclosure.

[0029] Figure 2 FIG. is a schematic flowchart of a risk identification method provided by the embodiments of the present disclosure.

[0030] Figure 3 FIG. is a schematic structural diagram of a risk identification device provided by the embodiments of the present disclosure.

[0031] Figure 4 FIG. is a schematic structural diagram of another risk identification device provided by the embodiments of the present disclosure.

[0032] Figure 5 FIG. is a schematic structural diagram of another risk identification device provided by the embodiments of the present disclosure.

[0033] Figure 6 FIG. is a schematic structural diagram of another risk identification device provided by the embodiments of the present disclosure. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0034] Next, the technical solutions in the embodiments of the present disclosure will be clearly and completely described with reference to the accompanying drawings of the embodiments of the present disclosure. Apparently, the described embodiments are only a part of the embodiments of the present disclosure, rather than all of the embodiments.

[0035] An e-wallet is a commonly used payment tool in e-commerce shopping activities. Electronic currency, such as e-cash, e-change, and e-bank cards, is stored in the e-wallet. The e-wallet can also be bound to a physical bank card. When binding a physical bank card, according to the requirements of different issuing banks, information such as the cardholder's name, ID number, card number, and reserved mobile phone number is sent to the bank side for verification. After the verification is passed, the card binding operation is completed. After successful binding, the bound bank card can be used for payment transactions through the e-wallet, and there is no need to use the physical bank card anymore. Users can use the e-wallet to recharge mobile phone bills, buy data traffic, and pay various living bills, such as electricity bills, water bills, Internet bills, and credit card repayments.

[0036] Users can download the e-wallet client on the terminal device and then use the e-wallet for transactions. The emergence of the e-wallet allows users to enjoy more convenient and efficient services. Users don't need to carry a large amount of cash when going out and can directly conduct transactions through the e-wallet. Therefore, more and more users have registered and used the e-wallet.

[0037] The terminal device in this disclosure can refer to a device that can provide the e-wallet client to users. The terminal devices in the embodiments of this disclosure can be mobile phones, tablets (Pads), laptop computers, handheld computers, mobile Internet devices (MIDs), wearable devices, virtual reality (VR) devices, and augmented reality (AR) devices.

[0038] With the popularization of e-wallets, many service providers (also known as business parties or merchants) have launched marketing activities on e-wallets to utilize the user resources of e-wallets and promote their own products.

[0039] For example, the service provider can embed its own operation position in the e-wallet, that is, there is an operation position of the service provider on the operation interface of the e-wallet client (or application (APP)). The service provider can launch its own marketing activities on this operation position. The operation position can be understood as an interface to enter the marketing activity interface. This operation position can be set at any position on the operation interface, such as the middle position, the upper left corner, the lower right corner, etc. This operation position can be presented in the form of a nine-square grid, a four-square grid, etc. After the user opens the e-wallet APP, they can see the marketing activities provided by the service provider on the operation interface. By clicking on the corresponding position, the user can participate in the marketing activities provided by the service provider.

[0040] Taking Alipay as an example, on the home page of Alipay, we can see one or more activity interfaces (or activity entrances), such as interfaces for movie shows, Gaode taxi-hailing, food delivery, claiming consumption vouchers, and claiming gas vouchers. The section or column where these activity interfaces are located can be understood as the operation position of the present disclosure embodiment. This operation position is available for multiple service providers to launch their own marketing activities. After the user clicks on the activity displayed on this operation position, the operation interface of the e-wallet can directly jump to the activity interface provided by the service provider. The activity interface can display the specific information of the marketing activity provided by the service provider, and the user can claim corresponding rewards according to their needs.

[0041] The present disclosure embodiment does not make specific limitations on the form of the marketing activity. The marketing activity can be, for example, claiming rewards. Claiming rewards can be, for example, claiming coupons or consumption vouchers, claiming gifts, participating in a lottery, etc. Consumption vouchers can be, for example, full reduction vouchers, no-threshold vouchers, etc.

[0042] Since marketing activities usually have great benefits, in order to prevent users from cheating during the participation in the activities (commonly known as "taking advantage of loopholes") and affecting the interests of service providers, it is necessary to identify the risk of users' operation behaviors. Especially for new user acquisition activities, since the benefits are relatively high, many users will use various means, such as changing devices, registering with different mobile phone numbers, and gang operations, to claim new user benefits, which will have a great impact on the interests of service providers.

[0043] In order to identify users' cheating behaviors, it is necessary for the risk control system to conduct a risk assessment on users' operation behaviors to identify whether there is a risk of cheating in users' operation behaviors. Common risk types can include, for example, same-person risk, device cheating, gangs, blacklisted users, etc.

[0044] The risk control system can achieve risk assessment through a risk control engine. The risk control engine can, in the way of real-time strategies, restrict transactions, limit permissions, conduct identity verification, etc. on events with risks. This part is the core of the risk control system. The risk control engine can call a rule engine, a model engine, and a data engine to conduct real-time risk control. The risk control engine mainly conducts prevention and control through users' data. For example, it discriminates the risk of the current operation based on users' historical behaviors, which is also the most widely used risk prevention and control method in the industry.

[0045] The risk control system can obtain user information and the current marketing event participated by the user, and conduct risk identification on the marketing event based on the user information. The marketing event can include the type of operation, such as the type of activity participated in, the number of times and amount of rewards claimed, etc. User information can include one or more of the following information: account information, device information, operation time information, operation environment information, risk tags, etc.

[0046] Account information may refer to the account information used by a user to log in to the operation platform. Such account information may be the account information of an e-wallet, and the account information may be information such as a user name. Device information may refer to the information of the device used by a user to log in to the operation platform. Device information may include the Internet Protocol (IP) address of the terminal device, information about the operating system, etc. Operating environment information may refer to the environment information in which the electronic device client runs. Risk tags can be used to indicate the risk level of a user being a risky user. Risk tags may include, for example, a whitelist, a blacklist, and a gray list.

[0047] If the risk control system identifies a marketing event as a risky event, the risk control system may intercept the marketing event. For example, the risk control system may intercept a user's reward claiming event, or prevent the user from verifying the claimed reward. If the risk control system identifies that a marketing event is risk-free, the risk control system may allow the user to claim a reward or verify the claimed reward.

[0048] The embodiments of the present disclosure do not specifically limit the manner in which the risk control system performs risk identification.

[0049] As an example, if a user's risk tag is high risk, or the user is on the blacklist, the risk control system may identify the user's operation behavior as a risky event and intercept the event.

[0050] As another example, if it is detected that the account information of a user participating in a marketing activity has been used before, that is, the account has claimed a reward or verified a reward before, the risk control system may identify the user's current operation behavior as a risky event and intercept the event.

[0051] As yet another example, if it is detected that the device used by a user is a tampered device, the risk control system may identify the operation behavior of the user on this device as a risky event and intercept the event.

[0052] As still another example, if the same IP participates in marketing activities frequently within a short period of time, or if the same IP switches accounts frequently within a short period of time, the risk control system may identify the marketing events participated in by this IP as risky events and perform corresponding interceptions.

[0053] With the vigorous development of the internationalization strategy, strategic projects for business cooperation between different countries have emerged. Among them, A+ Rewards marketing is a newly emerging key strategic-level business. A+ Rewards can be understood as the A+ side embedding its own operation position in the e-wallets of other countries and carrying out marketing activities in the name of A+ to drive A+ marketing signed users and A+ transactions. The service providers for A+ marketing activities are different from those of e-wallets. For example, the service providers for A+ marketing activities and e-wallets are service providers from different countries. Taking the Philippine e-wallet Gcash as an example, a business company in China can embed its own operation position in Gcash so that users in the Philippines can participate in the activities and drive the signed users or transactions of the Chinese business company.

[0054] Since the service providers for A+ marketing activities are different from those of e-wallets, the service provider of the e-wallet will be referred to as the first service provider and the service provider of A+ marketing activities will be referred to as the second service provider below. The second service provider is the organizer of the marketing activities. The second service provider can publish its own marketing activities on the e-wallet.

[0055] Most of the marketing activities are funded by the second service provider and configured on the second service provider side. That is, the second service provider invests a large amount of funds in the marketing activities. Therefore, the second service provider needs to conduct risk prevention and control for the marketing activities. Especially for Southeast Asian e-wallets, due to the very active black production in Southeast Asian e-wallets, the second service provider must conduct anti-fraud risk prevention and control for the marketing activities in this mode.

[0056] Since the operation position of the second service provider depends on the e-wallet of the first service provider, the user information belongs to the first service provider. That is, only the first service provider can obtain the user information, while the second service provider cannot obtain the user information, which causes great difficulties for the second service provider to conduct marketing anti-fraud risk prevention and control. In addition, since the marketing activities are configured on the second service provider, the first service provider cannot perceive the user's award-winning event. Therefore, the first service provider cannot conduct risk prevention and control either. In summary, due to the data fragmentation of user information and marketing events, neither the second service provider nor the first service provider can conduct effective risk prevention and control.

[0057] Related technologies have proposed a solution. The second service provider can obtain user information offline and then identify risks for the user's operation behavior based on the user information. Specifically, the first service provider can extract user information in the form of an offline data table and then transmit it to the second service provider through the secure file transfer protocol (SFTP). The second service provider then imports the user information into the risk control system of the second service provider, and the risk control system of the second service provider can perform risk interception based on the user information. The above solution has the following disadvantages:

[0058] 1. Slow timeliness. It takes one day for the first service provider to extract data, and then transfer it to the second service provider. The second service provider then imports the data into its risk control system, which also takes one day. Therefore, it takes two days from the data extraction by the first service provider to the receipt of data by the risk control system of the second service provider. In summary, the above solution has the problem of slow timeliness.

[0059] 2. Low data accuracy rate. Due to the two-day data transmission timeliness, when the risk control system of the second service provider uses the data, the data is actually two days old. During these two days, if user information changes or new users appear, the risk control system of the second service provider cannot perceive it and can only rely on the existing data. Especially for the new user acquisition activity, since all users are new users, the risk control system of the second service provider does not have time to obtain user information, and the risk control is basically in a naked state. And the benefits of the new user acquisition activity are relatively high, and the risk is higher than that of other activities. Therefore, the solution using offline data cannot meet the risk control requirements.

[0060] Based on this, the embodiments of the present disclosure provide a risk identification method. Taking the user's login to the operation position as a trigger condition to trigger the risk control system of the first service provider to collect user information, so that the risk control system of the first service provider can collect user information in real time. In addition, the risk control systems of the first service provider and the second service provider are connected, so that the risk control system of the second service provider can obtain the user information transmitted by the risk control system of the first service provider in real time. In this way, the risk control system of the second service provider can obtain user information in real time, and thus can perform real-time risk identification on the user's operation behavior.

[0061] For ease of description, hereinafter, the risk control system of the first service provider will be referred to as the first risk control system, and the risk control system of the second service provider will be referred to as the second risk control system. The first service provider and the second service provider are different service providers. For example, the first service provider and the second service provider belong to service providers from different countries, or the first service provider and the second service provider are different companies in the same country.

[0062] Figure 1 is the architecture diagram of the risk control joint defense system applicable to the embodiments of the present disclosure. Figure 1 The risk control joint defense system shown may include an e-wallet client 110, a first risk control system 120, and a second risk control system 130. The e-wallet belongs to the first service provider, and the first risk control system can collect user information of the e-wallet. The e-wallet may be, for example, Gcash.

[0063] The operation interface provided by the e-wallet client 110 includes the operation positions of the second service provider. On these operation positions, the second service provider can launch some marketing activities. By clicking on these operation positions, users can participate in these marketing activities.

[0064] The second risk control system is directly connected to the first risk control system, and the first risk control system can transmit data to the second risk control system in real time.

[0065] Figure 2 It is a risk identification method provided by an embodiment of the present disclosure. Figure 2 The method shown can be applied to the e-wallet client, the first risk control system, and the second risk control system. Figure 2 The method shown may include steps S210 to S250.

[0066] In step S210, the client of the e-wallet receives the login information of the user logging in to the operation position.

[0067] The user can open the e-wallet client on the terminal device. The operation page of the e-wallet client displays the operation positions of the second service provider. The second service provider can launch some marketing activities on these operation positions. By clicking on these operation positions, the user can enter the activity interface. The login information of the user logging in to the operation position can be understood as the event information of the user entering the operation position or participating in the marketing activity.

[0068] In step S220, the client of the e-wallet responds to the login information and sends a trigger message to the first risk control system.

[0069] After detecting the user's login information, the client of the e-wallet can generate a virtual trigger event and send a trigger message to the risk control system of the first service provider.

[0070] In step S230, after receiving the trigger message, the first risk control system responds to the trigger message and collects user information.

[0071] In step S240, the first risk control system sends the user information to the second risk control system.

[0072] After collecting the user information, the first risk control system can send the user information to the second risk control system through a direct connection channel. In this way, the risk control system of the second service provider can obtain the user information in real time.

[0073] The virtual event generated by the user logging in to the operation position can not only be used as a trigger message but also as a carrier of information to carry the user information. That is, the first risk control system can transmit the user information to the second risk control system through this trigger event.

[0074] User information can be stored on the server side of the e-wallet. After receiving the trigger information, the first risk control system can obtain the user's information from the server side of the e-wallet. When collecting user information, the first risk control system can collect only the data related to risk identification. For example, to protect the user's privacy, the first risk control system only collects information such as the user's account information, device information, environmental information, and risk labels, and does not collect other private information of the user.

[0075] In some embodiments, the first risk control system can also encrypt the collected user information and then transmit the encrypted data to the second risk control system. After receiving the data, the second risk control system can decrypt it using the corresponding decryption method to obtain the user information. This method can further enhance the security protection of user information to prevent attackers from stealing user information and causing the leakage of user information.

[0076] In some embodiments, the first risk control system can collect the information of only the users who log in to the operation position. For example, when user X uses the e-wallet client and logs in to the operation position of the second service provider, the e-wallet client sends trigger information to the first risk control system. After receiving the trigger information, the first risk control system can obtain the relevant information of user X from the server side of the e-wallet and then send the relevant information of user X to the second risk control system. This solution can reduce the amount of data collected and transmitted by the first service provider, thereby improving the speed of data collection and transmission, enabling the second risk control system to obtain the user's information in a timely manner.

[0077] Of course, if there are many users logging in to the operation position, the first risk control system can also collect the information of multiple users at the same time and then send the information of multiple users to the second risk control system.

[0078] In step S250, the second risk control system can identify the risk of the user's operation behavior based on the user information.

[0079] After the user enters the operation position, the second service provider can perceive the user's operation behavior on the operation position, and thus can collect marketing events related to the user, such as prize-winning events, reward cancellation events, etc. The second risk control system can associate the user information sent by the first risk control system with the marketing events collected by the first service provider through the association field, that is, it can integrate the information of the same user collected by the first risk control system and the second service provider, so as to judge whether the user's operation behavior has risks. The association field can be field information that can uniquely identify the user, and this association field can be, for example, the user's name, the user's ID number, etc.

[0080] In the embodiments of the present disclosure, the operation behavior of a user on the operation platform may be referred to as a marketing event. The second risk control system may determine whether there is a risk of fraud in the marketing event based on the data obtained from the first risk control system and the data it holds itself. When it is determined that there is a risk in the marketing event, the second risk control system may reject the user's award collection or reward cancellation. When it is determined that there is no risk in the marketing event, the second risk control system may allow the user to collect the award or cancel the reward. Some judgment methods are illustrated below.

[0081] If the risk label of the user is high risk, or the user is on the blacklist, the second risk control system may intercept the user's award collection event or prevent the user from canceling the collected reward.

[0082] If the device information used by the user has been used before, that is, the user or other users have used this device to collect awards or have already canceled the awards, the second risk control system may also intercept the user's award collection event or prevent the user from canceling the collected reward.

[0083] If the account information of the user has been used before, that is, the user of this account has collected awards or has already canceled the awards before, the second risk control system may also intercept the user's award collection event or prevent the user from canceling the collected reward.

[0084] When it is determined that there is a risk in the marketing event, the second risk control system may also add the user corresponding to the marketing event to the blacklist. In this way, when the user participates in a marketing activity next time, the operation behavior of the user can be directly rejected without data analysis.

[0085] Of course, in some embodiments, based on the existing data, the second risk control system may not be able to directly determine whether there is a risk in the marketing event. For this situation, the second risk control system may further determine whether the marketing event has a risk through means such as identity verification, so as to improve the accuracy of risk judgment.

[0086] The methods of identity verification may include one or more of the following: mobile phone SMS verification, verification code verification, password verification, security question verification, device verification, and real-name authentication, etc. Device verification may be, for example, verifying whether the SIM card corresponding to the mobile phone number is used in the current device. The methods of real-name authentication include but are not limited to the following methods: ID card OCR verification, face verification, live detection, etc.

[0087] The solution of the embodiment of the present disclosure can solve the problems of slow timeliness and low data accuracy in the related art. In the solution of the embodiment of the present disclosure, user information is collected and transmitted in real time. Therefore, as long as the user logs in to the operation position, the second risk control system can obtain the latest and most real-time data, and there is no time difference in the data obtained by the second risk control system. In addition, since user information is collected and called in real time, the second risk control system obtains the latest data of the user. For new users, as long as the new user logs in to the operation position, the second risk control system can collect the information of the user, so there are no problems of data missing and low accuracy.

[0088] Since the second risk control system can obtain real-time user information, it can perform risk judgment and decision-making on the operation behavior of users in real time.

[0089] As described above in conjunction with Figures 1 to 2 ,the method embodiments of the present disclosure have been described in detail. Next, in conjunction with Figures 3 to 6 ,the apparatus embodiments of the present disclosure will be described in detail. It should be understood that the description of the method embodiments corresponds to the description of the apparatus embodiments. Therefore, the parts not described in detail can be referred to the previous method embodiments.

[0090] Figure 3 FIG. is a schematic structural diagram of a risk identification apparatus provided by an embodiment of the present disclosure. Figure 3 The apparatus 300 of Figure 3 can be any of the above-described terminal devices capable of providing an electronic wallet client. The electronic wallet belongs to the first service provider, and the operation interface provided by the electronic wallet client includes the operation position of the second service provider.

[0091] The receiving unit 310 is configured to receive the login information of the user logging in to the operation position.

[0092] The sending unit 320 is configured to, in response to the login information, send a trigger message to the risk control system of the first service provider, where the trigger message is used to trigger the risk control system of the first service provider to collect user information, and send the user information to the risk control system of the second service provider, so that the risk control system of the second service provider can perform risk identification on the operation behavior of the user in the operation position.

[0093] In some embodiments, the user information includes one or more of the following information: account information, device information used, operation environment information, risk labels.

[0094] In some embodiments, the first service provider and the second service provider are service providers from different countries.

[0095] Figure 4It is a schematic structural diagram of a risk identification device provided by an embodiment of the present disclosure. Figure 4 The device 400 can be any one of the risk control systems of the first service providers described above. Figure 4 The device 400 includes a receiving unit 410, a collecting unit 420, and a sending unit 430.

[0096] The receiving unit 410 is configured to receive a trigger message sent by an e-wallet client. An operation interface provided by the e-wallet client includes an operation position of a second service provider. The trigger message is generated when a user logs in to the operation position. The e-wallet belongs to the first service provider, and the operation position belongs to the second service provider.

[0097] The collecting unit 420 is configured to collect user information in response to the trigger message.

[0098] The sending unit 430 is configured to send the user information to the risk control system of the second service provider, so that the risk control system of the second service provider can identify risks for the operation behavior of the user in the operation position according to the user information.

[0099] In some embodiments, the user information includes one or more of the following information: account information, device information used, operation environment information, risk labels.

[0100] In some embodiments, the first service provider and the second service provider are service providers from different countries.

[0101] Figure 5 It is a schematic structural diagram of a risk identification device provided by an embodiment of the present disclosure. Figure 5 The device 500 can be any one of the risk control systems of the second service providers described above. Figure 5 The device 500 includes a receiving unit 510 and a risk identification unit 520.

[0102] The receiving unit 510 is configured to receive user information sent by the risk control system of the first service provider. The user information is collected by the risk control system of the first service provider under the trigger of a trigger message. The trigger message is generated when a user logs in to an operation position provided on an operation interface of an e-wallet client. The operation position belongs to the second service provider, and the e-wallet belongs to the first service provider.

[0103] The risk identification unit 520 is configured to identify risks for the operation behavior of the user in the operation position based on the user information.

[0104] In some embodiments, the user information includes one or more of the following information: account information, device information used, operation environment information, risk labels.

[0105] In some embodiments, the first service provider and the second service provider are service providers from different countries.

[0106] Figure 6 It is a schematic structural diagram of another risk identification device provided by an embodiment of the present disclosure. Figure 6 The risk identification device 600 may include a memory 610 and a processor 620. The memory 610 may be used to store executable code. The processor 620 may be used to execute the executable code stored in the memory 610 to implement the steps in the various methods described above. In some embodiments, the device 600 may further include a network interface 630, and the data exchange between the processor 620 and external devices may be implemented through the network interface 630.

[0107] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present disclosure are generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by wire (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wirelessly (such as infrared, wireless, microwave, etc.). The computer-readable storage medium may be any available medium that can be read by a computer or a data storage device such as a server or data center that includes one or more integrated available media. The available medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a digital video disc (DVD)), or a semiconductor medium (for example, a solid state disk (SSD)), etc.

[0108] As described above, the foregoing are only specific embodiments of the present disclosure, but the protection scope of the present disclosure is not limited thereto. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed by the present disclosure, and all such changes or substitutions should be covered by the protection scope of the present disclosure. Therefore, the protection scope of the present disclosure should be subject to the protection scope of the claims.

Claims

1. A risk identification method, which is applied to an e-wallet client. The e-wallet belongs to a first service provider, and an operation interface provided by the e-wallet client includes an operation position of a second service provider. The method includes: Receiving login information of a user logging in to the operation position, where the operation position is used to provide a marketing activity launched by the second service provider in the operation interface; In response to the login information, sending a trigger message to the risk control system of the first service provider. The trigger message is used to trigger the risk control system of the first service provider to collect user information and send the user information to the risk control system of the second service provider, so that the risk control system of the second service provider can perform risk identification on the operation behavior of the user in the operation position.

2. The method according to claim 1, where the user information includes one or more of the following information: account information, device information used, operation environment information, risk label.

3. The method according to claim 1 or 2, where the first service provider and the second service provider are service providers from different countries.

4. A risk identification method, which is applied to the risk control system of a first service provider. The method includes: Receiving a trigger message sent by an e-wallet client. An operation interface provided by the e-wallet client includes an operation position of a second service provider. The trigger message is generated when a user logs in to the operation position. The operation position is used to provide a marketing activity launched by the second service provider in the operation interface. The e-wallet belongs to the first service provider, and the operation position belongs to the second service provider; In response to the trigger message, collecting user information; Sending the user information to the risk control system of the second service provider, so that the risk control system of the second service provider can perform risk identification on the operation behavior of the user in the operation position according to the user information.

5. The method according to claim 4, where the user information includes one or more of the following information: account information, device information used, operation environment information, risk label.

6. The method according to claim 4 or 5, where the first service provider and the second service provider are service providers from different countries.

7. A risk identification method, which is applied to the risk control system of a second service provider. The method includes: Receiving user information sent by the risk control system of a first service provider. The user information is collected by the risk control system of the first service provider under the trigger of a trigger message. The trigger message is generated when a user logs in to an operation position provided on an operation interface of an e-wallet client. The operation position is used to provide a marketing activity launched by the second service provider in the operation interface. The operation position belongs to the second service provider, and the e-wallet belongs to the first service provider; Based on the user information, performing risk identification on the operation behavior of the user in the operation position.

8. The method according to claim 7, where the user information includes one or more of the following information: account information, device information used, operation environment information, risk label.

9. The method according to claim 7 or 8, wherein the first service provider and the second service provider are service providers from different countries.

10. A risk identification device, on which an electronic wallet client is provided. The electronic wallet belongs to the first service provider, and the operation interface provided by the electronic wallet client includes the operation position of the second service provider. The device includes: A receiving unit, configured to receive the login information of the user logging in to the operation position, where the operation position is used to provide the marketing activities launched by the second service provider in the operation interface; A sending unit, configured to, in response to the login information, send a trigger message to the risk control system of the first service provider. The trigger message is used to trigger the risk control system of the first service provider to collect user information and send the user information to the risk control system of the second service provider, so that the risk control system of the second service provider can perform risk identification on the operation behavior of the user in the operation position.

11. The device according to claim 10, wherein the user information includes one or more of the following information: account information, device information used, operation environment information, risk labels.

12. The device according to claim 10 or 11, wherein the first service provider and the second service provider are service providers from different countries.

13. A risk identification device, which is the risk control system of the first service provider. The device includes: A receiving unit, configured to receive the trigger message sent by the electronic wallet client. The operation interface provided by the electronic wallet client includes the operation position of the second service provider. The trigger message is generated when the user logs in to the operation position. The operation position is used to provide the marketing activities launched by the second service provider in the operation interface. The electronic wallet belongs to the first service provider, and the operation position belongs to the second service provider; A collecting unit, configured to, in response to the trigger message, collect user information; A sending unit, configured to send the user information to the risk control system of the second service provider, so that the risk control system of the second service provider can perform risk identification on the operation behavior of the user in the operation position according to the user information.

14. The device according to claim 13, wherein the user information includes one or more of the following information: account information, device information used, operation environment information, risk labels.

15. The device according to claim 13 or 14, wherein the first service provider and the second service provider are service providers from different countries.

16. A risk identification device, which is the risk control system of the second service provider. The device includes: A receiving unit, configured to receive the user information sent by the risk control system of the first service provider. The user information is collected by the risk control system of the first service provider under the trigger of the trigger message. The trigger message is generated when the user logs in to the operation position provided on the operation interface of the electronic wallet client. The operation position is used to provide the marketing activities launched by the second service provider in the operation interface. The operation position belongs to the second service provider, and the electronic wallet belongs to the first service provider; A risk identification unit, configured to perform risk identification on the operation behavior of the user on the operation front based on the user information.

17. The device according to claim 16, wherein the user information includes one or more of the following information: account information, device information used, operation environment information, risk tags.

18. The device according to claim 16 or 17, wherein the first service provider and the second service provider are service providers from different countries.

19. A risk identification device, comprising a memory and a processor, wherein executable code is stored in the memory, and the processor is configured to execute the executable code to implement the method according to any one of claims 1-9.

Images