Stripe Fraud Disputes (Visa 10.4) Without CE 3.0: What Proof to Send
The customer says they didn't make the payment. Without the earlier payments Visa CE 3.0 needs, you answer by showing that the real cardholder paid and used what they bought.
1. Check What Stripe Already Has
If the payment passed 3D Secure, the bank's extra check at checkout (such as a code or an approval in the banking app), say so in your reply. The fraud loss should then move to the bank, and Stripe adds the proof for you.
If the customer paid you at least twice before on the same card, 120 to 365 days earlier, read the Visa CE 3.0 guide first. It can also move the loss to the bank.
The payment's page in Stripe shows whether the address check and the CVC check (the code on the back of the card) passed. If both passed, include that.
2. Show That the Real Customer Paid
Back each point with a record, with dates and times:
customer_purchase_ip) matches one the customer used before, or used later to log in.access_activity_log).customer_email_address), and proof if a family member or an employee made the payment.3. Keep the Reply Neutral
Calling the cardholder a scammer hurts your case. State the facts in order, and attach the record behind each one.
Questions
Stripe says fraud disputes rarely go the merchant's way, because the claim is often true. If you think the payment was real fraud, accept the dispute.
The IP address at checkout (customer_purchase_ip), the customer's email (customer_email_address), use after paying with times and IP addresses (access_activity_log), and a short summary of the facts.
Stripe suggests a statement descriptor (the name on the card statement) that customers recognize, with your business name and website, and a receipt after each payment.
The form opens on a fraud dispute and points out missing records and blaming wording.