Visa Reason Code 13.3: How to Win a "Not as Described" Dispute

A Visa reason code 13.3 chargeback means the customer is claiming that the service you delivered did not match what was promised or agreed upon. Unlike a 13.1 dispute (where the customer says the service never happened at all), a 13.3 dispute acknowledges that something was delivered but asserts it fell short of the agreement.

This distinction matters because it changes what you need to prove. With 13.1, you prove the service was performed. With 13.3, you prove the service matched the description the customer agreed to. This guide covers what 13.3 means for service businesses, what evidence Visa expects, the mistakes that cost winnable cases, and how to build your response.

What Visa Reason Code 13.3 Means

Reason code 13.3 falls under Visa's "Consumer Disputes" category (the 13.x family). The formal name is "Not as Described or Defective Merchandise/Services." When applied to a service business, the cardholder is telling their bank: "I received the service, but it was materially different from what the merchant described or agreed to provide."

This code covers several specific situations:

• The service delivered differed materially from the description given at the time of sale.
• The service was incomplete relative to the agreed scope.
• The quality of work was substantially below what was represented.
• Conditions or terms were misrepresented before the customer authorized payment.

Key parameters for 13.3 disputes:

• Response deadline: Typically 30 calendar days from the dispute notification. Confirm the exact date in your processor portal.
• Burden of proof: On the merchant. You must demonstrate that the service matched the description and terms the customer agreed to.
• Critical difference from 13.1: In a 13.3 dispute, the customer is not denying that the service occurred. They are denying that the service matched the agreement. Your evidence must focus on what was promised and what was delivered, not simply on whether the service happened.

What Evidence Visa Requires for 13.3

To overturn a 13.3 dispute, you need to show that the service matched what the customer agreed to receive. This requires two categories of evidence working together.

Scope documentation (what was agreed):

• The signed contract, service agreement, or booking confirmation that describes the scope of work.
• Any written estimate, proposal, or quote the customer approved before work began.
• Terms of service or service descriptions the customer acknowledged (a signed form, a checked box, or an email reply confirming the scope).
• Communication records where the customer discussed or confirmed the service details before authorization.

Fulfillment documentation (what was delivered):

• Completion records, progress photos, or work logs that match the agreed scope point by point.
• Before-and-after documentation (photos, measurements, reports) that demonstrate the described work was performed.
• Post-service communication where the customer acknowledged the work, left a review, or discussed results without raising a complaint.
• Any quality standards or certifications your work met.

The strongest 13.3 responses pair every item in the scope document with a corresponding piece of fulfillment evidence. For a detailed breakdown of evidence categories, see What Evidence to Submit for a Chargeback Dispute.

Why Service Businesses Lose 13.3 Disputes

A 13.3 dispute is harder to win than a 13.1 because the question is subjective: did the service match the description? These are the most common reasons service businesses lose defensible cases.

1. No written scope agreement. The service was discussed verbally, but nothing was put in writing before the work started. Without a document describing what was agreed, you have no baseline to compare the delivered work against. The reviewer sees the customer's complaint and no contractual reference that contradicts it. Fix this upstream with a signed scope document for every engagement, even small ones.

2. Vague scope language. The agreement exists but uses language like "professional cleaning" or "complete website redesign" without defining what those terms include. Vague terms favor the customer in a dispute because they allow the customer to claim that their interpretation of "complete" differed from yours. Specific deliverables, quantities, and standards are defensible. General descriptions are not.

3. Proving the wrong thing. Many merchants respond to a 13.3 by proving the service was performed (which answers 13.1, not 13.3). The customer already admits the service happened. Showing photos of completed work does not address the allegation unless those photos demonstrate that the work matches the agreed description. Match your evidence to the specific claim.

4. Ignoring post-service satisfaction signals. If the customer left a positive review, sent a thank-you message, referred another client, or used the service output without complaint for weeks before filing the dispute, those are powerful pieces of evidence. Many merchants do not think to include them. A customer who described the service as "exactly what I needed" in a Google review and then files a "not as described" dispute two months later has a credibility problem, but only if you present that review in your response.

5. No change-order documentation. During the project, the customer requested changes to the original scope. You made the changes, but nobody documented the updated agreement. Now the customer disputes based on the original scope, and you delivered something different. Document every scope change in writing, with the customer's acknowledgment, before performing the changed work.

Step-by-Step Response Walkthrough for 13.3

This walkthrough assumes you have read the general response guide and understand the overall process. These steps are specific to reason code 13.3.

Step 1: Identify the Specific Complaint

Read the dispute notice carefully. What exactly does the customer claim was "not as described"? Some processor portals include the customer's written complaint. If yours does, read it closely. Your response must address the specific allegation, not "not as described" disputes in general.

Step 2: Locate Your Scope Documentation

Pull the contract, proposal, booking confirmation, or service agreement that defines what was promised. This document is the foundation of your defense. If it contains specific deliverables, timelines, or quality standards, you can map your fulfillment evidence against each one.

Step 3: Map Scope to Fulfillment

For each item in the scope agreement, identify the corresponding proof that the item was delivered as described. Create a two-column exhibit: "Agreed" on the left, "Delivered" on the right, with supporting evidence referenced for each row. This is the core of a winning 13.3 response.

Step 4: Collect Satisfaction Signals

Search for any post-service communication that suggests the customer was satisfied: reviews, referrals, thank-you messages, continued use of the service, additional bookings, or a period of silence before the dispute. These signals do not replace scope documentation, but they undermine the customer's claim that the service failed to meet expectations.

Step 5: Write the Summary

Lead with the scope agreement, the delivery evidence, and the satisfaction signals. Your summary should state: "The service was performed according to the terms described in Exhibit A, as documented in Exhibits B through D, and the customer acknowledged satisfaction as shown in Exhibit E." A structured response letter keeps this organized.

Step 6: Assemble and Submit

Order your evidence packet: summary, scope agreement, scope-to-fulfillment mapping, satisfaction signals, then supporting exhibits. Submit through your processor portal before the deadline and save confirmation of the submission.

Preventing 13.3 Disputes

The pattern behind most 13.3 disputes is a gap between the customer's expectations and the merchant's delivery. That gap usually forms before the service begins, not after. Close it with specific scope agreements, written change orders, and a post-service confirmation step where the customer acknowledges the work before the final charge. For more prevention strategies, see How to Prevent Chargebacks Before They Happen.