A customer disputes a charge with their bank. The money is taken back, a fee is added, and you are asked for evidence within a short window.
The outcome depends almost entirely on records that had to exist before any of this started.
What actually counts as evidence
The terms they accepted, with a record of when. A checkbox at signup with a timestamp is worth more than terms published on a page nobody agreed to.
What was provisioned and when. The account creation record, the plan, the domain.
Server logs showing the service was used. This is the strongest item available to a hosting provider and it is frequently overlooked. Access logs demonstrating a site was being visited (and a control panel login record showing the customer was signing in) directly contradict a claim that the service was never received.
The support correspondence. A customer who raised tickets during the period they say they were not a customer has made your case for you.
Where server logs live covers finding those records, and note that they rotate, export what you need immediately rather than when the response is due.
Suspend, do not terminate
While a dispute is open, suspend the account.
Suspension stops the service, preserves everything, and is reversible in either direction. If the dispute resolves in your favour and the customer pays, they are back in a second.
Termination destroys the customer's data and your evidence at the same moment, and it is the action you cannot walk back if the dispute turns out to be a misunderstanding.
Suspending, unsuspending and terminating accounts deals with the mechanics and the checks before the irreversible one.
Try the conversation first
A surprising share of disputes are not disputes. They are a customer who did not recognise a charge, or who cancelled and believed that ended the billing, or whose card was used by someone else in their organisation.
A direct message asking what happened resolves those faster than any process, and the payment provider's route is slow and impersonal for both parties.
If the customer agrees it was a misunderstanding, ask them to withdraw the dispute with their bank: a refund from you does not automatically close one, and you can end up paying twice.
The common causes, and preventing them
An unrecognised charge. The billing descriptor does not match your business name. This is straightforwardly fixable and causes a real share of disputes.
Automatic renewal. The customer forgot the service renews. A reminder a week before renewal costs nothing and removes the surprise. Understanding billing cycles goes into what customers actually expect.
A cancellation that was not processed. A customer who emailed asking to cancel and was never actioned has a strong case and is right.
Dissatisfaction. A chargeback used as a refund request. The written refund policy matters here, and so does whether you responded to their complaints. What to include in your hosting terms sets out stating it in advance.
Respond even when you expect to lose
Providers weigh a merchant's dispute rate as well as individual outcomes. A pattern of unanswered disputes is worse than a pattern of answered ones that went against you.
Respond factually, with documents, and without argument. Nobody reading it is interested in how unreasonable the customer was.
Decide the policy before you need it
Whether a customer who charged back may return. Whether their data is kept, and for how long. Whether you refund in full when the complaint is reasonable.
Deciding these during an incident produces decisions you regret. Writing them down means every case is handled the same way, which is also what makes them defensible.
And take a final backup before terminating anything, whatever the outcome: it converts every future "can I get my site back" into a file transfer instead of an impossible conversation. What to do when a client leaves walks through the orderly version of the same ending.
Preserve the evidence before it rotates
Disputes arrive weeks after the period they concern, and by then the logs that would answer them may be gone.
zgrep -h "$(date -d '30 days ago' +%d/%b/%Y)" ~/logs/example.com*.gz 2>/dev/null | head cp ~/logs/example.com /root/evidence/example.com-$(date +%F).log
When a dispute is raised, the first action is to copy the relevant logs somewhere they will not rotate, before responding, not after.
What to keep: access logs showing the service was used, control panel login records showing the customer signed in, and the mail log if delivery was part of what they paid for. Where server logs live goes into finding each.
Present it in the order the reader needs
The person assessing a dispute reads many of them and gives each a few minutes.
Lead with the single strongest fact, usually that the service was demonstrably in use during the disputed period, then the terms they accepted, then the timeline. Attach the documents rather than describing them.
Keep it factual and short. A long account of how unreasonable the customer has been reads as weakness, and nobody assessing the case is interested in the relationship.
Reduce the disputes rather than winning them
Three changes remove most of them, and all are cheaper than responding.
A recognisable billing descriptor. A charge from a name the customer does not associate with your service is disputed as fraud in good faith.
A renewal reminder before the charge. Seven days is enough to remove the surprise, and it also recovers customers who intended to cancel and would otherwise dispute.
A cancellation route that works. A customer who tried to cancel and could not is a dispute you will lose and should. Understanding billing cycles goes into what customers actually expect.
Watch the rate, not only the outcomes
Payment providers assess merchants on the proportion of transactions disputed, and a rate that climbs brings consequences beyond the individual cases: higher fees, held funds, or the account being closed.
Track it monthly rather than reacting per case. A rising rate is a signal about the product or the billing, not about customers becoming less honest.
And respond to every one, including those you expect to lose. A pattern of unanswered disputes is treated worse than a pattern of answered ones that went against you. What to include in your hosting terms explains the document each response refers back to.