Help
  • FAQ
    • Introduction
    • Name Matching
      • Does Screena provide rules-based and/or fuzzy matching capabilities?
      • Does Screena have any machine learning or AI capabilities?
      • What are name cultures and how does Screena handle them?
      • How does Screena handle different scripts, diacritics, and transliteration?
      • How does Screena handle common names?
      • How does Screena handle inaccurate data?
      • What methods does Screena use to reduce false positives?
      • What is the percentage of false positives reduced with the methods used by Screena?
      • How does whitelisting work?
      • What differentiates pairwise name-matching between Screena One and Screena Plus?
      • How does secondary attributes-matching work?
      • Can Screena match beyond names and allow firms to blacklist identifiers or locations?
      • What is the difference between 'matchingNames' in screening responses and 'names' in 'targetData'?
    • Watchlists
      • Which lists are available out of the box?
      • Is Screena watchlist agnostic?
      • How is watchlist data loaded into Screena?
      • How frequently is data updated within Screena?
      • Do you provide proprietary watchlist data?
      • What sort of data (e.g., names, known aliases, known associates, etc) is used for name matching?
      • Does Screena support adverse media screening?
      • Do you provide information about whether a list entry is active, inactive or deceased?
      • Do you provide a URL link to the reference article for adverse media screening?
      • How is the data of third-party list providers conveyed to your name-screening API response?
      • Can I screen against specific sanction programs within a watchlist and not all of them?
      • What is the difference between the USA and the OFAC lists?
      • Is there a template to upload private lists into Screena?
      • How many records can I upload to my private watchlist?
      • Can I upload more than one private list?
      • How can I update my private list?
      • Why can't I find Politically Exposed Persons (PEPs) at regional level when I use Instant Search?
      • How do you monitor that watchlists are up to date and correctly uploaded to your platform?
    • Performance
      • Does Screena provide real-time screening capabilities?
      • What is the speed of screening?
      • How do you ensure horizontal and vertical scalability?
      • Does Screena support batch processing?
      • Do you have performance benchmarks?
    • Integration
      • Can clients configure the solution themselves or would they need support from you?
      • Do you partner with any other solutions/vendors?
      • Do you provide technology or solutions to support alert remediation investigation?
      • Can Screena be integrated within third-party platforms and systems?
      • How do you handle changes to your API data model?
    • Personalization
      • What options do I have to optimize my screening results?
      • What screening parameters can I configure to meet my risk appetite?
      • To which extent are the screening thresholds adjustable?
      • What is the difference between the algorithm value "ignore" and the option "nullMatch" set to false?
    • Hosting & Deployment
      • How can Screena be deployed?
      • How do you set resources per customer?
      • How do you segregate the data and configuration between customers?
      • How often does Screena release new versions?
      • How often are models re-trained and what does roll out to clients look like?
      • How do you handle High Availability?
      • What AWS regions do you operate as of now?
      • What operating systems and/or execution platforms are supported?
      • How do you provide bug fixes and distribution across clients?
    • Pricing & Support
      • What is your pricing model?
      • Can you clarify the difference between Screena One, Plus and Firm?
      • What additional modules are not included in your core product pricing package?
      • Do you charge for professional services and/or after-sales services?
      • Do you offer bespoke solutions to clients?
      • Can I test your solution for free?
      • What happens at the end of my trial period?
      • What are my payment options - credit card and/or invoicing?
      • What are your standard support & maintenance agreements?
      • Are there integration costs to work with Commercial-Off-The-Shelve (COTS) lists?
    • Security & Audit
      • Does Screena have security certifications?
      • What security measures do you apply?
      • How do you adhere to GDPR?
      • Does Screena provide versioning capabilities?
    • Tech Stack
      • What is your tech stack?
      • What programming language(s) is Screena written in?
      • What source and version control systems are used to manage development?
      • What testing tools do you use?
  • How To
    • Install Screena Portal
      • Preparing your system
      • Installing Screena Portal backend
      • Launching Screena Portal backend
      • Installing the web server
      • Configuring Screena Portal
    • Start Screena Portal
      • Starting PostgreSQL database
      • Starting Apache HTTP server
      • Starting Screena application
        • Start command
        • Restart command
        • Stop command
  • Release Notes
    • 2.1.17
    • 2.1.16
    • 2.1.15
    • 2.1.14
    • 2.1.13
    • 2.1.12
  • Legal
    • Terms & Policies
      • Website Terms of Use
      • Screena API Terms of Service
      • Screena API Data Policy
    • Privacy & Security
