Chargeback Representment: Merchant Playbook

The dispute is filed. Here's what you do next — in order.

A chargeback lands in Shopify Admin → Orders → Disputes. The account has already been debited. The cardholder's bank has provisionally credited them. Your job now is representment: re-presenting the transaction with evidence and argument sufficient for the issuer to reverse that provisional credit and rule in your favor.

Most merchants treat representment as a document-gathering exercise. It isn't. It's a legal argument delivered in a format an analyst will spend roughly ninety seconds evaluating. The merchants who win consistently aren't the ones with the most evidence — they're the ones whose submissions answer the right question, in the right order, without making the analyst work to find the point.

This playbook runs the full sequence: reading the dispute correctly, deciding whether to fight, assembling the packet, writing the rebuttal, submitting, and logging the outcome. Follow it in order. Skipping steps two and three — the ones that happen before you touch a single file — is where most cases are lost.

Step 1: Read the reason code before you open the order

The reason code is the cardholder's legal theory. Everything you submit must rebut that specific theory. Submitting evidence that's accurate but irrelevant to the code is the single most common representment failure — and it's invisible to merchants who skip this step.

The major code families, and what each one actually requires you to disprove:

• Unauthorized transaction (Visa 10.4, Mastercard 4837, Amex FR2): The cardholder claims they didn't make the purchase. You need to show they did — or that the transaction was authorized by someone with access to their account and device. AVS and CVV match prove the billing data was entered correctly; they don't prove the cardholder placed the order. Behavioral signals — device fingerprint, IP geolocation consistent with prior orders, same shipping address used in prior non-disputed transactions — carry more weight here than authorization data alone.
• Item not received (Visa 13.1, Mastercard 4855): Carrier confirmation with the delivery address matching the order is the core evidence. For high-value shipments, signature confirmation is close to mandatory. Screenshot the tracking record at the time of submission — carrier portals sometimes purge records, and a dead tracking link in your submission is worse than no tracking at all.
• Item not as described / significantly not as described (Visa 13.3, Mastercard 4853): Product photos, specification pages, and the customer's own prior communications are your primary tools. If the customer contacted you before filing and you resolved or offered to resolve the issue, that exchange is evidence of good faith and undercuts the dispute's premise.
• Credit not processed (Visa 13.7, Mastercard 4860): If you issued the refund, show the refund transaction record with date and amount. If the refund was issued after the chargeback was filed, note that explicitly — the issuer needs to know the credit exists to avoid a double-recovery. If you didn't issue a refund because the return wasn't received or the policy wasn't met, your refund policy and the customer communication record are the evidence.
• Subscription / recurring billing (Visa 13.2, Mastercard 4854): Enrollment confirmation, the recurring billing disclosure at checkout, and any cancellation request log (or absence of one) are the three required elements. If the customer cancelled and you billed anyway, concede — there's no representment path that wins that case.

Once you've mapped the code to the claim, open the order. Now you know what you're looking for.

Step 2: Audit the order timeline for gaps before you commit

Before building anything, run a fast timeline check. Pull the order record and map these dates in sequence: order placed → payment authorized → fulfillment triggered → carrier pickup scan → delivery confirmation → dispute filed. Any gap longer than your stated processing or shipping window is a liability. Any gap you can't explain with documentation is a gap the issuer will notice.

Also check: Was there a customer service contact between order and dispute? If so, what was said, and was it resolved? A customer who emailed "where is my order" three days before filing an item-not-received dispute, and received a tracking number in response, is a very different case than one who filed with no prior contact. The former is winnable. The latter depends entirely on whether delivery actually confirmed.

If the timeline has unexplained gaps — a fulfillment delay you can't document, a carrier scan that never happened, a customer service thread that went unanswered — that's a signal to evaluate whether fighting is worth it before you spend time building a packet.

Decision point: Fight or concede?

This is the most consequential decision in the representment process, and most merchants make it reflexively rather than analytically. Fighting every dispute is not a winning strategy. Neither is conceding every dispute.

Path A — Fight the dispute. You submit a full representment packet. If you win, you recover the transaction amount. If you lose, you absorb the chargeback (already debited), the dispute fee (typically $15–$25, confirm with your processor), and the time cost of building the response. More importantly, every dispute — won or lost — counts against your dispute ratio. Visa's VAMP program and Mastercard's ECM both monitor dispute-to-transaction ratios, and exceeding thresholds triggers monitoring programs that carry their own fees and, at the extreme end, account termination. Fighting unwinnable disputes inflates your ratio without recovering revenue.

