Check who you're paying. Keep the record.
Check customer and payee names against sanctions lists. Get a record of every check, including any required list Verifex could not check.
€49/month2,500 checksFree trialNo sales callNo annual contract
Principal PEPs included. Relatives and close associates are not.
- Coverage is explicit
- Evidence stays reviewable
- Limits are published
Why Verifex
Built to be defended, not just to answer.
A screening result is only as good as what it can show. Verifex keeps three things in the open.
Coverage is explicit
Each result says which required lists answered and which did not, so you know what was checked, and what was not.
Evidence stays reviewable
Keep the input, match reasoning and source metadata with the decision, and retrieve it later.
Limits are published
Inspect source health, methodology and our own benchmark failures before you choose.
Self-administered; failed gates are published.
How it works
From a name to a decision you can defend.
Your team always makes the final call. Verifex gives you the proof; it does not make your legal judgement.
01 · Screen
Send a name. Get the scope back with the result.
Screen a person, company or payment counterparty from your app or the dashboard. Verifex checks the sanctions, PEP and watchlist sources in your plan's scope, and tells you which ones answered.
02 · Review
Potential match — review required.
Each candidate arrives with the reason it matched, so an analyst can close it or escalate it. PEPs are kept apart from sanctions: a public role is not a designation.
03 · Prove
Keep a record of every check.
Every screening keeps a structured record: the input, why each candidate matched and the source metadata used. Retrieve it later and see whether it is durable, pending or unavailable.
No match found
A no-match is not the whole answer.
“No match found” only counts when the required lists were actually checked and their data was current. Verifex checks that each required list answered. If one did not, the result goes to review and the gap is written on the record.
A quick exact-spelling lookup never counts as a full check.
Condition 1: Required lists answered
Each list your policy requires was in scope and returned a result.
Condition 2: Current under its freshness policy
The data each required list was checked against was within its freshness policy, not merely reachable.
Condition 3: The full search ran
A quick exact-spelling lookup is a shortcut, not a full check. Nothing was cut from the search.
Any condition missing: the result goes to review, with the reason written on it.
An evidence record is written with each decision; the response says whether it is durable yet.
Products
Screen identities. Monitor submitted payments.
Two products, one set of lists and one record.
Verifex Screening
Sanctions, PEP and watchlist screening
Check people, companies and payment counterparties against configured sanctions, PEP and watchlist sources.
- Potential match — review required. Each candidate shows why it matched
- If a required list wasn't checked, we tell you
- A record of every check
Verifex Shield
Rules-based transaction monitoring
Evaluate submitted transactions against configured rules and screen the counterparty in the same call. Generally available, switched on per account.
- Five decisions: clear, review, delay, escalate, block
- Rules your team can change, test on past decisions and approve
- Cases and AML reports, with the rules that fired
Shield’s risk score is rules-based, not a probability of fraud.
Benchmark
Tested on real list names. Misses published.
We test on the names the lists really publish, through the same API you use, and we publish every pass mark we set before the test, including the ones we missed.
- real names from the OFAC and UN lists, spelled exactly as the lists publish them and sent through our live API, were flagged; none was served clear; 3 came back unresolved (October 13, 2026)
- 3,050/3,053
- of 2,000 known OFAC aliases found, in a test against the OFAC list only (September 7, 2026)
- 98.1%
- aliases of sanctioned companies and organisations found, in the same test
- 1,120/1,120
Self-administered benchmarks: we ran these tests ourselves, so they are not an independent audit. Both were measured before the engine changes deployed since October 17. The live-API test met none of the 7 pass marks we set before running it; every gate, including the failures, is on the benchmark page. Read the study · Every gate and failure
Coverage
40+ sources, each listed with where it comes from.
40+ sources catalogued. What you get depends on your plan; the public sources page shows the published scope and freshness of every list, and list health reports publisher access and screening impact separately.
- OFAC SDN and non-SDN lists
- UN Security Council
- EU, UK, Canada, Australia, Switzerland
- France, Japan, Hong Kong, New Zealand
- Azerbaijan, Czech Republic, Netherlands and more
Sanctions lists
- Principal politically exposed persons
- Brazil PEP register
- Relatives and close associates are not included
PEP data
- ADB and IDB Group debarments
- FBI and Europol most wanted
- US HHS OIG exclusions, ASIC banned persons
Watchlists and debarment
- BIS Entity List, Denied Persons, Unverified List
- US ISN nonproliferation
- EU and UK high-risk countries
Export controls and country risk
Solutions
Built for teams that move money.
Written for compliance officers, not engineers.
Plain guides to the regulations that shape screening, and how Verifex supports each one. Your policy and legal decisions stay yours.
Pricing
Clear prices. Start with a free trial.
Prices in EUR. Every plan shows which lists it covers before you pay.
Starter
€49 /month
2,500 screens/month
For teams building their first compliance screening flow.
Growth
€99 /month
10,000 screens/month
For teams scaling onboarding and review workflows.
Pro
€249 /month
50,000 screens/month
For compliance teams that need higher volume and evidence export workflows.
Every account starts with 5 free screens on Starter. No card. Starter, Growth and Pro are free for 7 days. The first payment is taken on day 8 — the monthly price, or the full year on annual billing. Cancel before then and you pay nothing.
Enterprise and Verifex Shield are priced per account, with custom volume, terms and security review. Talk to us
What is Verifex?
Verifex is a sanctions, PEP and AML screening API with a decision record behind every result. Screening checks people and companies against the sources you choose. Verifex Shield monitors transactions for fraud and AML risk and screens the counterparty in the same call. Both keep the evidence of what was checked, so a result can be explained to an auditor later.
What does Verifex screen against?
Verifex screens people and companies against sanctions lists, PEP data and watchlists, including OFAC, UK Sanctions, the United Nations, BIS and multilateral debarment lists. 40+ sources are catalogued. Coverage and update frequency vary by source; the data sources page shows the live state of each one.
Is there a free trial?
Two of them. Every new account gets 5 screens on the Starter source set (sanctions, PEP and watchlists) with no credit card, so you can test the API and read real responses before you pay; that allowance does not renew. Separately, there is a card-required trial on the paid plans: Starter, Growth and Pro are free for 7 days. The first payment is taken on day 8 — the monthly price, or the full year on annual billing. Cancel before then and you pay nothing.
What is Verifex Shield?
Shield is fraud and AML transaction monitoring. Each transaction gets one of five outcomes (clear, review, delay, escalate or block) with the rules that fired, a score, and a signed evidence record. Compliance teams can tune a rule, test it on past decisions and deploy it without engineering work. Shield is generally available and is switched on per account by Verifex, so talk to us to enable it.
Can we move from SanctionScanner to Verifex?
Yes. Shield offers a SanctionScanner-compatible API with the same paths, fields and response envelope, plus Shield's own extensions. Most integrations change the base URL and the API key. A native API is available for new integrations.
Does a potential match prove identity or wrongdoing?
No. Potential match — review required. Review the available identity context, source category and supporting evidence before deciding what to do.
Does “no match found” mean a customer is safe?
Not by itself. “No match found in the lists checked” only goes on your normal path when the full standard check ran (not a quick exact-spelling lookup), every list in scope answered, nothing was cut from the search and the proof was saved. If any of that is missing, the result goes to review and the reason is written on it. The legal decision always stays with your team.
Is a PEP the same as a sanctioned person?
No. A sanctioned person is someone you are legally barred from dealing with. A PEP (politically exposed person) holds a prominent public role and needs extra checks, not a ban. Verifex keeps the two apart: a PEP result never becomes a sanctions-grade result by itself. Verifex PEP data covers principal PEPs only; relatives and close associates are not included.
What does it mean that a decision can be replayed?
Every screening saves what was searched, why each possible match matched, which version of each list was used and which engine version ran, all tied to a unique fingerprint (a decision hash). Months later, your team can show exactly what was checked and why, instead of relying on a screenshot or the final label.
What do the benchmark numbers mean?
Verifex publishes two self-administered benchmarks: tests we ran ourselves, not an independent audit. In the live-API test of October 13, 2026, 3,050 of 3,053 real names from the OFAC and UN lists, spelled exactly as the lists publish them and sent through the same API customers use, were flagged; none was served clear; 3 came back unresolved. That test met none of the 7 pass marks we set before it ran, and every gate, including the failures, is published on the benchmark page. The second test looked up 2,000 aliases that OFAC publishes, against the OFAC list only, on September 7, 2026. Both were measured before the engine changes deployed since October 17; the next live test will measure those.
Start with a workflow you can test.
Review the plan scope, create an API key and test the responses your team will need to handle.