CHARGEBACKS

7 chargeback rebuttal letter samples for every dispute

Seven chargeback rebuttal letter samples by dispute reason (fraud, cancelled recurring, not received, credit not processed…) and the evidence each one needs.

Published 11 min read

7 chargeback rebuttal letter samples for every dispute

Have you ever lost a dispute not because the charge was invalid, but because your letter answered the wrong allegation? Proving that a customer used your software doesn’t establish that they hadn’t cancelled before renewal. Showing an approved payment doesn’t, by itself, resolve a claim that the service never arrived.

Chargeback rebuttal letter samples work best when the evidence matches the dispute reason. Fraud calls for an authorization-focused account history. Cancellation requires a timeline. A missing refund requires payment records, not another copy of your terms.

The samples below map those differences to the network reason codes. Confirm the current reason code, eligibility rules and submission requirements with your acquirer, particularly where a processor groups several conditions under a broader label. Mastercard, for example, now files most consumer disputes under 4853 Cardholder Dispute, although the older codes 4841, 4855 and 4860 still appear on dispute notices. Trial conversion isn’t a standalone reason code.

A missing signup record, consent event or cancellation timestamp can leave an otherwise defensible charge difficult to explain. Use these samples as evidence structures, replacing every bracketed field with a record you can attach.

1. Fraud dispute rebuttal using compelling evidence (Visa 10.4 / Mastercard 4837)

An active account isn’t the same thing as an authorized payment. For an unauthorized-transaction allegation, connect the disputed purchase to the relevant customer history rather than merely showing that someone logged in.

Say a SaaS subscriber disputes a renewal but previously paid for the same account without disputing those transactions. Collect the earlier payment references, account identifiers, available device information and relevant activity. Don’t describe matching IP addresses alone as proof of identity, especially for shared offices or corporate networks.

Sample response and supporting records

Disputed transaction: [Payment reference, date, amount and account identifier]. We contest the unauthorized-transaction allegation based on the attached account and transaction records.

The disputed payment is associated with [documented identifiers]. The attached comparison identifies matching records from [eligible prior transactions], including [specific matching fields]. Supporting account activity appears in [attachment reference].

Please assess this submission under the applicable dispute requirements. Each factual statement is linked to the corresponding payment or account record.

Build the comparison before drafting the narrative. Review the Visa Compelling Evidence 3.0 guide alongside your acquirer’s current requirements; don’t assume Visa and Mastercard accept identical evidence.

  • Collect: original consent records, transaction references, device metadata and timestamped account activity.
  • Explain: which fields match and how each record relates to the disputed payment.
  • Exclude: unsupported identity claims and unrelated activity exports.

Have a person check eligibility and attachment accuracy before submission. A persuasive account history still needs to meet the applicable rules.

2. Cancelled recurring transaction rebuttal (Visa 13.2 / Mastercard 4841)

The cancellation timeline matters more than the length of your terms. Start with when the customer requested cancellation, when the system received it, and which charge they’re disputing.

For an annual seat-based subscription, collect the renewal notice, delivery status, cancellation history and the terms presented when the customer subscribed. A database showing no completed cancellation isn’t conclusive if a support email contains an earlier request.

Sample cancellation timeline

Subject: Response to cancelled recurring transaction dispute, [dispute reference].

Merchant position: The disputed renewal occurred at [timestamp and time zone]. Our records show the cancellation request was received at [timestamp and time zone] through [channel]. The subscription’s resulting cancellation status was [status and effective date].

Supporting records: Attached are the billing event, cancellation event, relevant customer correspondence and applicable renewal terms. These records support our position because [specific explanation of the sequence and applicable cancellation window].

Requested outcome: Please review the attached timeline against the cardholder’s allegation.

Practical rule: check support inboxes and cancel flow events before claiming that no cancellation request exists.

Post-renewal usage may add context, but it shouldn’t substitute for answering whether the customer cancelled in time. If your records show a timely request that wasn’t processed, investigate the failure rather than defending the charge with login history.

For prevention, use a subscription chargeback prevention workflow that preserves requests, confirmations and billing timestamps together.

3. Merchandise or services not received rebuttal (Visa 13.1 / Mastercard 4855)

A receipt establishes that you billed the customer. It doesn’t establish delivery. For digital subscriptions, show the connection between payment, provisioned entitlement and the service the customer could access.

Consider an AI software customer who says paid access never activated. Useful records include the account’s entitlement change, successful authenticated requests and completed outputs during the disputed billing period. Check outage and support records before claiming uninterrupted availability.

Sample delivery evidence structure

Transaction and service: [Payment reference] purchased [specific subscription or deliverable] for [billing period].

Delivery record: The paid entitlement was provisioned to [account identifier] at [timestamp]. Attachment [reference] shows the access grant and associated product entitlement.

Evidence of receipt: Attachment [reference] records [successful feature use, completed download, delivered output or other relevant event]. These events belong to the account associated with the disputed purchase.

