Scene-based risk control in Decision Engine

更新时间:
复制 MD 格式

The Decision Engine integrates most risk identification services, such as the scene-based risk control service (registration and marketing). This article uses registration risk identification as an example to describe how to use the scene-based risk control service in the Decision Engine.

Create an event

  1. Create an event. In the Event Fields section, select Registration Event Template and click Fill to the table below. Alternatively, click Add Custom Field to add the required request parameters for registration risk identification one by one. We recommend that you add the mobile number or mobileMd5, ip, and deviceToken.

  2. Click Submit to complete the creation.

Create variables

  1. In Variable Center > Variable Selection, click Add Associated Variable, and create two variables: score and tag.

  2. Select 'Registration Risk Identification_Advanced_Score', associate the corresponding event, enter a variable name, map the event fields to the service fields, and click 'OK' to create the scoring variable.

In Select Event, select Registration Risk Event. In the variable fields, map event fields such as accountId and operateTime to the service fields.

  1. Create a new variable, select "registration risk identification_Advanced_tag", and repeat the preceding process to create the tag variable.

Create a policy

  1. Create a policy, click "Left Variable" and select "registration risk identification_Advanced_score" from Custom Variables, and then, as recommended on the official website, configure the policy to be triggered if the Registration Risk Identification Advanced score is greater than or equal to 85 (high risk).

  1. Configure output

    1. The policy outputs tags & scores. Note that after you select 'Variable' as the type, you can select the variables created above as the score and tag outputs.

    2. The final decision is configured as "Reject".

Validate

  1. Validate the configured event in Risk Identification OpenAPI. See the example below.

  2. Example request parameters

{"eventCode":"de_example","mobileMd5":"*","ip":"*.*.*.*","deviceToken":"*"}

  1. Example response parameters

{
  "Message": "OK",
  "RequestId": "371B720E-D755-5008-80BB-528A4B744BD5",
  "Data": {
    "score": 88.2,
    "finalDecision": "REJECT",
    "tags": "rl0502,rn0316"
  },
  "Code": 200
}