Monitoring across your channels
Designed for real-time transaction monitoring across core banking, card, mobile and agency channels, through the feeds Connection Studio maps in.
Trumi Watch
Trumi Watch was previously called IntegWatch.
A Deefrent product · Financial crime intelligence
For banks, microfinance banks, SACCOs, fintechs and payment service providers: monitor transactions for fraud and money laundering and work each alert as a case.
30-day pilot on one use case.
Trumi Watch is designed to sit beside the systems a bank already runs and to watch the channels its customers use. Microfinance banks, SACCOs, fintechs and payment service providers use the same platform, scoped to their channels.
Designed for real-time transaction monitoring across core banking, card, mobile and agency channels, through the feeds Connection Studio maps in.
Write fraud and AML rules in Rule Studio and simulate them on sample or historical transactions, so you see what a rule would flag before it reaches the live alert queue.
Alerts open as cases in Case Management, where your analysts triage, investigate and decide, with an evidence history kept on every case.
Trumi Watch runs alongside the core banking system you already have and reads transactions from it. It does not replace your core banking system.
Each transaction from your systems is evaluated, and anything that needs a closer look becomes a case. People make the decisions; the platform puts the evidence in front of them.
1
Connection Studio maps transactions from your core banking and payment systems into Trumi Watch.
2
Trumi Watch's transaction-risk engine evaluates each transaction against the rules and typologies you manage in Rule Studio.
3
Screening, Entity 360 and Graph add what is known about the people and accounts involved: list matches, risk signals and network patterns.
4
Alerts open as cases in Case Management, where your analysts investigate and decide.
Together they give an investigator one place to see a customer, an alert and the evidence behind it.
Connect a transaction feed from your core banking and payment systems, and manage those connections in one place.
Write detection rules and typologies, and test them in simulation before they go live.
Your analysts work each alert as a case through to a decision, with a record of every decision and the evidence behind it.
Sanctions and politically exposed person (PEP) screening of customers and counterparties, with each match recording the list it came from.
A single view of each customer, organisation and account, with every risk signal about them and the reasons behind it.
Network analysis of connected accounts and parties: who transacts with whom, and patterns such as fan-in, fan-out and several people sharing one phone number or address.
Trumi Watch's transaction-risk engine is an open-source project for real-time transaction monitoring, hosted by the Linux Foundation and released under the Apache 2.0 licence.
Trumi Watch is an independent product built on that engine, not a product of the open-source project itself. Because the core is open source, your team can inspect how transactions are evaluated instead of trusting a black box.
Built by Deefrent.
Deefrent has built core banking, payments and identity systems for African organisations since 2017. The same team builds Trumi Watch and works with you through an evaluation.
Trumi IDV and Trumi Watch are part of the Trumi family.
We do not publish detection rates: the results that matter are the ones on your own data. Banks, microfinance banks, SACCOs, fintechs and payment service providers judge Trumi Watch with us, on their own transactions.
Your risk, compliance and IT teams see the platform with the engineers who build it, and get straight answers on architecture, hosting and security.
We agree the scope, the data and what success looks like with you, then run the evaluation together.
The quickest way to judge Trumi Watch is on your own transactions. A pilot is scoped tightly, run with your compliance and IT teams, and measured against how you work today.
We agree a single fraud or AML use case with you, such as mule accounts or unusual mobile money flows, and connect one data feed from your systems.
Success criteria are agreed up front and measured against your current process: detection coverage, the false positives your analysts have to clear, and investigator time per alert.
At the end of the 30 days you get the results, the rules we tuned and what a full rollout would involve, so you can decide on evidence.
A 30-day pilot covers one fraud or AML use case and one data feed, run with your compliance and IT teams and measured against how you work today.
Want to see the platform first? Request a Trumi Watch walkthrough