AML Data with Python

AI-generated illustration High‑Stakes Hook It was 02:17 am on a rainy Tuesday. My phone buzzed – a senior manager from the BFIU had just emailed the SAR inbox with a subject line that read ‘URGENT: 1,237 new SARs – 0 hits’ . The numbers were screaming: 1,237 reports , each attached to a transaction under BDT 100,000, all flagged by our MFS velocity rule. The audit team was on standby, regulators were breathing down our necks, and our case‑management system was choking on the sheer volume. I stared at the dashboard, heart pounding. One false positive after another was drowning the real threats. If we didn’t act, the next audit would be a headline disaster. The Hidden Problem In Bangladesh, the BFIU mandates that any MFS transaction exceeding BDT 100,000 or exhibiting suspicious velocity must be reported within 24 hours. The guideline sounds simple, but the reality is a maze of noisy alerts. Most banks and fintechs treat the rule as a binary gate: if the threshold is crossed, dump a SAR....

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 → Bangladesh, 10 am. My phone buzzed. A frantic client from a small boutique in Gulshan shouted, “Our order‑processing bot stopped at BDT 1,200 and we’re losing sales!” I stared at the spreadsheet: 45 orders pending, each worth BDT 2,500. The bot was built with n8n, but a recent change in the payment‑gateway API broke it. I had to decide: rebuild in Python or patch n8n? The Hidden Problem Most SMEs Overlook Small businesses love “no‑code” tools. They promise speed, low cost, and the illusion of control. In Dhaka, where 3G still haunts the outskirts and data packs cost more than a cup of tea, that promise feels like a lifeline. Yet the hidden snag is maintenance blindness . When an API shifts, a visual node‑flow often hides the breaking point behind a purple circle. Most freelancers I know jump straight into the GUI, c...

AI-generated illustration High‑Stakes Hook It was 02:17 am on a humid Thursday in Dhaka. My phone buzzed—another alert from the BFIU’s real‑time watchlist. The flag read: Potential Trade‑Based Money Laundering (TBML) – BDT 12,000,000 . The transaction? A single export invoice from Chattogram to a shell company in the Maldives, declared value BDT 950 million, but the shipping manifest showed only 120 tons of jute. My heart raced. The senior manager on the call asked, “What did we miss?” I had to answer before the compliance window closed at midnight. The Hidden Problem Most of us in Bangladesh lean on the BFIU’s standard checklist: verify HS codes, match invoice amounts, cross‑check counterparties. It works for simple over‑/under‑invoicing, but TBML is a chameleon. Criminals layer trade documents, split shipments, and use “price‑adjustment” clauses that slip past a static rule set. In my first year I trusted a spreadsheet that only looked at price per unit . It never caught the Maldive...

AI-generated illustration Bangladesh, 02:13 AM. My phone buzzed. An urgent Slack ping from the senior AML lead: ‘We’ve just gotten a STR on a Rocket account moving BDT 12 million in 45 minutes. The flagger says it’s a false positive, but the pattern looks… off.’ I stared at the screen, heart thudding. The rule that should have caught this – our graph‑based network detector – had let it slip. All night, I was glued to the console, hunting the missing link that let a structuring ring slip through the cracks. The Hidden Problem: Why Classic Graph Rules Fail in Bangladeshi Fintech We all love the idea of a “graph” – nodes, edges, centrality scores. In theory, it should expose hidden rings: a cluster of accounts funneling money, a hub of agents, a spider‑web of transfers. In practice, three things break it in Bangladesh: Threshold noise. BFIU mandates monitoring every MFS transaction > BDT 100,000. That creates a dense graph of legitimate high‑value transfers – a fog that drowns the sig...

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 → My inbox pinged at 9:17 am. A Dhaka‑based graphic designer wrote, “I’m 3 days behind on invoices, clients are nagging, can you fix this today?” He’d been copy‑pasting rows from a CSV into a Google Sheet, then manually emailing PDFs. The total overdue amount? BDT 275,000. I grabbed a coffee, opened his Sheet, and saw the nightmare. The Hidden Problem: Freelancers Treat Invoicing Like an After‑thought Most indie freelancers treat invoicing like a chore, not a product. They use: Manual copy‑paste from time‑tracker to a spreadsheet. Ad‑hoc email drafts. Paper‑based receipts for the occasional client. Result? Missed due dates, duplicate invoices, and angry clients. In Bangladesh, where data plans cost about BDT 30 per GB, every extra email or re‑send burns both time and money. The real cost is hidden: lost trust, delayed...

