A dispute can contradict your records without revealing why the customer filed it. Your first job is to understand the claim and assess the evidence. Labeling the customer dishonest too early can distract the team from a valid complaint, an account-security problem or an avoidable misunderstanding.
Use a neutral investigation process that produces two useful outputs: a decision about the current case and an operating improvement when the facts reveal one.
Separate the allegation from the explanation
“Friendly fraud” is commonly used for disputes against apparently legitimate purchases. Treat it as a working category, not proof of intent. Record the processor’s stated reason, the customer’s available explanation and the facts your business can establish in separate fields.
Stripe distinguishes unauthorized payments from other fraud scenarios and notes that an approved payment does not itself prove cardholder authorization. That is an important boundary: an order confirmation or successful authorization is part of the record, not a complete answer to every fraud allegation.
Ask two different evidence questions
First, what does the allegation require you to explain? A non-delivery claim raises different questions from an unauthorized-payment claim. Second, how reliably can your records establish the relevant events? Keep those questions separate so the team does not use a strong record of one event to imply something it cannot show.
For example, a delivery scan may support that a parcel reached a location. It does not, by itself, establish who authorized the card payment. Account activity may show that someone used a service. Assess how the account, activity and disputed payment are linked before drawing a conclusion.
Build a small investigation worksheet
- Claim: Copy the allegation into a short, neutral sentence.
- Known facts: List the relevant events with dates and record references.
- Gaps: Name anything the current records cannot establish.
- Alternative explanation: Check for a refund, cancellation, household purchase or confusing statement name.
- Decision: Record whether to challenge, accept or escalate, and who owns that decision.
- Follow-up: Assign any operating problem to the team able to change it.
The worksheet is an internal decision aid. It should not become a list of speculative accusations in the response. Submit the facts that address the actual case and follow your processor’s current requirements.
Keep customer contact useful
When contact is appropriate, ask a question that can clarify the issue. Refer to the order, amount and product in language the customer will recognize. Explain any relevant support action accurately. Preserve the exchange without threatening the customer or insisting that a merchant policy prevents them from contacting their bank.
If the customer provides new information, update the investigation. A shipping-address change, cancellation request or report of account takeover may alter the assessment. Give support a way to reach the dispute owner before arranging another refund or replacement.
Example: a renewal the customer does not recognize
Imagine a subscriber disputes a renewal. The billing record shows a recurring plan, but support finds that the statement name differs from the product name. The team also discovers an unanswered message asking whether the account was still active.
The response decision depends on the claim and the complete billing history. Separately, the operating team can improve the receipt, statement-name explanation and support handoff. Describing the case as deliberate abuse would miss those actionable findings. This is an illustrative scenario, not a Safe customer result.
Review patterns without turning labels into facts
Use categories such as “records support challenge,” “merchant error confirmed,” “customer confusion indicated” and “insufficient evidence.” Keep the reason for the classification visible. Revisit a sample of decisions with another reviewer to check consistency.
A useful review improves the quality of decisions and the customer experience. It should leave the team knowing what is supported, what remains uncertain and which part of the business needs attention next.