Chunguza mtumiaji yeyote. Dhidi ya orodha 1,300+ za kimataifa.
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.
PEPs, vikwazo, taarifa hasi. Zote kwa simu moja ya $0.20.
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.
Jinsi inavyofanya kazi
Kuanzia kujisajili hadi mtumiaji aliyethibitishwa kwa hatua nne.
Hatua 01
Unda mtiririko wa kazi
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.
Hatua 02
Unganisha
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.
Hatua 03
Mtumiaji anapitia mtiririko
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.
Hatua 04
Unapokea matokeo
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.
Imejengwa kwa ajili ya kufuata sheria · Imejengwa dhidi ya udanganyifu · Wazi kwa muundo
Uwezo sita. Feature flag moja. AML.
Kila uwezo hapa chini ni swichi kwenye moduli moja. Hakuna viwango vya kuongeza mauzo, hakuna SKU tofauti, hakuna simu za nyongeza. Ziwasha kwa kila mtiririko wa kazi kwenye console au zipitishe ndani ya simu ya API.
Orodha 1,300+ za kimataifa. Vikwazo, PEPs, habari mbaya, maonyo.
Vikwazo vya kimataifa (OFAC, EU, UN, HMT, na kila orodha ya kitaifa ya G20), PEPs katika viwango vinne pamoja na jamaa zao na washirika wa karibu, habari hasi, utekelezaji wa udhibiti, usawa na uaminifu, kufilisika, watu na vyombo vya maslahi maalum, na orodha zako maalum. Simu moja inagonga zote, zinasasishwa mfululizo.
AML list catalogue
Refreshed continuously
Live
1,300+
Global lists
6
Categories
200+
Jurisdictions
24/7
Refresh
Sanctions412
PEP L1–L4318
Adverse media246
Warnings184
Regulatory92
Insolvency48
OFACEUUNHMTINTERPOLRCA
02 · Vyombo
Moduli moja. Watu na makampuni.
Aina ya chombo `person` inachunguza watu binafsi dhidi ya PEPs, vikwazo, na orodha za habari hasi. Aina ya chombo `company` inachunguza vyombo vya kisheria dhidi ya vikwazo, utekelezaji wa udhibiti, na rejista za Mmiliki Halisi wa Manufaa (UBO). Simu sawa, JSON sawa, $0.20 sawa, iunganishe ndani ya mtiririko wa Uthibitishaji wa Biashara au iendeshe kabla ya makubaliano ya B2B kufungwa.
Entity screening
One endpoint · POST /v3/aml/
$0.20 / check
entity_type: person
Full name
Carmen Espanola
Date of birth
14 / 03 / 1981
Nationality
Spain
Sanctions · PEP L1–L4 · Adverse media
entity_type: company
Registered name
Acme Trading SL
Registration nº
B-87214503
Incorporated
Spain · 2014
Sanctions · Enforcement · UBO
03 · PEP
Uainishaji wa PEP katika ngazi nne.
Kila PEP hit imeandikwa Level 1 (wakuu wa nchi, majaji wa mahakama kuu, mabenki makuu), Level 2 (wabunge, mabalozi, viongozi wa kijeshi), Level 3 (watumishi wa umma wa ngazi ya kati), au Level 4 (jamaa na washirika wa karibu). Vitendo vya kila ngazi kwenye console, idhinisha kiotomatiki, elekeza kwa ukaguzi, au kataa.
Alama ya Kulingana (0–100, kizingiti chaguomsingi 93) huamua kama hit ni mtu yule yule, jina lina uzito wa 60%, tarehe ya kuzaliwa 25%, nchi 15%. Alama ya Hatari (0–100) huamua jinsi ilivyo hatari, kategoria ina uzito wa 50%, nchi 30%, uhalifu 20%. Wakaguzi huona alama zote mbili pamoja na URL ya chanzo, hisia, na ubatilishaji wa nambari ya hati kwenye console.
AML scoring
Match score · Risk score
Approved
Match Score98/100
0≥ 93100
Risk Score65/100
0review 80100
DeclineReviewApprove
Match weights
Name60%
Date of birth25%
Country15%
Risk weights
Category50%
Country30%
Criminal20%
05 · Ufuatiliaji endelevu
Uchunguzi upya wa kila siku. $0.07 kwa mtumiaji kwa mwaka.
Washa ufuatiliaji unaoendelea na tunachunguza upya kila mtumiaji aliyesajiliwa kila siku dhidi ya orodha kamili ya zaidi ya 1,300. Vikwazo vipya au hit ya PEP huwasha webhook, hubadilisha hali ya session, huonyesha hit kwenye console na audit trail kamili. Payload sawa na uchunguzi wa awali, hakuna kazi ya ziada ya integration.
Ongoing monitoring
Daily rescreen · $0.07 / user / year
Live
8,420
Enrolled
12
In review
1
New hit
aml.new_hit · usr_5c81d22 · OFAC SDN8s ago
Cusr_a8c4f02Sanctions · PEPDailyClear
Musr_4d2b6e1Adverse mediaDailyIn Review
Lusr_5c81d22OFAC SDN · newTodayNew hit
06 · Wadhibiti
FATF, AMLD6, OFAC, MiCA. Inatii kwa muundo.
Imeunganishwa na FATF (Financial Action Task Force) customer-due-diligence, EU's 6th AML Directive, US OFAC sanctions enforcement, na MiCA (Markets in Crypto-Assets). Tesoro ya Uhispania, Banco de España, na SEPBLAC wamethibitisha rasmi Didit kuwa salama zaidi kuliko ana kwa ana, uthibitisho pekee wa aina hiyo sokoni.
Regulatory coverage
FATF · AMLD6 · OFAC · MiCA
Attested
FATFRecommendations 10–16 · Customer Due DiligenceGlobal
AMLD6EU 6th Anti-Money Laundering DirectiveEU
OFACUS Treasury sanctions enforcementUS
MiCAEU Markets in Crypto-Assets RegulationEU
Tesoro · Banco de España · SEPBLAC
Formally attested safer than in-person verification.
Unganisha
Endpoints mbili. JSON sawa. Bei sawa.
Unganisha AML ndani ya mtiririko wa kazi wa KYC au KYB unapotaka UI yetu iliyopangishwa iendeshe mtiririko. Piga API inayojitegemea wakati tayari una sehemu za chombo. Ripoti sawa kwa njia zote mbili.
Bandika block iliyo hapa chini kwenye Claude Code, Cursor, Codex, Devin, Aider, au Replit Agent. Jaza my_stack placeholder na framework yako, lugha, na matumizi. Agent huandaa Didit, huunda workflow, huunganisha webhook, na kutuma.
didit-integration-prompt.md
# 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
Unahitaji maelezo zaidi? Tazama nyaraka kamili za moduli.docs.didit.me →
Inatii kwa muundo
Fungua nchi mpya kwa kubofya mara moja. Tunafanya kazi ngumu.
Tunafungua kampuni tanzu za ndani, tunapata leseni, tunafanya majaribio ya kupenya, tunapata vyeti, na tunalingana na kila kanuni mpya. Ili kusafirisha uthibitishaji katika nchi mpya, geuza swichi. Nchi 220+ ziko hewani, zinakaguliwa na kupimwa kila robo mwaka, mtoa huduma pekee wa utambulisho ambaye serikali ya nchi mwanachama wa EU imemwita rasmi kuwa salama zaidi kuliko uthibitishaji wa ana kwa ana.
Vyanzo vya vikwazo vya kimataifa, PEP, taarifa hasi, na orodha za uangalizi.
Daily
Kipindi cha kuchunguza upya kwa kila mtumiaji aliyejiandikisha kwa ufuatiliaji endelevu.
$0.00
Kwa kila ukaguzi wa AML unaojitegemea. Mtu au kampuni.
$0.00
Kwa kila mtumiaji aliyejiandikisha kwa mwaka kwa ufuatiliaji endelevu.
Ngazi tatu, orodha moja ya bei
Anza bure. Lipa kulingana na matumizi. Panua hadi Enterprise.
Uthibitishaji 500 bila malipo kila mwezi, milele. Lipa kadri unavyotumia kwa uzalishaji. Mikataba maalum, uhifadhi wa data, na SLA (Service Level Agreements) kwenye Enterprise.
Bure
Bure
$0 / mwezi. Hakuna kadi ya mkopo inayohitajika.
Kifurushi cha bure cha KYC (Uthibitishaji wa Kitambulisho + Passive Liveness + Face Match + Uchambuzi wa Kifaa & IP), 500 / mwezi, kila mwezi
Watumiaji Waliozuiwa
Utambuzi wa Marudio
Ishara 200+ za udanganyifu kwenye kila session
KYC inayoweza kutumika tena kwenye mtandao wa Didit
Jukwaa la Usimamizi wa Kesi
Workflow Builder
Nyaraka za umma, sandbox, SDKs, server ya MCP (Model Context Protocol)
Anza bure → lipa tu wakati ukaguzi unafanyika → fungua Enterprise kwa mkataba maalum, SLA, au uhifadhi wa data.
FAQ
Maswali ya kawaida
What is Didit?
Didit is infrastructure for identity and fraud, the platform we wished existed when we were building products ourselves: open, flexible, and developer-friendly, so it works as a real part of your stack instead of a black box you integrate around.
One API covers verifying people (KYC, know your customer), verifying businesses (KYB, know your business), screening crypto wallets (KYT, know your transaction), and monitoring transactions in real time, on a stack built to be:
Fast, sub-2-second p99 on every session
Reliable, in production with 1,500+ companies across 220+ countries
Secure, SOC 2 Type 1, ISO 27001, GDPR-native, and formally attested by Spain's financial regulator as safer than verifying someone in person
The footprint underneath: 14,000+ document types in 48+ languages, 1,000+ data sources, and 200+ fraud signals on every session. The Didit infrastructure dynamically learns from every session and gets better every day.
Which lists and databases does Didit screen against?
1,300+ global sources in a single call. Sanctions from the US Office of Foreign Assets Control (OFAC), the European Union, the United Nations, the UK HM Treasury, and every G20 national list. Politically Exposed Persons across four levels, PEP Level 1 (heads of state, supreme court judges, central bankers), PEP Level 2 (parliamentarians, ambassadors, military leaders), PEP Level 3 (mid-level civil servants, local government), PEP Level 4 (Relatives and Close Associates / RCAs). Adverse media, Warnings and Regulatory Enforcement, Fitness and Probity, Insolvency, SIP (Special Interest Persons), SIE (Special Interest Entities), and your own custom lists. The full catalogue refreshes continuously, see docs.didit.me/core-technology/aml-screening/watchlist-database-aml-screening.
What is the response shape?
A single aml JSON object. Top-level status is one of Approved, Rejected, In Review, or Not Started. The object includes total_hits, an overall score (0–100, the highest non-False-Positive risk score), a screened_data block echoing the inputs used, a warnings array with structured risk codes, and a hits array. Each hit carries id, url, caption, datasets (which categories matched), match_score (identity confidence 0–100), risk_view.categories.score (entity risk 0–100), and typed sub-arrays, sanction_matches, pep_matches, warning_matches, adverse_media_matches, with list names, source URLs, legal basis, sanctioning authority, publication dates, and sentiment scores. Full reference at docs.didit.me/core-technology/aml-screening/report-aml-screening.
How fast is the verification for my end user?
The full flow normally takes under 30 seconds end-to-end, pick up the ID, snap the document, snap the selfie, done. That is the fastest in the market. Legacy KYC providers usually take more than 90 seconds for the same flow.
On the back end, Didit returns the result in under two seconds at p99, measured from the moment the user finishes the selfie to the moment your webhook fires. Mobile capture is tuned for slow phones and slow networks: progressive image compression, lazy software development kit load, and a one-tap hand-off from desktop to phone via QR code if the user starts on web.
How does Didit defeat false positives?
Two scores per hit. The match_score (0–100, default threshold 93) decides if the hit is actually the same person, weighted name similarity 60%, date of birth 25%, country 15%, with a Golden Key document-number override that can pin the score to 100. The risk_score (0–100, default approve 80 / review 100) decides how risky the entity is if it IS a match, weighted category 50%, country 30%, criminal records 20%. Hits below the match threshold are classified False Positive and dropped from the final status calculation. The final session status uses the highest risk score among the remaining non-False-Positive hits.
What happens if a user fails, abandons, or expires?
Every session lands on one of seven clear statuses, so your code always knows what to do:
Approved, every check passed. Move the user forward.
Declined, one or more checks failed. You can allow the user to resubmit the specific failed step (for example, re-take the selfie) without re-running the whole flow.
In Review, flagged for compliance review. Open the case in the console, see every signal, decide approve or decline.
In Progress, user is mid-flow.
Not Started, link sent, user has not opened it yet. Send a reminder if it sits too long.
Abandoned, user opened the link but did not finish in time. Re-engage or expire.
Expired, the session link aged out. Create a new session.
A signed webhook fires on every status change, so your database always stays in sync. Abandoned and declined sessions are free.
Where does my customer data live and how is it protected?
Production data is processed and stored in the European Union by default, on Amazon Web Services. Enterprise contracts can request alternative regions for jurisdictions whose regulators require it.
Encryption everywhere. AES-256 at rest across every database, object store, and backup. Transport Layer Security 1.3 in transit on every API call, webhook, and Business Console session. Biometric data is encrypted under a separate Customer Master Key.
Retention is yours to control. Default retention is indefinite (unlimited) unless you configure shorter, between 30 days and 10 years per application, and you can delete any individual session at any time from the dashboard or the API.
Certifications: SOC 2 Type 1 (Type 2 audit in progress), ISO/IEC 27001:2022, iBeta Level 1 PAD, and a public attestation from Spain''s Tesoro / SEPBLAC / CNMV that Didit''s remote identity verification is safer than verifying someone in person. Full report at /security-compliance.
Is Didit compliant for my industry?
Didit ships compliant by default for the regulators that matter to identity infrastructure:
GDPR + UK GDPR, controller / processor split, full Data Processing Agreement published, lead supervisory authority named (Spain''s AEPD).
AMLD6 + EU AML Single Rulebook, 1,300+ sanctions, politically exposed person, and adverse-media lists screened in real time.
eIDAS 2.0, EU Digital Identity Wallet aligned; reusable-identity ready.
MiCA (Markets in Crypto-Assets), ready for crypto on-ramps, exchanges, and custodians.
DORA, Digital Operational Resilience Act, EU financial-services operational resilience.
BIPA, CUBI, Washington HB 1493, CCPA / CPRA, US biometric privacy (Illinois, Texas, Washington) and California consumer privacy.
UK Online Safety Act, age-gating and child-safety obligations.
FATF Travel Rule, originator and beneficiary data on crypto transfers, IVMS-101 interoperable.