Quick answer: when a service chargeback may fit

Use "chargeback" carefully. For a U.S. credit card, the practical route is usually a written billing-error dispute with the card issuer. That route may fit when:

A chargeback is not a general-purpose refund request. The issuer investigates the facts and applies its process and the relevant card-network rules. A change of mind or ordinary dissatisfaction usually belongs first with the merchant's refund policy.

For a qualifying credit-card billing error, the issuer must receive your written dispute within 60 days after the first statement containing the error was sent to you. The Federal Trade Commission's billing-error guidance recommends keeping a copy and sending the letter to the issuer's billing-disputes address, not the address used for payments.

The templates below are free to copy. Use the issuer's online form too if it requests one, but don't let an online form replace written notice when you are relying on federal credit-card billing-error protections.

Identify the payment method first

The procedure changes with the payment rail. A credit-card billing dispute is not the same as a debit-card error or a PayPal claim.

Payment method What to do
Credit card Ask about the Fair Credit Billing Act billing-error process for a qualifying service problem. The 60-day written-notice period is the key federal benchmark.
Debit card or prepaid card The credit-card process does not automatically apply. Contact the bank or card issuer promptly and ask which error or unauthorized-transaction procedure covers the payment.
PayPal, another payment app, or a marketplace Check the platform's dispute deadline and rules. If a credit card funded the payment, you can also ask the card issuer about its process. Do not pursue two recoveries for the same charge.
ACH transfer, wire transfer, or cash There is no ordinary credit-card chargeback. Contact the bank or recipient promptly and ask about a recall, reversal, or other available procedure.

Service problems that may support a dispute

A strong claim connects one charge to one specific failure. These examples show the kind of evidence and limitation that matter.

Situation Useful evidence Important limit
A SaaS plan or digital service was never activated Receipt, promised activation date, account screenshots, and support messages A merchant's claim that an account existed may not show that the promised service was usable
Freelance or consulting work was not delivered Contract, milestones, due dates, messages, and missing deliverables Identify the work that was not completed instead of making a broad quality complaint
The service was not delivered as described or agreed Advertisement, order page, contract, and a side-by-side explanation of the difference Ordinary disappointment or a change of mind may not establish a billing error
A recurring charge posted after cancellation Cancellation confirmation, timestamp, terms, and the post-cancellation statement A charge before a valid cancellation or during a disclosed notice period may be treated differently
A promised refund was not credited Refund confirmation, refund date, and card statement Dispute only the amount that remains unpaid
You do not recognize the charge Statement, merchant descriptor, account records, and information about other authorized household users Check whether the descriptor differs from the brand name before calling an authorized purchase fraud
The same service was billed twice Statement lines, invoices, and receipts Identify both transactions and ask for correction of the duplicate

A no-refund policy does not decide whether a charge was unauthorized or whether the service was delivered. It can matter when the dispute concerns a renewal or a voluntary refund, especially if the cancellation and refund terms were clearly disclosed. Someone who simply changed their mind should usually start with those merchant terms.

Credit-card dispute letter for a service

Use the statement date, not just the transaction date. State the exact amount and describe what happened without including a reason that does not apply. The FTC's credit-card dispute instructions and sample letter provide additional format guidance.

[Date]

[Card issuer name]
Billing Inquiries or Dispute Department
[Address shown for billing disputes]

Re: Dispute of service charge on account ending in [last four digits]

Dear Sir or Madam:

I am writing to dispute the following credit-card charge as a billing error.

Merchant: [Business name and statement descriptor]
Transaction date: [Date]
Amount: [$ amount]
Statement date showing the charge: [Date]
Account ending in: [Last four digits]

I paid for [describe the SaaS plan, subscription, freelance work, consulting, hosting, or other service]. I dispute the charge because [choose and explain the accurate reason]:

- The service was not provided.
- The service was not delivered as agreed.
- I canceled the recurring service on [date], but the charge posted on [date].
- The merchant confirmed a refund of [$ amount] on [date], but the credit has not appeared.
- The charge is unauthorized.
- The amount was duplicated or billed incorrectly.

Facts and timeline:
[Briefly state what you purchased, what was promised, what happened, and the dates involved.]

