Emergency · United States

Chargeback Response Builder

Enter the order details, dispute reason, and evidence you can provide. The builder produces a reason-specific response letter and an evidence checklist you can attach when replying to Stripe, Shopify Payments, or PayPal.

Inputs

Order ID

Order amount ($)

Dispute reason

Processor

Strongest evidence you have

Refund status

Customer name

Result

Processor: Stripe / Shopify Payments
Order amount: $79.00
Response ready: Yes

Subject: Response to chargeback for order 1042

To Disputes Team,

We are responding to the chargeback opened by Jane D. for order 1042 in the amount of $79.00.

Rebuttal
Carrier tracking confirms the package was delivered to the address on file. A copy of the tracking record — and delivery photo where available — is attached.

Refund status
No refund has been issued because the order was fulfilled as described.

Evidence attached
- Carrier tracking record with delivered status
- Delivery photo (if available)
- Order confirmation email

We respectfully ask that this dispute be resolved in our favor based on the evidence provided.

Thank you,
[Your business name]
[Your email] · [Your phone]

Evidence checklist
[ ] Order confirmation email (PDF)
[ ] Carrier tracking record with delivery status
[ ] Delivery photo or signature if available
[ ] Product listing screenshot from the order date
[ ] Refund and return policy shown at checkout
[ ] Customer communication transcripts
[ ] IP / AVS / CVV log for the order
[ ] Prior order history from the same customer

Submit before the processor deadline — usually 7 to 21 days.

Upload evidence as PDF files, not screenshots pasted in the response body.

Direct answer

A winning chargeback response (called representment) follows the same 3-part structure Visa and Mastercard issuers expect. Part 1 is an order summary and authorization match: order ID, date, amount, the billing and shipping address, and proof that the Address Verification Service (AVS) and CVV checks passed at checkout. Part 2 is a reason-code specific rebuttal narrative: two or three factual paragraphs that answer the exact claim behind the code, such as fraud, item not received, or not as described, and nothing else. Part 3 is concrete digital proof: the carrier delivery photo or tracking record, signed proof of delivery (POD) for high-value orders, device fingerprint and IP logs that tie the purchase to the cardholder, and any customer messages confirming receipt. This free builder generates Parts 1 and 2 for you and gives you a checklist for Part 3, ready to paste into Stripe, Shopify Payments, or PayPal.

Key takeaways

Merchants who respond with organized, reason-specific evidence commonly win 40% to 60% of disputes, while merchants who ignore disputes lose 100% of them automatically.
Processor rebuttal deadlines are strict and usually 7 to 21 days; Stripe and Shopify Payments often allow about 7 to 20 days, PayPal typically 10, and a late response counts as a loss.
Friendly fraud — a real customer disputing a purchase they received — is now the most common source of ecommerce chargebacks, and it is the category you are most likely to win.
AVS/CVV match, delivery confirmation, and IP or device data matching past orders are the three strongest pieces of evidence for fraud claims.
Prevention beats representment: clear billing descriptors, visible refund and cancellation policies, and fast replies to customer emails stop many disputes before they are filed.

Method

Method: response = order facts + reason-specific rebuttal + evidence list + refund status + processor deadline reminder.

How this tool works

The builder starts with the facts you enter: order ID, customer name, amount, the dispute reason your processor shows, the strongest evidence you have, and whether any refund was issued. Each processor displays a simplified reason category, and behind each category is a card-network reason code. The builder maps the category to the argument an issuer expects to see for that code.

Fraud / unauthorized (Visa 10.4, Mastercard 4837): the rebuttal focuses on authorization. It states that AVS and CVV matched, that the shipping address matches the billing address or a previously used address, and that IP and device data align with the cardholder's prior purchase history.

Product not received (Visa 13.1, Mastercard 4855): the rebuttal focuses on fulfillment. It cites the carrier, tracking number, delivery date, and delivery address, and points to the carrier delivery photo or signed POD.

Not as described (Visa 13.3, Mastercard 4853): the rebuttal compares what was advertised to what was delivered. It references the product page, specifications, and photos at the time of purchase, and notes whether the customer used your return process.

Cancelled subscription (Visa 13.2, Mastercard 4841): the rebuttal shows that the customer agreed to recurring terms at checkout, that renewal notices were sent, and that no cancellation request was received before the billing date.

Duplicate charge (Visa 12.6): the rebuttal lists every transaction on the card for that day and shows that each charge corresponds to a separate order or that a duplicate was already refunded.

The builder then merges the matching rebuttal with your evidence list into a clean, factual letter and produces a checklist of documents to upload as separate PDFs. Everything runs in your browser; no order data is sent anywhere.

When to use this

Fight a dispute when you have evidence that directly answers the claim. The clearest cases are friendly fraud (tracking shows delivered to the verified address, but the customer says the item never arrived), subscription disputes where the customer agreed to renewal terms and never cancelled, and fraud claims where AVS, CVV, and IP data match a returning customer. These are the disputes merchants win most often, and each win protects both the revenue and your dispute ratio.

Accept liability when the evidence is against you or the cost of fighting exceeds the order value. Genuine carrier damage, a package that tracking shows was lost or delivered to the wrong address, an item that truly did not match its listing, or clear signs of stolen-card fraud (mismatched AVS, a freight forwarder address, a brand-new account) are usually better accepted. Fighting a dispute you cannot win wastes time and can annoy the issuer.

Also consider the economics. For a $12 order, the time spent building evidence may cost more than the refund, but patterns still matter: if the same customer or address files repeated disputes, respond and block them. Do not use this tool for pre-dispute refund requests — handle those directly with the customer, because a quick refund is cheaper than any chargeback.

Step-by-step

