Skip to main content
Card class: Cross-Channel • Category: Payment Gateway
When PayPal declines spike, do we see Shopify/BC/Adobe checkout completion drop? If yes, declines are causing real revenue loss, not just buyer remorse.

​
At a glance

Cross-channel correlation card that overlays PayPal decline-rate spikes against the commerce platform’s checkout funnel completion. The “is this real or just blocked fraud?” filter on every PayPal decline alert. Fires only when BOTH signals move together (decline rate jumps > 5 percentage points AND checkout completion drops > 5 percentage points in the same 24-hour window).
The formulaTwo-axis dual signal: Δ(pp_decline_rate vs prior 24h) > +5pp AND Δ(commerce_checkout_completion_rate vs prior 24h) < -5pp. Both conditions must hold simultaneously for the alert to fire.
PayPal axis (decline)T00xx events with status IN [D, F] divided by all T00xx attempts in the trailing 24 hours. Compared against the equivalent prior-24h baseline.
Commerce axis (funnel)Checkout completion rate from the connected commerce platform (Shopify / BigCommerce / Adobe Commerce). Defined as orders_placed ÷ checkouts_started. Compared against the equivalent prior-24h baseline.
Why this card matters (the merchant insight)A decline spike alone could mean (a) real customers being blocked from completing purchases (revenue loss) OR (b) fraud being blocked at the gate (good outcome, no real revenue loss). This card disambiguates: a simultaneous funnel drop confirms it’s hitting real customers; a flat funnel suggests the spike is blocked fraud and you can ignore it.
Refunds (T11) and disputes (T19)NOT counted on the PayPal axis. This card is decline-stage only, post-success events have their own cards.
Pending status (P) handlingPending payments are in the denominator on the PayPal axis (they were attempts) but not in the decline numerator.
Currencyn/a (rates only). Both axes are rates, currency-neutral.
What “checkout completion” means per platformShopify: Order.createdAt count ÷ Checkout.createdAt count for the window (uses Shopify’s checkout funnel data). BigCommerce: orders_placed ÷ checkouts_started from BC’s analytics. Adobe Commerce: quote_active → quote_converted ratio from the orders/quote indices.
Time alignmentBoth axes use the same 24-hour rolling window in UTC. The commerce platform is the upstream signal (customer hits checkout); PayPal is downstream (customer attempts payment). A decline spike with no funnel drop means the customer reached checkout but their payment was blocked, on a percentage basis few customers (most checkouts didn’t even reach payment). A funnel drop without a decline spike usually means customers abandoned earlier (price shock, shipping cost, slow page).
Page cap (PayPal axis)10,000 transactions per call. 24-hour windows on stores doing > 10k attempts/day truncate.
Page cap (commerce axis)Platform-specific. Shopify pagination on /orders is 250 per page; BC /orders is 250 per page; Adobe varies.
Time window24H (rolling 24 hours, both axes).
Alert triggerdecline > +5pp AND funnel drop > 5pp (both must be true simultaneously).
Rolesowner, finance, marketing

​
Calculation

Calculated automatically from your PayPal 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 US-based fashion brand on Shopify, with PayPal Express as a checkout option alongside Shop Pay (Stripe). The 24-hour window is 12 Apr 26. Scenario A: real revenue loss (alert fires) Prior 24h baseline:
MetricValue
PayPal decline rate (PP axis)5.2%
Shopify checkout completion (commerce axis)68.4%
Current 24h:
MetricValue
PayPal decline rate11.8%
Shopify checkout completion61.2%
Δ decline rate    = 11.8% − 5.2% = +6.6pp     (> +5pp ✓)
Δ funnel rate     = 61.2% − 68.4% = −7.2pp    (drop > 5pp ✓)

ALERT FIRES. Both conditions met.
What this means: real customers are reaching the Shopify checkout, choosing PayPal Express, AND being declined. The 7.2-percentage-point funnel drop confirms the decline isn’t just blocked fraud, it’s blocking customers who would have bought. The merchant should: (a) open PP Decline Event Codes, find the dominant subject; (b) if payer_authentication_required dominates, the 3DS provider has an outage and a chunk of legitimate customers can’t complete; (c) if denied_by_risk dominates AND the decline pattern looks normal-customer-not-fraud, PayPal Risk has tightened a rule that’s catching legitimate buyers; (d) consider showing customers a “try Shop Pay or Apple Pay instead” offer at the PayPal-decline page to recover the funnel. Scenario B: blocked fraud (alert does NOT fire) Prior 24h baseline:
MetricValue
PayPal decline rate5.2%
Shopify checkout completion68.4%
Current 24h:
MetricValue
PayPal decline rate14.1%
Shopify checkout completion67.9%
Δ decline rate    = 14.1% − 5.2% = +8.9pp     (> +5pp ✓)
Δ funnel rate     = 67.9% − 68.4% = −0.5pp    (drop < 5pp ✗)

