Skip to main content

Fighting a Chargeback (Representment)

Representment is the industry word for fighting a chargeback, and this page is whether yours is worth fighting. Looking for what evidence to send or how to present it?

Evidence lives on two pages: What Proof Card Networks Accept is which documents each network wants, and Winning Evidence is how to arrange them for the issuer's analyst.

TL;DR
  • Representment = Your formal response to a chargeback with evidence
  • Win rates depend on reason code and evidence quality
  • Match your evidence to the specific reason code. Generic responses lose
  • Response windows are tight: work to the date on your notice. Your processor can set it earlier than the network's own window. Every network's window

You've got a chargeback and you're deciding whether to fight. Representment's the fight: the formal response you send back through your processor, with evidence attached, asking for the money to be returned. What you send depends on whether it's true fraud or friendly fraud.

Should You Represent?​

Three Checks Before You Fight

This tree's about 3DS and liability shift. Its dollar bands are example routing, not cutoffs. The case is already filed, so the choice is respond or accept it, through the provider's case route. Don't send a separate refund on top. Refund strategy separates the pre-filing refund call from this one.

Is This Worth Your Time?​

Time vs. Money: A Quick Guide

Your time costs money. At an assumed $75/hour, a 30-minute response costs $75 x 0.5 = $37.50. On a $40 chargeback, that leaves just $2.50 before any response fee, even if you win. Use these suggested starting limits, then tune them to your fees and evidence:

  • Under $50: probably not worth it, unless you've got delivery proof ready to upload in under 5 minutes.
  • $50-$150: worth it if you've got the right evidence for the reason code. Spend 15-20 minutes max.
  • $150-$500: Worth up to 30 minutes building the package, when an eligible defense fits the code.
  • Over $500: Worth a thorough response when your evidence answers the code. Budget up to an hour.

Exception: If you see a pattern (same customer, same product, same complaint), document and investigate it. That doesn't mean submitting an unsupported response to every small case. Respond where each case has its own eligible defense.

Getting Started​

Before You Represent​

  1. Analyze the reason code - Understand what's being alleged
  2. Check evidence availability - Do you have what you need?
  3. Calculate win probability - Is it worth the effort?
  4. Check the deadline - Can you respond in time?

Key Resources​

Choose the customer's actual claim before collecting documents.

ResourcePurpose
What proof each network acceptsWhat evidence you need
Time FramesResponse deadlines
Representment WorkflowStep-by-step process

Evidence Requirements by Code Type​

Fraud Chargebacks​

Records to check. There's no universal order of strength:

  1. 3D Secure authentication data
  2. AVS match + delivery to the billing address AVS confirmed
  3. Prior undisputed transactions
  4. Customer correspondence

See: Mastercard 4837 | Visa 10.4

Non-Receipt Chargebacks​

Match the record to what was sold:

  • Physical goods: delivery to the full delivery address. Tracking, a signature and address verification support that; they aren't a universal packet
  • Digital goods: proof the customer actually received or accessed them
  • Services: proof the service was provided
  • Whichever fits: an overlooked credit, an invalid filing, or a withdrawn dispute

See: Visa 13.1

Cancelled Recurring​

Start from the actual complaint, then establish the dates:

  • When the customer cancelled, or your record search, set against the billing dates
  • Consent and the cancellation terms, as context. The code page lists the exceptions in Europe
  • Service use after the customer withdrew permission to bill and before the dispute was processed, with the cancellation date as the last day they were allowed to use it
  • Consent and 'no cancellation found' alone don't answer every 13.2. See the code page for its narrow routes

See: Visa 13.2

Which defenses hold up​

Chargeback TypeWith Good EvidenceWithout Evidence
Fraud (with 3DS/CE 3.0)3DS: whether the payment qualified for the liability shift. CE 3.0: eligibility plus matching purchase history-
Fraud (without 3DS)No authentication doesn't close the case. Other history, correspondence, invalidity and credit grounds can still applyWeak defense
Non-receipt (with tracking)Tracking can show shipment or a delivery status. It doesn't by itself prove receipt at the full address, or who took it inWeak defense
Quality disputesAnswer the actual quality or description allegation with records of what was promised and suppliedWeak defense
Cancelled recurringDepends on cancellation proofWeak defense

Track your own win rate by reason code rather than relying on a general figure.

Common Reasons for Losing​

ReasonPrevention
Missed deadlineCalendar + alerts
Insufficient evidenceEvidence checklist
Wrong evidence for codeMatch evidence to reason code
Poor documentationQuality standards
Invalid chargeback not challengedReview requirements

Network-Specific Guidance​

Mastercard Second Presentment​

  • Mastercard's compelling-evidence route covers eligible non-Maestro card-not-present payments: e-commerce, phone, mail, recurring, installment and airline. Have your acquirer confirm your transaction and system qualify. Your acquirer handles its message fields. Outside Mainland China domestic transactions, its guide puts COMP EVID in DE 72. That domestic route uses a comment field. You don't type either one. See What proof each network accepts

