Questions, answered plainly

AMLPRO screens people, companies and organizations against sanctions, PEP, watchlist and adverse-media data — from a console your team uses and an API your systems call, under matching rules you write yourself. Every search is kept on record with a PDF report.

Four: individual, company, organization and adverse media. An individual, company or organization search checks sanctions, PEP and watchlist data together. Adverse media is its own search, and can run in the same search on plans that include it.

Hundreds of sources — among them the US OFAC SDN list, the UN Security Council consolidated list, the EU Financial Sanctions Files, the UK HMT/OFSI and FCDO lists, INTERPOL Red Notices, the FBI Most Wanted, the World Bank debarment list and Wikidata PEPs. The Sources page in your console lists every source your account screens against, by country.

No. A screening runs when you ask for one. To review customers again, re-screen them through the API on the schedule your policy sets — each result filed under your own reference.

No. Each match comes with its evidence — which name matched, a match score, topics, sources and the full record — and your team applies your own risk rating. The match score measures how close the name is, not how risky the person is.

No. AMLPRO screens names. Identity-document checks, wallet screening and transaction monitoring come from specialist tools that sit alongside it.

Three ways: a match threshold (the lowest score that comes back), a result limit, and your workflow, which compares details such as date of birth, country, passport or registration number and drops look-alikes before anyone reviews them. A detail you don’t send is simply skipped.

A chain of steps you build for each kind of search. The name match always comes first; you decide what each later step compares and where records go when it matches or doesn’t. Every search follows it, in the console and through the API. See the workflow builder.

Which of the record’s names your search hit: the listed name, one of its aliases, or a weak alias the list itself marks as low-quality.

Your system signs each request with your key’s secret, time-stamps it, and sends a name with any details your workflow compares. It gets back each matching record with its sources and score, and a link to the PDF report. How a call works.

Yes. Each key can be limited to screening, to report downloads or both, to the addresses you list, and to an end date. Each key also has its own rate limit.

There’s no separate sandbox. Every account starts on a free plan with individual screening, so you can build and test the integration against the real service before you buy anything.

It says why — a missing field, a signature or timestamp that doesn’t check out, an address that isn’t allowed, a plan or key that doesn’t cover the search, not enough balance, or too many calls too quickly.

Yes. Every account starts on a free plan that includes individual screening. Company and organization screening, adverse media, workflows and team features come with a paid plan. See plans.

Top up a prepaid balance and each search is charged at your plan’s price. AML and adverse media are priced separately, and a search that runs both is charged for both. On Pay as you go, what you use is invoiced to you afterwards instead.

Yes. A clear result is still a screening: it’s kept on record, it has a report, and it’s charged like any other search.

Passwords are kept only as salted PBKDF2 hashes, anyone can add an authenticator code to their sign-in, the console signs itself out after ten idle minutes, and roles are enforced by the server. More on security.

Yes. Invite colleagues by email and give each a role. Your plan includes a number of seats; extra seats are invoiced separately, never taken from your screening balance.

What was asked, what was found, what it cost, and where it came from — the time, the key and the address — with a PDF report for each one.

Create an account, and you’re on the free plan straight away. Screen from the console, or create a key and call the API. If you’d rather talk it through first, get in touch.

Yes. Customers can message our team from inside the console and see replies as they arrive, and anyone can reach us through the contact page.