# Chargeback Representment: The Evidence That Wins and the Evidence That Gets Tossed

Source: https://bondproof.com/blog/2026-11-10-chargeback-representment-evidence-wins.html

[Home](../index.md) / [Blog](index.md)


**Short answer:** Representment is not an argument. It is a packet: delivery confirmation, the AVS and CVV result, the device and IP record, and the customer's messages in chronological order. Issuers decide on documents, not on how strongly you feel about the order.

## The issuer reads documents, not your side of the story

A chargeback is decided by an analyst at the issuing bank who has never seen your store, your product, or your customer. They have a packet, a reason code, and a deadline. The packet that wins is the one that answers the reason code with a document on every line. The packet that loses is a letter explaining that the customer is wrong. Issuers do not grade essays. They check whether the evidence matches the dispute.

The stakes for getting this wrong have gone up. Visa's Acquirer Monitoring Program, in effect since April 1, 2025, now includes enumeration criteria, so a merchant whose checkout is used for card testing can land in a monitoring program for the testing traffic alone, not just for chargebacks. The representment you file today is also the record of how your checkout behaves, and a thin packet tells the acquirer you are not watching it. [BIN attacks pick targets the same way](https://bondproof.com/blog/2026-11-08-bin-attacks-card-testers-targets.md): the checkout that looks unwatched gets tested first.

## The four documents that decide it

Delivery proof comes first, and it has to tie to the order, not just to an address. A tracking record showing delivery to the cardholder's address, with a date after the authorization, beats a screenshot of your shipping label. For high-value orders, a signature confirmation closes the argument that the goods never arrived. For digital goods, the access log showing the account used the product after purchase is the equivalent document. No delivery proof, no representment. File the refund instead.

The AVS and CVV result comes second. A full AVS match with a CVV match tells the issuer the cardholder's details were present at the time of the transaction, which undercuts a claim that the card was used without authorization. A mismatch you overrode anyway is evidence against you, so do not include it and hope nobody notices. [AVS codes mean specific things](https://bondproof.com/blog/2026-11-07-avs-codes-decoded.md), and the issuer knows what each one means better than you do.

Device and session data comes third. The IP address, device fingerprint, and session history showing the same device placed earlier legitimate orders, or that the account has a purchase history, is what separates a stolen card from a customer with buyer's remorse. Keep this data for at least 13 months, because that is the window a dispute can arrive in. And the customer's own messages come fourth: their emails asking about shipping, confirming the address, or thanking you, in chronological order, with nothing edited out. A single message where the customer confirms receipt ends most friendly fraud disputes on its own.

## What gets tossed

A screenshot of your refund policy with no proof the customer saw it before purchase. A generic letter stating the transaction was legitimate. A transaction log with no delivery record attached. A terms-of-service page the customer never clicked through. Issuers see these every day, and they lose every day. The other losing move is arguing the wrong reason code: answering a fraud claim with proof of delivery when the dispute is about merchandise not as described. Match the evidence to the code, or do not file.

The other packet that loses is the late one. Representment windows are short, usually 7 to 30 days depending on the network and your acquirer, and a packet filed on day 31 is a donation. Set the alert the day the chargeback lands, not the day someone gets around to it. [The bill after a card testing attack](https://bondproof.com/blog/2026-11-07-after-card-testing-attack-costs.md) includes the chargebacks you never fought because nobody tracked the deadline.

## The math before you fight

Not every chargeback deserves a fight. A $12 dispute with a thin packet costs more in staff time than the refund, and a lost representment still counts against your dispute ratio. Fight where the packet is complete: delivery proof, AVS and CVV match, device history, and the customer's own words. Refund where it is not, and fix the hole the dispute exposed. A merchant who fights everything signals to the acquirer that nothing is being filtered. A merchant who fights only complete packets wins most of them, and the ratio shows it.

## Frequently asked questions

### What is representment?

Representment is the merchant's response to a chargeback: a packet of evidence sent to the issuer through the acquirer, arguing the transaction was legitimate. The issuer reviews the packet and decides whether to reverse the chargeback or let it stand.

### How long do I have to file representment?

Usually 7 to 30 days from the chargeback notification, depending on the card network and your acquirer. The window is short and a late packet is rejected outright, so set the alert the day the chargeback lands.

### Does a full AVS and CVV match guarantee I win?

No, but it is the strongest single piece of evidence against an unauthorized-use claim, because it shows the cardholder's details were present at the transaction. It has to sit alongside delivery proof and device data to carry a case.

### Should I fight every chargeback?

No. Fight where the evidence packet is complete and the amount justifies the time. Refund where the packet is thin, and fix the hole the dispute exposed. Fighting everything with weak packets hurts your dispute ratio more than selective refunds do.

[Get a free bot-traffic audit](mailto:hello@bondproof.com?subject=Free%20free%20bot-traffic%20audit)