Screening inside your own systems
Send a name from your onboarding, payments or case system. Get back the records that match, the lists they came from, and a report you can keep.
Your system sends
- Name
- Jane Doe
- What it is
- An individual
- Date of birth
- 1981
- Country
- United Kingdom
- Closest matches
- up to 10
Signed with your key’s secret and time-stamped.
AMLPRO returns
- Matches
- 1 record
- Match
- 100% on name
- Found on
- 3 sanctions and exclusion lists
- Topics
- sanction · debarment
- Report
- ready to download
Charged to your balance and written to your usage log.
Six things happen on every call
In this order, whether the search comes from your code or from the console.
-
01
Verified
The request is signed with your key’s secret and carries the time it was made, so it can’t be forged or replayed later.
-
02
Checked
The key, the account, where the call came from and your plan all have to allow this kind of search.
-
03
Matched
Every name, alias and transliteration close enough to the one you sent becomes a candidate.
-
04
Filtered
Your own workflow keeps or drops each candidate, using the details you sent with the name. A detail you leave out is simply skipped.
-
05
Charged
Your plan’s price for that kind of search comes out of your prepaid balance. A search that finds nothing is still a search.
-
06
Recorded
The search lands in your usage log with what it found and what it cost, and a PDF report is prepared.
A key for every integration, and only what it needs
Keys are created in the console by the people on your team whose role allows it.
One per integration
Create as many as you need. Each has its own secret, shown once when you create it and never again.
Scoped to a job
Choose what each key may do — run screenings, download reports, or both. A key asked for more is refused.
Locked to your servers
Optionally allow a key to be used only from the addresses you list. A call from anywhere else is turned away.
Expire or revoke
Give a key an end date, or delete it the moment an integration is retired. Your other keys carry on.
Where to send it
The address your requests go to is shown beside the key when you create it, with everything you need to copy.
One log for everything
Searches from your code land in the same usage log as searches made in the console, so both can be answered for.
It says why, and what to fix
A refused call is never a silent failure or a vague error. It names the problem in a sentence your developers can act on.
- Something is missing or out of rangeThe refusal names the field.
- The signature doesn’t check outOr the request is too old to accept.
- The call came from somewhere not allowedIt names the address that was turned away.
- Your plan or key doesn’t cover itIt names the service or permission.
- The balance won’t cover the searchIt states the price and what’s left.
- Too many calls, too quicklyIt says how long to wait before trying again.
From sign-up to your first screening
- 1
Create an account. Every account starts on the free plan, which includes individual screening, so you can integrate before you buy anything.
- 2
In the console, create a key: choose what it may do, and copy the secret and the address shown with it.
- 3
Sign each request with the secret and send a name, with any details your workflow compares.
- 4
Read the result and keep the report. When you want fewer, better matches, build a workflow and every call follows it.
Ready to integrate AMLPRO?
Start on the free plan, create a key in the console, and screen your
first name from your own systems.