Chargeback for Services Not Rendered: What to Do
A chargeback for services not rendered happens when a customer disputes a charge because a paid-for service was never delivered or completed. Card networks route it to a specific reason code, and the customer usually has 120 days from the missed delivery date to file. Merchants get as little as 20 days to respond.
I've built dispute responses for my own stores.
A service claim is harder than a shipping claim, because the proof has to come from records you and the customer both saw.
Read this once and you'll know which code applies, which deadline is yours, and what proof answers the claim.
Key takeaways
- 01Card networks file non-delivery service claims under four different reason codes.
- 02Customers get 120 days to file, merchants often 20 to 45 days.
- 03Mastercard 4853 is a catch-all code covering several cardholder complaints.
- 04Prove the service happened, using records the customer also saw.
- 05Contact the merchant first, or the issuer may reject the dispute.
Watching disputes land after the fact? Catch them as alerts instead.
What counts as a chargeback for services not rendered?
A services-not-rendered chargeback is filed when a customer disputes a charge for a service that never happened. That covers a service never delivered, cancelled without fulfillment, or only partly completed.
The customer paid, and the bank pulls the money back.
Each network sends the claim to a specific dispute reason code, and that code decides what you have to prove:
| Network | Code | Shorthand name | What it covers |
|---|---|---|---|
| Visa | 13.1 | Merchandise/Service Not Received | Goods or services the cardholder paid for and never got |
| Mastercard | 4853 | Cardholder Dispute | A catch-all covering non-delivery among other complaints |
| American Express | C08 | Goods/Services Not Received | Nothing received, or only part of what was promised |
| Discover | RG | Non-Receipt of Goods, Services, or Cash | Services never delivered by the agreed date |
Mastercard is the one that trips merchants up. Goods or Services Not Provided was once reason code 4855, now bundled into 4853 with several other cardholder complaints.
Read the sub-claim on a 4853 notice to see which complaint you're answering, because the code number alone covers several. You can confirm it with the reason code lookup tool in seconds.
Each code here covers non-delivery and non-completion. A customer who got the service and disliked it files elsewhere. So does one who says it fell short of your description. Those quality claims run through Visa 13.3 and Amex C31 or C32, and through the same Mastercard and Discover catch-alls under a different sub-claim.
Answer a quality complaint with delivery evidence and you lose a case you could have won.
Summary: Four networks, four codes, one shared question: did the service actually happen?
Time limits for filing this dispute
A customer generally has 120 days to file, and merchants get 20 to 45 days to respond across Visa, Mastercard, and Amex. The clock starts at the transaction date or the promised service date, whichever is later. On Visa 13.1, the right expires 540 days after the original transaction.
The later-of rule exists because a service is only undelivered once its due date passes. A contract or a booked appointment still has time to run before then.
So the network counts from the date you promised delivery. After 540 days, a Visa cardholder loses the right however far out the service was booked.
Here is how the windows compare:
| Who files | Window | Starts from |
|---|---|---|
| Customer, Visa 13.1 | 120 days (540-day cap) | Transaction date or promised delivery date, whichever is later |
| Customer, Mastercard, Amex, Discover | 120 days | Transaction date or agreed delivery date |
| Merchant, Visa 13.1 | 30 days | Dispute processing date |
| Merchant, Mastercard 4853 | 45 days | Dispute processing date |
| Merchant, Amex C08 | 20 days | Dispute processing date |
| Credit cardholder, FCBA notice | 60 days | The charge appearing on the statement |
One deadline comes from federal law rather than the network rules, and merchants mix the two up constantly.
The Fair Credit Billing Act (FCBA) lets a credit cardholder send a written billing-error notice. That notice is due within 60 days of the charge showing up on the statement.
That right is separate and narrower. Miss the 60 days and you keep the 120-day network dispute. You give up the formal billing-error process the FCBA sets out.
Contact the merchant before you file
Card issuers generally expect the cardholder to try the merchant first. Many ask for proof of that attempt before they open a dispute. An email thread, a support ticket number, or a dated call log is usually enough.
The bank steps in last, after you and the merchant have failed to settle it.
Skipping that step is one of the reasons a dispute gets denied. Most issuers want proof you tried the merchant before they open the case.
A refund also reaches you in days, while a dispute takes weeks and sometimes months. Ask in writing and give them a date to reply by, five to seven business days out. Tell them you'll take it to your bank otherwise.
Merchants benefit from the same call. If the customer reaches you first, you decide whether to refund. If they reach their bank first, you pay a chargeback fee and lose the choice.
Most issuers apply this as a practice norm. Some open the dispute anyway when the merchant has gone quiet or shut down.
If you tried and got nowhere, say so and keep the record.
How merchants can respond
Winning a services-not-rendered dispute means proving you delivered the service, using the same three evidence types every time. A thick packet loses to a thin one that matches the code.
Each evidence type answers a different part of what the code asks:
- The service agreement or order confirmation: Establishes what you promised and by when.
- Delivery or completion proof: Signed work orders, login and session logs, appointment records, dated file handoffs.
- The communication log: Shows the customer knew the status and never raised a non-delivery claim with you.
The middle one wins or loses the case.
Export each record with its date attached, because the issuer checks those dates against the disputed service window. A screenshot of a summary screen proves nothing about when the work happened.
Merchants read 4853, assume non-delivery, and send delivery proof when the cardholder filed a quality complaint. Read the sub-claim field on the notice from your acquirer before you gather anything.
Packet mechanics differ by code family, and our guide to merchant dispute responses sets them out.
Stopping the dispute before it's filed costs less than winning it after. A dispute alert tells you early enough to refund the customer instead. That keeps the case off your chargeback ratio.
We offer alerts from every provider, which is the part of this you control.
What if the service was only partially delivered?
Represent the portion you delivered, with dated records for each period served. A full chargeback against a partly rendered service can be contested. You argue for the months you did serve and recover that share.
Recurring services produce most of these claims.
Cancelled services are the close cousin. When a customer cancels inside your stated window and you bill anyway, the dispute turns on the policy you published. Submit that policy as it read on the purchase date, alongside the timestamped cancellation record.
Say a customer prepays for twelve months and you deliver four before the relationship ends. Usage logs, session records, or dated deliverables from those four months answer the claim for that portion. Submit one record per period served.
Summary: Prove the service happened, period by period, and the partial months stop being a total loss.
If you're the customer: how to file
Yes, you can dispute a charge for a service that was never delivered. Call your card issuer, give them the specific dates, and tell them what you already tried with the merchant.
Have four things in front of you when you call:
- The transaction date and the exact amount on your statement.
- The date the service was supposed to happen.
- What you paid for, in one sentence.
- Your record of contacting the merchant, with dates.
The dates matter more than the story.
Your issuer needs the promised service date to start the 120-day clock correctly. A vague "sometime this spring" gets claims rejected that a written delivery date would have carried.
Your issuer files the dispute under the network's non-delivery code, and usually gives you a provisional credit while the case runs.
The merchant then gets its response window, and if its evidence answers the code, the credit reverses.
That reversal catches customers off guard. A provisional credit looks like a win, but the bank can take the money back once the merchant answers.
So leave it untouched until the case closes.
Describe what happened accurately and let the issuer pick the code. A customer who accepted the service and disliked it is making a different claim, and the non-delivery route gets that denied.
Our dispute vs. chargeback explainer traces the case from your first call through the merchant's response.
Credit card vs. debit card dispute rights
Credit cardholders can dispute an undelivered service as a billing error under Regulation Z, while debit cardholders fall under Regulation E, which covers unauthorized transfers. Regulation Z counts a service the consumer never accepted, or one that arrived outside what was agreed, as a billing error the issuer has to investigate.
Regulation E covers whether a transfer was authorized and processed correctly. Whether the service you bought ever showed up sits outside it.
That split sets different deadlines and liability caps, which our comparison of credit and debit chargebacks lays out side by side.
The difference here is a legal one.
Both card types still generate a chargeback under the same four codes above, and the networks treat them the same way. What changes is what federal law guarantees on top, and on a non-delivery claim, credit carries more.
You notice it when a bank refuses your claim. A credit cardholder can point to a billing-error right the issuer has to investigate, while a debit cardholder has only the network process to fall back on.
So for a large prepaid service, a booked contract, or anything scheduled months out, pay by credit card. You pay the same either way, and credit gives you a federal right on top.
FAQ
What happens if I miss the 120-day filing window?
You lose the network dispute right for that transaction, and the issuer will decline to file it. Asking the merchant directly for a refund is still open to you.
Can a merchant reverse a false non-delivery chargeback?
Yes, through a second presentment, which is a separate action from your first evidence submission. You resubmit the case with proof of delivery, and a win reopens the decision.
Does this chargeback count against my ratio if I win?
Yes. A filed chargeback counts toward your chargeback ratio whatever the outcome, which is why prevention beats representment.
What if the customer already used part of the service?
Partial use undercuts a total non-delivery claim, because the customer is arguing nothing arrived while your records show they used it. Submit the timestamped access data alongside the agreement.
