Home / Companies / Didit / Blog / Post Details
Content Deep Dive

The Two-Score AML Model: Match Score vs Risk Score

Blog post from Didit

Aggregate trend data notice

Excluded from normalized aggregate trends after staff review: 3056 posts were attributed to March 2026; 671 shared March 14, 2026. The preceding six-month median was 13.5 posts.

Review evidence: 3,056 posts in March 2026; 671 shared March 14, 2026; preceding six-month median 13.5. Reviewed August 9, 2026.

This company's pages remain public, but its content is excluded from normalized aggregate trends. Unfiltered raw trends and advanced filtering are available to Accelerate and Lead accounts.

Post Details
Company
Date Published
Author
Didit
Word Count
1,335
Company Posts That Month
190
Language
English
Hacker News Points
-
Post removed?
No
Summary

Didit's AML Screening engine employs a two-score model to enhance the accuracy of anti-money laundering checks by independently assessing identity confidence and entity risk, thus minimizing false positives and ensuring that analysts focus on genuinely risky entities. The Match Score evaluates whether a watchlist hit is genuinely the customer by analyzing factors like name similarity, date of birth, and country, while the Risk Score assesses the potential threat level of a confirmed match based on elements such as category, country risk, and criminal record. These scores are calculated separately, allowing the system to automatically dismiss weak identity matches as false positives, optimizing the workload for analysts. A unique feature is the "Golden Key," where a document-number match guarantees a 100% Match Score, indicating definitive identity proof. Configurable weights and thresholds allow users to tailor the system to their risk preferences, and both scores are integrated into Didit's verification workflows, with a per-check cost of $0.20.

Trends Found in this Post

No tracked trend matches for this post yet.

Use This Data

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.