Feature Module
Continuous Monitoring Cadence
Configure monitoring frequency by risk tier. High-risk merchants get scanned more often, automatically.
How it works
Define cadence policies
Set scan frequency rules per merchant risk tier: daily for critical-risk, weekly for high-risk, monthly for standard.
Scans run automatically
The scheduler queues scans based on each merchant's next-scan date. No manual triggering required for routine monitoring.
Escalate on missed coverage
If a scheduled scan fails or a merchant goes past their scan window, the platform flags the coverage gap for analyst attention.
Overview
Portfolio health at a glance
Merchants
1,247
23 flagged
Open Alerts
8
2 critical
Overdue
1
Violations
23
of 4,891 scans
Portfolio Risk Score
Alert Severity
Alerts Requiring Attention
INV DUE
4d 6hACK DUE
2d 1hINV DUE
12hRecent Scan Activity
Cadence controls by risk profile
Apply weekly, monthly, or risk-triggered cadence rules to merchant segments without manual scheduling. Each merchant inherits cadence from their risk tier, with per-merchant overrides available. The scheduler handles timing automatically.
Multi-layer coverage
Each monitoring cycle can include website crawling, integration checkpoints from SSM and eKYC services, and reputation signal checks. Coverage extends beyond the merchant's website to their broader digital footprint.
Escalation on coverage gaps
If a scheduled scan fails due to website downtime, crawler errors, or integration issues, the platform flags the coverage gap rather than silently skipping the merchant. Analysts see which merchants are past due and can trigger manual rescans.
Risk-triggered acceleration
Certain events trigger immediate rescans: a drift score spike, a reputation signal alert, or an external notification. The cadence adapts to actual risk conditions, not just calendar dates.
Frequently asked questions
- How often can scans run?
- Daily, weekly, monthly, or risk-triggered. The appropriate frequency depends on your portfolio risk profile and compliance requirements.
- Can cadence vary by segment?
- Yes. Risk tier and merchant profile define the monitoring frequency. High-risk gambling-adjacent merchants might be scanned daily, while standard retail merchants are checked monthly.
- What happens if a scan fails?
- Failed scans are retried automatically. If retries fail, the coverage gap is flagged for analyst attention so no merchant silently falls out of monitoring coverage.
- Can individual merchants be overridden?
- Yes. While merchants inherit cadence from their risk tier by default, any merchant can be given a custom scan frequency if their situation warrants closer or less frequent monitoring.