At a glance
Percentage of Square Online checkouts that hit a 3DS 2 challenge and the customer abandoned (did not complete the bank popup). NOT the same as decline (issuer rejected). Different fix: abandons need UX work; declines need issuer-side analysis. Square Online uses 3DS 2 for SCA-required EU traffic and for high-risk US traffic.
Calculation
Calculated automatically from your Square data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.Worked example
7 days of Square Online for a US-EU dual-market DTC brand:- EU 13.9% is at the alert threshold. PSD2 SCA forces 3DS challenges; abandon rates of 8, 15% are typical.
- US 15% on a small base (3 / 20) is noisy. Don’t over-react below 50 challenges per week.
- Frictionless rate matters more. 392 of 412 US sessions skipped 3DS entirely (95.1% frictionless); 122 of 158 EU did (77.2%).
- Square Risk Manager interaction. Square Risk can pre-emptively decline high-risk traffic before 3DS even fires; that suppresses both the challenge count and the abandon rate.
Sibling cards merchants should reference together
Reconciling against the vendor’s own dashboard
Where to look in the Square Dashboard: Square does not surface 3DS abandon as a headline KPI. Use Reports → Transactions filtered toStatus: Cancelled and inspect failure messages. The Risk Manager dashboard shows challenge-issuance counts.
Why ours may differ:
Cross-connector reconciliation: Stripe and Square 3DS abandon rates for the same business should be comparable in absolute terms (the 3DS protocol is shared); divergence usually reflects different challenge-trigger thresholds in the two PSPs’ risk engines.