Powered by GitBook
On this page
  • UN Named Record
  • OFAC SDN Named Record
  • UK Named Record
  • EU Named Record

Was this helpful?

  1. FAQ
  2. Watchlists

Is Screena watchlist agnostic?

PreviousWhich lists are available out of the box?NextHow is watchlist data loaded into Screena?

Last updated 1 year ago

Was this helpful?

Screena is 100% watchlist agnostic. We can source also known as Open Source Intelligence lists (OSINT), Commercial Off-The-Shelve (COTS) and private lists. There are no limitations regarding the number and size of lists that can be uploaded.

All lists are automatically mapped and unified with Screena’s named entity data model, requiring no development effort from our clients. Whenever technically feasible, we ensure data normalization across all lists for fields containing dates, countries, or nationalities.

Below are four named records in Screena's JSON format, demonstrating how the same sanctioned individual present in four distinct watchlists is mapped to our unified data model:

UN Named Record

{
	"records": [
		{
			"dataID": "QDi.312",
			"entityType": "individual",
			"names": [
				{
					"surname": "ALI CHAUDHRY",
					"givenName": "AAMIR",
					"normalized": "aamir ali chaudhry"
				},
				{
					"fullName": "عامر علی چوہدری",
					"normalized": "eamr ely cwhdry"
				},
				{
					"fullName": "Aamir Ali Chaudary",
					"normalized": "aamir ali chaudary",
					"type": "Good Quality Alias"
				},
				{
					"fullName": "Aamir Ali Choudry",
					"normalized": "aamir ali choudry",
					"type": "Good Quality Alias"
				},
				{
					"fullName": "Amir Ali Chaudry",
					"normalized": "amir ali chaudry",
					"type": "Good Quality Alias"
				},
				{
					"fullName": "Huzaifa",
					"normalized": "huzaifa",
					"type": "Low Quality Alias"
				}
			],
			"nationalities": [
				{
					"country": "PK"
				}
			],
			"datesOfBirth": [
				{
					"date": "1986-08-03"
				}
			],
			"identityDocuments": [
				{
					"type": "Passport",
					"number": "BN 4196361",
					"description": "expiring 27 Oct. 2013",
					"placesOfIssue": [
						{
							"country": "PK"
						}
					],
					"datesOfIssue": [
						{
							"date": "2008-10-28"
						}
					]
				},
				{
					"type": "National Identification Number",
					"number": "33202-7126636-9",
					"placesOfIssue": [
						{
							"country": "PK"
						}
					]
				}
			],
			"additionalInformations": [
				{
					"value": "Electronics and explosives expert for Tehrik-e Taliban Pakistan (TTP) (QDe.132). Involved in attack planning for TTP. Provided financial and logistical support for TTP and participated in TTP-sponsored militant training. Reportedly deceased. Review pursuant to Security Council resolution 2253 (2015) was concluded on 21 Feb. 2019. Review pursuant to Security Council resolution 2610 (2021) was concluded on 8 November 2022. INTERPOL-UN Security Council Special Notice web link:https://www.interpol.int/en/How-we-work/Notices/View-UN-Notices-Individuals"
				}
			],
			"categories": [
				"SANCTION"
			],
			"active": true,
			"keywords": [
				"Al-Qaida"
			],
			"dataset": {
				"label": "UN",
				"category": "SANCTION",
				"dateOfPublication": "2024-01-13T00:00:05.678",
				"dateOfUpload": "2024-01-16T10:00:03.436"
			},
			"revision": 3298,
			"created": "2023-03-26T22:00:04.673",
			"updated": "2024-01-16T10:00:03.154",
			"lastMatched": "2023-03-26T22:00:04.673"
		}
	]
}

