All Products
Search
Document Center

Fraud Detection:Device Fraud Detection features and parameter description

Last Updated:Jan 10, 2026

Device Fraud Detection is designed for mobile apps, H5 pages, and miniapps. It detects device exceptions, protects against technical attacks, and generates a unique device ID. The service detects risks such as emulator attacks, app multi-instance attacks, malicious tool execution, and tampered device parameters. You can use Device Fraud Detection in key business scenarios such as registration, logon, ordering, and coupon collection. This helps reduce business losses and achieve genuine user growth.

Version introduction

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.

Features

Basic Edition

Enhanced Edition

Real-time computing

Support

Support

Service response

Risk tag.

Risk tag and unique device ID

SLS delivery

Not supported.

Yes, you can grant authorization for log delivery. The logs are then stored for one year free of charge.

Service input 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

Field Name

Description

Data format

Sample data

Required

Remarks

deviceToken

The device token that is obtained 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 many 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.

Service 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.

.......

Log on to the Fraud Detection console and go to the Provisioning module to view more device tag definitions. Go to console

For more information about common response parameters, see the "Common response parameters" section of the Common parameters topic.