Documentation Index
Fetch the complete documentation index at: https://documentation.idenfy.com/llms.txt
Use this file to discover all available pages before exploring further.
The Blocklist feature allows you to automatically mark or deny specific companies or applicants during KYB automation flows.
Each entry defines what to match and what to do when a match occurs.
Step 1: Navigate to Blocklist
- Go to Custom Rules → Blocklist tab.You’ll find it next to the Automations tab under Configuration → Custom Rules.
- Here you can:
- View existing blocklist entries.
- Import or export lists for backup or migration.
- Click “Create Blocklist” to add a new rule.
Step 2: Create a New Blocklist Entry
Each blocklist entry consists of:
- A title (for identification),
- One or more data fields used for matching,
- And an action to perform when a match is found.
Title
Give your blocklist entry a unique, descriptive name — for example:
Suspicious Lithuanian Companies or Fraudulent Payment Domains.
This title will help differentiate your blocklist rules later.
Step 3: Define Matching Fields
In the Blocklist Values section, you can specify details across several categories:
Company, Applicant, UBO, Representative, and Timezone.
Each field is optional, but at least one must be filled.
| Field | Description | Example |
|---|
| Name | Company name (exact match required). Case-insensitive and accent-insensitive. | ABC Ltd |
| Registration Number | Official registration number. Commonly used for precise matching. | 123456789 |
| Country | Country of registration. | Lithuania |
| City | City name. | Vilnius |
| Street | Street address or partial address. | Gedimino pr. 1 |
| Postcode | Postal code. | 01103 |
| Type | Company type, e.g. UAB, LLC, LTD. | UAB |
| Activity Code | Company activity (NACE or other codes). | 6201 |
| Status | Company’s current legal or operational status. | Active |
| Domain | Website or email domain. | example.com |
Applies to the person submitting or representing the company.
| Field | Description | Example |
|---|
| Name | Full name of the applicant. | John Doe |
| IP Address | Originating IP address. | 192.168.0.1 |
| Email Address | Email address used in the submission. | john@example.com |
| Phone Number | Contact number. | +37060000000 |
| Field | Description | Example |
|---|
| Country of Residence | Where the UBO lives. | Lithuania |
| Nationality | UBO’s nationality. | Lithuanian |
| Field | Description | Example |
|---|
| Country of Residence | Country where the representative resides. | Germany |
| Nationality | Representative’s nationality. | German |
Timezone
| Field | Description | Example |
|---|
| Timezone | Timezone from which the verification originated. | Europe/Vilnius |
Step 4: Matching Logic
Matching is strict and rule-based to ensure accuracy.
- Perfect match only:
No fuzzy or similarity scoring.
“ABCLTD” will not match “ABC LTD” unless identical after normalization.
- Case-insensitive and accent-insensitive:
A = a, ą, Â, etc. (handled via database collation).
- Empty fields count as a match:
If both sides (company and blocklist) leave a field blank → it counts as matching.
- At least one field must match between the blocklist and the company data.
- Multiple blocklists:
If a company matches one rule, later blocklists or automations won’t proceed when the action is Block.
Example
| Field | Company Value | Blocklist Value | Result |
|---|
| Name | ABC | null | – |
| Registration Number | 123 | 123 | Match |
| Postcode | null | 123 | – |
Step 5: Select Action
Select what happens when a match is detected:
| Action | Description |
|---|
| ** Do Nothing** | Logs the event but takes no further action. Useful for observation or passive monitoring. |
| ** Flag** | Highlights the company in the system (under Tags). The verification continues normally. |
| ** Block** | Automatically denies the company and stops all subsequent blocklist and automation processing. |
Step 6: Save and Activate
Click Save to finalize the rule.
The entry becomes active immediately — no further activation steps required.
Notes & Best Practices
- Use registration number whenever possible for precision.
- Combine email domain and country for effective applicant-level blocking.
- Regularly review flagged entries to refine your lists.
- Use Import/Export for bulk updates or cross-environment synchronization.
