Recover 4x more chargebacks and prevent up to 90% of incoming ones, powered by AI and a global network of 20,000 merchants.
For an Item Not Received case, merchants should provide records that connect the disputed purchase to shipment, delivery, or digital fulfillment. The required evidence depends on the item and the case instructions. Proof that an order was created is different from proof that the customer received it.
Written by Jodi Lifschitz, Head of Content at Chargeflow. Updated 12 October 2026.
Scroll to compare all columns. Use the arrow keys when the table is focused.
| Order type | Evidence to gather | Check before submitting |
|---|---|---|
| Physical goods | Carrier tracking, shipment and delivery dates, delivery status, and destination details. | Match the record to the order and the transaction address. |
| Digital goods | Dated electronic delivery, access, or download records with recipient identifiers. | Connect the event to the purchased item and customer. |
| Services | Agreed scope, completion records, and relevant acknowledgments. | Explain what was fulfilled and when. |
PayPal’s proof-of-shipment and digital-delivery guidance describes physical documentation and electronic records. For intangible items, records may show when the item was sent and the recipient address, or that the recipient received or accessed it. Additional eligibility requirements still apply.
No universal current threshold should be assumed. The U.S. help guidance distinguishes transactions before January 26, 2026, over $750 USD, for which signatures are required, from later transactions, for which signatures are recommended but not mandatory. Check the terms applicable to the transaction and follow the case request.
Use the case instructions and deadline
Build an order-linked delivery response
Read the case
Identify the disputed transaction and the information requested.
Create the chronology
List payment, fulfillment, shipment or provisioning, delivery or access, and the complaint.
Attach relevant records
Include readable evidence with identifiers that connect it to this order.
Explain discrepancies
If an address, date, or status differs, describe what happened rather than omitting it.
Confirm submission
Retain the response confirmation and monitor follow-up requests.
Example: An order paid on September 1, shipped on September 2, and delivered on September 5 has three different dates. The response should explain that sequence. Delivery does not need to occur on the payment date.
For the complete response process, use our Item Not Received dispute guide. For coverage, see Seller Protection requirements; for case stages, see the PayPal disputes overview.
Check the carrier or fulfillment system for additional records and document the result. A shipping label alone does not establish completed delivery. A digital account’s existence alone does not establish that the purchased content was delivered or used. If your investigation confirms a fulfillment problem, evaluate an appropriate customer remedy.
Keep the response factual and specific. Coverage eligibility, the evidence requested, and the dispute outcome are separate considerations. Our evidence preparation guide can help structure supporting records. If a decision needs review, consult PayPal dispute appeals.
Teams connecting dispute operations can explore Chargeflow’s PayPal integration.
| Record | What it can support | What remains missing |
|---|---|---|
| Carrier record marked delivered, with date, tracking and matching transaction destination | Physical delivery evidence when the applicable policy requirements are met. | Other coverage conditions and the facts of the complaint still need review. |
| Shipping label or “label created” status | Preparation for shipment. | Carrier delivery, delivery date, and destination confirmation. |
| Tracking marked delivered to a different destination | A delivery event at that recorded destination. | A match to the address required by the transaction and applicable policy. |
| Dated digital fulfillment export tied to payment, item and recipient | Electronic delivery or access for that specific purchase. | Additional intangible-goods eligibility and any unresolved access problem. |
| Account signup screenshot with no purchased entitlement | An account exists. | Delivery or use of the item actually paid for. |
Address-match checklist: save the Transaction Details shipping address; save the carrier destination and delivery status; compare the permitted address details; explain differences and address changes; retain the payment-to-order-to-parcel connection. PayPal’s U.S. Seller Protection terms specify the U.S. delivery-proof standard. Do not treat this example table as a universal coverage approval.
Illustrative digital record: payment PP-DIG-22 → order D-22 → file version V3 → recipient buyer@example.com → download completed 5 September 2026 at 16:24 UTC. Explain what “completed” means in your system. A delivery email marked sent and a successful download are different events; retain failures and remedies as well.
Yes. Relevant electronic records can support fulfillment, subject to the case and applicable program requirements. Connect timestamps and recipient identifiers to the disputed purchase.
A number alone may not establish delivery. Provide the associated carrier information and explain how it matches the order and destination.
No. The reviewer evaluates the case and applicable requirements. Submit relevant, complete records by the requested deadline.
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.