Service Not Received Defense Playbook

Customer Timeframe 120 days from expected service date

Customer Difficulty Low easy to file

Merchant Difficulty High no carrier confirmation equivalent

Industry Win Rate ~43% lower than physical goods

Networks All 4 Visa · MC · Amex · Discover

What This Dispute Means

The cardholder claims they paid for a service that was never performed or provided. Unlike merchandise disputes, there is no tracking number, no carrier confirmation, and no physical delivery to point to. You must prove through documentation that you performed work, provided access, or fulfilled the obligation the customer paid for.

Service disputes span a wide range: a contractor who completed a renovation, a software company whose platform a subscriber accessed, a gym that provided ongoing membership access, a consultant who delivered a report. The evidence strategy differs significantly based on service type — but the standard is consistent across all networks. You must show the service happened and the customer received it.

Unlike fraud disputes, the customer is acknowledging they made the purchase. The dispute is not about whether the transaction was authorized — it is about whether you delivered what they paid for. That distinction shapes how you defend.

Network Coding

All four major networks classify service non-receipt under the same codes as merchandise non-receipt. The networks do not distinguish between physical and service delivery at the reason code level — but the evidence requirements differ substantially in practice.

Network	Code	Official Name
Visa	13.1	Merchandise/Services Not Received
Mastercard	4853	Goods or Services Not Provided
American Express	C08	Goods/Services Not Received or Only Partially Received
Discover	RG	Non-Receipt of Goods, Services, or Cash

Required Evidence

These three requirements form the foundation of every Service Not Received response. Missing any one of them puts the dispute at serious risk regardless of what else you submit.

#1 — Proof you performed or provided the service

This is the core of your case. What constitutes adequate proof depends on how the service was delivered:

Service Type	Evidence to Provide
In-Person (one-time)	Signed work completion form, technician's service report, photos taken at the job site, work order showing the date and scope of work performed.
In-Person (recurring)	Service logs covering each visit within the disputed billing period, with dates and services performed. Signed service verification for each period is strongly preferred.
Appointment-Based	Booking confirmation showing the appointment date, check-in record or attendance log, and service notes from the appointment.
Digital / Subscription	Access logs showing the service was provisioned and available during the billing period. Feature usage data, session records, API call logs, or login timestamps with IP addresses.
Professional Services	Delivered work product — reports, designs, code, campaigns, analysis — with timestamps showing delivery. Email records confirming receipt of deliverables.

#2 — Proof the service period has not yet occurred, if that is your defense

If the customer filed before the service date or before the service was overdue, demonstrate that clearly:

Service Type	Evidence to Provide
Appointment-Based	Booking confirmation showing the scheduled future date, with the current date demonstrating the appointment has not yet occurred.
Subscription / Ongoing	Service agreement or subscription confirmation showing the billing date, service period, and when access begins or next renewal is due.
Project / Milestone	The contract or statement of work showing the agreed delivery timeline and confirming the milestone is not yet overdue.

#3 — Proof the service was provided to the correct customer or location

Issuers need confirmation the service was delivered to the right party:

Service Type	Evidence to Provide
In-Person	The service address provided by the customer at booking, confirmed in your records. If a technician was sent, their report showing the address they attended.
Digital / Subscription	The email address or account ID the service was provisioned to, confirming it matches the cardholder's account details.
Professional Services	The client name and contact information on the service agreement, matching the cardholder's identity on the transaction.

Strongly Recommended Evidence

Required evidence establishes that you performed the service. Strongly recommended evidence establishes that the customer acknowledged it. The difference is critical — issuers can accept your required evidence and still rule for the cardholder if no independent confirmation of receipt exists.

#4 — Proof the customer acknowledged or accepted the service

