Transaction monitoring
Transaction monitoring is the continuous evaluation of financial transactions against configured rules and behavioural expectations, in order to identify activity that may be fraudulent or otherwise suspicious and to raise it for investigation. It runs for the life of an account, not only at onboarding.
In more detail
Monitoring runs for the life of an account because an account that was legitimate when opened can later be taken over, sold, or recruited as a mule account. The transaction is the observable event, so the transaction is where monitoring happens.
A monitoring system typically applies four families of rule: thresholds on a single attribute, velocity rules counting events in a time window, relationship rules about counterparties, and behavioural rules comparing the transaction against the account's own history.
A common misconception is that monitoring and blocking are the same thing. Monitoring produces a judgement and an alert; whether a payment is held or declined is a separate decision taken by whichever system controls the payment.
Mechanically, a monitoring system receives each event, enriches it with account history, evaluates it against the rules, and routes any breach into an investigator queue.
Example
An account that has never sent more than 400 euro initiates a 4,000 euro transfer to a beneficiary added eleven minutes earlier, from a device seen for the first time. No single attribute is remarkable on its own; the combination breaches a composite rule and raises an alert.
Related capability
Transaction monitoring on the platform
Related terms
Discuss your transaction monitoring requirements
Tell us which transaction flows you need to monitor, which systems Akoben would integrate with, and how your fraud team works today.
Request a demo