AML Data with Python

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 a rainy Thursday in Gulshan. My inbox pinged – a reply from a boutique textile shop in Mirpur that had just read my cold‑email. They’d looked at the Lighthouse report I’d attached, saw a 55 % performance score, and asked: ‘Can you fix this? We’re losing customers.’ I replied, "Sure, let’s chat," and booked a Zoom call for 3 PM. Fast forward two weeks: the shop’s PWA now scores 92 % on performance, 97 % on accessibility, and their sales jumped 18 %. The client paid BDT 45,000 – a tidy win for a solo freelancer. The Hidden Problem: Why Most Lighthouse Cold‑Emails Crash and Burn Most freelancers copy‑paste a generic Lighthouse link, write a one‑liner, and hit send. They assume the score alone will close the deal. Reality check: a 55 % score is a red flag, not a selling point. It tells the business they’re ...

🚌 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 → AI-generated illustration Real‑World Hook It was a rainy Tuesday in Gulshan. I stared at my laptop, coffee cooling, and saw a new notification: "You have a new lead!" The lead was a small boutique bakery, “Sweet Crumbs”, that’d just posted a Lighthouse report with a 62 Performance score. Their owner, Rafiq, was desperate—sales had dipped 12% since the last month, and his site was loading in 6 seconds on a 3G dongle. I drafted a cold email, slapped the Lighthouse score in the subject line, and hit send. No reply. After three more attempts, I realized I’d burned $1,200 of my own ad‑budget chasing a dead‑end. The Hidden Problem Most freelancers think a Lighthouse number is a magic bullet. “Your site scores 45, hire me!” sounds persuasive, but the reality in Bangladesh is messier. Local SMEs juggle: Spotty 3G/4G coverage tha...

🚌 Try it yourself — Bus Fare Calculator BD The app from this case study is live and free on the Microsoft Store. Check real fares and distances between any two points in Bangladesh. Get Bus Fare Calculator BD → AI-generated illustration My phone buzzed at 2 am. A client in Chittagong—owner of a tiny bus ticket kiosk—had just sent a screenshot of his PWA crashing on a 3G phone. The error: Service worker failed to fetch . He was losing 12 % of daily riders because the app wouldn’t load on the cheapest data plan. I had promised a fast, offline‑first fare lookup that would survive Dhaka’s 3G black spots. I was staring at a deadline, a frustrated client, and a pile of assumptions that I’d never questioned. The Hidden Problem Most Indie Developers Overlook Everyone talks about “offline‑first” as a buzzword. The reality in Bangladesh is far harsher: average 3G latency hovers around 2.8 seconds, data caps cost BDT 15 per gigabyte, and many commuters share a single 4G hotspot...

Photo by Mark Chan on Unsplash High‑Stakes Hook It was 02:13 am on a rainy Thursday. The BFIU inbox pinged, a SAR arrived, and the numbers screamed: BDT 4.2 million moved through three Rocket accounts in under five minutes, each just under the BDT 100,000 threshold. My team’s alert list was a sea of noise—1,200 warnings per hour, most of them false. The system timed out, the dashboard froze, and senior management started asking, “Did we miss a structuring ring?” I stared at a blinking red line on a Grafana panel and felt the weight of an audit looming. The Hidden Problem Standard batch‑oriented monitoring works in banks that process a few thousand wires a day. In Bangladesh’s mobile‑financial‑services (MFS) world, transaction velocity is a different beast. bKash, Nagad, Rocket—all push millions of micro‑payments per hour. The BFIU guideline Rule 3.2.1 tells us to watch any series of transactions that cumulatively cross BDT 100,000 within a 24‑hour window, but it does not prescribe ...

AI-generated illustration Bangladesh, 3 AM. My phone buzzed. The alert read: PEP match – BDT 12.4 million inbound transfer to a new corporate account. My supervisor’s voice crackled on the speaker: ‘We’ve got 30 minutes before the regulator’s audit team walks in. Explain this.’ My heart hammered. I stared at the transaction log – a single wire from a shell company in Chittagong, linked to a name that showed up in the BFIU’s “high‑risk PEP” list last year. The red flag was real, but the system had thrown *dozens* of similar alerts that turned out to be harmless relatives of the same politician. The audit team would see a mountain of false positives and wonder why we couldn’t separate wheat from chaff. The Hidden Problem: Bangladeshi PEP Data Isn’t Ready for Plug‑and‑Play Most off‑the‑shelf screening engines assume three things: Names are clean, Latin‑script, and consistently formatted. Sanctions lists are static, updated monthly. Local AML teams have a single, unified risk‑score thresh...

AI-generated illustration Bangladesh, 09/23/2026. My phone buzzed at 02:17 AM. The AML dashboard at bKash lit up with a red fire‑alarm: 5,432 alerts in the last 30 minutes. The system was choking. Our false‑positive rate had spiked from 12% to a staggering 68% overnight. I stared at the numbers, heart pounding, wondering if the BFIU audit deadline next week would turn into a nightmare. The Hidden Problem: Synthetic Test Data Isn’t Synthetic Enough We had built a tiny test harness months ago – a handful of hard‑coded CSV rows that mimicked a few typical MFS transfers. It was enough to convince the team that the rule set was solid. But when the regulator demanded a stress‑test of the entire rule engine, the harness fell apart. It didn’t cover: Cross‑border remittance patterns that bounce between Rocket, Nagad, and local banks Layered structuring attempts just under the BDT 100,000 threshold Entity‑resolution edge cases where a single phone number appears on three different accounts In ...

