All Products
Search
Document Center

Fraud Detection:Service event parameters and response parameters for Device Fraud Detection

Last Updated:Mar 17, 2025

You can integrate Device Fraud Detection SDK into a mobile app to generate a unique ID for each device. This helps identify device exceptions. For example, Device Fraud 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 tampered with. You can use Device Fraud Detection in scenarios such as registration, logon, ordering, and coupon distribution. After the device information is imported, Device Fraud Detection accurately identifies device risks to help combat frauds.

Editions

To meet the risk control requirements of different industries and enterprises at different stages of development, Device Fraud Detection provides Basic Edition and Enhanced Edition. The following table compares the features of the editions.

Feature

Basic Edition

Enhanced Edition

Real-time computing

Supported.

Supported.

Service response

Risk tag.

Risk tag and unique device ID

Log delivery to Simple Log Service

Not supported.

Supported. You can authorize Device Fraud Detection to deliver logs to Simple Log Service. Logs are stored in Simple Log Service free of charge 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 Fraud Detection SDK that applies to native apps on Android and iOS

Parameter

Description

Type

Example

Required

Remarks

deviceToken

The device token that is obtained by using Device Fraud Detection SDK.

String

Tk9SSUQuMS***************************ZDNmNWY5NzQxOW1oLTE2MjI2NDIyNjc4MzAtZmIwODAwOGE2NGZWFhdDgzMTBLUlVSU0VoWWVNcW82ZkZlZWJBY0s0QmFGOGNyT3poY2txZXVqRjMyc1lCaDdBL2pzRTRPdXhmZjU5NEgxcGlQMGFEU1AwajZpa1ZTQ1FlbE5IQmZkTklZVzVkV2VDM1hHNUMreVRtMXFFemp3PT0=

Yes

In most cases, the length of a token is approximately 600 bytes. However, if the network quality is poor, the length of a token may exceed 2.5 KB. If a large number of long tokens are returned, perform the following steps: Make sure that the client network is high-quality. Then, make sure that the interval between a call for the init operation and a call for the getSession operation is at least 2 seconds.

Response parameters

The response parameters for Device Fraud Detection include the risk tag and device ID.

Device ID

The device ID is returned only in Advanced Edition that is specified by device_risk_pro. The value of the extend field in the Data response parameter is the device ID.

Risk tag

The value of the tags field in the Data response parameter is the risk tag. If multiple risk tags are returned, the tags are separated by commas (,). The following table describes specific risk tags.

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.