Supervised Fraud Detection with Imbalanced Data
Why accuracy lies, how to train on a needle-in-a-haystack, and picking a threshold by the money it saves.
Fraud is a needle-in-a-haystack problem.
Articles about Risk — exploring patterns, best practices, and real-world implementations in production systems.
13 posts tagged with risk. ← All posts
Why accuracy lies, how to train on a needle-in-a-haystack, and picking a threshold by the money it saves.
Fraud is a needle-in-a-haystack problem.
A technically excellent model is worthless until it changes a number someone cares about. Here is how to design backward from that number.
Why technically excellent models never ship: no clear business metric, organizational buy-in, validation and model-risk sign-off, monitoring, and the prototype-to-production chasm.
Financial ML lives under regulators, adversaries, and money-denominated errors — so you design backward from a business metric, not forward from a model.
What sets financial ML apart from general ML: strict regulatory scrutiny and mandatory explainability, high-stakes and immediately quantifiable errors, messy multi-source data, non-stationarity, and adversarial actors.
How the two Basel liquidity ratios are computed from raw positions, and why the hard part is a data pipeline, not a formula.
How the Liquidity Coverage Ratio and Net Stable Funding Ratio are computed: HQLA classification, outflow factors, and the reporting pipeline.
How passive device and behavior signals become a trust score for auth and fraud — without turning into a surveillance liability.
How device signals and behavioral biometrics build a trust signal for auth and fraud, with privacy and false-positive trade-offs.
Turning geography, product, channel, and behavior into a single defensible number — and a due-diligence tier a regulator can follow.
Building a customer risk-rating model: risk factors, weighting, thresholds to due-diligence tiers, and explainability for regulators.
Why per-transaction scoring misses organized fraud, and how modeling accounts, devices, cards, addresses, and IPs as a graph catches the whole ring.
Modeling accounts/devices/payments as a graph, connected-component and community detection, shared-attribute linking, and analyst review.
Treating fraud, credit, and risk models as governed assets with a lifecycle, an inventory, and an audit trail regulators can actually read.
Development, independent validation, approval, monitoring, and retirement of risk/fraud/credit models under SR 11-7-style governance.
How to combine a deterministic rules engine with an ML risk model in a single decision: rule precedence, score bands, shadow mode, and champion/challenger evaluation with feedback labels.
Teaches how to combine a deterministic rules engine with an ML risk model in one decision path: rule-precedence and overrides, model score bands, shadow mode, and champion/challenger evaluation with feedback labels.
How a risk-driven layer escalates from silent approval to OTP, biometric, or 3DS challenge — holding a pending-challenge state and resuming the original transaction once the customer clears it.
Teaches how to build risk-based step-up auth: an orchestration layer that escalates from silent to OTP/biometric/3DS challenge based on risk signals, with pending-challenge state and resumable transaction context.
Building low-latency sliding-window counters, entity-keyed aggregates, and an online feature store that stays consistent with its batch-computed twin.
Teaches how to build low-latency velocity checks: sliding-window counters and aggregates in an online feature store, entity keys (card/device/IP), and consistency between real-time and batch-computed features.
When software holds the card and clicks "buy," the old questions — was this the cardholder, did they mean to, who pays if not — all get harder to answer.
The new fraud surface: prompt injection turning a shopping agent into an attacker's buyer, hijacked delegated credentials (Visa saw ~450% more dark-web 'AI Agent' chatter in H1 2026), and disputes when an agent acted on…
How a central counterparty turns a web of bilateral trades into a single, mutualized book of risk — and what your clearing systems must do to survive the margin cycle.
Novation to a central counterparty, initial vs variation margin, margin calls, and the default waterfall (margin, default fund, skin-in-the-game).
All posts on this site are written by Pratik Dhanave, an Agentic AI Architect with 7+ years building production distributed systems, multi-agent AI platforms, and cloud-native infrastructure. About the author → Each article includes working code, architecture diagrams, and references to the specific frameworks and standards discussed. Browse all posts or explore related topics using the tag cloud above.