Open the dispute in your processor dashboard and record the reason, reason code, amount, and response deadline. In Stripe it is under Payments → Disputes, in Shopify Payments under Orders → Chargebacks, and in PayPal in the Resolution Center. Put the deadline in your calendar with a reminder two days early.
Pull every relevant record for the order: the order confirmation, the AVS and CVV result from the payment details, the customer's IP address and device information, tracking and carrier delivery photo, any signed POD, customer emails or chat logs, and the product page as it looked at the time of purchase.
Enter the order details, dispute reason, and strongest evidence into the builder above. Choose the evidence you actually have on file — never claim evidence you cannot upload, because issuers compare the letter against the attachments.
Review the generated letter and edit the facts so they match your records exactly. Keep it short, factual, and focused on the reason code. Remove anything emotional or unrelated, such as complaints about the customer.
Convert each evidence item into its own clearly named PDF (for example 01-order-summary.pdf, 02-tracking-delivered.pdf). Stripe accepts one combined evidence file up to a size limit, Shopify Payments has dedicated upload fields per evidence type, and PayPal allows several attachments per case; follow each processor's format.
Paste the letter into the response field, upload the PDFs, and submit before the deadline. Then log the dispute, reason, evidence used, and final outcome in a simple tracker so you can spot repeat abusers and improve your prevention steps.

US example

A US Shopify seller receives a $79 'product not received' dispute through Shopify Payments. Tracking shows the package was delivered to the verified billing address with a carrier photo on the porch. The seller selects 'Product not received' and 'Tracking shows delivered', pastes the generated letter, and uploads the order summary, the tracking record, and the delivery photo as three PDFs. That is a classic friendly-fraud case with strong evidence.

A Stripe-based subscription brand receives a $49 'subscription cancelled' dispute. The customer's account shows no cancellation request, the checkout page clearly disclosed monthly renewal, and a renewal reminder email was sent five days before billing. The seller uploads the checkout terms screenshot, the reminder email, and the account activity log.

Reason code	Claim	Required proof documents	Typical win probability*
Visa 10.4	Fraud — card-absent environment	AVS/CVV match, IP and device fingerprint, prior undisputed orders from same account, delivery to billing address	20%–35%
Visa 13.1	Merchandise not received	Tracking with delivered status, carrier delivery photo, signed POD for high-value orders, address match	45%–65%
Visa 13.3	Not as described	Product page at time of sale, specs and photos, return policy, customer messages, proof no return was attempted	30%–45%
Mastercard 4837	No cardholder authorization	AVS/CVV match, IP geolocation, device ID, account login history, delivery confirmation	20%–35%
Mastercard 4853	Cardholder dispute (not as described / defective)	Listing and specs, quality or inspection record, return and refund policy, correspondence showing no return request	30%–45%

*Illustrative planning ranges based on common industry experience, not guarantees. Actual outcomes depend on the issuer, the evidence quality, and the processor.

Common mistakes

Submitting a 50-page unorganized PDF. Issuer reviewers spend minutes per case; bury the key proof on page 37 and it will not be seen. Use short, clearly named files with the strongest evidence first.
Missing the processor deadline. Late responses are automatic losses, and the deadline is often shorter than the card network's own window because the processor needs time to forward your case.
Arguing emotionally instead of factually. Calling the customer a scammer does not win disputes; timestamps, tracking records, and authorization data do.
Failing to prove the address match. For fraud and not-received claims, show that the shipping address matches the billing address verified by AVS, or a previously used and undisputed address.
Not providing cancellation and refund policy disclosures. For subscription and not-as-described disputes, include a screenshot proving the customer saw and agreed to your terms at checkout.

Frequently asked questions

How long do I have to respond to a chargeback?

Deadlines vary by processor and are usually between 7 and 21 days. Stripe and Shopify Payments often allow roughly 7 to 20 days, while PayPal typically gives about 10 days. The exact due date is always shown on the dispute record in your dashboard. Treat it as final — a late response is treated as accepting the chargeback.

What evidence wins a chargeback?

The strongest evidence directly answers the reason code. For fraud claims, AVS and CVV matches, IP and device data, and prior undisputed orders work best. For item-not-received claims, tracking with a carrier delivery photo or signed proof of delivery is most persuasive. For not-as-described claims, show the product page, specifications, and your return policy.

Will responding to disputes hurt my merchant account?

No. Responding does not hurt your account; ignoring disputes does. Your dispute ratio is counted whether you respond or not, but winning cases recovers revenue and shows the processor you manage risk actively. Card network monitoring programs generally start watching merchants whose dispute ratio approaches roughly 0.9% to 1%.

Can I win a fraudulent chargeback?

Yes, especially when the purchase was made by the real cardholder, which is called friendly fraud. Evidence that AVS and CVV matched, the order shipped to the billing address, and the IP or device matches previous undisputed orders makes a strong case. Win rates for true stolen-card fraud are low, so accept those and tighten your fraud filters instead.

What is friendly fraud and how do I prevent it?

Friendly fraud happens when a legitimate customer disputes a charge instead of asking you for a refund, often because they do not recognize the billing descriptor or forgot the purchase. Use a clear billing descriptor with your store name, send shipping and delivery emails, and make your refund policy and contact details easy to find. Requiring signature confirmation on high-value orders also removes the 'never received' argument.

Should I refund a customer after a chargeback is filed?

Usually no. Once a chargeback is filed, the funds are already pulled from your balance, so issuing a separate refund can cause you to lose the money twice. Instead, either accept the dispute in your processor dashboard or submit evidence. If you want to resolve it with the customer, ask them to withdraw the dispute with their bank.

Method and guidance reviewed by the AIFlowBiz Editorial Team.