#Fraud Detection

Articles about Fraud Detection — exploring patterns, best practices, and real-world implementations in production systems.

8 posts tagged with fraud detection. ← Blog home

#A/B Testing (3)#A2A (14)#ADK (8)#AG-UI (6)#AI (9)#AI Adoption (9)#AI Agents (355)#AI Architecture (22)#AI Cost (10)#AI Cost Optimization (8)#AI Engineering (316)#AI Evaluation (9)#AI Financial Engineering (14)#AI Gateway (8)#AI Governance (43)#AI Red Teaming (9)#AI Research (17)#AI Safety (12)#AI Security (35)#AI Strategy (8)#AI in Production (12)#AML (3)#API Design (17)#API Security (9)#APIs (69)#AWS (17)#Accountability (8)#Accounting (9)#Agent Memory (8)#Agent Skills (11)#Agentic AI (25)#Agentic Commerce (12)#Agentic Engineering (12)#Agentic RAG (8)#Agents (4)#Amazon Bedrock (8)#Analytics (3)#Architecture (45)#Attention (3)#Audit (4)#Authentication (11)#Authorization (3)#Automation (13)#Azure (11)#Azure AI Foundry (9)#Backend Engineering (322)#Benchmarks (3)#Best Practices (5)#BigQuery (6)#Billing (8)#Build Systems (4)#Business Finance (8)#Business Strategy (55)#C (8)#CI/CD (23)#Caching (11)#Capital Markets (14)#Card Payments (12)#Cards (13)#Career (30)#Causal Inference (8)#Cellular Automata (8)#Change Management (3)#Checkpointing (4)#Claude Code (8)#Cloud (5)#Cloud Architecture (3)#Cloud Native (10)#Code Review (9)#Coding Agents (20)#Collaboration (6)#Communication (9)#Complexity (8)#Compliance (54)#Computer Networking (9)#Computer Science (40)#Computer Vision (15)#Computer-Use Agents (8)#Concurrency (42)#Consulting (26)#Containers (10)#Context Engineering (19)#Conversational AI (8)#Cost Optimisation (5)#Cost Optimization (3)#Credit (16)#Credit Risk (16)#CrewAI (8)#Crypto (12)#Cryptocurrency (12)#Cryptography (9)#Custody (9)#DSPy (8)#Data (14)#Data Engineering (25)#Data Governance (3)#Data Science (8)#Data Structures (10)#Databases (48)#Deep Learning (20)#Deployment (5)#Design (3)#Design Patterns (10)#DevOps (24)#DevSecOps (22)#Developer Experience (7)#Developer Productivity (15)#Developer Tools (5)#Differential Privacy (3)#Diffusion Models (10)#Discovery (5)#Distributed Systems (104)#Documentation (3)#Edge AI (8)#Embeddings (21)#Emotional Intelligence (8)#Energy (8)#Engineering (14)#Engineering Culture (3)#Engineering Judgment (7)#Engineering Practices (21)#Enterprise AI (8)#Error Handling (4)#Evaluation (79)#Event-Driven (9)#Event-Driven Architecture (8)#Explainability (3)#Explainable AI (8)#FREE-AI (8)#FX (5)#Feature Engineering (3)#Feature Flags (3)#Feedback (4)#FinOps (23)#FinTech (6)#Financial AI (14)#Financial Engineering (8)#Financial Systems (133)#Fine-Tuning (12)#Fintech (134)#Flutter (8)#Forecasting (10)#Foreign Exchange (5)#Forward Deployed Engineer (43)#Forward Deployed Engineering (8)#Fraud (10)#Fraud Detection (8)#Function Tools (5)#Functional Programming (3)#Fundamentals (23)#Fundraising (8)#GCP (5)#GPU (8)#GUI Automation (8)#Gemma (4)#Generative AI (13)#Git (8)#Go (232)#Go-to-Market (31)#Google ADK (36)#Governance (61)#Granite (6)#Graph Neural Networks (8)#GraphQL (3)#Growth (3)#Guardrails (35)#HIPAA (3)#HTTP (3)#Harness Engineering (8)#Hiring (9)#Hugging Face (8)#Human-in-the-Loop (10)#IBM watsonx (8)#Idempotency (3)#Identity (11)#Image Generation (10)#Inference (8)#Information Retrieval (8)#Integration (3)#Integrations (8)#Intellectual Property (8)#Interfaces (3)#Interpretability (8)#JavaScript (8)#KYC (11)#KYC and AML (12)#Kafka (11)#Knowledge Graphs (11)#Kubernetes (17)#LLM (5)#LLM Inference (8)#LLM Infrastructure (8)#LLM-as-Judge (3)#LLMOps (9)#LLMs (197)#LangChain (8)#LangGraph (11)#Leadership (33)#Ledger (12)#Legal (8)#Lending (14)#Linux (9)#LlamaIndex (8)#Load Balancing (3)#MCP (25)#MLOps (39)#Machine Learning (119)#Marketing (16)#Markets (4)#Mathematical Finance (8)#Memory (16)#Memory Management (5)#Metrics (7)#Microservices (3)#Microsoft Agent Framework (150)#Middleware (6)#Migration (9)#Migrations (8)#Mixture of Experts (5)#Model Risk (3)#Monetization (9)#Monitoring (5)#Monorepo (3)#Multi-Agent (10)#Multi-Agent AI (14)#Multi-Agent Systems (76)#Multimodal (3)#Multimodal AI (11)#NIM (5)#NVIDIA (8)#Networking (3)#OAuth (3)#OWASP (7)#Observability (53)#On-Device AI (8)#Ontology (8)#Open Source (7)#OpenAPI (3)#OpenTelemetry (5)#Operating Systems (9)#Operations (14)#Opinion (6)#Orchestration (10)#Organizational Design (8)#Payment Rails (16)#Payments (55)#People (8)#Performance (56)#Personalization (9)#Platform Engineering (17)#Policy as Code (3)#PreSales (8)#Pricing (4)#Privacy (14)#Privacy Engineering (3)#Process (4)#Product (30)#Product Management (9)#Production (22)#Programming (10)#Programming Languages (48)#Prompt Engineering (86)#Prompt Injection (16)#Proof of Concept (3)#Protocol Buffers (3)#Protocols (9)#Providers (4)#Pydantic AI (8)#Python (142)#Quality (3)#Quantitative Finance (22)#RAG (72)#RBI (3)#REST (5)#Rails (16)#Real-Time (8)#Reasoning Models (8)#Recommender Systems (8)#Reconciliation (5)#RegTech (8)#Regulation (10)#Reinforcement Learning (9)#Reliability (68)#Resilience (4)#Responsible AI (5)#Retrieval (3)#Risk (22)#Risk Management (11)#Rust (32)#SLSA (3)#SRE (23)#SaaS (9)#Sales (9)#Sales Engineering (8)#Scalability (6)#Search (10)#Security (103)#Security Engineering (8)#Self-Evolving Agents (24)#Semantic Web (8)#Sessions (3)#Settlement (9)#Soft Skills (8)#Software (3)#Software Architecture (36)#Software Delivery (9)#Software Engineering (152)#Spanner (4)#Specification Engineering (3)#Speech (8)#Startups (30)#Statistics (8)#Strands (8)#Strategy (6)#Stream Processing (9)#Streaming (38)#Structured Output (4)#Supply Chain Security (10)#Sustainability (9)#System Design (32)#Systems Programming (56)#Technical Sales (6)#Testing (79)#Threat Modeling (3)#Time Series (9)#Tool Use (23)#Tooling (11)#Tools (4)#Trading (8)#Transformers (3)#Treasury (6)#Trust (4)#Type System (3)#Type Systems (12)#TypeScript (8)#Validation (3)#Valuation (3)#Vector Databases (23)#Vector Search (12)#Venture Capital (8)#Version Control (9)#Versioning (7)#Voice AI (9)#Web Development (6)#Webhooks (9)#Workflow (4)#Workflows (14)#eBPF (8)#gRPC (13)#smolagents (8)
Pratik Dhanave · ·4 min read

