List Management

The List Management page is where payment operators build and maintain the reusable value lists that power Corgi's fraud detection rules. Every allow list, block list, and attribute collection lives here, whether it ships as a Corgi default or you author it yourself. Spend a few minutes on this page and the rules you write elsewhere in Intelligence become dramatically easier to reason about, because each rule can simply ask "is this value in that list?" instead of hard-coding individual values inline.

What Are Lists?

Lists are collections of values (emails, card fingerprints, IP addresses, customer IDs, etc.) that can be referenced in your fraud rules. For example, you might create an email block list containing known fraudulent email addresses, and then create a rule that blocks any transaction matching an entry in that list.

This indirection is the whole point. One list can feed many rules, and updating the list propagates everywhere it is referenced. When a new bad actor shows up, you add the value once rather than editing every rule that needs to know about it.

Default Lists

Corgi provides several default block lists out of the box, pre-populated with known bad actors. Default lists are managed by the system and updated automatically, so you inherit ongoing threat intelligence without operational overhead.

Because these lists are system-managed, you cannot edit their entries directly, but you can reference them from your own rules exactly like any custom list.

Custom Lists

You can create custom allow and block lists for any supported attribute type. Custom lists are where your team's institutional fraud knowledge accumulates: the email domain that keeps chargebacks, the BIN range tied to a gift-card abuse pattern, the customer ID you want to always approve.

Choose the type that matches the attribute your rules will evaluate. Email Domain and Charge Description are worth calling out because they offer case-insensitive (and for Charge Description, case-sensitive) matching options, which matters when fraudsters vary capitalization to evade exact-match checks.

List Details

The main table shows all lists with:

The Alias column is the one you will use most often when authoring rules, because it is the short identifier your rule conditions actually reference. Pick aliases that read well inline, because they will appear in every rule that consumes the list.

Creating a New List

Click + New List to create a custom list. You'll need to specify:

Bulk import is the faster path when you are seeding a list from an existing spreadsheet, CSV export, or fraud analyst's investigation notes. Manual entry is better for one-off additions discovered in day-to-day review. Once the list exists, you can add or remove entries at any time, and every rule referencing the list picks up the change on the next evaluation.