Transaction monitoring
Catch transaction risk in flight
Onboarding data and ongoing monitoring in one platform, with deterministic rules your team can explain and real-time blocking where you need it.
One platform, from onboarding to monitoring
Few platforms combine a full KYC/KYB system with a genuine transaction-monitoring and AML engine. spektr does both, so monitoring starts with everything onboarding already knows.
Onboarding data and monitoring, finally in one place
The customer you onboarded and the transactions you monitor live on one record. Rules draw on what onboarding already knows, from risk level to tenure to entity type, and every finding flows back to sharpen the next check.
Approve transaction
Approve transaction
Deterministic and explainable by design
Every alert shows the rule it broke, the values that triggered it, and the transactions behind it. Same inputs, same result, every time. One engine does both real-time blocking and periodic case reviews.
Transaction RulesProcess
Hit AlertRouting
High Risk Transaction
Immediate Review
Medium Risk Transaction
Review SLA 48h
Approved
End
Build the scenarios your policy calls for, without engineering
Rolling-window aggregations, multi-leg patterns like a 24-hour U-turn, AND/OR logic, IP and geo conditions, all built visually by the analysts who own them. Test in shadow mode, then promote through an approval gate. A new scenario is a configuration, not a ticket.
Hard Stop TransactionStop a transaction and continue it through cases
Transaction rule stepCreate conditional transaction rules or choose existing templates
Approve TransactionApprove the Transaction without creating any cases
Transaction rule step
Add new ruleStart from scratch
Select templateChoose among many different transaction monitoring templates
Transaction monitoring runs on the four platform capabilities
1
Registries, providers and your own systems feeding one record.
2
Turn data into onboarding, monitoring and remediation workflows.
3
Put agents on the routine work the connected data makes possible.
4
Every source, call and result on the record, held to your own policies.
Want to try it for yourself?
Try our interactive demo
One rule engine, three process types:
Real-time
Build customizable workflows that eliminate manual bottlenecks and keep your pass rates at an all-time high.
Batch
Runs the same rules retrospectively over sets of transactions.
Periodic
Runs on a schedule over counterparties, creating cases for review.
Every match either blocks the transaction or opens a case with the triggering transactions attached. ML detectors from the Resistant AI integration run in parallel and flow into the same case workflow.
Alerts are only half the job.
Once a customer is onboarded, spektr keeps watching and reacts the moment their risk profile changes. Same platform, same policies, no handover.
Cases / CASE-1247
Suspicious refund activity — Stark
Manually approvedNo information found+1
Created from process: Corporate TM — TGAB
Case OverviewClient detailsCase evidenceTimelineTransactionsCommunica…
CASE TRIGGERS · 3 RULESSudden spike in reverse transactions and 2 more
CaseAI SummaryLast generated: 29 April 2026, 14:02
This case was opened on 25 July 2026 following 4 alerts flagged on Stark during the routine onboarding workflow. The case remains
under compliance review.
Key findings:
• 1 escalated alert requires senior review (Sanctions screening hit — Dow Jones).
“We need an infrastructure that can automate the routine work without losing the configurability each jurisdiction demands, whilst meeting increasingly complex regulatory demands.”
Catch transaction risk in flight
Onboarding data and ongoing monitoring in one platform, with deterministic rules your team can explain and real-time blocking where you need it.



