ArticlesChargebacksWhat actually wins a Visa reason code 13.1 dispute on Shopify

What actually wins a Visa reason code 13.1 dispute on Shopify

Ben Woodward

GM, Redo

What actually wins a Visa reason code 13.1 dispute on Shopify

A $68 hoodie shows delivered on the carrier's tracking page. The customer's bank says it never arrived. The merchant attaches the tracking screenshot and the order confirmation, and loses the case three weeks later.

That is reason code 13.1, Visa's label for merchandise or services the cardholder says they never received. Winning it means answering one narrow question: did the cardholder, or someone authorized to receive on their behalf, get the order at the address on file, by the date they were told to expect it. Not whether the order happened. Whether it arrived.

What Visa reason code 13.1 actually alleges

Visa's own rulebook, the Visa Core Rules and Visa Product and Service Rules, defines Condition 13.1 in one sentence: the cardholder participated in the transaction, but the cardholder or an authorized person did not receive the merchandise or services because the merchant was unwilling or unable to provide them (Visa Core Rules and Visa Product and Service Rules, 18 April 2026 edition, Section 11.10.2.1, checked July 22, 2026).

One sentence, three different situations. Nothing arrived at all. Something arrived, but after the date the customer was told to expect it. Something arrived, but not to the customer. Which of those you are actually facing changes which evidence matters most, and I have mapped that out in full in how to fight a product not received chargeback on Shopify. This piece stays one level down: what Visa's own rule requires from a response, and how to build toward it.

Visa's rule also states when a 13.1 dispute is invalid on its face. A cardholder who cancelled before the expected delivery date, ordinary buyer's remorse, cannot use this code. Neither can a claim that is really about quality or condition, or one where the cardholder states the transaction itself was fraudulent (Visa Core Rules and Visa Product and Service Rules, Section 11.10.2.3, checked July 22, 2026). If the customer's own words in the dispute describe a damaged or wrong item rather than a missing one, that is a possible miscoding worth raising with your acquirer, not a delivery-evidence problem.

The evidence Visa's own rule requires, not a paraphrase of it

Most guidance on this code is a vendor's summary of a summary. Visa publishes the actual requirement, and it is more specific than most articles let on.

For a shipped item, Visa's response rule asks for proof of delivery that contains the full delivery address, and it says so in language that leaves nothing to interpret: "tracking with partial address is not permitted" (Visa Core Rules and Visa Product and Service Rules, Section 11.10.2.6, checked July 22, 2026). For an order collected in person, it asks for an acknowledgment captured at pickup instead: a signature, a PIN, or a collection code.

The same rule set covers other response categories: a credit or reversal already issued, a written statement that the cardholder no longer disputes the charge, and for a card-present sale, certification that the customer took the merchandise at time of sale. The table below lines these up against what that looks like inside a Shopify order.

Visa's response requirementSatisfies it on ShopifyDoes not satisfy it
Proof of delivery, full addressCarrier event history ending in a delivery scan, with the delivered-to address matched to the order's shipping addressTracking number alone, or a partial address. Visa: "tracking with partial address is not permitted"
Pickup acknowledgment (card-absent collection)Signature, PIN, or collection code captured at handoffAn order marked fulfilled with no record of who collected it
Cardholder no longer disputesA dated customer message referencing the item after deliveryAssuming silence after delivery means acceptance
Credit or reversal already issuedShopify's own refund record, with amount and dateA refund the customer's bank has not yet posted

Sources: Visa Core Rules and Visa Product and Service Rules, Section 11.10.2.6 (checked July 22, 2026); Shopify Help Center chargeback response documentation (checked July 22, 2026).

Building the packet from data Shopify already holds

Pull the full carrier event history, not the final status

A "Delivered" badge is one line in a longer scan history. The address tied to that specific scan is the line Visa's rule actually asks for, and it usually sits one click past the summary view most people screenshot.

Match the delivered-to address against the order's shipping address

Field for field, not just city and state. A carrier record that returns only a partial address is a gap to close before you submit, not evidence to submit as it stands. Shopify's own chargeback guidance recommends shipping address verification alongside tracking for exactly this reason (Shopify Help Center, checked July 22, 2026).

Capture a signature, photo, or geolocation where the carrier recorded one

This is the strongest single artifact available, and most merchants never pull it, because it sits one click deeper in the carrier's portal than the tracking summary does.

Attach the proactive delivery message you sent

