Reference build: an AML screening service
A VASP needs to screen money in and out and keep an audit trail. This build wires three AML primitives into the deposit and withdrawal paths, with no separate compliance console to license or operate.
The challenge
Off-the-shelf compliance suites are priced per seat and per dashboard, and they sit outside your product. The goal here is to embed the same checks directly into the flows that already move money, and to keep every decision reproducible.
- Address risk-score / exposureC3
- Transaction screening / KYTC3
- Sanctions check + feedC2
- Fund-flow trace (hops)C4
Boundary screening on deposits and withdrawals
Call risk-score on the counterparty before crediting a deposit or releasing a payout. Persist the full response — score, confidence, exposure — next to the transaction so the decision is auditable.
Continuous monitoring with KYT
Route settled transfers through transaction screening so activity after onboarding keeps producing allow/review/block decisions, feeding a case queue rather than a static report.
Escalation with fund-flow tracing
When a score crosses your review threshold, trace the funds across hops to document exposure to mixers or sanctioned clusters before a human signs off.
What the build delivers
- Deposits and withdrawals screened inline, with thresholds you control
- Every decision stored with confidence and exposure for audit
- No per-seat dashboard license — pay per screen in credits
Frequently asked
Does this replace a compliance team?
No — it gives the team programmatic checks and an audit trail. Humans still own thresholds and escalations.
Which obligations does it map to?
VASP onboarding and ongoing-monitoring screening, with sanctions checks against a maintained feed.
Top up, get a key, ship.
Self-serve. Pay in crypto or card. Metered by credits — heavy primitives cost more, simple ones are cheap.
Get API key