Go back to Blog
Jennifer Edidiong
Marketing
11 min read
Share to
7 Hidden Signs of Fraud on Your African Fintech Platform (And How to Catch Them)

From 15 to 21 November 2026, organisations and fraud professionals around the world will mark International Fraud Awareness Week. The annual campaign draws attention to the different ways fraud affects businesses and why recognising it early matters.
The figures from Nigeria show why these patterns deserve attention. Social engineering accounted for 47% of fraud volume in 2025, while internet banking recorded ₦13.37 billion in losses across just 4,507 cases. Fraud does not always require thousands of suspicious transactions to cause significant losses. Sometimes, a small number of cases is enough.
For African fintechs, some signs of fraud are easy to recognise. They appear in suspicious transactions, unusual account activity and reported losses. The harder part is what looks normal: a customer who passes verification, an account that stays quiet for weeks, or several accounts that appear unrelated.
This year's Fraud Awareness Week, we're looking at seven hidden signs of fraud on African fintech and digital platforms. We follow the activity from account opening to money movement, showing what each sign looks like, why it can go unnoticed and what businesses can do to catch it.
Sign 1: Clean KYC and a Strange Session

A customer submits an identity document, takes a selfie, passes verification and gets an account. Everything checks out. But there's something unusual about how they completed the process. They're connecting through a VPN, their device location doesn't match the country on their ID, or the information in their registration form was entered at a speed that doesn't look quite human.
- Why it hides: Your KYC checks may confirm that the document is valid and the face matches. But that doesn't tell you everything about the session used to complete the verification. Someone can present a genuine identity document while using a suspicious connection or device.
- How to catch it: Don't stop at checking the ID and selfie. Examine IP and device signals during sign-up, including VPN or proxy use and location mismatches. Where your platform supports it, watch for pasted information and unusually fast form completion. Send suspicious combinations for further review instead of automatically approving them.
- What not to do: Don't treat a passed ID and selfie as proof that everything about the account is legitimate. The identity may check out, but the session deserves attention too.
Sign 2: One Device or Number Behind Many Accounts

Imagine approving several new accounts. Different names, identity documents and selfies. Each customer completes verification successfully. Nothing immediately raises a concern. But when you look closer, you notice that the accounts were opened using the same device or share the same phone number.
- Why it hides: Each account passes verification on its own. The connection between them only becomes visible when you compare customer records. If your checks stop at individual accounts, you may miss someone using multiple identities to operate several accounts.
In January 2026, the EFCC disclosed that investigations had uncovered a case involving one individual operating 960 accounts within a single bank, all allegedly used for fraudulent activities.
- How to catch it: Don't just check who is opening an account; pay attention to how many accounts are connected to the same device or phone number. Set limits that trigger a review when an identifier appears across several accounts. Also, watch for multiple accounts created within a short period.
- What not to do: Don't assume that different names and identity documents mean different people. Check the connections between accounts, not just the information on each one.
You can also review the customer records you already hold to uncover identity details that may link accounts you previously treated as separate.
Sign 3: A Dormant Account That Is Waiting

An account passes onboarding, gets approved, and then does nothing. No transactions, no logins, no activity worth flagging. Weeks later, it suddenly becomes active. The first sign of life may be a login from a new device, followed by a large transaction or several transfers in quick succession.
- Why it hides: A quiet account doesn't look urgent. If your monitoring focuses on what customers do every day, an account doing nothing can easily slip out of view. But inactivity doesn't tell you what the account will be used for later.
- How to catch it: Track how long an account stays inactive after opening. Pay attention when a dormant account becomes active again, especially if it logs in from a new device or moves a large amount soon after. Ask for a fresh verification step before allowing the activity to continue.
- What not to do: Don't assume an account is harmless just because it has been quiet. Keep its history in view, and pay attention when its behaviour changes.
For example, an account opens on Monday, stays inactive for six weeks, then logs in from a new device and sends most of its transaction limit within ten minutes.
Sign 4: A SIM Swap Before a Login

A customer has always used the same phone number to access their account. Then, shortly before a login or password reset, the SIM linked to that number is swapped. Soon after, someone requests an OTP or tries to log in from a new device. The code goes to the registered number, and the activity may look like a normal login.
- Why it hides: Your system sees an OTP delivered to the correct number and may treat that as proof of ownership. But the SIM swap may have happened outside your platform, giving someone else control of the number.
- How to catch it: Check for recent SIM swap activity when someone logs in, resets a password, or attempts a sensitive transaction. A recent swap combined with a new device should raise concern. Pause the action or request an additional verification step before granting access.
- What not to do: Don't assume that an OTP sent to the right number means the right person is using the account. The number may be familiar, but the person behind it may not be.
Sign 5: A New Beneficiary and a Fast Cash Out

