Welcome to the TD terminal SDK.

TD terminal SDK is a basic tool that the TD decision engine relies on. Its main function is to collect device and behavior data and report it to the server. The TD decision engine will accurately identify the device status based on these data and through real-time indicators, model decisions, and atlas correlation, providing capabilities including deviceID, risk detection, device trust score, and behavior recognition. These indicators will participate in the key links of TD risk decision-making, and provide more accurate support for intelligent risk decision-making to ensure that the TD decision engine can accurately intercept fraud. While reducing losses, avoid disturbing high-quality customers.

At the current SDK integration stage, the goal is to refine the process of technology docking and define some SDK specifications. Subsequent TD decisions will be made at key nodes of your business, based on the incoming data for risk interception. If you have any suggestions on the current docking process, you can contact our technical docking team at any time, and we will continue to optimize your docking experience.

The TD terminal SDK includes two parts: fingerprint and behavior verification. For TrustDevice, TrustID, TrustTransaction, and TrustPromo, please use the device fingerprint SDK. For MFA, please use the BehaviorVerification SDK.

• Fingerprint(TrustDevice、TrustID、TrustTransaction、TrustPromo)
• BehaviorVerification(MFA)

Description of Terms

Blackbox is not a deviceID, but an important query voucher in the risk control link of TrustDecision. The Mob-Risk SDK will generate two types of blackbox according to the current data collection reports. Both blackbox can be used to query device information without affecting the generation of deviceId and risk tag.

Non-Degraded Blackbox

The Mob-Risk SDK successfully reports the data. The SDK generates a normal blackbox based on the results returned by the request.

• Advantages: The blackbox is 26 characters long, and it is friendly to use HTTP requests to report the blackbox in business scenarios.
• Disadvantages: The data can only be returned if it is reported successfully. It does not apply to blackbox scenarios with high real-time requirements.

Degraded Blackbox

When the Mob-Risk SDK fails to report or fails to report, the SDK compresses and encrypts the currently collected data to generate a degraded blackbox.

• Advantages: The generation is not affected by the success of data reporting, and the device information can still be queried in case of network exceptions.
• Disadvantages: The blackbox is about 5000 characters long (it will rise according to the actual device situation). In the business scenario, developers who are limited in the length of the HTTP request body for reporting the blackbox are unfriendly.