Skip to main content
Card class: Cross-Channel • Category: Payment Gateway
Predicted chargeback $ over the next 30 days based on open inquiries and any commerce-sibling shipment delays that historically convert to INR disputes.

​
At a glance

Predicted dollar value of chargebacks over the next 30 days, derived from two leading indicators: (a) currently open PayPal inquiries that historically convert to formal disputes / chargebacks, (b) commerce-platform shipping delays that historically generate INR disputes 1-3 weeks later. The “what’s about to happen” view, gives merchants 2-4 weeks of runway to refund pre-emptively or correct fulfilment.
The formulaforecast_$ = (open_inquiries × historical_inquiry_to_dispute_rate × avg_dispute_value) + (current_shipping_delays × historical_delay_to_INR_rate × avg_INR_value). Two leading-indicator pools combined into a 30-day forward dollar projection.
Pool A (open inquiries)T19 events with status IN [P, WAITING_FOR_SELLER_RESPONSE] AND classified as PayPal Inquiry (not yet escalated). Multiplied by your store’s historical inquiry-to-formal-dispute conversion rate (typically 30-50%).
Pool B (shipping-delay leading indicator)Commerce-platform orders currently in shipping-delayed state (>3 days past expected ship). Multiplied by your store’s historical delay-to-INR conversion rate (from PP XC INR to Fulfilment calibration).
Why this card mattersChargebacks have a 1-3 week lag between cause (delay or unhappy buyer) and consequence (filed dispute). This card surfaces the consequence before it lands, giving the merchant time to refund pre-emptively (closes the case at refund cost rather than chargeback cost + fee + dispute-rate hit).
Refunds (T11) issued todayNOT in the forecast. A refund issued before a dispute escalates kills the dispute pool. The card is sensitive to current open state.
Disputes already lostNOT in the forecast. Lost disputes have already hit; this card is forward-looking only.
Pending status (P) handlingPool A counts T19 with status P (under-review by PayPal, may resolve in either direction). Pool B operates on currently-pending commerce-side state.
CurrencyMulti-currency without FX. Forecasts are summed in original currency. Multi-currency stores get per-currency forecasts.
Seller ProtectionCoverage doesn’t reduce the forecast directly (the dispute will still fire). It reduces the eventual cash hit if the dispute is lost; a Seller-Protection-eligible loss is reimbursed.
Why the conversion rates use historicals, not industry benchmarksEach store has a different inquiry-to-dispute conversion (your customer-service responsiveness changes it) and delay-to-INR rate (your customer-comms during delays change it). The forecast self-calibrates over time as the engine watches your actual conversion behaviour.
Confidence bandForecasts are point estimates, not certainties. Real chargebacks land within ±30% of forecast about 70% of the time (calibrated against backtested data). Spikes (Black Friday, weather events) widen the band.
Page cap10,000 transactions per call. 30-day forecast windows on heavy-volume stores see truncation in the historical calibration data.
Time window30D (forward-looking, predicts next 30 days).
Alert trigger> $2k forecast. Threshold calibrated to give merchants enough runway to refund pre-emptively without firing on noise.
Rolesowner, finance, operations

​
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 home-goods merchant on Shopify, dealing with the aftermath of a January snowstorm + USPS regional disruption. Today is 12 Apr 26. Pool A: open PayPal inquiries The Resolution Center currently shows:
Inquiries by reasonCountAvg dispute value
INR (Item Not Received)8$87
SNAD (Not As Described)4$124
Unauthorised1$245
Bank inquiry2$340
Historical conversion rate (this merchant, 12-month rolling): 38% of inquiries escalate to formal disputes. 
Pool A forecast
  = 15 inquiries × 38% × weighted_avg_value
  = 5.7 disputes × $124 (weighted)
  = $707
Pool B: shipping-delay leading indicator Shopify currently shows 142 orders in shipping-delayed state (>3 days past expected ship date), mostly from the recent USPS route disruption. Historical calibration: 6.5% of shipping-delayed orders convert to INR disputes within 21 days; weighted average dispute value is $89. 
Pool B forecast
  = 142 delayed orders × 6.5% × $89
  = 9.2 disputes × $89
  = $819
