compliance_monitoring · workflow
Stripe Radar uses machine learning to reduce fraud-driven chargebacks by 11%
Online fraud causes unnecessary losses for most online businesses—threatening viability for some—and as the online economy grows, fraud is becoming more sophisticated.
How it works
Common implementation structure
How this type of workflow is generally built, generalized across documented cases — not tied to any one vendor's stack. Click any stage to read what happens there. Specific products that implement these stages appear in “Tools commonly seen” below.
Stage 1 · Real-time signal collection
Stripe.js and mobile SDKs collect real-time fraud signals including screen resolution and browsing patterns.
Tools used
RadarStripe.jsmobile SDKs
Outcome
Radar's real-time fraud signals reduce the expected number of fraud-driven chargebacks a business will receive by 11%, shielding Stripe users from hundreds of millions of dollars of fraudulent transactions every month.
Results
Time savedhundreds of millions of dollars
Cost replaced11%
Running sincesince 2015
Grounding & classification
Source type: technical build writeup
20 fields verified against source quotes.
anomaly detectionfraud detectionmetric backedproduction runtime claimedsource backedtools describedworkflow describedecommercefinancial servicescost reductionerror reductiontechnical build writeupcompliance monitoringfinance opsmonitor detect alert