Chargeback guide for online retailers
Understand a chargeback and your response. Separate disputes from refunds, organise order evidence and check the processor’s requirements.
- Published
- Last updated
A chargeback is a card payment disputed through the customer’s card issuer and the card scheme. For a retailer, it can remove the disputed funds while the case is assessed. Your response must address the stated reason through the payment provider’s dispute process.
Open the case notice first. Identify the payment and response deadline before issuing another refund or assembling evidence. A customer’s complaint, a refund request and a formal card dispute require different actions.
How a chargeback reaches the retailer
A chargeback starts through the card issuer, then reaches the retailer through the acquiring and payment-processing arrangements. The customer’s support message alone doesn’t start that process. Visa’s merchant dispute explanation describes a reversal of all or part of a transaction from the issuer to the acquirer and usually to the merchant.
The customer is the cardholder making the claim. The issuer supplies their card. A card network, such as Visa, sets the scheme’s dispute rules. The acquirer supplies the merchant’s card-acceptance arrangement, sometimes through a payment provider that delivers notices and collects evidence. You are the merchant responding to the claim.
In Stripe’s documented card-dispute process, the network debits Stripe and Stripe debits the retailer’s balance for the disputed amount and a fee. The funds remain held during the case. Another provider’s account movements and notices can differ.
Identify the payment event
| Event | Who starts it | What the retailer must establish |
|---|---|---|
| Refund request | Customer contacts the store | Whether a refund is due and whether a formal dispute is already open |
| Merchant refund | Retailer sends money back through the payment system | Which payment received the refund and its completed status |
| Payment reversal | Payment system unwinds or cancels a payment movement | Whether the record means an authorisation was released, a refund was processed as a reversal or a dispute caused funds to move |
| Enquiry | Issuer asks for information before a formal chargeback | The response required and whether the case later escalates |
| Chargeback | Issuer raises a card-scheme dispute | The challenged transaction, funds movement and evidence deadline |
For Shopify Payments, an enquiry initially leaves the funds in place, while a chargeback withdraws the disputed amount and fee. An enquiry can escalate. A response to the earlier enquiry doesn’t necessarily answer the later chargeback.
A chargeback credit on a customer’s statement is money credited through that dispute process. Its appearance doesn’t establish that the retailer has won or that the case has reached a final outcome. Use the provider’s case status and settlement records to track your side.
PayPal also has its own buyer-dispute process. A card-funded PayPal payment can instead be challenged through the card issuer. Keep the case type visible so staff respond through the correct channel.
Check the dispute before responding
Read the case details and reconcile the payment before deciding whether to accept or challenge the chargeback. A delivery complaint needs different evidence from a claim that the cardholder never authorised the payment.
- Record the case reference and linked payment identifier. Confirm the store account, currency and exact disputed amount.
- Read the reason category and any issuer claim provided. Identify what the customer alleges happened.
- Record the provider’s response route and deadline, including the time zone. Assign one staff member to submit the response.
- Reconcile the order with each captured payment and completed refund. Keep fees separate from the amount the customer disputes.
- Decide whether the claim is supported. Accept a justified chargeback through the case workflow. Challenge it when relevant records support your position.
Stripe’s response instructions describe a response window usually between 7 and 21 days, depending on the network. The deadline on the case controls your response. The customer’s filing window and the bank’s later review period are separate clocks.
A chargeback fee is a provider charge for handling the dispute, additional to the disputed purchase amount. Fee refunds depend on the provider and outcome. Shopify Payments returns its chargeback fee after a win. Stripe distinguishes its dispute-received fee from its fee for challenging a dispute, with different refund rules.
Don’t issue a separate payment to the customer to close an open card dispute. Stripe blocks ordinary refunds while the dispute is open. Shopify also restricts refunds during an open chargeback. Use the provider’s documented case process to avoid returning the same money twice.
Reconcile a split payment
A dispute against one payment component doesn’t automatically cover every tender used for the order. Separate the order total from the individual payment records and the case amount.
Consider a fictional $300 order paid with an $80 gift card and a $220 card payment. Before the dispute, the retailer refunds $40 to the card. The issuer then disputes the original $220 card payment.
| Record | Amount | What it establishes |
|---|---|---|
| Order total | $300 | Value before the refund |
| Gift-card payment | $80 | Separate tender outside this card-dispute notice |
| Original card payment | $220 | Transaction challenged by the issuer |
| Completed refund to that card | $40 | Money already returned, with its own refund reference |
| Card amount retained after refund | $180 | $220 less $40, before the chargeback debit |
| Chargeback notice | $220 | Amount the processor has actually put in dispute |
Include the completed refund record in the evidence. Don’t silently change the notice to $180 or assume the bank has deducted the $40. Explain the difference so the processor can account for the earlier refund. The gift-card component needs its own refund reconciliation if it is also challenged through the store.
Shopify’s refund documentation shows why the payment destination matters: partial refunds on orders with multiple transactions have a suggested split that merchants can adjust. A refund to a gift card doesn’t prove that the disputed card payment was refunded.
Build evidence around the actual claim
Build a short response that answers the dispute reason and connects every assertion to a record. An order confirmation proves that an order exists. It doesn’t alone prove that the cardholder authorised it or received the goods.
| Dispute reason | Evidence that answers it | Limit to recognise |
|---|---|---|
| Payment not authorised | Recorded authentication outcome, transaction details and relevant evidence of cardholder participation | A successful payment or a support email alone doesn’t prove authorisation |
| Goods not received | Order contents, agreed delivery address and carrier delivery records | Dispatch proves sending, while the claim concerns receipt |
| Goods not as described | Description shown at purchase, selected variant, supplied goods and relevant customer correspondence | A current edited product page doesn’t establish what the customer saw |
| Refund not received | Refund identifier, amount, original payment link and completed status | An internal note promising a refund doesn’t prove completion |
| Duplicate charge | Separate payment identifiers and records of each purchase or correction | Two charges require evidence of two valid transactions or the relevant refund |
Visa’s merchant dispute guide gives reason-specific evidence requirements. For delivery disputes, it describes proof matching the agreed delivery address and carrier status. Use the reason and card scheme for the actual case instead of sending the same bundle for every dispute.
A focused delivery response
In a fictional non-receipt case, order R204 contains one lamp. The retailer’s response identifies the disputed card transaction and the lamp on the order. It attaches the carrier record showing delivery to the agreed address, plus the relevant support exchange about that delivery.
If the carrier record shows a different address, investigate the mismatch before asserting delivery. If the customer alleges an empty parcel, a delivered status alone doesn’t answer that allegation. The case narrative must match what the records establish.
Stripe’s evidence guidance recommends ordered evidence with relevant excerpts and short explanations. A full conversation transcript can hide the message that answers the claim. It can also expose unrelated orders or personal information.
Keep original records privately and submit readable copies through the processor’s secure evidence channel. Remove unrelated content while retaining the identifiers and delivery details the case requires. Provide records themselves where requested, because an external link might not be reviewed.
Submit and verify the response
Submit through the provider handling the disputed payment and retain proof that the case has moved beyond a draft. Uploading files and saving them doesn’t necessarily send the response.
- Open the provider’s case and confirm it still accepts evidence. If it has already resolved automatically, read the recorded outcome before attempting a normal response.
- Check the case reference and evidence against the final disputed amount. Include any completed refund and its payment link.
- Review the final response for unsupported claims and unnecessary personal information. Check that each attachment opens and is readable.
- Submit or confirm the provider’s scheduled submission. Save the receipt or status confirmation and a copy of the evidence sent.
- Watch for a request or outcome in the case. When it closes, reconcile the actual funds and fees with the decision.
Stripe permits one final evidence submission through its dashboard. The response cannot then be edited, and its status changes to “under review”. Shopify Payments can populate available evidence and send it on the due date. Review the available evidence before that happens.
Shopify’s resolution instructions also address customer withdrawals. If a customer says they cancelled the chargeback, keep responding through the case and provide the required bank withdrawal letter. Their message alone doesn’t establish that the banking process has closed.
If the submission option is missing, check whether the case is closed or whether a network-resolution program has already refunded the customer. Contact the provider with the case reference if the recorded state conflicts with the notice. Retain the deadline and any submission error when reporting the problem.
Timing and outcomes
Stripe’s card-dispute lifecycle describes a process that can take two to three months from initiation to final decision. Issuer evidence review usually takes 60 to 75 days. Those are documented Stripe timings, not a deadline for every provider or payment method.
Evidence supports a challenge but doesn’t guarantee a win. A closed case can return funds, leave the chargeback in place or produce a partial outcome where the provider supports one. Confirm the amount that actually returns, including how the provider treats fees.
Complain about the provider’s handling separately
A complaint about missed evidence or an incorrect fee is different from challenging the customer’s card dispute. Submit a formal complaint to the provider’s complaints team. Identify what went wrong and the remedy you want, with the case record and submission evidence.
For example, Stripe’s complaints procedure gives Australian users a written-response timeframe of 30 calendar days. Its Australian external-escalation route applies to users receiving regulated financial services from Stripe Payments Australia Pty Ltd. Don’t assume every Stripe service or contracting entity has the same route.
The Australian Financial Complaints Authority (AFCA) can consider eligible small-business complaints about financial services, including merchant facilities. Its complaint eligibility guidance requires a complaint against an AFCA member and applies its own jurisdiction and time limits. AFCA generally defines a small business as having fewer than 100 employees, with group rules also relevant.
Use the provider’s internal complaint process first, then assess AFCA eligibility for that provider, service and business. A provider-handling complaint doesn’t itself pause a card-dispute deadline or guarantee that a card-scheme result will change.
Reduce avoidable disputes
Reduce disputes by addressing the cause the store can control. Accurate product descriptions help customers buy the intended item. Delivery promises must match fulfilment, and customers need a direct route to resolve missing or damaged orders.
Use a recognisable billing descriptor and explain it in the order confirmation where useful. Tell customers about delays before an expected delivery is missed. Keep refund status visible to support staff so they can distinguish a completed refund from an unfulfilled promise.
Treat chargeback fraud as deliberate misuse of the dispute process. An unfamiliar descriptor or a genuine delivery failure doesn’t establish abuse. Use payment authentication and proportionate fraud checks for suspicious transactions, while keeping a review route for legitimate customers.
Australian consumer guarantees still apply. A store’s fraud policy or “no refunds” wording cannot remove statutory rights. Assess the required remedy separately from whether you have evidence to challenge a chargeback.
Compare what a prevention or management service actually does
An alert, an automatic refund and a prepared evidence file are different services. Compare the provider’s documented responsibility at each stage without treating a prevention claim as a promise that every dispute disappears.
| Capability | Establish before relying on it |
|---|---|
| Alerts | Which networks and payments are covered, when the alert arrives and who must act |
| Early resolution | Whether the service refunds automatically, which rules trigger it and what funds and fees it uses |
| Evidence preparation | Which records it imports, what staff must add and whether you can inspect the final response |
| Submission | Who sends the evidence, whether approval is required and how a submission receipt is retained |
| Fees and protection | Whether charges arise per alert, refund or challenged case, and which losses or fees the contract covers |
| Source records | Whether transaction identifiers and original documents remain accessible after the case closes |
Shopify documents network-resolution arrangements that refund customers before a formal chargeback and provide no evidence-submission window. That is a different action from Stripe’s documented process of collecting evidence for a final issuer submission. Both require you to understand what the provider has actually done.
Protection also has boundaries. PayPal’s Australian Seller Protection terms exclude item-not-received claims made as issuer chargebacks on card-funded transactions. Other eligible claim types have conditions, including required evidence and timely responses. The word “protection” alone doesn’t establish coverage for a particular case.
Choose one recently closed dispute for an internal review. Trace the customer’s complaint to the submitted evidence and the final money movement. Assign the underlying product, delivery or support fix to someone who can prevent that same avoidable problem on the next order.
Give your store its own shopping agent
Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.