I contacted the merchant on [dates] by [email, chat, phone, or support ticket]. The result was [no response, refund denied, partial refund, or other result]. Copies of the relevant records are enclosed.

Please investigate this dispute under your billing-error process. If the investigation confirms an error, please credit the disputed amount and related charges as required and send me the result in writing.

Enclosures:
- Copy of the statement with the charge marked
- Receipt or invoice
- Contract, service terms, or cancellation confirmation
- Relevant emails, messages, screenshots, or support tickets
- [Other evidence]

Sincerely,

[Your full name]
[Address]
[Phone number]
[Email address]

Send copies, not originals. Redact your full card number, passwords, and unrelated personal information. Keep proof of when and where the issuer received the dispute.

Short fact paragraphs to add

SaaS access problem:

I paid for the [plan name] on [date]. The merchant charged my card, but my account was never activated, or access was removed on [date] before the paid period ended. Support contacted me on [dates], but the problem was not corrected.

Subscription canceled but charged:

I canceled the subscription through [method] on [date] and received [a confirmation or cancellation number]. A recurring charge of [$ amount] nevertheless posted on [date]. I am disputing that post-cancellation charge.

Freelance or consulting work not delivered:

The agreement required [specific deliverable] by [date]. I paid [$ amount], but that deliverable was not provided. My messages on [dates] requested completion or a refund, and the merchant [did not respond or refused the request].

Refund or cancellation request to the merchant

Contacting the merchant is not always a legal prerequisite to a credit-card dispute, but it can solve the problem faster and creates a useful record. Send the request promptly; do not wait until the issuer's deadline is close.

Subject: Refund or cancellation request for [service] charged on [date]

Hello [merchant or support team]:

I am requesting [cancellation and a refund, a partial refund, or correction of a duplicate charge] for this transaction:

Account or order number: [Number]
Service: [Name]
Charge date: [Date]
Amount: [$ amount]
Statement descriptor: [Descriptor]

The problem is:
[State the specific service failure, cancellation date, missing deliverable, duplicate charge, or promised refund.]

Please [cancel future recurring charges and refund $ amount, provide the missing service by an agreed date, or confirm why the charge is valid]. Please reply in writing and include any refund reference number.

I have attached [receipt, contract, cancellation confirmation, screenshots, or messages].

Thank you,

[Name]
[Email]

If the merchant refunds the charge after you contact the issuer, notify the issuer. Do not seek or keep two recoveries for the same transaction.

Credit-card deadlines and the investigation

For a qualifying U.S. credit-card billing error, the FTC says these federal time frames generally apply:

Step Benchmark
Written dispute The issuer must receive it within 60 days after the first statement containing the error was sent
Acknowledgment The issuer generally must acknowledge the dispute in writing within 30 days, unless it resolves the issue sooner
Investigation and decision The issuer generally must resolve it within two complete billing cycles, and no later than 90 days after receiving the dispute

These deadlines are not universal for debit cards, prepaid cards, payment apps, or every type of card transaction. Card networks and issuers may also have additional procedures or different time windows. Use the deadline in the issuer's notice, but do not assume that a longer network window extends the federal 60-day billing-error period.

While a qualifying dispute is being investigated, you generally do not have to pay the disputed amount or related finance charges. Continue paying the rest of the account on time. Follow the issuer's instructions so an unrelated balance does not become delinquent.

What chargeback reason codes mean

Reason codes are internal labels used by card issuers, networks, processors, and merchants. Consumers usually do not choose them. Explain the facts in plain language and let the issuer classify the claim.

These are examples that may appear in network or processor notices:

Problem Visa example Mastercard example
Service not received 13.1 4855, goods or services not provided
Recurring charge after cancellation 13.2 4841, canceled recurring transaction
Service not as described or defective 13.3 4853, cardholder dispute
Merchant credit or refund not processed 13.6 The issuer may use a different credit-related category
Cardholder does not recognize the charge The applicable fraud or unrecognized-transaction category depends on the facts 4863, cardholder does not recognize

Code names, subcategories, and evidence requirements can change. The code on your issuer's or processor's notice controls the particular case. Do not copy a code from an old template just because it sounds persuasive. A clear timeline supported by records is more useful.

