Skip to content

Transaction monitoring software

Scenarios you can read, test on your own data and change yourself. Watch payments, customers and counterparties, for AML and fraud.

How it works

Trusted by 130+ financial institutions across 30 jurisdictions

Transaction monitoring software checks payments and customer activity against rules, called scenarios, that describe suspicious behaviour, and raises an alert for a compliance or fraud team to work when one fires.

Watch payments, customers and counterparties with scenarios your team can read, test on your own history and change, using Salv Monitoring. Salv screens and monitors around 96 million transactions a month.

  • nearly 100 milliontransactions checked in a recent month
  • 130+institutions across 30 jurisdictions
  • 250M+end-customers covered

What transaction monitoring software watches

  1. 01On paymentsMany small payments under a threshold, rapid movement of funds in and out, activity out of line with a customer's usual pattern, and payments to high-risk countries.
  2. 02On customersSeveral sharing one IP address, a change in risk level, and frequent changes to personal details.
  3. 03CounterpartiesAre monitored too, so a customer who looks clean but pays a suspicious counterparty still surfaces.

Run it for AML and fraud

For AML, the scenarios cover the typologies a supervisor expects you to watch for; see AML software. For fraud, the same tool carries scam and mule patterns; see fraud detection software and scam and mule detection. Salv Monitoring deploys as cloud, private cloud or on-premise.

See it on your own data

Start from the library, or add your own scenarios

Start from the library and adjust each scenario's type, threshold and segments, or add your own alongside them. Set an alert suppression interval so a repeating customer doesn't re-alert every day. For tuning in depth, see the AML rules engine and fraud rules engine.

Three ways to run a scenario

Choose per scenario. Real-time returns an answer inside the API response, so your system can hold the payment; Salv itself executes nothing. Post-event runs when data arrives, and periodic runs on an interval you set. More on real-time AML monitoring.

Test it on your own data before it goes live

Run any scenario version against up to a year of your own history, with no real alerts, and see what it would have caught before your team works a single alert. Save the settings that worked as a new version.

Client testimonials

Banks know what the problems are, but Salv worked out how to really solve them. And it's not just in money laundering and terrorist financing, it's also been useful in fraud prevention.

Olavi Lepp CEO, Swedbank Estonia

With Salv's risk scoring tool, we can assess and manage customer risk, uncover high-risk patterns, and do so in a short time. As for transaction monitoring, we were able to cut the number of false positives significantly.

Michael Brand, Fincrime product manager · Juni

The transparent UI makes Salv's transaction monitoring convenient and easy to use. It has a clear structure that allows us to add and modify rules using our own criteria.

Paytend Europe

Specifically, we were looking for better rule implementation, reporting, and integrated customer risk scoring. Salv ticked all the boxes. Using Salv has helped us to significantly improve our team's efficiency.

Kroo Bank
All case studies

Salv tools that work together

  • Screening
    Screen customers and payments against sanctions, PEP and adverse-media lists, with matching you configure and lists Salv keeps current.
  • Risk scoring
    Customer risk rating on weighted rules built around your framework. Kept current as the facts change, feeding the monitoring and screening that act on it.
  • Intelligence sharing
    The secure network where fraud, AML and sanctions teams settle a case directly with other institutions. Send structured requests, answered in minutes, under rules your network agrees.
  • Alert and case management
    When an investigation grows, it becomes a case. Bring the related alerts, customers and payments together and work it from one place as a team.
Trust and security What we hold, where your data sits, and how every decision is recorded.
Explore

Transaction monitoring software FAQ

Software that checks payments and customer activity against scenarios describing suspicious behaviour, and raises an alert when one fires for a compliance or fraud team to work and decide on.

Monitoring looks at behaviour: what a customer is doing, with whom, and whether the pattern fits. Screening looks at identity, checking names against lists.

Patterns you describe in a scenario — many small payments that stay under a threshold, rapid movement of funds in and out, activity that does not fit a customer's usual behaviour, payments to high-risk countries — and customer-side patterns such as several customers on one IP address, a change in risk level, or frequent changes to personal details.

Yes. Start from the library and add your own alongside it, then test any version on up to a year of your own history before it goes live.