Service Type	Evidence to Provide
In-Person	Customer signature on a completion or acceptance form. If no form was used, any written or text communication from the customer after the service date that references the work — even a brief "thanks, looks good" — serves as acknowledgment.
Digital / Subscription	Login timestamps with IP addresses showing the customer accessed the platform. Feature usage logs, downloads, or data created within the account. For courses: progress records, video completion data, or certificates.
Professional Services	Email acknowledgment of receiving deliverables, meeting or call records after deliverables were sent, or client feedback on the work product.

#5 — Post-service customer communication

Any message from the customer mentioning or referencing the service after the service date — including follow-up questions, feedback, or support requests about the service itself.
Reviews or ratings submitted by the customer after the service date.
Referrals or recommendations the customer made — any evidence they were satisfied enough to promote the service to others.

#6 — Statement that the customer never raised a concern prior to filing

State clearly and directly that the customer did not contact you before filing the dispute to report that the service was not performed.

Pro Tip

The absence of a complaint is meaningful in service disputes because a genuine non-receipt claim would almost always generate a pre-dispute contact. When a customer files a chargeback without ever reaching out first, it's a signal that reviewers will notice. Make sure your response states this fact explicitly and directly.

Supporting Evidence

These items rarely win a dispute on their own, but they complete the picture and become critical if the dispute escalates to arbitration.

#7 — Service agreement or booking confirmation

The agreed-upon scope of services — what was promised, when, and for what price.
Signed contract or booking confirmation accepted by the customer.
Any amendments or changes to scope agreed to after the original booking.

#8 — Policy documents available to the customer at booking

Cancellation and refund policy.
Service terms and conditions.
Service level agreements or delivery guarantees, if applicable.

Pro Tip

If your booking or checkout flow requires the customer to acknowledge your cancellation or refund policy before confirming, include a screenshot of that step. A policy the customer had to accept is substantially stronger than one posted on a webpage they may not have visited.

Critical Mistakes

Service disputes are among the hardest to win when merchants are underprepared — and among the most winnable when they document their work methodically. The margin between winning and losing usually comes down to documentation habits, not whether the service was actually performed.

Mistake #1: Submitting only an invoice as proof of service

An invoice proves you billed for a service — not that you performed it. Networks treat invoices as transaction records, not delivery confirmation. This is the single most common reason service merchants lose disputes, and it is entirely avoidable.

What to do instead

Always accompany an invoice with proof of completion: a signed work order, a delivered report, access logs, a technician's service record, or equivalent documentation specific to your service type. An invoice alone is the minimum evidence floor, not an adequate defense.

Mistake #2: Not obtaining customer sign-off at service completion

For in-person services, the absence of a customer signature on any completion document leaves your entire defense dependent on your own internal records. If the customer says it never happened and you have no acknowledgment from them, you are unlikely to win regardless of the quality of your internal documentation.

What to do instead

Build a lightweight completion form into every service transaction. Even a text message reply confirming the work is done can serve as acknowledgment. For digital services, configure your platform to capture usage events that demonstrate access. Make collection of acknowledgment a standard part of your workflow, not an exception.

Mistake #3: Assuming access equals delivery for digital services

For subscription and digital services, proving that you made something available is not the same as proving the customer received it. An account that was created but never logged into does not establish receipt. Issuers will rule for the cardholder in this scenario.

What to do instead

Submit login records, session timestamps, or feature usage data. For courses: completion records or progress tracking. For software: feature activity logs, data stored in the account, or actions taken within the platform. The more specific the usage evidence, the more difficult the claim becomes to sustain.

Mistake #4: Ignoring a complaint the customer raised before filing

If the customer emailed a complaint about service performance, submitted a support ticket, or contacted you in any channel before filing the dispute — and you didn't respond — the dispute narrative shifts dramatically. Reviewers will assume the merchant failed to address a legitimate concern, regardless of whether the service was actually performed.

What to do instead

Always attempt resolution before a dispute escalates. If you did attempt resolution, include that correspondence. If the customer rejected your proposed remedy, document that clearly. A documented good-faith resolution attempt significantly strengthens your position and is often enough to result in the cardholder abandoning the dispute.

