When a cardholder disputes a payment, the merchant can be asked to accept the chargeback or challenge it with evidence. The challenge stage is commonly called representment. Winning depends less on sending a large file than on supplying evidence that directly answers the card issuer's stated reason for the dispute.
Start with the reason code and deadline
A chargeback notification should identify why the cardholder disputed the transaction and the deadline for the merchant response. Common disputes include unauthorised use, goods not received, goods not as described, duplicate processing or a refund that the customer says never arrived.
Do not use one generic response pack for every case. A delivery dispute needs fulfilment evidence; an unauthorised-use dispute needs transaction, authentication and customer-linkage evidence. Missing the provider's deadline normally means losing the opportunity to contest regardless of how good the evidence might have been.
Submit evidence that proves the specific commercial facts
Stripe's UK fraud guidance lists examples such as web logs, customer emails, shipment tracking, delivery confirmation and evidence of previous refunds. The useful evidence depends on the dispute type and the card scheme's rules.
For a service business, signed acceptance, login records, usage history and communications can be stronger than a shipping label. For a subscription, show signup terms, renewal notice and cancellation history. Keep the pack concise enough that the issuer can see the relevant timeline without searching through dozens of unrelated screenshots.
Show that the customer saw the refund and cancellation terms before purchase
Where the dispute concerns cancellation or refund rights, evidence should show the policy that applied at the time of purchase and how it was presented to the customer. A policy added to the website after the transaction is weak evidence.
Store the version or timestamp of material terms for online orders. For high-value bookings, send confirmation containing the cancellation conditions. Good commercial documentation reduces chargebacks and also makes representment stronger when a customer later disputes what was agreed.
Prove delivery to the right customer or location
For physical goods, use carrier tracking, delivery address, signature where available and order communication. If the customer collected in person, preserve collection identification or signed handover according to the business's privacy policy.
High-value merchants should design fulfilment with later disputes in mind. Leaving a £2,000 parcel outside without proof may be operationally convenient but creates weak representment evidence. The cost of stronger delivery can be justified by the fraud and dispute profile.
Contacting the customer does not replace the formal response
It can be useful to contact the customer and resolve a misunderstanding, but Stripe advises merchants to submit dispute evidence even if the customer says they will withdraw the claim. The issuer controls the formal dispute process.
Keep customer communication professional and do not pressure a cardholder to withdraw a legitimate dispute. If a refund is agreed, coordinate it through the processor so the merchant does not both refund separately and lose the chargeback amount.
Keep the disputed amount, fees and final outcome separate in the ledger
When a chargeback opens, the processor can debit the disputed amount and a fee from merchant settlement. Record the amount as a disputed receivable or appropriate adjustment rather than hiding it inside payment-processing fees.
If representment succeeds and the amount is restored, reconcile the credit back to the original dispute. Track win rate by reason code. A high volume of lost delivery disputes suggests an operational problem that evidence alone will not solve.
Build a dispute library by reason code before volumes become large. Keep standard evidence locations for delivery, terms, authentication, refunds and customer communication, but never submit boilerplate without tailoring it to the actual transaction. A standard process should make evidence faster to assemble, not turn representment into an automated pile of irrelevant documents.
Use a worked loss calculation. If a £600 order is disputed and the merchant has already paid £25 processing and shipping costs, losing the chargeback can cost more than £600. That makes prevention decisions easier to justify. Signature delivery, stronger fraud screening or manual review can look expensive until the business compares them with the full cost of lost disputes.
Review disputes by acquisition channel. Social-media sales, first-time international buyers or one marketing campaign can produce disproportionate chargebacks. If one channel generates 5 percent of sales but 40 percent of disputes, the response should be commercial as well as procedural.
Keep response ownership outside frontline customer service for material disputes. A trained payments or finance employee should review the reason code, select evidence and submit before deadline. Customer-service notes remain important evidence, but untrained staff should not decide whether a £10,000 chargeback is accepted or contested.
Editorial Verdict
Representment is an evidence exercise. Start with the reason code, meet the deadline and submit facts that answer the issuer's question rather than a generic bundle of documents.
Design ordering, fulfilment and refund processes so evidence exists before a dispute happens. The best chargeback programme does not only win more cases; it uses dispute data to reduce the underlying causes.
Sources
- Stripe UK, Managing fraudulent transactions: https://stripe.com/gb/guides/managing-fraudulent-transactions
- Stripe UK, Ecommerce chargebacks explained: https://stripe.com/gb/resources/more/ecommerce-chargebacks-101
- Stripe UK, Chargeback time limits in the UK: https://stripe.com/gb/resources/more/chargeback-time-limits-in-the-uk