Shipped, in-store, and digital merchandise. Evidence requirements, critical mistakes, and winning response frameworks across all four major networks.
The cardholder claims they paid for merchandise but never received it. This is most common for online transactions where merchandise must be shipped, but it also occurs on in-store transactions — particularly where delivery is scheduled after purchase.
Unlike fraud disputes, the customer is acknowledging that they participated in the purchase. They know what they bought, when they bought it, and when they expected to receive it. That distinction matters: you are not defending an unauthorized transaction, you are defending that delivery occurred or that delivery is not yet overdue by the original agreement.
All four major networks cover this dispute type under different codes. The requirements are similar, but each network weights evidence differently. Our recommendations are calibrated to meet the highest bar across all four.
| Network | Code | Official Name |
|---|---|---|
| Visa | 13.1 | Merchandise/Services Not Received |
| Mastercard | 4853 | Goods or Services Not Provided |
| American Express | C08 | Goods/Services Not Received or Only Partially Received |
| Discover | RG | Non-Receipt of Goods, Services, or Cash |
These three requirements form the foundation of every Item Not Received response. Missing any one of them puts the dispute at serious risk, regardless of what else you submit.
This is the core of your case. The requirement varies by how the item was sold:
| Delivery Method | Evidence to Provide |
|---|---|
| Shipped | The carrier tracking number or bill of lading. This is your minimum viable evidence for any shipped order. |
| In-Store (immediate) | A clear statement that the customer took possession of the merchandise at the time of the transaction. Do not assume this is obvious — say it explicitly. |
| In-Store (future delivery) | A statement of how the customer will take possession, plus shipped evidence if the item will be shipped from the store. |
| Digital | Proof that access was made available. For login-based products, show the account has the item. For email delivery, show the email was sent. |
If the customer filed too early and the item is not yet overdue, you need to demonstrate that clearly:
| Delivery Method | Evidence to Provide |
|---|---|
| Shipped | The original order confirmation showing the estimated delivery date communicated at the time of purchase. |
| In-Store (future delivery) | Order details showing when the item will be available for pickup or delivery. |
| Digital | Order details showing the expected availability date disclosed at checkout. |
Issuers need confirmation the merchant shipped to the right place — not a default address or a merchant-side error:
| Delivery Method | Evidence to Provide |
|---|---|
| Shipped | The shipping address the customer entered during checkout, confirmed from your order record. |
| In-Store (future delivery) | Invoice or receipt showing the agreed-upon delivery address. |
| Digital | The email address entered by the customer during checkout, confirmed from your order record. |
Required evidence establishes that you tried to deliver. Strongly recommended evidence establishes that the customer actually received it. The distinction is critical: issuers can accept your required evidence while still ruling for the cardholder if there is no proof the right person received the item.
| Delivery Method | Evidence to Provide |
|---|---|
| Shipped |
A screenshot of the delivery confirmation from the carrier portal — not just a tracking number, but confirmation showing the specific delivery date, time, and address. If the delivery required a signature, include a screenshot of the signature and the name of the package acceptor. This is typically not visible via a public tracking lookup, so if you can see it in your account, the reviewer cannot find it independently — include it. Include carrier delivery photos if available, but do not rely on them as primary evidence. |
| Digital |
Proof the customer actually accessed the item — not just that access was made available. Login timestamps with IP address, download records, or proof of usage. Document that the IP address at purchase matches the IP of subsequent usage. This is strong evidence the same person who bought it also used it. |
It's difficult to prove something that never happened. Rather than trying to show "proof" of no contact, make a clear, assertive statement that the customer never raised a delivery concern — and shift the burden of proof back to them. A simple, confident assertion carries more weight than an absence of records.
The same burden-of-proof principle that governs non-receipt claims works in your favor when customers claim they returned merchandise. Just as you must prove the customer received a delivery (not just that you shipped it), customers must prove you received a return (not just that they shipped it back). A tracking number showing a package was sent to your general area is not proof your business has the merchandise in its possession. This is one of the most underutilized defenses in chargeback representment. See our Returned Merchandise & Credit Not Processed Defense Playbook for the complete framework.
These items rarely win a dispute on their own, but they round out your case and become important if the dispute escalates to network arbitration.
If your checkout flow requires the customer to view or acknowledge these policies before completing the purchase, include a screenshot of that step in your documentation. It is significantly harder for a cardholder to claim they were unaware of policies they were required to acknowledge.
Item Not Received is one of the most winnable dispute types when merchants have solid logistics data. It is also one of the most commonly lost — not because merchants lack evidence, but because they mishandle what they have.
An unsigned proof of delivery does not prove the right person received the package. The cardholder can deny receipt, and because you cannot prove who accepted the delivery, they will typically win. Networks hold merchants responsible for ensuring items reach the correct recipient.
Require signature confirmation for high-value shipments. When responding, include screenshots of all tracking details available in your account — not everything visible to you is accessible via a public tracking lookup, and it doesn't count as evidence if the reviewer can't see it.
A different shipping and billing address immediately raises a red flag. Reviewers assume the cardholder at the billing address never received anything because the package went somewhere else.
Document why the addresses differ: include the customer's email requesting alternate delivery, proof of prior successful deliveries to that address, or evidence it is a known business or workplace address for the customer.
Many merchants process transactions in-store but deliver products later. If you treat same-day in-store pickup as self-evident, you risk failing to directly address the customer's claim that they did not receive the item — which is the entire dispute.
Be explicit. If the customer completed the transaction and walked out of the store with the merchandise in hand, say exactly that in plain language.
If you promised 5-7 day delivery but shipped 14 days later, the customer may have reasonably assumed the order was cancelled and made other arrangements. Networks side with customers on unreasonable delays unless there is strong proof the customer now has possession.
For delayed shipments, provide three things: (1) evidence you notified the customer of the delay, (2) the customer's acknowledgment or absence of a cancellation request, and (3) a brief explanation of why the delay occurred.
Evidence that you sent a download link is weak on its own. Anyone can claim the link never worked or the email never arrived. Networks need proof the customer received and used the product.
Provide server logs showing login timestamps and IP addresses, download records, usage statistics, screenshots of account activity, or completion certificates for courses. The stronger the access and usage data, the harder the claim becomes to sustain.
How you present your evidence matters as much as what you submit. Reviewers are processing many cases — a well-structured response that leads with your strongest evidence gets more attention than a document dump in chronological order.
State the facts of the delivery in plain language. Do not make the reviewer infer anything from your documents — lead them to the conclusion you want.
Put your strongest evidence first, not your oldest. Reviewers pay the most attention at the start and fade as the document grows longer. If you have a signed delivery confirmation or a post-delivery product review, those belong on page one — not buried at the end.
| Priority | Evidence Type |
|---|---|
| First | Delivery confirmation — tracking screenshot, GPS coordinates, signature, carrier photo. |
| Second | Post-delivery customer behavior — product review, warranty registration, support contact about the product, account activity for digital goods. |
| Third | Shipping and order documentation — confirmation email, shipment notification, address on order. |
| Last | Supporting policies — shipping policy, cancellation and return policy, prior order history. |
Every piece of documentation should be named, numbered, and given a one-sentence explanation. Do not make the reviewer guess what they are looking at. Context shapes how evidence is perceived.
The situation: $285 purchase of wireless headphones. Cardholder disputed 27 days after delivery claiming "I never received this item. Maybe they delivered it to the wrong address or it was stolen."
| Page | Evidence |
|---|---|
| 1 | FedEx tracking confirmation showing delivery on 6/18/24 at 2:34 PM at 742 Maple Street, Austin TX, with FedEx delivery photo of the package on the front porch. |
| 2 | Customer product review posted 6/25/24 — seven days after delivery — stating "Great sound quality, battery life is amazing!" Plus warranty registration on 6/20/24 using the serial number from the delivered headphones. |
| 3 | Shipment confirmation email sent 6/15/24 to the customer, with read receipt showing the email was opened the same day. |
| 4 | Packing slip and warehouse photo of the headphones in the box before sealing. Order confirmation showing billing and shipping addresses as identical. |
Result: Chargeback successfully represented. Claim abandoned.
The situation: $129 monthly subscription box. Cardholder disputed claiming "I never received my March box and they won't respond to my emails."
Result: Dispute ruled in cardholder's favor.
| Mistake | Explanation |
|---|---|
| No tracking number provided | Claimed tracking showed delivery but never included the actual number. The reviewer could not verify anything. |
| No delivery address shown | Never demonstrated where the package was delivered — the most basic requirement. |
| Defensive framing | Focusing on a 99% success rate is irrelevant to this specific transaction. It reads as deflection. |
| Accused the customer | "Trying to steal our product" shifts the tone from factual to adversarial. Reviewers respond to evidence, not frustration. |
| Irrelevant terms of service | Networks do not honor merchant policies that disclaim liability for stolen packages. If you arrange shipping, you are responsible for delivery to the correct recipient. |
Run through this checklist before finalizing your response.
The most effective chargeback defense is the evidence you collect before a dispute is ever filed. These steps reduce your exposure and build a documentation trail that makes responses straightforward.
| Action | Why It Matters |
|---|---|
| Require signature for high-dollar orders | Make it optional at lower thresholds and mandatory above a set amount. The shipping upcharge is small compared to the liability reduction on disputed high-value orders. |
| Send automated shipment notifications within 24 hours | Email customers with tracking numbers and carrier links when orders ship. This single step reduces non-receipt disputes by 47% — customers who can track their package file far fewer claims. |
| Enable carrier delivery photos | UPS, FedEx, and Amazon offer photo-on-delivery at no extra cost. Enable it across all shipments. A delivery photo combined with tracking confirmation is a significant upgrade over tracking alone. |
| Verify addresses at checkout | Use USPS Address Verification or a similar service to catch errors before shipping. When shipping and billing addresses differ, send a confirmation email asking the customer to verify before the order ships. |
| Build post-delivery touchpoints | Email customers 5–7 days after delivery asking for reviews, sharing tips, or offering support. Any reply proves receipt. Save every interaction — these emails become your evidence. |
| Use delivery confirmation as your baseline | Not just tracking ("in transit"), but delivery confirmation ("delivered"). For orders over $50, this is a minimum. It costs almost nothing and provides a meaningful baseline of dispute protection. |
| Document at packaging time | Take photos of items being packed, shipping labels, and tracking numbers at the moment of fulfillment. Tools like ShipStation or Shopify can automate this. You cannot prove delivery with evidence you never preserved. |
| Consider separate transactions for separate shipments | Visa requires customers who file non-receipt chargebacks on three or more transactions with the same merchant to provide a written statement explaining why they continue to purchase from a merchant that allegedly does not deliver. This creates significant friction that discourages serial non-receipt claims. By processing individual items or shipments as separate transactions rather than one bundled charge, you reach this threshold faster if a customer disputes multiple items — activating a powerful built-in deterrent. |
This playbook is updated at least twice annually to reflect changes in network rules and issuer practices. Document Version: 2026.1 · Last Updated: February 3, 2026 · Covers: Visa 13.1 / Mastercard 4853 / Amex C08 / Discover RG
Continue building your chargeback defense knowledge: