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

Cutting AML False Positives With Configurable Thresholds

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,266
Company Posts That Month
220
Language
English
Hacker News Points
-
Post removed?
No
Summary

Didit’s AML screening approach focuses on reducing costly false positives, particularly namesake matches across more than 1,300 watchlists, by allowing organizations to tune identity and risk decisions to their populations. Users can adjust match-score weights for name, date of birth, and country; set a match threshold that automatically classifies lower-confidence records as false positives; and configure risk thresholds that determine whether confirmed matches are approved, reviewed, or declined. A matching document number, called the Golden Key, overrides the match score to 100% and provides a stronger identity signal that can eliminate name ambiguity. Suppressed records retain scores and statuses for auditability, enabling teams to explain automated decisions to regulators. The service is positioned for uses including fintech, crypto, lending, marketplaces, and iGaming, with configuration available through the console and AML screening priced at $0.20 per check.

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.