The shipping confirmation or carrier notification that told the customer what to expect and when, dated, is evidence that the estimate came from you, not from the customer's own assumption.

Check the order's message thread for an acknowledgment

A sizing question, a review reply, a return request naming the item. Any of those functions as a cardholder statement that the item arrived, in their own words, which is one of the response categories Visa's guidelines describe (Visa Dispute Management Guidelines for Visa Merchants, June 2024 edition, checked July 22, 2026).

Assembling that from four separate systems, carrier, order, messaging, refunds, is most of what makes a single response take 20 to 45 minutes. Reclaim pulls the carrier record, the shipping address, and the message thread from the same Shopify order and files before the due date, at no install cost and no cut of what comes back.

Why an order confirmation or invoice does not answer the claim

An order confirmation states that a transaction happened. Nobody in a 13.1 dispute is arguing that it did not. The clearing record already told the issuer that much before the dispute was ever filed.

Stripe's own evidence guidance makes the same point from the processor side: a shipping tracking number added without proof of delivery or fulfillment history is treated as thin (Stripe dispute evidence documentation, checked July 22, 2026). A product-page screenshot answers a question about your storefront, not this customer's order. None of the three, confirmation, invoice, screenshot, contains an address, a delivery scan, or a signature, which is what Visa's rule actually asks for.

When conceding is the right call

Filing every 13.1 dispute is not a strategy. Some of them are not winnable no matter how the packet is built, and building one anyway spends the fee and the labor twice.

A genuinely lost package concedes itself. If the carrier's own event history stops mid-transit and never produces a delivery scan, there is no address to match and no signature to pull, because the thing you would be proving did not happen. If the shipment was insured, that is a carrier claim, not a chargeback response.

No tracking at all is the same problem, earlier. An untracked or unsigned shipping method leaves nothing to submit once a dispute lands, and that is a decision made back at checkout, not one you can fix after the fact.

A wrong-address case the customer caused is more nuanced. Visa's rule requires the cardholder to attempt to resolve with the merchant before a dispute is filed at all (Visa Core Rules and Visa Product and Service Rules, Section 11.10.2.2, checked July 22, 2026), worth raising with your acquirer if the shipping label matches what the order held at the moment it shipped. It is a point to raise, not a guarantee.

The same caveat that applies to every reason code applies here too. Winning a proof-of-delivery response recovers the money. It does not remove the dispute from the count your acquirer watches, since that count runs on filings, not outcomes. The fuller math on when any representment is worth the 20 to 45 minutes it takes, for this code or another, is in chargeback representment explained without the vendor spin.

One more timing detail worth planning around. Visa's rule lets a 13.1 dispute arrive up to 120 days after the last date the cardholder expected delivery, not to exceed 540 days from the original transaction (Visa Core Rules and Visa Product and Service Rules, Section 11.10.2.4, checked July 22, 2026). Carrier portals and message threads both age out well before that window closes, so the retention problem usually runs longer than most merchants plan for.

Frequently asked questions

What is Visa reason code 13.1?

Visa's label for a cardholder claim that they, or someone authorized to receive on their behalf, did not get merchandise or services they paid for. It covers items that never arrived, arrived late, or arrived somewhere else. It does not cover quality complaints or claims that the transaction itself was fraudulent.

Does a tracking number by itself win a 13.1 dispute?

No. Visa's own response rule states that tracking with a partial address is not permitted as evidence. A winning response needs the carrier's delivery scan matched to the full shipping address on the order, plus a signature, photo, or geolocation where the carrier captured one.

How long after the sale can a 13.1 dispute be filed?

Visa requires the issuer to wait at least 15 calendar days from the transaction, return, or cancellation date, then file no later than 120 days from the transaction processing date or 120 days from the last date the cardholder expected delivery, whichever applies, not to exceed 540 days total from the original transaction.

Should I fight a 13.1 dispute if the package was genuinely lost?

Usually not. If the carrier's event history never produces a delivery scan, there is no address or signature to submit, because the thing the response would need to prove did not happen. Concede it, and file a carrier claim separately if the shipment was insured.

The audit worth running on your last ten 13.1 disputes

Pull your last ten reason-code 13.1 cases and check one thing for each: does the carrier's own record show a full delivery address, not just a delivered status? If most of them fail that single test, the gap is not your win rate. It is that nobody is pulling the address line out of the tracking event before the response goes in.