Dispute Rate, PayPal

Metrics type: Supporting Metrics • Category: Payment Gateway

At a glance

Percentage of successful PayPal payments that triggered a dispute (T19xx) in the period. Includes both PayPal-buyer-protection cases (Item Not Received, Significantly Not As Described) and bank-initiated chargebacks routed through PayPal. The 20%-weight component of PP Payment Health Score, amplified ×50 in the composite to track the Visa/Mastercard 1.0% threshold.


The formula	`COUNT(event_code STARTS T19) ÷ COUNT(event_code STARTS T00 AND status='S') × 100`. Disputes ÷ successful payments.
Event code filter (numerator)	T19xx only. PayPal’s dispute / chargeback event family. Includes inquiries, formal disputes, escalated cases, and pre-arbitration.
Transaction status filter	Numerator counts ALL T19 events regardless of status (open, won, lost, abandoned). Denominator counts only T00 with `status = S` (successful payments).
What “dispute” includes	(1) PayPal Buyer Protection cases (Item Not Received “INR”, Significantly Not As Described “SNAD”, Unauthorised Transaction); (2) bank-initiated chargebacks on card payments routed through PayPal; (3) inquiries that did NOT escalate to a formal case (still count as dispute friction). For the breakdown see PP Dispute Reason Mix.
Pending status (P) handling	Pending payments are NOT in the denominator (only `S`). A dispute filed on a payment that’s still pending is rare but does count in numerator if T19 fires before the payment fully clears.
Refund treatment	Refunds (T11) are NOT disputes. A customer who refunds is happy enough to ask politely; a dispute is the customer (or their bank) escalating around you. Only T19 events count here.
Currency	n/a (rate, currency-neutral). Multi-currency PayPal accounts get a single, valid dispute rate.
Seller Protection	Seller Protection coverage doesn’t change whether a dispute counts; it changes whether you LOSE money on a dispute. See PP Seller Protection Coverage. Disputes on protected orders still appear here.
Visa / Mastercard cap (the regulatory threshold)	Card networks place merchants in monitoring or excessive-chargeback programmes when chargeback rate exceeds 1.0% of transactions. PayPal aligns its own thresholds to match. The composite uses a ×50 amplifier to keep this card’s contribution bound to that 1% ceiling: a 0% dispute rate scores 100, a 2% dispute rate scores 0.
Page cap	10,000 transactions per `/v1/reporting/transactions` call. Disputes are typically a small fraction of total feed volume so the cap rarely matters here.
Time window	`30D vsP` (default 30D vs prior 30D). Disputes have long tails (filed up to 180 days after the original payment) so shorter windows can be misleading.
Alert trigger	`> 0.9%` (90% of the Visa cap, gives you headroom to act before the regulatory threshold hits).
Roles	owner, 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 apparel brand with a 30-day window covering 14 Mar 26 to 12 Apr 26. PayPal carries the higher-risk traffic slice (international, mobile, younger demographics). The transactions feed for this period:

Event family	Count	Notes
T00 successful payments (status=S)	4,820	The denominator
T11 refunds	192	Not relevant here
T19 dispute events	23	The numerator
T03 payouts	28	Not relevant here

Drilling into the 23 T19 events by transaction_subject normalised to PayPal dispute reasons:

Dispute reason	Count	What it means	Seller Protection helps?
Item Not Received (INR)	11	Customer says package didn’t arrive	Yes if shipping with tracking
Significantly Not As Described (SNAD)	6	Customer says product isn’t as advertised	Sometimes (item-eligible only)
Unauthorised Transaction	4	Card-on-file fraud (someone used a stolen card)	Usually yes
Bank chargeback (card-routed)	2	Issuing bank initiated, not buyer	Treated as Unauthorised

PP Dispute Rate
  numerator   = 23 (all T19 events)
  denominator = 4,820 (T00 with status = S)
              = 23 ÷ 4,820 × 100
              = 0.477%

Composite contribution under the ×50 amplifier:

Component score = 100 − 50 × 0.477
                = 100 − 23.85
                = 76.15
Weighted contribution = 0.20 × 76.15
                      = 15.23 (out of 20.00 possible)

Five things worth noticing:

0.477% is well below both alert thresholds. Vortex IQ alerts at 0.9%, the regulatory cap is 1.0%. The merchant has room. But a doubling (to 0.95%) would fire the alert AND drop the composite score by 4 points (×50 amplifier).
INR (Item Not Received) is the largest bucket at 48% of disputes. That’s an operations / fulfilment signal, not a product / fraud signal. Look at: shipping-with-tracking compliance (PP Seller Protection Coverage), carrier reliability, recent address-validation failures. INR > 30% of disputes typically means a logistics issue, not a buyer-fraud issue.
4 Unauthorised Transactions are fraud signals. PayPal’s seller protection usually covers Unauthorised Transactions if the order shipped to the verified address. Check PP Fraud Velocity for clustering, multiple unauthorised disputes from similar IPs / billing addresses suggest a card-testing attack.
2 bank-initiated chargebacks routed through PayPal. These are card-network chargebacks (Visa / Mastercard) that the issuer filed directly and PayPal forwards to the merchant. They count toward the Visa 1.0% cap. Win rates on these are lower than buyer-protection cases because the card network’s evidence requirements are stricter.
PayPal disputes typically run 0.2-0.6% for healthy merchants. This rate (0.477%) is on the higher end of healthy. If it climbs above 0.7% over the next two periods, watch the dispute reason mix; a SNAD spike points to a product-listing issue (misleading photos, missing variants, wrong sizing chart), an INR spike points to fulfilment.

