Building a chargeback
representment packet
that actually wins

The packet is the argument. Not the phone call your staff had with the customer, not your gut read on whether the dispute is legitimate -- the documents you submit through your acquirer, matched precisely to what the reason code is actually asking the issuing bank to verify. A strong packet built to answer the wrong question loses exactly as often as no packet at all. This picks up where our reason-code reference and chargebacks as a hidden tax left off: not what the codes mean, but what to actually build and send once one lands on your desk.

Start with the deadline, not the evidence

Before assembling anything, confirm two dates: when the notification was issued, and when your response is due. Both major networks set a firm response window, and it runs from the date the chargeback was issued to your acquirer -- not the date someone on your team actually opens the notification. Mastercard's documented first-chargeback response deadline is 45 days. Visa's timelines vary by dispute category and workflow (allocation disputes under Fraud and Authorization move faster than the "collaboration" workflow for Processing Errors and Consumer Disputes), but a 30-day merchant response window is the figure most consistently cited across chargeback-management vendor documentation reviewing Visa's published rules. Missing the deadline is an automatic loss regardless of how strong the underlying evidence is -- a representment packet that arrives one day late is not read.

Fraud codes: prove the transaction was authenticated, not that the customer is lying

Visa 10.4 (Other Fraud: Card-Absent Environment) and Mastercard 4837 (No Cardholder Authorization) are both framed around the same question: was this specific transaction actually authorized by the legitimate cardholder? The packet doesn't need to prove the customer is being dishonest -- it needs to prove the transaction cleared the checks that a fraudulent one typically wouldn't.

• AVS and CVV match results from the original authorization, showing the billing address and security code matched what the issuer had on file.
• 3-D Secure authentication data if the transaction ran through it -- a successful 3DS challenge shifts a meaningful share of fraud liability to the issuer under current network rules, which is often enough to close a 10.4 or 4837 dispute outright. (See 3-D Secure: liability shift vs conversion cost for when this trade-off is worth the checkout friction.)
• Device and IP history showing the order came from a device or location consistent with the cardholder's prior undisputed orders, if your gateway captures it.
• Order history demonstrating the same card, name, or account has multiple prior undisputed purchases -- weak evidence alone, but useful alongside AVS/CVV and 3DS data.

What doesn't belong in a fraud-code packet: your return policy, delivery tracking, or a note that "the customer seemed satisfied." None of it answers whether the transaction was authorized, which is the only question a fraud-category dispute is actually asking.

Consumer-dispute codes: prove fulfillment or a disclosed policy, not authentication

Visa 13.1 (Merchandise/Services Not Received), 13.7 (Cancelled Merchandise/Services), and Mastercard 4853 (Cardholder Dispute, Mastercard's broad non-fraud catch-all) run on the opposite logic. The issuer already isn't disputing that the cardholder made the purchase -- the dispute is about whether the merchant delivered what was promised, or handled a cancellation the way the cardholder agreed to at purchase.

Code	Network	What it's disputing	Winning evidence
13.1	Visa	Goods or services never arrived	Tracking number with delivery confirmation, signed proof of delivery, or a valid future delivery date still within terms
13.7	Visa	Cancelled purchase, credit never issued (or claimed not to be)	Refund transaction ID, amount, and post date; or the cancellation policy the cardholder agreed to plus proof it wasn't met (e.g. cancelled after the deadline)
4853	Mastercard	Broad: not-as-described, non-receipt, unprocessed credit, recurring billing dispute	Depends on the specific sub-reason listed on the notice -- itemized product description, delivery confirmation, or refund evidence matching the actual complaint

13.7 specifically is worth building a standing template for: it's the code that fires whenever a subscription cancellation or return doesn't line up with the cardholder's expectation of when a refund should post. The single most common losing mistake here is sending proof the original sale happened -- that was never in dispute. The packet needs to show the refund or credit either was issued (with the transaction ID and date) or wasn't owed under the terms the cardholder agreed to.

The code is the question. Answer it directly, with the specific document type it's asking for, or the packet doesn't get read as a rebuttal -- it gets read as evidence you misunderstood the dispute.

On "4517" and unfamiliar codes

Visa's live reason codes, in place since the April 2018 Visa Claims Resolution rollout, follow a two-digit-dot-one-digit format: 10.4, 13.1, 13.7, and so on. Mastercard's codes are four digits beginning with 48, like 4837 or 4853. A code formatted as "4517" doesn't match either network's current documented numbering convention, and neither network's published reason-code references list it as of 2026. If a real notice cites a code that doesn't look like either pattern, the first move is confirming the exact code and category with your acquirer or processor directly -- portals and statement descriptors occasionally truncate or reformat codes, and building a representment packet around a misread code wastes the response window on the wrong evidence.

What to build before a dispute ever lands

The fastest representment packets are assembled from records that already exist, not scrambled together after a notification arrives. Three habits shorten every future response:

1. Keep AVS/CVV and 3DS results attached to the order record, not buried in a payment gateway log that requires a support ticket to retrieve.
2. Log refunds with a timestamp and transaction ID the moment they're issued -- this single habit is what wins most 13.7 and 4853 non-receipt-of-credit disputes.
3. Write down the cancellation and refund policy the customer actually agreed to, and keep proof of where and when they agreed to it (checkout screen, signed agreement, emailed terms). A policy that exists only in an employee's head doesn't count as evidence.

Frequently asked questions

What is a chargeback representment packet?

A representment packet is the evidence a merchant submits through their acquirer to dispute a chargeback -- effectively re-presenting the transaction to the issuing bank with proof the charge was legitimate or the dispute's underlying claim doesn't hold up. What belongs in it depends entirely on the reason code: fraud codes need authentication evidence, consumer-dispute codes need fulfillment evidence, and mismatching the two is the single most common reason a winnable packet loses.

What does Visa reason code 13.7 mean and what evidence beats it?

Visa 13.7 (Cancelled Merchandise/Services) covers disputes where the cardholder returned goods or cancelled a subscription but says they never received the promised credit. The winning evidence is proof the credit was actually issued -- a refund transaction ID, the date it posted, and the amount -- or, if no credit is owed, the cancellation policy the cardholder agreed to and proof it wasn't followed.

Is 4517 a real Visa or Mastercard chargeback reason code?

No. Visa's current codes follow a two-digit-dot-one-digit format like 10.4 or 13.1, and Mastercard's are four digits starting with 48, such as 4837 or 4853. "4517" doesn't match either pattern and isn't documented in either network's published references as of 2026. Confirm the exact code with your acquirer before building evidence around an unfamiliar one.

How long does a merchant have to respond to a chargeback?

Mastercard gives the acquirer and merchant 45 days to respond to a first chargeback. Visa's timelines vary by dispute category, but 30 days is the commonly cited merchant response window. Cardholders get up to roughly 120 days from the transaction or expected delivery date to file the original dispute.