PayPal and Klarna dispute handling: a step-by-step merchant playbook (2026)
Updated
This playbook walks through the complete operational workflow for contesting PayPal inquiries and Klarna disputes: from initial intake and triage through evidence compilation, upload, messaging, and deadline management. It's written for e-commerce operations and payments teams who need provider-specific, deadline-safe handling without building a dedicated fraud team.
What you'll accomplish: respond to every dispute before its deadline, submit correctly formatted evidence, and avoid the most common reasons merchants lose winnable cases.
Prerequisites: access to your PayPal Resolution Center, Klarna merchant portal, order management system (OMS), and carrier tracking data. Estimated time per case (manual): 20–40 minutes. With automated tooling, under 2 minutes.
Difficulty: intermediate. Familiarity with PayPal Seller Protection and Klarna Merchant Protection Program terminology is assumed.
When to contest vs. accept: the merchant decision framework
The goal is straightforward: recover revenue and protect margins while keeping operational cost proportional to the disputed amount.
Contest a dispute when you have at least one of the following:
Documented proof of shipment or delivery to the address on record
Evidence that the delivered item matches the listing description and condition
Proof that the payment was authorized by the account holder
Accept (refund or settle) when critical evidence is unavailable, when the cost of manual case handling exceeds the disputed amount, or when partial shipment records cannot be reconciled.
Reason-code to evidence mapping (quick reference):
Dispute type | Primary evidence required |
|---|---|
PayPal Item Not Received (INR) | Tracking number + carrier delivery confirmation to buyer's address |
PayPal Significantly Not as Described (SNAD) | Listing screenshots, item photos, comms logs |
PayPal Unauthorized transaction | Shipment to PayPal-verified address + Seller Protection eligibility confirmation |
Klarna Goods Not Received | Proof of Delivery (POD) linked to the disputed Klarna capture |
Klarna Significant Deviation | Product photos, order confirmation, return correspondence |
One hard deadline warning applies to both providers: PayPal disputes auto-close after 20 days if not escalated, and closed disputes cannot be reopened. Klarna's evidence submission windows are phase-dependent, so evidence submitted outside the active inquiry window may not be accepted.
PayPal dispute lifecycle: timelines, stages, and escalation rules
The PayPal dispute resolution process moves through three distinct stages:
Inquiry stage: the buyer opens a dispute; both parties exchange messages in the Resolution Center. No PayPal adjudication occurs yet. This is your window to resolve directly with the buyer.
Claim stage: either party escalates the dispute to a claim; PayPal reviews evidence and makes a binding decision.
Settlement stage: PayPal closes the case and, if found in the buyer's favor, debits the merchant's account.
Hard deadlines (PayPal):
Event | Deadline |
|---|---|
Dispute auto-closes (if not escalated) | 20 days after opening |
Escalation to claim eligibility | At least 7 days after payment date |
INR dispute filing window | Within 180 days of payment date |
SNAD dispute filing window | Within 30 days of delivery, or 180 days from payment (whichever is sooner) |
Unauthorized transaction reporting | Within 13 months of payment date |
Other statement errors | Within 60 days of statement |
Operational buffer recommendation: treat Day 17 as your internal escalation deadline, not Day 20. Missing the window by even a few hours is unrecoverable, closed disputes cannot be reopened or escalated to a claim per PayPal's published help documentation.
Klarna dispute timelines:
Event | Deadline |
|---|---|
First follow-up request (Unauthorized purchases) | Up to 7 days (168 hours) |
First follow-up request (all other reasons) | Up to 14 days (336 hours) |
Subsequent follow-up requests | 7 days (168 hours) |
Klarna investigation decision (after review begins) | Typically 30–50 days |
Step 1: Intake and triage
Open a case dossier immediately when a dispute notification arrives. Populate the following fields before taking any other action:
Order ID and capture/transaction ID
Dispute reason code (PayPal or Klarna classification)
Payment method and provider
Order date, shipment date, and confirmed delivery date
Carrier name and tracking number
Shipping address on the order vs. address on the dispute
Item SKUs and quantities (flag partial shipments separately)
Refund status (any partial refunds already issued)
Prior customer communications (support tickets, chat logs, email threads)
Triage rules:
Confirm the reason code. INR, SNAD, and Unauthorized each require different evidence packages. Misidentifying the code wastes preparation time.
Confirm evidence availability. Query your OMS for shipment records, your carrier API for tracking events, and your PSP for transaction metadata.
Check protection program eligibility. For PayPal, confirm Seller Protection coverage before filing a claim response (coverage requirements include shipment to the address on the PayPal transaction, tangible goods, and no prohibited item categories). For Klarna, verify Merchant Protection Program readiness based on your integration tier and dispute reason.
Case dossier readiness status:
Green: tracking confirmation + address match + all SKUs shipped. Proceed to evidence pack assembly.
Yellow: partial tracking data or address discrepancy. Pull additional carrier data before responding.
Red: no tracking, refund already issued, or prohibited item category. Evaluate settlement cost vs. contest cost.
Target your first response within 48 hours of dispute notification. This leaves maximum buffer against both providers' follow-up deadlines.
Step 2: Evidence to collect by dispute type
Assembling the right evidence before responding prevents back-and-forth requests that eat into your deadline window. Here's the precise breakdown by reason code:
PayPal Item Not Received (INR)
Carrier tracking number with full event history (scan-by-scan)
Delivery confirmation showing the delivery address matches the PayPal transaction address
Signature confirmation if available (required for high-value orders to maintain Seller Protection)
Proof of shipment date (carrier pickup scan or postage receipt)
PayPal Significantly Not as Described (SNAD)
Screenshots or PDF of the original product listing at time of sale (title, description, condition, photos)
Photos of the item as packed and shipped if available
Any return request communications from the buyer
If the buyer claims item is defective: your QC records or third-party inspection notes
PayPal Unauthorized transaction
Proof of shipment to the PayPal-verified address on the transaction (this is the primary Seller Protection condition)
Proof that the item was a physical, tangible good
Transaction ID and confirmation that the payment cleared without a hold or flag
Klarna Goods Not Received
Klarna's own merchant documentation identifies Proof of Delivery (POD) as the primary evidence artifact for Goods Not Received disputes. Your POD must include: delivery timestamp, recipient address, carrier name, and tracking reference. Where available, include signature or photo confirmation from the carrier. All documents must be directly linked to the disputed Klarna capture, reference the Klarna order ID explicitly in your evidence submission. For more context on how Item Not Received claims work across providers, see the Guzco glossary.
Klarna Significant Deviation (faulty goods / not as described)
Klarna's evidence guidelines require that all submitted documents are legible, complete, and clearly attributable to the specific disputed transaction. Collect: product listing at time of sale, order confirmation PDF with line items, any customer-submitted photos of the alleged defect, and your written response to the customer's complaint prior to escalation.
Evidence mapping table:
Evidence artifact | Supported dispute types | Required fields |
|---|---|---|
Carrier tracking + delivery confirmation | PayPal INR, Klarna GNR | Tracking #, delivery date, delivery address, carrier name |
Signature or photo POD | PayPal INR (high value), Klarna GNR | Recipient name/address, timestamp |
Product listing screenshot | PayPal SNAD, Klarna Significant Deviation | Title, description, condition, date captured |
Order confirmation PDF | All types | Order ID, SKUs, shipping address, payment amount |
Customer communication log | PayPal SNAD, Klarna Significant Deviation | Date, channel, content summary |
Transaction record (PSP) | PayPal Unauthorized | Transaction ID, payer email, IP, device data |
Step 3: Formatting and uploading evidence
PayPal Resolution Center upload flow
Log in to your PayPal business account and navigate to Resolution Center.
Locate the relevant dispute and select Respond to Claim.
Choose Submit Requested Info (or the equivalent prompt for your dispute stage).
Drag and drop your evidence file(s) into the upload area, or use the file browser.
Add a concise description for each file (e.g., "Carrier tracking history showing delivery to buyer's address on [date]").
Click Submit.
PayPal evidence file constraints (per developer acceptance criteria):
Supported formats: PDF, JPG, PNG, GIF
Maximum file size per document: 5 MB
Minimum file size: 30 KB (files below this threshold are rejected)
Total evidence upload cap per case: 10 MB
Upload quality checklist:
Documents must be fully legible at 100% zoom; no glare on photos
All four corners of any physical document must be visible
Business name on documents must match your PayPal account name
Dates must be clearly visible and consistent with your case timeline
Avoid screenshots with browser UI cropped in; export as clean PDFs where possible
Klarna evidence submission
Klarna requires that each evidence document is directly traceable to the disputed capture. Include the Klarna order reference on or alongside every file. Evidence must be legible and complete, partial screenshots or cropped carrier labels are rejected. Submit via your Klarna merchant portal within the active inquiry phase; evidence submitted outside the phase window may not be reviewed.
Operational tip: build one master evidence pack per case first (all documents in a single folder), then create provider-specific subsets. This prevents duplicate effort when a dispute exists on both a Klarna capture and a linked payment dispute, and ensures you don't accidentally submit a document meant for one provider to another.
File naming convention:
Step 4: Copy-ready response templates
Use these templates as starting points. Replace all bracketed fields with case-specific data. Generic responses without evidence references are a common reason merchants lose otherwise winnable disputes.
Template 1: PayPal Item Not Received
Template 2: PayPal Significantly Not as Described
Template 3: PayPal Unauthorized Transaction
Do-not-say list:
Don't blame the carrier without a specific incident reference (e.g., "the carrier must have lost it" with no carrier exception record)
Don't contradict the shipping address in your response vs. what appears on the transaction
Don't submit a generic "item was shipped" statement without attaching the tracking evidence it references
Don't reference a refund that hasn't been processed yet as a resolution offer unless you've confirmed it in your system
Timing buffers and escalation flow
Missed deadlines are the single most preventable cause of dispute losses. Here's the operational schedule to run for every PayPal case:
Day | Action |
|---|---|
Day 0 | Dispute notification received. Open case dossier. Confirm reason code and evidence availability. |
Day 1–2 | Assemble evidence pack. Send first inquiry-stage response with evidence references. |
Day 7 | Escalation to claim becomes eligible (7 days after payment date per PayPal policy). Assess whether buyer has responded; if not resolved, prepare claim-stage evidence. |
Day 14–15 | Internal escalation review. If still unresolved at inquiry stage, escalate to claim with full evidence pack attached. |
Day 17 | Hard internal deadline. All escalations must be filed. |
Day 20 | PayPal auto-close deadline. Disputes not escalated close permanently and cannot be recovered. |
For Klarna, the phase structure differs. The initial inquiry window allows up to 14 days (336 hours) for your first response on non-Unauthorized disputes (7 days/168 hours for Unauthorized). Subsequent follow-up requests carry a 7-day (168-hour) response window. Once Klarna escalates to a formal review, expect a decision within 30–50 days. You can't accelerate this timeline, but you can ensure evidence is complete before the review phase opens.
Decision points during the escalation window:
If the buyer responds with new information at Day 3–5, request updated evidence from your OMS/carrier team before escalating
If no buyer response by Day 7, stop message-only responses and attach full evidence to any further communications
If tracking shows delivery but the buyer insists otherwise, pull the carrier's detailed scan history (not just the summary) and attach it as a separate document
Manual tracking of these windows across a high-volume dispute queue is operationally expensive. Guzco's automated claims processing handles deadline monitoring, evidence compilation from carrier and OMS data, and provider-specific response filing, with published metrics of 0% deadlines missed and 97% dispute win rates across cases handled.
Evidence pack structure: minimum viable vs. full pack
For merchants balancing case volume against preparation time, maintain two evidence pack tiers:
Minimum viable evidence pack (MVP):
Order confirmation PDF (order ID, items, address, amount)
Carrier tracking confirmation (delivery date, delivery address, carrier name)
One-page summary response citing both documents
Use the MVP when case value is below your threshold and evidence is unambiguous (clear delivery, address match).
Full evidence pack:
Order confirmation PDF
Carrier tracking history (all scan events)
Signature or photo POD (if available)
Product listing screenshot (for SNAD/Significant Deviation cases)
Customer communication log
PSP transaction record
Return policy (for SNAD cases)
Completed response template with evidence cross-references
Use the full pack for high-value disputes, repeat claimants, or cases where the buyer has provided counter-evidence.
Checklist download fields (CSV format):
FAQs and common pitfalls
What happens if a PayPal dispute closes before I escalate?
It's permanent. Per PayPal's published help documentation, closed disputes cannot be reopened or escalated to a claim. This is why the Day 17 internal deadline matters. If a dispute closes due to missed escalation, the only remaining option is a direct chargeback process through your acquiring bank, which carries its own timeline and fee structure.
What if my PayPal evidence upload fails?
Check the most common causes: file size over 5 MB per file (compress or split), total case upload exceeding 10 MB (prioritize highest-impact documents), file below 30 KB (ensure the document isn't a near-empty placeholder), or unsupported format (convert to PDF, JPG, PNG, or GIF). If the portal returns an error after these checks, try a different browser or clear cached session data before re-attempting.
When can I submit evidence in a Klarna dispute?
Evidence submission is phase-dependent. You can submit during the active inquiry/follow-up request window. Once Klarna moves the case to formal investigation, the evidence record is typically closed. Submit all documents during the initial response phase, don't wait for a follow-up request to add critical evidence. After Klarna begins review, expect a decision within 30–50 days.
Common pitfalls that turn winnable cases into losses:
Delivery address on evidence doesn't match the address on the transaction record (even minor formatting differences create review friction)
POD document is photographed at an angle, making the address or timestamp illegible
Partial shipments are submitted as complete delivery without a line-item breakdown
Recipient name on the POD doesn't match the buyer name on the order
Escalation filed on Day 19 with no buffer, a portal timeout or upload error means the case closes
Response templates submitted without populating evidence reference fields (a reviewer sees "[TRACKING_NUMBER]" literally in the text)
For merchants handling transaction disputes at scale, the volume of individual deadline checks, evidence pulls, and portal submissions across PayPal and Klarna queues creates meaningful manual overhead. Platforms like Guzco connect directly to carrier APIs, OMS data, and payment providers to compile and submit provider-specific evidence packages automatically, moving dispute outcomes from the industry average of around 20% win rates to 90%+ without a dedicated fraud team or manual queue management.
For Klarna-specific automation details, see the Guzco Klarna solution. For managing fraud risk management more broadly across your operation, including order-level risk scoring to reduce the volume of disputes reaching the claims stage, the same data infrastructure that powers dispute responses also feeds pre-shipment eligibility checks.
GUZCO
Keizersgacht 264
1016EV Amsterdam
As featured in
© 2026 Guzco AI. All rights reserved.