Posts

The Audit Wake‑Up Call: How I Fixed the One Rule That BFIU Inspectors Never Let You Forget

Image
AI-generated illustration Bangladesh, 03:12 AM. My phone buzzed. A red banner on the compliance dashboard read ‘STR #84273 – BDT 27.4 million – 12‑hour velocity breach’ . My heart jumped. The audit team from BFIU was on the floor tomorrow, and they loved to hunt the exact pattern I was staring at. I grabbed a coffee, opened the log files, and realized my velocity rule was flagging every 100 k‑BDT transaction after midnight – but the regulator’s own guidance says the threshold should be applied per *customer*, not per *account*. One mistake, and the whole audit could turn into a three‑day interrogation. The Hidden Problem: Why the Usual Velocity Rule Crumbles in Bangladesh Most fintechs in Dhaka, Chattogram, or Sylhet build a simple count‑and‑sum filter: Group by customer_id Sum transaction_amount for the last 24 hours If sum > BDT 100,000, raise an alert Sounds solid, right? It mirrors the BFIU’s Regulation 15‑2023 on “High‑Velocity MFS Transactions”. Yet in practice the rule tri...

Why Most Dhaka Shops Fail at Automation and the 9‑Step DIY Fix I Built in a Weekend

Image
AI-generated illustration 🚌 Try it yourself — Bus Fare Calculator BD This case study is based on a real, live product. Check it out below. Get Bus Fare Calculator BD → It was 9 AM on a rainy Tuesday. My phone buzzed: a small textile shop in Old Dhaka had just lost BDT 45,000 because their inventory spreadsheet never updated after a flash sale. The owner, Rafiq, was on the phone screaming, "If I don’t know what’s left, I can’t restock!" I was still half‑asleep, but the panic was real. I promised a fix by Friday. The Hidden Problem Most small businesses in Dhaka treat automation like a luxury only big firms can afford. They either hire a developer for a one‑off script that breaks after a month, or they keep doing manual copy‑pastes because "it’s easier than learning code". The real blocker isn’t the tech; it’s the mindset that automation requires a full‑time dev team. Automation is a habit, not a product. When I asked Rafiq why he never tried a bot, he said: "My...

Why My Small Shop Chose n8n Over a Python Script—and How You Can Replicate the 6‑Step Win

Image
AI-generated illustration 🚌 Try it yourself — Bus Fare Calculator BD This case study is based on a real, live product. Check it out below. Get Bus Fare Calculator BD → It was 9 am on a rainy Tuesday in Gulshan. My client, a boutique tea retailer, pinged me with a panic‑filled screenshot: their order‑sync webhook was choking on 1,200 new rows every hour. The dashboard showed a red exclamation, the sales team was fielding angry calls, and the owner threatened to pull the next month’s retainer. The Hidden Problem Most SMEs Miss Everyone assumes “just write a Python loop” and you’re done. In Bangladesh the reality is harsher: 3G still haunts the outskirts, data caps bite hard, and the average developer on Upwork is juggling three time zones. A raw script that pulls a MySQL dump, massages it, and pushes to Shopify works in a dev box, but in production it stalls at 10 % CPU, throws “connection reset” errors, and eats the client’s limited bandwidth. The pattern is the same: a one‑off sc...

The 7‑Step PageSpeed Outreach Engine I Built After Losing a $2,000 Client

Image
AI-generated illustration 🚌 Try it yourself — Bus Fare Calculator BD This case study is based on a real, live product. Check it out below. Get Bus Fare Calculator BD → Real‑World Hook It was 9 a.m. on a rainy Tuesday in Banani. My client, a boutique apparel shop that sold t‑shirts on a custom Shopify store, pinged me: “Google just sent us a PageSpeed warning. We’re losing 12 % of traffic, and the checkout page is now a 6‑second crawl.” I stared at the email while the monsoon drummed on my window. The client’s ad budget was BDT 45,000 per month; a 12 % drop meant roughly BDT 5,400 vanished overnight. I had to act fast, but I also needed a repeatable way to catch these alerts before they turned into lost sales. My first instinct was to fire off a manual Lighthouse run, copy‑paste the results into a Google Sheet, and send a cold email with a PDF report. It took me 45 minutes per site and still missed half the pages that were actually slow. That night I fell asleep with a half‑written...

The Hidden Gap Between FATF Recommendations and Bangladesh BFIU Rules: How I Uncovered a 12‑Million‑BDT Blind Spot

Image
AI-generated illustration It was 02:13 am. My phone buzzed. An alert from the in‑house monitoring dashboard lit up the screen: BDT 12,450,000 moved from a Nagad wallet to a newly‑opened corporate account in under three minutes. No SAR had been filed. My heart pounded. The same pattern had slipped past the BFIU’s 100 k BDT threshold rule three weeks earlier, and the audit team was breathing down my neck. The Hidden Problem: Why Standard FATF‑Based Controls Miss the Mark in Bangladesh We all love the FATF Recommendations. They’re the global bible, 40 pages of best‑practice prose. In theory you copy‑paste them, you’re compliant. In reality, Bangladesh’s BFIU guidelines are a different beast. They cherry‑pick clauses, add local thresholds, and sprinkle vague language about “reasonable suspicion.” The result? A compliance framework that looks solid on paper but leaks cash like a busted pipe. Two big mismatches keep showing up: Threshold vs. Pattern: FATF’s Recommendation 10 tells you to ...

