Chargeback Disputes: What Merchants Get Wrong Before They Submit

You can lose before the issuer ever evaluates your evidence

Most lost chargebacks are operational losses, not evidence losses. A late submission, a missing delivery status, a payment detail that doesn't match — any one of these kills the case before an issuer reads a single line of your response. If you're using Shopify Payments, the dispute surfaces under Shopify Admin > Orders > [Order] > More Actions > Submit Evidence. That's where the deadline lives, and that deadline is non-negotiable. Issuers won't review submissions past it, and processors won't extend it — confirm the exact window with your processor, since response timelines vary.

Before you build an evidence package, run the order through four Admin checks: Payment Details (verify the transaction data matches exactly what the issuer has on file), Timeline (pull every customer communication — issuers look for documented interaction to assess dispute validity), Fulfillment Details (confirm tracking status and whether delivery confirmation is present), and Fraud Analysis (flag any high-risk indicators that should have stopped fulfillment). If any of these surfaces a gap, that gap is in your response too. DisputeDesk handles evidence organization and deadline tracking automatically, but the merchant still owns the final review of what those fields actually say.

What the evidence actually proves — and where issuers push back

Three evidence types show up in almost every goods-not-received dispute, and all three have a ceiling.

AVS Y confirms the billing address matched the card issuer's records at authorization. That's a meaningful signal — it suggests the cardholder authorized the transaction. What it doesn't do is prove the cardholder physically received anything. Issuers handling goods-not-received claims are looking for possession, not authorization. AVS Y is supporting context, not a standalone win. Visa and Mastercard may weigh it differently depending on processor routing, so don't anchor your response to it.

Tracking marked delivered confirms the carrier logged a delivery event at the shipping address. Issuers will accept this as evidence of fulfillment completion — up to a point. Multi-unit residences, business addresses, and package theft scenarios all create room for the cardholder to argue non-receipt without technically lying. Carrier delivery confirmation is necessary but not sufficient for high-value disputes.

Customer acknowledgment emails — a message from the cardholder confirming receipt or satisfaction — are the strongest possession evidence available. The problem: issuers in high-value disputes sometimes flag these as potentially fabricated, especially without corroborating metadata. Submit with full email headers and timestamps. Pair with delivery logs. An email alone, stripped of headers, is easier to dismiss than you'd expect.

The $1,200 electronics dispute that looked fightable and wasn't

An electronics merchant with a $350 average order value received a goods-not-received chargeback totaling $1,200. The order timeline was clean: placed January 5th, shipped January 6th with tracking, carrier logged delivery January 8th. The chargeback came in January 15th. The merchant submitted evidence January 20th — within the deadline, but five days after the dispute was filed.

The evidence package included AVS Y, the carrier delivery confirmation with tracking number, and a customer email from January 9th — one day after delivery — that appeared to confirm receipt. On paper, this looks like a strong response. AVS match, delivery confirmed, customer acknowledgment in writing. Most merchants would submit this and expect a win.

The case was vulnerable for one reason: no signature, and no proof the cardholder personally received the package. The delivery address was a multi-unit building. The January 9th email had been forwarded from the customer's account without original headers — the merchant had stripped metadata when copying it into the evidence package. The issuer flagged the email's authenticity, discounted it, and ruled for the cardholder. The delivery confirmation showed the carrier's scan, not cardholder possession. AVS showed billing match at authorization, not receipt.

The merchant had the right evidence types and the wrong versions of them. The email needed headers and timestamps intact. The delivery needed a signature or, at minimum, a photo-on-delivery confirmation from the carrier. For any order above $500, signature-on-delivery is the operational fix — not an evidence fix, a fulfillment fix that makes future disputes fightable before they're filed.

Decision lesson: A case with AVS Y, carrier delivery, and a customer email is fightable — if the email has intact headers and the delivery has cardholder-level confirmation. Without those, the issuer has two pieces of circumstantial evidence and one document of questionable authenticity. That's a loss. The evidence existed; the versions submitted didn't hold up.

Before you submit: what to verify in sequence

Work through this before hitting submit on any dispute response.

1. Deadline: Pull the exact response deadline from Shopify Admin under the dispute record. Confirm it against your processor's stated timeline — Shopify's display and your processor's internal clock can differ by a day. Set an internal alert at least 48 hours before cutoff.

2. Shopify Protect status: Check whether the order shows PROTECTED, ACTIVE, or no Protect coverage. If it's PROTECTED, Shopify absorbs the dispute cost — you may not need to respond at all. Confirm the coverage scope before spending time on evidence.

3. Dispute reason code: The reason code determines what the issuer actually needs to see. Goods-not-received requires possession evidence. Fraud requires authorization evidence. Submitting the wrong evidence package for the reason code is a common way to lose a winnable case.

4. Evidence match: Every document in your package should directly address the reason code. AVS for authorization disputes. Delivery confirmation plus cardholder acknowledgment for goods-not-received. Customer communication logs for service disputes. Trim anything that doesn't map to the code — it adds noise without adding weight.

5. Delivery proof quality: Does your delivery confirmation prove cardholder receipt, or just carrier drop-off? For orders above a threshold you're comfortable absorbing, signature-on-delivery or photo confirmation is the standard. Confirm with your carrier what's available for the specific shipment.

6. Email and document integrity: Any customer communication submitted should include full headers and timestamps. Stripped or forwarded copies are easier for issuers to discount.

7. Fight or accept: If the order value is below your dispute response cost — time, fees, and probability-weighted loss — accepting may be the right call. A $40 order with weak evidence and a $25 response overhead isn't worth the fight. Run the math before you build the package.