A dispute crosses several desks fast. Support knows what the customer said. Fulfillment knows what shipped. Finance sees the payment and refund. Someone has to connect those facts before the response deadline.
This eight-step workflow gives a small online store a clear handoff from notice to submission. Follow the current instructions inside your payment provider’s dispute screen. Evidence rules and deadlines vary by provider, card network, and case type.

The Online Merchant Chargeback Response Prompts book provides prompts you can adapt to the case. Stripe’s response guidance says deadlines are usually 7 to 21 days depending on card network. Use the deadline in your own dispute screen, not a general range.
Step 1: assign one case owner
Name the person responsible for tracking the deadline, collecting evidence, and submitting the response. Other people can supply records, but one owner should know which files are complete and which questions are still open.
Record the transaction ID, dispute ID, order number, customer account reference, amount, and response due date. Keep the notice and its attachments in the case folder.
Step 2: read the claim and instructions
Open the dispute in the processor’s account. Read the stated reason or category, the customer’s explanation if available, requested evidence fields, file limits, and deadline. Save a copy or screenshot of those instructions for the internal file.
Visa’s current Core Rules and Product and Service Rules specify response requirements by dispute condition. Your provider’s form determines how you submit information for the case.
Step 3: connect the payment to the order
Before you collect documents, verify that the processor transaction belongs to the order in question. Match amount, currency, date, transaction reference, product or service, and customer account. If one field differs, investigate before you use the record.
This prevents an easy mistake: attaching a delivery receipt from the same customer but a different order. Save the exact processor and order references in the case index.
Step 4: ask each team for its source records
Send a narrow request to the people who hold the evidence. Support can provide customer messages. Fulfillment can provide warehouse and carrier events. Billing can confirm refunds, credits, or invoices. Product or service teams can explain what was provided.
| Team | Record to request | Question it may answer |
|---|---|---|
| Customer support | Messages and case notes | What did the customer report or request? |
| Fulfillment | Pick, pack, carrier, delivery, or return records | What happened to this specific order? |
| Billing | Payment, refund, credit, and invoice records | Was an amount charged or returned? |
| Product or service | Product page, service scope, access or completion records | What was offered and what was provided? |
Ask people to preserve original records. Do not ask them to recreate an event from memory or rewrite the customer conversation.
Step 5: build one short timeline
Arrange the main events in date order. Include the order, payment, fulfillment or service, customer contacts, refund or cancellation, and dispute notice when they apply. Put the source next to each event.
Check dates and time zones. If two systems show different times, explain the format or mark the discrepancy for review. A timeline should make the records easier to follow, not hide gaps.
Step 6: resolve open questions and contact the customer if appropriate
Use the processor’s available channel to contact the customer if that could clarify the issue. Keep the message calm and factual. If you resolve the complaint, retain the conversation and any refund, replacement, or other action record.
Do not let a conversation delay the formal response. Stripe explains that an inquiry may be a pre-dispute stage and that a formal chargeback requires a separate response if it escalates. Check the status in your own processor account.
Step 7: draft, check, and submit through the provider
Write a short response that addresses the specific claim and refers to the supporting records. Check every sentence against its source. Follow the processor’s evidence categories, file rules, and redaction instructions.
Stripe says a Dashboard response is forwarded to the issuing bank and cannot be edited or supplemented afterward. Other providers may handle submissions differently. Assemble the complete file, confirm the transaction and deadline, and have a second person review it before you submit.
Step 8: save the receipt and track the next status
Save the submission confirmation, date, response text, and exact files sent. Assign someone to check for new messages or a decision. If the outcome shows a record gap, update the internal process for future orders.
Keep the final case record with restricted access. Remove duplicate drafts, but retain the exact submission copy according to your company’s record policy.
Use AI only for a bounded support task
If your business allows it, AI can help assemble a timeline from redacted records or flag missing evidence. Do not share full payment credentials, passwords, or private customer information with an unapproved tool.
“Using only these redacted records for one transaction, create a timeline with date, event, source file, and any conflict. Then list which processor evidence fields appear to have a supporting file and which remain open. Do not decide whether the claim is valid, infer customer intent, create evidence, or submit anything. Mark uncertain items for a human reviewer.”
Check the output against the original records. AI may confuse a refund request with a completed refund or a carrier scan with proof of delivery. The case owner is responsible for the final packet.
Where to continue
For preparation mistakes, read the seven chargeback response mistakes guide. The prompt guide covers evidence indexing and final review. Next, use the merchant Q&A to resolve open questions and the templates to keep the case file organized. The Online Merchant Chargeback Response Prompts book offers more prompt patterns for human review.
Frequently asked questions
What should I do first when a chargeback arrives?
Open it in your processor, save the reason and case details, confirm the deadline, and assign an owner for the response file.
How long do merchants have to respond to a chargeback?
The deadline depends on the provider, network, and dispute. Stripe says its windows are usually 7 to 21 days, but use the deadline shown for your case.
Should I contact the customer during the dispute?
If the provider offers a contact route, a factual conversation may clarify the complaint. Keep a record and follow the formal process and deadline.
Can I add more evidence after submitting my response?
It depends on the provider and dispute stage. Stripe says a Dashboard response cannot be edited or supplemented after submission. Check your provider’s instructions.
Does following this workflow guarantee that I will win?
No. The issuer or network decides under its rules. This process helps organize a timely, relevant response but does not guarantee an outcome.