Service Incorrect or Misrepresented Defense Playbook

Customer Timeframe 120 days from transaction date

Customer Difficulty Low quality claims are hard to disprove

Merchant Difficulty Very High subjective quality and scope disputes

Industry Win Rate ~35% among the hardest to defend

Networks All 4 Visa · MC · Amex · Discover

What This Dispute Means

The cardholder claims the service they received materially differed from what was advertised, described, or contracted. The service was performed — the customer is not claiming nothing happened — but they are asserting that what happened did not match what they agreed to pay for.

This is one of the hardest dispute categories to defend. Unlike product disputes where a description can be compared to a physical item, service quality and scope are often subjective. The customer can characterize the service as inadequate, incomplete, or misrepresented in ways that are genuinely difficult to disprove with documentation alone.

Common triggers: service delivered at a lower scope than contracted, quality significantly below what was advertised, material terms not disclosed at booking, substitute providers used without disclosure, or scope reduced without agreement after the sale.

Your best defense in this category is always a written service agreement that defines scope precisely, combined with documentation that the agreed scope was delivered.

Network Coding

All four networks cover service misrepresentation under their "not as described" codes, using the same codes that apply to physical product disputes.

Network	Code	Official Name
Visa	13.3	Not as Described or Defective Merchandise/Services
Mastercard	4853	Cardholder Dispute — Goods or Services Not as Described
American Express	C31	Goods/Services Not as Described
Discover	RM	Non-Matching Services

Required Evidence

These three requirements are the foundation of every Service Incorrect response. The first is the most critical — and the one most merchants fail to have in a form that can be submitted as evidence.

#1 — Proof that your service description matched what was delivered

This is the central question the reviewer must answer. Evidence requirements vary by service type:

Service Type	Evidence to Provide
Professional / Project Services	The signed service agreement or statement of work defining the agreed scope, and delivered work product — reports, designs, code, campaigns — with timestamps confirming delivery within the contracted timeline.
In-Person Services	The service booking confirmation showing what was agreed to, and your service completion report or technician notes documenting exactly what was performed.
Digital / Subscription	Your advertised feature set or service description as it appeared at the time of purchase, and access or usage logs confirming those features were available and active during the billing period.
Event / Venue / Experience	The booking confirmation or event description as shown to the customer at the time of purchase, attendance records, and any post-event communications acknowledging the customer's participation.

#2 — The specific terms or scope that was agreed to

Document Type	What to Include
Signed contract or agreement	The specific scope, deliverables, timeline, and payment terms the customer agreed to. Any amendments or change orders agreed to after the original signing.
Booking confirmation	The service details as confirmed at booking — what was included, what was not, and any terms acknowledged at the time.
Advertised service description	Your service listing or advertisement as it appeared at the time of purchase, archived or screenshotted at the sale date.

#3 — Your refund or resolution policy, communicated at booking

Refund or dispute resolution policy as it was available to the customer at the time of booking.
Any policy requiring concerns to be raised within a specific timeframe.
If your checkout or booking flow required the customer to acknowledge the policy, include a screenshot of that acknowledgment step.

Strongly Recommended Evidence

Required evidence establishes what was agreed to and that the service was performed. Strongly recommended evidence closes the gap between performance and acceptance — it demonstrates the customer received the service, engaged with it, or at minimum had an opportunity to raise concerns before filing a dispute.

#4 — Direct rebuttal of the customer's stated complaint

The single most important step is reading the dispute reason carefully and addressing it point by point:

Complaint Type	Rebuttal Evidence to Provide
Scope dispute (less delivered than promised)	Your service agreement defining scope, and documentation of every deliverable completed — timestamped reports, emails attaching work product, CMS logs, time tracking records.
Quality dispute (service performed poorly)	Pre-service and post-service documentation, completion reports, any third-party review or external validation of the quality of work. If a quality standard was specified in the agreement, show it was met.
Misrepresentation dispute (advertised capabilities not delivered)	Your advertised service description at the time of purchase, and documentation that the described capabilities or features were available and functional during the service period.
Substitute provider dispute (different person or company performed the work)	Disclosure documentation showing substitution was permitted under your terms, or communications where the customer acknowledged and agreed to the substitute provider.

