
By eLotPay · Published and reviewed
A refund is a merchant-initiated return of funds. A chargeback is a reversal through the card dispute process. Fraud is an allegation or finding about what happened, such as an unauthorised payment; it is not a synonym for every chargeback. The first step in handling a complaint is to establish which process is already underway. That determines who controls the next action and what evidence is useful.
Identify the event before moving money
When a customer asks for their money back, locate the order and payment reference. Check whether the payment was captured, whether a refund exists and whether a formal dispute is open. Do not infer a successful refund from a note in the support inbox. Check its provider status and record the amount and reference. If the customer raises an unfamiliar charge, verify the order through the normal support process without asking for full card details.
Stripe’s explanation of the dispute process illustrates how a cardholder can contest a payment through their bank and how the merchant may be notified, debited and asked to respond. The details depend on the network, provider and arrangement. Follow your provider’s instructions for an open case. In particular, check before sending a separate refund: an independent payment back to the customer may leave two adjustments to reconcile.
| What you see | First operational check |
|---|---|
| Customer requests a refund | Find the captured payment, applicable customer terms and any refund or dispute already recorded. |
| Provider opens a dispute | Record the reason, amount, response deadline and agreed response channel. |
| Order appears suspicious | Check fulfilment status and route the order for review under your internal policy. |
| Refund already issued | Match its status, amount and reference to the original payment before deciding the next step. |
Collect evidence that answers the actual allegation
Start with the reason provided rather than sending every record the business holds. If the question is cancellation, assemble the offer shown to the customer, the renewal date, the cancellation request and the billing record after that request. If the complaint is non-delivery, show what delivery was promised and what actually occurred. For an unfamiliar charge, identify the order and customer communications, while recognising that an order record alone does not settle whether the cardholder authorised it.
Keep customer-facing terms as they appeared at purchase. A revised cancellation page can show what the business has fixed; it cannot prove what the earlier customer saw. Use dated records and preserve the original evidence. Provide only material relevant to the case through the agreed provider channel. Do not paste card details, passwords or intimate customer activity into a general enquiry or support note.
Worked example: a renewal is disputed after support promised a refund
Imagine a fictional membership merchant charging EUR 40 for a monthly renewal. The customer says they cancelled before renewal. An agent replies that a refund will be arranged, but the billing tool has no completed refund. The next morning a dispute notification arrives for the same payment. At this point the email is evidence of a promise, not a payment record. Issuing a second adjustment without checking the open case could complicate the reconciliation.
The merchant checks the cancellation timestamp, the plan terms presented at enrolment and the renewal event. It records the dispute reference and response deadline and confirms the permitted next step with the provider. If the company discovers that its cancellation tool stopped access but left future billing active, it should correct that process rather than relying on a general defence of the renewal. Review whether other customers were affected and route those cases through the appropriate operational process.
Finance then ties the original EUR 40 payment to the dispute, any confirmed refund and any separate fee shown on the statement. It does not count the promised refund as paid. The numbers are illustrative, not a fee quote or a prediction about the dispute. Our subscription cancellation guide provides a practical test for the gap between cancelling access and stopping billing.
Reduce future incidents at the point they begin
Sort recent complaints by cause before changing the payment setup. If customers recognise the purchase but not the statement entry, review the description used at checkout and in confirmation messages. If they bought a trial and dispute the first renewal, look at what the offer said and whether the cancellation flow works. If the issue is non-delivery, examine the promise, dispatch record and communication before treating it as a fraud screening problem.
Set a named owner for disputed renewals, refund approvals and fulfilment exceptions. Record the payment reference in the order system so support can find it without copying sensitive data between tools. Separate merchant-initiated refunds from disputed payments in internal reporting. Otherwise a refund campaign or a backlog can obscure the trend the business is trying to improve. Check any monitoring definitions and reporting periods with the providers responsible for the actual arrangement.
Merchant FAQs
Should I refund whenever a customer threatens a chargeback?
Check the case and applicable obligations. A legitimate refund may be the right resolution; a threat by itself does not tell you whether a dispute is already open or whether funds have already been returned. Confirm the status before moving money and give the customer an accurate update.
Can authentication prevent all chargebacks?
No. A customer can contest delivery, duplicate billing or a cancelled subscription even where the original payment included authentication. Ask the provider how authentication evidence applies to the specific reason and arrangement. Keep evidence of the underlying customer journey as well.
What if a partial refund was already sent?
Record the amount, status, refund reference and how it relates to the amount disputed. Ask the provider how to present it within the open case. Do not assume the remaining amount or final outcome from your own calculation alone.
Review your dispute process with eLotPay
Our chargeback management service helps define prevention, evidence and response responsibilities for eligible merchants. Use the eLotPay enquiry form to describe your billing model, common dispute reasons and current support process. The form confirms receipt after saving; scope and available tools depend on the agreed arrangement.