Skip to content
GKgkml.dev
← All scenarios
AWSMLOpsSAA-C03brutal~35 min

Design real-time fraud scoring

Payments platform. 4,000 transactions per second at peak, 800 average. Every transaction must receive a fraud score before authorisation, and the end-to-end budget for scoring is 50ms at p99.

Fraud labels arrive from chargebacks, 30 to 90 days after the transaction. Roughly 0.15% of transactions are fraudulent. A false negative costs the average transaction value, about £70. A false positive blocks a legitimate customer, and the business estimates the lifetime cost of that at roughly £15 — but it is politically far more visible.

Regulatory requirement: any declined transaction must be explainable to the customer on request, and the decision must be reproducible for two years.

Design this. I want the serving architecture, the feature strategy, the model choice, the threshold decision, and the monitoring — and for each, what you are optimising for and what you are giving up.

Choose how you want to be interrogated

The same case under two modes is two different exercises. If you are unsure, RCA drill is the one that trains root-cause analysis most directly.

Before you start: you begin locked. The Mentor will give you nothing — not a nudge, not a category — until you state a specific position and the mechanism you think produces it. Four genuine attempts unlock the resolution. There is no shortcut.