How to respond to a chargeback, with a SaaS rebuttal letter example

What should you record when a dispute arrives?

Open the case in your payment processor. Record the disputed charge, amount, currency, reason, current stage, and exact response deadline. Assign someone to investigate and someone to check that the response was actually submitted. A draft in an internal tool is not a filed response.

Stripe’s response documentation explains how to review and act on a dispute in the Dashboard. Follow the deadline on the case instead of relying on a general number of days from an article. Card networks, case types, and payment methods can differ.

Check whether you are looking at an inquiry or a formal chargeback. Keep those stages distinct in your notes. An earlier customer conversation, inquiry response, or withdrawal request should not be treated as proof that the current case is closed.

Reconstruct what happened before deciding to contest

Read the customer’s explanation before collecting favorable records. Locate the relevant invoice and subscription, then compare billing history with cancellation requests, support messages, and service availability. Check for an already completed refund or a duplicate charge.

Use two columns in your investigation notes: facts supporting the charge and facts supporting the complaint. Record gaps separately. A missing cancellation event could mean no request was made, but it could also mean the request arrived through a channel you have not searched.

When the records show a billing mistake or support the customer’s claim, do not invent a defense. Follow the processor’s procedure for accepting or resolving the case. If the dispute is already open, check the processor’s instructions before sending a separate refund so you do not create conflicting money movements.

What is chargeback representment?

Chargeback representment is the merchant's challenge to a chargeback through its acquiring provider. It combines an explanation with the records needed for the actual claim. A rebuttal letter supplies the narrative; it does not replace the provider's evidence fields, attachments, approval, or submission.

Use the reason-code reference to choose the question your response must answer. Keep an inquiry, initial chargeback, and any supported pre-arbitration review separate.

A chargeback rebuttal letter example for SaaS

A response should identify one payment and address the actual allegation. General statements about the reliability of your business do not establish what happened in this purchase.

Fictional teaching example for “service not received.” This separate case is DEMO-DELIVERY-002. All events and references below are invented. It is a drafting example, not a submitted response or evidence for a real payment.

Subject: DEMO-DELIVERY-002 — response to the service-not-received claim

We are responding to the disputed EUR 49 payment DEMO-PAY-002, collected on October 8, 2026 for access from October 8 to November 7. The reviewed complaint says the purchased reporting service was not received.

P1 identifies this payment, subscription, account, and service period. P2 records the reporting entitlement being enabled for that account on October 8 at 09:02 UTC. P3 records a report being created and downloaded through the account on October 9.

P4 is the support exchange from October 10: the account holder asks how to change the columns in the downloaded report. Together, these records support delivery of the reporting function during the disputed period.

The activity record establishes an account action, not an independent identification of the cardholder. This explanation addresses non-delivery. It does not establish that a different cancellation, authorization, or service-quality complaint would be unfounded.

The references below identify the authorized excerpts to include in the provider's accepted submission format.

In a real response, include relevant original excerpts and the account-to-payment mapping, not just these reference labels. Read the whole conversation and check cancellation and remedy promises before approving the narrative. Use only facts supported by the actual case.

If the records instead contain an earlier cancellation promise, the finding changes. The sample evidence packet shows that contrasting case in full. Do not combine it with this fictional non-delivery letter.

Stripe advises keeping evidence factual, professional, and concise. Use precise verbs: “the account downloaded a report” says what the record shows. “The customer clearly intended to pay” adds an inference the event cannot establish.

Review, submit, and retain the confirmation

1. Check that the charge, customer, amount, currency, and billed period agree across the packet.
2. Match the evidence to the dispute category and current processor instructions.
3. Read attachments at normal size and remove unrelated information.
4. Confirm the case owner approves the response and any automated action.
5. Submit through the processor or authorized service and retain the confirmation and submitted version.

The evidence needed varies by dispute category. A generic response letter is a drafting aid, not a complete response for every reason code. Confirm whether your processor allows changes after submission before treating a first draft as final.

Provider status names need interpretation too. Adyen separates receiving defense documents from the issuer's review, and its Chargeback Reversed stage can return funds while that review continues. Keep submission confirmation, current case stage, and final financial outcome as separate fields. A returned balance alone should not close the investigation.

Use the outcome to improve the customer workflow

Track submitted, accepted, won, lost, and still-open cases separately. Record why you accepted a valid complaint and why you challenged another. Do not count a pending case as recovered revenue.

Look for operational causes: a confusing statement descriptor, a broken cancellation step, a missed refund promise, or a delay between support and billing. Fixing those failures can be more useful than writing a longer response next time. Keep outcome measures separate from the quality of the original decision; a bank’s ruling does not make every allegation about intent true.

Give the response a clear factual starting point

Evidenz is designed for B2C and B2B SaaS teams doing the work between receiving a dispute and writing the response: reconstructing the customer history that explains the charge. A support agent may know about a cancellation promise, finance may hold the payment record, and the product history may explain whether access worked. Those records need one coherent sequence.

Evidenz’s planned timeline is aimed at precisely this handoff between departments. It gives the investigation a shared basis for a reviewed response draft, whether the case concerns cancellation of an individual plan or an unapplied change to a company’s seats. Account links, service events, and support commitments explain the payment. The argument follows the finding about the actual complaint.

Common follow-up questions

Does our inquiry response also cover a later chargeback?

No. Stripe states that an inquiry which escalates to a chargeback needs another response. Reopen the current case, confirm its reason and deadline, and review whether the earlier records still answer it. Keep both stages linked, but do not mark the formal dispute submitted because the inquiry was answered.

How should we prioritize several cases approaching their deadlines?

Use the actual deadlines, remaining investigation, approvals, and action needed for each case. Do not sort only by disputed amount or an unverified risk label. Assign an owner and backup, identify missing records early, and verify the outcome of each action. The deadline guide explains the difference between the provider's deadline and an internal review target.