Stop fraud and money laundering in real time

Map of Africa with connected points across the continent
infrastructureRuns on your own servers
integrationConnected to your payment rails
configurationTuned to your transaction data
complianceData stays in your jurisdiction

Who we work with

PSPs

High-volume transaction switches are exactly where fraud and laundering slip through. We embed monitoring close to the rails.

Banks

Commercial and microfinance banks under regulatory pressure to detect financial crime in real time, without handing transaction data to a third party.

Fintechs

Digital lenders, wallets and neobanks scaling fast, often faster than their compliance infrastructure can keep up.

Insurance

Insurers exposed to premium and claims fraud, needing detection built into their own systems rather than bolted on after the fact.

The problem we solve

Fraud and money laundering move at the speed of the transaction. Most institutions only catch them after the fact, once the loss or the violation has already happened. Regulators increasingly expect real-time detection, not overnight batch reports, and building that in-house is slow, expensive, and hard to keep current.

We solve it by implementing Tazama: an open-source, real-time transaction monitoring engine for fraud and financial-crime detection, hosted by Linux Foundation Charities with support from the Bill & Melinda Gates Foundation. It scales from a single small provider to a national payment switch processing thousands of transactions a second

Real-timeScores transactions before they complete
Open sourceNo license fees, no vendor lock-in
ConfigurableDetection rules set outside the code, easy to tune

How we work

Getting real-time fraud and AML monitoring live inside your institution, implemented on Tazama, the open-source engine, from architecture to production.

01

Assess

We map your architecture, transaction volumes, fraud and AML exposure, and constraints before anything gets deployed.

02

Deploy

We stand Tazama up on your own infrastructure: your own servers or your private cloud, your choice.

03

Configure

We tune rules and typologies to your data, not generic defaults.

04

Enable

We connect it to your core banking system, payment switch and case management tools, and build what's missing.

05

Support

We stay on as your rules, volumes and requirements change.

Frequently asked questions

Why should fraud and AML monitoring run on your own infrastructure?+

Because your transaction data never leaves your environment or jurisdiction, often a hard requirement for regulated institutions. You're also not dependent on a third party's uptime or roadmap for something this critical. We implement this using Tazama, the open-source monitoring engine, so you get a proven system without vendor lock-in.

If Tazama is open source, what does Basalink actually add?+

The software is free; getting it deployed, tuned to your transaction patterns, and integrated into a live production environment is the part that takes specialist time. We handle that end to end, and stay on to support it afterwards.

Can you deploy on our own infrastructure?+

Yes, that's the default. We deploy on your own servers or inside your own private cloud account.

Get in touch

Tell us what you're running, your transaction volumes, and what fraud or AML risks you need to catch. We'll tell you honestly whether we're the right fit.

hello@basalink.co.ke