# Value lists

Use value lists to compare against a list of data when setting conditions for rules or binds, or applying filters to data table segments.
Commonly used lists contain values related to conditions that target specific properties such as: customers, transactions, or BINs.

- Example use case

  This example describes how to create a value list of high-risk countries and require customers from those locations to submit KYC documents before their transactions are processed.

  1. Create a value list of high-risk countries and name it `High-risk countries`.
  2. Create a gateway routing automation using the 'Gateway account requested' event.
  3. In the **Conditions** section, select the `Transaction > Bank account > Risk metadata > Country` filter, then select `is in list`.
  4. In the value list dropdown, select the `High-risk countries` value list.
  5. In the **Actions** section, press **Add action**, then select **Request KYC**.
  6. Define the KYC documents to request from the customer.
  7. Press **Save rule**.

Value list conditions:

- **is in list:** The selected value must be in a specified list.
- **is not in list:** The selected value must not be in a specified list.
- **is empty or is in list:** The selected value must be empty or in a specified list.
- **is empty or is not in list:** The selected value must be empty or not in a specified list.

## Create a value list

Use this process to create a value list.

1. In the left navigation bar, press **Automations**.
2. In the **Rules engine** section, press **Value lists**.
3. Press **Create value list**.
4. In the **Description** field, enter a list name.
The **ID** field is populated automatically.
5. In the **List values** section, enter list values, or press **Upload CSV** to upload them.
6. Press **Save value list**.

## Use a value list in a rule or bind

This process describes how to use value lists when setting conditions in a rule or bind.

1. [Create a value list](#create-a-value-list).
2. Configure a rule or bind.
In the **Conditions** section, clear the **No conditions** checkbox.
3. In the **Select filter** dropdown, select a filter.
4. In the next field, select from the following:
  - **is in list**: Values must be in a specified list.
  - **is not in list**: Values must not be in a specified list.
  - **is empty or is in list**: Values must be empty or in a specified list.
  - **is empty or is not in list**: Values must be empty or not in a specified list.
5. In the next field, select or add the related list.
For more information, see [Rule and binds](/docs/automations/rules-and-binds).

## Use a value list in a filter or segment

This process describes how to use a value list to apply filters in a data tables segment.

1. [Create a value list](#create-a-value-list).
2. In the left navigation bar, press **Data tables**, press **Customers**, **Payments**, **Billing**, or **Logs**, then select a segment.
3. In the top right of the table, press **Filters**.
4. In the **Filter** dropdown, select a value to filter.
5. In the **Operation** dropdown, select from the following conditions:
  - **is in list**: Values must be in a specified list.
  - **is not in list**: Values must not be in a specified list.
  - **is empty or is in list**: Values must be empty or in a specified list.
  - **is empty or is not in list**: Values must be empty or not in a specified list.
6. In the **Value** field, select a value list.
7. Press **Apply filter**.
8. Optionally, to save the filtered data to the active segment, press **Save**.
9. Optionally, to create a new segment based on the filtered data, press **Save segment as**, enter a name for the new segment, and then press **Save**.

## Empty conditions

Use the empty condition option to match conditions where a value is null, not in a specified value or range, or not in a specified value list.

The empty condition is an option when creating a rule or bind.
If an event matches the condition, the rule, or bind is executed.

For example, if an event has the 'is empty or is in' criteria configured for the country ID: 'CA'.
And, has the 'transaction > payment card > bank country' filter applied.
This rule or bind will only execute when the bank country ID, related to a payment card, is null or is in Canada (CA is the country code for Canada).

Empty condition rule or bind conditions:

- **is empty:** the selected value must be null.
- **is not empty:** the selected value must not be null.
- **is empty or is in:** the selected value must be null or within a specified value or range.
- **is empty or is not in:** the selected value must be null or not within a specified value or range.
- **is empty or is in list:** the selected value must be empty or in a specified [value list](/docs/automations/create-a-value-list).
- **is empty or is not in list:** the selected value must be empty or not in a specified [value list](/docs/automations/create-a-value-list).