Fraud, AML/CFT and risk scoring in the WAEMU

Every transaction scored.Every alert explained.

Fraud detection, analysis and risk scoring for the digital finance of French-speaking Africa. Reasons your supervisor understands, and a report ready for the CENTIF.

Request a demo See the journey

LiveYARDA consoleDemonstration data

AlertMobile money

Abidjan → Ouagadougou

950,000 CFA francs

Score94

Why this decision

RuleSplitting under the threshold at the same agent
Anomaly modelFive transfers in under an hour
Anomaly modelNew receiver for this sender

LabelEscalate

Transactions scored

Dakar → BissauTransfer · 45,000 CFA francs6Allowed
AbidjanMerchant payment · 12,500 CFA francs3Allowed
Ouagadougou → AbidjanTransfer · 150,000 CFA francs11Allowed

What you can check

BCEAO Instruction 001-03-2025
Article 12
Reporting statistics and the map of suspicious operations, counted by the console.
Read the guide
Suspicious transaction report
CENTIF
Written on the official form of the CENTIF of Côte d’Ivoire, missing fields flagged.
See the method
Pseudonymised data
HMAC-SHA256
Identifiers replaced on arrival. Names and addresses never kept.
Security page
French first
FR · EN
A console written in French, with the vocabulary of the BCEAO and the CENTIFs, and available in English.
Discover the console
The weight of this page
275 kB
HTML, styles, scripts, fonts, images and the map’s data, compressed and measured on every build. No third-party script.

The economy we protect

French-speaking Africa’s digital finance deserves tools built for it

A cash-in at the neighbourhood agent, a merchant payment by QR code, a transfer from a fintech in Abidjan or Dakar: every day, the Union relies on fast, low-cost transactions. YARDA protects that trust, in French, as close as possible to the BCEAO’s rules.

e-money accounts in the WAEMU at the end of 2024, up 19% in a year: 248 million
and one uniform anti-money laundering law: 8 states
per state, where your suspicious transaction reports go: 1 CENTIF

Source of the first figure: BCEAO, Annual report on digital financial services in the WAEMU, 2024 (in French)

Mobile money, every day

Cash-ins, cash-outs and payments at the agent or the shopkeeper: fraud hides in that volume.

Fintechs and banks that innovate

Payment institutions, e-money issuers, aggregators: teams building the Union’s finance.

The compliance analyst, at the heart of it

The person who examines, decides and reports. YARDA is first of all their tool.

Who it is for

Mobile money operators
Payment and e-money institutions
Payment aggregators
Money transfer companies
Next: banks and microfinance institutions

The problem

The tools on the market were not built for you

A compliance officer must detect, justify and report. With fixed rules and solutions designed elsewhere, each of these steps costs too much.

Fraud gets around fixed rules
Splitting under limits, pass-through accounts, fake reversals: the schemes change faster than thresholds written once and for all.
02
Tools designed for other markets
Agents, cash-ins and cash-outs, transfers between the Union’s countries: international solutions know neither these uses nor the BCEAO’s vocabulary.
Channel
- Card
- Wire
- Cash-in at the agentUnknown
Alerts no one can justify
A score without an explanation cannot be defended before an auditor or your supervisor. And every false alert ties up an analyst.

How it works

From the transaction to the report, in six moves

YARDA follows your compliance team’s path, from raw data to the CENTIF, and every decision makes your models better.

Data comes in

Connect your transactions however you can

Through the real-time API, through a file uploaded in the console, or through a view of your database read every minute. Identifiers are pseudonymised on arrival, before anything is stored.

YARDA scores

Every transaction gets a score from 0 to 100

Your rules and models trained on your data alone, specific to your institution, score every transaction. The decision follows the thresholds of your policy.

The analyst understands

Reasons in plain language

Every alert comes with its reasons, strongest first: the rule that fired, what the model found unusual. Enough to justify a decision before an auditor.

The team decides

Label, escalate, approve with four eyes

A case gathers the related alerts, the timeline and the comments. When your policy requires it, a decision proposed by one person is approved by another.

You report

The suspicious transaction report, ready for the CENTIF

The draft is written from the case, on the official form of the CENTIF of Côte d’Ivoire. When it is sent, it is sealed with a SHA-256 fingerprint. Sending it remains yours.

The model learns

Your decisions make your models better

Your labels retrain your models. A new model first runs in observation: it only goes live if it outperforms the current one.

What your team gets

Your whole AML/CFT set-up, in one console

Every feature below exists in the product today. What it does not do yet is written on our product pages and our comparison.

01 · DetectDemonstration data
IfAmount summed over 24 hgreater than1,000,000 CFA francs
AndSame agentThenAlert
Replay over 90 days37 alerts it would have raised
Your rules, and a model of your own
Every transaction goes through your rules and through models trained on your data alone, isolated from other operators’.
- An IF/THEN editor and eight built-in typologies
- A replay over 30, 60 or 90 days of your history
- Sanctions screening: the United Nations list and the national list of Côte d’Ivoire
Product proof
A rule can only be submitted for approval after a replay on your history.
The guide to setting the policy
02 · DecideDemonstration data
Case#04123 · Related alerts
Proposed byAnalyst
Approved bySupervisor
Audit trail
#1042 · sha256 9f3c…a41e
#1043 · prev 9f3c…a41e · 2b7d…0c95
Cases kept with four eyes
A case gathers the related alerts, the timeline and the comments. A decision proposed by one person is approved by another.
- Closures, reports and rules submitted for approval, as your policy sets
- Four roles and two-factor authentication your policy can require
- A chained audit trail the database refuses to change
Product proof
Each entry of the trail carries the SHA-256 fingerprint of the one before.
The guide to working a case
03 · ReportDemonstration data
Suspicious transaction report
CENTIF · Côte d'Ivoire
Mandatory fieldscomplete
Sealed
Annual report to the BCEAO
Reporting statistics
Map of suspicious operations
Compliance ready to sign
The suspicious transaction report is written from the case, on the official form of the CENTIF of Côte d’Ivoire, and the annual report gets its figures.
- Missing mandatory fields flagged before sending
- A report sealed with a SHA-256 fingerprint, as a PDF on the CENTIF form
- The statistics and the map of article 12 of BCEAO Instruction 001-03-2025
Product proof
YARDA prepares the report; sending it remains yours.
The guide to reporting to the CENTIF
04 · ProtectDemonstration data
ReceivedStored
Customer identifierCLI-20931→hmac 9f3c…a41e
Phone+225 •• •• •• 12→hmac 2b7d…0c95
Name•••••• ••••→Never kept
Data that does not say who
YARDA needs neither your customers’ names nor their addresses to score a transaction. Your identifiers become fingerprints on arrival.
- A keyed fingerprint (HMAC-SHA256) specific to your institution
- Each institution isolated by the data access layer
- A console checked on every release against a 3G profile: 400 ms of latency, 400 kbit/s
Product proof
Hosting, in the United States today, is stated plainly and discussed before any pilot.
Read the security page

Request a demo

A demo on fictitious data, then a free diagnostic on your history.

Discover the console

Two ways to start

Start with no development, move to real time when you choose

Both routes feed the same history and the same console. The free diagnostic starts from a simple export.

YARDA ConnectMonitoring
A file or a view of your database
Upload an export from the console, or let YARDA read a view of your database. No integration project.
- Your own column names, mapped once
- A PostgreSQL view read every minute, read-only
- Ideal for the free diagnostic on your history
Does not stop a transaction before it executes: it is scored afterwards.
Discover Connect
Real-time APIPrevention
A decision before execution
Your system calls YARDA for each transaction and receives the score, the decision and its reasons.
- Complete documentation, generated from the API’s description
- Keys with limited rights, shown only once
- Retryable requests, never recorded twice
Needs development work on your side or your provider’s.
Read the documentation

Start with a file and move to the API later: your history and your settings stay in place.

Request a demo

A demo on fictitious data, then a free diagnostic on your history.

Security and data

Your data, without approximation

A compliance officer must be able to answer their supervisory authority. Here is what is true today, including what is not true yet.

Hosting

Your data is hosted in the United States today, outside the WAEMU. Hosting in the region or at your institution is being studied: let us talk about it before any pilot.

Pseudonymised on arrival
Customers, phones, wallets and agents become a keyed fingerprint (HMAC-SHA256), specific to your institution.
Each institution isolated
Every read and every write is restricted to your institution by the data access layer itself.
Controlled access
Four roles, two-factor authentication your policy can require, identity confirmation for sensitive acts.
Verifiable traceability
A chained audit trail, sealed reports, and every access by YARDA support listed in the console.

Request a demo

A demo on fictitious data, then a free diagnostic on your history.

Read the security page

Frequently asked questions

What compliance teams ask us

See pricing and the pilot

When does YARDA start detecting?

Your rules and the typologies you switch on apply from the first transaction received. The anomaly model then learns from your history, with no prior labels, and the supervised model joins as your teams label alerts.

How much does it cost?

The diagnostic on your own data is free. The pilot, of 60 to 90 days, follows success criteria agreed together before it starts. The subscription is then billed in CFA francs, according to your volume.

Do we need to send our customers’ names?

No. YARDA does not need them to score a transaction: send your internal identifiers, pseudonymised on arrival. Only sanctions screening needs a name, compared in memory and then forgotten.

Where is our data hosted?

In the United States today, with Neon for the database and Railway for the API. This transfer outside the WAEMU may call for formalities with your data protection authority: we discuss it before any pilot.

Can we start with a file and move to the API later?

Yes. The imported history and your settings stay in place; only the way transactions are sent changes. Both routes can also run together.

Are the console and the support in French?

Yes. The console is written in French, with the vocabulary of the BCEAO and the CENTIFs, and available in English. Support is given in French and English.

See YARDA on your own transactions

Tell us who you are: we will get back to you to arrange a demo, then a free diagnostic on your history. No development, no commitment.

What happens next

A demo of the console, on fictitious data
A free diagnostic on three to six months of your history
A pilot with success criteria agreed together

Every transaction scored.Every alert explained.

What you can check

French-speaking Africa’s digital finance deserves tools built for it

The tools on the market were not built for you

Fraud gets around fixed rules

Tools designed for other markets

Alerts no one can justify

From the transaction to the report, in six moves

Connect your transactions however you can

Every transaction gets a score from 0 to 100

Reasons in plain language

Label, escalate, approve with four eyes

The suspicious transaction report, ready for the CENTIF

Your decisions make your models better

Your whole AML/CFT set-up, in one console

Your rules, and a model of your own

Cases kept with four eyes

Compliance ready to sign

Data that does not say who

Start with no development, move to real time when you choose

A file or a view of your database

A decision before execution

Your data, without approximation

Pseudonymised on arrival

Each institution isolated

Controlled access

Verifiable traceability

What compliance teams ask us

See YARDA on your own transactions

French-speaking Africa’s digital finance deserves tools built for it

The tools on the market were not built for you

Fraud gets around fixed rules

Tools designed for other markets

Alerts no one can justify

From the transaction to the report, in six moves

Connect your transactions however you can

Every transaction gets a score from 0 to 100

Reasons in plain language

Label, escalate, approve with four eyes

The suspicious transaction report, ready for the CENTIF

Your decisions make your models better

Your whole AML/CFT set-up, in one console

Your rules, and a model of your own

Cases kept with four eyes

Compliance ready to sign

Data that does not say who

Start with no development, move to real time when you choose

A file or a view of your database

A decision before execution

Your data, without approximation

Pseudonymised on arrival

Each institution isolated

Controlled access

Verifiable traceability

What compliance teams ask us

See YARDA on your own transactions