PracHub
QuestionsCoachesLearningGuidesInterview Prep
|Home/Analytics & Experimentation/PayPal

Assess card transactions and plan risk strategy

Last updated: Mar 29, 2026

Quick Overview

Assess card transactions and plan risk strategy evaluates metric design, causal reasoning, experiment setup, diagnostics, SQL/statistical checks, and recommendations in a realistic interview setting. A strong answer states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

  • hard
  • PayPal
  • Analytics & Experimentation
  • Data Scientist

Assess card transactions and plan risk strategy

Company: PayPal

Role: Data Scientist

Category: Analytics & Experimentation

Difficulty: hard

Interview Round: Onsite

Given feature summaries for two card transactions (e.g., merchant category, amount, velocity, geolocation, device fingerprint, account tenure, historical approval/chargeback rates), decide approve or decline for each and justify the decision. Then outline a simple risk strategy for cold-start: propose concrete rules (velocity checks, geo-velocity, MCC limits, block/allow lists, step-up authentication), thresholds, and escalation paths, discussing the loss–friction trade-off and expected impact on approval rate, chargeback rate, and false positive rate. Finally, model adversary behavior: enumerate likely fraudster tactics (card testing, mule addresses, BIN attacks, device spoofing) and explain how you would detect adaptation and update rules or models.

Quick Answer: Assess card transactions and plan risk strategy evaluates metric design, causal reasoning, experiment setup, diagnostics, SQL/statistical checks, and recommendations in a realistic interview setting. A strong answer states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

Related Interview Questions

  • How would you measure impact? - PayPal (medium)
  • How to evaluate a new homepage feature - PayPal (easy)
  • Design and evaluate a fraud detection strategy - PayPal (easy)
  • Design a fraud mitigation strategy under constraints - PayPal (hard)
  • Design metrics and experiment for donation feature - PayPal (easy)
|Home/Analytics & Experimentation/PayPal

Assess card transactions and plan risk strategy

PayPal logo
PayPal
Jul 31, 2025, 12:00 AM
hardData ScientistOnsiteAnalytics & Experimentation
3
0

Assess card transactions and plan risk strategy

Card Fraud Decisions and Cold‑Start Risk Strategy

Context

You are designing the first version of card risk controls for an online checkout platform. You have no production ML model yet and must rely on rules, step‑up authentication, and manual review. You receive feature summaries for two example card‑not‑present transactions.

Assumptions:

  • Liability for confirmed fraud is borne by the platform/merchant (no chargeback protection).
  • Features available at authorization time: merchant category (MCC), amount, velocity signals (per account/device/IP/card), geolocation comparisons, device fingerprint reputation, account tenure/behavior, merchant historical approval/chargeback rates.

Data: Two Example Transactions

  • Transaction A
    • MCC: 5732 (Electronics)
    • Amount: $1,199
    • Account tenure: 1 day; 0 prior successful payments
    • Velocity (last 10 min): account = 4 attempts; device = 19 attempts across 12 cards; IP = 35 attempts across 25 cards
    • Geolocation: IP country = GB; card BIN country = US; shipping address = Miami, FL to a known freight‑forwarder ZIP range
    • Device fingerprint: first seen yesterday; seen on 6 distinct accounts in 24h; 2 prior confirmed frauds tied to this fingerprint
    • Merchant history: sitewide approval rate 92%; chargeback rate 0.8% overall, 1.5% for electronics >$500
  • Transaction B
    • MCC: 5816 (Digital services/subscriptions)
    • Amount: $29
    • Account tenure: 3 years; 24 prior successful payments; no chargebacks
    • Velocity (last 10 min): account = 1 attempt; device = 1 attempt; IP = 1 attempt
    • Geolocation: IP city within 25 miles of billing ZIP; card BIN country matches IP country
    • Device fingerprint: seen 60+ times over 3 years for this account only; no prior fraud associations
    • Merchant history: approval rate 98%; chargeback rate 0.1%

Tasks

  1. Decisioning
    • For each transaction (A and B), decide Approve or Decline and justify using the features.
  2. Cold‑Start Risk Strategy
    • Propose concrete rules: velocity checks, geo‑velocity, MCC/amount limits, block/allow lists, step‑up authentication.
    • Include specific thresholds and escalation paths (auto‑approve/decline → step‑up → manual review).
    • Discuss the loss–friction trade‑off and expected direction/magnitude of impact on approval rate, chargeback rate, and false positive rate.
  3. Adversary Modeling
    • Enumerate likely fraudster tactics (e.g., card testing, mule addresses, BIN attacks, device spoofing, enumeration).
    • Explain how you would detect adaptation over time and update rules or models accordingly.

Constraints & Assumptions

  • Preserve the scope, facts, inputs, and requested outputs from the prompt above.
  • If the prompt leaves a detail unspecified, state a reasonable assumption before relying on it.
  • Keep the answer interview-ready: concise enough to present, but concrete enough to implement or evaluate.

Clarifying Questions to Ask

  • Clarify the business objective, unit of analysis, time window, exposure definition, and primary metric.
  • State assumptions about instrumentation, randomization, sample size, and data quality.
  • Separate descriptive analysis from causal claims.

What a Strong Answer Covers

  • A metric framework with primary, guardrail, and diagnostic metrics.
  • A credible analysis or experiment design with clear assumptions and bias checks.
  • SQL/statistical logic for segmentation, variance, confidence, and data validation where relevant.
  • An actionable recommendation that explains trade-offs and next steps.

Follow-up Questions

  • What sanity checks would you run before trusting the result?
  • How would you handle novelty effects, seasonality, or selection bias?
  • What decision would you make if metrics disagree?
Loading comments...

Browse More Questions

More Analytics & Experimentation•More PayPal•More Data Scientist•PayPal Data Scientist•PayPal Analytics & Experimentation•Data Scientist Analytics & Experimentation

Write your answer

Your first approved answer each day earns 20 XP.

Sign in to write your answer.
PracHub

Master your tech interviews with 8,000+ 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
  • AI Coding 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.