OFAC SDN Named Record

{
	"records": [
		{
			"dataID": "15517",
			"entityType": "individual",
			"names": [
				{
					"surname": "CHAUDHRY",
					"givenName": "Aamir Ali",
					"normalized": "aamir ali chaudhry"
				},
				{
					"surname": "CHAUDARY",
					"givenName": "Aamir Ali",
					"normalized": "aamir ali chaudary",
					"type": "a.k.a. - strong"
				},
				{
					"surname": "CHOUDRY",
					"givenName": "Aamir Ali",
					"normalized": "aamir ali choudry",
					"type": "a.k.a. - strong"
				},
				{
					"surname": "CHAUDRY",
					"givenName": "Amir Ali",
					"normalized": "amir ali chaudry",
					"type": "a.k.a. - strong"
				},
				{
					"surname": "HUZAIFA",
					"normalized": "huzaifa",
					"type": "a.k.a. - weak"
				}
			],
			"nationalities": [
				{
					"country": "PK"
				}
			],
			"datesOfBirth": [
				{
					"date": "1986-08-03"
				}
			],
			"identityDocuments": [
				{
					"type": "Passport",
					"country": "PK",
					"number": "BN4196361",
					"datesOfExpiry": [
						{
							"date": "2013-10-27"
						}
					]
				},
				{
					"type": "National ID No.",
					"country": "PK",
					"number": "33202-7126636-9"
				}
			],
			"categories": [
				"SANCTION"
			],
			"active": true,
			"keywords": [
				"SDGT"
			],
			"dataset": {
				"label": "OFAC SDN",
				"category": "SANCTION",
				"dateOfPublication": "2024-01-12T00:00:00",
				"dateOfUpload": "2024-01-16T10:10:18.132"
			},
			"revision": 6674,
			"created": "2023-03-26T22:10:11.035",
			"updated": "2024-01-16T10:10:13.445",
			"lastMatched": "2023-03-26T22:10:11.035"
		}
	]
}

UK Named Record

{
	"records": [
		{
			"dataID": "12809",
			"entityType": "individual",
			"names": [
				{
					"surname": "CHOUDRY",
					"givenName": "Aamir Ali",
					"normalized": "aamir ali choudry",
					"type": "AKA - Good quality"
				},
				{
					"surname": "CHAUDRY",
					"givenName": "Amir Ali",
					"normalized": "amir ali chaudry",
					"type": "AKA - Good quality"
				},
				{
					"surname": "CHAUDHRY",
					"givenName": "AAMIR ALI",
					"normalized": "aamir ali chaudhry",
					"type": "Primary name"
				},
				{
					"fullName": "عبد العالي ابو ذر",
					"normalized": "ebd alealy abw dhr",
					"type": "Primary name"
				},
				{
					"surname": "CHAUDARY",
					"givenName": "Aamir Ali",
					"normalized": "aamir ali chaudary",
					"type": "AKA - Good quality"
				},
				{
					"surname": "HUZAIFA",
					"normalized": "huzaifa",
					"type": "AKA - Low quality"
				}
			],
			"nationalities": [
				{
					"country": "PK"
				}
			],
			"datesOfBirth": [
				{
					"date": "1986-08-03"
				}
			],
			"identityDocuments": [
				{
					"type": "Passport",
					"number": "BN 4196361",
					"description": "Pakistani"
				},
				{
					"type": "National ID",
					"number": "33202-7126636-9",
					"description": "Pakistani national identity card"
				}
			],
			"additionalInformations": [
				{
					"type": "Other Information",
					"value": "(UK Sanctions List Ref):AQD0087. (UN Ref):QDi.312. Electronics and explosives expert for Tehrik-e Taliban Pakistan (TTP) (QDe.132). Involved in attack planning for TTP. Provided financial and logistical support for TTP and participated in TTP-sponsored militant training. Reportedly deceased. Review pursuant to Security Council resolution 2253 (2015) was concluded on 21 Feb. 2019. INTERPOL-UN Security Council Special Notice web link: https://www.interpol.int/en/notice/search/un/5741575"
				}
			],
			"categories": [
				"SANCTION"
			],
			"active": true,
			"keywords": [
				"ISIL (Da'esh) and Al-Qaida"
			],
			"dataset": {
				"label": "UK",
				"category": "SANCTION",
				"dateOfPublication": "2023-11-09T00:00:00",
				"dateOfUpload": "2024-01-16T10:12:00.085"
			},
			"revision": 2726,
			"created": "2023-03-26T22:20:03.368",
			"updated": "2023-11-14T10:20:04.036",
			"lastMatched": "2023-11-14T10:20:04.036"
		}
	]
}