If next period the dispute rate climbed to 0.95%, the composite would drop ~4 points (the ×50 amplifier) AND the alert would fire. By the time you hit 1.0% you’d be in the Visa monitoring programme, which can lead to higher fees, rolling reserves, and eventual merchant-account termination if not addressed in 90 days. The 0.9% alert exists to give you the runway.

Sibling cards merchants should reference together

Card	Why pair it with PP Dispute Rate
PP Dispute Reason Mix	The “why” behind the rate. INR / SNAD / Unauthorised splits, with each pointing to a different remediation.
PP Dispute Value	The dollar exposure. Rate tells you frequency, value tells you risk.
PP Dispute Rate Trend	Monthly trend to spot deterioration before it triggers the 0.9% alert.
PP Buyer Protection Win Rate	Of disputes you defended, how many did you win? Below 35% suggests evidence packs need work.
PP Seller Protection Coverage	Coverage on the underlying payments. High coverage = disputes hurt less; low coverage = exposed to losses.
PP Disputes Open	Live count needing response action right now.
PP Dispute Response Time	How fast you respond to disputes. PayPal expects evidence within 10 days for most case types.
PP Unauthorised Dispute Rate	Fraud-specific subset. Spikes here indicate card-testing attacks.
PP Payment Health Score	This card is the 20%-weight component, amplified ×50. The largest single risk-side input.
Stripe Dispute Rate (twin)	The Stripe twin. Same 1.0% Visa/Mastercard ceiling applies to both.

Reconciling against the vendor’s own dashboard

Where to look in PayPal Business: The closest PayPal-native views:

PayPal Resolution Center, the row-level dispute case list. Filter by date range and case type (Inquiry, Dispute, Chargeback, Pre-Arbitration).
PayPal Business → Reports → Disputes report (where available), an aggregate view by month.
PayPal Seller Performance dashboard shows your dispute rate against PayPal’s own thresholds and any seller-performance flags.

Other views that look like this but aren’t:

“Cases” tile on the home dashboard groups disputes + claims + escalations into one number; this card is rate, not count.
“Refunds and reversals” in the Activity feed includes refunds (T11), which we exclude here.
“Fraud risk” in the Risk dashboard counts flagged-but-blocked-at-payment events, which never became disputes (they’re declines, see PP Decline Rate).

Why our number may legitimately differ from PayPal Business:

Reason	Direction of divergence	What to do
Page cap (10,000 transactions per call). Disputes are sparse so the cap rarely matters here, but if both denominator and numerator are truncated the rate may shift.	Either direction	Use shorter windows.
Time zone. PayPal Business uses your account-configured timezone; Vortex IQ uses UTC.	Boundary-day drift	Compare equal date ranges accounting for tz offset.
Event-code interpretation drift. PayPal’s `T19xx` sub-codes have evolved; older disputes may use codes since deprecated. Inquiries that closed without escalation may or may not be counted depending on which engine you ask.	Tiny drift on long historical windows	Use shorter, recent windows.
Seller-protection eligibility refresh lag. Doesn’t affect rate directly but may affect which cases you see in the Resolution Center vs which we counted.	Rare	No action.
Dispute close-out timing. PayPal can re-open closed cases (rare, on appeal). The rate at sync time may be off by 1-2 cases vs the live PayPal Business view if a re-open happened between syncs.	Tiny	Wait for next refresh.

Cross-connector reconciliation:

Comparison	Expected relationship	When divergence is legitimate
`pp_dispute_rate` ↔ `stripe.stripe_dispute_rate`	Both subject to the same 1.0% Visa/Mastercard regulatory cap. PayPal often runs slightly higher because its Buyer Protection programme makes it easier for buyers to file (no need to call the bank, just click in the PayPal app).	A PayPal-side gap of 0.1-0.3 percentage points above Stripe is normal. Larger gap usually means a SNAD spike (product / listing issue) or an INR spike (fulfilment issue), neither bank-side.
`pp_dispute_rate` ↔ commerce platform refund rate	Refunds and disputes are inversely linked: if the merchant is generous with refunds, disputes drop (customer satisfied without escalating).	Watch PP Refund Rate alongside; rising refunds AND rising disputes is the worst combination, suggesting product or fulfilment failure.
`pp_dispute_rate` ↔ `paypal.pp_payment_health_score`	Composite component (×50 amplifier on this rate).	Internal identity, must move together. The amplifier is calibrated to the 1% regulatory ceiling.

