Visa 13.3 wins on the return-attempt requirement. Under Visa rules, cardholders must attempt to return and give merchant a chance to remedy before disputing. Most cardholders skip this step. Documenting that they didn't attempt return, combined with clear return policy and QC records, wins 55–75% of cases. Merchants who don't invoke the return-attempt requirement lose 30–40% more cases.
What Visa 13.3 covers
Visa 13.3 is "Not as Described or Defective Merchandise." Cardholder received the item but claims:
- Materially different from listing (wrong color, size, specifications)
- Damaged or defective on arrival
- Not as described in some material way
Distinct from 13.1 (not received). With 13.3, receipt is not in dispute — condition or match to listing is.
The return-attempt requirement
Under Visa Core Rules, cardholders must attempt to return the item and give merchant a chance to remedy before disputing 13.3. Single most important rule for defense.
Most cardholders skip this. They receive item, decide they don't like it, dispute directly with their bank. Legally they can't — Visa requires the return attempt first.
Merchants who cite this rule in the rebuttal narrative win significantly more:
"Cardholder disputed under 13.3 without attempting return or contacting merchant support. Visa Core Rules require cardholders to attempt resolution before disputing under 13.3. Merchant's return policy (attached) was clearly displayed at checkout, and merchant received no return request or support ticket (system logs attached)."
That paragraph — properly documented — wins cases that otherwise lose.
The evidence stack
For 13.3 representment:
- Product listing at time of purchase — screenshot of the exact listing customer saw. No post-hoc edits.
- QC or fulfillment records — pre-shipment quality check log.
- Return policy display — screenshot of the return policy visible at checkout.
- System logs — records showing no return request submitted.
- Delivery proof — establishes customer received item and had it in possession.
- Communication history — any support tickets or chat about the order.
The listing-at-purchase problem
Trap: cardholder claims item didn't match the listing, but you've updated the listing since. Current listing ≠ what cardholder saw. Issuers don't accept post-hoc listings.
Solutions:
- Wayback Machine — archive.org may have snapshotted your listing around the purchase date.
- Internal versioning — Shopify has version history; WooCommerce with revisions plugin.
- CDN cache — Cloudflare/Fastly may retain cached copies.
- Email archive — if you emailed the customer a product confirmation with listing details embedded, dated evidence.
Merchants who produce point-of-purchase listing win 13.3 substantially more often. If you're not versioning listings, start.
Frequently asked questions
What is Visa 13.3?
"Not as Described or Defective Merchandise." Cardholder received the item but claims it was defective or didn't match the listing.
Does the cardholder have to attempt return before disputing?
Yes — Visa Core Rules require it. Merchants who invoke this requirement in representment win substantially more often.
How do I prove the listing at time of purchase?
Version your listings with timestamps. Alternatives: Wayback Machine snapshots, CDN cache logs, or email confirmations with listing details embedded.
Post reflects public documentation, industry surveys, and Aurai's own book of disputes as of the publish date. Visa, Mastercard, American Express, Discover, Stripe, PayPal, and Shopify are trademarks of their respective owners; Aurai is independent and not endorsed by any of them. Network rules change — always verify current official rules before acting on any specific tactic.