Services not rendered chargebacks: prove the service happened
The client paid, the work got done — and then the chargeback arrives claiming the service was never provided. These disputes are filed in the "services not received / not provided" family: Mastercard reason code 4855 (goods or services not provided) and Visa's 13.x consumer-dispute family for services not received. They hit agencies, consultants, law and accounting firms, and freelancers hardest, because there is no tracking number for work product. What replaces the tracking number is a dated paper trail — and most service businesses lose these disputes not because the trail doesn't exist, but because nobody assembled it.
What the bank is actually deciding
Strip away the legal flavor and the analyst's question is simple: did the service happen, on roughly the dates the agreement promised? The bank is not a court. It will not weigh whether your advice was good, whether the client was difficult, or who breached what — arguments about quality, effort, and fairness read as noise. A dispute that says "services not provided" is answered by one thing: dated proof that the service was performed and delivered to this client. Every exhibit in the packet should point at that single question.
This cuts both ways, and it's worth being honest about it: if the engagement genuinely never started, or the deliverable never went out, the evidence will show that too — and accepting the dispute is the right call. The winnable cases are the ones where the work happened and the records prove it.
The exhibits that carry the case
- Exhibit A — The engagement agreement. The signed contract, engagement letter, statement of work, or accepted proposal: what was promised, the scope, the price, and the client's signature or written acceptance. This defines what "the service" was, so everything after it can be measured against the promise.
- Exhibit B — Dated deliverables. The work product itself, with dates: the report as sent, the designs, the filed documents, the audit, the strategy deck. Use the version the client received, and show the transmission — the email that sent it, the shared-folder timestamp, the portal upload record.
- Exhibit C — Proof of performance along the way. Meeting invites and notes, call logs, time records, drafts exchanged, project-management activity, login or session records for ongoing services. A service performed over weeks leaves a rhythm of dated traces; that rhythm is very hard for a "never happened" claim to survive.
- Exhibit D — Client communications. Emails or messages where the client reviews the work, requests revisions, approves a draft, or discusses results. A client who commented on the deliverable has conceded it exists — analysts notice this immediately.
- Exhibit E — The completion point. The final delivery email, sign-off, invoice marked against the engagement, or the client's last use of the service. This anchors the end of the timeline: hired → performed → delivered → used.
Structure the response like this
- One-page summary first. State plainly what the service was and when it happened, in 3–5 sentences: "Mastercard 4855, 'services not provided.' The client engaged us on Mar 2 for a brand-identity package (Exhibit A). Drafts were delivered Mar 14 and Mar 21; the client requested revisions Mar 22 (Exhibit D); final files were delivered Apr 2 (Exhibit B). The service was performed in full." The analyst should never have to guess what the review, audit, campaign, or engagement actually was — say it in the first lines, with dates.
- Timeline. Engaged → work performed → drafts/reviews → final delivery → dispute filed. Dated, chronological, each row pointing at an exhibit.
- Exhibits, in reading order. Every claim in the summary points at one exhibit; no orphan attachments the analyst has to connect themselves.
| Date | Event | Exhibit |
|---|---|---|
| Mar 2 | Engagement agreement signed; scope and fee set | A |
| Mar 9–21 | Work performed; meetings held; drafts delivered | B, C |
| Mar 22 | Client reviews drafts and requests revisions | D |
| Apr 2 | Final deliverables sent and acknowledged | B, E |
| May 19 | "Services not provided" dispute filed — seven weeks after delivery | — |
Mistakes that lose winnable services cases
| Mistake | Why it loses |
|---|---|
| Arguing the contract like a court filing | Breach arguments, legal citations, and indignation don't answer the analyst's question. The bank decides whether the service happened, not who was right about the relationship. |
| Sending the deliverable with no dates or transmission proof | An undated file could have been made yesterday. The dated email, portal record, or timestamp showing the client received it is what makes it evidence. |
| Burying the summary | If the first page doesn't plainly state what the service was and when it was performed, a busy analyst may never reconstruct it from 40 pages of exhibits. |
| Complaining about the client's motives | "They just don't want to pay" may be true and is still not evidence. The dated record makes that point on its own. |
| A partial-performance case argued as full performance | If part of the scope genuinely wasn't delivered, say so and show the math on what was. Analysts who catch an overstatement discount everything else in the packet. |
A note on partial and ongoing services
Retainers, subscriptions for professional time, and phased engagements often end mid-stream — the client disputes the full amount after using part of the service. Handle these with usage records (sessions held, hours logged, deliverables sent per phase) and clean proration math: what was consumed, what it was worth under the agreement, what — if anything — was already refunded. A packet that concedes the unused portion and proves the used portion is far stronger than one that claims all or nothing.
Other reason codes
- Product not received (Visa 13.1): delivery evidence that wins →
- Duplicate charge: two charges, two separate records →
- Not as described (Visa 13.3): listing, specs, and receipt proof →
- American Express reason codes in plain English →
- The full Stripe chargeback evidence checklist, by reason code →
Have a "services not provided" dispute open right now?
Parry assembles this packet from your uploads — dispute notice, engagement agreement, dated deliverables, client messages — into a case summary, rebuttal draft, timeline, and labeled exhibits. It's an AI draft: you review every fact and submit it yourself. We never submit in your name, never invent evidence, and the outcome is always the bank's call.
$10 for your first month, then $29/mo. Up to 5 evidence packets/month, dispute deadline alerts, and a saved store/evidence profile. Cancel anytime. No success fee.
Parry is not affiliated with Stripe, Visa, or Mastercard. Reason-code descriptions are general information, not legal advice; your processor's dispute notice controls deadlines and requirements. Last updated: November 3, 2026.