finance_ops · workflow
Stripe uses AI and issuer collaboration to create adaptive Radar fraud rules that increase payment success rates
Radar's default rules blocked transactions whenever CVC or postal code verification failed, causing legitimate low-risk transactions to be blocked alongside fraudulent ones and leaving revenue on the table.
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 · Transaction fails CVC or postal code check
A payment transaction that fails CVC or postal code verification initiates Radar's adaptive rule evaluation.
Tools used
RadarRadar for Fraud Teams
Outcome
Businesses migrating to the adaptive rules see a 1.3 percentage point increase in payment success rates with minimal changes to fraud rates, representing the potential for billions of dollars in additional collective revenue each year.
Results
Volume1.3 percentage point increase
Cost replacedbillions of dollars in additional revenue each year
Grounding & classification
Source type: technical build writeup
20 fields verified against source quotes.
fraud detectionpredictive analyticsmetric backedproduction runtime claimedtools describedvendor confirmedworkflow describedfinancial servicesconversion increaseerror reductionrevenue increasetechnical build writeupcompliance monitoringfinance opsextract classify routemonitor detect alert