Combined forecast 
PP XC Chargeback Forecast
  = Pool A + Pool B
  = $707 + $819
  = $1,526 / next 30 days

  Below $2k alert threshold; card does NOT fire (just barely).
But add the historical 12-month average chargeback baseline of 890/monthandyougeta∗totalexpected∗cashhitofabout890/month and you get a *total expected* cash hit of about 2,416 over the next 30 days. The card surfaces the additional leading-indicator risk above baseline. Six things worth noticing:
  1. The forecast is below the $2k alert but uncomfortably close. A few more inquiries this week or another shipping disruption pushes it over. The merchant should treat this as “elevated but manageable” and start working the queue.
  2. Pool B is larger than Pool A. The shipping-delay leading indicator ($819) is the bigger threat. This is consistent with PP XC INR to Fulfilment showing high INR-shipping correlation. The remediation is operational (carrier diversification, customer comms) not customer-service.
  3. **Pre-emptive refunds on Pool A would clear 707oftheforecast.∗∗Eachopeninquiryrefundedtodayclosesthatcaseasresolution−by−agreement(nodisputefiled,noimpactondisputerate).Cost:15× 707 of the forecast.** Each open inquiry refunded today closes that case as resolution-by-agreement (no dispute filed, no impact on dispute rate). Cost: 15 × ~140 = ~2,100inrefunds.Benefit:2,100 in refunds. Benefit: 707 in avoided disputes + ~$200 in chargeback fees + the dispute-rate hit. ROI is positive only on cases likely to lose; merchants typically refund cases with weak evidence (no tracking uploaded, customer wronged) and defend cases with strong evidence.
  4. Pool B can’t be easily refunded pre-emptively. The 142 delayed orders haven’t yet generated disputes; they’re just slow shipments. Refunding them all would be expensive and most won’t dispute. The lever here is customer comms: proactive emails (“your order is delayed due to USPS issues, here’s your updated tracking”) prevent the customer from going to PayPal in frustration. Industry data: well-communicated delays reduce INR conversion by 40-60%.
  5. The forecast is point estimate. Confidence band is roughly ±30%, so the real outcome over the next 30 days could be 1,068−1,068 - 1,984. Spikes (another snowstorm, a viral negative review, a Black Friday-scale traffic event) widen the band further. Don’t over-react to small movements; do react to sustained elevation.
  6. The merchant’s historical baseline ($890/month) includes everything this card forecasts plus baseline noise. The card is most useful as a trend signal: forecast rising 50% month-over-month means leading indicators are deteriorating, even if absolute numbers are modest.
If the next refresh shows pool B grow to 200 delayed orders (carrier issue worsening), the forecast climbs to ~$2,000+ and the alert fires. The merchant has 2-4 weeks of runway to fix the carrier issue OR to refund pre-emptively, before the disputes actually land.

​
Sibling cards merchants should reference together

CardWhy pair it with PP XC Chargeback Forecast
PP Disputes OpenLive queue, this card uses open inquiries as Pool A.
PP XC INR to FulfilmentCalibrates Pool B (delay-to-INR conversion rate). High correlation = forecast is more reliable.
PP Dispute RateThe headline rate the forecast eventually contributes to. Use forecast to manage rate proactively.
PP Dispute ValueHistorical actual chargeback dollars. Compare against forecast to validate calibration.
PP Buyer Protection Win RateWin-rate adjusts the cash impact of the forecast (high win-rate = lower expected cash loss).
PP Seller Protection CoverageCoverage absorbs Seller-Protection-eligible losses; high coverage = lower net cash hit.
PP Refund RatePre-emptive refunds clear Pool A. Rising refunds with falling forecast = your cs team is working it.
PP Alert Dispute ThresholdThe regulatory escalation. If forecast points toward crossing the 0.9% rate alert, urgent intervention needed.
Shopify Order Fulfilment TimeThe commerce-side ship-time gauge. Pool B’s leading indicator.
PP Dispute Rate TrendHistorical trend; pair with this forward forecast for full picture.

​
Reconciling against the vendor’s own dashboard

Where to look in PayPal Business and your commerce platform: PayPal Business does NOT publish a chargeback forecast; this is a Vortex IQ-derived projection from leading indicators. The closest reference views per side: PayPal axis (Pool A, open inquiries): Commerce axis (Pool B, shipping delays):
  • Shopify: Apps → Fulfilment SLA reports, or custom view of Order.fulfillments for orders past expected ship date.
  • BigCommerce: Analytics → Fulfilment → orders past SLA.
  • Adobe Commerce: Reports → Sales → orders in “Processing” status past expected ship.
Other views that look like this but aren’t:
  • “Open disputes count” is current-state only, not forecast.
  • Generic risk-scoring dashboards from third-party tools (Signifyd, Forter) score individual transactions, not aggregate forecast.
  • PayPal’s “Account health” tile shows historical performance, not forward projection.
Why our forecast may legitimately differ from a hand-built model:
ReasonDirection of divergenceWhat to do
Conversion-rate calibration. We use this merchant’s historical inquiry-to-dispute and delay-to-INR rates. These can shift over time as your customer-service / customer-comms practices change.Either directionUse PP Dispute Rate Trend to see whether actuals are tracking the forecast; if forecast is consistently high or low, the historical baseline needs refresh.
Confidence band. Forecasts are point estimates; actuals fall within ±30% about 70% of the time. Spikes (Black Friday, weather events, viral negative review) widen the band.Real outcome may differUse the forecast as a budget input not a precise prediction.
Refund-induced contraction. If the merchant aggressively pre-emptively refunds open inquiries, Pool A drops faster than the forecast tracks (the forecast is computed before the refund clears the case).Forecast over-statesRefresh the card after batch-refunding.
Seasonality. The historical baseline may not capture seasonal patterns well (BFCM, January returns, weather seasons). The forecast over-fits to the trailing window’s character.Forecast may under-fire during quiet seasons or over-fire approaching known busy seasonsManually adjust expectations during seasonal transitions.
Page cap. Both axes have caps; very heavy-volume stores see truncation that distorts the conversion-rate calibration.Either directionUse shorter calibration windows or warehouse-backed view.
Cross-connector reconciliation:
ComparisonExpected relationshipWhen divergence is legitimate
pp_xc_chargeback_forecast ↔ Stripe equivalentStripe’s chargeback forecast (when available) uses a similar shape but different leading indicators (Stripe’s open evidence-needed cases + Stripe-specific shipping signals). The two forecasts are independent.A PayPal-only elevated forecast is normal; PayPal’s Buyer Protection makes inquiry filing easier, so PayPal often shows higher forward exposure for the same actual customer-dissatisfaction level.
pp_xc_chargeback_forecast ↔ pp_dispute_value historicalForecast should approximate the next 30 days of actual dispute_value within ±30%.If forecast is consistently 50%+ off, calibration is broken; check inquiry-to-dispute rate and delay-to-INR rate.
pp_xc_chargeback_forecast ↔ pp_xc_inr_to_fulfilmentWhen INR-to-fulfilment correlation is high (> 0.6), Pool B is reliable; when correlation is low, Pool B is noisier and forecast accuracy drops.The card surfaces a confidence indicator alongside the forecast for transparency.
pp_xc_chargeback_forecast ↔ commerce platform return-rate forecastForecasts are different shapes (returns are pre-dispute customer behaviour); should move together loosely.Rising returns + flat chargeback forecast = customers are choosing returns over disputes (good); flat returns + rising forecast = customers can’t reach support (bad).
This card is a Vortex IQ-derived forecast. Neither PayPal nor commerce platforms publish chargeback predictions; the leading-indicator approach is proprietary to Vortex IQ but uses transparently-defined inputs (open inquiries, shipping delays) that merchants can hand-validate.

​
Known limitations / merchant FAQs

