Real-Time Transaction Risk Scoring at $0.02 per Transaction
Blog post from Didit
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.
Didit’s Transaction Monitoring API provides real-time, inline risk scoring for fiat and cryptocurrency payments, enabling businesses to assess transactions in milliseconds before funds settle rather than identifying suspicious activity after the fact. Each transaction is evaluated against active rules that can add to a cumulative risk score, change its outcome, apply tags or notes, and flag involved parties; the API returns one of four statuses: APPROVED for transactions that can proceed, IN_REVIEW for analyst investigation, DECLINED for hard blocks such as sanctioned counterparties, and AWAITING_USER for cases requiring user remediation such as re-verification or proof of funds. Businesses can configure rules and thresholds, submit transactions through the unified API using stable transaction identifiers, and synchronize later decisions through webhooks, allowing policies to vary by product or risk tolerance. The service supports applications including fintech transfers, crypto wallet screening, lending disbursements, marketplace payouts, and iGaming deposits, and is priced at $0.02 per transaction with separate $0.20 AML screening for flagged parties.
| Trend | Post Mentions | Total Month Mentions | Posts | Companies | MoM |
|---|---|---|---|---|---|
| Real-time | 6 | 6,790 | 1,736 | 269 | -9% |
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.