Path B — Accept the loss. You do nothing, or you formally accept the dispute in Shopify. The chargeback stands. You absorb the transaction amount and the dispute fee, but you don't spend time on a losing case, and you don't add a representment attempt that still counts as a dispute event. For low-value disputes where your evidence is weak, this is often the correct call — especially if the order value is below your processor's dispute fee threshold, where fighting costs more in time than the transaction is worth.

The decision criteria: Fight if (a) the transaction amount meaningfully exceeds your dispute fee, (b) you have direct evidence that rebuts the specific reason code, and (c) the cardholder's claim has a factual weakness you can document. Concede if any of those three conditions fails, or if the order timeline has a gap you can't explain.

One additional consideration: if you're seeing repeated disputes from the same customer or the same SKU, the representment decision is secondary to the operational question of why that pattern is occurring. Winning individual cases doesn't fix a systemic problem.

Step 3: Assemble the evidence packet — structure over volume

The standard advice is to submit everything. In practice, a focused five-signal submission beats a twenty-document dump. Past a certain point, the analyst stops reading — and a submission that buries the key evidence under irrelevant screenshots actively hurts your case by making the analyst work to find the argument.

Build the packet in issuer-reading order, not merchant-logic order. The issuer doesn't care how the order flowed through your system. They care about one question: does the evidence support the merchant's claim that this transaction was valid and fulfilled as described?

Assemble in this sequence:

1. Rebuttal letter — goes first, always. This is the only document the analyst reads in full. Everything else is an exhibit referenced by the letter.
2. Order confirmation — shows the transaction details, billing address, shipping address, and what was purchased.
3. Authorization record — AVS result, CVV result, 3DS authentication if applicable. Pull this from your payment processor dashboard, not from Shopify's order view, which may not surface the full authorization detail.
4. Fulfillment and delivery evidence — carrier tracking with delivery confirmation, timestamped. For item-not-received disputes, this is the load-bearing document. Screenshot it at the time of submission.
5. Customer communication record — any email, chat, or support ticket exchange. Relevant whether it helps or hurts: if it helps, include it; if it reveals a service failure, factor that into your fight-or-concede decision before you get here.
6. Policy documentation — refund policy, subscription terms, or product description page, depending on the reason code. A screenshot of the checkout page showing policy acknowledgment is stronger than a link to the policy page.

For Shopify Payments disputes specifically, the Disputes interface in Admin pre-populates some of this — order details, transaction record, basic fulfillment data. Treat that as a starting point, not a complete submission. The pre-populated fields rarely include behavioral signals, customer communication, or policy acknowledgment screenshots, which are often the difference between a won and lost case on unauthorized-transaction codes.

Step 4: Write the rebuttal letter — this is the case

The rebuttal letter is not a cover page for your evidence. It is the argument. Every other document in the packet exists to support claims made in this letter. If the letter doesn't make the argument clearly, the exhibits don't save it.

Structure the letter in three parts: factual record, rebuttal of the specific claim, and evidence index. Keep it to one page if possible — two at the absolute maximum. Analysts processing dozens of disputes per day do not read long letters carefully; they scan for the argument and check whether the exhibits support it.

Here is a sample rebuttal opening for an unauthorized transaction dispute, adapted for a fulfilled physical goods order:

"This representment responds to dispute [dispute ID] filed under reason code [10.4 / 4837], claiming the transaction was unauthorized. The transaction was authorized with AVS full match and CVV2 match on [date]. The order was shipped to the billing address on file and delivered with carrier confirmation on [date], [X] days before the dispute was filed. The cardholder's email address on the order matches the address used in [number] prior non-disputed transactions on this account. We respectfully request reversal of the chargeback. Supporting exhibits are attached in the order referenced below."

Adjust the specific signals to match what your evidence actually shows. Do not claim AVS match if your authorization record shows a partial match or mismatch — issuers verify these claims, and a factual error in the rebuttal letter is case-ending.

For an item-not-received dispute where delivery confirmed:

"The order was fulfilled on [date] and delivered to [city, state] on [date] per [carrier] tracking [number], attached as Exhibit B. Delivery occurred [X] days prior to the dispute filing date. The shipping address matches the address provided at checkout. No contact was received from the cardholder prior to the dispute filing requesting a replacement or refund."

For a credit-not-processed dispute where your policy wasn't met:

"No return was received by [merchant name] prior to the dispute filing date. Our return policy, accepted at checkout on [date] and attached as Exhibit C, requires items to be returned within [X] days of delivery in original condition before a refund is issued. The cardholder did not initiate a return request through our support channel. We are unable to issue a refund for an item that has not been returned."

