%201.svg)
Why Do I Get So Many Item Not As Described Disputes?
Chargebacks?
No longer your problem.
Recover 4x more chargebacks and prevent up to 90% of incoming ones, powered by AI and a global network of 20,000 merchants.
600+ reviewsItem not as described (SNAD) disputes, Visa reason code 13.3, Mastercard 4853, happen when what arrives doesn't match the listing. Tighten product pages, use honest images, capture buyer acknowledgment, and submit matching evidence fast to prevent and win them.
What is an item not as described dispute?
An item not as described (SNAD) dispute is a chargeback a cardholder files when the product they received doesn't match the listing they bought, filed under Visa reason code 13.3 and Mastercard reason code 4853. Banks treat “not as described” as subjective, so they usually side with the cardholder unless you can prove the delivered item matched your description exactly. Both map to specific chargeback reason codes.
Why do you get so many item not as described disputes?
Most SNAD disputes come from expectation gaps, not defective products. Unclear specs, photos that oversell, and slow or confusing returns push customers to their bank instead of your support team. Because “not as described” is easy to claim and hard to disprove, it's also a common vehicle for first-party (“friendly”) misuse — which industry estimates put at well over half of all chargebacks — and the same behavior drives disputes customers file even after a refund. SNAD is also one of the most commonly lost categories; see why I keep losing chargeback disputes. For the psychology behind why shoppers dispute instead of returning, read Chargeflow's Psychology of Chargebacks report.
How do you reduce item not as described chargebacks?
- Audit your product pages like a buyer. Read titles, descriptions, and specs as if you have never seen the product. Remove vague claims. Add exact dimensions, materials, limitations, and what the product does not do.
- Fix images and videos. Lifestyle images cause more disputes than they prevent when they hide scale, texture, or color. Add neutral images, real lighting, and close-ups.
- Set expectations before checkout. Surface key details near the buy button. Sizing notes, compatibility warnings, digital access rules, or subscription terms should not be buried.
- Capture customer acknowledgment. Use checkboxes or confirmations for high-risk products so you can prove the customer understood what they were buying. Chargeflow Prevent stops friendly-fraud SNAD abuse before checkout.
- Track repeat dispute patterns. If the same SKU keeps getting item not as described claims, pause traffic and fix it. Chargeflow Insights helps spot these patterns early.
- Submit clear, tight evidence. When disputes still happen, use Chargeflow Automation to submit the exact product page, order details, and customer confirmations without gaps.
Which platforms see the most SNAD disputes, and why?
What evidence do you need to win an item not as described dispute?
FAQ
What reason code is used for item not as described?
Item not as described disputes file under Visa reason code 13.3 and Mastercard reason code 4853.
Is an item not as described dispute the same as fraud?
No. It's a consumer merchandise dispute, not criminal fraud, though the category is often misused as first-party (friendly) fraud.
Can I win an item not as described chargeback?
Yes. Submit the product page from the purchase date, full specs, and proof the delivered item matched the listing.
How do I prevent SNAD disputes?
Use accurate specs, honest images, clear pre-checkout terms, and buyer acknowledgment on high-risk products.
What evidence do I need for an item not as described dispute?
Product page screenshot, full description and specs, checkout images, order confirmation, customer acknowledgment, and proof the item matched.
Chargebacks?
No longer your problem.
Recover 4x more chargebacks and prevent up to 90% of incoming ones, powered by AI and a global network of 20,000 merchants.
.png)
More articles.
How Do I Track Dispute Performance Across Multiple Accounts?
To track dispute performance across multiple accounts, consolidate chargeback data from every processor, store, and merchant account into one dashboard, then compare the same core metrics, dispute rate, win rate, recovery rate, and reason-code trends at both account and portfolio level. Centralized reporting surfaces rising-risk accounts before they trip card-network thresholds like Visa’s VAMP.
How Do I Standardize Evidence Across Dispute Types?
Standardize chargeback evidence by building one core evidence package for every order, transaction, fulfillment, customer, and policy records, then layering in dispute-specific proof mapped to the reason code. A single repeatable framework beats managing evidence reason code by reason code: it closes gaps, speeds responses, and lifts win rates.
How Do I Align Customer Support and Payments to Reduce Disputes?
Many chargebacks start as unresolved support issues, not payment problems. When customer support and payments share one dispute-prevention queue, escalation rules, and pre-chargeback alert data, you resolve refund, delivery, and billing complaints before they reach the issuing bank.
Questions?
we’ve got answers.
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.
You only pay a percentage of the revenue we help you recover. No upfront fees, no subscriptions — just success-based pricing.
Yes. Chargeflow is SOC 2, GDPR, and ISO certified. We use top security standards to keep your data safe.
need more help?
Have a question? We’re here to help. Just hit the chat button to initiate a conversation with support.