Skip to main content
Card class: Non-Hero • Category: Payment Gateway

​
At a glance

The percentage of Recharge charges that triggered a 3DS challenge and were abandoned by the customer (not declined by the issuer). On Recharge specifically, 3DS abandonment is overwhelmingly a Recharge Checkout first-order problem, not a rebill problem, recurring rebills should qualify for MIT (Merchant Initiated Transaction) exemption and not face 3DS at all. If you see meaningful abandonment on rebills, your MIT exemption flag is misconfigured. UK and EU first-order traffic typically runs 8, 15% abandon on a 3DS challenge; US traffic doesn’t see this card materially.
What it countsCOUNT(charges WHERE 3DS challenged AND customer abandoned) ÷ COUNT(3DS challenged) × 100. Abandonment = challenge initiated, customer never returned to complete. Distinct from challenge-failed-by-issuer (that’s a decline, not an abandon).
Where 3DS even appliesEU/UK card-not-present transactions over EUR 30 (PSD2 SCA mandate). US, AU, CA traffic largely doesn’t see 3DS on subscription.
Recharge Checkout first-order vs rebillFirst-orders may face 3DS as fresh-cardholder authentication. Rebills should qualify for MIT exemption. If both populate this card it’s a config issue.
CurrencyCurrency-neutral.
Failed / declined paymentsExcluded; abandonment is a separate state from decline.
Time window7D vsP rolling default.
Alert trigger>20% absolute; +5pp vsP. sentiment_key: threedsecure_abandon (gauge inverse, lower = better).
Reading hintsUK first-order abandonment 8, 12% normal. >15% suggests friction in 3DS challenge UX (translation issues, slow issuer pages, mobile-popup blocking).
Rolesowner, finance, operations

​
Calculation

Calculated automatically from your Recharge data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.

​
Worked example

“Daily Greens Co” UK customers, 7-day window 26 Apr 26 to 02 May 26.
Cohort3DS challengedCompletedAbandonedIssuer-rejectedAbandon rate
Recharge Checkout first-order, UK240196281611.7%
Monthly rebill, UK (mis-flagged, no MIT)18124222.2%
Annual prepaid renewal, UK (mis-flagged)421125.0%
Period totals (UK only):
  Total challenged                      = 262
  Total abandoned                       = 33
  
  Blended abandon rate (this card)      = 33 ÷ 262 × 100 = 12.6%
  First-order only abandon rate         = 28 ÷ 240 × 100 = 11.7%
What the merchant should notice:
  1. The 22 rebill challenges (18+4) shouldn’t exist. Recurring rebills on saved tokens qualify for MIT (Merchant Initiated Transaction) exemption under PSD2 SCA. If this card shows non-zero rebill challenges, the MIT flag is missing in the Recharge → processor API call. This is a config bug; open a Recharge support ticket.
  2. First-order abandon at 11.7% is normal range for UK 3DS friction. Below 8% is excellent (clean challenge UX, fast issuer pages); above 15% suggests a UX problem in the challenge popup (mobile blocking, language mismatch).
  3. Annual prepaid challenges abandoned 25% because the customer was challenged by the issuer for a high-value (USD 790) transaction; they were unsure if they really wanted to commit and abandoned. High-value transactions intentionally face higher abandonment. Mitigate with clear pre-challenge UX (“you’re about to be authenticated for your annual subscription, please complete the bank prompt”).
  4. US customers don’t appear here because PSD2 SCA doesn’t apply outside EEA. A US customer never sees a 3DS prompt unless the issuer chose to step-up authenticate (rare, and not Recharge-driven).
  5. Issuer-rejected (19 total) is NOT abandonment, it’s decline. The customer attempted, the issuer said no. They’re tracked in rec_decline_rate as AUTHENTICATION_REQUIRED or AUTHENTICATION_FAILED.

​
Sibling cards merchants should reference together

CardWhy pair it with 3DS Abandon Rate
rec_decline_rateCousin metric: 3DS-challenge-failed-by-issuer is decline, not abandon.
rec_top_decline_reasonsAUTHENTICATION_REQUIRED cluster reveals MIT mis-config.
rec_total_volumeLost volume from abandoned challenges visible here.
rec_success_rateAbandonment is in the gap between attempted and successful.
Stripe / Shopify Payments 3DS abandon rateUnderlying processor view.

​
Reconciling against the vendor’s own dashboard

Where to look in the Recharge merchant portal: admin.rechargepayments.com. Recharge admin doesn’t expose a dedicated 3DS abandon view; the better source is the underlying processor’s dashboard (Stripe Radar → 3DS, Shopify Payments → Authentication) for the same window. Recharge’s Charges → Failed → AUTHENTICATION_REQUIRED lists the issuer-rejected slice, which is the cousin to abandons. Why our number may legitimately differ from the underlying processor:
ReasonDirectionWhy
Abandon definition windowSlight differences”Abandoned” needs a timeout window (typically 30 minutes of no return). Different processors apply different windows.
First-order vs rebill splitRecharge admin doesn’t splitThe processor view often blends first-purchase 3DS with subscription-rebill 3DS. We surface both flavours.
Cross-connector reconciliation:
ComparisonExpected relationshipWhen divergence is legitimate
rec_threedsecure_abandon_rate ↔ Shopify storefront 3DS abandon rateRecharge typically lowerStorefront includes one-time purchases with first-time customers; Recharge first-orders are subscription-committed (lower abandon).

​
Known limitations / merchant FAQs

“My rebill abandon rate isn’t zero, what’s wrong?” The MIT (Merchant Initiated Transaction) exemption flag isn’t being set in the Recharge → underlying processor API call for rebills. Recurring rebills should be exempt from SCA under PSD2; if the flag is missing, the issuer treats the rebill as fresh-customer auth and challenges. Open a Recharge support ticket. “What’s a normal first-order 3DS abandon rate for the UK / EU?” 8, 12% on Recharge Checkout first-orders is normal. Above 15% suggests a UX problem in the challenge popup (mobile blocking, language mismatch, slow issuer page). Below 8% is excellent. “Annual prepaid 3DS abandon is higher, can we reduce it?” High-value (USD 790) prepaid renewals naturally face more friction; some abandonment is “I changed my mind”. Pre-challenge UX helps: a clear screen explaining “you’ll be authenticated by your bank for the annual subscription, please complete the prompt” before redirect. Recharge Checkout templates support this. “Do US customers face 3DS at all?” Rarely. PSD2 SCA only mandates EEA card-not-present. Some US issuers run their own step-up authentication on suspicious patterns, but it’s <0.1% of US traffic typically. “How does this card relate to AUTHENTICATION_REQUIRED in decline reasons?” AUTHENTICATION_REQUIRED is when the issuer demands a challenge but the merchant didn’t initiate one (mis-config, no 3DS support). The challenge never happens; the charge declines. Abandon (this card) is when a challenge DID happen, and the customer didn’t complete it. They’re complementary metrics. “Why is one issuer (e.g. NatWest) abandoning more than another?” Some issuer 3DS pages are slower, less mobile-friendly, or display language mismatches that confuse customers. The fix is on the issuer side; you can’t directly improve their pages. Practical mitigation: route higher-friction issuers to alternative payment methods (PayPal Billing Agreement, Shop Pay) at signup. “Is 3DS challenge worth the abandonment cost?” For EEA traffic it’s not optional, PSD2 mandates it. The abandonment is the unavoidable cost of compliance. The alternative (no 3DS) means the issuer auto-declines, which is worse for conversion.

​
Tracked live in Vortex IQ Nerve Centre

3DS Abandonment Rate is one of hundreds of KPI pulses Vortex IQ tracks across Recharge 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 or book a demo to see this metric running on your own data.