AI-generated illustration Bangladesh, 02:17 am. My phone buzzed. An email from BFIU: ‘Immediate audit – 150 flagged transactions pending review’ . My team’s sanctions screen had just exploded with false positives – 1,200 alerts for a $5 million daily volume. The regulator was breathing down our necks, senior management was threatening budget cuts, and I could hear the coffee machine sputtering in the background. I was staring at a dashboard that looked like a fireworks show. That night, I realized we’d built the wrong kind of filter. The Hidden Problem Behind the Noise Most banks in Bangladesh start with a “plug‑and‑play” sanctions list from the UN and OFAC, then sprinkle a few country‑code checks. It sounds sensible until you factor in three local quirks: Bangladeshi Mobile Financial Services (MFS) push billions through BDT 100,000 thresholds, but the BFIU only requires detailed SARs for transactions above BDT 5 million . Names are often transliterated from Bangla to Latin script, pr...

AI-generated illustration The Moment the Dashboard Went Red It was 09:15 on a humid Tuesday. My phone buzzed, the AML console lit up with 1,245 alerts in under a minute. The spike wasn’t random – the total flagged amount topped BDT 12 million, most of it clustered around a single merchant ID that processed 3,800 micro‑payments in the last 24 hours. My team stared, coffee gone cold, and the compliance manager whispered, “We’re about to get a BFIU audit tomorrow.” The room fell silent. That was the hook that pulled me out of my chair and into a frantic sprint to understand why the model we’d just deployed was blowing up our false‑positive budget. The Hidden Problem Behind the Numbers Most AML models I’ve seen in Bangladesh start with a textbook approach: train a gradient‑boosted tree on historic SARs, add a few rule‑based thresholds (BDT 100,000 MFS limit, high‑risk country flag), and call it a day. The reality is messier. Our fintech’s user base is 65 % unbanked, transaction velocity sp...

AI-generated illustration Real‑World Hook It was a rainy Thursday in Gulshan. My inbox pinged: "Need a PWA for my boutique, budget BDT 30,000, deadline 2 weeks" . The client, a 28‑year‑old fashion retailer named Riya, showed me her Shopify store loading at 7 seconds on 3G. She’d lost roughly BDT 12,000 in sales last month because customers abandoned carts. I replied, "I can make it offline‑first, under 2 seconds, for BDT 30,000." I signed the contract on Upwork, sent the first invoice, and started building. The Hidden Problem Most freelancers think pricing is just a math exercise: hours × rate + buffer. I did the same. I estimated 80 hours, set my hourly rate at BDT 400, added a 10% contingency, and landed on BDT 35,200. I rounded down to BDT 30,000 to look tempting. What I missed was the hidden cost of post‑launch support and the reality of Bangladeshi data plans. Riya’s customers use 3G most of the day, paying BDT 30 per GB. A PWA that still pulls a 5 MB bundle e...

AI-generated illustration Bangladesh, 03:12 AM. The BFIU dashboard flashes a red line: a burst of 27 transactions, each just under the BDT 100,000 MFS threshold, moving between five Rocket agent accounts in 45 minutes. The total? BDT 3,027,842. My heart skips. The alarm that should have screamed never did. I was staring at a structuring ring that had slipped through the cracks of our rule‑based engine. The Hidden Problem: Why Classic Threshold Rules Fail in Dhaka We all start with the obvious: set a hard limit at BDT 100,000, flag anything above. Works for big jumps, but not for the slow, steady drip that smurfs money across multiple agents. In Bangladesh the BFIU Circular 15/2023 explicitly calls out “multiple low‑value transfers to a single beneficiary within a short window” as a red flag, yet most AML platforms still treat each transaction in isolation. My first attempt was a naïve count‑per‑hour rule. If an account sends more than three transactions over BDT 95,000 within an hour...

Photo by Ricardo Gomez Angel on Unsplash Real‑World Hook It was 9 am on a rainy Tuesday in Dhaka. My client, a tiny transport cooperative that runs 12 minibuses across Gulshan, sent a frantic WhatsApp voice note: “The fare‑lookup app you built just froze for half the riders. We lose at least 200 BDT per hour!” They’d just spent BDT 12,000 on a Google Play listing that never got any downloads because the app wouldn’t work on the 3G phones their commuters still use. I stared at the crash logs, the analytics, and my own coffee‑stained notebook. The numbers were clear: 75 % of sessions timed out after 8 seconds . The client’s revenue hit a dent of roughly BDT 9,000 a day. I had to turn this around before the next fare‑collection cycle. The Hidden Problem Most indie developers treat PWAs like glorified static sites. They sprinkle a service worker, slap an addToHomeScreen prompt, and call it a day. In Bangladesh, that shortcut is a recipe for disaster. Three realities bite hard: 3G is stil...