PracHub
QuestionsPremiumLearningGuidesCheatsheetNEWCoaches
|Home/ML System Design/PayPal

Detect credit-card transaction fraud

Last updated: Mar 29, 2026

Quick Overview

This question evaluates a data scientist's competency in real-time fraud detection system design, including feature engineering, rule-based and model-based decisioning, unsupervised anomaly detection, handling delayed labels and class imbalance, and operational constraints such as low-latency inference.

  • hard
  • PayPal
  • ML System Design
  • Data Scientist

Detect credit-card transaction fraud

Company: PayPal

Role: Data Scientist

Category: ML System Design

Difficulty: hard

Interview Round: Onsite

##### Question Given two credit-card transactions with limited information, decide whether to accept or decline each and justify your reasoning. Outline a full fraud-detection strategy for card transactions: data required, feature engineering, real-time rules, and model-based approaches. Explain how unsupervised learning can be applied to detect fraudulent transactions and list suitable algorithms. Detail appropriate evaluation metrics for fraud models, including how to assess unsupervised methods without labeled data.

Quick Answer: This question evaluates a data scientist's competency in real-time fraud detection system design, including feature engineering, rule-based and model-based decisioning, unsupervised anomaly detection, handling delayed labels and class imbalance, and operational constraints such as low-latency inference.

Related Interview Questions

  • Design a traditional fraud detection system - PayPal (hard)
  • Design RL-based spending limit policy - PayPal (hard)
  • Design fraud detection from raw transactions - PayPal (hard)
PayPal logo
PayPal
Aug 4, 2025, 10:55 AM
Data Scientist
Onsite
ML System Design
10
0

Credit-Card Fraud Detection: Decisions and System Design

Context

You are designing a real-time decisioning system for card transactions with strict latency constraints. At authorization time, only a subset of features is available; post-transaction outcomes (e.g., chargebacks) arrive weeks later.

For the accept/decline exercise, assume the following two minimal transaction snippets are available at decision time:

  • Transaction A
    • Channel: e-commerce (card-not-present)
    • Amount: $4,200
    • Cardholder home country: UK
    • Merchant country: US (electronics)
    • Local time at cardholder: 03:17
    • Device fingerprint: new to platform
    • IP geolocation: NG (Nigeria), VPN likely
    • Velocity: 5 auth attempts in last 10 minutes on this card across different merchants
  • Transaction B
    • Channel: card-present (EMV chip + PIN)
    • Amount: $18.75
    • Cardholder home country: UK
    • Merchant country: UK (coffee shop)
    • Local time at cardholder: 12:41
    • Device/terminal: known merchant terminal, low dispute history
    • Velocity: consistent with past user pattern (daily coffee purchases)

Tasks

  1. Decide whether to accept or decline each transaction and justify your reasoning. If a conditional action (e.g., step-up authentication) is preferable, state it.
  2. Outline a full fraud-detection strategy for card transactions: data required, feature engineering, real-time rules, and model-based approaches (including system/latency considerations).
  3. Explain how unsupervised learning can be applied to detect fraudulent transactions and list suitable algorithms.
  4. Detail appropriate evaluation metrics for fraud models, including how to assess unsupervised methods without labeled data.

Solution

Show

Comments (0)

Sign in to leave a comment

Loading comments...

Browse More Questions

More ML System Design•More PayPal•More Data Scientist•PayPal Data Scientist•PayPal ML System Design•Data Scientist ML System Design
PracHub

Master your tech interviews with 7,500+ real questions from top companies.

Product

  • Questions
  • Learning Tracks
  • Interview Guides
  • Resources
  • Premium
  • For Universities
  • Student Access

Browse

  • By Company
  • By Role
  • By Category
  • Topic Hubs
  • SQL Questions
  • Compare Platforms
  • Discord Community

Support

  • support@prachub.com
  • (916) 541-4762

Legal

  • Privacy Policy
  • Terms of Service
  • About Us

© 2026 PracHub. All rights reserved.