All modules
    Spot suspicious activity in real time

    Transaction Monitoring

    AI co-pilot, rule-based and behavioural monitoring built for AML and fraud teams.

    ComplianceSuite · Transaction Monitoring
    stream · live
    Monitoring › Live alerts
    Live · 1,284 tx/min
    3 new alerts
    TX-77821
    Volt Wallet · MT
    €48,200Alert
    TX-77820
    Stripe · GB
    €12,940Alert
    TX-77819
    Binance · MT
    €2,100Alert
    TX-77818
    Revolut · LT
    €680Clear
    Alerts / day
    142
    False positives
    ↓ 71%
    MTTR
    6.4 min
    <200ms
    Per-transaction screening
    p95 — streaming engine
    ↓ 71%
    False positives
    vs. legacy rules-only systems
    AI
    Rule suggestions
    Drafted from live regulator feeds
    Look-back
    Retrospective sweeps
    Replay new rules on 12+ months of history

    What it does

    Spot suspicious activity in real time

    Define typologies once and apply them across every channel. Combine deterministic rules with anomaly detection and an AI co-pilot that drafts new rules from the latest FATF, EU AMLR, EBA and national-regulator updates — then route alerts to investigators in one click.

    • AI co-pilot drafts new rules from FATF, EU AMLR, EBA and regulator publications
    • Regulator-driven rule suggestions with 90-day back-tests before activation
    • Pre-built typologies for AML, terrorism financing, and fraud
    • Custom rule builder — no code required
    • Behavioural baselining and anomaly scoring
    • Real-time alerting with case integration
    • Post-transaction monitoring — retrospective rule replay and scheduled look-back sweeps on historical transactions
    • Tunable thresholds backed by simulation mode

    Use cases

    How teams put it to work.

    Three concrete scenarios from regulated institutions running ComplianceSuite in production today.

    1

    Real-time payment screening

    A payment institution must screen every SEPA Instant payment in under 200ms with structuring, smurfing and mule-account typologies, while keeping STP rates above 99%.

    The streaming engine evaluates every transaction in <100ms median, applies your typology library, and routes only genuinely suspicious activity to investigators — STP holds at 99.4%.

    2

    Crypto deposit and withdrawal monitoring

    A licenced exchange must apply the FATF Travel Rule, monitor for high-velocity deposits from sanctioned jurisdictions, and detect mixers and tumblers across multiple chains.

    On-chain analytics signals feed the same rule library as fiat transactions, so the same investigators can triage cross-chain mule clusters in one inbox — with full evidence packs ready for the FIU.

    3

    AI-drafted rules from a new regulator publication

    The EBA publishes revised Travel Rule guidelines on a Friday afternoon. The MLRO needs to translate the new expectations into live monitoring rules before the next supervisory dialogue.

    The AI co-pilot ingests the EBA text overnight, drafts 4 candidate rules with rationale and source citations, runs each against 90 days of production transactions, and presents the projected alert volume and false-positive rate. The MLRO reviews, edits, four-eyes approves and activates — same week.

    4

    Post-transaction look-back and retrospective rule replay

    After a regulator publishes a new typology, the MLRO must replay the new rule across 12 months of historical transactions, run scheduled overnight sweeps for slow-burn patterns (layering, dormant-account reactivation, periodic structuring), and produce a defensible look-back report — without disrupting the real-time stream.

    Post-transaction monitoring replays any rule against historical data in batch, schedules recurring typology re-runs (daily, weekly, monthly), surfaces newly-suspicious historical activity as cases with full evidence packs, and produces a regulator-ready look-back report — all isolated from the live streaming engine.

    5

    Tuning a typology safely

    An MLRO wants to tighten a structuring threshold but is worried about flooding investigators with new alerts.

    Simulation mode replays the proposed rule against 90 days of real production transactions, surfaces the projected alert count, false-positive rate and customer-impact distribution before activation — all four-eyes approved.

    How teams use it

    Built into a single end-to-end workflow.

    STEP 1

    Configure

    Map your policies, risk factors, and regulator requirements into the engine — no code.

    STEP 2

    Operate

    Your reviewers work from one inbox with full context, history, and supporting evidence.

    STEP 3

    Prove

    Generate audit-ready reports in minutes, on demand, with full versioned trail.

    FAQ

    Buyer questions, answered.

    The five things compliance, product and security teams ask before activating Transaction Monitoring. Need more detail? Talk to a specialist.

    Reviewed by our compliance product team — Q1 2026

    Up next

    Customer Risk Scoring

    Continue