Visa Representment​

  • Your acquirer's initial response runs 30 days (see your notice) from the Dispute Processing Date, with shorter exceptions. Your own deadline is the earlier date in your provider's notice
  • Include all transaction identifiers
  • Reference CE 3.0 when qualifying, against the checklist

Amex Response​

  • 20 days for US merchants direct with Amex. On OptBlue, work to your processor's date
  • Use the response route on your notice: Amex's portal direct, or your processor's case screen
  • Answer inquiries too. On Amex, no reply turns one into a chargeback

How Representment Actually Works​

Knowing what happens on the other end makes your cases better.

The Message Flow​

You (Merchant) → Your Processor → Acquirer → Card Network → Issuer
↓
Issuer Reviews
↓
Decision flows back the same path

How to order the packet​

  1. Identify the payment and the customer's actual claim
  2. Put the records that answer that claim first
  3. Set out the relevant events in date order, and group the supporting records clearly
  4. Check your provider's format and submission deadline

That's preparation advice (Stripe's evidence practices, accessed 4 November 2026), not a published bank workflow. Networks set which grounds count; they don't publish one review order for every bank.

Why Cases Get Rejected​

Rejection ReasonWhat to checkFix
Missing required evidenceCompare the packet with the reason-code checklistAdd the required records
Evidence doesn't address reason codeMatch each record to the actual claimRemove irrelevant material
Unclear or unorganized responseCheck it follows the order aboveAdd a clear summary
Deadlines missedCheck the submitted timestamp and case deadlineTrack deadlines and delivery
Response too long to reviewCheck provider limits and relevanceKeep the packet concise

What to check against each claim​

Reason Code TypeRecords to check first
Fraud (10.4, 4837)3DS data? Device/IP match? Prior transactions?
Not received (13.1)Delivery to the full address, digital receipt, or service provided? Any overlooked credit?
Cancelled recurring (13.2)Cancellation, billing and use dates set side by side? Consent and terms?
Not as described (13.3)Product description at sale? Images? Return policy?

Amex and Discover Quirks​

Amex and Discover don't work like Visa and Mastercard.

American Express​

AspectAmex Difference
Timeline20 days to respond for US merchants direct with Amex; your processor's date on OptBlue
Inquiry processAmex can ask for evidence first (an inquiry) or issue a chargeback straight away
PortalAmex's merchant portal direct, or your processor's route
Reason codesUS and Canada use the letter format (F29, C08). Other countries use a four-digit format
ArbitrationNo such stage; Amex decides after any re-dispute

Amex-specific tips:

  • Respond to inquiries before their reply-by date. No reply and the inquiry becomes a chargeback
  • Use Amex's specific evidence format
  • Note: Amex disputes don't count toward Visa/MC ratios

Discover​

AspectDiscover Difference
TimelineThe reply-by date in your provider's notice
Reason codesLetter or numeric values, by provider. Braintree, for example, reports 4868 replacing UA02/7030 for card-not-present disputes opened from 17 April 2026, with older cases keeping their values. Use the code on your notice and your provider's current mapping
ProcessWork the case route your processor gives you

Work to the reply-by date on your Discover notice. Ask your acquirer (the bank behind your processor) in writing for the rule and submission instructions that apply to that case. Use your provider's code mapping, not an assumption that one format runs across Discover (Braintree's evidence requirements, Important Notice, accessed 4 November 2026).

Discover-specific tips:

  • Match the evidence to the reason code, same as Visa and Mastercard
  • Lower volume means less practice, so don't neglect these
  • Some processors bundle Discover with Visa/MC workflow

Portal Reality: Working with Processor Interfaces​

Your processor's portal is where representment actually happens. Plan around what yours can't do.

Common Portal Problems​

ProblemReality
Clunky uploadFile size limits, format restrictions
Poor status tracking"Pending" doesn't tell you anything
Slow notificationsEmail can lag what's already in the portal
Limited searchHard to find historical cases
No bulk operationsOne case at a time

Working Around Portal Limitations​

LimitationWorkaround
File size limitsCompress images, split documents
Format restrictionsPre-convert to accepted formats
Poor trackingExternal tracking spreadsheet
Slow notificationsCheck portal daily, don't wait for email
No bulkRequest API access if high volume

What to Ask Your Processor​

Ask Your Processor

"What file formats and sizes does your portal accept? Can I get API access for representment? How quickly are status updates reflected?"

High-Volume Considerations​

If you're doing 100+ disputes a month:

  • Request direct API access
  • Consider a representment vendor
  • Build internal tracking systems
  • Don't rely on portal notifications

Next Steps​

  1. Read what proof each network accepts
  2. Review Time Frames
  3. Follow the Representment Workflow
  4. Study reason codes for your most common chargebacks

Something wrong on this page? Email matt at paymentsandrisk.com and say what needs fixing.