> ## Documentation Index
> Fetch the complete documentation index at: https://docs.godiligent.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Using risk_check_set_id

> Control which risk checks run when performing CDD

A `risk_check_set_id` tells the API which set of risk checks to run for a Customer Due Diligence (CDD) case. If you do not supply this field, your account's default risk check set is applied automatically.

## Default behaviour

By default, every account has a risk check set configured in the dashboard. When `risk_check_set_id` is omitted from a request, the CDD case uses this default set of checks.

## Providing a custom risk\_check\_set\_id when create CDD case

Specify `risk_check_set_id` in the request body to apply a different set of checks. The value must be the UUID of a risk check set that exists for your account.

```json theme={null}
{
  "risk_check_set_id": "550e8400-e29b-41d4-a716-446655440000"
}
```

You can create or modify risk check sets in the **Dashboard** under **Settings > Risk Checks**. The dashboard lists the IDs of all configured sets.

## When to use

Use `risk_check_set_id` when you need to tailor the checks for a specific case or workflow. For most integrations, omitting the field and relying on the default configuration is sufficient.

### Examples

Risk check sets let you run different checks depending on the selling channel or customer type. For example:

* `online-sellers` – run enhanced verification for sellers that only operate online
* `in-store-sellers` – apply simplified checks for customers selling exclusively in store

Similarly, a business might define `inbound-in-store` and `outbound-in-store` sets to apply different checks depending on how customers engage. Set the appropriate `risk_check_set_id` when creating the case so the API performs the correct checks.