Accept or contest a chargeback: make the decision from the records

Find out whether the complaint is valid

A large disputed amount is a reason to investigate carefully. It is not a reason to defend a billing mistake. Equally, a small charge is not automatically unworthy of review if it exposes a repeated operational problem.

Read the customer's explanation and identify the exact payment. Check the invoice, agreement, service period, cancellation messages, delivery records, and prior refunds. Write down evidence against the charge as well as evidence supporting it. If you only gather favorable events, the decision will look stronger than the underlying case.

Stripe provides accept and counter actions for disputes, with a different treatment for inquiries. Confirm the current case stage before choosing an action. This guide's decision record is a suggested internal practice, not a substitute for the options and deadline shown by your provider.

Separate an adverse fact from a missing record

An adverse fact directly weakens the charge: a valid cancellation confirmation, a duplicate captured payment, or a support admission that the purchased service failed. A missing record means something is not established. Those situations should not receive the same explanation.

For example, “we have not located the acceptance record” is different from “the customer did not agree.” Search the relevant system and preserve the uncertainty. Do not fill the gap with an unrelated login or today's version of the terms.

A duplicate payment should not become a writing exercise

Illustrative case. Two €240 captured charges refer to the same monthly workspace invoice. The customer says they paid twice. Engineering confirms a retry created the second payment. The first payment is valid; the duplicate is the one disputed.

A receipt, signed agreement, and extensive workspace activity might support the original purchase. They do not justify collecting the same invoice twice. Record the duplication and use the provider's appropriate resolution process for the disputed payment. Investigate the retry failure separately so the next month does not repeat it.

Now change one fact: the two payments belong to different workspaces and distinct invoices. That can support a different conclusion, but only after the account links, purchasing authority, and billed periods are checked. Two invoice numbers are not sufficient if one workspace was created accidentally or support had already promised to close it.

The useful habit is to state what would change the decision. It keeps the reviewer from defending whichever explanation they happened to see first.

Adyen also identifies insufficient supporting documents as a reason to consider accepting a dispute. Use that provider guidance to test the actual evidence, not to replace the investigation with an amount threshold. A high-value payment still needs a defensible explanation; a low-value complaint can still reveal an error worth fixing.

Calculate the cost of the next action

After reviewing validity and obligations, list costs that differ between accepting and contesting. These may include a countering fee, a specialist's fee, remaining staff review time, and additional work needed to repair poor records. Use your contract and actual effort, not a generic internet estimate.

Stripe distinguishes fees for receiving and countering disputes, with regional and contractual qualifications. Check your own terms. A fee already incurred is different from a fee triggered by the next action; neither changes whether the underlying complaint is justified.

Avoid inventing a percentage chance of winning because the form requests a number. A risk score, account activity count, or vendor-wide result is not a calibrated probability for this case. If historical outcomes inform the decision, identify the comparable cases, unresolved outcomes, and limits. When that evidence is absent, say that recovery is uncertain.

Leave a decision another person can audit

Use a short note containing the claim, payment, material facts, contrary records, unresolved gaps, chosen action, approval, and confirmation. A label such as “low value” or “friendly fraud” cannot replace that explanation.

Stripe's evidence guidance favors relevant, factual material. The same discipline helps the internal decision: describe the record before interpreting it. “A scheduled job ran” is narrower than “the customer used and accepted the service.”

Once decided, follow the response workflow and verify that the provider received the action. Keep the decision quality separate from the eventual issuer outcome. A loss can follow a reasonable, documented response; a win does not prove every allegation about customer intent.

Bring the contrary records into the decision

Evidenz is being built for SaaS teams serving individual subscribers (B2C) or company workspaces (B2B), connecting the payment with its account, support, and product history before the team chooses a response. A personal renewal may conflict with a cancellation promise; a company invoice may conflict with an agreed seat reduction. A failed access attempt or refund discussion can change either review. The intended workflow should make those contradictions part of the decision rather than leave them in separate systems. The case owner still needs to explain the conclusion, document remaining gaps, and confirm the appropriate action through the provider.