Chunguza mtumiaji au kampuni yoyote dhidi ya hifadhidata 1,300+ za vikwazo, PEP (mtu aliye wazi kisiasa), habari hasi, na orodha za uangalizi. $0.20 kwa kila ukaguzi, $0.07/mtumiaji/mwaka kwa ufuatiliaji endelevu. 500 bila malipo/mwezi.
Robinhood Ventures
Inaaminika na mashirika 2,000+ duniani kote.
Orodha za uangalizi 1,300+
Simu moja inashughulikia vikwazo vya kimataifa, PEPs, jamaa na washirika wa karibu, habari hasi, na maonyo. Iunganishe ndani ya KYC kamili, au sasisha kila mtumiaji kila siku kwa $0.07 kwa mwaka.
Chagua ukaguzi unaotaka, ID, liveness, face match, vikwazo, anwani, umri, simu, barua pepe, maswali maalum. Ziburute kwenye mtiririko kwenye dashibodi, au tuma mtiririko huo huo kwenye API yetu. Panga masharti, fanya majaribio ya A/B, hakuna code inayohitajika.
Pachika asili na SDK yetu ya Web, iOS, Android, React Native, au Flutter. Elekeza kwenye ukurasa uliopangishwa. Au tuma tu kiungo kwa mtumiaji wako, kwa barua pepe, SMS, WhatsApp, popote. Chagua kinachofaa stack yako.
Didit inasimamia kamera, ishara za mwanga, uhamishaji wa simu, na ufikiaji. Wakati mtumiaji yuko kwenye mtiririko, tunapata alama za ishara 200+ za udanganyifu kwa wakati halisi na kuthibitisha kila sehemu dhidi ya vyanzo vya data vya mamlaka. Matokeo chini ya sekunde mbili.
Webhooks zilizosainiwa kwa wakati halisi huweka hifadhidata yako sawa mara tu mtumiaji anapoidhinishwa, kukataliwa, au kutumwa kwa ukaguzi. Piga API kwa mahitaji. Au fungua console kukagua kila kikao, kila ishara, na kudhibiti kesi kwa njia yako.
Inaburudishwa mfululizo
Orodha za kimataifa
Kategoria
Mamlaka
Onyesha upya
Endpoint moja · POST /v3/aml/
Ngazi 1–4 · RCA
Alama ya kulingana · Alama ya hatari
Uchunguzi upya wa kila siku · $0.07 / mtumiaji / mwaka
FATF · AMLD6 · OFAC · MiCA
$ curl -X POST https://verification.didit.me/v3/session/ \
-H "x-api-key: $DIDIT_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"workflow_id": "wf_kyc_aml",
"vendor_data": "user-42"
}'{ "session_url": "verify.didit.me/..." }$ curl -X POST https://verification.didit.me/v3/aml/ \
-H "x-api-key: $DIDIT_API_KEY" \
-d '{
"entity_type": "person",
"full_name": "Carmen Espanola"
}'{ "status": "Approved", "total_hits": 0 }# Didit AML Screening — integrate in 5 minutes
You are integrating Didit's Anti-Money Laundering (AML) Screening module into
<my_stack>. Follow these steps exactly. Every URL, header, and enum value
below is canonical — do not paraphrase or "improve" them.
AML Screening covers four lookup categories on every call:
- Sanctions (OFAC, EU, UN, HMT, and 1,300+ more global lists)
- Politically Exposed Persons (PEPs) — Levels 1 through 4 + RCAs
- Adverse Media — financial-crime news, court records, regulatory press
- Warnings and Regulatory Enforcement, Insolvency, SIP / SIE lists
The same module screens BOTH persons and companies — set the
"entity_type" parameter to "person" or "company".
## 1. Provision an account
- Sign up: https://business.didit.me (no credit card required).
- Or provision programmatically: POST https://apx.didit.me/auth/v2/programmatic/register/
(returns an API key bound to the workspace + application).
## 2. Two integration paths — pick one
### Path A — Workflow Builder (hosted UI / linked KYC)
Best when you want AML screened automatically as part of a verification
session. Run it alongside ID Verification, or chain it after a Know Your
Customer (KYC) check, or fire it on its own.
1. Create a workflow that contains the AML feature:
POST https://verification.didit.me/v3/workflows/
Authorization header: x-api-key: <your-api-key>
Body: workflow_label, features array with the entry
{ "feature": "AML" } (UPPERCASE — strict enum)
Optional per-workflow configuration:
- match_score_threshold (default 93)
- approve_risk_threshold (default 80)
- review_risk_threshold (default 100)
- include_adverse_media (default true; adds ~10s to the call)
- include_ongoing_monitoring (default false; +$0.07/user/year if on)
- sanctions_categories (subset of dataset enums)
2. Create a verification session for an end user:
POST https://verification.didit.me/v3/session/
Body: workflow_id (from step 1), vendor_data (your own user id),
expected_details { first_name, last_name, date_of_birth,
nationality, document_number }.
Response: session_url — redirect the user to it. If your workflow has
only the AML feature and you already collected the identity fields,
the session resolves server-side with no UI step.
3. Listen for webhook callbacks (see "Webhooks" below).
### Path B — Standalone server-to-server API
Best when you already have the screened entity's name + identifiers and
do not want a hosted session. Synchronous response, no webhook needed.
POST https://verification.didit.me/v3/aml/
Content-Type: application/json
Headers:
x-api-key: <your-api-key>
Body (person):
{
"entity_type": "person",
"full_name": "Carmen Espanola",
"date_of_birth": "1980-01-01",
"nationality": "ESP",
"document_number": "CAA000000",
"include_adverse_media": true,
"include_ongoing_monitoring": false
}
Body (company):
{
"entity_type": "company",
"full_name": "Acme Holdings Ltd",
"registration_number": "12345678",
"incorporation_country": "GBR",
"include_adverse_media": true
}
Response: JSON report with status, hits, scores, and a warnings array.
## 3. Webhooks (Path A and Path B ongoing monitoring)
- Register a webhook destination once via
POST https://verification.didit.me/v3/webhook/destinations/
Body: url, subscribed_events: ["session.verified", "session.review_started",
"session.declined", "aml.new_hit"]
- Response includes secret_shared_key — store it.
- Every webhook delivery carries an X-Signature-V2 header you MUST verify
before trusting the payload. HMAC-SHA256 verification MUST run against the raw body bytes (the raw payload as Didit sent it) BEFORE any JSON parsing — re-serialising the parsed body changes whitespace and key order, which invalidates the signature.Algorithm:
1. sortKeys(payload) recursively
2. shortenFloats (truncate trailing zeros after the decimal point)
3. JSON.stringify the result
4. HMAC-SHA256 with the secret_shared_key
5. Hex-encode, compare to the X-Signature-V2 header.
## 4. Reading the report (both paths return the same shape)
The aml object includes:
- status: "Approved" | "Rejected" | "In Review" | "Not Started"
- total_hits: integer
- score: number 0-100 (overall AML risk score; highest non-False-Positive
match risk score wins)
- screened_data: the inputs used for the lookup
- hits: array of matched entities. Each hit includes:
- id, url, caption (matched display name)
- datasets: which categories matched (PEP, PEP Level 1..4, Sanctions,
Adverse Media, Warnings and Regulatory Enforcement, Fitness and
Probity, SIP, SIE, Insolvency)
- match_score (0-100, identity confidence — is it the same person)
- risk_view.categories.score (0-100, entity risk if it IS a match)
- sanction_matches, pep_matches, warning_matches,
adverse_media_matches (typed arrays with list names, source URLs,
legal basis, sanction program, sanctioning authority, publication
dates, sentiment scores, etc.)
- warnings: Array<{ risk, log_type, short_description, long_description }>
Two-score system (the part most agents get wrong):
1. Match Score answers "is this the same person we are screening".
Below the match_score_threshold (default 93) the hit is a
False Positive and excluded from the final status. At or above the
threshold it is Unreviewed (a possible match).
2. Risk Score answers "how risky is this entity if it IS a match".
The session's final status comes from the highest risk score among
non-False-Positive hits:
- risk score below approve_risk_threshold (80) => Approved
- between approve and review => In Review
- above review_risk_threshold (100) => Declined
Warning codes you should branch on:
- POSSIBLE_MATCH_FOUND (informational — at least one hit above the
match threshold; review or auto-approve
per your risk policy)
- COULD_NOT_PERFORM_AML_SCREENING (KYC fields incomplete; session is held
in In Review and re-triggered automatically
once full_name, date_of_birth, issuing
state and document_number are populated)
## 5. Hard rules — do not change
- Base URL for /v3/* endpoints is verification.didit.me (NOT apx.didit.me).
- Feature enum is UPPERCASE: AML, ID_VERIFICATION, LIVENESS, FACE_MATCH,
IP_ANALYSIS. The AML feature flag is AML, not AML_SCREENING.
- Auth header is x-api-key (lowercase, hyphenated).
- Webhook signature header is X-Signature-V2 (NOT X-Signature).
- Always verify webhook signatures before trusting payload data.
- Status casing matches exactly: "Approved", "Rejected", "In Review",
"Not Started" (title-cased, space-separated).
- entity_type is lowercase: "person" or "company".
## 6. Ongoing monitoring
- Toggle include_ongoing_monitoring=true on the workflow or the standalone
request to enroll the screened entity in continuous AML monitoring.
- Didit rescreens every enrolled entity DAILY against the full 1,300+
watchlist database (sanctions, PEPs, adverse media, warnings).
- A status change (new hit above review or decline threshold) fires the
aml.new_hit webhook, flips the session status to In Review or Declined,
and surfaces the hit in the Business Console with full audit trail.
- Billing: $0.07 per enrolled entity per year. Toggle off at any time
from the Business Console — billing prorates to the day.
## 7. Pricing reference (public)
- AML Screening (one-time, per person OR per company): $0.20 per check
- Ongoing AML Monitoring: $0.07 per enrolled entity per year
- Bundled inside a full KYC workflow (ID + Liveness + Face Match + IP):
$0.33 per session — AML is an add-on at the same $0.20 standalone price
- 500 free checks every month, forever, on every account.
## 8. Verify your integration
- Sandbox starts on signup at https://business.didit.me — no separate flag.
- Test names: deterministic synthetic entities returned in sandbox
(Approved by default; canonical "PEP test name" returns an In Review
with a Wikidata PEP hit so you can exercise the review queue).
- Switch to live: flip the application environment toggle in the console.
When in doubt: https://docs.didit.me/core-technology/aml-screening/overview
$0 / mwezi. Hakuna kadi ya mkopo inayohitajika.
Lipa tu kwa unachotumia. Moduli 25+. Bei za umma kwa kila moduli, hakuna ada ya chini ya kila mwezi.
MSA & SLA maalum. Kwa idadi kubwa na programu zilizodhibitiwa.
Anza bure → lipa tu wakati ukaguzi unafanyika → fungua Enterprise kwa mkataba maalum, SLA, au uhifadhi wa data.
Didit ni miundombinu ya utambulisho na udanganyifu, jukwaa ambalo tulitamani lingekuwepo tulipokuwa tukijenga bidhaa sisi wenyewe: wazi, rahisi, na rafiki kwa waendelezaji, ili lifanye kazi kama sehemu halisi ya stack yako badala ya sanduku jeusi unalounganisha.
API moja inashughulikia kuthibitisha watu (KYC, mjue mteja wako), kuthibitisha biashara (KYB, mjue biashara yako), kuchunguza pochi za crypto (KYT, mjue muamala wako), na kufuatilia miamala kwa wakati halisi, kwenye stack iliyojengwa kuwa:
Alama ya chini: aina 14,000+ za hati katika lugha 48+, vyanzo vya data 1,000+, na ishara za udanganyifu 200+ kwenye kila kipindi. Miundombinu ya Didit hujifunza kwa nguvu kutoka kila kipindi na inakuwa bora kila siku.
OFAC), Umoja wa Ulaya, Umoja wa Mataifa, Hazina ya HM ya Uingereza, na kila orodha ya kitaifa ya G20. Watu Walio Wazi Kisiasa katika ngazi nne, PEP Level 1 (wakuu wa nchi, majaji wa mahakama kuu, mabenki makuu), PEP Level 2 (wabunge, mabalozi, viongozi wa kijeshi), PEP Level 3 (watumishi wa umma wa ngazi ya kati, serikali za mitaa), PEP Level 4 (Ndugu na Washirika wa Karibu / RCAs). Habari mbaya, Maonyo na Utekelezaji wa Udhibiti, Usawa na Uaminifu, Kufilisika, SIP (Watu Wenye Maslahi Maalum), SIE (Mashirika Yenye Maslahi Maalum), na orodha zako maalum. Katalogi kamili inasasishwa kila mara, angalia docs.didit.me/core-technology/aml-screening/watchlist-database-aml-screening.aml cha JSON. status ya juu ni mojawapo ya Approved, Rejected, In Review, au Not Started. Kitu hicho kinajumuisha total_hits, score ya jumla (0–100, alama ya juu zaidi ya hatari isiyo ya False-Positive), block ya screened_data inayoakisi pembejeo zilizotumika, array ya warnings yenye misimbo ya risk iliyopangwa, na array ya hits. Kila hit hubeba id, url, caption, datasets (ambazo kategoria zilingana), match_score (uhakika wa utambulisho 0–100), risk_view.categories.score (hatari ya chombo 0–100), na sub-arrays zilizochapishwa, sanction_matches, pep_matches, warning_matches, adverse_media_matches, zenye majina ya orodha, URL za chanzo, msingi wa kisheria, mamlaka ya vikwazo, tarehe za kuchapishwa, na alama za hisia. Marejeleo kamili yanapatikana docs.didit.me/core-technology/aml-screening/report-aml-screening.Mchakato mzima kwa kawaida huchukua chini ya sekunde 30 kuanzia mwanzo hadi mwisho, chukua kitambulisho, piga picha hati, piga picha selfie, umemaliza. Hiyo ndiyo kasi zaidi sokoni. Watoa huduma wa zamani wa KYC kwa kawaida huchukua zaidi ya sekunde 90 kwa mchakato huo huo.
Kwa upande wa nyuma, Didit inarudisha matokeo kwa chini ya sekunde mbili kwa p99, ikipimwa kuanzia wakati mtumiaji anamaliza selfie hadi wakati webhook yako inapoanza. Upigaji picha wa simu umeboreshwa kwa simu za polepole na mitandao ya polepole: ukandamizaji wa picha unaoendelea, upakiaji wa polepole wa SDK, na uhamishaji wa kugusa mara moja kutoka kompyuta hadi simu kupitia msimbo wa QR ikiwa mtumiaji anaanza kwenye wavuti.
match_score (0–100, kizingiti cha msingi 93) huamua ikiwa hit ni mtu yule yule, uzito wa kufanana kwa jina 60%, tarehe ya kuzaliwa 25%, nchi 15%, na kibali cha nambari ya hati ya Golden Key ambayo inaweza kuweka alama hadi 100. risk_score (0–100, idhini ya msingi 80 / ukaguzi 100) huamua jinsi chombo kilivyo hatari ikiwa NI mechi, uzito wa kategoria 50%, nchi 30%, rekodi za uhalifu 20%. Hits zilizo chini ya kizingiti cha mechi huainishwa kama False Positive na huondolewa kwenye hesabu ya hali ya mwisho. Hali ya mwisho ya kipindi hutumia alama ya juu zaidi ya hatari kati ya hits zilizobaki zisizo za False-Positive.Kila kipindi huishia kwenye mojawapo ya hali saba zilizo wazi, kwa hivyo msimbo wako unajua nini cha kufanya kila wakati:
Approved, kila ukaguzi umefaulu. Endeleza mtumiaji.Declined, ukaguzi mmoja au zaidi umeshindwa. Unaweza kumruhusu mtumiaji kutuma tena hatua maalum iliyoshindwa (kwa mfano, piga tena selfie) bila kurudia mchakato mzima.In Review, imewekwa alama kwa ukaguzi wa kufuata. Fungua kesi kwenye console, angalia kila ishara, amua kuidhinisha au kukataa.In Progress, mtumiaji yuko katikati ya mchakato.Not Started, kiungo kimetumwa, mtumiaji bado hajafungua. Tuma ukumbusho ikiwa itakaa muda mrefu sana.Abandoned, mtumiaji alifungua kiungo lakini hakumaliza kwa wakati. Rudisha ushiriki au muda wake uishe.Expired, kiungo cha kipindi kimepitwa na wakati. Unda kipindi kipya.Webhook iliyosainiwa huwaka kwenye kila mabadiliko ya hali, kwa hivyo hifadhidata yako inabaki sawa kila wakati. Vipindi vilivyoachwa na vilivyokataliwa ni bure.
Data ya uzalishaji inachakatwa na kuhifadhiwa katika Umoja wa Ulaya kwa chaguo-msingi, kwenye Huduma za Wavuti za Amazon. Mikataba ya biashara inaweza kuomba maeneo mbadala kwa mamlaka ambayo wadhibiti wao wanahitaji.
Usimbaji fiche kila mahali. AES-256 wakati wa kupumzika katika kila hifadhidata, hifadhi ya kitu, na chelezo. Usalama wa Tabaka la Usafiri 1.3 wakati wa usafiri kwenye kila simu ya API, webhook, na kipindi cha Business Console. Data ya kibayometriki imesimbwa kwa ufunguo tofauti wa Mteja Mkuu.
Uhifadhi ni wako kudhibiti. Uhifadhi wa msingi ni usio na kikomo (usio na ukomo) isipokuwa ukisanidi mfupi zaidi, kati ya siku 30 na miaka 10 kwa kila programu, na unaweza kufuta kipindi chochote cha kibinafsi wakati wowote kutoka kwenye dashibodi au API.
Vyeti: SOC 2 Aina ya 1 (ukaguzi wa Aina ya 2 unaendelea), ISO/IEC 27001:2022, iBeta Level 1 PAD, na uthibitisho wa umma kutoka Tesoro / SEPBLAC / CNMV ya Uhispania kwamba uthibitishaji wa utambulisho wa mbali wa Didit ni salama zaidi kuliko kumthibitisha mtu ana kwa ana. Ripoti kamili inapatikana /security-compliance.
Didit inatii sheria kwa chaguo-msingi kwa wadhibiti muhimu kwa miundombinu ya utambulisho:
Memo ya kina, kila cheti, kila barua ya mdhibiti: /security-compliance.
Njia tatu za kuunganisha, chagua inayofaa stack yako:
Dashibodi sawa, bili sawa, bei sawa ya kulipa kwa mafanikio kwa zote tatu. Mwongozo wa hatua kwa hatua unapatikana docs.didit.me/integration/integration-prompt.
API moja kwa KYC, KYB, Ufuatiliaji wa Miamala, na Uchunguzi wa Wallet. Unganisha ndani ya dakika 5.