Visa 13.1 (Merchandise Not Received): The Winning Evidence Checklist

A Visa 13.1 chargeback lands when a customer tells their bank they paid you but never got what they ordered. The good news: it is one of the most winnable reason codes there is, because delivery either happened or it didn’t, and the carrier keeps the receipt.

What Visa reason code 13.1 means

Visa 13.1 — Merchandise/Services Not Received is filed when a cardholder acknowledges they made the purchase but claims the goods never arrived or the service was never provided. It sits in Visa’s Consumer Disputes group (reason codes starting with 13), which is distinct from the fraud group (reason codes starting with 10).

That distinction matters. The customer is not saying “I didn’t authorize this.” They are saying “I authorized it, I paid, and I got nothing.” So your job in representment is narrow and concrete: prove the customer received the merchandise or that the service was made available.

Common triggers for a legitimate 13.1:

• A package genuinely lost or delayed in transit
• An order that shipped to an old address
• A service the customer expected but that was never activated
• A delivery date that fell after the customer’s patience ran out

And common triggers for an illegitimate 13.1 (friendly fraud):

• The item was delivered but the customer forgot or claims otherwise
• A household member received it
• Buyer’s remorse dressed up as non-delivery
• Deliberate abuse to keep the product and the money

Your evidence doesn’t need to guess the customer’s motive. It just needs to show delivery.

Why delivery and tracking proof is decisive

For 13.1, delivery evidence is the whole ballgame. Visa’s own dispute rules for this reason code look for compelling evidence that the merchandise was received or the service was rendered. Carrier tracking is the single strongest artifact you can submit, because it is timestamped, third-party, and hard to argue with.

The strongest delivery evidence has three properties:

1. A delivered status from the carrier, not just “in transit” or “label created.”
2. An address match — the delivery address on the tracking record lines up with the cardholder’s billing or confirmed shipping address.
3. A signature or proof of receipt where the carrier captured one, especially for higher-value orders.

When those three line up, most issuers rule in your favor because the customer’s core claim — non-receipt — is directly contradicted by the record.

The 13.1 winning evidence checklist

Assemble as many of these as apply to the order. More corroborating documents means a stronger representment.

Include a short written rebuttal that walks the reviewer through the timeline: order placed, shipped, tracking milestones, delivered on a specific date to the customer’s address. Make the reviewer’s job easy — point at the delivered status and the address match explicitly.

For a broader framework on building a persuasive submission, see how to win a chargeback dispute.

The digital-goods nuance: proving delivery with no shipment

Plenty of 13.1 disputes involve software, subscriptions, downloads, courses, or other services where nothing physical ships. You can still win — you just prove availability and use instead of shipment.

For digital and service-based orders, gather:

• Access and login logs showing the customer’s account was active
• Download or streaming timestamps proving the content was retrieved
• IP address records that match the customer’s location or prior sessions
• License or activation keys and the record of when they were issued and used
• Email confirmations delivering credentials, links, or receipts
• Usage data — API calls made, lessons completed, sessions logged

The argument writes itself: the customer says they received nothing, but here are the timestamps showing they logged in, downloaded the file, or used the service. For subscriptions, evidence of prior successful billing periods and continued usage is especially persuasive.

Because there is no carrier record for digital goods, the completeness of your logs is what carries the case. This is exactly the kind of evidence that is easy to lose track of manually and easy to capture automatically.

The time limit — and why it’s the real risk

The response deadline for a Visa dispute is set by the network and surfaced by your processor, and for Visa it commonly falls around 20 to 30 days from when the dispute is filed. Your processor’s dashboard shows the exact due date for each case.

That deadline is firm. If you submit even a day late, you lose automatically — no matter how conclusive your tracking is. The most common way merchants lose winnable 13.1 disputes isn’t weak evidence; it’s a missed deadline, a case that slipped through a busy week, or evidence that got assembled too slowly.

For the full picture on how the various clocks work across networks, see how chargeback reason codes are structured and the broader Visa reason code reference.

Bottom line

Visa 13.1 is a delivery question, and delivery leaves a paper trail. Prove the package arrived at the cardholder’s address — or that the digital service was accessed — and you win the overwhelming majority of these cases. The two things that lose them are incomplete evidence and blown deadlines.

That is precisely what automation removes. DisputeDash detects a 13.1 the moment your processor reports it, pulls the carrier tracking (across 1,200+ carriers), matches the delivery address, assembles the reason-code-specific evidence, and submits before the deadline — so a winnable case never becomes a lost one.