Visa 13.1 wins on structure, not volume.The dispute is decided in the first 60 seconds an issuer analyst spends on your rebuttal. A short cover narrative + one delivery-proof document + one identity-continuity document (CE 3.0 if you qualify) beats a 40-page kitchen-sink packet almost every time. If you sell physical goods with real tracking and can name the customer, you should be winning > 70% of your 13.1 disputes. If you're not, this playbook is why.
What Visa 13.1 actually means
Visa reason code 13.1 covers "Merchandise/Services Not Received"— the cardholder claims they paid but never received the goods or service. It lives in Visa's Consumer Disputes category (Dispute Category 13), the same bucket as 13.2 (defective merchandise) and 13.5 (misrepresentation).
Critically, 13.1 is a consumerdispute, not a fraud dispute. The cardholder isn't claiming their card was stolen — they're claiming the merchant failed to deliver. That distinction is what makes 13.1 winnable: fraud disputes turn on whether the transaction was authorized, but consumer disputes turn on whether the merchant did what they promised. And "we shipped it, here's the tracking" is a much easier claim to prove than "the transaction was authorized."
The cardholder's trigger is usually one of: (a) the package took longer than expected and they filed before it arrived; (b)the package was marked delivered but they can't find it; (c)genuine friendly fraud — the goods arrived, someone in the household kept them, and they're disputing the charge anyway. All three respond to the same evidence stack.
Deadlines & the response window
Visa gives merchants 30 calendar days from the chargeback date to submit representment. Miss the deadline and you automatically lose — the funds are gone and the reason code is closed. Some acquirers apply an internal 20-day cap to leave themselves buffer, so the effective merchant window is often shorter.
On Stripe, the true deadline is in dispute.evidence_details.due_by— treat that as gospel. On PayPal Braintree, it's dispute.replyByDate. Shopify Payments surfaces it directly in the admin dispute detail view. If you're operating manually without an automation, put every open dispute on a spreadsheet with due_by - 3d as the operational deadline.
The issuer's review after you submit typically takes 30–45 days. During that window nothing you do matters — the case is with the issuer, and Visa disallows contacting them directly. If they rule against you, your only path forward is pre-arbitration (which we cover in the CE 3.0 section below).
The evidence stack that wins
A winning 13.1 packet has four pieces. Not forty. Four. Issuers spend under a minute per case; length actively hurts you by burying the strong evidence.
Delivery proof
Carrier tracking (USPS / UPS / FedEx / DHL / OnTrac) showing Deliveredstatus with a delivery date and — critically — a delivery address that matches the AVS-verified address on file. If the carrier provides a signature or proof-of-delivery image (EasyPost's Tracker API surfaces these), attach it.
Fulfillment record
A timestamped record from your OMS or Shopify order detail showing when the order was placed, packed, and shipped. The point is to demonstrate that fulfillment happened before the cardholder filed the dispute — issuers are trained to spot merchants who ship late and then blame the customer.
Customer communication history
Shipping notification email with tracking number, delivery-confirmation email, and any support tickets. If the cardholder emailed after delivery — even to ask a question — that's gold. It proves they knew the order arrived.
Identity continuity (CE 3.0)
Records of at least two prior undisputed transactions from the same cardholder in the past 120–365 days, with matching IP, device fingerprint, or shipping address. This is the CE 3.0 evidence and it's the strongest single piece you can submit — see the next section.
Compelling Evidence 3.0 qualification
Visa's Compelling Evidence 3.0 rules went live in April 2023. When your evidence qualifies under CE 3.0, the issuer is requiredto accept the representment — not "encouraged," not "persuaded." Required. It's the single highest-leverage change to Visa's dispute rules in a decade.
To qualify a 13.1 dispute for CE 3.0, you need to show:
- At least two prior undisputed transactions from the same cardholder, at least 120 days before the disputed transaction and no more than 365 days before it.
- Matching identifier across all three transactions — the same IP address, device fingerprint, shipping address, or customer account ID.
- None of those prior transactions were disputed — even a soft chargeback that was later reversed disqualifies the sequence.
If you meet all three conditions, submit the identity-continuity evidence with your representment and reference CE 3.0 explicitly in the rebuttal narrative ("This dispute qualifies for Compelling Evidence 3.0 under Visa Core Rules 11.4"). Well-qualified CE 3.0 responses win in the 85–95% range in our book — dramatically better than the ~65% baseline for 13.1 without CE 3.0.
Digital goods & services
Physical-goods 13.1 wins on delivery proof. Digital goods and services can't use delivery proof — there's nothing to ship. What replaces it is access proof:
- Login timestamps from the customer's account, matched to the IP used at purchase.
- Device fingerprint at first successful access.
- Feature-usage logs — download timestamps for a file, streaming session logs, API calls made against an issued key.
- For SaaS: recorded usage over multiple sessions across days, not one login.
Digital 13.1 has a lower baseline win rate (~35–50%) precisely because access proof is easier to hand-wave away as "someone else logged in." CE 3.0 helps enormously here — the same identity-continuity data that proves "this customer bought from you three times before" also proves they're the one accessing the account now.
Three mistakes that lose winnable cases
Almost every 13.1 loss we've reviewed traces to one of these three:
1. Kitchen-sink packet
A 40-page PDF with the ToS, privacy policy, ten screenshots of the order status page, and no clear narrative. Issuers won't read past page 3. Lead with the delivery proof, put everything else in appendices.
2. No AVS match reference
Delivery to 123 Elm St. and AVS-verified billing at 456 Oak Ave. isn't automatically a loss — but if you don't explain it (e.g. gift, shipped to work address), the issuer will assume the delivery was to a friendly-fraud accomplice.
3. Late fulfillment, no explanation
Order placed on the 1st, shipped on the 15th, cardholder disputed on the 12th. Technically you can still win, but you have to address the delay directly — otherwise the issuer sees a merchant who took payment then sat on the order.
Rebuttal narrative template
Every 13.1 representment should open with a 3-sentence cover narrative that tells the issuer exactly what happened. Here's the template we use in Aurai:
Sentence 1: Cardholder [name], order #[X], placed on [date], fulfilled and shipped on [date] via [carrier] with tracking [number].
Sentence 2: Carrier records confirm delivery on [date] to [address], which matches the AVS-verified billing address on file (proof attached).
Sentence 3: [If CE 3.0 qualifies] This dispute qualifies for Compelling Evidence 3.0 under Visa Core Rules 11.4, with two prior undisputed transactions from the same cardholder / IP / device on [dates] (proof attached).
That's the whole thing. Three sentences, one paragraph, followed by the four attachments in order. Add a fifth "we attempted to contact the customer on [date] with no response" sentence if it's true — it demonstrates good faith and issuers weight it.
Frequently asked questions
What is Visa reason code 13.1?
Visa 13.1 covers "Merchandise/Services Not Received" — the cardholder claims they paid for something that never arrived. It's the most common ecommerce dispute reason and lives in Visa's Consumer Disputes category.
How long do I have to respond to a Visa 13.1?
30 calendar days from the chargeback date. Miss the deadline and you automatically lose. Some acquirers apply an internal 20-day cap — check evidence_details.due_by on Stripe or the equivalent on your processor.
Does Compelling Evidence 3.0 apply to 13.1?
Yes. CE 3.0 applies to 13.1 for digital goods, ongoing services, and physical goods with delivery. If you can show two prior undisputed transactions from the same cardholder with matching IP, device, or address, the issuer is required to accept the representment.
What's the industry win rate on Visa 13.1?
Well-represented physical-goods 13.1 disputes with delivery proof win 60–80%. With CE 3.0 that jumps to 85–95%. Digital-goods 13.1 without CE 3.0 wins 35–50%. Merchants who submit no evidence win under 10%.
Can Aurai handle 13.1 disputes automatically?
Yes — 13.1 is one of the reason codes Aurai handles end-to-end. We pull carrier tracking (including proof-of-delivery images), assemble the four-part evidence stack, check CE 3.0 qualification against your transaction history, and submit before the deadline. You pay 25% only on disputes we win.
This playbook reflects our reading of Visa Core Rules v2025.1 and the Aurai team's own book of disputes as of July 2026. Visa is a trademark of Visa Inc.; Aurai is independent and not endorsed by Visa. Network rules change — always check the current Visa Core Rules and Product and Service Rules for the official language before acting on any specific tactic.