Quick rule for support tickets: if a merchant says “PayPal Resolution Center shows 30 disputes, your card shows 23” in the same period, 90% of the time the difference is timezone (boundary days) or category (we exclude T11 refunds, they may include them). For higher-stakes reconciliation, export the Resolution Center CSV and match row-by-row.

Known limitations / merchant FAQs

Why is PayPal’s dispute rate higher than Stripe’s for the same merchant? Two structural reasons. First, PayPal’s Buyer Protection programme makes filing a dispute trivially easy for the customer, three clicks in the PayPal app, no need to call the bank. Stripe customers must initiate a chargeback through their issuing bank, which has more friction and lower filing rates. Second, PayPal carries more international and younger-demographic traffic where dispute behaviour is higher. A PayPal-higher gap of 0.1-0.3 percentage points is normal. Why does the alert fire at 0.9% when the regulatory cap is 1.0%? Headroom. By the time you actually hit 1.0% you’ve crossed into Visa/Mastercard chargeback monitoring territory, which can lead to higher fees, mandatory rolling reserves, and eventual merchant-account termination if not corrected within 90 days. The 0.9% alert gives you time to identify the cause and fix it before the regulatory clock starts. What’s the difference between INR, SNAD, and Unauthorised disputes? Three different root causes, each with a different fix:

INR (Item Not Received): customer says package didn’t arrive. This is a logistics signal, fix shipping with tracking compliance, carrier reliability, address validation. Seller Protection covers INR if you uploaded valid tracking.
SNAD (Significantly Not As Described): customer says product wasn’t as advertised. This is a product / listing signal, fix photos, copy, sizing charts, variant accuracy. Seller Protection partially covers SNAD only for eligible item types.
Unauthorised Transaction: card-on-file fraud, someone used a stolen card. This is a fraud signal; Seller Protection usually covers if you shipped to the verified address.

If INR > 30% of disputes, prioritise fulfilment fixes. If SNAD > 30%, audit product listings. If Unauthorised spikes, check PP Fraud Velocity for card-testing attacks. Are inquiries counted as disputes? Yes. A PayPal inquiry is the buyer asking PayPal to mediate without yet filing a formal case. It still creates dispute friction (you have to respond), and it shows the customer is unhappy enough to escalate. Most engines including ours count inquiries in the rate. PayPal Resolution Center may show inquiries separately depending on the view; for reconciliation include both. Does this card include refunds? No. Refunds (T11) are voluntary returns; disputes (T19) are escalations. They’re tracked separately. If you refund a customer who filed a dispute, the dispute usually closes in your favour but the T19 event still counts here. Can I lower my dispute rate by issuing more refunds? Yes, this is the practical playbook. Generous refund policies head off disputes before customers escalate. The trade-off is refund cost vs dispute cost: a refund costs you the order value plus fulfilment cost; a lost dispute costs you the order value plus the chargeback fee (usually $20) and counts against your 1.0% threshold. For most merchants, refunds are cheaper than lost disputes. My dispute rate looks fine now but it could spike, what’s the early warning? Watch four cards together: PP Dispute Reason Mix (the trend in INR vs SNAD vs Unauthorised), PP Refund Rate (refunds often precede disputes), PP Unauthorised Dispute Rate (early fraud signal), and PP Buyer Protection Win Rate (your defence quality). A simultaneous rise in refunds + SNAD disputes is the classic “product or listing issue” pattern. Why is the ×50 amplifier in the composite so aggressive? Because the regulatory ceiling is at 1.0%. The amplifier is calibrated so the dispute component scores 0 at 2.0% (twice the regulatory cap, an unrecoverable position) and scores 50 at 1.0% (the regulatory threshold). The composite drops below 70 well before 1.0%, ensuring the operator is alerted while there’s still room to fix. My multi-currency PayPal account, does this rate work? Yes, count-based ratios are currency-neutral. A multi-currency account gets one valid dispute rate across all currencies.

Tracked live in Vortex IQ Nerve Centre

Dispute Rate 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.

Get Started

The AI OS

At a glance

Calculation

Worked example

Sibling cards merchants should reference together

Reconciling against the vendor’s own dashboard

Known limitations / merchant FAQs

Tracked live in Vortex IQ Nerve Centre

​At a glance

​Calculation

​Worked example

​Sibling cards merchants should reference together

​Reconciling against the vendor’s own dashboard

​Known limitations / merchant FAQs

​Tracked live in Vortex IQ Nerve Centre

At a glance

Calculation

Worked example

Sibling cards merchants should reference together

Reconciling against the vendor’s own dashboard

Known limitations / merchant FAQs

Tracked live in Vortex IQ Nerve Centre