#5 — Customer acknowledgment or engagement after service delivery

Any communication from the customer after the service date that references the work — even requesting a follow-up, asking a question, or providing feedback.
Reviews or ratings submitted by the customer after the service date.
Communications showing the customer used or engaged with deliverables — replied to a report, logged into a platform, attended a follow-up call.

#6 — Statement that the customer did not raise concerns before filing

Confirm clearly that the customer did not contact you about service quality or scope prior to filing the dispute. If they did raise concerns, include the full communication thread and your response.

Pro Tip

Service Incorrect disputes that follow unresolved complaints are very difficult to win. If the customer complained before filing and you have no record of a response or resolution attempt, your first step should be to reach out and offer a remedy. A resolved complaint is far less likely to proceed. If you did respond and the customer rejected your offer, that documented good faith significantly strengthens your dispute position.

Supporting Evidence

These items round out your case and become important if the dispute escalates to arbitration.

#7 — Prior service history with this customer

If this is a recurring engagement, prior deliverables, communications, and satisfaction records establish a baseline of performance the customer accepted without dispute.
Positive reviews or feedback from this customer on prior engagements are relevant if the complaint suggests a systemic problem with your service that would have been apparent earlier.

#8 — Third-party or independent corroboration

For professional services: peer review, external audits, or client sign-off from a stakeholder other than the cardholder if applicable.
For in-person services: photographic evidence, materials receipts, or subcontractor records if additional parties were involved in delivering the service.
For digital services: independent uptime or availability records showing the platform was operational and accessible.

Critical Mistakes

Service Incorrect disputes have the lowest merchant win rates of any non-fraud dispute type. Most losses are not caused by a service that was genuinely wrong — they are caused by merchants who cannot document that the service matched the agreement.

Mistake #1: Operating without a written service agreement

Without a written agreement defining scope, deliverables, timeline, and quality standards — the customer's characterization of what was promised carries more weight than yours. Verbal agreements and informal understandings are invisible to a dispute reviewer.

What to do instead

Every service engagement should begin with a written document the customer accepts: a contract, a statement of work, a booking confirmation with terms, or at minimum an emailed scope summary with the customer's reply confirming it. For recurring services, this agreement should cover what each billing period includes and what constitutes satisfactory delivery.

Mistake #2: Defining scope vaguely in your advertising

Service descriptions that rely on aspirational language — "world-class," "comprehensive," "full-service," "premium" — invite disputes because they set an undefined standard that the customer gets to characterize after the fact. If your service description doesn't specify what you will do, it's impossible to prove you did it.

What to do instead

Use specific, measurable language in both your advertising and your agreements. "Monthly retainer includes four deliverables, two review calls, and a performance report" is defensible. "Comprehensive digital marketing support" is not. Specificity protects you at every stage — from setting customer expectations to defending a dispute.

Mistake #3: Not documenting delivery of work product

For professional services, the most common losing scenario is a merchant who performed the work but cannot prove they delivered it. Completing a task internally is not the same as delivering the output to the client. If there is no record that deliverables were sent, received, or acknowledged, they effectively don't exist from the reviewer's perspective.

What to do instead

Email deliverables directly to the client at completion, preserving a timestamped record of both the content and the delivery. Use project management tools that log when tasks were marked complete and when clients reviewed or commented on work. Keep a delivery log for every engagement — what was sent, when, and to whom.

Mistake #4: Substituting providers or changing scope without written agreement

If a customer hired a specific person, team, or company for their service and a different provider was used without their knowledge — or if the scope was reduced after the sale without consent — the dispute is very difficult to defend. Networks treat undisclosed substitution as a form of misrepresentation.

What to do instead

Always get written consent before changing a provider or reducing scope. Even a brief email exchange confirming the customer's acknowledgment is sufficient. If your terms allow for substitution, make sure that is clearly disclosed at booking and referenced in your service agreement.

Mistake #5: Responding to a quality claim with volume metrics

"We submitted 50 items" or "we worked 40 hours" does not answer a quality dispute. Volume is not the same as value, and reviewers reviewing a quality claim are looking for evidence that what was produced met the agreed standard — not just that something was produced.

What to do instead

