Your Rules. Real-Time.
Zero False Positives.
EyesClear's Scenarios and Flow Guard give compliance teams a no-code business rules engine that monitors every transaction in real time — detecting suspicious patterns, enforcing thresholds, and triggering alerts the moment something breaks policy.
See Detection Rules in Action →Two Engines. Complete Coverage.
Scenarios catch individual transaction anomalies the moment they arrive. Flow Guard tracks cumulative behavior over time. Together, they cover every detection pattern your compliance program needs.
Rule-Based Transaction Alerts
Scenarios evaluate every incoming transaction against configurable rules in real time. If a transaction matches — by amount, geography, account type, or any combination — an alert fires instantly via email, Kafka, or automatic case creation.
- Visual query builder with AND/OR nested logic
- Field-level conditions across all message types
- Personal or enterprise-wide scope
- Monitoring timeframes and working-day schedules
- Validate rules before deployment
Cumulative Behavioral Monitoring
Flow Guard tracks transaction volumes and amounts over configurable time windows — daily, weekly, monthly, quarterly, or annually. When cumulative activity crosses an upper or lower threshold, an alert fires and the counter resets.
- Volume-based or amount-based thresholds
- Configurable refresh periods (daily to annual)
- Upper and lower threshold boundaries
- Historical threshold proposal from real data
- D3-based history visualization
From Transaction to Alert in Milliseconds
Every transaction flows through both detection engines simultaneously — matching scenario rules and updating Flow Guard counters in a single pass.
Three Alert Channels
Route alerts to exactly the right place — your inbox, your case management queue, or a downstream Kafka topic for external system integration.
HTML-templated email notifications with transaction details, priority routing, and delivery tracking.
Case Creation
Automatically generate a case in EyesClear Case Management — with template selection, risk scoring, and SLA tracking from the start.
Kafka Topic
Forward alerts as structured messages to external compliance platforms, SIEM systems, or downstream analytics via Apache Kafka.
Built for Compliance Teams
Every feature is designed to reduce false positives, prevent alert fatigue, and give analysts the context they need to act fast.
No-Code Query Builder
Build detection rules visually with drag-and-drop conditions, nested AND/OR logic, and field auto-completion — no SQL knowledge required.
- jQuery-based visual rule builder
- Dynamic field lists per message type
- Operators: equals, contains, between, greater, less
Personal & Enterprise Rules
Analysts create personal rules for their own investigations. Managers deploy enterprise-wide rules shared across departments with maker-checker approval.
- Personal rules visible only to creator
- Enterprise rules with department assignment
- Proposed status for review workflows
Flexible Scheduling
Run detection rules 24/7, during business hours only, or on working days versus non-working days — matching your compliance program's operating model.
- Start/end time windows (HH:MM)
- All days, working days, or non-working days
- Holiday-aware scheduling
Threshold Intelligence
Flow Guard analyzes your historical transaction data and proposes optimal thresholds — reducing guesswork and fine-tuning detection from day one.
- Propose Threshold from real data
- Upper and lower boundary configuration
- Currency-specific amount thresholds
Clone & Iterate
Right-click any scenario or Flow Guard profile to duplicate it instantly. Refine thresholds, adjust conditions, and test variations without starting from scratch.
- One-click clone for scenarios & Flow Guards
- Validate before saving
- Version through proposed status
DILAB Integration
Build queries in the Data Investigation Lab, then convert them directly into scenarios or Flow Guard profiles — bridging investigation and detection seamlessly.
- Save as Scenario from DILAB
- Save as Bucket Profile from DILAB
- Pre-filled conditions carry over
Scenarios vs. Flow Guard at a Glance
| Capability | Scenarios | Flow Guard |
|---|---|---|
| Detection approach | Per-transaction rule matching | Cumulative behavioral thresholds |
| Alert speed | Real-time (per transaction) | Real-time (on threshold breach) |
| Threshold type | Condition-based (field values) | Volume or amount over time window |
| Time windows | Monitoring timeframe (HH:MM) | Refresh period: daily to annually |
| Email channel | ✓ | ✓ |
| Auto case creation | ✓ | — |
| Kafka forwarding | ✓ | — |
| Visual query builder | ✓ | ✓ |
| Historical threshold proposal | — | ✓ |
| D3 history visualization | — | ✓ |
Ready to Build Your Detection Rules?
See how EyesClear's Scenarios and Flow Guard catch what static rules miss — with zero coding required.