3DS Friction Revenue Loss, Stripe

​

At a glance

An estimate of revenue lost to 3D Secure (SCA) friction over the last 30 days. Specifically: charges that were sent through 3DS, the customer abandoned the challenge, and the customer did not retry. Most material for UK and EU stores subject to PSD2 / SCA mandates.

​

Calculation

​

Worked example

Total 3DS-friction charges       = 18 + 6 + 41 = 65
Total gross loss                 = £1,710 + £570 + £3,895 = £6,175
Abandon-to-lost-sale correlation = 65% (Vortex IQ default for UK fashion)
3DS Friction Revenue Loss        = £6,175 × 0.65 = £4,014 / month

1. The SCA-abandoned bucket (requires_action) is the dominant loss. £3,895 of the £6,175 gross sits there: customers got the SCA challenge SMS, didn’t open it, and never came back. This is the friction the card was built to surface; it’s largely invisible on Stripe-only dashboards because requires_action charges sit between “succeeded” and “failed” filters.
2. The 35% discount factor is meant to be honest. Of those 65 customers, some would have abandoned for non-3DS reasons (changed mind, found cheaper alternative, hit a shipping issue). The 65% correlation factor reflects the share that would have completed if the SCA step weren’t there. UK fashion has a higher correlation factor than UK electronics (more impulse-driven purchases, larger SCA dropoff).
3. The fix is technical, not commercial. Implementing frictionless 3DS (passing more risk-data fields to the issuer to reduce the rate of full challenges), enabling Stripe’s request_three_d_secure: 'automatic' instead of 'any', and using exemptions for low-value transactions can typically halve the friction loss. UK ecommerce best practice is 60, 70% of 3DS attempts ending frictionless.

​

Sibling cards merchants should reference together

​

Reconciling against the vendor’s own dashboard

• Payments → All payments → filter “Required action” for the SCA-abandoned subset.
• Payments → Failed payments filtered to outcome.reason = authentication_required for 3DS-failed declines.
• Reports → Authentication report for the historical 3DS-attempt and success-rate inputs.
• Settings → Payment methods → 3D Secure for the configured 3DS request mode (automatic vs any vs challenge).

• Stripe’s “Requires action” tile. Counts charges in flight, not lost revenue. Most of those will resolve (succeed or fail explicitly) within a few hours; only the abandoned ones contribute to this card.
• Stripe Sigma “3DS abandon” custom queries. Closest equivalent. They typically don’t apply the abandon-to-lost-sale correlation factor; the gross number runs higher than ours.
• GA4 checkout-step-abandonment funnel. Sees the customer abandonment but not the 3DS-specific cause.

​

Known limitations / merchant FAQs

Reconciliation questions are answered in the Reconciling against the vendor’s own dashboard section above.

1. Frictionless 3DS optimisation. Pass more risk-data fields (browser fingerprint, address, email, account age) on the charge so the issuer can authenticate without challenging the customer. Stripe handles this automatically when you use request_three_d_secure: 'automatic'.
2. Exemption usage. For low-value transactions (< €30), Stripe can request issuer exemption, skipping the SCA challenge. Configure in Settings → Payment methods → 3DS.
3. Challenge-UX improvements. If your store uses a custom checkout, ensure the challenge iframe is fully visible, doesn’t redirect away, and shows the bank’s branding (which prevents customers thinking it’s a phishing attempt). Most customers who abandon do so because they distrust the SCA prompt.

• UK fashion / apparel: 65%
• UK electronics: 55% (more shopping-around behaviour)
• UK subscription / SaaS: 80% (high purchase intent)
• DE fashion: 60%
• FR fashion: 70%
• Universal default if vertical is unknown: 65%

​

Tracked live in Vortex IQ Nerve Centre