Payment disputes, chargebacks, and refunds explained
Discuss with AI
Opens an AI with a question about the public article URL. Check its answer and sources.
The page must be published. Access and prefilled text are not guaranteed; copy the prompt if needed. Only the public URL and this prompt are passed along.
A payment dispute is a challenge to a payment. In card payments, a customer can raise it with their card issuer, and the process can lead to a chargeback. A merchant refund is a separate way to return money. Bank-wire fraud follows a different process again.
In this article
Which payment process are you dealing with?
“The customer wants their money back” can describe several different situations. Ask who is handling the request and which payment rail moved the money. That determines where to act and what records matter.
Scroll sideways to see every column.
| Process | Where it starts | Merchant’s first step |
|---|---|---|
| Merchant refund | A customer asks the business, or the business finds an error. | Check the original payment and refund policy, then use the processor’s refund workflow. |
| Card dispute / chargeback | A cardholder challenges a charge with the issuer. | Open the processor’s case, check its stage and deadline, and investigate the claim. |
| Fraudulent bank wire | A transfer goes to a fraudster, sometimes after deceptive payment instructions. | Contact the bank immediately about the transfer and preserve the payment instructions. |
Stripe distinguishes merchant refunds from card chargebacks by who initiates and processes the return of funds. The terms can be used loosely in conversation, so use the case status and payment method to establish what has actually happened.
There can also be a platform-specific claim. PayPal distinguishes a claim investigated within its process from a card chargeback decided by the issuer. If a customer says they opened a PayPal case, identify the actual case type before choosing a workflow. Do not copy a card-response deadline or refund instruction into a different process.
What changes when a card dispute becomes a chargeback?
A cardholder’s complaint can trigger a formal process through the issuer and payment network. The merchant receives the case through its processor and can accept it or respond with evidence where the process permits.
An inquiry may precede a formal chargeback. Stripe documents inquiries and formal disputes as distinct stages, with actions available in the Dashboard. Read the current case rather than assuming that a previous reply settled it.
A chargeback notification is an allegation to investigate. It does not by itself prove criminal fraud, merchant wrongdoing, or customer dishonesty. A duplicate charge, a renewal after cancellation, an unauthorized purchase, and an undelivered service need different explanations.
Why subscription disputes need more than a payment receipt
A receipt shows a payment. A subscription dispute may turn on the agreement and a sequence of later events. Was the renewal disclosed? When did the customer ask to cancel? Did access fail? Had support promised a refund?
For example, a customer may have used a service throughout September and correctly canceled before the October renewal. September usage does not establish that the October charge was valid. Keep activity tied to the relevant payment and service period.
The useful investigation links billing, account changes, support, and service records. Look for mistakes by the business as well as evidence supporting the payment.
Evidenz is being developed for B2C and B2B SaaS teams facing this problem: the payment record is clear, but the relationship behind it spans several systems. Its planned customer history connects the invoice, relevant account, support commitments, and product events before the team drafts a response or reviews a refund complaint.
This approach suits an individual plan renewal or company workspace charge that depends on what happened between the original purchase and the latest payment. A coherent sequence gives support and finance a shared explanation of the customer's complaint, the business's actions, and the facts that should guide the next step.
Bank-wire fraud needs a different response
Here, “wire fraud” means fraud involving a bank-wire transfer, not the broader legal meaning of that term. One example is business email compromise: someone impersonates a supplier and sends altered bank details. The payer sends a transfer to the wrong recipient.
The FBI advises victims of business email compromise to contact their financial institution immediately and report the incident to IC3 in the United States. Outside the US, use the relevant local reporting authority as well. Preserve the instructions, messages, bank details, transfer reference, and times.
A card chargeback evidence packet is not a bank-wire recall request. Evidenz does not offer bank-wire monitoring, transfer recalls, or wire-fraud recovery. Do not delay contacting a bank while investigating a customer timeline. Recovery depends on the transfer and the institutions involved; no outcome is assured.
Common follow-up questions
Does a dispute also cancel the customer's subscription?
Treat the payment case and future billing as separate tasks. Confirm what the customer wants to stop, the affected subscription, and the effective date. Verify the change in the billing system and communicate its result. Do not assume that opening or resolving a bank case has processed a cancellation request. The cancellation guide shows why scope and dates matter.
Which amount should we investigate after a partial refund?
Keep the original charge, completed refund, current disputed amount, and actual balance adjustments separate. Do not infer the remaining amount from a ticket summary or add every displayed figure as a final loss. Reconcile the provider's current records first. The refund-cost guide gives a worked example of the distinction.
Sources and scope
Sources checked
Published by Evidenz. Examples are illustrative, not customer results. Check current requirements and the actual case against the linked sources.