Evidence checklist for SaaS, subscriptions, and freelance work

Put the records in date order and label each item. Include only material connected to the disputed charge.

An IP address, login record, or generic "service delivered" statement rarely answers the whole question by itself. A login may show access, for example, but it does not necessarily prove that a promised consulting deliverable or specific feature was supplied.

Common service disputes

SaaS and subscriptions

Start by checking the statement descriptor, sign-up email, renewal notice, account history, and cancellation record. A brand may bill under a different legal or payment-processing name, so an unfamiliar entry is not automatically unauthorized.

Save the cancellation confirmation and identify the first charge after cancellation. If you merely stopped using the service, nonuse alone usually does not establish that the charge was an error. Review the terms accepted at sign-up and ask the merchant how the renewal was authorized.

Freelance and consulting services

Compare the contract with what was actually delivered. Point to the missed milestone, incomplete work, or specific promised result instead of describing the entire engagement as fraudulent.

Partial performance matters. Explain which part is disputed and how you calculated the amount. A card dispute does not replace a contract claim, so keep the agreement and communications in case the issuer declines the dispute and another remedy becomes necessary.

Web hosting and other digital services

Save the service-level terms, outage dates, support responses, and account-access records. A short outage or slower-than-expected performance may be a service complaint rather than a billing error. The strength of a dispute depends on what the provider promised and whether the failure fits the issuer's category.

No-refund policies and recurring billing

A no-refund policy is a merchant term, not a ruling by the card issuer. It may show what the customer agreed to, but it does not prove delivery or defeat a claim of unauthorized use. It also should not conceal recurring billing or make cancellation impractical.

A clearer policy tells customers:

State laws and sector-specific rules may impose additional requirements. A no-refund clause is not a substitute for meeting those requirements or addressing a genuine service failure.

If you are the service provider responding to a chargeback

The processor's notice supplies the response deadline and the specific claim. The consumer's 60-day credit-card deadline is not a universal merchant response deadline.

A useful rebuttal answers the stated reason directly. Repeating a no-refund policy without showing delivery, access, acceptance, or the applicable cancellation terms is unlikely to address the factual dispute.

[Business name]
[Address]
[Date]

To: [Acquirer or payment processor]
Re: Chargeback case [case number]
Transaction date: [Date]
Amount: [$ amount]
Card ending in: [Last four digits]
Reason shown on notice: [Exact label or code]

We dispute this chargeback based on the following transaction facts.

The customer purchased [service] on [date]. The agreed service period, deliverable, or access terms were [brief description]. We provided [specific service] on [dates]. The relevant evidence is attached and labeled [A, B, C].

The customer [accessed the service, accepted a deliverable, requested support, canceled on a specified date, or did not contact us] as shown by [specific records]. Our refund and cancellation terms were displayed [where and when], and the customer accepted them on [date], if applicable.

The customer's claim is inaccurate because [address each factual point directly]. We are not relying only on a general no-refund statement.

We request reversal of the chargeback.

Attachments:
- Transaction and invoice records
- Terms accepted at checkout
- Delivery, access, or milestone records
- Customer communications
- Cancellation and refund history

Sincerely,

[Name and title]
[Business name]
[Contact information]

Submit the response through the processor's required channel and meet its deadline. Remove unnecessary customer data from attachments. A service business should make its billing descriptor, renewal timing, cancellation method, and support contact easy to identify.

If the issuer denies the dispute

Read the decision and compare its stated reason with your evidence. A short, focused response is usually more useful than sending the entire history again.

  1. Ask the issuer's dispute department whether reconsideration or an appeal is available.
  2. Request the explanation and supporting information needed to understand the decision.
  3. Address the precise reason for denial and attach only the strongest documents.
  4. Keep the case number, dates, letters, uploads, and merchant communications.
  5. If the issuer did not follow its stated process, ask for a supervisor and use the complaint route for the regulator that supervises the issuer. For a large or contract-heavy dispute, consider qualified legal or consumer-help advice.

Before sending either template, write down the statement date, the 60-day receipt deadline, and the exact amount in dispute. Send the letter to the billing-disputes address, keep proof of delivery, and continue paying the undisputed part of the account on time.