Merchant Account Disputes
Merchant Account Chargeback Dispute: How to Respond and What Evidence to Send
On a traditional merchant account or acquirer — Adyen, Worldpay, or any direct processor — you respond through your provider’s dispute channel, and the card network decides. The outcome turns on whether your evidence answers the reason code. Here is what to gather and how to submit it.
Build My Evidence Pack — $19To respond to a merchant account chargeback, start from the notice your acquiring bank sends, read the reason code and deadline, gather the evidence that answers that specific code, write a short rebuttal letter, and submit a labeled package through your provider’s dispute channel before the deadline. Your processor forwards the evidence; the card network decides, so the pack has to read for that reviewer. This works in any processor’s portal, with no account to connect.
What evidence should you gather?
The weight of each evidence type shifts with the reason code and whether the sale was in person or online. Prioritize what directly answers the cardholder’s claim.
| Evidence Type | What It Proves | Priority |
|---|---|---|
| AVS & CVV Match Records | The cardholder’s address and security code matched at authorization | Critical |
| Delivery / Tracking Proof | The product reached the address on the order | Critical |
| Customer Communication | The buyer confirmed the order, receipt, or acceptance | Critical |
| Transaction Records | Order details, ARN, transaction ID, timestamp, and amount | High |
| Refund / Return Policy | The customer agreed to your terms before purchase | High |
| EMV / Signed Receipt (in-person) | The card was physically present and the buyer authorized the sale | High |
| IP / Device Information | The transaction matched the cardholder’s known location or device | Medium |
Which evidence fits your dispute type?
Each dispute type needs a different evidence strategy.
Fraudulent / Unauthorized
The cardholder says they did not authorize the transaction.
Key: For card-not-present sales, lead with AVS and CVV match data plus device, IP, and delivery evidence. For in-person sales, EMV chip read and signed receipts are strongest.
- AVS (address) and CVV2 match results
- Device fingerprint or IP matching the cardholder
- EMV chip read or signed receipt (in-person)
- Delivery confirmation to the verified address
Product / Service Not Received
The customer claims they never received what they paid for.
Key: Tracking with delivery confirmation to the order address is essential. For services, documentation that the service was completed.
- Tracking number with carrier and delivery confirmation
- Shipping date relative to the order date
- Service completion records with dates
- Communication confirming delivery or completion
Not as Described
The customer claims the product or service did not match the description.
Key: Your original listing or service description plus communication showing the customer knew what they were buying.
- Original product listing or service description
- Photos of the item as shipped
- Communication before purchase
- Return policy shown at checkout
Duplicate or Credit Not Processed
The customer claims a double charge or a refund they say was never issued.
Key: Show that each charge maps to a separate order, or document the refund and the policy under which it was or was not owed.
- Separate order or invoice numbers for each charge
- Itemized receipts showing distinct purchases
- Refund confirmation if a credit was issued
- Refund policy accepted at checkout
How do you respond to a merchant account chargeback?
Read the chargeback notice from your acquirer
Your acquiring bank or merchant-account provider sends a chargeback notice or retrieval request. It lists the reason code, the acquirer reference number (ARN), the dispute amount, and the response deadline. Start from that document.
Identify the reason code
The reason code tells you exactly what the cardholder claims. A fraud code needs authorization and identity evidence; a non-receipt code needs delivery proof. Match your evidence to the code before gathering anything else.
Gather your evidence
Pull AVS/CVV results, the transaction and ARN records, delivery or service-completion proof, EMV or signed receipts for in-person sales, and customer communication. Your processor stores the transaction detail; you supply the proof around it.
Write the rebuttal and label exhibits
Lead with a short rebuttal letter that names the reason code and answers it point by point, then attach labeled exhibits. The card network, not your acquirer, makes the final decision, so the package must read for that reviewer.
Submit to your acquirer before the deadline
Send the response package through the channel your acquirer specifies — a dispute portal, secure upload, or email — ahead of the stated deadline. A missed deadline forfeits the dispute automatically.
Frequently Asked Questions
How do I respond to a chargeback on my merchant account?↓
How long do I have to respond to a merchant account chargeback?↓
Does this apply to Adyen, Worldpay, and other processors?↓
Can I use ChargebackKit for any processor?↓
Build your merchant account response pack
$19. A submission-ready evidence pack that works in any processor’s portal, with 100% of the recovery yours.
Build My Evidence Pack — $19Secure checkout via Stripe · No subscription · Volume discounts available
Disputing on a different processor?
The evidence that wins is the same across processors. Only the dispute flow and where you submit it change. See all processors.
Keep going
The card network decides the dispute. Match your exhibits to the reason code, then assemble the pack.