Chargeback fundamentals

What Is a Chargeback? A Shopify Merchant’s Starting Guide

Online shopping credit cards.
Photo: Shopify Partners / Burst

A chargeback is a payment dispute raised through the cardholder’s bank that reverses a disputed card payment through the payment system. For a Shopify merchant, its arrival creates a bank case connected to a transaction. The order may already have been delivered, and the customer may never have contacted the store.

The useful first question is therefore concrete: which payment is being challenged, for what amount, under which reason, and where is the merchant expected to respond? Those details turn an alarming notification into a manageable operational record. Shopify’s chargeback overview describes the bank-led process and its Shopify Payments context.

Start with the payment, then identify the case

An order records a purchase from your store. A card transaction records the movement of payment associated with that purchase. A chargeback concerns a challenged transaction. Keeping these objects separate prevents mistakes when an order contains several payments, an edited amount, or more than one fulfillment.

Open the order associated with the notice and establish which processor accepted the payment. Shopify is the commerce platform, but a Shopify order can involve a payment provider with its own dispute interface. The place where you sell and the place where you answer a bank claim are not always identical.

Record the store, order reference, transaction reference if available, and dispute reference if shown. An order number alone is weak identification across multiple stores because each store can use similar numbering. The amount and currency provide another cross-check, but two purchases can share a total. Use the combination of identifiers rather than selecting the first familiar-looking order.

Understand what the notification actually gives you

Treat the notice as a pointer to a live case. It normally provides enough information to locate the disputed transaction and tells you that attention is required. The authoritative working record is the applicable dispute page, where you should verify the current state and any response deadline.

A practical intake record contains five fields:

Field Question it answers
Case type and current status What process is happening now?
Processor and transaction Where does responsibility sit?
Disputed amount and currency What value is actually challenged?
Assigned reason What allegation needs to be understood?
Response deadline, with time zone When does a merchant action become unavailable?

Do not fill gaps with assumptions. If an email omits a time zone, inspect the native case. If its reason is broad, read any available claim details. If the order total differs from the disputed amount, preserve both values. Changing the record to make the numbers match destroys a useful clue.

Shopify explains that third-party payment disputes can follow different processes in its response guidance. Apply the workflow belonging to the actual processor.

Separate an allegation from your conclusion

The reason attached to a chargeback describes the issue raised through the bank. It is the starting question, not a complete reconstruction of events. A claim about nonreceipt could involve a lost parcel, an incomplete shipment, a delivery-location misunderstanding, or a disagreement about when delivery was promised.

Your first internal note should be factual: “Payment challenged as product not received; carrier record not yet checked.” That statement preserves uncertainty and gives the next person a useful task. “Customer committed fraud” does neither unless a reliable investigation has established that conclusion.

Do the same with successful fulfillment. A fulfilled order is a store operational record. It does not independently answer every allegation that a bank can receive. The appropriate question depends on the reason: whether the purchase was authorized, whether the goods arrived, whether the promised credit occurred, or something else.

A hypothetical first case

Suppose a fictional homewares store receives a notice for order H1048. The order total is £126, but the disputed amount is £42. The order shows three items shipped together. The reason is product unacceptable.

An effective intake note reads: “H1048, Shopify Payments, £42 disputed from £126 order. Product unacceptable. Current case and deadline verified in native dispute page. Owner: operations lead. Need to identify which item and complaint correspond to £42.”

The merchant has not yet decided whether to contest. That is appropriate. The note identifies the payment channel, preserves the smaller claim amount, and directs the next review toward the relevant product rather than the entire shipment.

An ineffective intake would copy the £126 order total into a dispute tracker and assign a task to prove delivery. That task answers a different question and starts with the wrong value.

Choose the next decision deliberately

Once the case is identified, assign one person to decide whether the claim is valid, disputed, or still unclear. The owner should know where the live case sits and when the response opportunity closes. Detailed evidence preparation belongs after that orientation.

Before leaving the first review, confirm that the case is linked to the correct transaction, its deadline is recorded from the current interface, and the next action has an owner. These modest steps do not determine the bank’s decision. They establish the reliable starting point every later decision needs.

Explore Lower Chargeback to review Shopify dispute status, amounts, and deadlines.

Explore Lower Chargeback

Related reading in this collection: