Tazama and WiredIn Partner Following Joint RSwitch Deployment in Rwanda

Tazama, the open-source transaction-monitoring project, and WiredIn have announced a strategic partnership following their first joint deployment with RSwitch in Rwanda. The announcement is Tazama's. Our interest in it is different: it is one of the clearer public examples of fraud-monitoring technology being implemented inside a live African payment environment, rather than discussed in principle.

Why this development matters

Most fraud technology conversations stop at capability. What can the engine detect? How fast does it score a transaction? Which typologies are covered?

Those questions matter, but they are rarely the reason a programme succeeds or stalls. The harder work sits between the technology and the payment environment it is supposed to protect: understanding the transaction flows, mapping the data, agreeing where monitoring sits, connecting the alerts to people who can act, and keeping all of it running once the launch team has moved on.

A deployment involving a national switch is a useful reminder that this combination — technology, integration capability and local implementation expertise — is what turns a product into a control.

The challenge: fraud is moving as quickly as payments

Payment ecosystems across our markets have become faster, more digital, more interconnected and more distributed. A single payment may pass through a customer, a channel, an account or wallet, a payment platform, a switch or processor, a bank or fintech, and finally a merchant or beneficiary.

Fraud controls designed for a slower, more centralised world struggle in that environment for two reasons. They often assume a settlement delay that no longer exists, and they often sit inside one institution while the fraud pattern spans several.

That is why monitoring increasingly has to operate close to the transaction flow, with enough context available at decision time to be useful.

Why implementation matters as much as technology

This is the part of the story we would ask executives to focus on.

Even strong monitoring technology has to be integrated into existing platforms, configured for local rules and thresholds, connected to real transaction and customer data, tested against realistic volumes, wired into investigation and case-management workflows, and then operated and maintained.

Each of those steps is an engineering and operating-model problem, not a licensing decision. Programmes tend to under-scope them, and the result is familiar: a capable platform producing alerts nobody can action.

AO's systems integration capability exists precisely for this layer — connecting monitoring to switches, core systems, channels, customer data and downstream processes so that a detection signal becomes an operational response.

Rwanda as a practical example

Rwanda has been deliberate about digital payments and interoperability, and a deployment with a national switch reflects that. We would not generalise one market into a continental pattern — conditions, regulation and infrastructure differ substantially across African markets.

What the example does illustrate is a set of requirements that recur: support for growing digital payment volumes, interoperability between participants, fraud controls that work at scheme level rather than only inside individual institutions, room to scale, and respect for local regulatory and operational requirements.

From transaction monitoring to connected financial intelligence

Transaction monitoring is most valuable when it is not isolated. In the architecture AO works with, it sits in a chain:

Identity establishes who the customer is. Transaction monitoring observes what the account is doing. Behavioural signals indicate whether that activity makes sense for this customer. Risk scoring turns that into a decision. Action is the alert, the hold, the investigation or the customer contact.

Tazama sits primarily in the transaction-monitoring layer. It does not perform identity verification or behavioural banking; those come from other components. The value of connecting them is that each layer makes the others more accurate — a point we explored in Synthetic Identities and Mule Accounts: Why KYC Alone Is No Longer Enough.

The same logic runs through Connected Banking: onboard, transact, monitor, understand, engage, grow.

How AO can help

AO works with banks, fintechs, switches and payment providers on the implementation side of this problem: assessing transaction-monitoring requirements, designing the architecture and where monitoring sits in the payment flow, integrating with existing platforms and APIs, building the data pipelines and mappings, configuring and testing rules, connecting alerts to case management and reporting, supporting deployment and testing, and operating the capability where that is contracted.

AO Transaction Monitoring describes that capability in more detail. We can incorporate technologies such as Tazama within it; we do not present them as AO-owned products, and we do not claim any technology eliminates fraud. What good implementation does is shorten detection time, give investigators usable context, and make it realistic to adapt as fraud patterns change.