How accurate is this forecast? Calibrated against backtested data, the actual 30-day chargeback dollar value lands within ±30% of the forecast about 70% of the time. Spikes (Black Friday, weather events, viral PR moments) widen the confidence band; quiet seasonal periods narrow it. Treat the forecast as a budget input, not a precise prediction. Should I refund every open inquiry pre-emptively to clear Pool A? No, only the ones likely to lose. Refunding a case where you have strong evidence (delivery confirmation, listing accuracy, signature) is leaving money on the table. Refund the cases with weak evidence (no tracking uploaded, customer wronged, item genuinely defective). Industry rule of thumb: refund anything where the dispute would cost you more than the order value plus chargeback fee. Can I reduce the Pool B forecast without refunding? Yes, by improving customer comms during shipping delays. Industry data: well-communicated delays reduce INR conversion by 40-60%. Send proactive emails (“your order is delayed due to USPS issues, here’s updated tracking, click here for a partial-shipping-credit”); offer in-flight refund options; partner with carriers that provide better tracking visibility. The forecast self-recalibrates over weeks as customer-comms improvements pay off. The forecast is 1,800anddroppedto1,800 and dropped to 1,200 last week, what happened? Three usual causes: (a) the merchant cleared inquiries (Pool A shrank via refunds or successful defences), (b) shipping delays resolved (Pool B shrank as carriers caught up), or (c) historical conversion rates ticked down (your customers are converting less aggressively from inquiry to formal dispute). Cross-check Pool A and Pool B inputs to see which lever moved. **Why is the alert at 2kspecifically?∗∗Calibratedtogivemerchantsenoughrunway.Below2k specifically?** Calibrated to give merchants enough runway. Below 2k forecast, the manual intervention cost (operations team time spent triaging) outweighs the avoided-cost benefit. Above $2k there’s enough leverage in the lookahead to justify the work. The threshold is a heuristic; high-margin / high-LTV businesses might want a lower threshold (every dispute matters more), low-margin / high-volume might use a higher one. Does the forecast include disputes that already escalated past inquiry stage? Already-formal disputes are tracked on PP Disputes Open, not here. This card is leading indicators only (inquiries that might escalate, delays that might generate INR). The two cards complement: open disputes for “what’s already happening”, forecast for “what’s about to happen”. My multi-currency PayPal account, does the forecast work? Yes, multi-currency stores get per-currency forecasts. The conversion-rate calibration is currency-agnostic (a 38% inquiry-to-dispute rate holds regardless of currency); the dollar weighting uses original currency without FX. A multi-currency account’s headline forecast might look like “$1,200 + €400 + £200” expected over the next 30 days. The forecast says $0 but I’m getting disputes anyway, what’s broken? Likely calibration. If your historical conversion rates are very low (you defended every recent inquiry successfully), Pool A multiplies to zero even when current open inquiries are real. The card needs ~6 months of historical data for stable calibration; new merchants or merchants with recent process changes will see flatter forecasts. Refresh the calibration window after major operational changes. Should I integrate this with my refund-policy decision logic? Yes if you want a smart pre-emptive-refund pipeline. Rule of thumb: if the forecast’s dollar contribution from a specific inquiry is > 50% of the order value, refund pre-emptively (you’re going to lose more than you’d save by defending). Industry tools like Chargeback Pros, Justt, etc. automate this decision; for smaller merchants a weekly manual review of the queue + forecast contribution is sufficient. Does the forecast account for Seller Protection? The forecast surfaces gross dispute exposure (dollar value of disputes likely to fire). The cash impact depends on Seller Protection coverage. A high-coverage merchant (PP Seller Protection Coverage > 80%) will see a smaller cash hit than the forecast suggests because PayPal absorbs the eligible portion. The forecast doesn’t subtract that automatically because the dispute count still hits your dispute rate regardless of who pays the cash. Black Friday is approaching, will the forecast spike? Probably yes. Historical patterns show BFCM increases inquiry filings (more new customers, more high-velocity orders) and shipping delays (carrier capacity stretched). Use the forecast as one input among several (historical BFCM patterns, shipping carrier capacity contracts, customer-service staffing) rather than a precise BFCM-day projection. The card will recalibrate after the season ends.

​
Tracked live in Vortex IQ Nerve Centre

Chargeback Risk Forecast (next 30d) 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.