Mistake #5: Submitting company credentials instead of transaction-specific evidence

Service disputes often lead merchants to over-explain with business history, client testimonials, years of operation, or professional credentials. Reviewers need evidence this specific service was performed for this customer — general proof that you exist and operate well is irrelevant to whether this transaction was fulfilled.

What to do instead

Lead with direct evidence of delivery for the specific transaction and date in question. Keep your response tightly focused on the disputed service. Background information can be included briefly if it directly supports your case, but it should never substitute for transaction-specific evidence.

Winning Response Framework

How you structure your response matters as much as what you submit. Lead with your strongest evidence and state your conclusions plainly — do not make the reviewer infer what your documents prove.

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 explicitly

State the facts of service delivery in plain language. Don't make the reviewer read through documents to determine what happened — tell them directly.

Template Language

The transaction was processed as payment for [service name or description] provided to [customer name] on [date(s) of service]. [The service was performed at the customer's location at [address] / The service was made available digitally through the customer's account at [platform name].] [The service was completed on [date] and acknowledged by the customer / The customer actively accessed the service from [start date] through [end date] as shown in the attached access logs.] To date, the customer did not contact us prior to filing this dispute to raise any concern about whether this service was performed. The following documentation is attached: - [Service completion record / access logs / delivered work product] - Booking confirmation or service agreement - [Customer acknowledgment / post-service communication] - Cancellation and refund policy Please provide our documentation to the cardholder and have them provide an updated response specifically identifying their area of concern.

Step 3 — Sequence your evidence by strength, not chronology

Put your strongest evidence first. Reviewers pay the most attention at the start of a document and attention fades as length increases. If you have a signed completion form, a usage log showing active access, or a post-service email from the customer — those belong on page one.

Priority	Evidence Type
First	Customer acknowledgment — signed completion form, post-service communication, usage logs showing active access.
Second	Proof of service delivery — work report, delivered work product, session records, technician log.
Third	Booking and agreement documentation — appointment confirmation, service agreement, scope of work.
Last	Supporting policies — cancellation and refund policy, service terms, prior service history with the customer.

Step 4 — Label and explain each exhibit

Every piece of documentation should be named, numbered, and given a one-sentence explanation. Context shapes how evidence is perceived.

Template Language

Exhibit A: Service Completion Report Technician's service report completed at the customer's location on [date], documenting all work performed, the time of arrival and departure, and materials used.

Real-World Examples

The situation: $1,800 monthly retainer for SEO services. Cardholder disputed the March charge claiming "I never received any services — nothing was ever done on my account."

Opening statement submitted:

Opening Statement

"This charge represents the March 2024 monthly retainer for SEO services provided under our service agreement dated January 15, 2024. During March 2024, our team published four keyword-optimized articles to the customer's website, completed two technical SEO audits, submitted 14 backlink outreach requests, and delivered a monthly performance report on April 2, 2024. The performance report was emailed to the customer and includes organic traffic data showing an 18% improvement month-over-month. Our account manager communicated with the customer on March 6, March 13, and March 21 via email regarding active campaign work and strategy. The customer has not contacted us to express any dissatisfaction with this or any prior month's work."

Evidence provided (in order submitted):

Page	Evidence
1	April 2 monthly performance report delivered to the customer's email, documenting all March deliverables with timestamps, organic traffic data, and backlink activity.
2	Email thread showing three substantive exchanges between the account manager and customer during March, discussing active campaign decisions.
3	CMS export showing four articles published to the customer's website during March, each dated and attributed to the agency account.
4	Service agreement signed by the customer on January 15, showing the agreed scope of monthly deliverables and payment terms.

Result: Chargeback successfully represented. Claim abandoned.

Why it won:

