Representment is the merchant's right to dispute a chargeback by submitting evidence that the original transaction was valid. The right comes from the card networks' operating rules, and the Fair Credit Billing Act of 1974 gave US consumers the right to dispute charges in the first place, so representment is the merchant's half of a process designed for both sides. The numbers are blunt: merchants win only about 45 percent of the disputes they actively fight with proper evidence, and the net recovery rate across all chargebacks received is 8 to 18 percent, because most merchants never respond at all. A non-response is an automatic loss. The merchants who clear 30 percent or higher, 77 percent of merchants once they are organised, do it with the same discipline: the evidence is collected before the dispute, the packet is matched to the reason code, and the response goes in before the deadline. Most representment windows close 7 to 30 days after the dispute posts, depending on the network and processor, and a late response is the same as no response.
Build the packet before the dispute, not after
The packet is the same set of records for every order, collected as a matter of routine: order records, IP logs, device fingerprint, delivery confirmation, AVS and CVV results, and the written rebuttal matched to the reason code. The mistake is treating the packet as a dispute-time activity. By the time the dispute arrives, the IP log has rotated, the device data is gone, and the delivery confirmation is in a carrier portal that takes an hour to search. A store that logs these fields at order time can assemble a packet in under an hour. A store that does not will spend days, miss the window, and lose by default.
The rebuttal letter is the part teams get wrong. It is not a complaint about the customer. It is a short, factual narrative that walks the reviewer through the evidence in the order the reason code asks for: this is the transaction, this is the delivery, this is the customer's history, this is why the claim does not hold. Visa's Dispute Management Guidelines score evidence quality, not submission speed, so a fast packet with the wrong evidence loses to a slower packet with the right one. The deadline matters, but the match matters more.
Related reading on this site: Home and Bot Traffic and Ad Spend: Why Your ROAS Suddenly Dropped cover the neighbouring problems in more depth.
Match the evidence to the reason code
A Visa 10.4 fraud claim needs AVS and CVV matches, device and IP history, and prior-transaction evidence. A Visa 13.1 merchandise-not-received claim needs carrier tracking, a delivery signature, and usage logs showing the customer used the product after the delivery date. A 13.3 not-as-described claim needs the listing as the customer saw it, the photos, and the refund policy the customer agreed to at checkout. The same packet sent for every reason code is a generic packet, and generic packets lose, because they answer the claim the merchant wishes had been filed instead of the one that was.
The win rates by category make the point: non-fraud disputes, service and processing errors, are won about 57 percent of the time, while true fraud chargebacks are won about 9 percent, because the networks heavily favour cardholders on confirmed fraud claims. Digital goods merchants achieve the highest win rates, around 72.6 percent, because delivery evidence and IP and device logs are strongest there. The lesson is to fight where the evidence is strong and the category is winnable, and to deflect or accept where it is not.
The deadline is the whole game
Most representment windows close 7 to 30 days after the dispute posts, and the exact window depends on the network and the processor. A store that learns about a dispute on day 25 has five days to build a packet, and a store that learns about it on day 31 has already lost. The fix is automation at the intake: disputes ingested automatically, triaged by reason code, and assigned a deadline the day they arrive, with an alert at half the window. Chargeflow and Justt both auto-ingest disputes and triage by reason code, and the merchants using them report response times dropping from days to under an hour.
The second fix is to stop treating representment as a finance task. It is an operations task, and it belongs to the person who owns the order data, not to the person who owns the bank relationship. The evidence lives in the order system, the delivery system, and the support inbox, and the person who can reach all three is the one who should own the response. Give that person the deadline, the packet template, and the authority to submit, and the win rate will follow the process, not the other way around.
Frequently asked questions
What is chargeback representment?
Representment is the merchant's right to dispute a chargeback by submitting evidence that the original transaction was valid. It is the merchant's half of the dispute process, and it must be filed inside the network's window, usually 7 to 30 days after the dispute posts.
What is the average merchant win rate on chargebacks?
About 45 percent when chargebacks are actively fought with proper evidence, per Chargebacks911. The net recovery rate across all chargebacks received is 8 to 18 percent, because most merchants never respond, and a non-response is an automatic loss.
What evidence wins a fraud chargeback?
AVS and CVV matches, device and IP history, and prior undisputed transactions from the same cardholder under Visa CE 3.0. True fraud claims are the hardest to win, around 9 percent, because the networks heavily favour cardholders on confirmed fraud.
What happens if a merchant misses the representment deadline?
The dispute is lost by default. Most windows close 7 to 30 days after the dispute posts, so disputes should be ingested automatically, triaged by reason code, and assigned a deadline the day they arrive.