Source-linked AI summary

Topological Fraud Detection in Latent Transaction Spaces

Avraham Bourla

arXiv:2609.08445v1cs.LGcs.CR

TL;DR

The paper addresses fraud detection across institutional data silos under privacy and real-time latency constraints. It applies iterative filtering and classification to anonymized latent transaction representations. On the reported test split, the final model achieved 91.74% precision and 79.88% recall, with mean single-row prediction latency of 4.74 ms.

  • Problem

    Institutions face fragmented transaction data and privacy barriers, while privacy-enhancing approaches can have latency and communication overheads that challenge real-time fraud detection.

    Source: §1.1 · pp. 1–2
  • Method

    The pipeline combines topological projections and iterative unsupervised filtering with supervised classification of residual transactions in anonymized representations.

    Source: §2 · pp. 2–3, §3 · p. 4, §3.2 · p. 5
  • Results

    On the 10% test split, the final model achieved 91.74% precision, 79.88% recall, an F1 score of 0.8540, and mean single-row prediction latency of 4.74 ms.

    Source: §4 · p. 6
  • Takeaways & Limitations

    The authors conclude that the pipeline can identify fraud in anonymized latent spaces, while its efficacy across vendor datasets and temporal scales remains to be evaluated.

    Source: §4 · p. 7

    The approach rests on the hypothesis that fraudulent activity forms distinct, well-formed clusters in latent topological embedding spaces.

    Source: §1.2 · p. 2

Abstract

from arXiv · show

Working entirely on topologically anonymized embeddings, we perform fraud detection using iterative rounds of unsupervised filtering followed by supervised sniping. The result is an ultra-low latency privacy--preserving triage that allows institutions to flag suspicious activity without compromising Personally Identifiable Information.

1 Introduction

Fraud defenses face rising losses, institutional data silos, and privacy-preserving inference requirements that conflict with latency demands. The paper motivates a topological approach combining latent-space structure with tree-based classification and autoencoder filtering.

1.1 The Privacy Preserving Real Time Fraud Detection Challenge

  • Privacy and competitive barriers keep transaction data siloed, leaving institutions with fragmented datasets and limited shared intelligence for fraud detection.The paper frames privacy-preserving cross-institutional detection as a need that must also protect consumer confidentiality and competitive advantages.Source: §1.1 · p. 1
  • Cryptographic privacy methods can impose latency and communication overheads that miss the 1 ms target for real-time commerce.The passage contrasts FHE’s seconds-to-minutes latency with the sub-millisecond inference goal.Source: §1.1 · pp. 1–2
  • The paper connects privacy-preserving, low-latency inference with potential network-wide shielding and collaborative intelligence across institutions.It describes a flagged malicious pattern as a basis for shielding the network before a transaction reaches more computationally intensive institutional models.Source: §1.1 · pp. 1–2

1.2 Synergizing Topology with Tree-Based Models and Deep Learning

  • The proposed topology-based rationale is that fraud forms distinct clusters in latent spaces, while UMAP preserves structural nuances for visualization.The text also notes that anonymized datasets can be shared under current regulatory frameworks and that latent-space feature labels are irrelevant to the approach.Source: §1.2 · p. 2
  • Tree-based models are presented as suitable for fast tabular classification, while an autoencoder trained only on legitimate behavior captures its manifold for filtering.Reconstruction error is used to isolate legitimate signatures and distinguish benign behavioral shifts from adversarial anomalies under temporal concept drift.Source: §1.2 · p. 2

2 Methodological Prerequisites: EDA and Feature Engineering

The section uses the Kaggle anonymous credit-card dataset to inspect transaction structure and engineer amount-based features. Its exploratory observations motivate a log-amount feature and a synthetic amount signature.

