Visa 13.3 is best understood as a comparison dispute. The cardholder says the merchandise or service received was not what the merchant described, or that it was defective. The response therefore has to compare promise and performance. A parcel marked “delivered” may prove receipt, but it does not prove the contents matched the listing.
Preserve the offer as it existed when the customer bought. Product pages change, SaaS features evolve, service scopes get edited, and inventory descriptions are updated. A current web page can be the wrong evidence for a purchase made months earlier.
Freeze the purchase-time promise
Save the SKU, model, size, quantity, condition, feature list, service scope, delivery format, and any compatibility limitations that formed the offer. For services, include the signed statement of work or proposal. For software or courses, preserve the plan features and access term that applied at checkout.
Highlight objective terms instead of marketing adjectives. “Includes two 60-minute sessions” is auditable. “Premium coaching experience” is not. A strong response gives the reviewer concrete criteria to compare against what the customer says was missing or defective.
Define the complaint with the same level of precision
Pull the customer’s complaint from support tickets, return notes, photos, or the dispute narrative. Was the wrong item shipped? Did the device fail? Was a promised feature absent? Was the service late, incomplete, or outside scope? Avoid collapsing all of those into “customer was unhappy.”
If the customer’s own photos or messages show the alleged defect, include them. They may weaken the merchant’s case, but they help establish what is actually being disputed. A truthful file is more useful than a selective one that ignores the main complaint.
For a not-as-described allegation, freeze the customer-facing promise as it existed at purchase time. Save the product page version, specifications, images, service scope, delivery estimate, and any written customization. Then compare those promises with what was actually supplied. A merchant response that says only “item delivered” answers the wrong question when the customer agrees it arrived but says the item was materially different. Photos, inspection notes, serial numbers, installation records, and support correspondence can help show whether the complaint is accurate or whether a remedy was offered.
Show what was delivered, not only that something moved
For physical goods, connect packing records, serial numbers, inspection notes, and shipment detail to the disputed order. For services, use deliverables, work logs, acceptance notes, or milestone communications. For digital products, show the entitlement and the features actually available to that account at the relevant time.
If a replacement was sent, explain whether it replaced the alleged defective item and whether the customer received it. If a repair was offered, show the offer and response. The merchant’s handling after the complaint can clarify whether the underlying issue was resolved or left open.
A side-by-side summary makes the logic visible
A concise four-column summary can be effective: cardholder allegation, purchase-time promise, merchant record of delivery, and resolution attempt. Every row should point to an attachment. This is more reviewer-friendly than a ten-page narrative that repeats the same claim in different words.
Be careful with screenshots of updated listings. If the merchant changed a product description after complaints began, disclose the change and use the archived version for the disputed transaction. The response should not create the impression that today’s offer was necessarily the offer the customer saw.
Use 13.3 losses as merchandising and quality signals
A recurring 13.3 pattern is often diagnostic. Wrong-model disputes may point to picking errors. “Not as described” on a subscription may reveal ambiguous feature copy. Defective-item disputes may expose a vendor or packaging problem. Service disputes may show scope language that sales and delivery teams interpret differently.
Tag the concrete mismatch in the internal chargeback log. The goal is not only to recover a transaction but to reduce the number of future customers who can plausibly make the same complaint.
Create a two-column review before deciding to contest: customer allegation on the left, merchant record on the right. If the complaint is about color, size, condition, performance, or missing components, address exactly that attribute. Do not bury a known defect under unrelated evidence such as IP logs or a signed delivery scan. If the merchant's own support notes acknowledge the same defect and promise a refund or replacement, the operational lesson may be to honor that remedy and repair the product-description or quality-control process.
Example: product color variance versus a materially different model
A customer says a product is 'not as described.' One complaint is a slight color difference under different lighting; another is receiving a different model with fewer features. The merchant should translate the complaint into the exact specification being challenged and compare it with purchase-time listing and delivered item records.
A side-by-side table forces discipline: promised model/specification, customer allegation, delivered SKU/serial or service record, and remedy. If the merchant actually shipped the wrong model, no amount of delivery proof fixes the description problem.
Separate four questions: promise, delivered condition, complaint, and remedy
A 13.3 file is easier to evaluate when it is divided into four independent questions. First, what exactly did the merchant promise at the time of purchase? Preserve the purchase-time product page, proposal, scope of work, model or variant, dimensions, material, compatibility, condition description, or service deliverables. Second, what did the merchant actually deliver? Use SKU or serial records, warehouse scans, completion logs, inspection photos, service outputs, or other records appropriate to the product. Delivery evidence proves arrival; it does not prove conformity unless it also identifies what arrived.
Third, translate the customer's complaint into measurable claims. 'Bad quality' may mean damaged packaging, wrong size, a missing feature, poor workmanship, or dissatisfaction with a subjective result. Do not answer a vague label with a vague rebuttal. Quote or summarize the complaint accurately, then create a row for each contested attribute: promised value, delivered value, merchant record, customer record, and unresolved difference. If the complaint is about one accessory in a bundle, keep the dispute focused on that accessory rather than treating the entire order as if every component were challenged.
Fourth, document what happened after the complaint. A return authorization, replacement, repair, partial refund, re-performance, discount, or refusal of a remedy can materially change the remaining amount in dispute. Show what the merchant offered, what the customer accepted, what was actually completed, and what economic value remained. If the merchant acknowledged a defect, do not write a response that says the order matched the description in every respect. An accurate partial concession paired with evidence for the undisputed portion is more credible than an all-or-nothing narrative contradicted by support records.
Before submission, conduct a blind review. Give a second reviewer only the purchase-time promise, the customer's complaint, the delivered-item or service record, and the remedy history. Ask whether they can explain in one paragraph what differed and why the merchant believes the disputed amount is or is not still owed. If they cannot, the case probably needs better evidence rather than more persuasive language. Repeated 13.3 losses should also be grouped by SKU, supplier, listing, service team, or marketing claim because the dispute data may be revealing a product-quality or expectation-setting problem.
VERIFY CURRENT RULES
Primary references
Processor interfaces, reason-code mappings, filing windows, and network rules can change. Check the active dispute notice and current official documentation before submitting.