Visa condition 13.5 concerns misrepresentation, so the merchant file has to compare the promise made at purchase with the actual transaction outcome. This is broader than simply showing that something was delivered. The strongest evidence is the purchase-time offer, the terms or disclosures that applied, the order details, what the merchant provided, and the customer's specific complaint.
Start by writing the alleged misrepresentation in plain language. If the complaint cannot be stated precisely, the response will usually become a collection of unrelated policy pages. The live processor notice and current Visa guidance should control the case-specific requirements.
Preserve the purchase-time promise
Archive the product or service page, pricing, included features, exclusions, trial or renewal disclosure, shipping or performance promise, and any other representation relevant to the complaint. Use the version that applied when the customer bought, not a page updated after the dispute.
If the offer changed frequently, retain structured order metadata or versioned page archives going forward. A merchant cannot credibly prove what was represented months earlier using only today's marketing copy.
Translate the complaint into testable statements
Break the allegation into specific claims such as 'feature X was promised but unavailable,' 'the product was marketed as new but arrived used,' or 'the fee was not disclosed before checkout.' Then identify one record that proves or disproves each statement.
This prevents the merchant from answering a different complaint. Delivery evidence is relevant to non-receipt, for example, but does not resolve a claim that the delivered service materially differed from the offer.
Show the actual fulfillment or service outcome
Use itemized fulfillment records, service scope, work logs, account configuration, usage records, or other transaction-specific evidence to show what the merchant actually provided. For services, completion alone may not answer a claim about scope; connect the delivered work to the agreed deliverables.
Where the merchant made substitutions or changes, include the customer approval or explanation if retained. Unexplained deviations from the original offer should be treated as adverse facts, not hidden behind the purchase policy.
Include the resolution path
Preserve customer complaints, troubleshooting, replacement offers, credits, partial refunds, cancellations, and final resolution. A merchant may have cured the issue before the chargeback, or the records may show that the complaint remained unresolved.
If the business promised a remedy but failed to complete it, that fact can outweigh a polished rebuttal. Reconcile the remedy status before deciding whether the case is worth contesting.
Use a claim-versus-record table
For complex cases, create rows for each customer allegation and columns for purchase-time representation, delivered outcome, supporting record, and resolution. This format forces the merchant to confront contradictions and keeps the submission focused on the exact misrepresentation claim.
Do not cite broad testimonials, brand reputation, or statements about what the business 'normally' provides. Network disputes are transaction-specific, and the packet should be built from this customer's offer and outcome.
Feed 13.5 cases back into merchandising
Group losses by missing disclosure, ambiguous offer copy, unavailable feature, sales-agent promise, fulfillment deviation, or unresolved support issue. Repeated 13.5 disputes often reveal a marketing-to-operations gap rather than a pure dispute-team problem.
Change the offer or checkout only after the root cause is clear. More legalistic wording is not always the answer; a clearer price, scope, renewal, or limitation at the decision point can be more useful to customers and easier to document later.
Example: marketing promised 'unlimited' but product had a hidden cap
A service page says 'unlimited exports,' while the actual plan throttles or caps usage after a threshold that was not disclosed at checkout. A Visa 13.5 misrepresentation case should not be answered with evidence that the customer logged in and used the service. The complaint is about the promise.
The merchant should preserve the purchase-time offer, any disclosed limitation, actual plan behavior, customer complaint, and remedy. If the cap was genuinely hidden, the dispute is a merchandising/product problem rather than an evidence-packaging problem.
Translate marketing language into measurable transaction promises
Misrepresentation cases often begin with broad marketing claims that were never translated into operational commitments. Preserve the purchase-time page, ad, sales message, proposal, or signup flow and identify the specific statement the customer says was misleading. Words such as unlimited, guaranteed, free, instant, lifetime, or no-risk can carry practical expectations that need to be compared with limits, exclusions, or conditions shown at the time of purchase.
Build a claim table with four columns: customer-facing statement, qualification or disclosure, actual product/service behavior, and customer complaint. This exposes hidden contradictions. If an ad says 'unlimited' while the terms impose a hard monthly cap that is not prominent, the merchant should not rely on the cap as though it were obvious. If the customer ignored a clear, adjacent limitation, preserve the evidence that it was disclosed. The point is to reconstruct the purchase representation, not defend the current website.
Show what actually happened after purchase. Usage, delivery, service outputs, support interactions, and remedies can clarify whether the complaint is about an unmet promise or dissatisfaction with an accurately described product. If the merchant corrected a misleading statement, offered a refund, or changed the service after the complaint, include that timeline. Do not use post-complaint edits to imply the earlier offer was identical.
Use 13.5 as a marketing-quality metric. Group disputes by landing page, campaign, salesperson, affiliate, product tier, and claim. Review whether one message generates disproportionate complaints or refunds. Legal and policy review may also be appropriate for high-risk claims, but from a dispute-operations perspective the control is simple: every material sales promise should map to a product behavior the business can demonstrate and support.
Review affiliate and reseller claims separately from the merchant's own copy
Misrepresentation can originate outside the merchant's main site. Preserve affiliate landing pages, reseller descriptions, sales scripts, and campaign creatives when those channels materially influence the purchase. If an affiliate promised a feature the product does not provide, the merchant should not defend only the official product page and ignore the representation that actually brought the customer to checkout.
Tag 13.5 cases by acquisition source and claim owner. Repeated disputes from one partner can justify creative review, updated partner rules, or termination. The evidence process should therefore include marketing provenance, not only product fulfillment, when the customer's allegation is about what they were told before buying.
Preserve disclaimers in the same visual context as the marketing claim
If the merchant relies on a qualification to explain a strong marketing statement, preserve how that qualification was actually displayed: proximity, size, placement, and the page or step where the customer saw it. A disclaimer hidden in separate terms may not explain what a prominent headline communicated. The dispute team should avoid making legal conclusions and instead document the purchase-time presentation accurately. Internally, repeated 13.5 complaints should trigger a review of whether material limits are visible where the claim is made rather than technically present somewhere on the site.
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.