> ## Documentation Index > Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt > Use this file to discover all available pages before exploring further. # 3DS Friction Revenue Loss, CyberSource > 3DS Friction Revenue Loss for CyberSource stores. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it. **Metrics type:** [Cross-Platform Metrics](/nerve-centre/overview#metrics-types-explained) • **Category:** [Payment Gateway](/nerve-centre/connectors#connectors-by-type) ## At a glance > Estimated dollar value of revenue lost specifically to 3DS challenge friction in the period. Cross-platform: combines CS 3DS abandon counts with the connected commerce platform's AOV and an estimated abandon-to-lost-sale correlation percentage. The CFO-facing card for "what's PSD2 / SCA actually costing us", converts 3DS abandon rates into a dollar figure that justifies UX investment in saved-payment-method flows, smart routing, and frictionless-rate optimisation. | | | | ------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **The formula** | `3ds_abandon_count × commerce_sibling.aov × abandon_to_lost_sale_correlation_pct`. The three factors compound: how many customers abandoned a 3DS challenge, what they would have spent on average, and what percentage of those abandons translate to truly lost (vs delayed) sales. | | **`3ds_abandon_count`** | Count of `threeDSecureStatus = ABANDONED` rows from `/tss/v2/searches`. The numerator from [3DS Challenge Abandon Rate](/nerve-centre/kpi-cards/cybersource/3ds-challenge-abandon-rate). | | **`commerce_sibling.aov`** | The connected commerce platform's 30D rolling average order value. Sources: Adobe Commerce, BigCommerce, Shopify, Magento. Multi-currency merchants get per-currency AOV and the sum is per-currency. | | **`abandon_to_lost_sale_correlation_pct`** | Default 65%. Calibrated against industry data showing roughly 65% of 3DS challenge abandons translate to truly lost sales (the remaining 35% retry on a different card / payment method / day, or the merchant captures via cart-recovery email). Configurable per-merchant if their actual recovery data differs. | | **Why a correlation factor and not 100%?** | A 3DS abandon doesn't always mean a lost sale. Some customers retry immediately on a saved Apple Pay / Google Pay credential (no 3DS challenge). Some come back via cart-recovery email and complete days later. The 65% factor captures the genuinely-lost slice; the 35% absorbed slice is captured separately by the storefront's cart-recovery KPIs. | | **Required connectors** | CyberSource AND a commerce-platform connector for the `aov` factor. The card grays out without a commerce sibling. | | **Currency** | Single currency at sync-time FX for the headline; per-currency drilldown available. | | **Refunds / disputes** | Excluded. Abandons never authorise so there's nothing to refund / dispute. | | **Failed / declined payments** | The card is specifically about 3DS abandons (not declines). Declines on 3DS-authenticated transactions live in [Decline Rate](/nerve-centre/kpi-cards/cybersource/decline-rate). | | **Time window** | `30D`. | | **Refresh cadence** | Daily. This is a trend / projection card, not a real-time pulse. | | **Alert trigger** | `> $1,000/month`. The threshold is intentionally low; at enterprise scale the actual number is typically $50k-$500k/month for PSD2-mandated geographies. | | **Roles** | owner, finance, marketing | ## Calculation Calculated automatically from your CyberSource data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading. ## Worked example A UK-based enterprise online fashion retailer running CyberSource for ecommerce + Adobe Commerce for the storefront. The 30-day window covers 14 Mar 26 to 12 Apr 26. Roughly 451,100 3DS challenges shown across UK + EU + global traffic; 122,400 of those were abandoned (27.13% abandon rate, see [3DS Challenge Abandon Rate](/nerve-centre/kpi-cards/cybersource/3ds-challenge-abandon-rate)). The factors: | Factor | Value | Source | | -------------------------------- | ------- | ------------------------------------------ | | 3DS abandon count | 122,400 | `/tss/v2/searches`, 3DS status = ABANDONED | | Adobe Commerce AOV (GBP) | £68 | 30D rolling | | Abandon-to-lost-sale correlation | 65% | Default calibration | ```text theme={null} 3DS Friction Revenue Loss = 3ds_abandon_count × AOV × correlation_pct = 122,400 × £68 × 0.65 = £5.41M per period ``` Five things worth noticing for a UK-based ecommerce VP of Conversion: 1. **£5.41M/period in 3DS friction loss is meaningful.** PSD2 / SCA mandated 3DS in the UK + EU is genuinely costing the merchant \~£65M/year. Worth an annual VP-level conversation about where the merchant should invest to reduce the abandon rate. 2. **The 65% correlation factor is conservative.** Industry data shows 60-75% of 3DS abandons are truly lost (the customer doesn't come back via any path). The 65% default is a middle estimate; for fashion retailers with strong cart-recovery email programmes, actual recovery may be slightly better than 35% (so the friction loss is closer to £4.5M); for low-loyalty / commodity-product merchants, recovery is worse (so the loss is closer to £6.0M). Override the default with the merchant's actual data for calibrated accuracy. 3. **The card pairs naturally with [3DS Challenge Abandon Rate](/nerve-centre/kpi-cards/cybersource/3ds-challenge-abandon-rate).** The abandon-rate card is the diagnostic; this card is the dollar quantification. For the same incident, abandon-rate goes up 1pp → this card goes up \~£200k/period (at this merchant's volume + AOV). The £200k-per-percentage-point-of-abandon-reduction is the metric that justifies UX investments in saved-payment-method flows, smart routing, and frictionless-rate optimisation. 4. **Action plan with quantified ROI.** Three improvements typically reduce 3DS abandon by 5-8pp combined, recovering 25-40% of this card's value: * **Push to network-token saved flows** (Apple Pay, Google Pay): 3DS happens at provisioning time, not at checkout. Estimated abandon reduction 2-3pp = £1.0-1.5M annual recovery. * **Smart routing for mobile-web** (route to issuers with better mobile-challenge UX): 1-2pp reduction = £0.5-1.0M. * **Frictionless-rate optimisation via richer device-fingerprint data**: 2-3pp reduction (more transactions go frictionless = fewer challenges = fewer abandons) = £1.0-1.5M. 5. **Geography-specific drilldown is critical.** UK / EU traffic is PSD2-mandated; non-EU traffic is opt-in 3DS. Splitting the card by geography shows: UK / EU contributes \~85% of friction loss; non-EU only \~15%. The merchant can prioritise EU-specific UX investments and consider opt-out 3DS for non-mandated geographies above the AOV threshold for liability protection. If next period the merchant ships the listed improvements and abandon rate drops from 27.13% to 22.0%, the projected friction loss falls from £5.41M to \~£3.95M, an annualised £17.5M recovery on UX investment that typically takes 1-2 quarters of engineering work. ## Sibling cards merchants should reference together | Card | Why pair it with 3DS Friction Revenue Loss | | ------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------- | | [3DS Challenge Abandon Rate](/nerve-centre/kpi-cards/cybersource/3ds-challenge-abandon-rate) | The diagnostic rate; this card is the dollar quantification. | | [3DS Frictionless Volume](/nerve-centre/kpi-cards/cybersource/3ds-frictionless-volume) | Higher frictionless = fewer challenges = lower friction loss. | | [3DS Success Rate](/nerve-centre/kpi-cards/cybersource/3ds-success-rate) | Of the challenges shown, what percentage succeeded? | | [3DS-Authenticated Transactions](/nerve-centre/kpi-cards/cybersource/3ds-authenticated-transactions) | The volume side. | | [3DS Failure Alert](/nerve-centre/kpi-cards/cybersource/3ds-failure-alert) | Real-time alert when 3DS success drops sharply. | | [Recoverable Revenue (decline-driven)](/nerve-centre/kpi-cards/cybersource/recoverable-revenue) | The decline-side companion. Decline + 3DS friction together cover most cross-platform revenue loss. | | [Decline Spike vs Checkout Funnel Drop](/nerve-centre/kpi-cards/cybersource/decline-spike-vs-checkout-funnel-drop) | Diagnostic chart for live decline-driven revenue loss. | | [Authorisation Success Rate](/nerve-centre/kpi-cards/cybersource/authorisation-success-rate) | High 3DS abandon directly drags the auth rate. | | Adobe Commerce / Shopify / BigCommerce checkout-funnel | The storefront pulse measuring payment-step abandon. | ## Reconciling against the vendor's own dashboard **Where to look in CyberSource Business Center (EBC2):** This card has no direct EBC2 counterpart, it's a Vortex IQ derived figure that joins CS 3DS abandon counts to the connected commerce platform's AOV. Operators investigating the underlying data should reference: * [EBC2 → Decisions → Payer Authentication → Performance Reports](https://ebc2.cybersource.com/ebc2/app/RiskManagement/PayerAuthentication), CyberSource's 3DS Server performance dashboard. * [EBC2 → Reports → Payer Authentication Report](https://ebc2.cybersource.com/ebc2/app/Reports/StandardReports), the daily 3DS-outcome dump. * The commerce-platform's analytics for the AOV factor. **Why our number may legitimately differ from a hand-rolled equivalent:** | Reason | Direction | What to do | | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------- | ------------------------------------------------------------------------------------------------ | | **65% correlation default**. Our default abandon-to-lost-sale correlation is industry-calibrated. Merchants with strong cart-recovery / saved-payment-method flows recover more (lower correlation, lower friction loss); merchants with weak post-abandon recovery lose more (higher correlation). | Either direction. | Override `abandon_to_lost_sale_correlation_pct` in the manifest with the merchant's actual data. | | **Reporting API extraction lag**. Reporting v3 overnight batch on the 3DS data side. | Vortex IQ may lag EBC2 2-6 hours on most-recent day. | Negligible at 30D window. | | **AOV calibration window**. We use the commerce-side 30D rolling AOV. Merchants with seasonal AOV (luxury, gift) may see swings that lag this card. | Either direction. | Lengthen the AOV window in the manifest if seasonal. | | **Multi-currency**. We sum per-currency at sync-time FX. Bank-side recovery may differ. | Tiny drift. | Use per-currency drilldown for finance-grade reporting. | **Cross-connector reconciliation:** | Comparison | Expected relationship | When divergence is legitimate | | ------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------ | | `cs_xc_3ds_friction_loss` ↔ [`cs_3ds_abandon_rate`](/nerve-centre/kpi-cards/cybersource/3ds-challenge-abandon-rate) | This card's value scales linearly with the abandon count. A 1pp reduction in abandon rate ≈ N% reduction in this card. | n/a (causal). | | `cs_xc_3ds_friction_loss` ↔ commerce platform's "abandoned cart" recovery KPI | The 35% NOT counted as lost in this card should approximately equal the commerce-side abandoned-cart-recovery success rate. | A divergence suggests calibration drift on the correlation factor. | | `cs_xc_3ds_friction_loss` ↔ [`cs_xc_recoverable_revenue`](/nerve-centre/kpi-cards/cybersource/recoverable-revenue) | Different friction sources (3DS vs decline). Both are real cross-platform revenue loss for an enterprise merchant. Sum them for total payment-friction-driven revenue loss. | n/a (independent). | ***
Documentation cross-reference (for PSD2-mandated merchants) This card is unique to CyberSource within Vortex IQ Nerve Centre because the 3DS outcome data quality on `/tss/v2/searches` is materially better than what other gateways expose. For multi-acquirer enterprises operating in PSD2 / SCA territory, this remains the canonical "what is 3DS costing us" CFO-facing card.
## Known limitations / merchant FAQs **Why is the correlation factor 65% and not 100%?** Because not every 3DS abandon is a truly lost sale. Industry data shows \~35% of abandons are absorbed by alternate paths: customer retries on a saved Apple Pay / Google Pay credential immediately (no 3DS challenge), or comes back via cart-recovery email and completes days later. The 65% factor isolates the truly-lost slice. For merchants with weaker post-abandon recovery flows, the correlation can run higher (70-80%); for merchants with strong saved-payment-method options, lower (50-60%). **My PSD2 / SCA exposure is high. Can I opt out?** Not for in-scope EU / UK transactions; PSD2 / SCA is regulatory. The lever is reducing how often customers see a challenge: (a) maximise frictionless rate via richer device-fingerprint data; (b) invoke TRA exemption for low-risk transactions; (c) invoke low-value exemption (under €30); (d) push to saved-payment-method flows where 3DS happened at provisioning. None of these is "opt out"; all reduce the challenge rate, which reduces this card's value. **My non-EU traffic is also flowing through 3DS. Why?** Either: (a) merchant opt-in to 3DS for liability shift on potentially-fraudulent transactions; (b) the issuer requires 3DS regardless of regulatory regime (some Latin American, India, parts of Asia mandate 3DS); (c) the merchant's gateway / orchestration layer is configured to invoke 3DS by default. For non-mandated geographies above the AOV threshold, 3DS-for-liability-shift can be net-positive (saving more on chargeback exposure than the friction loss costs); below, it's net-negative. **The number is huge. Is it really lost or is it just delayed?** 65% genuinely lost; 35% delayed / recovered. This is the calibrated default. The merchant can validate by comparing this card's monthly value to the commerce-side cart-recovery email programme's actual recovered revenue. If the recovered revenue is meaningfully higher than 35% of this card's value, the correlation factor should be lowered. If lower, raised. **Does this card help me decide whether to invest in saved-payment-method flows?** Yes, directly. Saved-payment-method flows (Apple Pay, Google Pay, network tokens) bypass per-transaction 3DS by handling authentication at provisioning time. Each percentage point of traffic shifted to saved-payment-method reduces this card's value roughly proportionally (because those transactions don't hit the 3DS challenge flow). For a merchant with £5M/period 3DS friction loss, shifting 30% of EU traffic to saved-payment-methods is worth \~£1.5M/period. **Why doesn't Stripe have an equivalent card?** Stripe's 3DS implementation is internal to its `payment_intents` flow and the abandon data isn't surfaced as cleanly as CyberSource's `/tss/v2/searches` `threeDSecureStatus` field. Multi-acquirer merchants with both CS and Stripe should treat this CS card as the canonical 3DS-friction view across processors. **My multi-currency global merchant, does this card work?** Yes. The card sums abandon-count × per-currency-AOV separately, then aggregates to display currency at sync-time FX. The drilldown shows per-currency breakdown for finance-grade reporting. **How fast does this card refresh?** Daily. This is a trend / projection card, not real-time. For active-incident 3DS spikes use [3DS Failure Alert](/nerve-centre/kpi-cards/cybersource/3ds-failure-alert) which fires in real-time on rate-of-change in success / abandon rates. **Can I exclude opt-in 3DS from the calculation?** Not in the default formula, but the manifest supports filtering by 3DS-mandate flag if the merchant tags their authentication flows. For most merchants the regulatory-mandated 3DS dominates the friction loss anyway, so the filter has small impact. **Is the correlation factor calibrated regionally?** Not by default; the 65% is global. Regional calibration is a manifest setting that some enterprise merchants enable, especially when they have very different cart-recovery effectiveness across geographies (UK / EU strong recovery, LATAM / India weaker). *** ### Tracked live in Vortex IQ Nerve Centre *3DS Friction Revenue Loss* is one of hundreds of KPI pulses Vortex IQ tracks across CyberSource and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English. [Start for free](https://app.vortexiq.ai/login) or [book a demo](https://www.vortexiq.ai/contact-us) to see this metric running on your own data.