Sanctions and PEP watchlist screening
One search returns nine categories of matches from public sources. Every hit arrives cross-checked, detail by detail, against your customer’s file.
One match in the politically exposed person category. It is recorded in the file without holding up the onboarding.
Every hit is cross-checked against your customer’s details.
Singula searches the name across nine list categories and compares every hit with the date of birth, country and ID you already saved. Contradicted hits are discarded. Confirmed ones arrive with their degree of certainty and their evidence.
- DateCountryIDNamesake
- DateCountryIDYour customer
- DateCountryIDNamesake
One name shows up across the sources with different people behind it. The answer counts how many there are and checks each one against your file.
How it works, step by step
One search against the customer file you already created, with the answer in the same exchange.
Data from the file
The search is built from the details you already saved for the customer: name and surnames, date of birth, country, gender and official ID.
Name · date of birth · country · gender · ID
Data cross-check
The search compares every hit with the date of birth, country, gender and ID you saved for the customer.
Each detail confirms or contradicts the hit
Filtered answer
Hits contradicted by the cross-check are left out of the answer. The ones that arrive carry their degree of certainty and their evidence.
All nine categories are reviewed in every search
Result in the same query
The answer to the search includes the risk level and the evidence behind it.
The complete answer in a single step
The nine categories
All nine come from public sources and are reviewed in every search, whether or not they return hits. Three are critical and only they take the verdict to its highest level. The three informational ones are recorded without moving the verdict.
Sanctions
People and companies named in sanctions programmes issued by authorities. The most serious of the nine.
Criminal
Flags of criminal origin published by authorities.
Tax
Flags of tax origin published by authorities.
Debarment
People and companies barred from contracting with the public sector.
Export control
Restrictions on dealing in controlled goods.
Other
Published flags that do not fall under any of the categories above.
Politically exposed person
Public office holders and the people close to them. The match is reported as informational, without moving the verdict.
State-owned company
State participation in the company.
Adverse media
Mentions of the person or the company in negative press.
What each level means
The level depends on which category matched and how solid that match turns out to be. It indicates the priority at which the file goes to review.
Every hit includes its degree of certainty and the way it appeared: the name verbatim, an alias or a spelling variant. The answer adds the field-by-field cross-check, with the details that support the hit and the ones that contradict it.
- High
A critical category matched with high certainty. It is the only level the search flags as a stop.
- Medium
A less solid critical hit, or a hit in a relevant category. The level sends the file to manual review.
- Informational
An informational category matched. It is recorded in the file without holding up the onboarding.
- Low
Low-certainty hits. They are recorded in the file.
- Clear
None of the nine categories returned anything relevant. With a date and a receipt, it goes on record in the file.
What you get back
The level, the evidence and the receipt, in the same shape on every search.
The verdict of the search in one word: high, medium, informational, low or clear.
Example informational
API field: risk_summary.level · stringHow solid the best match found for that customer is.
Example 78
API field: best_certainty · numberWhich of the nine categories returned hits.
Example pep
API field: categories_found · string[]Every category comes back in the answer even when it is empty.
API field: groups · objectFull name, known aliases, date of birth, nationality and identity numbers of the flagged person.
API field: results · arrayWhether the name matched verbatim, through an alias, a spelling variant or one that merely sounds alike.
Example fuzzy
API field: match_type · stringDetail by detail, whether it matched your customer, contradicted them or was never sent.
API field: attribute_analysis · objectThe short list of details that reinforce the hit and the ones that disprove it.
API field: confirms · conflicts · string[]A readable summary of why that hit ended up at that degree of certainty.
API field: explanation · stringThe publication the flag came from and the country of that source.
API field: source_list · source_country · stringThe direct link to read the flag where it was published.
API field: source_url · string | nullHow many people share that name across the sources and which countries they are from.
API field: disambiguation · objectThe date and time the search ran.
Example 2026-07-28T10:31:00Z
API field: checked_at · stringA unique identifier to audit or trace this search.
Example req_9c4b2ad17e
API field: request_id · stringHow it fits your operation
Where the search runs within onboarding, periodic review and the customer file.
At onboarding
Run the search before approving the account. The level indicates whether the file needs review and at what priority.
At periodic review
Run it again whenever your policy says so: every quarter, or at contract renewal. Every run keeps its own date.
In the customer file
Every search leaves a record with a date and a receipt, even when it comes back clean.
Alongside identity verification
The search works on the name and details in the file. CURP validation and biometric verification confirm the person’s identity.
The final decision
The answer delivers the level and the evidence with its source. Accepting, rejecting, escalating or filing with the authority is defined by your compliance policy.
The regulatory references on this page are orientative and are not legal advice. The acceptance policy, the privacy notice, the consent and any filing with the authority belong to the entity and its compliance officer.
Everything runs through the API.
Every operation on this page runs as an API call. The full field-by-field reference is in the documentation.
- Use it directly (the value in the body) or on a customer file. Same response.
curl https://api.singula.mx/app/blacklist/customer/cus_lzk9m4ab3f \
-H "Authorization: Bearer sk_live_..."
→ {
"request_id": "6622f8a1c1d2e3f4a5b6c7d8",
"data": {
"query": "MARIA GARCIA RODRIGUEZ",
"risk_summary": {
"level": "clear",
"best_certainty": 0,
"categories_found": []
},
"checked_at": "2026-07-28T10:31:00Z"
}
}Frequently asked questions
The match is reported as informational and recorded in the file without moving the verdict. It arrives with its source and its cross-check, like any other hit. Applying enhanced due diligence is defined by your compliance policy.
The cross-check discards hits contradicted by the customer’s details before building the answer. The more details the file holds (date of birth, country, ID), the more namesakes are ruled out.
The answer carries the namesake count and the country of each one. Every hit comes with the details that confirm it and the ones that contradict it.
A clean result across the nine categories, with the date the search ran and its receipt. The record registers that the review ran that day and on that customer.
Yes. The search is built from the customer file registered in Singula. The test environment costs nothing.
Run your first search
The test environment costs nothing and includes the complete flow: the search, the level and the evidence for each hit.
Create free account