> ## Documentation Index > Fetch the complete documentation index at: https://docs.corsa.finance/llms.txt > Use this file to discover all available pages before exploring further. # Lists - Block, Allow and Watch Lists for Transaction Monitoring > Keep block, allow and watch lists of clients, accounts, identifiers and network data, and use them as conditions in transaction monitoring rules. Lists hold the clients, accounts and identifiers your rules check on every transaction. Put a known bad actor on a block list, a trusted counterparty on an allow list, or a party under review on a watch list, then reference the list type in a [transaction monitoring rule](https://docs.corsa.finance/transaction-monitoring/building-rules.md). Open **Intelligence Hub** → **Lists** (`/app/lists`). > [!NOTE] > > Lists is rolled out per platform behind a feature flag. If you don't see **Lists** under Intelligence Hub, ask your Corsa contact to enable it. ## How it works 1. Create a list, choose its type (**Block**, **Allow** or **Watch**) and pick the item types it accepts. 2. Add items — clients from your records, or values such as emails, IBANs, wallets and IP ranges. 3. In a rule, add the condition the list type feeds: **On Block List**, **On Allow List** or **On Watch List**. For example, **Sender · On Block List is true**. 4. Changes to a list apply to the very next transaction evaluated. There is nothing to publish. ## List types | Type | Use it for | Rule condition | | - | - | - | | **Block** | Known bad actors and identifiers. Rules can stop or alert on any match. | **On Block List** | | **Allow** | Trusted parties. Rules can skip or soften checks for a match. | **On Allow List** | | **Watch** | Parties under review. Rules can raise the risk or route a match for review. | **On Watch List** | | **314(a)** | FinCEN 314(a) subjects. Shown only when such lists exist, and only to users with 314(a) access. | — | A condition is true when the sender or receiver you point it at matches an item on **any active list** of that type. You can create Block, Allow and Watch lists yourself. 314(a) lists are not created from this page. ### Which items rules match Rules check a transaction's participants against these item types: | Item type | What the rule compares | | - | - | | **Individual client**, **Corporate client** | The sender or receiver client. | | **Wallet** | The sender or receiver wallet record, or its blockchain address. | | **Bank account** | The sender or receiver bank account record, or its account number. | | **Device** | The devices on the client's sessions for the transaction. | | **IP address**, **IP range** | The IP addresses on the client's sessions for the transaction. | Items of the other types (email, phone, name + date of birth, tax ID, document number, payment account, card hash, card BIN, BIC / SWIFT, merchant ID, ASN, domain, company registration) can be stored and looked up with **Check a value**, but rules do not match them yet. To act on a person, add their client record. ## What a list can hold The person who creates a list picks which item types it accepts. Items of other types are rejected. | Group | Item types | Notes | | - | - | - | | Clients & identity | **Individual client**, **Corporate client** | Picked from your client records. Matches transactions where the client is the sender or receiver. | | | **Email** | Matched case-insensitively. | | | **Phone** | Stored in international format. Include the country code, or set a default phone country on the list. | | | **Name + date of birth** | Both must match. Names are compared without case or accents. | | | **Tax ID** | Punctuation is ignored. | | | **Document number** | Passport or ID number. Add the issuing country to avoid cross-country collisions. | | Accounts & payments | **Bank account**, **Payment account**, **Wallet** | An IBAN, account number, payment account identifier or blockchain address — or the matching Corsa record. | | | **Card hash** | Hex digest of the card number (32–128 characters). Never paste a card number. | | | **Card BIN** | First 6 to 8 digits of a card number. | | | **BIC / SWIFT** | 8 or 11 characters. | | | **Merchant ID** | Merchant identifier as sent on transactions. | | Network & device | **IP address** | IPv4 or IPv6. Checked against the transaction's session IPs. | | | **IP range** | CIDR range. Every address inside the range matches. | | | **ASN** | Autonomous system number, for example a hosting provider. | | | **Device** | Device fingerprint ID from your session provider. | | | **Domain** | Email or website domain, without the protocol. | | Businesses | **Company registration** | Company registration number. | ## List settings | Setting | What it does | | - | - | | **Name** and **Description** | Describe what belongs on the list and who maintains it. The description is optional. | | **Type** | Block, Allow or Watch. The type can't be changed after the list is created. | | **What can go on this list** | The accepted item types. Presets cover common combinations (clients, identity, payments, network). | | **Items expire by default** | Optional. Items added without their own expiry date stop matching after this many days (1 to 3,650). | | **Treat Gmail aliases as one address** | Shown when the list accepts emails. `j.doe+promo@gmail.com` and `jdoe@googlemail.com` are treated as `jdoe@gmail.com`. | | **Default phone country** | Shown when the list accepts phone numbers. A two-letter country code used to read numbers entered without a country code. | ## Adding items Open a list and select **Add items**. Only the types the list accepts are offered. * **Clients** — search by name or reference ID and pick one or more clients. If client search is unavailable, the picker says so and offers **Try again**; it never shows an outage as "no clients match". * **Other values** — enter one value, or paste several at once, one per line or separated by commas. You can add up to 1,000 values in one go. * **Reason** (recommended) — why the item is on the list. It is shown in the item's detail panel. * **Expires on** (optional) — the item stops matching after this day. Leave it empty to use the list's default expiry, or to keep the item until someone removes it. * **Name + date of birth** items need a date of birth. **Document number** items take an optional issuing country. If any value is invalid, nothing is added. Each rejected value is listed with its reason, and one click removes the rejected values so you can resubmit the rest. Duplicates are merged rather than added twice. This includes case variants and, when the Gmail option is on, Gmail aliases of an address that is already on the list. > [!NOTE] > > On platforms with field encryption, plaintext values of personal identifier types — such as email and phone — are not stored in lists. Add the client record instead. ## Managing items The list page shows a searchable table of items. Select an item to open its detail panel: what it matches on, the reason, its source (for example manual or API), who added it and when, its expiry, and for client items a link to the client profile. For bank account, payment account and wallet records, **Refresh identifiers** re-reads the record's current identifiers. Remove one item from its detail panel, or select several rows and remove them together. Removals are recorded in the audit log. ## Check a value From the Lists overview, select **Check a value** to see whether a value is on any active list. Pick the item type, enter the value, and select **Check**. The result lists each matching list and how the value matched: directly, through a record's identifiers, or inside an IP range. * **Document number** shows an optional **Issuing country**. A document added with a country is stored with it, so check it with the same country. * **Name + date of birth** asks for the date of birth. * If the value isn't valid for its type, the dialog shows the reason (for example `not a valid international phone number`) instead of a result. Client records aren't checked here; open the client's profile instead. ## Archive and restore Archiving a list stops its items from matching immediately. The items are kept, and you can restore the list at any time. Turn on **Archived** on the overview to see archived lists. ## Permissions | To | You need | | - | - | | View lists and their items, and check a value | `lists:view` | | Create, edit, archive and restore lists; add and remove items | `lists:edit` | | See 314(a) lists | `lists:view` and `fincen_314a:view` | Grant **Lists** and **FinCEN 314(a)** in the team permissions editor, under **Insights & Audit**. The built-in role presets (Read only, Analyst, Investigator, Admin) don't include them, so grant them to each person who needs them. ## Related * [Building rules](https://docs.corsa.finance/transaction-monitoring/building-rules.md) — add an **On Block List**, **On Allow List** or **On Watch List** condition to a rule. * [Conditions reference](https://docs.corsa.finance/transaction-monitoring/conditions-reference.md) — every operator and entity available in rule conditions. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.