The Day My Velocity Rule Stopped a BDT 80 Million MFS Scam – A Step‑by‑Step Build

Image
Photo by Luka Savcic on Unsplash High‑Stakes Hook It was 02:17 AM on a humid Thursday. My phone buzzed – an alert from the SAR queue that read: "Potential structuring: 45 transactions, BDT 1.8 million each, 30‑minute window, Nagad wallet #987654321" . My stomach dropped. The pattern matched a known structuring play, but the volume was off the charts – 45 × BDT 1.8 million = BDT 81 million in under half an hour. Within minutes the compliance lead was on the line, the regulator’s hotline was lit, and the senior manager asked, “Can we stop this before the next batch hits?” I stared at the dashboard, the numbers flashing like a warning light on a motorcycle. The existing rule‑set had missed similar bursts three weeks earlier, and the audit team was already circling, citing BFIU’s Section 9.2 – Velocity Monitoring as a gap. The Hidden Problem Most MFS firms in Bangladesh rely on static thresholds: “Flag anything over BDT 100,000 in a day.” It works for lone‑off spikes, but it co...

Why My First Cache‑First PWA Crashed on 4G and the 9‑Step Fix I Built for Dhaka Sellers

Image
AI-generated illustration 🚌 Try it yourself — Bus Fare Calculator BD This case study is based on a real, live product. Check it out below. Get Bus Fare Calculator BD → It was 9 pm on a rainy Tuesday. My client, a tiny apparel shop on Daraz, sent a panicked screenshot: the “Add to Cart” button never responded for users on 3G. Their conversion rate dropped from 4.2% to 1.1% overnight. I stared at the service‑worker console, heart thudding. The site was a brand‑new PWA that I had set to cache‑first for everything – HTML, CSS, images, even API calls. My gut told me the strategy was sound, but the numbers screamed otherwise. The Hidden Problem Most Bangladeshi freelancers ship a cache‑first manifest because it looks safe. “Everything is cached, the user never sees a network hiccup,” we tell ourselves. The reality? Rural users on 3G/4G have tiny data caps and intermittent latency. When the service worker grabs a huge bundle (2 MB of fonts, 1.5 MB of product JSON) and tries to serve ...

Why Most AML Teams Drown in False Positives – The 9‑Step Rescue I Built After a BDT 8 Million Alert

Image
AI-generated illustration High‑Stakes Hook It was 02:17 AM on a rainy Thursday in Dhaka. My phone buzzed – a senior manager from the compliance desk shouted, “We’ve got a BDT 8 million structuring alert on the MFS feed!” I ran to my laptop, opened the SAR queue, and saw 1,342 rows of red‑flagged transactions, all tagged “potential structuring.” The team was already on overtime; the regulator was breathing down our necks. Within minutes the whole AML desk was buried under a mountain of noise. No one could tell which line, if any, was the real threat. That night taught me a painful truth: false positives are not just annoying alerts – they are productivity assassins. They steal analyst hours, inflate audit costs, and, worst of all, mask the one true signal that could save the bank from a $10 million fine. The Hidden Problem: Why Standard Rules Fail in Bangladesh Most banks and fintechs in Bangladesh still rely on the classic “threshold‑plus‑velocity” rule set that the BFIU recommended ba...

Why Most Rule‑Based AML Alerts Miss Bangladesh’s Biggest Structuring Rings – My 12‑Step ML‑Hybrid Fix

Image
AI-generated illustration High‑Stakes Hook It was 02:13 am on a humid Tuesday. My dashboard lit up with BDT 27 million of inbound MFS transfers all flagged as ‘low‑risk’. The BFIU audit team was on the phone, demanding a justification before the next morning’s regulator‑roundtable. My heart raced. I knew the rule‑set that raised the alert was a three‑day velocity check on accounts crossing BDT 100,000. It had missed the elephant in the room – a layered structuring ring using bKash and Nagad wallets, each transaction just under the threshold, hopping across five accounts before landing in a shell company. I had 45 minutes to prove the system could catch it. The Hidden Problem Bangladesh’s AML ecosystem leans heavily on static thresholds and simple rule chains. The BFIU guidelines still cite “ any transaction exceeding BDT 100,000 in a single day must be reported ”. In practice, most banks and MFS providers translate that into a handful of SQL WHERE clauses. The result? Rule‑fatigue ....

Why Most Real‑Time MFS Dashboards Miss the Biggest Fraud Rings – My 9‑Step Fix

Image
AI-generated illustration High‑Stakes Hook I was staring at a blinking red line on our monitoring console at 02:13 AM. The alert said: BDTU 12 million structured across 4,217 Nagad wallets in 48 hours . My heart raced. The batch job that should have caught it two days ago was still processing 10 million rows. The regulator’s phone was about to ring. The Hidden Problem In Bangladesh, most MFS teams still rely on nightly batch jobs. They dump every transaction into a Hadoop lake, run a velocity check at 02:00 AM, and hope the BFIU’s 100,000 BDT threshold rule will catch anything. In practice, the lag creates a blind spot where structuring rings slip through, SARs pile up, and auditors point fingers. Why does it happen? Batch windows are too long – 24 hours of data is a lot to scan. Rules are static – they don’t adapt to new patterns like “burst‑and‑hide”. Alert fatigue – analysts drown in 300+ low‑value hits per day. Technical Breakdown & Logic Flow I decided to scrap the nightly bat...