Visa Reason Code 13.1: How to Win a "Services Not Received" Dispute

If you run a service business and receive a chargeback with Visa reason code 13.1, the customer is claiming they paid for a service that was never provided. This is the most common dispute reason code for service businesses on the Visa network, and it is the one where strong documentation makes the biggest difference between winning and losing.

This guide explains what 13.1 means, what Visa requires from the merchant to overturn it, the mistakes that lose otherwise winnable cases, and a step-by-step walkthrough for building your response.

What Visa Reason Code 13.1 Means

Reason code 13.1 falls under Visa's "Consumer Disputes" category (the 13.x family). The formal name is "Merchandise/Services Not Received." When applied to a service business, the cardholder is telling their bank: "I paid for a service, and the merchant never performed it."

This code does not mean the customer thinks the service was poor or incomplete (that would be 13.3, "Not as Described"). It means the customer is asserting that the service simply did not happen at all. Your job is to prove it did.

Key parameters for 13.1 disputes:

• Response deadline: Typically 30 calendar days from the dispute notification, but always confirm the exact deadline in your processor portal. Some acquirers set shorter windows.
• Burden of proof: On the merchant. You must demonstrate that the service was provided as agreed.
• Pre-arbitration: If the issuer rejects your initial response, you may have the option to escalate to Visa arbitration, which carries additional fees. Winning at the initial response stage is significantly less expensive.

What Evidence Visa Requires

To successfully challenge a 13.1 dispute, Visa expects the merchant to provide compelling evidence that the service was delivered. For service businesses specifically, this means:

Primary evidence (at least one of these is essential):

• Documentation proving the service was performed on the agreed date (completion records, signed acceptance forms, time-stamped photos of completed work).
• Proof that the cardholder or an authorized person received the service (a signature, a login confirming access, or communication acknowledging delivery).
• For digital or remote services, proof that the service was accessed or used by the cardholder (login timestamps, download records, access credentials delivered and used).

Supporting evidence (strengthens your case):

• The original authorization record (signed agreement, booking confirmation, or electronic acceptance).
• Communication records showing the customer discussed or acknowledged the service after it was performed.
• Cancellation policy the customer agreed to, if the dispute involves a no-show or late cancellation.
• Any post-service interaction (a review the customer left, a follow-up email they responded to, a referral they made).

For a complete breakdown of all seven evidence categories and how to score each piece, see What Evidence to Submit for a Chargeback Dispute.

Why Service Businesses Lose 13.1 Disputes

Most merchants who lose a 13.1 dispute had a defensible case. They lost because of how they responded, not because the evidence did not exist. These are the most common failures:

1. No fulfillment documentation. The service was performed, but nothing was recorded at the time. No photos, no completion form, no follow-up email, no GPS record. The business owner knows the work was done, but cannot prove it to a third party. This is the number one reason for 13.1 losses, and the fix is operational, not legal. Build documentation into your service workflow before the next dispute arrives. Our prevention guide covers how.

2. Evidence without timestamps. Photos of completed work are strong evidence, but photos without dates, times, or location metadata are weak. A reviewer cannot verify when undated photos were taken. If your phone camera has location and date metadata enabled, the EXIF data in the photo file is often sufficient. If not, pair the photos with a dated email or message that references them.

3. A disorganized response. Submitting a stack of files with no narrative, no chronology, and no evidence index forces the reviewer to reconstruct your argument. They will not. An unstructured submission reads as a weak case even when the underlying evidence is strong. Use a structured response letter template to avoid this.

4. Responding to the wrong allegation. A 13.1 dispute claims the service was not received. If your response focuses on proving the customer authorized the payment (which is the answer to an unauthorized transaction dispute, not this one), you have addressed a claim nobody made. Match your evidence to the reason code.

5. Missing the deadline. A late response is an automatic loss. Record the deadline the moment you receive the notice and work backward from that date.

Step-by-Step Response Walkthrough for 13.1

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

Step 1: Confirm the Allegation

Read the dispute notice carefully. Verify the reason code is 13.1 and not a different code in the 13.x family. "Services not received" (13.1) requires different evidence than "not as described" (13.3) or "counterfeit merchandise" (13.4). Your entire response strategy follows from the reason code.

Step 2: Locate Your Fulfillment Records

Before you draft a single sentence, gather every document that proves the service was performed. Prioritize:

1. Signed completion or acceptance forms.
2. Time-stamped photos (before and after, if applicable).
3. GPS or check-in records from the service location.
4. Calendar records showing the appointment was kept.
5. Post-service communication (the follow-up email, a text exchange, a review).

If you have at least one strong fulfillment document (a signed form, dated photos, or an email the customer responded to after service), you have a defensible case. If you have none of these, your response relies entirely on indirect evidence, and your win probability drops significantly.

Step 3: Build the Chronology

Write the timeline from booking to dispute, linking each event to an exhibit. For a 13.1 dispute, the critical entries are the service performance date and the proof that the service was completed. Everything else supports those two facts.

Step 4: Write the Summary Paragraph

State the transaction, the allegation, and your factual position in one paragraph. For 13.1, your summary should explicitly state: "The service was performed on [DATE] as documented in Exhibits [X, Y, Z]." Do not bury the fulfillment claim. Lead with it.

Step 5: Assemble the Packet

Organize your submission in this order:

1. Summary paragraph
2. Chronology with exhibit references
3. Evidence index
4. Exhibits (fulfillment evidence first, then authorization, then communication)

Put fulfillment evidence before authorization evidence. The reviewer is evaluating whether the service was received. Show them that answer first.

Step 6: Verify and Submit

Check every date, amount, and exhibit label against the source documents. Confirm that the packet meets your processor's file format and size requirements. Submit before the deadline and save confirmation of the submission.

After the Response

Record the outcome in your dispute tracker. If you win, note which evidence the case rested on. If you lose, identify the gap. Was it missing fulfillment documentation? An undated photo? A disorganized packet? Each loss teaches you what to capture at the point of service going forward.

If you are seeing repeat 13.1 disputes, the problem is almost always upstream. You are performing services without creating a fulfillment record at the time of completion. Fix the documentation workflow and the disputes become defensible by default.