A customer logs in, adds a new beneficiary, and sends most of the money in their account to that person within minutes. Each action may look ordinary on its own. But when they happen one after another, so quickly, it's worth asking what's going on.
- Why it hides: The login is valid. Adding a beneficiary is allowed, and sending money is a normal part of using an account. If your system checks these actions separately, you may miss the unusual sequence connecting them.
- How to catch it: Pay attention to what happens after a customer adds a new beneficiary. Set a rule to flag large transfers made to a newly added beneficiary within a short period. Consider holding or delaying the first transfer and notifying the account holder through a verified channel before allowing it to go through.
- What not to do: Don't let a first transfer to a new beneficiary go through instantly just because the login is valid. A successful login doesn't automatically make every action that follows safe.
Take, for example, a customer who logs in at 9:02, adds a new beneficiary at 9:04, and sends nearly their entire account balance at 9:06.
Sign 6: Money In From Many and Out Fast

Imagine an account receiving several small payments from different people throughout the morning. Then, before the day is over, almost all the money is transferred out, leaving the account with little or nothing in it.
- Why it hides: Each payment may look normal on its own. The outgoing transfer may also appear legitimate. The concern becomes clearer when you look at how the money moves through the account: many people send money in, and someone quickly moves it all out.
- How to catch it: Don't just look at how much money enters or leaves an account. Pay attention to how many different people send money into it and how quickly that money leaves. Flag accounts that repeatedly receive money from multiple unrelated senders and quickly transfer or cash it out. Also, review the accounts receiving the money.
- What not to do: Don't assess credits and debits one transaction at a time. Look at the full movement of money through the account.
For instance, an account that receives eleven small payments from eleven unrelated people in one morning, then makes one transfer that clears almost the entire balance by lunchtime.
Sign 7: A Profile That Does Not Fit Its Activity

A customer signs up as a student, but months later, their account starts handling sums you'd expect from a business. Or a small business account begins moving money like a personal account. The activity no longer matches the profile they provided.
- Why it hides: The profile information was valid when the customer signed up. But if nobody checks it against their activity later, the mismatch can go unnoticed.
- How to catch it: Don't rely on onboarding information alone. Compare each customer's stated occupation and expected transaction volume with their actual account activity. If there's a significant mismatch, flag it and ask for more information.
- What not to do: Don't treat customer information collected at onboarding as final. People's financial activities change, and your understanding of their accounts should change with them.
Each of these looks harmless alone, and that is the point.
Bring the Hidden Signs of Fraud Into View
Some fraud signals are easy to see. It appears in suspicious transactions, customer complaints and reported losses. But other signs are harder to catch: the account that passes verification but behaves unusually, the same device linked to multiple accounts, or money moving through an account before anyone notices the pattern.
The impact may go beyond the transaction itself. The good news is that businesses can do something about it by looking beyond individual checks and examining what their systems might be missing.
Here are two free ways to start:
Test how your fraud controls work together: Fraud Stack Assessment Test
Signs 1, 5 and 6 share a cause. Each check passed on its own, and nothing connected them: the KYC was clean, the login was valid, the payments looked normal. You may already verify customers, monitor payments and flag high-risk activity. The harder question is whether those checks talk to each other.
The Fraud Stack Assessment Test is a free way to find out. It reviews your current approach and shows where gaps exist. It looks at whether:
- Customers are verified at onboarding.
- Payments and transfers are watched.
- High-risk activity is marked.
- Customer information is connected across checks.
- Alerts are reviewed and acted on.
- Alerts are followed up.
Take the free Fraud Stack Assessment Test to find gaps in your fraud controls.
Look closer at your existing customer records: Dojah Double Take Initiative
You may have verified thousands of customers. But have you checked whether the same face appears across different accounts, or whether records carry conflicting identity details? Sign 2 showed accounts linked by a device or a phone number. The identity version of that problem can sit inside the records you already hold, and it rarely shows when each record is checked on its own.
The Dojah Double Take Initiative is a free fraud discovery audit that gives selected eligible businesses a second look at their existing customer identity records. Through a complimentary Identity Integrity Assessment, Dojah checks for:
- Potentially matching faces linked to different customer records.
- Similar facial images associated with different identity details.
- Repeated or inconsistent identity information.
- Other supported identity-data anomalies that deserve closer investigation.
You receive a report outlining the records reviewed, potential matches, areas to investigate and recommended next steps. Registration does not require you to upload customer data. Selected businesses complete eligibility, legal and security checks before any assessment begins, and potential matches do not automatically indicate fraud.
Start using Dojah for all your business needs