Zing Forum

Reading

MLOps in Practice: Building a Scalable Multi-Class Financial Fraud Detection System

A financial fraud detection project based on modern MLOps practices, using multi-class classification to handle transaction risks, integrating DVC version control, SMOTE sampling, and XGBoost model, achieving an ROC-AUC of 0.96 on a synthetic credit card dataset.

MLOpsfraud detectionXGBoostSMOTEDVCfinancial riskmulti-class classificationSHAPcredit card fraud
Published 2026-05-19 06:44Recent activity 2026-05-19 06:49Estimated read 5 min
MLOps in Practice: Building a Scalable Multi-Class Financial Fraud Detection System
1

Section 01

[Introduction] MLOps in Practice: Key Points of Building a Scalable Multi-Class Financial Fraud Detection System

This project is a financial fraud detection project based on modern MLOps practices. It uses multi-class classification to categorize transactions into four risk levels (TT: Completely Normal, TF: Suspicious but Normal, FT: Low-Impact Fraud, FF: High-Impact Fraud). It integrates DVC version control, SMOTE sampling, and XGBoost model, achieving an ROC-AUC of 0.96 on a synthetic credit card dataset, providing financial institutions with more refined risk assessment capabilities.

2

Section 02

Project Background and Motivation: Addressing Core Challenges in Financial Fraud Detection

Financial fraud detection faces the problem of extremely imbalanced data (fraud accounts for only about 1%). Traditional binary classification methods lose risk gradient information and cannot distinguish transactions of different impact levels. This project is led by a graduate student team from DePaul University, aiming to build a reproducible and scalable MLOps workflow for fine-grained risk stratification of transactions, using a synthetic credit card transaction dataset with 43 features.

3

Section 03

Technical Architecture and MLOps Practices: Modular Design and Key Components

The project adopts a modular src architecture, with core components including:

  1. Data Engineering: Preprocessing pipeline (category encoding, train-test split), behavioral feature engineering (rolling window statistics, geographic distance, time features, etc.);
  2. Model Training: Comparing Logistic Regression, Random Forest, LightGBM, XGBoost, using SMOTE oversampling (strategy 0.3) to handle imbalance;
  3. DVC Version Control: Managing data and model versions, models stored as joblib files, metadata recorded in JSON, large files stored in Google Drive remote repository.
4

Section 04

Model Evaluation and Interpretability: Performance and Compliance Support

Model evaluation uses metrics such as F1 score, ROC-AUC, PR curve, and TimeSeriesSplit cross-validation. XGBoost is optimal with an ROC-AUC of 0.9614, F1 score of 0.5829, and threshold of 0.60. SHAP is used to analyze feature importance, ensuring model interpretability and meeting financial compliance audit requirements.

5

Section 05

Current Status and Future Plans: Project Progress and Expansion Directions

Currently, the project is in the first phase, using 100,000 sampled data for experiments; future plans include expanding to the complete dataset, exploring ensemble models and real-time inference architecture. Automated testing and code checks have been established, and experimental results and model performance are versioned and recorded.

6

Section 06

Practical Insights: Key Experiences in Building Financial Fraud Detection Systems

The insights from the project include:

  1. Multi-class classification is better than binary classification, supporting precise business decisions;
  2. MLOps (DVC, modularization, automated testing) should be established early;
  3. Emphasize both interpretability and performance, SHAP tool improves transparency;
  4. Prevent data leakage, apply techniques like SMOTE in the correct order. This project provides a full-process reference for production-level systems.