A payment notification arrives on a Tuesday morning: a customer has disputed a charge with their card issuer. The amount has been withdrawn from your balance, there is a reason code you have never seen, and a deadline is counting down.
Most small companies handle their first dispute by improvising. A short routine, written down before it is needed, makes the first day calm and the response complete.
What a dispute is
When a customer disputes a card payment, they ask their bank to reverse it. The bank (or your payment provider on its behalf) notifies you, usually takes the funds back for the time of the review, and gives you a window to respond with evidence. If you do not respond in time, the customer usually wins by default. Providers such as Stripe describe this flow and its deadlines in their dispute documentation.
The reasons vary: the customer does not recognise the charge, says the goods or service never arrived, says it was not as described, claims they cancelled, or the card was used without their knowledge. The reason stated in the notice decides which evidence is useful.
The first day
Do these in order, and keep the notes in one place.
- Read the notice completely. Write down the amount, the order or invoice it relates to, the stated reason and the response deadline. Put the deadline in a shared calendar, not only in an inbox.
- Tell the owner. One person owns the response. In a small company this is often whoever manages finance or the payment account. A named backup covers holidays.
- Find the order. Locate the order, invoice, contract or subscription behind the payment. If you cannot match the charge to a customer, that is a finding in itself: check for a vague statement descriptor or a payment made by someone else in the customer's company.
- Pause anything automatic. Hold repeat billing, reminders and renewals for that customer until the case is understood, so you do not add a second dispute.
- Decide: contest or accept. Not every dispute is worth contesting. If the customer is right, or the evidence is thin and the amount small, accepting the dispute is a legitimate and faster choice. Write down the reason.
Evidence worth gathering
Match the evidence to the reason in the notice. Keep it short and relevant; a clear folder of five documents beats fifty unsorted ones.
- The agreement: the order confirmation, quote, contract or the terms the customer accepted, with the date.
- Delivery or use: for physical goods, shipping and delivery confirmation; for services and software, access logs, usage records, delivered files, a signed acceptance or a meeting record.
- Communication: emails, support tickets or chat messages showing the customer received what was promised, or never raised a problem before the dispute.
- Your policy: the cancellation, refund and billing terms, and proof that the customer could see them before paying.
- Identity of the payer: customer name, billing details and, where you have them, the matching account or login.
Write a cover note of one page: what was ordered, what was delivered, when, and why the charge is valid. Refer to each attachment by name. Reviewers read many cases, and a plain, factual note helps.
Who talks to the customer
Contact the customer once, early, and calmly. Many disputes are not fraud. The charge appears under a name they do not recognise, a subscription renewed without a reminder, or a family member made the purchase. A short message often solves it:
We received a notice that the payment of X on date Y was disputed with your bank. In case it is a misunderstanding, here is what the payment was for: [order]. If you would prefer a refund, tell us and we will arrange it right away.
If the customer agrees to withdraw the dispute, ask them to inform their bank, and confirm the status with your payment provider. Do not refund the money separately while the dispute is still open without checking with the provider, because the customer could receive the amount twice. Our note on returns, refunds and credit notes covers how to keep those cases consistent.
The person answering the bank should not argue with the customer in public or in the dispute text. Keep the tone neutral and factual.
Closing the case
After the decision from the bank arrives:
- record the outcome, the amount, the reason and the date in your finance notes;
- if the case was lost, check whether the credit note or ledger entry needs to be corrected;
- ask what caused it: an unclear descriptor, a missing reminder before renewal, a weak confirmation email or slow support;
- fix the one cause that would prevent the most repeats.
If the dispute is really about the invoice rather than the bank, the route is different; see an invoice the customer disputes.
How to make the next one easier
- Use a payment descriptor customers recognise, ideally your trading name.
- Send a clear receipt and, for subscriptions, a reminder before renewal.
- Make it easy to reach you and to ask for a refund; an easy refund is cheaper than a dispute.
- Store order, delivery and communication records so one person can find them in minutes.
- Keep the policy pages visible at checkout, with the date the customer accepted them.
A simple start
- Name an owner for disputes and a backup.
- Write a one-page checklist from the first-day steps above and keep it with your payment account notes.
- Add a calendar reminder rule for every dispute deadline.
- Create a folder template: agreement, delivery or use, communication, policy, cover note.
- Review the last twelve months of refunds and complaints to see which cause would be the first to fix.
If orders, delivery records and customer messages live in separate tools, a custom software layer that pulls them into one customer record can turn a half-day search into a few minutes.
Sources
- Stripe, How disputes work (the dispute process, response windows and consequences of not responding).
- Stripe, Responding to disputes (what evidence to submit).