ALERT DOES NOT FIRE. Decline spike, but no real customer impact.
What this means: the decline spike is real but it’s hitting attempted-but-not-completing-checkout traffic, almost certainly a card-testing attack. The fraudsters are loading product into a cart, hitting PayPal, getting denied by PayPal Risk, and not coming back. Real customers are sailing through. The decline spike alert may have fired (PP Alert Decline Spike) but THIS card stayed quiet, the merchant should treat the alert as informational only and watch PP Fraud Velocity to confirm the attack signature. Scenario C: funnel drop without decline (alert does NOT fire) Prior 24h baseline:
MetricValue
PayPal decline rate5.2%
Shopify checkout completion68.4%
Current 24h:
MetricValue
PayPal decline rate5.4%
Shopify checkout completion60.1%
Δ decline rate    = +0.2pp     (< +5pp ✗)
Δ funnel rate     = −8.3pp     (drop > 5pp ✓ but PayPal flat)

ALERT DOES NOT FIRE. Funnel issue is upstream of payment.
What this means: customers are abandoning before they even reach payment. PayPal isn’t the problem. Likely causes: a price increase pushed today, a shipping-cost change, a slow product page, or a free-shipping threshold hike. Investigate the commerce platform’s earlier funnel stages (cart → shipping → payment), not the payment processor. The card’s value is binary correlation logic, it specifically catches the case where BOTH signals move together, which is the only scenario where PayPal declines are causing real customer-side revenue loss.

​
Sibling cards merchants should reference together

CardWhy pair it with PP XC Decline vs Funnel
PP Decline RateThe PayPal-side absolute view. This card adds the cross-channel correlation.
PP Alert Decline SpikeThe PayPal-only spike alert. This card is the “is the spike real?” filter.
PP Revenue at Risk (live)The dollar-weighted live signal. This card confirms the dollars are real customer loss not blocked fraud.
PP Fraud VelocityWhen the alert DOESN’T fire (decline spike + flat funnel), this card surfaces the fraud attack signature.
PP Decline Event CodesWhen the alert DOES fire, first card to drill into. Tells you what’s blocking real customers.
Shopify Conversion RateThe Shopify-side funnel signal. This card uses checkout completion specifically; conversion rate is broader.
BigCommerce Conversion RateBC-side equivalent.
Adobe Commerce Conversion RateAdobe-side equivalent.
PP XC Recoverable RevenueThe 30-day forecast version of decline-driven loss. This card is “now”; that one is “month over month”.

​
Reconciling against the vendor’s own dashboard

Where to look in PayPal Business and your commerce platform: This is a Vortex IQ-derived signal that combines two upstream sources, neither of which has a native equivalent. The closest comparable views per side: PayPal axis: Commerce axis:
  • Shopify: Analytics → Reports → “Online store conversion over time” or “Checkout funnel”. The “Reached checkout” → “Sessions converted” ratio.
  • BigCommerce: Analytics → Conversions → “Abandoned cart” or “Checkout abandonment”.
  • Adobe Commerce: Reports → Sales → “Abandoned carts” report.
Other views that look like this but aren’t:
  • “Cart abandonment rate” includes pre-checkout abandons (cart → shipping); we focus on the checkout stage specifically (where payment actually happens).
  • “Site conversion rate” includes session-level abandonment from the homepage onwards; we focus on the bottom-of-funnel where PayPal is involved.
  • PayPal’s own “Approval rate” looks similar to decline rate but uses a different denominator (only authorised vs only attempted).
Why our signal may legitimately differ from a hand-correlation:
ReasonDirection of divergenceWhat to do
Time alignment. PayPal axis uses UTC; commerce platform uses store timezone. Boundary days may shift one axis vs the other.Boundary effectsAlign both views to the same UTC window for verification.
Funnel definition. We use “checkouts started → orders placed” but each commerce platform has its own definition of “checkout started” (cart filled vs payment-screen reached).Platform-specific driftVerify the commerce platform’s funnel definition matches our usage.
PayPal-only attribution. The decline axis tracks only PayPal declines, the funnel axis tracks ALL checkouts (Stripe, Shop Pay, Apple Pay, manual transfer, gift cards). On stores where PayPal is a small share of checkout, a PayPal decline spike may not move the overall funnel meaningfully even when it’s real.Vortex IQ may under-fire on PayPal-minority storesUse PP Alert Decline Spike for the PayPal-isolated view.
Refresh lag. Both sides refresh independently; the cross-correlation is computed from the most recent values, which may be 5-15 minutes apart.TinyWait for next refresh.
Page caps. PayPal axis caps at 10k transactions per call; commerce axis caps at 250 per page on Shopify / BC. Heavy-volume stores may see truncation on either axis.Either directionUse shorter windows.
Cross-connector reconciliation:
ComparisonExpected relationshipWhen divergence is legitimate
pp_xc_decline_vs_funnel ↔ stripe.stripe_xc_decline_vs_funnelThe Stripe twin. Different traffic lanes; can fire independently.A PayPal-only fire usually means PayPal-side issue (Risk rule, eCheque, PayPal-traffic ad campaign). A both-fire usually means upstream (3DS network outage, your checkout deploy).
pp_xc_decline_vs_funnel ↔ commerce platform funnelThis card USES the commerce funnel as its commerce axis. Internal identity.If the commerce funnel signal is broken or stale, this card is unreliable.
pp_xc_decline_vs_funnel ↔ pp_revenue_at_risk_liveWhen XC fires, Revenue at Risk should also be elevated (real customer loss has real dollar exposure).Revenue at Risk fires more sensitively than XC; it’s normal for Revenue at Risk to fire alone (small-volume hours where the funnel signal is too noisy).
This card is Vortex IQ-derived, neither PayPal nor your commerce platform offers a native cross-channel correlation alert. The closest equivalent is manually overlaying PayPal Activity and Shopify checkout-funnel charts in the same time period, which is what merchants did before this card existed.

