Most merchants who lose a "fraudulent transaction" chargeback assume the card network never looked at their evidence. In practice, an analyst at the issuing bank usually did look at it, for about 90 seconds.
Issuing bank dispute teams work through strict queues. When a processor submits a 14-page PDF padded with AI-generated cover letters, legal boilerplate, and uncropped full-page screenshots, the reviewer does not read paragraph four. They scan for structured fields that satisfy the card network's reason code rules. If the required proof is buried or missing, the dispute defaults to the cardholder.
Understanding what banks actually check, and the hard technical limits of payment gateways, makes a bigger difference than writing longer narratives.
Why Long AI Narratives Backfire
Many automated chargeback tools generate multi-page rebuttal essays explaining why the store is trustworthy and why the customer probably forgot about the order. Bank analysts are not evaluating persuasion. They are checking off network-defined evidence fields for a specific reason code, such as Visa 10.4 (Other Fraud - Card-Absent Environment) or Mastercard 4837 (No Cardholder Authorization).
A dense wall of text slows down verification. A clean two-column summary table on page one, followed by labeled raw logs (AVS/CVV match, IP address, timestamp, delivery confirmation), lets a reviewer verify the case inside their 90-second window.
Visa Compelling Evidence 3.0 (Reason Code 10.4)
For merchants dealing with first-party fraud ("friendly fraud") on card-not-present Visa transactions, Visa Compelling Evidence 3.0 (CE 3.0) is the highest-leverage rule available. When all criteria are met, liability shifts away from the merchant under reason code 10.4.
The technical requirements are strict, and missing even one disqualifies the submission:
- Historical transactions: You must provide at least 2 prior undisputed transactions from the same cardholder / payment method.
- Age window: Both historical transactions must be settled between 120 and 365 days prior to the dispute date. Transactions newer than 120 days or older than 365 days do not qualify.
- Matching data elements: The disputed transaction and both prior undisputed transactions must share at least 2 of the following 4 core elements:
- IP address
- Device ID or device fingerprint
- Account ID (login username or customer ID)
- Shipping address
- Mandatory element rule: At least one of the two matching elements must be either the IP address or the Device ID / fingerprint. Matching only Account ID and Shipping Address is not sufficient under CE 3.0.
CE 3.0 Eligibility Check (Visa 10.4): - Prior undisputed orders >= 2 - Settlement age: 120 <= days_before_dispute <= 365 - Matched fields >= 2 from { IP, Device_ID, Account_ID, Shipping_Address } - Required: (IP matched) OR (Device_ID matched) If your backend logs Stripe PaymentIntent metadata, checkout IPs, and session device hashes, pulling those three rows into a single comparison table on page one of your evidence PDF gives the issuing bank exactly what the Visa rule requires. You can cross-check the exact field requirements across Visa, Mastercard, and Amex on the reason codes reference.
Hard Gateway File Limits (Silent Truncation)
Even strong evidence fails when the file hits processor ingestion limits. Payment gateways enforce strict payload ceilings before forwarding documents to the card networks:
- Stripe: Maximum 4.5 MB total file size and 49 pages per evidence PDF (with each individual upload field capped).
- Shopify Payments: Maximum 4.0 MB total file size.
High-resolution Retina screenshots exported directly from macOS or order dashboards routinely weigh 1.5 MB to 3 MB per image. Combining four unoptimized screenshots easily crosses the 4.0 MB Shopify limit or the 4.5 MB Stripe limit. Worse, oversized or poorly encoded PDFs can trigger silent truncation, downscaling that makes timestamps unreadable, or flat-out ingestion errors right before the submission deadline.
Keep evidence packets compact: downsample screenshots to 1200px wide, convert to grayscale or medium-quality JPEG inside the PDF, strip unnecessary email headers, and keep the entire packet under 2 MB and under 10 pages whenever possible.
The Math Behind 25% Success-Fee Platforms
Because chargeback rules feel opaque, many e-commerce teams hand disputes over to automated recovery vendors like Chargeflow or Chargeblast. Most of these platforms charge a 20% to 25% success fee on every recovered dispute.
The unit economics break down quickly on medium- and high-ticket orders:
| Order Value | Dispute Fee (Stripe) | 25% Recovery Fee | Net Cost Just to Keep Your Own Revenue |
|---|---|---|---|
| $400 | $15 | $100 | $115 |
| $1,500 | $15 | $375 | $390 |
| $3,200 | $15 | $800 | $815 |
On a single $1,500 dispute, paying a 25% success fee hands over $375 for generating a PDF from data that already lives in your own Stripe dashboard and order database. A detailed breakdown of how percentage-based tools compare against in-house flat-cost workflows is documented in this Chargeflow alternative comparison.
Nothing guarantees a win on every dispute, because final decisions always rest with the issuing bank and card network arbitration rules. Still, compiling a clean, CE 3.0-compliant, under-4 MB PDF does not require handing away a quarter of your order value.
Practical Checklist Before You Submit
Before uploading your response to Stripe or Shopify:
- Put a one-page executive table first: reason code, transaction ID, AVS/CVV result, and CE 3.0 match matrix.
- Verify that prior undisputed orders fall strictly inside the 120-365 day window.
- Confirm IP address or Device ID matches across all three transactions.
- Check final PDF size (< 4.0 MB for Shopify, < 4.5 MB and <= 49 pages for Stripe).
If you want to assemble a bank-formatted, size-checked evidence PDF directly in your browser without creating an account or paying percentage fees, you can use the open checklist and free browser-based generator at disputepack.pages.dev/builder. Everything runs client-side, outputs a compact PDF tailored to the reason code, and keeps your order data off third-party servers.