Address quality claims by pointing to the agreed standard in your contract, then showing documentation that the standard was met. If your agreement didn't define quality standards, your time records and volume metrics will carry less weight. Going forward, define acceptance criteria in every service agreement.

Winning Response Framework

Service Incorrect responses must be tightly organized around the gap between what the customer claims and what your documentation shows. Every component of your response should either prove the agreed scope was delivered, or directly contradict a specific point in the customer's complaint.

Step 1 — Identify the chargeback clearly

Template Language

Case Number [1234567891234] (provided by your processor/acquirer) We are responding to the chargeback against the [MM/DD/YYYY] transaction made by [BOBBY CUSTOMER] in the amount of [$$$.$$]. Please find our response and supporting documentation attached.

Step 2 — Summarize your case and directly address the complaint

Identify the specific mismatch the customer is claiming, then show — point by point — why your documentation contradicts it.

Template Language

The transaction was processed as payment for [service name or description] under our service agreement dated [date], accepted by the customer at booking. The agreed scope of service included: [brief list of key deliverables or service components from the contract]. [Address the customer's specific complaint directly, e.g.: The dispute states that [specific claim]. Our service agreement defines [scope or standard]. Enclosed is documentation confirming [specific rebuttal evidence].] All contracted deliverables were completed and delivered to the customer by [date]. Enclosed is [description of delivery documentation]. To date, the customer did not raise any concern about service scope or quality prior to filing this dispute. We encourage the cardholder to contact us at [contact info] to discuss any remaining concerns. The following documentation is attached: - Signed service agreement or booking confirmation - [Deliverable documentation / work product / completion records] - [Customer acknowledgment or post-service communication] - Refund and cancellation policy Please provide our documentation to the cardholder and request a specific response identifying any remaining area of concern.

Step 3 — Sequence your evidence by strength, not chronology

Priority	Evidence Type
First	Customer acknowledgment — post-service communication, acceptance of deliverables, usage logs, or any engagement with the work product after delivery.
Second	Deliverable documentation — timestamped work product, completion reports, technician records, or access logs demonstrating the agreed scope was fulfilled.
Third	Service agreement or scope definition — the written record of what was agreed to, showing that what was delivered matches it.
Last	Refund policy, prior engagement history, and advertised service description from the time of purchase.

Step 4 — Label and explain each exhibit

Every document should be named, numbered, and described in one sentence. Do not make the reviewer determine what a document proves — tell them.

Template Language

Exhibit C: Monthly Deliverables Log — March 2024 Internal project management export showing all tasks marked complete during the disputed billing period, with completion dates, assignees, and links to delivered files.

Real-World Examples

The situation: $4,500 website design project. Cardholder disputed claiming "the website I received looks nothing like the mockups I approved — they did whatever they wanted and ignored my feedback."

Opening statement submitted:

Opening Statement

"This transaction represents payment for a custom website design project under our service agreement signed by the customer on January 8, 2024. Our agreement included three design revisions after each of two major milestone deliveries, and final delivery upon customer approval of the completed design. Enclosed is documentation of the full project timeline: the initial mockups delivered January 22, the customer's written feedback received January 29, revised mockups delivered February 5, the customer's written approval of the revised design received February 8, and the final website delivered February 20. The customer replied to the final delivery email on February 20 confirming receipt and stating 'looks great, thanks for your work.' The dispute was filed 34 days after this confirmed acceptance."

Evidence provided (in order submitted):

Page	Evidence
1	February 8 email from the customer explicitly approving the revised design: "This looks great, please proceed with development." Establishes the customer approved the final design direction before production began.
2	February 20 customer reply to final delivery email confirming receipt: "Looks great, thanks for your work." Establishes acceptance of the completed project.
3	Full project communication log — 14 emails spanning January 8 through February 20, showing every round of feedback, revision, and approval, with dates.
4	Signed service agreement dated January 8, defining the revision process, deliverable schedule, and payment terms.

Result: Chargeback successfully represented. Claim abandoned.

Why it won:

Written customer approval of the specific design direction before production started directly contradicted the claim that feedback was ignored
Written acceptance of the final delivery 34 days before the dispute was filed was the single most compelling piece of evidence
Full project communication log showed an ongoing collaborative process — not a one-sided delivery the customer had no input into
Service agreement established that the revision process was defined and completed as agreed

The situation: $600 for a 10-session personal training package. Cardholder disputed after completing 4 sessions claiming "the trainer they gave me was not the certified professional they advertised — it was an intern."

What they submitted:

Response Submitted

"We are a professional training studio with certified trainers on staff. All of our trainers are qualified. The customer completed 4 sessions without any complaint. We cannot give a refund for sessions already used. Our policy is no refunds on completed sessions. The customer attended the sessions and received the service they paid for."

Result: Dispute ruled in cardholder's favor.

Why it lost:

Mistake	Explanation
Did not address the specific complaint	The customer's claim was about provider identity — not quality. The response never addressed who conducted the sessions or whether a substitution occurred.
No documentation of trainer credentials or identity	No session records showing which trainer conducted each appointment. Without this, the customer's account of an uncertified substitute goes unrebutted.
No disclosure of substitution policy	If the trainer who was advertised was not the one who conducted the sessions, there is no evidence the customer was informed or agreed to this. Undisclosed substitution is treated as misrepresentation.
No-refund policy submitted as primary defense	A no-refund policy does not override network rules for misrepresentation. Submitting it as the main argument without rebutting the substantive claim was counterproductive.

What they should have submitted:

Session records showing which trainer conducted each of the four sessions, with their credentials and certification status
Their booking or terms disclosure confirming which trainer (or trainer tier) was included in the package
If a substitute was used: documentation of the customer's consent, or terms explicitly permitting trainer assignment by the studio
An offer to resolve — either completing the remaining sessions with the advertised trainer or providing a partial credit for the unused sessions

Before You Submit

Run through this checklist before finalizing your response.

Service agreement and scope documentation

Signed service agreement or booking confirmation included
Specific scope, deliverables, or services agreed to are clearly documented
Quality standards or acceptance criteria defined in the agreement
Any amendments or scope changes agreed to after the original booking
Provider identity or qualification requirements disclosed to the customer

Service delivery documentation

Timestamped work product or deliverable documentation included
Completion records, service reports, or access logs for the disputed period
Provider identity or credentials for in-person services
All agreed deliverables confirmed as completed and documented

Rebuttal evidence

The customer's specific complaint has been read carefully and addressed point by point
Each claimed discrepancy is mapped to a piece of contradicting documentation
Customer acknowledgment or post-service engagement included if available
Any pre-dispute communication from the customer and your response are included

Policy and resolution documentation

Refund and cancellation policy included
Any resolution offered to the customer prior to or during the dispute
Prior service history with the customer, if relevant

Proactive Prevention

Service Incorrect disputes are the hardest to win after the fact and the easiest to prevent before the fact. The gap between performing a service and proving you performed it as agreed is closed by documentation habits, not after-the-fact reconstruction.

Action	Why It Matters
Write specific service agreements for every engagement	A precise scope definition — deliverables, timeline, quality standards, and acceptance criteria — is the foundation of every winning dispute response. Vague agreements protect no one.
Get written approval at every major milestone	For project-based services, a written sign-off at each stage closes disputes before they start. A customer who approved the design, the draft, and the final delivery cannot credibly claim it was wrong.
Log every deliverable with a timestamp	Email deliverables directly and keep the sent records. Use project management software that logs when tasks were completed and when clients interacted with them. Delivery you cannot prove is delivery that didn't happen in a dispute.
Disclose provider assignments explicitly at booking	If your service may be delivered by any qualified provider on your team, say so at booking and include it in your agreement. Undisclosed substitution is one of the most common triggers for misrepresentation disputes.
Create a post-service check-in process	A brief follow-up after every engagement — "are you satisfied with the work?" — surfaces complaints before they become disputes and creates a record of satisfaction when there are none.
Respond to quality complaints within 24 hours	Service Incorrect disputes almost always follow an unresolved complaint. Fast, good-faith responses to service concerns stop disputes before they start and demonstrate the professionalism your service description promised.

About This Guide

This playbook is updated at least twice annually to reflect changes in network rules and issuer practices. Document Version: 2026.1 · Last Updated: March 3, 2026 · Covers: Visa 13.3 / Mastercard 4853 / Amex C31 / Discover RM

Related Guides

Continue building your chargeback defense knowledge: