Go back to Blog
Jennifer Edidiong
Marketing
9 min read
Share to
Five Things Your Fintech Should Never Do: A 2026 Fraud Awareness Week Guide

Fraudsters don’t need to hack anything when they can simply ask. A message that looks like it came from your bank, a supplier who has “changed banks”, a customer with perfect documents: most scams work because they look believable for a few seconds. Those few seconds are where fraud is won or lost.
You have felt that pause yourself, with your thumb over a link and a message that almost made sense. Now picture it landing with an engineer on your wallet team, an agent on your support desk, or the finance lead who approves payouts. In a fintech, those few seconds sit close to money.
International Fraud Awareness Week runs from 15 to 21 November. The Association of Certified Fraud Examiners leads it as a global effort to minimise the impact of fraud through awareness and education, and Dojah is taking part. ACFE’s Certified Fraud Examiners estimate that organisations lose about 5% of their revenue to fraud every year. Losses like that rarely arrive as one dramatic event. They build from small moments nobody questioned.
This guide is for the people who keep a fintech running: engineering teams, compliance and risk teams, finance and operations, and product and support. It covers five things never to do, each with a Golden Safeguard you can start using today, and it ends with two free reviews to help you check where you stand.
1. Don’t click first and check later
For everyone with an inbox, especially engineering and security teams.
Fraudsters love to go fishing, and their favourite bait is a message that looks like it came from someone you trust. It has the right logo, it knows your name, and it really wants you to “click here”. Look closer and something is often off by a letter or two.
Try this. Which of these senders is real?
- alerts@examplebank-secure.com
- alerts@examp1ebank.com
- alerts@examplebank.com
- alerts@examplebank.com.verify-now.net
Only one is genuine. The others add an extra word, swap the letter “l” for the number “1”, or hide the real domain at the very end.
Your staff are targets too, and in a fintech company, one laptop can sit close to the systems that move money. In October 2026, attackers drained about $6.3 billion from Binance’s hot wallets, most of it in roughly 20 minutes. Binance’s own investigation report calls it a multi-stage attack, not a one-off breach or a simple phishing attack. The first steps were ordinary:
- June: An engineer searching for a popular AI coding tool downloaded a tampered installer.
- September: Another engineer, approached through a legitimate job platform, went through two rounds of fake interviews and was asked to download an “assignment” to a work computer. It ran malicious code, and Binance says its security tools missed it.
- October: The attackers used that laptop and an internal AI tool to take over two more engineers’ computers. They found a token with deployment permissions and, days later, used it to reach the system that signs wallet transactions.
Binance says it will cover all losses and that 98% of the affected assets have been replenished. No single click did all this. For engineering teams, the lesson is plain: never run code from someone you haven’t verified, and keep powerful credentials off everyday work laptops. For everyone else, make it safe to report an odd recruiter approach or download without fear of blame.
Golden Safeguard: Check the full sender address and the real web address before you click. When in doubt, skip the link, open the official app or type the website yourself. Never run code or open files from someone you have not verified, even when the request arrives through a professional platform.
2. Don’t trust a face or a name you haven’t verified
For compliance, risk and onboarding teams.
Picture your review queue on a busy Monday. An account opens with a clean ID and a good selfie, and it passes every check. Three weeks later, another account opens with a different name and different ID details. Looked at one at a time, both look fine. Put side by side, the face is the same.
Verifying someone at the door is the right start, but it doesn’t settle the question. A fraudster who gets through looks like any other customer. What stays hidden is the pattern: the same face across several accounts, or two records with conflicting identity details. Those patterns rarely show when records are reviewed one at a time. That second look is what The Dojah Double Take Initiative is for, and you can read about it below.
Golden Safeguard: Confirm who someone is before you give them an account, a limit or your trust, and look again at the records you already hold.
3. Don’t let a code leave your hands
For support, operations and engineering teams.
A fraudster can have your name, your number and your email, but they still need your code. Never share your password, OTP or MFA code, and never approve a sign-in you didn’t start. Dojah will never ask for your password, OTP or PIN by email, phone or message, and no genuine organisation should.
Fraudsters will happily pretend to be you. Picture a caller who knows a customer’s name asking your support agent to “reset” an account, or a staff member getting an “urgent” approval prompt for a login they never started. Two habits help. Tell customers plainly how you will and will not contact them, and repeat that line in every message you send. And teach staff that an approval prompt they didn’t trigger is always a reason to stop and report.
Golden Safeguard: If someone asks for a code, the answer is no, however urgent or friendly the request sounds.
4. Don’t change where money goes because an email said so
For finance, operations and risk teams.
Imagine a supplier you pay every month emails to say they’ve changed banks. The email looks right, the tone sounds right, and the new account details are right there. It might be genuine, or it might be a fraudster quietly redirecting your payment
The same trick turns up in vendor payments, settlement accounts and payout details. Replying to the email, or calling the number in its signature, may lead straight to the fraudster. A small test payment only proves the account exists, not who owns it.
Nobody can watch every transaction by eye. Warning signs include a first payment to a new account, sudden large transfers, or money that arrives and leaves almost immediately. Spotting these across thousands of transactions is what transaction monitoring is for. Dojah’s EasyDetect checks each transaction against rules you set and returns a decision to allow, flag for review or block. Flagged transactions go to a queue where an analyst records the decision and the reason.
Golden Safeguard: An email alone is never enough to change where money goes. Call the business on a number you already have, have a second person approve the change, and hold the payment until it is confirmed.
5. Don’t let an alert sit
For compliance, fraud operations and engineering teams.
Anyone can click something they shouldn’t have. What matters is what happens next. Report it straight away to your bank, your IT team or the platform involved. The sooner it’s reported, the more can be done.
The same goes for alerts inside your business. Many fintechs have the right tools: they verify customers, watch transactions and flag risky activity. The gaps appear between those tools, when information isn’t connected, or when an alert is raised and nobody follows it up.
Speed matters across the industry too. At the 2026 Nigeria Electronic Fraud Forum, the CBN and industry players recommend cutting fraud response times to under 30 minutes. A flag that waits in a queue for days works against that target. The Fraud Stack Assessment Test asks whether your alerts have an owner and get followed up.
Golden Safeguard: Report fast and give every alert an owner and a deadline.
How to Safeguard Your Fintech Today
Two gaps are easy to miss in a fintech, and both hide in the space between things you already do. One sits between your tools, while the other sits between your customer records. Dojah has a free offering for each.
Disconnected defences: The Fraud Stack Assessment Test
You may already verify customers, monitor transactions and flag high-risk activity. The question is whether those tools work together. Gaps open when information isn’t connected or an alert has no owner: an onboarding check marks a customer as higher risk, but the flag never reaches the team watching their payments. Every tool does its job, and the fraud still slips through.
The Fraud Stack Assessment Test is a free way to find those gaps. It reviews your current approach against a stronger strategy, one where:
- Customers are verified at onboarding.
- Payments and transfers are watched.
- High-risk activity is marked.
- Alerts are reviewed and acted on.
- Information is connected.
- Alerts are followed up.
Take the free Fraud Stack Assessment Test.
Duplicate identities: The Dojah Double Take Initiative
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 identifiers, such as the same BVN or NIN on different customer records.
- Other supported identity-data anomalies that deserve closer investigation.
You receive a report with the records reviewed, potential matches, areas to investigate and recommended next steps. It is for banks, fintechs, digital lenders, marketplaces and other businesses with customer identity databases.
Registration does not require you to upload customer data, and selected businesses complete eligibility, legal, and security checks first. A potential match is a lead to investigate, not proof of fraud.
Start using Dojah for all your business needs