EU Named Record

{
	"records": [
		{
			"dataID": "EU.3073.96",
			"entityType": "individual",
			"names": [
				{
					"fullName": "عامر علی چوہدری",
					"normalized": "eamr ely cwhdry"
				},
				{
					"surname": "Chaudhry",
					"givenName": "Aamir",
					"fatherName": "Ali",
					"normalized": "aamir ali chaudhry",
					"type": "Reportedly deceased"
				},
				{
					"fullName": "Aamir Ali Chaudhry",
					"normalized": "aamir ali chaudhry"
				},
				{
					"fullName": "Aamir Ali Chaudary",
					"normalized": "aamir ali chaudary",
					"type": "good quality alias"
				},
				{
					"fullName": "Aamir Ali Choudry",
					"normalized": "aamir ali choudry",
					"type": "good quality alias"
				},
				{
					"fullName": "Amir Ali Chaudry",
					"normalized": "amir ali chaudry",
					"type": "good quality alias"
				},
				{
					"fullName": "Huzaifa",
					"normalized": "huzaifa",
					"type": "low quality alias"
				}
			],
			"positions": [
				"Electronics and explosives expert for Tehrik-e Taliban Pakistan TTP)"
			],
			"nationalities": [
				{
					"country": "PK"
				}
			],
			"datesOfBirth": [
				{
					"date": "1986-08-03"
				}
			],
			"identityDocuments": [
				{
					"type": "National identification card",
					"country": "PK",
					"number": "33202-7126636-9"
				},
				{
					"type": "National passport",
					"country": "PK",
					"number": "BN 4196361",
					"datesOfExpiry": [
						{
							"date": "2013-10-27"
						}
					]
				}
			],
			"additionalInformations": [
				{
					"value": "(pakistani national identity card)"
				}
			],
			"categories": [
				"SANCTION"
			],
			"active": true,
			"keywords": [
				"TAQA"
			],
			"sources": [
				{
					"path": "https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=uriserv%3AOJ.LI.2023.043.01.0001.01.ENG&toc",
					"title": "TAQA",
					"dateOfPublication": "2023-02-13"
				}
			],
			"dataset": {
				"label": "EU",
				"category": "SANCTION",
				"dateOfPublication": "2024-01-15T12:40:43.699",
				"dateOfUpload": "2024-01-16T10:05:06.363"
			},
			"revision": 3307,
			"created": "2023-03-26T22:05:07.608",
			"updated": "2024-01-16T10:05:03.627",
			"lastMatched": "2024-01-15T12:05:04.471"
		}
	]
}

Additionally, we provide endpoints to import blacklisted countries, CTRP lists (cities, towns, regions, ports), and custom stopwords.

public watchlists