Device Fraud Detection event parameters and technical workflow

Select an edition

• Basic Edition: Suitable for scenarios that require only risk tag determination, such as identifying whether a device is an emulator, rooted, or running in a multi-instance environment.

• Enhanced Edition: Suitable for scenarios that require a unique device ID for cross-session tracking, or log delivery to SLS for in-depth analysis.

Service parameter

The Service parameter specifies the service edition. Different editions use the following Service parameter values.

ServiceParameters

ServiceParameters contains the business request parameters in JSON format, corresponding to the ServiceParameters field in Common parameters. The following table describes the request parameters for the device risk identification service (both Basic Edition and Enhanced Edition).

SDK for Android

Device ID

The extend field in the Data object contains the unique device ID. Only the Enhanced Edition returns this field.

Device risk tags

The tags field in the Data object contains the risk detection results. If multiple tags are returned, they are separated by commas. The following table lists some common tags.

For more information, see Common response parameters.

Maven dependencies

Add the following Java Maven dependency:

<dependency>
    <groupId>com.aliyun</groupId>
    <artifactId>aliyun-java-sdk-saf</artifactId>
    <version>3.0.1</version>
</dependency>

Recommended dependency arbitration:

<dependency>
    <groupId>com.aliyun</groupId>
    <artifactId>aliyun-java-sdk-core</artifactId>
    <optional>true</optional>
    <version>4.5.25</version>
</dependency>
<dependency>
    <groupId>com.alibaba</groupId>
    <artifactId>fastjson</artifactId>
    <version>1.2.68.noneautotype</version>
</dependency>
<dependency>
    <groupId>org.apache.httpcomponents</groupId>
    <artifactId>httpclient</artifactId>
    <version>4.5.3</version>
</dependency>
<dependency>
    <groupId>io.opentracing</groupId>
    <artifactId>opentracing-util</artifactId>
    <version>0.31.0</version>
</dependency>

Java SDK source code

// The AccessKey pair of an Alibaba Cloud account has permissions on all API operations.
// Use a RAM user for API access and daily O&M.
// Do not save the AccessKey ID and AccessKey secret in your project code to prevent AccessKey leakage,
// which may compromise the security of all resources under your account.
// This example uses environment variables to read the RAM user AccessKey for API authentication.
// Before running this code, make sure the following environment variables are configured:
// ALIBABA_CLOUD_ACCESS_KEY_ID, ALIBABA_CLOUD_ACCESS_KEY_SECRET.
// Create and initialize a DefaultAcsClient instance. Initialize only once.
DefaultProfile profile = DefaultProfile.getProfile(
    "cn-shanghai", // Region ID. cn-shanghai is recommended for the China site. Must match the client SDK reporting domain.
    System.getenv("ALIBABA_CLOUD_ACCESS_KEY_ID"),     // RAM user AccessKey ID
    System.getenv("ALIBABA_CLOUD_ACCESS_KEY_SECRET")  // RAM user AccessKey secret
);
// HTTP connection pool configuration
HttpClientConfig clientConfig = HttpClientConfig.getDefault();
clientConfig.setMaxRequestsPerHost(6);
clientConfig.setMaxIdleConnections(20);
// HTTP timeout configuration
clientConfig.setReadTimeoutMillis(10000);
clientConfig.setConnectionTimeoutMillis(3000);
profile.setHttpClientConfig(clientConfig);
IAcsClient client = new DefaultAcsClient(profile);

// Send the request
ExecuteRequestRequest executeRequestRequest = new ExecuteRequestRequest();
// To specify a custom version number, modify it here. Default: 2019-05-21
executeRequestRequest.setVersion("2019-05-21");
// Specify the request method
executeRequestRequest.setSysMethod(MethodType.POST);
// Specify the protocol. Currently, only HTTPS is supported.
executeRequestRequest.setSysProtocol(ProtocolType.HTTPS);

// Product code for the device risk identification service: device_risk or device_risk_pro.
// See the Service parameter row in the "Editions" table.
String service = "device_risk_pro";
executeRequestRequest.setService(service);
// Business parameters. Set only the parameters you need.
Map<String, Object> serviceParams = new HashMap<String, Object>();
// deviceToken is required.
serviceParams.put("deviceToken", "TK******************");
executeRequestRequest.setServiceParameters(JSONObject.toJSONString(serviceParams));
executeRequestRequest.setAcceptFormat(FormatType.JSON);

try {
    ExecuteRequestResponse httpResponse = client.getAcsResponse(executeRequestRequest);
    System.out.println("httpResponse:" + JSONObject.toJSONString(httpResponse));
} catch (Exception e) {
    e.printStackTrace();
}

Verify the call result

After sending a request through the SDK, verify the integration by checking the following:

• A response with Code=200 indicates that the request is successful.

• The Data object contains the tags field, which confirms that the device risk detection result is returned.