> ## 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. # Dispute Threshold Watch, PayPal > Dispute Threshold Watch for PayPal stores. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it. **Metrics type:** [Key Metrics](/nerve-centre/overview#metrics-types-explained) • **Category:** [Payment Gateway](/nerve-centre/connectors#connectors-by-type) ## At a glance > Regulatory-threshold watch for the PayPal dispute rate, fires when the rolling 30-day rate climbs above **0.9%** (90% of the Visa/Mastercard 1.0% chargeback monitoring threshold). The headroom alert: gives you 0.1 percentage points of buffer to act before the regulatory clock starts. Pair card to [PP Dispute Rate](/nerve-centre/kpi-cards/paypal/dispute-rate), same numerator and denominator, but explicitly framed against the network ceiling. | | | | --------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **The formula** | `COUNT(event_code STARTS T19) ÷ COUNT(event_code STARTS T00 AND status='S') × 100`. Same shape as PP Dispute Rate, fires at > 0.9% threshold instead of computing as a gauge. | | **Event code filter** | T19xx (numerator: all dispute event sub-types). T00xx with `status='S'` (denominator: successful payments). | | **Why 0.9%, not 1.0%?** | Headroom. Visa's chargeback monitoring programme triggers at 1.0% in monthly volume; Mastercard's matches; PayPal's seller performance system is calibrated to the same 1.0% threshold. By alerting at 0.9% you get 0.1 percentage points of buffer to identify the cause and remediate before regulatory consequences (higher fees, mandatory rolling reserves, eventual merchant-account termination if uncorrected within 90 days). | | **What "Visa cap" means in practice** | Visa's Chargeback Monitoring Program (VCMP) places merchants exceeding 1% chargeback rate AND 100+ chargebacks in any month into "Early Warning" status (mandatory remediation plan), then "Standard" status (additional fees), then "High Risk" status (potential card-network termination). Mastercard's Excessive Chargeback Programme follows similar logic. PayPal aligns enforcement to these thresholds. | | **Refund treatment** | Refunds (T11) are NOT in the numerator; they're customer returns, not disputes. A merchant who refunds aggressively keeps disputes (and this card) low. | | **Pending status (P) handling** | Pending payments are NOT in the denominator (only S). | | **Currency** | **n/a (rate, currency-neutral).** Multi-currency PayPal accounts get a single, valid threshold check across all currencies. | | **Seller Protection** | Doesn't change whether a dispute counts toward this rate; it changes whether you'll *lose money* on disputes that count. See [PP Seller Protection Coverage](/nerve-centre/kpi-cards/paypal/seller-protection-coverage-rate). | | **Why a SEPARATE alert card from PP Dispute Rate?** | PP Dispute Rate is a gauge (read continuously by ops / finance). This card is a **regulatory-threshold trigger** (fires only when crossed). They share the same calculation but serve different audiences: the gauge for daily monitoring, this card for "the regulator is paying attention" escalation. | | **Page cap** | 10,000 transactions per call. Disputes are sparse so cap rarely matters; if you have > 10k disputes in 30 days you have a much bigger problem. | | **Time window** | `30D` (rolling 30-day window, matches the Visa monitoring window). | | **Alert trigger** | `> 0.9%` (90% of the Visa/Mastercard 1.0% cap). | | **Roles** | owner, finance | ## 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 digital-goods + fashion brand running PayPal alongside Stripe. PayPal carries the higher-risk traffic mix (international + younger + bank-funded + digital-goods buyers, all dispute-prone). 30-day window: 14 Mar 26 to 12 Apr 26. The transactions feed: | Event family | Count | Notes | | ---------------------------------- | ----- | --------------- | | T00 successful payments (status=S) | 4,820 | The denominator | | T19 dispute events | 47 | The numerator | ```text theme={null} PP Alert Dispute Threshold numerator = 47 denominator = 4,820 rate = 47 ÷ 4,820 × 100 = 0.975% Threshold check 0.975% > 0.9% → ALERT FIRES 0.975% < 1.0% → still under regulatory cap (just) ``` Drilling into the 47 disputes by reason: | Reason | Count | Pattern | | ----------------------- | ----- | ----------------------- | | INR (Item Not Received) | 21 | Logistics signal | | SNAD (Not As Described) | 14 | Listing accuracy signal | | Unauthorised | 8 | Fraud signal | | Bank chargeback (Visa) | 4 | Issuer-routed | Six things worth noticing: 1. **0.975% is above the alert but below the regulatory cap.** Vortex IQ pings the merchant; they have \~0.025 percentage points (about 1.2 disputes) of buffer before they cross 1.0%. Each new dispute filed in the next few days could push them over. 2. **INR dominates at 45% of disputes.** 21 of 47 are "package didn't arrive". For a multi-product store this points to fulfilment / shipping issues (carrier reliability, address validation, "in-transit" tracking that never shows delivered). The merchant should: (a) audit recent shipping failures with the carrier, (b) verify [PP Seller Protection Coverage](/nerve-centre/kpi-cards/paypal/seller-protection-coverage-rate), tracking-uploaded orders are protected against INR. If coverage is \< 80%, the fix is "upload more tracking", which is operational, not customer-facing. 3. **SNAD at 30% (14 cases) points to listing accuracy issues.** Photos that don't match the product, missing variant info, sizing chart errors. The merchant should audit the top-10 SNAD-prone SKUs (group disputes by `transaction_subject`'s product context) and tighten listings. 4. **Unauthorised at 17% (8 cases) is a fraud signal.** [PP Fraud Velocity](/nerve-centre/kpi-cards/paypal/fraud-velocity) and [PP Unauthorised Dispute Rate](/nerve-centre/kpi-cards/paypal/unauthorised-dispute-rate) carry the deeper investigation; clustered IPs / billing-shipping mismatches indicate card-testing. 5. **Crossing 1.0% triggers regulatory consequences.** If the rate hits 1.0% in any of the next two months, PayPal places the merchant on its watchlist (not yet termination, but additional scrutiny + a potential rolling reserve held against future payouts). Visa enrols the merchant in VCMP; chargeback fees rise; if the rate stays above 1.0% for 4+ consecutive months, card-network privileges can be revoked. 6. **The remediation playbook (with the 0.9% buffer):** (a) refund any open dispute likely to lose, refunds close cases without contributing to the rate; (b) freeze high-risk product categories or shipping methods causing INR concentration; (c) tighten PayPal Risk settings to block the email/IP patterns driving Unauthorised disputes; (d) monitor [PP Dispute Rate Trend](/nerve-centre/kpi-cards/paypal/dispute-rate-trend) daily, the rolling rate should bend down within 7-14 days if remediation is working. If next week brings 5 more disputes (hypothetical: 52 ÷ 4,820 = 1.08%), the merchant has crossed the regulatory cap. PayPal will likely place them on review; Visa's monitoring kicks in. The 0.9% alert exists exactly to prevent this, the 30-day window means each new dispute compounds against the rate for a full month. ## Sibling cards merchants should reference together | Card | Why pair it with PP Dispute Threshold Watch | | ---------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------ | | [PP Dispute Rate](/nerve-centre/kpi-cards/paypal/dispute-rate) | Same calculation, gauge framing. This card fires at threshold; that one shows the gauge for steady monitoring. | | [PP Dispute Reason Mix](/nerve-centre/kpi-cards/paypal/dispute-reason-code-mix) | When this fires, first card to open. Tells you whether the cause is logistics (INR), listings (SNAD), or fraud (Unauthorised). | | [PP Dispute Rate Trend](/nerve-centre/kpi-cards/paypal/dispute-rate-trend) | Monthly trend so you can see deterioration approaching before this card fires. | | [PP Disputes Open](/nerve-centre/kpi-cards/paypal/open-disputes) | Live queue. Pre-emptive refunds on open cases keep them from contributing to the rate (refunds close in your favour). | | [PP Buyer Protection Win Rate](/nerve-centre/kpi-cards/paypal/buyer-protection-win-rate) | The defence-effectiveness card. If you win \< 35% of disputes, your evidence packs need work. | | [PP Refund Rate](/nerve-centre/kpi-cards/paypal/refund-rate) | Refunds prevent disputes. A generous refund policy keeps this card quiet. | | [PP Alert Dispute Velocity](/nerve-centre/kpi-cards/paypal/dispute-velocity-alert) | Hourly velocity alert. Spots an attack before it shows up here. | | [PP Payment Health Score](/nerve-centre/kpi-cards/paypal/payment-health-score) | The composite. Disputes at 0.9% drop the composite by \~22 points (×50 amplifier). | | [Stripe Dispute Threshold Alert](/nerve-centre/kpi-cards/stripe/dispute-threshold-watch) | The Stripe twin. Same Visa/Mastercard 1.0% cap applies to both processors. | ## Reconciling against the vendor's own dashboard **Where to look in PayPal Business:** * [PayPal Seller Performance dashboard](https://www.paypal.com/businessmanage/sellerperformance) is the single most important screen here. PayPal surfaces your dispute rate against its OWN thresholds (calibrated to align with Visa/Mastercard) and flags you publicly if you're approaching trouble. * [PayPal Resolution Center](https://www.paypal.com/disputes) for the case-level view, count cases in the trailing 30 days against payment count. * [PayPal Business → Reports → Disputes report](https://business.paypal.com/merchantdata/reportHome) (where available) for an aggregated monthly view. * [Visa Chargeback Monitoring Programme docs (regulatory context)](https://www.visa.com/) if you want to read the actual regulatory programme details. Other views that look like this but aren't: * "Refunds and reversals" feed includes T11 refunds, NOT dispute events. * "Cases" tile groups disputes + claims + escalations + abandoned inquiries. * "Risk dashboard" surfaces fraud-flagged-blocked transactions (declines), not disputes. **Why our number may legitimately differ from PayPal Seller Performance:** | Reason | Direction of divergence | What to do | | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------ | -------------------------------------------------------------- | | **Window definition**. We use rolling 30 days. PayPal Seller Performance often uses calendar-month or aligned-30-day windows. Around month boundaries the two views diverge by a few hundredths of a percentage point. | Either direction | Compare equal windows. | | **Dispute counting**. PayPal sometimes excludes Inquiries from its formal "dispute rate" if they closed without escalating. Our card counts all T19 events including resolved Inquiries. | Vortex IQ may be **slightly higher** | Compare against the formal "Disputes" count in PayPal Reports. | | **Time zone**. PayPal Business uses your account-configured timezone; Vortex IQ uses UTC. | Boundary effects on month-edge cases | Compare equal date ranges. | | **Status sync timing**. A case the merchant just refunded may still show in our 30-day count for up to 24 hours. | Vortex IQ may be **slightly higher** | Wait for next refresh. | | **Page cap** (10,000 transactions per call). Sparse for disputes, more relevant on the denominator (successful payments) for very large stores. | Either direction | Use shorter windows or warehouse-backed view. | **Cross-connector reconciliation:** | Comparison | Expected relationship | When divergence is legitimate | | -------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `pp_alert_dispute_threshold` ↔ [`stripe.stripe_alert_dispute_threshold`](/nerve-centre/kpi-cards/stripe/dispute-threshold-watch) | Both subject to the same 1.0% Visa/Mastercard regulatory cap. PayPal usually fires first because PayPal's Buyer Protection makes filing easier. | A PayPal-only fire usually means a customer-satisfaction issue concentrated in PayPal-paid orders (international, mobile). Both firing simultaneously usually means a fraud attack or a bad product launch. | | `pp_alert_dispute_threshold` ↔ commerce platform return rate | Loosely related, generous returns reduce disputes. | Rising returns + this card firing = product/listing/fulfilment problem. Falling returns + this card firing = customers can't reach your support and are escalating directly. | | `pp_alert_dispute_threshold` ↔ [`paypal.pp_payment_health_score`](/nerve-centre/kpi-cards/paypal/payment-health-score) | Composite component. When this card fires (rate \~ 0.9%), the composite has dropped about 22 points (×50 amplifier on the dispute rate). | Internal identity, must move together. | **Quick rule for support tickets:** if a merchant says *"PayPal Seller Performance shows my dispute rate is fine but your card is alerting"*, 80% of the time the difference is window alignment. Use rolling-30 vs calendar-month windows on equal date ranges. ***
Documentation cross-reference (for agencies running multiple platforms) The Stripe twin is [`stripe.stripe_alert_dispute_threshold`](/nerve-centre/kpi-cards/stripe/dispute-threshold-watch). Same regulatory threshold (Visa/Mastercard 1.0% cap, alert at 0.9%), different processor. Multi-processor merchants must hit the threshold on each processor's monthly volume separately, the cap is per-processor, not aggregate.
## Known limitations / merchant FAQs **What happens if I cross 1.0%?** Three sequential consequences as the rate persists above 1.0%: 1. **Month 1**: PayPal flags your seller-performance status. Visa enrols you in the Chargeback Monitoring Programme (VCMP), Early Warning tier. PayPal may impose a rolling reserve (typically 5-15% of payouts held for 60-90 days as protection against future chargebacks). 2. **Month 2-3**: VCMP escalates to "Standard" tier. Per-chargeback fees rise (from $20 to $50 typically). PayPal may require a remediation plan submitted in writing. 3. **Month 4+**: VCMP "High Risk" tier. Card-network privileges can be revoked for that merchant ID. PayPal may terminate the merchant account. The 0.9% alert exists to give you the runway to fix the cause before any of this happens. **My dispute rate is at 0.95%, but I have a rolling reserve already, am I safer?** A reserve protects PayPal against your future chargebacks; it doesn't protect you against the regulatory consequences. If your rate stays above 1.0% for the regulatory monitoring window, the card-network programme still kicks in regardless of whether PayPal has a reserve. Reserves are a symptom of risk, not a cure. **Can I lower the rate fast by issuing pre-emptive refunds on open disputes?** Yes, this is the standard playbook when you're approaching the cap. A refund issued through PayPal usually closes the case in your favour and the case (T19) doesn't count toward the lost-dispute count for VCMP. Caveat: refunds *do* close the dispute as "buyer favoured" so they appear in the resolution outcome but don't count as chargebacks. Worth doing aggressively when this card is firing. **Why does PayPal's threshold align with Visa, not its own rule?** Because most PayPal disputes that escalate are routed through Visa or Mastercard for chargeback adjudication. The networks set the regulatory floor; PayPal's seller performance system aligns to it. Your PayPal-only dispute exposure (Buyer Protection cases, never escalated to a card network) is technically separate, but in practice PayPal's enforcement uses the same 1.0% threshold across both populations. **My multi-product / multi-channel store, do disputes from one product affect my whole rate?** Yes. The dispute rate is per merchant account, not per product. One bad SKU (say a defective batch) generating high SNAD disputes can push the entire account's rate above the cap. Use [PP Dispute Reason Mix](/nerve-centre/kpi-cards/paypal/dispute-reason-code-mix) to identify product concentration; consider freezing or unlisting the offender until the rolling 30-day window flushes the cases. **Why is this a separate alert card from PP Dispute Rate?** Two reasons. First, audience: this card is a CFO / regulatory escalation; PP Dispute Rate is a daily monitoring gauge. Second, framing: this card explicitly references the regulatory threshold (Visa cap), making it clear what the "cost" of crossing is. PP Dispute Rate's threshold is calibrated to your peer band; this card's is calibrated to the regulator's. **My multi-currency PayPal account, does the threshold apply per-currency?** No, the regulatory threshold is per-merchant-account, applied to the aggregate rate across all currencies. The Visa/Mastercard programmes don't care which currency the disputes were in. Your single, valid dispute rate (count-based, currency-neutral) is what's checked. **A friend hit 1.5% but didn't get terminated, why?** Three possibilities: (1) their volume was below the 100-chargeback floor (VCMP requires both 1% rate AND ≥100 chargebacks/month, low-volume merchants can have very high rates without triggering), (2) PayPal granted them a remediation period and they pulled the rate back below 1.0% before consequences, (3) they're in a high-risk vertical where PayPal's tolerance is genuinely different (some categories like CBD, supplements, and adult products have different baselines). Don't extrapolate; the 0.9% buffer is the safe assumption. **What's the fastest way to bring the rate down once it's elevated?** Three lever order: (1) refund all open disputes likely to lose (closes them as resolution-by-agreement, doesn't count), (2) freeze the dispute-driving channel (a specific SKU, a specific shipping option, a specific traffic source), (3) tighten PayPal Risk to block the patterns generating Unauthorised disputes. Combined, expect the rate to bend down within 7-14 days as the rolling window ages out the older disputes. **Stripe's twin is also alerting, what does that mean?** Both processors are seeing the same dispute pressure, usually a product / listing / fulfilment issue affecting all customers regardless of payment method. Cross-reference [PP Dispute Reason Mix](/nerve-centre/kpi-cards/paypal/dispute-reason-code-mix) and Stripe's reason mix; if both show INR dominance, it's logistics; if both show SNAD, it's product / listing. *** ### Tracked live in Vortex IQ Nerve Centre *Dispute Threshold Watch* 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](https://app.vortexiq.ai/login) or [book a demo](https://www.vortexiq.ai/contact-us) to see this metric running on your own data.