Risk in Production — Latency Budgets, Explainability, and Proving You Prevented Anything

The last mile of a fraud system is operational: score inside the authorization window without becoming the payment path's weakest dependency, explain decisions to customers, auditors, and your own reviewers, and answer the question every budget cycle asks — how much fraud did all this actually prevent, given that prevented fraud is precisely the thing that didn't happen? This closing post is the production discipline that makes the whole stack deployable, defensible, and fundable.

Production risk: the money-path budget (precomputed features, staged degradation, decisions stamped with full configuration), explainability as three products (reviewers, customers and regulators, governance with disparity monitoring), and prevention measured against counterfactuals — holdout slices, an estimated ledger, loss-rate SLOs. Closes the series.

#Fraud Detection#MLOps#Explainability#Risk#Machine Learning
Pratik Dhanave · ·4 min read

Humans in the Loop — Review Queues, Friction Ladders, and the Third Answer

The best fraud decision is often neither yes nor no but "prove it" — a verification step that fraudsters abandon and legitimate customers clear in seconds. And for the genuinely ambiguous rest, trained human reviewers remain the highest-precision classifier available, at a unit cost that makes their deployment an optimization problem. This post builds the human layer: friction as a decision outcome, review queues as both safety valve and labeling engine, and the operations that keep both honest.

Friction separates by behavior — fraudsters abandon challenges, customers clear them — priced by abandonment and bent by 3DS liability shift. Review queues run as operations: capacity-driven routing, value-tiered SLAs, reviewers measured like models — and a declared capacity split for the queue's second job: labeling.

#Fraud Detection#Human-in-the-Loop#Operations#Risk#Machine Learning
Pratik Dhanave · ·4 min read

