What Is Chargeback Compelling Evidence? Network Rules and Evidence Types

Chargeback compelling evidence is documentation that supports a merchant’s response to the specific allegation behind a disputed payment. It can include sales, delivery, login, policy, and support records, based on the type of dispute.

The term has two meanings. Mixing them up loses cases:

• General compelling evidence: any records that answer the cardholder’s claim, such as tracking, receipts, or login history.
• Network-defined compelling evidence: data sets that a card network accepts under a formal rule, such as Visa Compelling Evidence 3.0 or Mastercard First-Party Trust.

Start with the chargeback reason code, then check the complaint and the transaction.

{{cta}}

Why Compelling Evidence Decides the Outcome

The issuer decides the case, not your processor. It reads what you send and nothing else. Weak or off-topic records lose cases you could have won.

Sources: Mastercard, updated June 2026, research by Datos Insights; Stripe dispute evidence best practices.

Fraud claims are the biggest group. Stripe’s evidence guidance says fraudulent disputes make up over half of all disputes. It also warns that a Visa fraud dispute without compelling evidence has a very low chance of being overturned.

Even the strongest score tops out at 60%. Evidence improves your odds, but it never guarantees a win. That is why the right records matter more than the number of records. For the full response process, see our handbook on how to win chargeback disputes.

How Card Networks Define Compelling Evidence

Each network treats the term differently under its own network rules. Visa and Mastercard publish formal data rules for fraud claims on real purchases. Amex and Discover accept similar proof under their own codes.

Sources: current Visa rules, Mastercard’s First-Party Trust FAQ, and the Amex and Discover reason code guides. For the side-by-side detail, see our CE3.0 vs First-Party Trust comparison.

Understand Visa Compelling Evidence 3.0

Visa Compelling Evidence 3.0 is a defined framework for qualifying card-absent fraud cases. It is not the same as the everyday use of the term.

Visa sets strict rules on past sales, timing, and matching data. A case qualifies only when all of these hold:

• The dispute is Visa condition 10.4, Other Fraud in a card-absent setting.
• The same card has two or more earlier undisputed, non-fraud sales.
• Those earlier sales are 120 to 365 days old at the dispute date.
• At least two of four data elements match across all three sales: account or login ID, delivery address, device ID or fingerprint, and IP address.
• One of the matching elements is the IP address or the device ID.

For disputes processed on or after 24 October 2026, the April 2026 Visa rules widen CE3.0. Earlier sales may come from other merchants, and a linked credential can count. Ask your acquirer to confirm each case. Not every repeat customer qualifies.

Keep each old record tied to its original sale. Do not reconstruct missing identifiers. Our guide to Visa Compelling Evidence 3.0 explained covers setup in more depth.

How Mastercard First-Party Trust Works

Mastercard First-Party Trust covers 4837 fraud claims on real purchases. It does not use a fixed purchase-history window. Instead, you send one data element from each category:

• Device: IP address, device ID, or device fingerprint.
• Delivery: shipping address or email.
• Additional identity: account login ID, phone number, device location, device name, or billing address.

Mastercard checks those values against the cardholder’s past activity. A case that fails Visa CE3.0 can still meet the Mastercard rule, so check each network separately.

The Main Types of Compelling Evidence

Most chargeback proof falls into six groups. Each one proves something specific, and each has limits.

The type of proof you need depends on the claim. For the full chargeback evidence matrix by reason code, see how to tailor compelling evidence to each chargeback reason code. To find where each record lives in your stack, use the chargeback evidence source map.

What Evidence Helps Win Payment Disputes?

The evidence that helps win payment disputes answers the exact allegation. A delivery scan wins a non-receipt case. It does little for a fraud claim. Use this chargeback evidence checklist before you build the packet:

How can organizations prove a customer authorized a transaction? Use 3D Secure results, matching device and IP data, login history, and past undisputed orders. Customer messages help, but on their own they do not verify identity.

Separate Facts From Assumptions