Relevant exceptions: [Explain any outage, failed activation or support issue and its resolution.] We request review based on the attached delivery and access records.

  • For software: preserve entitlement events and successful use, not just attempted logins.
  • For physical goods: attach shipment details and available proof of delivery tied to the order.
  • For mixed subscriptions: separate digital access from physical add-on delivery.

Don’t submit an unexplained server log. Label the relevant events, identify the account, and distinguish successful delivery from failed requests. If onboarding prevented access, address that failure directly.

4. Not as described or defective rebuttal (Visa 13.3 / Mastercard 4853)

Start with the customer’s specific complaint. A feature-access dispute needs a comparison between what you promised and what you supplied, not a general statement that your product works.

Suppose a subscriber says their plan included a reporting feature that wasn’t available. Retrieve the plan description shown at signup, the purchased tier, the account’s feature configuration and the support conversation. Use the historical offer, not today’s pricing page. A current product screenshot can show present functionality; it can’t establish what the customer was promised at purchase.

Sample promise-to-delivery response

Cardholder concern: [Accurately summarize the alleged missing feature, defect or misleading description.]

Description presented at purchase: The customer purchased [plan]. The archived checkout and plan records identify [relevant feature, limitation or entitlement].

Service supplied: Account configuration and service records show [specific facts addressing the complaint]. Attachment [reference] connects the purchased entitlement to the delivered functionality.

Support and resolution: We received the reported issue through [channel] and responded with [documented troubleshooting or remedy]. The attached correspondence shows [outcome]. We request review of these records against the specific allegation.

The trade-off is straightforward: a clear plan limitation can support your position, but buried language won’t repair an inaccurate sales promise. Don’t treat acceptance of general terms as a complete answer to a concrete defect.

Records to collect: dated checkout captures, versioned plan descriptions, entitlement settings, relevant incident reports and complete support threads. If the feature failed, document the failure and remedy rather than submitting a selective screenshot.

5. Credit not processed rebuttal (Visa 13.6 / Mastercard 4860)

Check the refund ledger before writing anything. The question is whether a credit was owed or promised and, if so, what happened to it.

An internal note marked approved isn’t the same as a completed refund. For a goodwill credit after an outage, collect the customer-facing promise, processor refund record, status, amount, destination and available tracing reference.

Sample refund-status response

Refund status: The disputed purchase is [payment reference]. A refund of [documented amount] was [submitted/completed] on [date], with processor status [exact status] and reference [identifier].

The attached refund record identifies [destination details available from the processor] and connects the credit to the original purchase. The attached customer correspondence describes the refund commitment and subsequent communication.

Please consider the existing credit when reviewing this dispute. We have described the processor’s recorded status without asserting when the customer’s bank displayed the funds.

If no credit was owed, replace that explanation with the applicable policy, checkout disclosure and complete correspondence. Don’t deny a refund commitment just because the standard policy excluded refunds. A support agent’s promise needs to be addressed.

Before choosing whether to refund or fight a chargeback, reconcile the payment and dispute status with your processor. Avoid creating an additional credit without checking whether the dispute has already affected settlement.

6. Duplicate processing rebuttal (Visa 12.6.1 / Mastercard 4834)

Two similar-looking entries require reconciliation, not assumptions. Determine whether they represent separate settled charges, a pending authorization, a failed attempt or a completed reversal.

Say a customer upgrades a subscription and sees a recurring charge beside a prorated adjustment. Your response should identify the purpose of each settled payment and show the underlying plan-change calculation. If you processed a duplicate, document the correction rather than defending both charges.

Sample transaction reconciliation

Disputed entries: [Payment reference and status] and [payment reference and status].

Explanation: These entries represent [distinct billing periods, separate purchases or a documented plan adjustment]. The attached invoices identify the service covered by each settled charge.

Calculation or payment status: [Explain the proration using the actual invoice calculation, or identify the failed, reversed or pending entry using processor records.]

Supporting documents: Attached are the transaction ledger, relevant invoices, plan-change event and any reversal or refund record. We request review of the allegation against these transaction-specific records.

  • Preserve payment states: keep authorization, capture, failure, reversal and refund events distinguishable.
  • Connect invoices: show which service or adjustment belongs to each settled payment.
  • Explain customer-facing entries: keep receipts and billing messages consistent with the ledger.

Reconciliation check: never call an entry declined if your processor records show that it settled.

A retry history can explain confusing payment activity, but it doesn’t excuse an actual duplicate. Check the complete lifecycle of each payment before deciding which version of the sample applies.

7. Free trial conversion dispute rebuttal

Trial conversion isn’t a standalone network reason code. Match the actual dispute allegation, which may concern cancellation, authorization or a misleading description, before choosing your evidence.

Consider a mobile app subscriber who says the trial converted without clear notice. Collect the signup disclosure, affirmative consent event, conversion terms, reminder records, cancellation history and billing event. App activity can establish use, but it doesn’t replace evidence of the terms presented before payment.

