Enterprises can integrate Device Risk Detection SDK into a mobile app to generate a unique ID for each device to help identify device exceptions. For example, Device Risk Detection can detect whether the app runs on an emulator, whether multiple instances of the app are running, whether malicious tools are used, and whether device parameters are maliciously tampered with. Enterprises can apply Device Risk Detection to scenarios such as registration, logon, ordering, and coupon distribution. After the device information is imported, Device Risk Detection accurately identifies device risks to help combat fraud.
Editions
To meet the risk control requirements of different industries and enterprises at different stages of development, Device Risk Detection provides Basic Edition and Advanced Edition. The following table compares the features of the two editions.
Feature | Basic Edition | Advanced Edition |
Real-time computing | Supported | Supported |
Service response | Risk tag | Risk tag and unique device ID |
Log delivery to Log Service | Not supported | Supported. You can authorize Device Fraud Detection to deliver logs to Log Service. Logs are stored in Log Service for free for one year. |
Service event parameters
Service event parameters refer to the request parameters that are passed to the common request parameter ServiceParameters in the JSON format. For more information, see Common parameters. The following tables describe the service event parameters that are passed to the ServiceParameters parameter for Device Fraud Detection Basic Edition and Enhanced Edition.
Device Risk Detection SDK that applies to native apps on Android and iOS
Parameter | Description | Type | Example | Required | Remarks |
deviceToken | The deviceToken value that is obtained by using Device Risk Detection SDK for iOS or Device Risk Detection SDK for Android | String | Tk9SSUQuMS***************************ZDNmNWY5NzQxOW1oLTE2MjI2NDIyNjc4MzAtZmIwODAwOGE2NGZWFhdDgzMTBLUlVSU0VoWWVNcW82ZkZlZWJBY0s0QmFGOGNyT3poY2txZXVqRjMyc1lCaDdBL2pzRTRPdXhmZjU5NEgxcGlQMGFEU1AwajZpa1ZTQ1FlbE5IQmZkTklZVzVkV2VDM1hHNUMreVRtMXFFemp3PT0= | Yes | In normal cases, the length of a token is about 600 bytes. However, in poor network conditions, the length of a token may exceed 2.5 KB. If a large number of long tokens occur, check whether the client is in good network conditions. Then, make sure that the call interval between the init and getSession operations of the SDK is greater than 2 seconds. |
Response parameters
The response parameters for Device Fraud Detection include the risk tag and device ID. The device ID is returned only in Advanced Edition. The following table describes some values of the tags parameter in the Data response parameter for Device Risk Detection.
Value | Description |
is_emulator | The device is suspected of being an emulator. |
is_rooted | The device is suspected of being rooted. |
is_virtual | The device is suspected of running multiple instances of the app. |
....... | To view more information about risk tags, log on to the Fraud Detection console and go to the Integration Guide page. |
For more information about common response parameters, see the "Common response parameters" section of the Common parameters topic.