Drift and Adaptation — Defending Against an Adversary Who Read Your Model

Ordinary ML drift is weather — the world changes and models age. Fraud drift is war — the distribution shifts precisely because you deployed, as attackers probe the new boundary and route around it. A fraud system's long-run performance is therefore determined less by any single model than by its adaptation loop: how fast drift is detected, how fast a response ships, and how safely the response is validated against labels that haven't arrived yet. This post builds that loop.

Against an adapting adversary the system is the loop: detection cascaded by speed (input drift, score drift, proxy labels, chargeback truth), responses laddered by cost (expiring tactical rules in minutes, threshold posture, cadence-plus-trigger retrains, shadow challengers), validation staged around label delay.

#Fraud Detection#Concept Drift#MLOps#Machine Learning#Risk
Pratik Dhanave · ·4 min read

The Label Problem — Delay, Noise, and the Data Your Own Decisions Hide

Supervised learning assumes someone hands you the truth. In fraud, the truth arrives 30 to 90 days late, labeled by processes with their own agendas, for only the transactions you approved — and silence means nothing, because unreported fraud and un-disputed legitimate purchases are indistinguishable until they aren't. Label engineering is the least glamorous layer of a fraud system and the one that decides whether everything upstream learns reality or a convenient fiction.

Labels are an engineered pipeline: maturity horizons (recent silence is not legitimacy), labels as versioned state trajectories, early proxies weighted then reconciled; noise handled by provenance; and censoring confronted with bought data — bounded exploration of would-be declines booked as data acquisition cost.

#Fraud Detection#Machine Learning#Data Engineering#Risk
Pratik Dhanave · ·4 min read

Scoring, Thresholds, and the Cost of Errors — Where ML Meets the P&L

A fraud model outputs a probability; the business needs a decision; and the line between them — the threshold — is where machine learning stops and economics begins. Set it by gut and you've made your most consequential business decision by vibes. This post builds the machinery that makes the error trade-off explicit: metrics that survive extreme imbalance, calibration that makes scores mean something, and thresholds derived from costs rather than from tradition.

At 0.1% base rates ROC-AUC flatters; use precision at review capacity and recall at FP budget on time-split, segmented data. Calibration makes scores probabilities; thresholds become cost derivations that move with amount and segment, extended into a ladder across approve, friction, review, and decline.

#Fraud Detection#Machine Learning#Decision Science#Risk
Pratik Dhanave · ·4 min read

Features and Feature Stores — Where Fraud ML Is Actually Won

Ask practitioners where fraud detection quality comes from and the answer is uniform: not the model — the features. Velocities, histories, graph signals, and their freshness carry the signal; the model just reads it. And ask where production fraud ML fails and the answer is equally uniform: the gap between how features were computed in training and how they're computed at serving time. This post covers both — the feature families that catch fraud, and the feature-store discipline that keeps them honest.

Signal lives in velocities (second-fresh streaming aggregates), histories, precomputed graph neighborhoods, and composed scores. The characteristic failure is training/serving skew — feature time-travel leaking the future into training. The feature store fixes it by construction: one event-time definition, two materializations.

#Fraud Detection#Feature Stores#ML Infrastructure#Machine Learning#Risk#Streaming
Pratik Dhanave · ·4 min read

Rules and Models — Why Fraud Systems Need Both

Every few years someone declares rules dead — just let the model learn everything — and every production fraud team quietly keeps both, because rules and models are good at different, complementary things: rules deploy in minutes against the attack happening right now, encode hard policy exactly, and explain themselves completely; models find the subtle multidimensional patterns no human would write down. The engineering question isn't which — it's how the two compose into one decision.

Rules deploy in minutes against live attacks, encode policy exactly, explain themselves completely, and hold the blind spots; models (GBDTs as the tabular workhorse) own the unstateable patterns. Composition makes them one decision: policy first, scores next, cost-thresholded logic last — versioned and golden-tested.

#Fraud Detection#Rules Engines#Machine Learning#Risk
Pratik Dhanave · ·4 min read

The Fraud Problem — Adversarial, Asymmetric, and Allergic to Textbook ML

Fraud detection looks like a classification problem and behaves like nothing else in machine learning: the adversary adapts to your model, the classes are wildly imbalanced, the labels arrive months late, your own decisions censor the data you learn from, and both kinds of error cost real money in different currencies. This series builds fraud and risk systems from first principles — and this opening post is about why the textbook assumptions fail, because every architecture decision downstream flows from these five inversions.

Fraud inverts the textbook five ways: an adversary that adapts to your model, tiny base rates with asymmetric error currencies, labels that arrive months late and partly wrong, decisions that censor their own training data, and a milliseconds budget in the payment path. The answer is a decision system, not a classifier. Opens the series.

#Fraud Detection#Machine Learning#Risk#Fintech#Financial Systems

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 the blog or explore related topics using the tag cloud above.