AML / Sanctions Screening
Screen every user. Stay screened forever.
A clean check at onboarding is not enough. Amani screens every user against global sanctions, PEP and adverse-media sources in real time - then keeps monitoring them daily, so you hear about a hit before your regulator does.
Capabilities
What AML / Sanctions Screening gives you.
Global watchlists
OFAC, UN, EU, UK HMT and hundreds of regional sanctions and enforcement lists, updated continuously.
PEP coverage
Politically exposed persons across four tiers, with relatives and close associates included.
Adverse media
Structured negative-news screening that separates real risk stories from name-match noise.
Fuzzy matching, tuned
Configurable matching thresholds handle transliteration, aliases and partial dates of birth without drowning you in false positives.
Ongoing monitoring
Re-screening of your whole customer base as the lists change, with alerts only when something material changes. $0.10 per user a year, on Compliance and Enterprise.
Case management
Review, resolve and document every hit in Amani Studio - with a full audit trail for your MLRO.
From session to signed result.
Four steps - the same integration pattern as every Amani module.
Create a session
One API call (or a Studio journey) starts a verification session for this module.
User completes the flow
Your customer is guided through capture in your branded UI - web or mobile.
Checks run in real time
AML / Sanctions Screening executes alongside any other modules in the journey.
You receive a signed result
A webhook delivers the decision, scores and evidence to your backend.
For developers
Integrate AML / Sanctions Screening.
Authenticate, create a profile, generate a verification URL - then let Amani handle the rest. Or describe what you want to your AI coding agent and let Amani Skills wire it up from the live docs.
Available on
verify.sh
# 1 · Authenticate (server-side only)
curl -X POST 'https://ae.amani.ai/api/v2/user/login/' \
--form 'username="you@company.com"' \
--form 'password="••••••••"'
# 2 · Create the customer profile
curl -X POST 'https://ae.amani.ai/api/v2/profile' \
-H 'Authorization: Bearer $ACCESS_TOKEN' \
--form 'id_card_number="784199012345678"' \
--form 'name="Layla Haddad"'
# 3 · Generate the verification URL
curl -X POST 'https://ae.amani.ai/api/v2/profile/url' \
-H 'Authorization: Bearer $ACCESS_TOKEN' \
-H 'Content-Type: application/json' \
--data '{
"profile": PROFILE_ID,
"web_sdk_url": "https://verify.amani.ai",
"language": "en",
"return_url": "https://yourapp.com/verified"
}'
# AML / Sanctions Screening runs inside this session - configure it in Amani Studio.aml-screen.sh
# Screen a person against 210+ sanctions, PEP and
# adverse-media sources across 48 jurisdictions.
curl -G 'https://ae.amani.ai/api/v2/aml/search' \
-H 'Authorization: Bearer $ACCESS_TOKEN' \
--data-urlencode 'name=Layla Haddad' \
--data-urlencode 'birth_date=1990-04-17'
# Retrieve the full report for a match
curl 'https://ae.amani.ai/api/v2/aml/report/{report_id}' \
-H 'Authorization: Bearer $ACCESS_TOKEN'with Amani Skills
# Install Amani Skills once
npx -y github:AMANI-AI-ORG/skills --global
# Then ask your coding agent:
You › In our Node backend, screen every new customer against Amani AML on signup and store the report ID against their record.
# The matching skill fetches the live docs, pins the
# current SDK version and wires up the integration -
# secrets left as placeholders. Claude Code, Cursor and
# any Agent-Skills-compatible tool.webhooks.ts
// Amani signs every webhook with an HMAC signature using
// your secret. Always verify it before processing.
import crypto from 'node:crypto';
app.post('/webhooks/amani', (req, res) => {
// Confirm the exact header name in the Webhooks API reference.
const signature = req.get('X-Amani-Signature') ?? '';
const expected = crypto
.createHmac('sha256', process.env.AMANI_WEBHOOK_SECRET)
.update(req.rawBody)
.digest('hex');
const valid =
signature.length === expected.length &&
crypto.timingSafeEqual(Buffer.from(signature), Buffer.from(expected));
if (!valid) return res.status(401).end();
const { profile, status } = req.body;
if (status === 'approved') activateAccount(profile);
res.status(200).end();
});AML / Sanctions Screening - common questions
How do you keep false positives down?
Matching is tuned per list and per market - transliteration-aware name matching, secondary identifiers and risk-based thresholds typically cut review queues dramatically.
How fresh is the list data?
Sanctions lists are refreshed continuously and your customer base is re-screened daily on monitoring plans.
Can screening run standalone?
Yes - call the screening API directly with a name and date of birth, or run it as part of a KYC or KYB flow.
Related modules
Add AML / Sanctions Screening to your flow
Switch it on in Amani Studio, or call it directly from the API.