2 Methodological Prerequisites: EDA and Feature Engineering

  • The Kaggle dataset contains actual European card transactions, with anonymized PCA features V1–V28 intended to preserve predictive structure while protecting privacy.The text characterizes the dataset as highly imbalanced and publicly available.Source: §2 · pp. 2–3
  • Figure 1’s exploratory analysis includes a scatterplot of two important PCA features, where most fraud transactions lie outside one dense cluster.The same exploration reports that the base-10 logarithm of amount has a rough normal distribution.Source: §2 · p. 3, Figure 1 · p. 3
  • The amount feature engineering adds a logarithmic z-score using the prospective mean and standard deviation.The section also maps each amount into a synthetic signature using its leading significant digit and cents, motivated by possible decimal-pattern divergence between fraud and benign transactions.Source: §2 · p. 3
  • An 85/5/10 stratified split is used to provide training data for the multiple iterations required for convergence.The authors state that the training-heavy split is intended to capture complex patterns in residuals.Source: §2 · p. 3

3 An Iterative Topological Sniping/Filtering Scheme

The scheme combines topological projections, unsupervised anomaly filtering, SOM-based removal of likely legitimate records, and supervised classification of residuals. Its AE-derived dimensions distinguish legitimate and fraudulent rows, and the pipeline uses separate models for safe removal and fraud flagging.

3 An Iterative Topological Sniping/Filtering Scheme

  • AE-derived dimensions distinguish the means and standard deviations of legitimate and fraudulent rows in the IEEE-CIS representation.The resulting dataframe has nine columns, including an amount signature, log amount, five UMAP dimensions, AE-centroid distance, and SOM quantization error.Source: §3 · pp. 3–4, Figure 2 · p. 4

3.1 Pre-sniping via Classical Anomaly Detection

  • Pre-sniping processes small batches while retaining only 50% of the least dense observations, then evaluates UMAP clusters and anomaly-flagged subsets.The scheme combines DBSCAN with Isolation Forest and Local Outlier Factor metrics, then uses GMM covariance eigenvalue ratios to score sub-cluster eccentricity.Source: §3.1 · pp. 4–5

3.2 Filtering using SOM Clusters

  • The SOM stage hard-removes high-confidence legitimate rows, using AE reconstruction error to mark hot and safe seed cells and nearest-prototype distance as another anomaly signal.Safe seeds can expand along a compactness-weighted frontier, with hot clusters acting as a guardrail.Source: §3.2 · p. 5
  • After safe rows are pruned, CatBoost classifies remaining candidates for soft removal using their latent SOM embeddings.The paper attributes its suitability to operation on anonymized latent features and fast inference with oblivious symmetric trees.Source: §3.2 · pp. 5–6

3.3 The Round Classifier

  • LightGBM flags fraud once per iteration after the SOM/CatBoost safe-removal chain and before the final filter pass.It is selected for fast inference and precision under the latency budget; leaf-wise tree growth is described as keeping the ensemble small.Source: §3.3 · p. 6

3 An Iterative Topological Sniping/Filtering Scheme

  • The pipeline’s round structure places fraud flagging after high-confidence legitimate records are removed and before the final filter pass.The section identifies the single-stage iterative scheme as the overall process.Source: §3 · p. 4, §3.3 · p. 6

4 Results and Conclusions

The final evaluation reports classification metrics and measured single-row latency, while the conclusion calls for broader validation across datasets and time. It also raises transfer to other high-stakes domains as an open question.

4 Results and Conclusions

  • 91.74% precision, 79.88% recall, and 0.8540 F1 were reported on the 10% test split.On an AMD Ryzen 7 3700U, mean single-row latency was 4.74 ms (P95 6.61 ms, P99 7.80 ms, P100 16.48 ms).Source: §4 · p. 6
  • The conclusion says the pipeline satisfies sub-millisecond latency constraints, while the reported mean latency is 4.74 ms and clearing 1 ms is projected for a compiled backend.The measured benchmark used a consumer-grade AMD Ryzen 7 3700U.Source: §4 · pp. 6–7
  • The evaluation uses C13 = 13 × FP + FN, weighting false positives to reflect the long-term customer-lifetime-value impact of erroneous declines.The authors state that changing the safe growth ratio can improve the C13 score, but provide no score comparison in this passage.Source: §4 · p. 6
  • The authors call for testing across vendor datasets and temporal scales, and pose adaptation to macroeconomics and clinical medicine as an open question.Source: §4 · p. 7
Loading 2609.08445v1…