These are starting points, not templates. The specific facts of your order need to replace the bracketed fields, and the argument needs to track the actual evidence you have — not the evidence you wish you had.

Step 5: Submit, confirm receipt, and log everything

In Shopify Admin → Orders → Disputes, upload your evidence files and submit before the deadline shown in the dispute record. The deadline displayed is typically the acquirer-imposed deadline, which may be shorter than the network maximum — do not assume you have the full network window. Confirm the exact deadline with your processor if the Shopify-displayed date seems inconsistent with what you'd expect.

After submission, confirm that Shopify registers the response as submitted, not pending. A submission that stalls in a pending state due to a file format error or size limit is a missed deadline — and missed deadlines are unrecoverable. Shopify's dispute interface accepts PDF, JPEG, and PNG; file size limits apply (confirm current limits in your Shopify Payments settings, as these have changed). If you're submitting through a third-party dispute management tool, verify that the tool's submission confirmation maps to an actual network submission, not just an internal queue entry.

Log the submission internally with: dispute ID, reason code, transaction amount, submission date, evidence files included, and a one-line summary of the rebuttal argument. This log becomes your audit trail if the case goes to arbitration, and it's the data source for any win-rate analysis you run later.

Internal note format that works:

"Dispute [ID] | Visa 10.4 | $[amount] | Submitted [date] | Evidence: auth record, delivery confirmation, 3x prior non-disputed orders same address | Argument: authorized transaction, delivered pre-dispute, behavioral pattern inconsistent with unauthorized use | Outcome: pending"

Where representment cases die — the failure modes worth knowing

Deadline misses are the most common single-point failure, and they're almost always avoidable. The dispute appears in Shopify, the merchant opens the order to start gathering evidence, and the deadline tracking falls out of the workflow. By the time the packet is assembled, the window has closed. Build deadline tracking into the first step, not the last — the moment a dispute appears, log the deadline somewhere outside the Shopify interface, because if the dispute record is accidentally archived or the tab is closed, the deadline goes with it.

File format failures are the second most common silent killer. A PDF that won't open, a JPEG that renders sideways, a screenshot that's too low-resolution to read the tracking number — these don't generate an error message that tells you the submission failed. The analyst simply can't use the evidence. Before submitting, open every file yourself and confirm it's legible at normal viewing size.

Reason code mismatch is the third. A merchant who submits delivery confirmation for a "significantly not as described" dispute has answered the wrong question. The cardholder isn't claiming they didn't receive the item — they're claiming it wasn't what was described. Delivery confirmation is irrelevant to that claim. The evidence that matters is the product listing, the specification, and any pre-dispute customer communication about the product's condition or function.

The fourth failure is subtler: submitting evidence that technically supports your position but contradicts itself internally. A rebuttal letter that claims no customer contact was made, paired with a customer service exhibit that shows a contact was made and ignored, is worse than submitting no customer service evidence at all. Audit the packet for internal consistency before you submit. If the evidence tells a complicated story, the rebuttal letter needs to address the complication directly — not pretend it doesn't exist.

After the ruling: what to do with the outcome

When the issuer rules, Shopify updates the dispute status in Admin → Orders → Disputes. A win means the provisional debit is reversed and the transaction amount is returned to your account, minus any fees — confirm the exact fee structure with your processor, as some acquirers retain the dispute fee even on won cases. A loss means the chargeback stands.

On a loss, the question is whether arbitration is worth pursuing. Arbitration — available through Visa's CE 3.0 process and Mastercard's equivalent — is expensive. Filing fees run $250–$500 (confirm with your processor), and if you lose at arbitration, you absorb those fees on top of the original chargeback. Arbitration makes sense when the transaction amount is large, your evidence is strong, and the issuer's ruling appears to have ignored directly relevant documentation. It rarely makes sense below $500, and almost never below $200.

Whether you won or lost, update your internal log with the outcome and a one-line diagnosis: what the issuer apparently found persuasive, or what the submission was missing. Over time, that log tells you which evidence types are actually moving issuers on your dispute profile — and that's more operationally useful than any general win-rate benchmark.

If you're seeing a pattern of losses on a specific reason code, the representment process isn't the place to fix it. The fix is upstream: in your checkout flow, your fulfillment documentation, your post-purchase communication, or your fraud screening. Representment recovers individual transactions. It doesn't repair the conditions that generate disputes in the first place.