Compelling Evidence Guide
Before building evidence packets, ensure you understand:
- Reason codes for your disputes (determines required evidence)
- 3DS authentication data (highest-value evidence for fraud disputes)
- Representment workflow for process and deadlines
- Your current chargeback metrics and win rates
- Evidence strength ranking: 3DS (+40-60% win rate) > Signed delivery (+30-40%) > Prior undisputed txns (+25-35%) > AVS+CVV (+15-25%)
- Visa CE 3.0: 2+ prior undisputed transactions, 120+ days old, matching 2 of 4 elements (IP, device, address, account)
- Mastercard: Include
COMP EVIDin DE 72; need signed receipt, delivery confirmation, or correspondence - Amex: Respond within 20 days (not 30); use Amex portal
- Before building evidence packets: call 5 customers who disputed—understand the root cause
Compelling evidence is documentation that proves the cardholder participated in or benefited from the transaction.
Before you build evidence packets, understand WHY you're losing. Evidence quality matters less than root cause.
Feedback Loop: Talk to Customers First
Pull 5 recent disputes you lost. Call or email the cardholder.
Questions to ask:
- "Walk me through what happened after you placed the order."
- "When did you first think something was wrong?"
- "Did you contact us before disputing?"
What you'll learn:
- If it's descriptor confusion: you have a recognition problem, not an evidence problem (see descriptors and comms)
- If it's shipping delays: you have a fulfillment problem
- If the customer is lying: you have a friendly fraud problem (fight these)
- If the customer genuinely didn't receive value: you have a product/service problem
5 conversations tell you whether you have a representment problem or a root cause problem. Then decide where to invest.
For a month, add delivery photos to 50% of "goods not received" response packets. Track win rate difference. If no improvement, stop doing it. Your time is better spent elsewhere.
Evidence Hierarchy
Not all evidence is equal. Here's the general strength ranking:
| Evidence Type | Strength | Win Rate Impact |
|---|---|---|
| 3D Secure authentication | Strongest | +40-60% |
| Signed delivery confirmation | Strong | +30-40% |
| Prior undisputed transactions | Strong | +25-35% |
| AVS match + CVV match | Medium | +15-25% |
| Customer communication | Medium | +10-20% |
| IP/device match only | Weak | +5-10% |
Mastercard Compelling Evidence
E-commerce / Mail Order / Telephone Order
You need at least one of the following:
| Evidence Type | Description | Documentation |
|---|---|---|
| Signed receipt | Receipt or work order signed by cardholder | Scanned copy with signature visible |
| Delivery confirmation | Written confirmation of electronic delivery registration | Carrier confirmation + registration |
| Correspondence | Email, SMS, or chat with cardholder about the transaction | Full conversation thread with timestamps |
| Pickup confirmation | Merchant statement documenting in-store pickup | Pickup receipt with signature/ID |
| Authenticated follow-on | For partial shipments after authenticated initial transaction | Original auth + subsequent transaction link |
Message text: Include COMP EVID in DE 72
Registered Account Purchases
When your site requires account registration, you can use:
| Evidence Type | Description |
|---|---|
| Purchase history | Other undisputed purchases from same registered account |
| Device/IP match | Transaction from registered device and IP address |
| Delivery proof | Signed proof of delivery to registered address |
| Digital delivery | Email addresses used for digital downloads |
| Product registration | Cardholder registered goods for warranty/updates |
| Usage proof | Evidence disputed goods were used |
| Identity Check | Fully enabled Identity Check used for PAN registration |
This defense does NOT apply to guest checkout purchases. Customer must have created an account before the transaction.
Airline Transactions
You need at least one of:
| Evidence Type | Description |
|---|---|
| Boarding documents | Flight ticket or boarding pass with passenger name |
| Manifest | Flight manifest or itinerary with passenger name |
| Connected charges | Upgrades, baggage fees, in-flight purchases |
| ID linkage | Passenger ID documentation linked to cardholder |
| Loyalty credits | Frequent flyer miles credited for the flight |
| Ticket delivery | Proof of ticket receipt (signed delivery, email confirmation) |
Recurring / Subscription Transactions
For recurring and subscription transactions, you need ALL of these:
- ✅ Description of goods/services provided
- ✅ Start date with:
- Original transaction authorization date
- Authorization approval code
- CIT value (if present)
- ✅ Proof transaction was properly identified as recurring in both authorization and clearing
Gaming Payment Transactions
When cardholder disputes funding but received payouts:
| Required Per Gaming Payment |
|---|
| Date of each Gaming Payment Transaction |
| Switch Serial Number or ARN |
| Transaction amount |
Visa Compelling Evidence 3.0
Visa's CE 3.0 program provides enhanced representment for merchants with customer history.
CE 3.0 Requirements
To qualify:
- Two prior undisputed transactions with same payment credentials
- At least 120 days before the disputed transaction
- Matching data elements - at least two of four:
| Data Element | Description |
|---|---|
| IP Address | Same IP as prior undisputed transactions |
| Device ID | Same device fingerprint |
| Shipping Address | Same shipping address |
| User Account ID | Same customer account |
CE 3.0 Process Flow
CE 3.0 Benefits
- Pre-arbitration liability protection
- Higher win rates (70-85%)
- Faster resolution
- Reduced dispute costs
Standard Visa Compelling Evidence
For disputes not qualifying for CE 3.0:
| Evidence Type | When to Use |
|---|---|
| Signed delivery | Physical goods delivered |
| Access logs | Digital goods accessed |
| Customer correspondence | Email/chat showing acknowledgment |
| AVS/CVV match | Address and CVV verification |
| Prior transactions | Same card, undisputed |
American Express Requirements
Fraud Disputes (F Codes)
| Evidence Type | Effectiveness |
|---|---|
| SafeKey (3DS) authentication | Highest - liability shift |
| Delivery confirmation | High |
| Customer verification records | Medium |
| AVS match documentation | Medium |
Service/Merchandise Disputes (C Codes)
| Evidence Type | Effectiveness |
|---|---|
| Signed service completion | High |
| Delivery with signature | High |
| Terms and conditions accepted | Medium |
| Quality documentation | Medium |
Amex Response Requirements
- Respond within 20 days (not 30 like Visa/MC) - see time frames
- Use Amex merchant portal
- Include Amex case number
- Provide required evidence per reason code
Evidence Quality Standards
Document Requirements
All documentation must be:
- ✅ Legible - Clear and readable
- ✅ Complete - All pages, not truncated
- ✅ Relevant - Specific to disputed transaction
- ✅ Properly identified - With transaction reference
PAN Handling
Per PCI DSS requirements:
- Show only last 4 digits of card number
- Mask full PAN in all documents
- Match visible digits to dispute
Language Requirements
| Network | Requirement |
|---|---|
| Mastercard | English translation for arbitration |
| Visa | English preferred |
| Amex | English required |
Submission Deadlines
| Network | Documentation Window |
|---|---|
| Mastercard | 8 calendar days (10 for ATM/Maestro) |
| Visa | 18 calendar days |
| Amex | 10 calendar days |
Evidence by Dispute Type
Fraud Disputes
| Priority | Evidence |
|---|---|
| 1 | 3D Secure/SafeKey authentication data |
| 2 | AVS + CVV match |
| 3 | Delivery confirmation to verified address |
| 4 | Prior undisputed transactions (same card) |
| 5 | Device fingerprint match |
| 6 | Customer correspondence |
Non-Receipt Disputes
| Priority | Evidence |
|---|---|
| 1 | Signed delivery confirmation |
| 2 | Tracking showing delivered to billing address |
| 3 | Photo proof of delivery |
| 4 | Digital access logs |
| 5 | Download confirmation |
Not-As-Described Disputes
| Priority | Evidence |
|---|---|
| 1 | Product listing as shown to customer |
| 2 | Terms and conditions accepted |
| 3 | Customer communications (pre-sale) |
| 4 | Inspection/return refusal documentation |
| 5 | Quality specifications met |
Credit Not Processed
| Priority | Evidence |
|---|---|
| 1 | Proof credit was issued (with ARN) |
| 2 | Credit pending notification |
| 3 | Terms showing refund not applicable |
| 4 | Return not received |
Common Mistakes
Documentation Errors
| Mistake | Impact |
|---|---|
| Wrong transaction referenced | Automatic loss |
| Illegible copies | Evidence rejected |
| Missing pages | Incomplete case |
| Late submission | Time frame expired |
| No English translation | Rejected at arbitration |
Evidence Gaps
| Gap | How to Fix |
|---|---|
| No delivery proof | Implement tracking + signature |
| No customer communication | Start confirmation emails (see descriptors and comms) |
| No AVS data | Require address verification |
| No login records | Enable access logging (see behavioral analytics) |
Building Your Evidence Collection System
At Transaction Time
Collect and store (per your evidence framework):
- IP address
- Device fingerprint
- AVS/CVV results
- Session data
- Click timestamps
At Order Confirmation
Document:
- Order details email sent
- Confirmation page shown
- Terms acceptance timestamp
- Customer contact info verified
At Fulfillment
Record:
- Shipping carrier + tracking
- Delivery confirmation
- Signature (if applicable)
- Digital delivery logs
Throughout Lifecycle
Maintain:
- Customer communications
- Support tickets
- Login/access history
- Transaction history
Next Steps
Building your evidence system?
- Start with transaction-time collection - IP, device, AVS
- Enable 3DS - Strongest possible evidence
- Implement device fingerprinting - CE 3.0 matching
Improving win rates?
- Talk to customers first - Understand root cause
- Check CE 3.0 eligibility - Higher win rates
- Review by dispute type - Match evidence to reason code
Responding to a specific dispute?
- Check the reason code - Know required evidence
- Review time frames - Don't miss deadlines
- Follow representment process - Step-by-step
See Also
- Mastercard 4837 - Fraud - Mastercard fraud codes
- Visa 10.4 - CNP Fraud - Visa fraud codes
- Time Frames Reference - Response deadlines
- 3D Secure Implementation - Liability shift authentication
- Representment - Fighting chargebacks
- Winning Evidence - What wins disputes
- Chargeback Lifecycle - Full dispute flow
- Device Fingerprinting - CE 3.0 matching
- AVS & CVV - Verification evidence
- Friendly Fraud - First-party abuse
- Chargeback Prevention - Prevention hierarchy
- Network Programs - VAMP ratio protection