Photo by Joshua Hoehne on Unsplash High‑Stakes Hook It was 02:17 AM on a humid Tuesday in Dhaka. My dashboard lit up with 312 alerts from the Rocket‑to‑Bank channel, all flagged for “suspicious rapid‑fire deposits.” The total amount? BDT 5,127,894 in the last 45 minutes. My heart raced. The BFIU audit deadline was two weeks away, and the compliance team was already buried under SAR filings. I grabbed a cold cup of tea, stared at the spike, and asked myself: Why are our existing rules blowing up like fireworks? The answer was staring back—our velocity thresholds were set to a blunt BDT 100,000 per hour, a number copied from a 2019 bank policy that never considered today’s MFS frenzy. The Hidden Problem In Bangladesh, Mobile Financial Services (MFS) have exploded. bKash alone processes over BDT 1 trillion daily. The BFIU guideline (Section 4.3) says any “unusual high‑frequency activity” above BDT 100,000 in a 24‑hour window must be reviewed. Most fintechs treat that as a static ceiling...

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 → My inbox pinged at 9:17 am on a rainy Thursday. A small boutique in Old Dhaka wrote: “Our site loads in 12 seconds on 3G, sales dropped 30% last month. Can you help?” I was still sipping chai, half‑asleep, and the numbers hit me like a brick. 12 seconds? That’s longer than most people wait for a bus. I pulled up the PageSpeed Insights report – LCP 9.8 s, Total Blocking Time 4 s, and a Lighthouse score of 42. The client had a WordPress theme that hadn’t been touched in three years, a handful of plugins, and a CDN that was basically a glorified static file host. The Hidden Problem: WordPress + Bad Assets ≠ Speed Most indie businesses in Bangladesh think “just install a caching plugin and we’re good”. They ignore three brutal facts: Most visitors are on 3G/4G with data caps – every extra kilobyte costs them. WordPress ...

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 → My phone buzzed at 6 am. The client – a two‑person food‑delivery startup in Banani – had just received a 4‑star rating on Google Play, but the real problem was hidden in the analytics dashboard: 8‑second page loads on 3G , a 45 % bounce rate, and a $1,200 daily revenue dip. Why Most Freelancers Miss the Real Caching Question We all love the buzzword offline‑first . We read it on the MDN docs, we brag about it in Upwork proposals, and we sprinkle it into cold‑email pitches. But the default Service Worker template that the CLI hands you is a blunt instrument. It forces a network‑first strategy on every request, assuming the network is always faster. In Bangladesh, that assumption is a lie. My first attempt was to stick the boilerplate in, hope for the best, and move on to the next gig. The result? The PWA still waite...

Photo by shahin khalaji on Unsplash 🚌 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 I was staring at my inbox on a rainy Saturday in Gulshan, coffee cooling beside my laptop, when the reply pinged. "We love your numbers, but can you guarantee a 90 % Lighthouse score?" The client was a boutique tea shop in Old Dhaka, selling hand‑rolled blends on a clunky WordPress theme. Their page load was 5.6 seconds on 3G, and the Lighthouse Performance tab screamed 38 / 100. I replied with a cold‑email that quoted a $1,200 fix, promising a perfect score in two weeks. They said yes. Two weeks later, the site still loaded slower than a rickshaw on a pothole‑filled road, and the client’s sales dip was 12 %. That $1,200 turned into a $0 win and a bruised reputation. The Hidden Problem Most freelancers treat Lighthouse like a badge‑collector’s trophy. They chase the perfect 100, slap...

Photo by Peo Hedin on Unsplash 🚌 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 I was staring at my inbox on a rainy Tuesday in Gulshan. One cold‑email reply. BDT 1,200 earned. The subject line? “Your site’s Lighthouse score is 42 % – let’s fix it.” The prospect? A boutique clothing shop on Daraz with a 3‑page static site, hosted on a cheap shared server. Their bounce rate was 78 %, cart abandonment 85 %. I replied, attached a PDF, and waited. Two days later, the owner called. He’d seen the report, was terrified of losing traffic, and asked for a quick fix. I quoted BDT 1,200 for a “quick win”. He said yes. I delivered a PWA‑style service worker, compressed images, and a 1.2 s improvement. The shop’s traffic spiked 27 % in a week. That’s the story that started this deep dive. The Hidden Problem Most freelancers treat Lighthouse scores like a vanity metric. They copy‑past...

AI-generated illustration Bangladesh, 09/28/2026. My phone buzzed at 02:17 am. An alert from our real‑time MFS monitor flashed: BDT 3,245,876 moved across three Rocket accounts in 12 minutes, all under the BFIU’s BDT 100,000 threshold. My gut screamed – this was a structuring ring about to explode. I fired up the back‑testing suite we’d built two years ago, expecting a clean hit list. The report came back empty. Zero alerts. My heart sank. Two weeks later, the regulator knocked. A formal audit discovered that our back‑testing methodology was blind to exactly the pattern we’d just seen. The BFIU cited us for “inadequate validation of detection logic.” I was forced to shut down the alert engine for a week while we rewrote the whole thing. The Hidden Problem: Why Most Bangladeshi Backtests Miss the Real Threat Everyone tells you to “split your data 70/30, train on the past, test on the future.” Sounds neat. In reality, our local MFS landscape throws that rule out the window. Transaction ...