Stripe asks for short, relevant, readable files. It also notes that customer emails do not verify identity. A message that confirms receipt can support delivery. It does not show who approved the payment.

Use the same discipline with every record:

• A shipping label shows that a label was created.
• A delivery scan supports delivery to the address the carrier recorded.
• A login event records account activity.

Explain what each record shows. Do not stretch it into a claim it cannot support.

If you suspect friendly fraud, keep the response factual. Avoid accusing the customer of lying. A genuine service failure should be resolved on its merits.

{{cta}}

Build a Chargeback Evidence Packet Reviewers Can Follow

A chargeback evidence packet is the full set of files and explanations you submit for one case. Before you assemble it, create a short internal index. For each attachment, record the source system, order ID, event date, and the fact it supports.

• Remove records that belong to a different order or customer.
• Fix any gap between order totals, payments, and partial credits.
• Show which items shipped in which parcel for split orders.
• Keep the terms shown at purchase, not today’s version. For restaurant chargebacks, that means the no-show policy the guest accepted at booking.
• Assign an owner to any missing record and a date to retrieve it.

Then use a chargeback response letter to connect the exhibits into a short timeline. For a step-by-step view of the evidence generation workflow, see the linked guide.

Format Documents for the Actual Submission Route

Processors set hard limits. For merchants using Stripe, its published guidance sets these rules:

Make the packet self-contained. Crop screenshots to the key detail and label what each one shows. Check that a PDF conversion has not cut off an address, date, or amount.

Handle Refunds and Withdrawal Requests Carefully

Reconcile prior refunds before responding. A full-value dispute on a partly refunded purchase needs a clear note of the credit and the remaining amount. Do not issue a second refund without checking the open case.

Stripe’s withdrawal guidance explains that a customer’s request to withdraw does not complete your response. Keep following the case instructions and submit evidence on time.

For an account claim rather than a card dispute, use the PayPal response and appeal guide. Each process has its own checklist.

Submit, Confirm, and Learn From the Result

For the full process after submission, see chargeback representment. If the issuer rejects your evidence, the case can move to pre-arbitration. Track your chargeback win rate by reason code, and review the common reasons merchants lose chargeback disputes.

Perguntas frequentes

What Does Compelling Evidence Mean?

Compelling evidence means records that directly answer a cardholder’s dispute claim, such as delivery proof, authentication data, or purchase history. For Visa and Mastercard fraud claims, it also means data that meets a formal network rule.

Does Compelling Evidence Guarantee a Chargeback Win?

Compelling evidence supports your response, but it does not guarantee a win. The applicable rules, the case facts, and the issuer’s review decide the outcome.

Is Customer Communication Always the Strongest Evidence?

Customer messages help when they answer the claim. They are not stronger than transaction, authentication, delivery, or refund records, and they do not verify identity.

Is Visa CE 3.0 the Same as a Normal Evidence Packet?

Visa CE 3.0 is a specific eligibility framework for 10.4 card-absent fraud claims. A normal packet can still win a case without it.

What Is Fraudulent Chargeback Evidence?

Fraudulent chargeback evidence is proof that the cardholder took part in a purchase they now call fraud. Examples are 3D Secure results, matching device and IP data, account logins, and earlier undisputed orders.

Can I Submit a Link to My Refund Policy?

Attach the policy excerpt through the processor’s upload fields. Do not rely on the reviewer following an external link.

Which Tools Detect Missing Dispute Evidence?

A chargeback evidence tool such as Chargeflow Automation pulls records from your store, processor, and support systems and flags any gap before the deadline. Without a tool, an internal evidence index does the same job by hand.

What Should I Do When Evidence Is Missing?

Identify the missing record, assign an owner, and check whether it can be retrieved before the deadline. Do not invent facts to fill a gap.

Make Evidence Collection Part of Daily Operations

Chargeflow Automation pulls evidence from your connected tools. It builds packets that meet card network rules, including Compelling Evidence 3.0, and submits them on time. You pay only for chargebacks we recover; see pricing. Pair it with a clear review process for missing or conflicting records.