Disputes resolved in seller’s favour ÷ total resolved. PayPal is buyer-friendly; below 35% means evidence packs are weak.
At a glance
The percentage of resolved buyer-protection cases that the merchant won (resolved in seller’s favour) out of all closed cases in the period. PayPal’s Buyer Protection programme is structurally buyer-friendly, which means a healthy industry baseline is 35-50 percent seller-win rate. Brands consistently below 35 percent are losing winnable cases through weak evidence submissions; brands consistently above 60 percent are either selling extremely well-described digital products, defending only the strongest cases, or have an unusually high friendly-fraud cohort. PayPal disputes follow a fundamentally different escalation path than card-network chargebacks; this card surfaces how well the merchant is navigating that path.
| What it counts | COUNT(disputes WHERE outcome = 'RESOLVED_SELLER_FAVOUR') ÷ COUNT(disputes WHERE status IN ['RESOLVED', 'WON', 'LOST']) × 100. Disputes still under review (status = OPEN, WAITING_FOR_BUYER_RESPONSE, WAITING_FOR_SELLER_RESPONSE, UNDER_REVIEW) are excluded from both numerator and denominator until they close. |
| PayPal dispute lifecycle | A PayPal dispute opens in the Resolution Centre as a buyer complaint (status: OPEN). The merchant has 20 days to respond. If unresolved through buyer-seller messaging, the buyer can escalate to a Claim (PayPal arbitrates). Claims close as RESOLVED_BUYER_FAVOUR (refund issued from merchant balance) or RESOLVED_SELLER_FAVOUR (case dismissed). Some claims are chargeback-escalated, where the buyer’s card issuer takes over, at which point the win-rate calculation switches to card-network rules. |
| Three buyer-protection categories | (1) Item Not Received (INR): ~50 percent of typical merchant volume. Merchant defends with shipping carrier tracking + delivery confirmation; win rate is high (60-75 percent) when documentation is clean. (2) Significantly Not As Described (SNAD): ~35 percent of volume. Merchant defends with product photos, item description match, return-and-refund policy compliance; win rate is mixed (35-50 percent). (3) Unauthorised Transaction: ~15 percent of volume. Almost always lost (5-15 percent win rate) because PayPal favours the cardholder unless the merchant has 3DS authentication or proof of session-level fraud-protection actions. |
| Currency | n/a, this is a count-based ratio. The currency-denominated impact surfaces in pp_dispute_value. |
| Fees / processing cost | A lost case returns the disputed amount to the buyer from the merchant’s balance plus any merchant-side fees PayPal charges for the dispute resolution (typically the original transaction fee is not refunded). Won cases incur no penalty fee but do consume operational time. |
| Refunds vs disputes vs chargebacks | A merchant-initiated refund (issued before any dispute is filed) does not count in this calculation. A buyer requesting a refund through the Resolution Centre that the merchant approves before the case escalates does count as a closed case (typically RESOLVED_OTHER or RESOLVED_BUYER_FAVOUR depending on PayPal’s classification). A card-network chargeback that escalates from a PayPal claim follows different timing and rules; the chargeback win/loss surfaces separately in pp_chargeback_lifecycle. |
| Buyer Protection eligibility | Some transactions are not Buyer Protection eligible (intangible goods, custom items, motor vehicles, real estate, certain digital services). Disputes against ineligible transactions can still be filed but PayPal will close them as RESOLVED_SELLER_FAVOUR automatically without merchant evidence. Brands selling Buyer Protection ineligible categories should expect artificially high win rates; the pp_ineligible_transactions card surfaces the eligibility split. |
| Seller Protection programme | Separate from Buyer Protection. Seller Protection covers the merchant against specific buyer-fraud patterns (unauthorised transactions, item not received with valid tracking) when the merchant follows the prescribed evidence-handling process. Seller Protection coverage rate is tracked in pp_seller_protection_coverage_rate; the two programmes interact but score differently. |
| Auto-closure rules | PayPal auto-closes cases in the merchant’s favour when the buyer fails to respond within 20 days, when the merchant provides full documentation early in the case, and when the buyer-stated reason is technically ineligible. Auto-closures count as wins in this card’s calculation. |
| Time window | 90D (rolling 90 days). PayPal disputes have a 20-day initial response window plus up to 20 additional days for buyer response, which means cases can take 40-60 days to close. The 90-day window ensures the calculation is dominated by fully-closed cases rather than open ones. |
| Alert trigger | <35 percent (a sustained sub-35 percent win rate across the rolling 90-day window suggests the merchant’s evidence-submission process is materially weaker than industry baseline). |
| Sentiment key | pp_buyer_protection_win |
| 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 UK-based fashion brand on Shopify accepting PayPal alongside card payments through Stripe, processing roughly 12 percent of order volume through PayPal. Snapshot for the rolling 90-day window ending Wednesday 15 May 26.| Dispute category | Cases closed | Won by seller | Win rate | Industry baseline |
|---|---|---|---|---|
| Item Not Received (INR) | 84 | 62 | 73.8% | 60-75% (in band) |
| Significantly Not As Described (SNAD) | 51 | 18 | 35.3% | 35-50% (low end) |
| Unauthorised Transaction | 22 | 2 | 9.1% | 5-15% (in band) |
| Refund-request closed before claim escalation | 38 | n/a | n/a | (excluded) |
| Total resolved cases (in calc) | 157 | 82 | 52.2% | 35-50% account-level baseline |
- The 52.2 percent blended win rate is in the healthy upper band for a fashion brand. Industry data puts the typical fashion-vertical PayPal seller win rate at 35-50 percent; 52.2 percent indicates the brand is doing meaningful evidence work. The headline figure is reassuring; the diagnostic value sits in the per-category breakdown.
- The INR cohort at 73.8 percent is close to peak performance. Item Not Received is the most defensible category because shipping carrier tracking and delivery confirmation are objective evidence. The 22 lost cases of 84 typically split: ~12 cases where the tracking shows delivery to the wrong address (carrier error, not seller fault, but PayPal still favours buyer); ~6 cases where the buyer claims the package was stolen from the doorstep after delivery; ~4 cases where tracking was missing or incomplete. The lever to push INR win rate higher is signature-required delivery for orders above a value threshold (typically £100); this adds ~£0.50/order cost but raises INR win rate by 5-10 percentage points.
- The SNAD cohort at 35.3 percent is the load-bearing problem. SNAD is buyer-friendly by design; PayPal’s bias is “if the buyer says it’s not as described, the buyer is right unless the merchant has overwhelming counter-evidence”. Brands at 35 percent are at the floor of “evidence pack is reasonable but not exceptional”. Lifting SNAD win rate to 45-50 percent typically requires: (a) photographing every item before shipping with timestamps and order-number visible; (b) documenting the product detail page at sale time as a screenshot stored against the order; (c) clear return-and-refund policy that the buyer accepted at checkout; (d) a written response to the SNAD claim that addresses the buyer’s specific complaint, not a boilerplate denial.
- The Unauthorised Transaction cohort at 9.1 percent is at the floor. This is structural; PayPal almost always rules in favour of buyers in unauthorised-transaction cases unless the merchant has enabled 3DS authentication and the transaction was 3DS-verified. For brands wanting to reduce unauthorised-transaction losses, the lever is upstream: enable 3DS on PayPal-funded orders, particularly high-value ones. This shifts liability to the issuing bank for verified transactions. The trade-off is checkout friction (3DS adds a step), so brands with high cart-abandonment risk often choose to absorb the unauthorised-transaction losses instead.
-
The 38 refund-request cases that closed before claim escalation are not in the calculation but represent meaningful operational signal. When a merchant proactively refunds a buyer through the Resolution Centre, no claim is filed and no win/loss is recorded. Brands with high “refund before claim” rates are doing the right thing: it preserves the customer relationship and avoids the dispute counting against the merchant’s PayPal account standing. The
pp_refund_velocitycard surfaces this proactive-refund pattern. -
Account-level implications. PayPal monitors merchant accounts on three thresholds: (1) dispute-rate (similar to card-network metrics, see
pp_dispute_rate); (2) buyer-protection-loss-rate (lost cases × disputed value ÷ payment volume); (3) chargeback-escalation rate (claims that escalate to card-network chargebacks). A 52.2 percent win rate keeps the merchant safely below the buyer-protection-loss-rate threshold for account standing; thepp_payment_health_scorecard surfaces this composite.
- Decompose by category.
pp_dispute_reason_mixbreaks resolved cases by INR, SNAD, Unauthorised. The category mix usually concentrates the problem; SNAD is the most-fixable. - Cross-reference with
pp_dispute_response_time. Cases lost because the merchant did not respond within 10 days of the dispute opening are 100 percent operational waste; the buyer’s claim auto-resolves in their favour after the response window. Brands at low win rates typically have high response-time gaps. - Check
pp_dispute_valuefor the financial impact. Win rate is a count-ratio; the currency-denominated loss surfaces here. A 30 percent win rate on a £20,000 disputed-value 90-day cohort is a £14,000 loss; a 30 percent win rate on a £200,000 cohort is a £140,000 loss. Effort allocation should match the financial size. - Pair with
pp_seller_protection_coverage_rate. Seller Protection covers specific patterns (validated tracking, no-signature-required exceptions); brands not following the Seller Protection process leave eligible coverage on the table. - For high-volume brands, consider Resolution Centre automation. PayPal’s API allows automated case-creation, evidence-uploading, and status tracking. Brands above ~50 disputes/month typically benefit from semi-automated dispute response that ensures consistent evidence packs.
| Time horizon | Action |
|---|---|
| Immediate (every dispute) | Respond within 24 hours of case opening with shipping tracking, photos, and product description match. The fastest wins come from auto-closure when buyer fails to escalate. |
| Weekly review | Triage open cases by disputed-value descending; allocate human evidence-pack time to the top decile of value. |
| Monthly review | Compare win rate by SKU, by region, by acquisition channel. Concentrated losses on a single SKU usually indicate a product-quality or product-page-description issue. |
| Quarterly review | Re-evaluate Seller Protection compliance and policy alignment. PayPal updates programme rules quarterly; staying compliant reduces the loss rate over time. |
Sibling cards merchants should reference together
| Card | Why merchants reach for it |
|---|---|
pp_dispute_rate | The inflow rate of disputes; this card is the outflow defence rate. The two together drive the loss math: loss rate = dispute rate × (1 - win rate). |
pp_dispute_value | The currency-denominated impact alongside the win-rate count. A 30 percent win rate on £200,000 disputed value tells the size of the problem. |
pp_dispute_reason_mix | The category breakdown by INR, SNAD, Unauthorised. Each category has a different defence pattern and different fixable lever. |
pp_dispute_response_time | The operational lever for win rate. Cases lost because the merchant did not respond within 10 days are 100 percent recoverable through process tightening. |
pp_disputes_open | The current open-case count. The defence pipeline backlog. |
pp_chargeback_lifecycle | Cases that escalate from PayPal claims to card-network chargebacks. Win rate calculation switches to card-network rules at the chargeback boundary. |
pp_seller_protection_coverage_rate | The coverage offered by PayPal’s Seller Protection programme. Following the programme rules raises win rates on covered case patterns. |
pp_unauthorised_dispute_rate | The unauthorised-transaction-specific dispute rate; this category has the lowest win rate (5-15 percent) and the highest 3DS-authentication leverage. |
pp_dunning_recovery_rate | For subscription-PayPal brands, the recovery rate on past-due renewals. Pre-emptive recovery reduces dispute filings. |
pp_alert_dispute_threshold | The alert that fires when dispute rate breaches threshold; works alongside this win-rate card. |
pp_alert_dispute_velocity | Dispute-volume velocity alert. Sudden dispute-volume spikes often correlate with win-rate degradation as the operational team is overwhelmed. |
pp_payment_health_score | The composite that folds dispute rate, win rate, fraud signals, and seller protection coverage into one number that approximates PayPal’s account-standing assessment. |
pp_xc_chargeback_forecast | Cross-channel forecast combining PayPal dispute rate, Stripe dispute rate, and fraud signal velocity. |
Stripe stripe_dispute_win_rate | The Stripe parallel for brands running both processors. Stripe’s chargeback-defence and PayPal’s buyer-protection use different escalation paths but the operational discipline is similar. |
pp_refund_rate | High refund rate alongside high win rate suggests merchant-initiated refunds are pre-empting weak-evidence disputes; high refund rate alongside low win rate suggests reactive defensive refunds rather than proactive customer service. |
Reconciling against the vendor’s own dashboard
Where to look in PayPal’s own dashboard:- PayPal Resolution Centre for the live list of open and closed disputes with full message threads and evidence trail.
- PayPal Business → Reports → Disputes Report for the case outcome breakdown over time. The Resolution Centre’s “Closed cases” tab is the closest 1-to-1 comparison to this card.
- PayPal Business → Insights → Account Health for PayPal’s own composite health score that includes win rate as one input.
| Reason | Direction | What to do |
|---|---|---|
| Refund-before-claim cases. The Vortex IQ card excludes cases that were refunded before formal claim escalation; some PayPal reports include them as “resolved in buyer’s favour” by default. | Vortex IQ higher when refund-before-claim rate is high | Use the same “claim-only” filter in PayPal Resolution Centre when reconciling. |
| Auto-closure timing. Cases auto-closed because the buyer failed to respond within 20 days are reported instantly by PayPal but Vortex IQ surfaces them on the next refresh. | Either direction during the 20-day window | The 90-day window smooths this. |
| Chargeback-escalated cases. When a PayPal claim escalates to a card-network chargeback, the case status changes mid-cycle. Vortex IQ tracks the final state; some PayPal reports show the intermediate state. | Either direction | Use the pp_chargeback_lifecycle card for the escalated-case-specific view. |
| Buyer Protection ineligibility. Some categories are not eligible for Buyer Protection; cases against ineligible transactions auto-close in seller’s favour without merchant evidence. PayPal sometimes reports these separately; Vortex IQ folds them into the headline win rate. | Vortex IQ higher for brands selling ineligible categories | The pp_ineligible_transactions card surfaces the eligibility split. |
| Time zone. PayPal Resolution Centre uses the merchant’s account-level time zone; Vortex IQ uses UTC for period boundaries. | Boundary days differ | Largest impact on T (today) and 7D windows; for 90D the drift averages out. |
| Comparison | Expected relationship | When divergence is legitimate |
|---|---|---|
pp_buyer_protection_win_rate ↔ Stripe stripe_dispute_win_rate | Independent metrics; comparable but not equivalent | PayPal’s Buyer Protection programme follows different rules than card-network chargebacks. PayPal cases tend to have higher seller win rates than card-network chargebacks because PayPal’s process allows for two-way messaging before formal arbitration. Brands running both processors typically see PayPal win rates 5-15 percentage points higher than Stripe win rates for similar product mixes. |
pp_buyer_protection_win_rate ↔ Shopify Resolution Centre (when Shopify Payments is in use) | Not directly comparable | Shopify Payments uses Stripe under the hood; PayPal disputes for PayPal-paid orders go through PayPal’s Resolution Centre regardless of the upstream commerce platform. |
pp_buyer_protection_win_rate ↔ Internal customer-service metrics (e.g. NPS, refund-request rate) | Should correlate negatively with win rate when service is strong | Brands with strong customer service should see lower dispute volume (fewer disputes filed) but similar or slightly higher win rates on the disputes that do escalate (because the cases that reach claim status are more likely to be friendly fraud rather than legitimate service complaints). |
Known limitations / merchant FAQs
Why is my PayPal win rate so much lower than my Stripe chargeback win rate? PayPal’s Buyer Protection programme is structurally buyer-friendly by design (it is one of PayPal’s primary value propositions to consumers). PayPal favours buyers in close cases unless the merchant has overwhelming evidence; card-network chargebacks have more balanced dispute resolution rules with codified evidence requirements. Brands typically see PayPal win rates 10-20 percentage points below their Stripe chargeback win rates for the same product mix and operational quality. This is not a sign of weak operations; it is the structural difference between the two dispute-resolution systems. My win rate is 25 percent. Should I stop accepting PayPal? Probably not. PayPal still drives meaningful incremental revenue for most ecommerce brands (the buyer-friendly programme is partly why customers choose PayPal at checkout; they trust the safety net). The economically correct framing is net contribution:(PayPal revenue) - (PayPal-driven dispute losses) - (PayPal fees) - (operational cost of dispute defence). Brands with even a 25 percent win rate usually still see positive contribution from PayPal because the dispute losses are typically 1-3 percent of PayPal revenue, while PayPal acceptance lifts conversion rate by 5-15 percent on the orders that include it. The right response to low win rate is to fix the operational evidence-pack quality, not to drop the channel.
What evidence pack should I submit for an Item Not Received dispute?
PayPal’s Resolution Centre accepts: shipping carrier name and tracking number, delivery confirmation (PDF, screenshot, or carrier-API response), the order-confirmation email sent to the customer, and any post-purchase customer-service interactions. Best-practice pack: (1) tracking number with link to carrier confirmation page; (2) screenshot of carrier delivery scan with timestamp; (3) buyer’s IP address and account login history (if available); (4) order-confirmation email; (5) any messages from the buyer post-delivery. PayPal weights signature-required deliveries more heavily than no-signature; brands shipping high-value items should require signatures.
What evidence pack should I submit for a Significantly Not As Described dispute?
(1) Photos of the item taken before shipping with timestamp and order number visible; (2) screenshot of the product detail page at the time of sale (the description the buyer agreed to); (3) the buyer’s specific complaint quoted from the dispute message; (4) a written response addressing the specific complaint (not boilerplate); (5) the merchant’s published return-and-refund policy that the buyer accepted; (6) any post-purchase customer-service messages where the buyer’s complaint was discussed. Generic responses lose; specific, evidence-supported responses win.
Should I just refund every dispute to avoid losing PayPal account standing?
Refunding every dispute does keep account standing intact in the short term, but it has long-term consequences: (a) the merchant pays back the disputed amount in every case, including ones that were friendly fraud and would have been won; (b) PayPal’s algorithm tracks “merchant always refunds” patterns and may classify the merchant as high-risk, raising rolling reserves and tightening payout schedules; (c) the customer learns “filing a dispute always works” and the dispute rate climbs over time. The economically right response is to defend cases the merchant believes are recoverable (typically 30-60 percent of disputes) and pre-emptively refund the rest before they escalate.
Why are my Unauthorised Transaction win rates so low?
PayPal’s policy strongly favours the cardholder in unauthorised-transaction cases unless the merchant has 3DS authentication on the original transaction. Without 3DS, the merchant typically loses regardless of evidence quality. The lever to raise unauthorised-transaction win rates is upstream: enable 3DS for PayPal-funded orders, particularly above a value threshold. The trade-off is checkout friction (3DS adds a step), so brands choose whether to absorb the unauthorised-transaction losses or to add the friction. The pp_threedsecure_abandon_rate card surfaces the friction cost.
Can I appeal a lost case?
Yes, within 10 days of the case closing. Appeals require new evidence (not a re-submission of the original pack). Successful appeals typically include: shipping carrier delivery-confirmation that arrived after the case closed, a buyer follow-up message admitting the item was received, or new customer-service messages clarifying the dispute. Appeals win in roughly 20-30 percent of cases when accompanied by genuinely new evidence; appeals based on the same evidence almost always fail.
My win rate suddenly dropped 15 percentage points this month. What happened?
Common causes, in order of likelihood. (1) Operational team change: a customer-service team turnover, holiday cover, or process change can degrade evidence-pack quality. The first 30 days post-team-change usually show degradation. (2) PayPal policy update: PayPal updates Buyer Protection policy quarterly; the most recent updates have generally tightened seller win rates in SNAD cases. (3) Product-category shift: a new product launch in a category with higher SNAD risk (apparel, jewellery, electronics) raises overall dispute volume and reduces the blended win rate. (4) Geographic expansion: launching in new markets brings unfamiliar dispute patterns; localising the evidence-pack response (translation, region-specific carrier evidence) takes time. (5) Genuine fraud-pattern shift, less common but possible.
Can Vortex IQ submit dispute evidence on my behalf?
Read-only by design. Vortex IQ surfaces win-rate patterns, identifies process gaps, and flags low-win-rate categories for operational attention; the merchant’s customer-service team executes inside PayPal Resolution Centre. The Vortex Mind Decline Recovery Intelligence report generates merchant-side Actions when win-rate degradation patterns suggest specific fixes (e.g. “INR win rate dropped because tracking number quality degraded”), but the response itself sits with the merchant.
Is win rate the only metric that matters for PayPal account standing?
No. PayPal’s account-health score combines win rate, dispute rate, dispute-value-to-payment-value ratio, chargeback rate, and seller-protection-coverage compliance. The composite pp_payment_health_score card folds these into one number. Brands focused only on win rate without watching dispute rate can still hit account-standing thresholds even with healthy win rates if dispute volume scales aggressively.