Sample trial-conversion response

Dispute allegation: [State the allegation and the category shown in the dispute notice.]

Signup disclosure: At enrollment, the customer was presented with [trial duration, conversion date or calculation, subsequent price, billing frequency and cancellation method]. Attachment [reference] preserves the applicable screen version.

Consent and notice: The account recorded [documented consent event]. The attached messaging records show [reminder content, sending status and delivery information where available].

Cancellation and billing: The cancellation history shows [verified events]. The conversion charge occurred at [timestamp] under [documented terms]. We request review based on these records and the applicable dispute category.

For subscriptions sold through an app store, identify who processed the purchase and which records your business can access. Don’t imply that you control a dispute submission process handled by another party.

Check before contesting: compare the actual signup experience with applicable auto-renewal and consumer-protection requirements. Your business remains responsible for legal compliance. If the disclosure was unclear or the cancellation path failed, address those facts rather than treating a checked box as sufficient evidence.

Which rebuttal letter sample fits your dispute?

Dispute type Reason code (Visa / Mastercard) Core evidence Best for
Fraud dispute using compelling evidence Visa 10.4 / Mastercard 4837 Prior undisputed transactions with matching account, device, IP or usage data Fraud claims involving established customers
Cancelled recurring transaction Visa 13.2 / Mastercard 4841 (now under 4853) Cancellation and billing timeline, accepted terms and post-charge usage Disputes over whether cancellation occurred before renewal
Merchandise or services not received Visa 13.1 / Mastercard 4855 (now under 4853) Access or delivery records tied to the disputed billing period Claims that a subscription or product was not delivered
Not as described or defective Visa 13.3 / Mastercard 4853 Purchase-date plan details, accepted terms, feature availability and support records Claims that a service differed from its description
Credit not processed Visa 13.6 / Mastercard 4860 (now under 4853) Refund transaction details, policy, request history and payment method Claims that a promised refund or credit was not received
Duplicate processing Visa 12.6.1 / Mastercard 4834 Charge dates, amounts, billing periods, retry outcomes and refund records Claims of duplicate charges caused by retries, proration or plan changes
Free trial conversion No single code; depends on the allegation (cancelled recurring, not as described or fraud) Trial terms and consent, conversion details, reminder delivery and usage records Claims of an undisclosed or unauthorized charge after a free trial

From sample to submission: turning these templates into wins

The best rebuttal letter samples help you organize a defensible case. They don’t turn missing records into evidence, establish compliance by themselves or guarantee a reversal.

Start with the allegation, then test whether your records support contesting it. A valid purchase can still involve a missed cancellation, a delivery failure or an outstanding refund promise. Keep those questions separate.

Five checks before you submit a rebuttal
  1. 01 Identify the reason code Confirm the condition and evidence requirements with your acquirer
  2. 02 Assemble the matching records Authorization history, cancellation timestamps, delivery events or ledger records
  3. 03 Reconcile contradictions Compare support emails, billing events and account history
  4. 04 Keep the narrative short The allegation, your position, the attachment behind each fact
  5. 05 Review before the deadline A person checks amounts, timestamps, identifiers and attachments

Before submission, use this action checklist:

  • Identify the reason code: read the dispute notice and confirm the applicable condition and evidence requirements with your acquirer.
  • Assemble the matching records: collect authorization history for fraud, cancellation timestamps for recurring disputes, delivery events for non-receipt and ledger records for payment corrections.
  • Reconcile contradictions: compare support emails, billing events and account history before making categorical claims.
  • Keep the narrative short: state the allegation, your position and the attachment that supports each material fact.
  • Review before the deadline: have a person verify amounts, timestamps, account identifiers, attachment readability and the final submission.

Human review should test the case, not just proofread the letter. Remove unsupported conclusions, resolve inconsistent dates, and confirm that every attachment addresses the actual complaint. For the full list of records by dispute type, see the chargeback evidence checklist for SaaS.

Treat each dispute as a recordkeeping review, too. If you can’t retrieve the checkout version, cancellation event or completed refund, fix that collection gap. Every won rebuttal starts with data collected long before the dispute arrives.

How NoChurn helps

Manual evidence assembly can be the slowest part of preparation, because invoices, usage, emails, cancellation events and support conversations live in different systems. NoChurn builds the evidence file from those records by dispute reason and drafts the reply with AI, using only the evidence in the file. By default nothing is submitted to your payment provider until a person on your team has read the draft and sent it, in one click, before the deadline. Chargeback evidence and replies are included in every plan. See chargebacks.

PROMPT

Read https://www.nochurn.sh/llms.txt,
then follow https://docs.nochurn.sh/quickstart/
to add NoChurn to this app. Use a test key
(nc_test_…) until I say we go live.

Stop leaking revenue.

  • Free until $300 MRR
  • No card needed
  • Live in 10 minutes
  • No commission