What Proof Card Networks Accept (Compelling Evidence)
- Match evidence to the claim: use the reason code, not a universal strength ranking
- Visa CE 3.0: for Visa 10.4 fraud disputes, check the earlier purchases, dates and matching data below
- Mastercard: gather records that answer the reason code; have your acquirer (the bank behind your processor) confirm the submission route
- Amex US direct merchants: Amex's guide gives 20 days to answer an inquiry or chargeback. Through a processor, use its case deadline. NETWORK Amex guide
- Before you build a packet, talk to a few customers who disputed. It can show you the root cause
- From disputes processed on 24 October 2026, those earlier purchases can be at other shops, not just yours. Ask your processor if it supports that
This page is the reference checklist: what evidence each network requires, CE 3.0 specs, submission deadlines, and format standards. Winning Evidence is how to think about it: what issuers actually look at, how to organize a response, and what people get wrong. That one's strategy, this one's the checklist.
You've got a chargeback to answer. The proof you send back, your compelling evidence, has to match what the customer claims. Mastercard's merchant guidance says to address the reason code. NETWORK Mastercard's merchant FAQ.
Before you build evidence packets, investigate WHY you're losing. Use the records and the customer's account together.
Feedback Loop: Talk to Customers First
For a small investigation, try 5 recent disputes you lost. Call or email the cardholder. That number is a starting point, not a validated sample size.
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 to investigate:
- Billing descriptor confusion: check for a recognition problem (see descriptors and comms)
- Shipping delays: check fulfillment records
- A claim your records contradict: investigate possible friendly fraud before deciding to fight
- A customer who didn't receive the promised value: review the product or service
Use those conversations to form a hypothesis. Check it against your records before deciding where to invest.
Example test design: for a month, add delivery photos to a randomly chosen 50% of eligible "goods not received" packets. Keep the reason code and other evidence comparable. Track outcomes and packet counts. A small or uneven sample won't establish whether photos help.
Evidence to Check
Match evidence to the reason. These are records to check, not a strength ranking.
| Evidence Type | What to Check |
|---|---|
| 3D Secure authentication | Whether the payment and fraud claim qualify for the liability shift |
| Signed delivery confirmation | Recipient, address and delivery date |
| Prior undisputed transactions | Whether the history meets the route's eligibility rules |
| AVS match + CVV match | Verification results for the disputed payment |
| Customer communication | Relevant messages about the purchase |
| IP/device match | How the record links the purchase to the customer |
Stripe says 3DS authentication doesn't guarantee liability shift for a particular payment or dispute. VENDOR Stripe's 3DS guide. Track your own win rate by reason code.
- Carrier signature: save the signature record with the tracking details
- Photo proof of delivery: save the photo and its delivery details separately from any signature
- Carrier delivery confirmation without signature: save the status, address and timestamp; label it as unsigned
- For high-value items: consider signature confirmation as a shipping control, without treating it as a dispute guarantee
For Stripe merchandise disputes, its guide asks for shipment and delivery records with the full delivery address. VENDOR Stripe's evidence guide.
Mastercard Compelling Evidence
E-commerce / Mail Order / Telephone Order
Mastercard's merchant FAQ says the evidence should answer the reason code. These are collection prompts, not a complete eligibility checklist. Have your acquirer confirm the current route. NETWORK Mastercard's merchant FAQ.
| Evidence Type | What to Pull |
|---|---|
| Signed receipt | Receipt or work order connecting receipt of the goods or services to the cardholder |
| Electronic-delivery registration | The customer's written registration confirmation, rather than a carrier tracking page |
| Correspondence | Relevant email, SMS or chat about participation in the purchase |
| Pickup confirmation | Pickup record and any signature you collected |
| Authenticated follow-on | Initial payment and linked shipment records for the acquirer to assess |
Message text: This Dual Message route covers eligible non-Maestro transactions. The 13 May 2025 guide puts COMP EVID in DE 72 for it outside Mainland China domestic transactions. That domestic route uses a comment field. Your acquirer handles these fields, and confirms the system, the transaction's eligibility and the Mainland China exception. Where this route doesn't apply, the other responses below still stand. NETWORK Mastercard guide, pp. 425 to 428.
Registered Account Purchases
Pull registration and authentication records with the order history. Also check linked device records and evidence that the goods or services were used. These are collection prompts for the guide's registered-account route. Account creation alone isn't enough; have your acquirer confirm the required packet. NETWORK Mastercard guide, p. 427.
The guide excludes guest purchases from this registered-account defense. That doesn't exclude every other response to a guest-checkout dispute.
Airline Transactions
Pull the booking, passenger and travel records. Ask your acquirer which documents connect the passenger to the cardholder for this claim.
Recurring / Subscription Transactions
For recurring and subscription transactions, pull the agreement, start date, initial authorization and recurring-payment records. Have the acquirer check the applicable route before submission.
Gaming Payment Transactions
Keep the disputed funding and payout records linked. The guide's gaming route concerns later, undisputed gaming credits; a payout alone isn't a defense. NETWORK Mastercard guide, p. 429.
Visa Compelling Evidence 3.0
Visa's CE 3.0 rules use the customer's earlier purchases to answer a Visa 10.4 fraud dispute. Qualifying history can support an invalid-dispute condition or a pre-arbitration response. Have your processor verify eligibility and outcome. NETWORK Visa public rules, 24 October 2026 edition, sections 11.8.5.3 and 11.8.5.6. Ask separately how the case counts toward your VAMP ratio.
CE 3.0 Requirements
Visa's 24 October 2026 public rules set the requirements for the purchase-history route below. They carry dated versions of it, so use the one that covers your dispute's processing date:
- Two earlier purchases on the same card or its token, neither reported to Visa as fraud by the issuer. A past non-fraud dispute doesn't rule one out. Ask your processor to check the fraud-report timing for the stage you're using.
- Each processed more than 120 days and no more than 365 days before the dispute, measured from the dispute, not from the disputed purchase. On the invalid-dispute route, an earlier Original Credit Transaction doesn't have to clear the 120-day lower limit. The pre-arbitration version from 24 October 2026 doesn't carry that exception, so have your acquirer pick the stage and its dated version before you rely on it. From disputes processed on 24 October 2026, those purchases can be at other shops, subject to the route's limits. NETWORK Visa public rules.
- Matching data elements: at least two of four, and one must be IP Address or Device ID/fingerprint:
| Data Element | Description | Required? |
|---|---|---|
| IP Address | Same public IP as the earlier purchases | At least one of these two is mandatory |
| Device ID/fingerprint | Same device ID or fingerprint; these count as one element | At least one of IP or device is mandatory |
| Full delivery address | Same full shipping address, street to country | Optional (can't be the only two matches) |
| Customer account or login ID | Same login the customer signs in with. That includes the login of an AI shopping agent the customer bought through (an agentic payment provider) | Optional (can't be the only two matches) |
Shipping address plus account ID alone won't qualify. One match must be IP or device. Device ID and device fingerprint count as one element, so you need another match.
Collect the data in the form Visa accepts:
- IP address: the customer's public IP, not hashed
- Device ID: an identifier the customer can verify, such as a serial number or IMEI, at least 15 characters, not hashed
- Device fingerprint: built from at least two device properties, such as browser and operating system versions, at least 20 characters; it can be hashed
- Account or login ID: the ID the customer signs in with, readable by them, not hashed. An agentic payment provider's login counts here
- Full delivery address: the customer's full shipping address, street to country, not hashed. Don't substitute a billing address
Also required: a description of what was bought, for the disputed purchase and both earlier ones. On the invalid-dispute route, a purchase order number sent to the customer can stand in for that description, but only on e-commerce payments carrying ECI 7 with a valid Visa Secure CAVV, a valid Visa Token Service TAVV, or a valid Visa IDX match key. Those are authentication fields your processor can see. A field being present doesn't make it valid. Ask whether this payment carries a valid one. Don't assume the purchase-order swap travels to every stage. Ask your processor which route you're on.
NETWORK Visa public rules, 24 October 2026 edition, section 11.8.5.3, Table 11-29, and section 11.8.5.6, Table 11-32. These are network criteria; your processor's implementation can differ. For example, Stripe's CE 3.0 API guide describes its own date and evidence checks. VENDOR
Can other shops' purchase history help?
Yes, for Visa 10.4 disputes processed on or after 24 October 2026, subject to the route's limits. The rule text now says the same card, or a payment credential linked to it such as a token, was used at one or more merchants for the two earlier purchases. Don't read more into that than it says. It doesn't tell you what your processor can pull or submit. The invalid-dispute extension doesn't apply in Chile. Both the invalid-dispute and pre-arbitration routes carry the newer wording. Through 23 October 2026, the provision ran on the same payment credential without that at-one-or-more-merchants wording.
One limit matters in pre-arbitration: your acquirer can only submit transaction data it accepted and processed. History at a shop on a different acquirer won't come through that route. You also need a description of each purchase, the disputed one and the two earlier ones.
Ask your processor: "Can you use history from other merchants for this dispute? Which stage, records and date checks apply?" If it can't support that route, follow its ordinary evidence instructions.
NETWORK Visa public rules, 24 October 2026 edition, sections 11.8.5.3 and 11.8.5.6. Edition and access date are in Sources.
If that history route isn't available
Keep your own order records; leave cross-shop matching to your processor. Use the ordinary evidence checklist when that history route is unavailable.
Visa RC 83 belongs to the Visa decline-code reference: it's an authorization response, not a chargeback reason. Ask your processor which payment attempt produced the code. It isn't a reason to submit CE 3.0 evidence.
CE 3.0 Process Flow
CE 3.0 Benefits
- Qualifying history can support an invalid-dispute condition or a pre-arbitration response
- Ask your processor to confirm eligibility and the outcome for your case
Two Other 10.4 Invalid Conditions Worth Asking About
These aren't CE 3.0. They're separate ways a Visa 10.4 dispute can be invalid in the same table. Ask your processor or acquirer to check them against the authorization and dispute records.
- The security code didn't match, and the sale went through anyway. A 10.4 dispute is invalid when the CVV2 was present, its result came back N (no match), and the authorization was still approved.
- A serial disputer. A 10.4 dispute is invalid on a payment credential the issuer has already disputed more than 35 times in the previous 120 calendar days. For disputes processed on or after 24 October 2026, that count runs per payment credential. That's the card or a linked token. Through 23 October 2026, it ran per account number. In Brazil, the rule doesn't apply to a domestic installment payment, and the limit counts by the original authorization. Separate clearings of one authorization count as one only when they carry a multiple-clearing sequence number.
NETWORK Visa public rules, 24 October 2026 edition, section 11.8.5.3, Table 11-29.
Standard Visa Compelling Evidence
For disputes not qualifying for CE 3.0, choose records that answer the reason code. Stripe's reason-code guide offers these kinds of evidence; this isn't a separate Visa eligibility test. VENDOR Stripe's guide.
| Evidence Type | What to Check |
|---|---|
| Signed delivery | Recipient and delivery details for physical goods |
| Access logs | Use or download of the digital product, linked to the customer |
| Customer correspondence | Relevant acknowledgment of the purchase |
| AVS/CVV match | Verification results for the payment. A match isn't proof the buyer owned the card |
| Prior transactions | Whether the history supports this particular response |
American Express Requirements
Fraud Disputes (F Codes)
Use the exact fraud code. Amex's US guide lists code-specific response options, rather than an effectiveness ranking. NETWORK Amex US guide.
| Evidence Type | What to Check |
|---|---|
| SafeKey (3DS) authentication | Ask whether this payment and fraud claim qualify for liability shift |
| Delivery confirmation | Recipient and address, tied to the disputed purchase |
| Customer verification records | What the payment and account records actually establish |
| AVS documentation | Address result and where the goods went |
Service/Merchandise Disputes (C Codes)
| Evidence Type | What to Check |
|---|---|
| Signed service completion | What work the customer acknowledged |
| Delivery with signature | What the delivery record shows |
| Terms and conditions accepted | The relevant terms and acceptance record |
| Quality documentation | The listing, condition and response to the specific complaint |
Amex Response Requirements
- Amex US direct merchants: its guide gives 20 days to answer an inquiry or chargeback. Through a processor, use the case deadline it gives you. NETWORK Amex US guide
- Use the response route on the notice. Amex's guide offers online submission, fax or mail
- Include the case and merchant account identifiers requested
- Provide evidence for the specific reason code
Evidence Quality Standards
Document Requirements
Use this preparation checklist:
- ✅ Legible - Clear and readable
- ✅ Complete - Enough context to understand the record
- ✅ Relevant - Specific to the disputed transaction and claim
- ✅ Properly identified - With the transaction reference
Stripe asks for readable, relevant evidence and focused excerpts rather than entire policies or long email chains. VENDOR Stripe's evidence guide.
PAN Handling
PCI DSS's display rule isn't "last four only." Requirement 3.4.1 limits routine display to the BIN and last four digits, with more restricted to personnel with a legitimate business need. PCI SSC distinguishes masking a display from protecting stored card data. NETWORK PCI SSC FAQ 1492.
For an evidence packet, use the processor's transaction reference and masked card details. Check that they match the dispute. Send any requested card data through its approved route.
Language Requirements
Confirm the language and translation requirements for the case stage with your acquirer. Mastercard's 13 May 2025 guide distinguishes shared-language cases and Brazil domestic arbitration from other arbitration cases. It isn't a universal "English at every stage" rule. NETWORK Mastercard guide, pp. 45 to 46.
For Visa disputes processed in VROL, network members must provide documents in English or with an English translation. Ask your acquirer what it needs from you. NETWORK Visa public rules, section 11.3.1.
For Amex cases, ask: "Which documents need translating, into which language, and by what deadline?"
Submission Deadlines
Use the reply-by date on your case. A network-to-acquirer processing window isn't automatically the time you have to send documents. Ask: "When must you receive my complete packet, and when does the network clock start?"
| Route | Published Merchant Response Guidance |
|---|---|
| Stripe | Usually 7 to 21 days, depending on the network; use the case deadline. VENDOR Stripe's response guide |
| Amex US direct merchants | 20 days for an inquiry or chargeback in its US guide. NETWORK Amex US guide |
| Other processors/acquirers | Get the reply-by date and submission route from the notice or provider |
See Time Frames for the stage-by-stage reference.
Evidence by Dispute Type
Fraud Disputes
These are collection prompts, without a universal priority order. Match them to the reason code. VENDOR Stripe's reason-code guide.
| Record to Check | Evidence |
|---|---|
| Authentication | 3D Secure/SafeKey authentication data |
| Verification | AVS + CVV match |
| Delivery | Delivery confirmation to verified address |
| History | Prior undisputed transactions (same card) |
| Device | Device fingerprint match |
| Communications | Customer correspondence |
Non-Receipt Disputes
| Record to Check | Evidence |
|---|---|
| Signature | Signed delivery confirmation |
| Tracking | Tracking showing the delivery address and date |
| Photo | Photo proof of delivery |
| Access | Digital access logs |
| Download | Download confirmation |
Not-As-Described Disputes
| Record to Check | Evidence |
|---|---|
| Listing | Product listing as shown to customer |
| Terms | Terms and conditions accepted |
| Communications | Customer communications (pre-sale) |
| Return | Inspection/return refusal documentation |
| Specifications | Quality specifications met |
Credit Not Processed
| Record to Check | Evidence |
|---|---|
| Refund | Proof the credit actually processed: date and amount, with the ARN when there is one, or the STAN, RRN or other provider reference your route uses. A request or a pending credit doesn't prove settlement |
| Status | Refund status and dates, including whether it actually processed |
| Policy | Relevant refund terms and the customer's acceptance |
| Return | Return tracking and correspondence |
Common Mistakes
Documentation Errors
| Mistake | Check Before Submitting |
|---|---|
| Wrong transaction referenced | Match the case, payment, amount and dates |
| Illegible copies | Export a readable copy |
| Missing pages | Include the relevant context |
| Late submission | Confirm the provider's reply-by date |
| Missing translation | Confirm the language needed for this stage |
Evidence Gaps
| Gap | What to Review |
|---|---|
| No delivery proof | Carrier records, tracking and any signature collected |
| No customer communication | Confirmation emails and relevant replies (see descriptors and comms) |
| No AVS data | Whether your checkout captures verification results |
| No login records | Whether access logging would help link use to the purchase (see behavioral analytics) |
Building Your Evidence Collection System
At Transaction Time
Choose records relevant to your product and dispute risks (per your evidence framework):
- IP address
- Device fingerprint, if collected
- AVS/CVV verification results, not the security code itself
- Session data linked to the order
- Click timestamps
PCI DSS prohibits merchants from storing the card security code after authorization, even encrypted. NETWORK PCI SSC FAQ 1280.
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
Don't have device fingerprinting or advanced logging? Use what you've got:
- Order confirmation email: save what was sent and when; a screenshot alone doesn't establish receipt
- Shipping tracking page: save the carrier's reported status, address and time; distinguish that from who received it
- Customer communication: save relevant messages; a thread alone doesn't establish the sender's identity
- Login or access logs: save product-specific download or usage events linked to the purchase; a generic page visit doesn't establish digital delivery
- Signed agreement or invoice: save the agreed scope and acceptance record; an unsigned invoice alone doesn't establish agreement
Use these records to explain what happened, without claiming more than they show. Start collecting better evidence going forward. See what to check above.
Do next
- Follow representment process - Step-by-step
- Chargeback Lifecycle - Full dispute flow
- Chargeback Prevention - Prevention hierarchy
Look up
- Check the reason code - Know required evidence
- Mastercard 4837 - Fraud - Mastercard fraud codes
- Visa 10.4 - Card-not-present Fraud - Visa fraud codes
Deeper
- Chargebacks - The chargebacks hub
Building your evidence system?
- Start with transaction-time collection - IP, device, AVS
Improving win rates?
- Talk to customers first - Understand root cause
- Check CE 3.0 eligibility - Confirm the dates and route with your processor
- Review by dispute type - Match evidence to reason code
Sources
| Source | Supports | Opened |
|---|---|---|
| NETWORK Visa public rules | Fallback and the response-code 83 distinction (sections 7.3.6.3, 11.7.5.3 and 11.7.5.6); purchase history from other merchants | 21 October 2026 |
| VENDOR Stripe CE 3.0 guide | Provider-specific eligibility, ordinary evidence fallback and test-environment limits | 21 October 2026 |
| NETWORK Mastercard merchant FAQ | Published 26 November 2020; reason-code relevance and acquirer deadline | 22 October 2026 |
| NETWORK Mastercard Merchant Edition guide | Edition 13 May 2025, pp. 45 to 46 and 425 to 429; scoped route and language summaries. Confirm current applicability with the acquirer | 22 October 2026 |
| NETWORK Visa public rules | Edition 18 April 2026, sections 11.3.1, 11.7.5.3 and 11.7.5.6; VROL language, purchase-history criteria, dates, data formats, Chile limit and acquirer restriction. Edition 24 October 2026, sections 11.8.5.3 and 11.8.5.6, Tables 11-29 and 11-32, pp. 709-711 and 714-716, for the stage limits | 22 October 2026; 24 October edition read 4 November 2026 |
| NETWORK Amex US Disputes Reference Guide | Cover version 2024. US direct-merchant response guidance, pp. 4 and 7 to 9; code-specific evidence, including F29 | 22 October 2026 |
| VENDOR Stripe evidence practices and reason-code categories | Stripe-specific preparation, delivery and reason-dependent evidence guidance; no universal evidence ranking | 22 October 2026 |
| VENDOR Stripe 3DS guide and response guide | Conditional liability shift; usual 7 to 21 day merchant response range, with the case deadline controlling | 22 October 2026 |
| NETWORK PCI SSC FAQ 1492 | Display masking versus stored-data protection; requirement 3.4.1 BIN-plus-last-four display limit and documented business justification | 22 October 2026 |
| NETWORK PCI SSC FAQ 1280 | October 2023 FAQ; merchants can't retain card security codes after authorization | 22 October 2026 |
| VENDOR Stripe CE 3.0 API guide | Stripe-specific dates and matching fields differ from the network summary; no publication date shown | 22 October 2026 |
| NETWORK Visa public rules | Edition 24 October 2026, sections 11.8.5.3 (Table 11-29) and 11.8.5.6 (Table 11-32); dated purchase-history provisions, description and purchase-order alternative, data-element formats, CVV2 no-match and 35-dispute credential counting | 28 October 2026 |