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.
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.
Now onboarding early-access partners.
In evaluation and open to early-access partners. Three of six modules are in development.
IntegWatch 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.
IntegWatch 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 IntegWatch.
2
IntegWatch's transaction-risk engine evaluates each transaction against the rules and typologies you manage in Rule Studio.
3· In development
Screening, Entity 360 and Graph will 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.
Connection Studio, Rule Studio and Case Management are in evaluation today. Screening (sanctions and PEP), Entity 360 and Graph are in development. Together they are designed to give an investigator one place to see a customer, an alert and the evidence behind it.
Map the data from your core banking and payment systems to the formats IntegWatch reads, and manage those connections in one place.
Write detection rules and typologies, and simulate them before they go live.
Alert triage, investigations, cases and reports in one place, so your analysts work each alert through to a decision.
Being built to screen customers and counterparties against sanctions and politically exposed person (PEP) lists, with each match recording the list and the version it came from.
One view of each person, organisation and account, with every risk signal about them and the reasons behind it.
Map who transacts with whom, and surface network patterns such as fan-in, fan-out and several people sharing one phone number or address, with the transactions behind each.
An early-access partner evaluates what is built today. The roadmap is listed separately so the two are never confused.
On the evaluation platform, with your own transaction data.
Not available today. Planned capabilities, subject to build and readiness; we will tell you exactly where each one stands.
IntegWatch'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.
IntegWatch 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 IntegWatch and works with you through an evaluation.
IntegWatch is not yet generally available, and 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 that join early access evaluate it with us.
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.
Early-access partners help decide which capabilities and integrations come first.
The quickest way to judge IntegWatch 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 is 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 an IntegWatch walkthrough