Chargeback representment explained without the vendor spin
A $214 dispute came in under reason code 13.1, merchandise not received. The response that went back held the order confirmation, the paid invoice, and a screenshot of the product page. It lost, and it deserved to.
Not one of those three documents said the package arrived.
That gap, between proving the order existed and disproving what the cardholder actually claimed, is most of what separates a representment worth filing from 30 minutes you will not get back.
Representment is one step in a longer sequence
The word is literal. Your acquirer presents the transaction to the issuing bank a second time, with evidence attached, and asks the issuer to reverse the chargeback it just filed.
The sequence runs like this. The cardholder disputes a charge with their bank, the issuer files a chargeback and pulls the funds, and your processor notifies you with a window to respond.
You submit evidence, and the issuer either accepts your case or holds its position.
If the issuer holds, some networks allow escalation to pre-arbitration and then arbitration, where the network decides and the losing side pays the fees.
Two things follow from that shape. You are arguing to the issuer, not to the customer, and you get one substantive shot at it.
Evidence answers an allegation, it does not describe an order
Every chargeback arrives with a reason code, and the reason code is a specific accusation. Your evidence has to contradict that accusation. Order confirmations, invoices, and screenshots of your storefront rarely do.
Merchandise not received. Carrier tracking that shows delivery, the delivery address matched against the address on the order, delivery confirmation or signature where the carrier captured one, and any customer message acknowledging receipt.
Not as described or defective. Your product page copy and images as they stood on the purchase date, the specification the customer actually bought against, your published policy, and the support thread where the issue was raised or never raised.
Cancelled recurring transaction. The subscription terms the customer agreed to, your cancellation record showing no cancellation before the renewal, the renewal notice you sent, and any usage after the renewal date.
Fraud in a card-absent environment. This one is different, because you cannot prove delivery to someone who claims they never bought anything. You have to link the transaction to the cardholder: AVS and CVV results, IP address, device fingerprint, account history, and prior orders on the same card that were never disputed.
That last pattern is formalized for Visa reason code 10.4 under Compelling Evidence 3.0. Stripe's documentation sets out the qualifying test: at least two previous undisputed transactions on the same payment method, between 120 and 364 days before the disputed one, matching on either two main evidence elements or one main and one secondary element. Meet it and liability can shift to the issuer.
The same mapping in one view. These codes are Visa's; other networks number them differently but allege the same things.
| Allegation | Visa reason code | Evidence that answers it | Evidence that does not |
|---|---|---|---|
| Merchandise not received | 13.1 | Carrier tracking showing delivery, address match, signature where captured | Order confirmation, invoice, product-page screenshot |
| Not as described or defective | 13.3 | Product copy and images as of the purchase date, published policy, the support thread | Generic storefront screenshots |
| Cancelled recurring transaction | 13.2 | Agreed subscription terms, cancellation record, renewal notice, post-renewal usage | The original signup on its own |
| Fraud, card-absent | 10.4 | AVS and CVV results, IP, device fingerprint, two prior undisputed orders on the same card (CE 3.0) | Proof the order shipped |
Reason codes and their evidence requirements differ by network, and they get revised. Pull the current dispute rules for the network in question rather than working from a list you saved last year.
The deadline is not one number
There is no universal representment deadline, and any article that hands you one is guessing on your behalf. It depends on the network, your processor, your acquirer, and your region.
On Shopify, the admin shows a due date per dispute, and Shopify's help documentation says the deadline is "typically 7 to 21 days after the chargeback is filed." Stripe's representment guide says Visa allows businesses a maximum of 30 days to respond, with the caveat that timeframes vary by network. Confirm the rules for your own setup in your processor's dispute documentation and your acquirer's merchant agreement.
Then build the worksheet from your records. For each open dispute, write down five things: the due date your processor shows, an internal cutoff at least two days earlier, the person who owns the response, the evidence items that reason code requires, and whether that evidence is still retrievable. The last one catches people out, because carrier tracking detail and device logs both age out.
When not to fight, and the math for everything else
Filing everything is a strategy, and it is usually the wrong one. Some cases are worth conceding on the day they arrive.
You cannot answer the allegation. A not-received claim on a digital product with no access log is not winnable by adding more paperwork.
The customer is right. The item did arrive damaged, or the cancellation request did sit unactioned in a shared inbox. Fighting costs you the fee, the labor, and the customer.
The transaction was genuinely fraudulent. Mismatched AVS, a freight-forwarder address, a card used once and never again. That is a real fraud loss, and representment is not the tool for it.
Your own ledger disagrees with you. On credit-not-processed and duplicate-processing claims, check whether the refund actually settled before you argue that it did.
For everything left, the arithmetic is simple enough to do in your head. Take the disputed amount, multiply by your realistic recovery rate for that reason code, and subtract what filing costs you.
Assembling a genuine evidence packet runs 20 to 45 minutes of somebody's time. Chargeback fees run $15 to $25 and up, and whether that fee comes back on a win depends on where you are: Shopify's documentation says it might refund the chargeback fee depending on your country or region.
Then subtract the vendor's cut, if you use one. At 25% of recovered revenue, a won $214 dispute returns about $160 before you count the labor. That percentage is what most recovery pricing in this category is built on, and it is why we made representment free at Redo: no install fee, no success fee, and you keep all of what comes back. The work still costs you the 20 to 45 minutes if you would rather run it yourself.
Low-value disputes often fail this test even at a high win rate. That is a legitimate reason to concede, and a different thing from conceding because nobody got to it in time.
The honest part
Visa's Acquirer Monitoring Program fact sheet defines the VAMP ratio as the count of fraud (TC40) plus disputes (TC15) over the count of settled transactions (TC05). The exclusions it lists are disputes resolved through pre-dispute solutions and TC40 fraud that qualifies for Compelling Evidence 3.0. Disputes you won are not on that list.
The same sheet puts the excessive-merchant threshold at 150 basis points for the US, Canada, Europe and Asia Pacific from April 1, 2026, with CEMEA on a different figure. Check the current fact sheet and rules before acting on any of those numbers, mine included.
So a strong win rate and an acquirer warning letter can arrive in the same quarter, which is the argument in winning a chargeback does not fix your dispute ratio.
Nobody can promise you a win either. The issuer decides, and Shopify's documentation is blunt that once a decision is made, "that decision is final." Any vendor quoting a headline win rate is quoting a denominator you cannot inspect, which is exactly why representment win rates mislead.
Frequently asked questions
What is chargeback representment?
Presenting a disputed transaction to the issuing bank a second time, with evidence attached, asking it to reverse the chargeback. Your acquirer submits it for you. You are arguing to the issuer, not the customer, and you generally get one substantive response.
How long do I have to respond to a chargeback?
There is no universal deadline. On Shopify it is typically 7 to 21 days after filing, shown per dispute in the admin; Visa allows up to 30 days, varying by network and region. Confirm it in your processor's documentation and set an internal cutoff two days earlier.
Which chargebacks are not worth fighting?
Ones where you cannot answer the allegation, where the customer is right, where the transaction was genuinely fraudulent, or where your own ledger shows the refund already settled. Conceding those on day one is a decision, not a failure.
What to do with your last quarter
Pull every dispute you responded to and sort the outcomes by reason code rather than looking at the overall number.
You will usually find one or two codes carrying almost all of the losses. If those are not-received cases, your problem is delivery evidence, and that is fixable this month. If they are card-absent fraud cases, check how many had two prior undisputed transactions on the same card, because you may have been leaving a qualifying argument unmade.