​
Known limitations / merchant FAQs

The PayPal decline-spike alert fired but this card stayed quiet, what does that mean? The decline spike is real (PayPal-side) but it’s not affecting checkout completion. Most likely it’s blocked fraud, attempted-but-not-completed traffic. Your real customers are sailing through. No urgent action needed; cross-check PP Fraud Velocity to confirm the attack signature. Treat the decline spike alert as informational only. This card fired but PayPal decline alert didn’t, can that happen? Rarely, only if the decline spike was just barely below the σ threshold but the funnel impact is real. Usually both fire together. If only this card fires, the issue may be a slow attrition pattern rather than a sudden spike, check PP Decline Rate for steady-state level. Why both axes need to move > 5 percentage points? To filter noise. Small movements on either axis are normal hour-to-hour. A 5pp jump in decline rate (from 5% to 10%) is statistically meaningful even on small stores; a 5pp drop in funnel completion (from 68% to 63%) is similarly meaningful. The 5pp + 5pp logical AND ensures the alert only fires when something real is happening on both sides. What if PayPal is a tiny share of my checkout, will this card ever fire? Possibly never, even when there’s a real PayPal-side issue. If PayPal is < 10% of your checkout traffic, a complete PayPal outage might only move your overall funnel by 1-2pp because most customers are using Stripe or Shop Pay. For PayPal-minority stores, PP Alert Decline Spike and PP Revenue at Risk (live) are better trigger cards; this XC view is most valuable when PayPal is > 20% of checkout. My funnel dropped but my PayPal rate is fine, what’s happening? Customers are abandoning before they reach payment. Possible causes: a price increase pushed today, a shipping-cost change, a slow product page or checkout, a free-shipping threshold hike, a coupon code that broke, a 3DS challenge introduced on Stripe (Shop Pay’s primary path). Investigate the commerce platform’s earlier funnel stages, not the payment processor. Why doesn’t this card use Shopify’s “PayPal-specific checkout completion”? Shopify doesn’t break out checkout completion by payment method in its public analytics. We use overall checkout completion as the commerce-side signal. On stores where PayPal is dominant, the overall funnel mostly reflects the PayPal experience; on stores where PayPal is minority, the funnel signal is noisier with respect to PayPal specifically. My Adobe Commerce store, does this card work? Yes. The commerce axis adapts to whichever platform is connected: Shopify, BigCommerce, or Adobe Commerce. The funnel definition is platform-specific (Shopify: orders ÷ checkouts started; BC: orders ÷ checkouts started; Adobe: quote_converted ÷ quote_active) but the card’s logic is identical. The card fires every Friday afternoon, why? Two common reasons: (1) end-of-week ad-platform optimisation moments where ad networks shift bidding to higher-risk-but-higher-volume traffic, both decline rate and funnel may move together; (2) seasonal patterns where Friday-afternoon shoppers (often distracted, mobile) abandon at higher rates AND PayPal sees more guest checkout (which declines more). If the pattern is recurring and you’ve investigated the cause, suppress alerts during that window. Should I integrate this card with my paging system? Yes if you want a high-quality “wake the on-call” trigger. The dual-condition AND logic makes false positives rare; when it fires, real customer revenue is at risk. Most ops teams page on this card and treat the simpler PP Alert Decline Spike as informational-only. Does the alert window of 24h smooth out spikes too much? For some use cases, yes. The 24h rolling window catches sustained issues (a PayPal Risk rule change applied this morning hits all day) but smooths short spikes (a 30-minute 3DS provider blip washes out). Pair with PP Revenue at Risk (live) which uses a 1-hour window for short-spike detection.

​
Tracked live in Vortex IQ Nerve Centre

Decline Spike vs Checkout Funnel Drop is one of hundreds of KPI pulses Vortex IQ tracks across PayPal 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.