Winning Evidence
The evidence lists below assume you shipped a package or logged a digital session. Looking for the service business version?
If you performed work instead, a repair or a haircut or a consulting job, your proof is the signed work order and the photos rather than a tracking number.
- Issuer analysts work from the reason code's requirements. Organize the response so the matching record is the first thing they see
- Submit evidence about that transaction, not a boilerplate terms-of-service PDF
- Visa CE 3.0 can answer a 10.4 fraud dispute with qualifying earlier purchase history. The dates, matching data and description rules live on the CE 3.0 checklist. Collecting that data at transaction time is the strategy
- Keep the packet short, relevant and legible. A few specific pieces that answer the claim are easier to work with than a long undifferentiated dump
This page is how to think about evidence: what issuers actually look at, how to organize a response, and what people get wrong. What proof each network accepts is the reference checklist: what evidence each network requires, CE 3.0 specs, submission deadlines, and format standards. Read this one first, then work off that one when you're actually building a response.
Responses lose when merchants submit the wrong evidence. You're not arguing with a jury. You're arguing with an issuer analyst who's checking your packet against the claim, fast.
The difference is knowing what issuers actually look for. Track your own win rate by reason code.
What Matters
- Issuers check against the claim. Match your records to the code's requirements. That's the game.
- Transaction-specific evidence beats boilerplate. Your TOS doesn't prove this customer got this product.
- Visa CE 3.0 can answer a fraud dispute with purchase history. Only if you've got the right data. Ask your processor separately how a qualifying case counts toward your VAMP ratio.
- Less is more. Keep it concise, relevant and transaction-specific, inside your provider's upload limits.
- Timing matters. Usage after the dispute date answers a never-received claim head-on. It shows the account kept being used.
Evidence by Dispute Type
What Issuers Look For
Run the case against its own code first. Network reason codes set the admissible grounds, and each code asks for evidence that answers its claim. See the Visa and Mastercard lists. Evidence that answers a different claim earns nothing.
Fraud Claims: Visa 10.4, card-not-present
Customer claims they didn't authorize the transaction. This could be true fraud or friendly fraud. This section is 10.4 only. Visa 10.1 to 10.3 are EMV and card-present claims with their own conditions. Check the exact code and channel on your notice before you collect anything. The history, IP, device and CE 3.0 records below belong to the 10.4 route, under its qualifying conditions.
Records to check for your response ground:
- Device fingerprint matches prior purchases
- IP address matches cardholder location
- Shipping address matches the billing address, and the AVS result matches the address the bank has on file. They're different checks, so send both results
- Prior successful transactions on same card
- Customer login after purchase date. Login and IP records support a case; on their own they don't prove the cardholder authorized the sale
- Customer communication acknowledging purchase
Not helpful:
- Signed TOS (proves nothing about this transaction)
- Generic fraud prevention description
- Generic security claims
Not received: Visa 13.1
Customer claims the merchandise or service wasn't received. Category 13 is not one claim: 13.2 is cancelled recurring, 13.3 is not as described or defective, 13.7 is cancelled merchandise or services, and 13.8 and 13.9 cover credit and cash cases. Keep each claim with its own response ground.
Records to check for your response ground:
- Delivery to the full delivery address on the order. A carrier scan or signature supports it; neither is universally required, and neither settles it alone
- For digital goods, proof of actual receipt or access. For services, proof the service was provided
- Photos of product as shipped, as support only. They don't show it arrived
- Customer communication confirming receipt
- Customer usage logs after delivery
- Or the other answers the code allows: an overlooked credit, an invalid filing, or a withdrawn dispute
Not helpful:
- Generic shipping policies
- Average delivery times
- "Most customers are satisfied" claims
Cancelled recurring: Visa 13.2 (13.7 is cancelled merchandise or services)
Customer claims they cancelled or didn't authorize recurring billing.
Records to check for your response ground:
- The actual cancellation, billing and service-use dates set side by side, against 13.2's response routes. Those routes have exceptions in Europe where the bank advised the account was closed, facilities were withdrawn or the customer had died
- Consent and the terms agreed at signup, as context. Consent alone doesn't answer a later cancellation
- Renewal notification emails, with delivery proof, as support only. They don't make a charge after cancellation valid
- 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. An empty support inbox, signup consent or a later login alone doesn't establish a valid charge
Not helpful:
- Pointing to cancellation policy they didn't follow
- "They should have cancelled properly"
- Generic subscription terms
Visa Compelling Evidence 3.0
For the full CE 3.0 requirements, eligibility criteria, and implementation details, see Compelling Evidence: Visa CE 3.0. What's here is strategy: when CE 3.0 actually moves your win rate.
CE 3.0 is Visa's route for answering a 10.4 fraud dispute with the customer's earlier purchase history. Its requirements are on the checklist. Work off the full checklist.
The strategy point is collection. You can't invent last year's device and IP records when a dispute lands. Log them at purchase time, and ask your processor what qualifying history it can supply before you rule CE 3.0 out. Ask your processor how a qualifying case counts toward your VAMP ratio.
"Are we collecting and storing device fingerprints and IP addresses in a way that supports CE 3.0 submission? Can we query prior transactions for matching data elements?"
For the operational strategy (when and how to collect CE 3.0 data throughout the transaction lifecycle), see Defending Against Fraud Losses.
Digital Goods Evidence
Digital goods are harder to prove because there's no physical delivery. See digital goods fraud risks for prevention strategies.
What Works for Digital
| Evidence Type | Why It Helps |
|---|---|
| IP at purchase | Links transaction to location |
| IP at usage | Shows access after purchase |
| Account login timestamps | Shows ongoing usage |
| In-app activity logs | Shows the account used the product |
| Download records | Shows delivery to a device |
| License key activation | Ties specific purchase to usage |
| Streaming/viewing history | Shows content was watched on the account |
Digital Evidence Package
For digital goods disputes, compile:
- Purchase timestamp and IP
- Account creation date (if before dispute)
- Login timestamps after purchase
- Usage activity (features used, content accessed)
- Download or activation records
- Any customer support tickets (especially ones acknowledging the product works)
Evidence Organization
How you present evidence matters. So does what you present.
Format Guidelines
| Do | Don't |
|---|---|
| The format your processor's upload accepts, clearly labeled | Loose attachments with no summary |
| Page numbers and sections | Wall of text |
| Key evidence on first page | Bury important items |
| Highlighted relevant sections | Raw log dumps |
| Clear timestamps | Ambiguous dates |
Ideal Response Structure
Page 1: Summary
- Transaction details (date, amount, last 4)
- Customer details (name, address, email)
- 2-3 sentence summary of why this should be reversed
Page 2-3: Key Evidence
- The strongest pieces proving your case
- Screenshots with timestamps
- Highlighted delivery confirmation
Page 4+: Supporting Documentation
- Full logs if needed
- Complete communication history
- Policies (only if directly relevant)
What Wastes Analyst Time
- 30+ page responses
- Unformatted server logs
- Irrelevant company history
- Emotional appeals
- Legal threats
- Screenshots of your TOS homepage
Inquiry Deflection
Some cases start as an inquiry before they become a chargeback. Stripe's dispute guide describes Amex, Discover and Mexico-domestic inquiries separately from the usual Visa and Mastercard flow (accessed 4 November 2026).
Inquiry vs. Chargeback
Amex has no pre-arbitration or arbitration. After representment, it can reinvestigate a cardholder re-dispute and ask you for more information, then decides. The last two rows below don't apply to Amex. See Time Frames.
| Stage | What It Is | Your Opportunity |
|---|---|---|
| Inquiry | Issuer asking for information | Resolve here, no chargeback filed |
| First chargeback | Formal dispute filed | Respond through the provider to contest it. Some cases change without a new evidence packet: an existing credit, an invalid filing, or an automatic protection |
| Pre-arbitration | Second review, where the network and code provide one | Higher stakes. Who can open it, what can be added and its deadline depend on the network, the transaction and the stage |
| Arbitration | Network decides | Fees dwarf a low-value dispute |
Deflecting at Inquiry
If you can resolve at the inquiry stage:
- No formal chargeback is filed on that case. A fraud report already made isn't removed, and how it counts follows the network's program rules
- Whether there's a fee depends on your provider, so check its schedule. A deflection product or service can carry its own
- Whether it costs less overall is your arithmetic: product fees and pass-through terms against the chargeback cost avoided. The full cost stack is in what a chargeback costs
Two different things get called deflection:
- Sharing purchase details through issuers. Visa Order Insight and Ethoca Consumer Clarity pass rich transaction data (product details, images, tracking) to participating issuers (both read 4 November 2026). Reach depends on issuer participation and your integration. How they fit with alerts
- Answering a formal inquiry. That happens in your provider's case, by the date on the notice
For a formal inquiry:
- Respond well before the date on the request. On Amex, no reply turns an inquiry into a chargeback. On Discover, no reply can become a chargeback you can't fight (Stripe's dispute guide)
- For a clear loss at inquiry stage, check which state the payment is in before refunding. A partial refund can still escalate
Evidence Templates: Use Carefully
Prefer transaction-specific evidence over boilerplate. A template can hold your structure; the facts in it have to be this sale's.
What Templates Can't Do
- Prove this specific customer received this specific product
- Show device or IP matching
- Demonstrate customer usage
- Provide unique transaction details
When Templates Help
Templates are useful for:
- Consistent formatting
- Reminder checklists (what evidence to gather)
- Standard policy language (as supplement, not substitute)
Building Useful Templates
Instead of boilerplate responses, build evidence checklists by reason code:
| Reason Code | Evidence Checklist |
|---|---|
| 10.4 (Card-not-present fraud) | □ 3DS data □ Device fingerprint □ IP match □ Prior transactions □ AVS match |
| 13.1 (Not received) | □ Delivery to the full address, or digital receipt, or service provided □ Tracking and carrier record □ Any overlooked credit |
| 13.2 (Cancelled recurring) | □ Cancellation date □ Billing dates □ Service-use dates □ Consent and terms □ The Europe exceptions on 13.2 |
| 13.3 (Not as described) | □ Product description at sale □ Images of what was supplied □ Correspondence on the actual defect alleged □ Return record where one applies |
Use this checklist before responding. It's a collection aid, not a verdict. A missing pictured document doesn't doom a case that has another valid answer, such as an overlooked credit or an invalid filing.
Template Dos and Don'ts
| Do | Don't |
|---|---|
| Use templates for document formatting | Copy-paste the same letter for every dispute |
| Include evidence collection reminders | Submit generic "we have a fraud prevention system" |
| Standardize header/transaction info | Skip transaction-specific details |
| Create reason-code-specific structures | Use one template for all reason codes |
Evidence Assembly Workflow
- Receive chargeback notification
- Check reason code → pull corresponding checklist
- Gather evidence from each checklist item
- Identify gaps → decide whether to accept this open case or respond
- Assemble package in standard format
- Submit with summary highlighting strongest evidence
Gather the evidence first, then use a template to format it. Don't let the template decide what goes in.
Test to Run
30-day evidence improvement audit:
Week 1: Baseline
- Pull win rate by reason code for past 90 days
- Review 10 lost disputes for evidence gaps
- Identify most common reason codes
Week 2-3: Improve
- Create evidence checklist by reason code
- Verify CE 3.0 data is being collected
- Train team on new evidence standards
Week 4: Measure
- Compare win rate to baseline
- Identify remaining gaps
Success criteria: Compare win rates on the same reason codes, with the same follow-up time for outcomes to land. A short window with a different case mix won't tell you anything.
Scale Callout
| Volume | Focus |
|---|---|
| Under $100k/mo | Manual evidence collection. Focus on top 2-3 reason codes. Don't over-invest in low-volume disputes. |
| $100k-$1M/mo | Standardized evidence packages. CE 3.0 data collection. Track win rates by reason code. |
| Over $1M/mo | Automated evidence assembly. Dedicated representment team or vendor. Real-time win rate optimization. |
Where This Breaks
-
True fraud. If the transaction really was fraudulent, the cardholder's the victim. Responsibility can still turn on an eligible fraud-liability shift, an invalid chargeback, or a credit already processed. Check those before you write the case off. If none applies, take the loss.
-
Service failures. A missed service alone doesn't settle it. A credit, an invalid filing or a withdrawal can still answer the chargeback, so check those first. If it's valid and no answer is left, accept it through your provider and reconcile any credit already given, so the customer isn't paid twice. Then fix the problem.
-
Friendly fraud with thin data. Device fingerprints, IPs and usage logs matter most on the card-not-present history routes. Other cases can rest on signatures, receipt records or correspondence. Collect the data your codes actually ask for; device and IP history isn't a universal entry ticket.
Analyst Layer: Metrics to Track
| Metric | What It Tells You | Target |
|---|---|---|
| Overall win rate | Representment effectiveness | Compare with your own baseline |
| Win rate by reason code | Where to focus | Varies by code |
| Response time | Receipt to decision and any submission | Set an internal target before each notice deadline; investigate late cases separately |
| CE 3.0 qualification rate | Data collection health | Track it, and why cases fail |
| Evidence completeness score | Process quality | Internal benchmark |
Track your own win rate by reason code.
Evidence to Check by Reason Code
| Reason Code Category | Evidence to Check |
|---|---|
| Fraud (10.4, card-not-present) | Device and IP matches, prior transactions, customer usage, under that route's conditions |
| No merchandise (13.1) | Delivery to the full address, digital receipt, or service provided |
| Not as described (13.3) | Product description at sale, images, correspondence |
| Cancelled recurring (13.2) | Cancellation, billing and service-use dates, with consent and terms as context |
| Cancelled merchandise or services (13.7) | The disclosed policy and whether the customer followed it, or the code's other routes |
Review lost cases for evidence gaps and process problems. For win rate in the context of overall chargeback metrics and when to stop fighting specific reason codes, see Chargeback Metrics: Win Rate.
Next Steps
Just getting started with representment?
- Review the representment workflow → Step-by-step response process
- Pull your last 10 chargebacks → What evidence did you have? What was missing?
- Implement device fingerprinting and IP logging → Start collecting CE 3.0 data now
Improving your win rate?
- Segment by reason code → Focus on codes where you have evidence advantage
- Build evidence templates by reason code → Standardize your response packages
- Set up evidence collection at transaction time → Capture records as they happen and keep their timestamps. After a dispute you can still retrieve what exists and collect genuine later communications, labeled with when they arose. Never back-fill or backdate a missing log
Already fighting chargebacks?
- Track win rates by reason code → Find your weak spots
- Review lost cases → What evidence would have won?
- Prevent chargebacks first → Weigh prevention against representment on your own eligibility, added cost, recoverable amounts and mature outcomes. Neither wins every time
Related Pages
- Representment - Fighting chargebacks
- Compelling Evidence - Detailed evidence guide
- Chargeback Lifecycle - Full dispute flow
- Fraud vs. Friendly Fraud - Classification
- Chargeback Ratio Crisis - Crisis response
- Chargeback Prevention - Prevention hierarchy
- Device Fingerprinting - CE 3.0 matching
- What is the customer actually claiming? - Match the notice before arranging the evidence
- Time Frames - Response deadlines
- Network Programs - How cases count toward VAMP
- Chargeback Vendors - Representment services
- Chargeback Metrics - Win rate tracking
- Representment for Service Businesses - Evidence strategies for contractors, consultants, salons, and repair shops