Recover 4x more chargebacks and prevent up to 90% of incoming ones, powered by AI and a global network of 20,000 merchants.
An unauthorized PayPal claim is a report that an account holder did not approve a payment. To reduce these claims, make purchases recognizable, review suspicious order activity, and keep records that connect the payment to fulfillment.
Written by Jodi Lifschitz, Head of Content at Chargeflow. Updated 12 October 2026.
An unauthorized claim can involve account takeover, an unrecognized purchase, or friendly fraud. Do not classify every claimant as dishonest. Review the order history, customer messages, account activity, and fulfillment record before deciding how to respond.
Keep an internal reason for each decision: fulfillment error, payment recognition issue, suspected account compromise, or disputed authorization. This helps you distinguish a service problem from an abuse pattern and choose an appropriate prevention control.
Payment recognition and risk review
Five controls for avoidable unauthorized claims
Recognizable confirmation
Send an order confirmation that clearly identifies your store, the purchase, and a support contact.
Contextual order review
Review unusual combinations of order value, account changes, delivery requests, and purchase history. Escalate uncertain orders for review.
Connected records
Keep a single record connecting the payment ID, order ID, buyer communication, and fulfillment evidence.
Useful customer support
Provide prompt support when a buyer asks about a charge. Explain the purchase clearly and investigate legitimate concerns.
Repeat-pattern review
Review repeated abuse using identity and behavioral signals. Chargeflow Prevent supports post-purchase fraud and abuse prevention; do not treat it as a guarantee that every future disputed order will be blocked.
Build these controls into your ecommerce fraud prevention process. Chargeflow Prevent can complement that process by identifying patterns relevant to post-purchase abuse.
Under PayPal’s U.S. Seller Protection terms, unauthorized claims require eligible transactions and qualifying fulfillment proof. For physical goods, use the address on Transaction Details. For unauthorized claims, proof must show shipment or provision no later than two days after notification; this is not a universal evidence-upload deadline. Digital goods have additional eligibility and fulfillment requirements. Terms vary by account country.
Use the case notification to identify the actual response deadline. Keep the eligibility check separate from your operational investigation: a transaction status is one part of the assessment, not a promise of a particular outcome.
Follow the case route and deadline
Build a traceable PayPal response
Case details and owner
Record the case ID, payment ID, claim type, deadline, and assigned owner.
Purchase and communication
Collect the order confirmation and relevant customer correspondence.
Physical fulfillment
For shipped orders, capture the tracking history and the transaction’s delivery address.
Digital fulfillment
For digital orders, preserve dated fulfillment or access records linked to the recipient.
Attachment explanation
Explain what each attachment demonstrates. Include only records you can substantiate.
PayPal account claims and bank-filed chargebacks follow different processes. Identify the route before choosing your evidence; the dispute and claim stages explain the distinction. A delivery complaint needs its own item-not-received response, while a closed claim calls for an appeal review.
Illustrative case: a parcel was delivered to the transaction address, but the account holder reports a compromised PayPal account. Preserve the delivery record and investigate the account/authorization complaint; do not answer it only with tracking. Record payment ID, alleged unauthorized activity, case route, protection status, and relevant purchase and fulfillment records.
Use PayPal’s U.S. Seller Protection terms to distinguish unauthorized-payment coverage from Item Not Received coverage and their different proof conditions. A paid invoice establishes a payment record; it does not settle who approved it. Escalate missing or contradictory records to the source owner using the chargeback evidence source map.
Unauthorized PayPal claims can reflect account theft, confusion, or misuse. Investigate the available records before classifying the claim.
Tracking alone does not guarantee Seller Protection. Check the applicable policy, transaction eligibility, fulfillment requirements, and requested response.
A merchant receiving an unauthorized claim should open the case, record its deadline, and pause any automatic response until the claim route and evidence needs are clear.
Merchants can review repeat claims by cause and connected order history, then adjust communication, fulfillment, or abuse controls. A blanket block on everyone who has filed a dispute can also exclude legitimate customers.
For connected dispute management, review the verified PayPal integration and automated chargeback recovery workflow.
Recover 4x more chargebacks and prevent up to 90% of incoming ones, powered by AI and a global network of 20,000 merchants.
Track disputes across accounts with consistent metrics, reconciled recovery, currency controls, and clear treatment of pending cases.
Standardize chargeback evidence with reusable source records, case-specific selection, quality controls, and verified submission.
Align support and payments with shared case records, refund controls, escalation ownership, and practical dispute-prevention workflows.
Chargeflow collects data from dozens of third party signals, not just transaction data like Stripe Dispute does. This allows for much more coverage and much better win rates because the evidence submitted is much more comprehensive and compelling..
Chargeflow collects data like order info, customer messages, and payment details. It builds a full dispute case for you, so you don’t have to lift a finger.
Yes! Chargeflow works with many processors — not just Stripe. That means one tool for all your chargebacks, no matter how you process payments.
Chargeflow Automation uses success-based pricing on recovered chargebacks. Other Chargeflow products have separate pricing. Check the pricing page and your agreement for the applicable terms.
Chargeflow’s security documentation describes SOC 2 Type 2 compliance, GDPR compliance, encryption at rest and in transit, and access controls. Review the security page for details on its safeguards and data handling.
Have a question? We’re here to help. Just hit the chat button to initiate a conversation with support.