Monthly performance report documented every action taken during the billing period with objective data
Email communications proved the customer was actively engaged throughout the month
CMS records are timestamped and tied to the customer's own website — not internal-only documentation
Service agreement established the agreed scope, making it clear deliverables were fulfilled as contracted
No pre-dispute complaint on record undermined the claim that nothing was ever done

The situation: $180 biweekly cleaning charge. Cardholder disputed claiming "no one showed up for my last cleaning appointment."

What they submitted:

Response Submitted

"We have been cleaning this customer's home for 8 months and have never had a complaint. Our cleaner completed the March 14th appointment as scheduled. This customer has always been satisfied with our service. We have great reviews online and many loyal customers. Our internal schedule shows the appointment was completed. We find this chargeback unfair."

Result: Dispute ruled in cardholder's favor.

Why it lost:

Mistake	Explanation
Internal schedule record only	An internal calendar entry proves the appointment was planned — not that it happened. The reviewer has no way to verify it independently.
No customer acknowledgment	No completion signature, no text confirmation, no post-service communication from the customer. The dispute came down to the customer's word against the merchant's internal records.
Service history used as a substitute	"Eight months without a complaint" is irrelevant to whether this specific appointment occurred. General history cannot substitute for specific evidence.
Online reviews submitted	Reviews from other customers do not establish that this customer's appointment was completed. They are irrelevant to the dispute.

What they should have submitted:

Cleaner's service report or checklist for the March 14 appointment showing arrival time, work performed, and departure time
Any text or app notification sent to the customer confirming the appointment was completed
Entry log or building access record if the property had electronic access tracking
Before-and-after photos if the cleaner took any at the appointment

Before You Submit

Run through this checklist before finalizing your response.

Service completion documentation

Work order or service completion form included
Service date and time documented
Service address or digital account confirmed and matches booking
Customer sign-off or acknowledgment included if obtained
Technician or provider identification included for in-person services
Session logs or access records included for digital services

Booking and agreement documentation

Service contract or booking confirmation included
Agreed scope of services clearly documented
Scheduled service date or billing period confirmed
Customer's contact information on booking matches cardholder account

Post-service evidence

Any customer communication referencing the service after the service date
Delivered work product (reports, designs, outputs) with timestamps included
Feature usage or login activity for digital services included
Customer reviews or feedback submitted after the service date, if available

Order and payment documentation

Invoice or receipt for the disputed transaction
Prior service history if this is a recurring charge
Cancellation and refund policy
Any customer communication prior to the dispute (including complaints and your response)

Proactive Prevention

The most effective chargeback defense is the evidence you collect before a dispute is ever filed. These steps reduce your exposure and build a documentation trail that makes responses straightforward.

Action	Why It Matters
Require a signed completion form for every in-person service	A customer signature at service completion is the single most reliable protection against non-receipt claims for in-person work. Make it standard practice for every job, regardless of size.
Build usage visibility into digital products	Give customers access to their own session history and usage data. When customers can see their activity, they are far less likely to claim non-receipt — and you have a built-in evidence source if they do.
Send post-service summaries within 24 hours	Email a brief recap of what was done and when after every service. This creates a paper trail the customer has implicitly acknowledged, and gives them a natural opportunity to raise concerns before a dispute is filed.
Collect customer acknowledgment at every touchpoint	Completion emails, text confirmations, in-app acceptance screens — any moment where the customer confirms the service occurred is a moment of evidence. Automate this where possible using your service management tools.
Respond to complaints within 24 hours	60–70% of service disputes follow an unanswered complaint. Resolving issues quickly before they escalate to chargebacks is the most cost-effective dispute prevention strategy available.
Document your work in process, not after the fact	Photos during and after in-person service, timestamps on digital deliverables, client-facing reports delivered at completion — these are easier to create in the moment than to reconstruct later. Make documentation part of every service workflow.

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: February 3, 2026 · Covers: Visa 13.1 / Mastercard 4853 / Amex C08 / Discover RG

Related Guides

Continue building your chargeback defense knowledge: