← 返回
开发者工具 Key 中文

Didit Aml Screening

Integrate Didit AML Screening standalone API to screen individuals or companies against global watchlists. Use when the user wants to perform AML checks, scr...
集成 Didit AML 筛选独立 API,针对全球监控名单筛查个人或企业。适用于用户需要进行 AML 检查、筛查等情况。
rosasalberto
开发者工具 clawhub v1.1.0 1 版本 100000 Key: 需要
★ 0
Stars
📥 869
下载
💾 11
安装
1
版本
#latest

概述

Didit AML Screening API

Overview

Screens individuals or companies against 1,300+ global watchlists and high-risk databases in real-time. Uses a two-score system: Match Score (identity confidence) and Risk Score (threat level).

Key constraints:

  • full_name is the only required field
  • Supports entity_type: "person" (default) or "company"
  • Document number acts as a "Golden Key" for definitive matching
  • All weight parameters must sum to 100

Coverage: OFAC SDN, UN, EU, HM Treasury, Interpol, FBI, 170+ national sanction lists, PEP Levels 1-4, 50,000+ adverse media sources, financial crime databases.

Scoring system:

  1. Match Score (0-100): Is this the same person? → classifies hits as False Positive or Unreviewed
  2. Risk Score (0-100): How risky is this entity? → determines final AML status

API Reference: https://docs.didit.me/standalone-apis/aml-screening

Feature Guide: https://docs.didit.me/core-technology/aml-screening/overview

Risk Scoring: https://docs.didit.me/core-technology/aml-screening/aml-risk-score


Authentication

All requests require x-api-key header. Get your key from Didit Business Console → API & Webhooks, or via programmatic registration (see below).

Getting Started (No Account Yet?)

If you don't have a Didit API key, create one in 2 API calls:

  1. Register: POST https://apx.didit.me/auth/v2/programmatic/register/ with {"email": "you@gmail.com", "password": "MyStr0ng!Pass"}
  2. Check email for a 6-character OTP code
  3. Verify: POST https://apx.didit.me/auth/v2/programmatic/verify-email/ with {"email": "you@gmail.com", "code": "A3K9F2"} → response includes api_key

To add credits: GET /v3/billing/balance/ to check, POST /v3/billing/top-up/ with {"amount_in_dollars": 50} for a Stripe checkout link.

See the didit-verification-management skill for full platform management (workflows, sessions, users, billing).


Endpoint

POST https://verification.didit.me/v3/aml/

Headers

HeaderValueRequired
---------
x-api-keyYour API keyYes
Content-Typeapplication/jsonYes

Body (JSON)

ParameterTypeRequiredDefaultDescription
---------------
full_namestringYesFull name of person or entity
date_of_birthstringNoDOB in YYYY-MM-DD format
nationalitystringNoISO country code (alpha-2 or alpha-3)
document_numberstringNoID document number ("Golden Key")
entity_typestringNo"person""person" or "company"
aml_name_weightintegerNo60Name weight in match score (0-100)
aml_dob_weightintegerNo25DOB weight in match score (0-100)
aml_country_weightintegerNo15Country weight in match score (0-100)
aml_match_score_thresholdintegerNo93Below = False Positive, at/above = Unreviewed
save_api_requestbooleanNotrueSave in Business Console
vendor_datastringNoYour identifier for session tracking

Example

import requests

response = requests.post(
    "https://verification.didit.me/v3/aml/",
    headers={"x-api-key": "YOUR_API_KEY", "Content-Type": "application/json"},
    json={
        "full_name": "John Smith",
        "date_of_birth": "1985-03-15",
        "nationality": "US",
        "document_number": "AB1234567",
        "entity_type": "person",
    },
)
print(response.json())
const response = await fetch("https://verification.didit.me/v3/aml/", {
  method: "POST",
  headers: { "x-api-key": "YOUR_API_KEY", "Content-Type": "application/json" },
  body: JSON.stringify({
    full_name: "John Smith",
    date_of_birth: "1985-03-15",
    nationality: "US",
  }),
});

Response (200 OK)

{
  "request_id": "a1b2c3d4-...",
  "aml": {
    "status": "Approved",
    "total_hits": 2,
    "score": 45.5,
    "hits": [
      {
        "id": "hit-uuid",
        "caption": "John Smith",
        "match_score": 85,
        "risk_score": 45.5,
        "review_status": "False Positive",
        "datasets": ["PEP"],
        "properties": {"name": ["John Smith"], "country": ["US"]},
        "score_breakdown": {
          "name_score": 95, "name_weight": 60,
          "dob_score": 100, "dob_weight": 25,
          "country_score": 100, "country_weight": 15
        },
        "risk_view": {
          "categories": {"score": 55, "risk_level": "High"},
          "countries": {"score": 23, "risk_level": "Low"},
          "crimes": {"score": 0, "risk_level": "Low"}
        }
      }
    ],
    "screened_data": {
      "full_name": "John Smith",
      "date_of_birth": "1985-03-15",
      "nationality": "US",
      "document_number": "AB1234567"
    },
    "warnings": []
  }
}

Match Score System

Formula: (Name × W1) + (DOB × W2) + (Country × W3)

ComponentDefault WeightAlgorithm
---------
Name60%RapidFuzz WRatio — handles typos, word order, middle name variations
DOB25%Exact=100%, Year-only=100%, Same year diff date=50%, Mismatch=-100%
Country15%Exact=100%, Mismatch=-50%, Missing=0%. Auto-converts ISO codes

Document Number "Golden Key":

ScenarioEffect
------
Same type, same valueOverride score to 100
Different type or one missingKeep base score (neutral)
Same type, different value-50 point penalty

Classification: Score < threshold (default 93) → False Positive. Score >= threshold → Unreviewed.

> When data is missing, remaining weights are re-normalized. E.g., name-only → name weight becomes 100%.


Risk Score System

Formula: (Country × 0.30) + (Category × 0.50) + (Criminal × 0.20)

Final AML Status (from highest risk score among non-FP hits):

Highest Risk ScoreStatus
------
Below 80 (default)Approved
Between 80-100In Review
Above 100Declined
All False PositivesApproved

Category scores (50% weight):

CategoryScore
------
Sanctions / PEP Level 1100
Warnings & Regulatory95
PEP Level 2 / Insolvency80
Adverse Media60
PEP Level 4 / Businessperson55

Status Values & Handling

StatusMeaningAction
---------
"Approved"No significant matches or all False PositivesSafe to proceed
"In Review"Matches found with moderate riskManual compliance review needed
"Rejected"High-risk matches confirmedBlock or escalate per your policy
"Not Started"Screening not yet performedCheck for missing data

Error Responses

CodeMeaningAction
---------
400Invalid request bodyCheck full_name and parameter formats
401Invalid API keyVerify x-api-key header
403Insufficient creditsCheck credits in Business Console

Warning Tags

TagDescription
------
POSSIBLE_MATCH_FOUNDPotential watchlist matches requiring review
COULD_NOT_PERFORM_AML_SCREENINGMissing KYC data. Provide full name, DOB, nationality, document number

Response Field Reference

Hit Object

FieldTypeDescription
---------
match_scoreinteger0-100 identity confidence score
risk_scorefloat0-100 threat level score
review_statusstring"False Positive", "Unreviewed", "Confirmed Match", "Inconclusive"
datasetsarraye.g. ["Sanctions"], ["PEP"], ["Adverse Media"]
pep_matchesarrayPEP match details
sanction_matchesarraySanction match details
adverse_media_matchesarray{headline, summary, source_url, sentiment_score, adverse_keywords}
linked_entitiesarrayRelated persons/entities
first_seen / last_seenstringISO 8601 timestamps

Adverse media sentiment: -1 = slightly negative, -2 = moderately, -3 = highly negative.


Continuous Monitoring

Available on Pro plan. Automatically included for all AML-screened sessions.

  • Daily automated re-screening against updated watchlists
  • New hits → session status updated to "In Review" or "Declined" based on thresholds
  • Real-time webhook notifications on status changes
  • Zero additional integration — uses same thresholds from workflow config

Common Workflows

Basic AML Check

1. POST /v3/aml/ → {"full_name": "John Smith", "nationality": "US"}
2. If "Approved" → no significant watchlist matches
   If "In Review" → review hits[].datasets, hits[].risk_view for details
   If "Rejected" → block user, check hits for sanctions/PEP details

Comprehensive KYC + AML

1. POST /v3/id-verification/ → extract name, DOB, nationality, document number
2. POST /v3/aml/ → screen extracted data with all fields populated
3. More data = higher match accuracy = fewer false positives

Utility Scripts

screen_aml.py: Screen against AML watchlists from the command line.

# Requires: pip install requests
export DIDIT_API_KEY="your_api_key"
python scripts/screen_aml.py --name "John Smith"
python scripts/screen_aml.py --name "John Smith" --dob 1985-03-15 --nationality US
python scripts/screen_aml.py --name "Acme Corp" --entity-type company

版本历史

共 1 个版本

  • v1.1.0 当前
    2026-03-30 06:33 安全 安全

安全检测

腾讯云安全 (Keen)

安全,无风险
查看报告

腾讯云安全 (Sanbu)

安全,无风险
查看报告

🔗 相关推荐

developer-tools

Gog

steipete
Google Workspace 命令行工具,支持 Gmail、日历、云端硬盘、通讯录、表格和文档。
★ 921 📥 185,924
data-analysis

Didit Face Match

rosasalberto
集成Didit Face Match独立API以比对两张面部图像。适用于用户需要比对面部、验证身份或实现生物识别的场景。
★ 0 📥 1,156
developer-tools

CodeConductor.ai

larsonreever
AI驱动平台,提供快速全栈开发、智能体、工作流自动化及低代码AI集成的可扩展产品创建。
★ 68 📥 180,461