compliance_monitoring · workflow
Stripe uses ML to reduce SCA friction by 20% and fraud by 8%
SCA regulations in the EEA and UK mandate two-factor authentication for card transactions, creating customer friction and conversion loss; navigating the 20+ considerations for authentication and SCA exemptions is too complex to optimize without ML.
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 · New card transaction arrives
When presented with a new transaction, the authentication engine begins processing.
Tools used
authentication engine
Outcome
The ML authentication engine reduced two-factor challenges shown to customers by 20%, decreased fraud by 8% on average for eligible card transactions, and improved the average authorization rate by 61 basis points.
Results
Volume20%
Cost replaced8%
Running sincefive months before Stripe Sessions announcement
Grounding & classification
Source type: technical build writeup
20 fields verified against source quotes.
fraud detectionpredictive analyticsmetric backedproduction runtime claimedsource backedtools describedvendor confirmedworkflow describedfinancial servicesaccuracy improvementconversion increaseerror reductiontechnical build writeupcompliance monitoringfinance opsautonomous resolution