%201.svg)
Chargebacks?
No longer your problem.
Recover 4x more chargebacks and prevent up to 90% of incoming ones, powered by AI and a global network of 20,000 merchants.
600+ reviewsTL;DR:
- Identify the current stage before choosing an action.
- Keep one case record linking payments, evidence, refunds, and deadlines.
- Confirm submission and reconcile the final financial outcome.
- Use escalation only when the applicable workflow permits it.
The chargeback process is the sequence through which a card issuer raises a payment dispute, the merchant receives the case, and any permitted response is evaluated. For merchants, the practical workflow is intake, investigation, decision, evidence submission, outcome tracking, and reconciliation.
{{cta}}
Know Which Stage You Are Handling
An inquiry, an early resolution event, and a filed chargeback are not the same stage. Some cases resolve before a formal chargeback; some filed disputes cannot be challenged. Confirm the current case status before assigning an action.
Stripe’s dispute lifecycle documentation explains the movement of disputed funds and notes that some disputes are unchallengeable. Do not design a workflow that assumes every case follows every stage.
Merchant workflow
Notification
Match the case to its payment and order.
Complete when: Case owner, status, reason, and deadline recorded.
Investigation
Review fulfillment, authorization, billing, and refunds.
Complete when: Known facts and missing records identified.
Decision
Accept or challenge where permitted.
Complete when: Decision and rationale recorded.
Preparation
For a permitted challenge, select evidence that answers the claim.
Complete when: Final packet checked for relevance and readability.
Submission
Send a permitted response through the supported channel.
Complete when: Submission confirmed before the case cutoff.
Review
Monitor the case and any new instructions.
Complete when: Current status and next action visible.
Closure
Reconcile funds, fees, refunds, and outcome.
Complete when: Financial entries matched and process gaps assigned.
This is a merchant task map, not a universal network timeline. Some cases resolve early or cannot be challenged. Acceptance follows the provider's supported route; preparation and submission apply when a response is permitted.
Create One Authoritative Case Record
Use the current case and provider requirements
Connect the case identifiers with accountable action
One connected case record
Connect the dispute ID with the payment, order, customer account, and any refund or alert event. Record the amount and currency, the exact claim, the response deadline including time zone, and the responsible person.
Consistent evidence and provider coordination
Use the evidence standardization guide to keep reusable records consistent. If several providers are involved, follow the multi-processor workflow rather than allowing separate teams to initiate conflicting actions.
Decide Whether to Accept or Challenge
Acceptance may be appropriate when the complaint is valid, available evidence does not support a challenge, or expected recovery does not justify handling costs. A challenge should explain why the claim is unsupported by the relevant records.
Check the dispute reason before choosing evidence. A receipt identifies a sale; a delivery record addresses fulfillment; an accepted cancellation policy supplies contract context. None is a universal answer to every claim.
Do not treat acceptance as a separate refund. Review refund and chargeback differences before moving money outside the case workflow.
Prepare and Submit the Response
Before final submission
1. Write a brief factual explanation addressing the claim.
2. Attach the specific source records that support each relevant point.
3. Reconcile names, amounts, order references, and dates.
4. Check current file limits and preview the final packet.
5. Confirm the response was sent, not merely saved or queued.
The representment guide covers the formal response. Keep a submission confirmation so a later audit can distinguish evidence problems from missed or failed submissions.
Handle Escalation Only When It Is Available
Some network workflows include pre-arbitration or arbitration. These are not automatic options for every merchant or provider. Ask your acquirer or processor which step is available, what new issue must be answered, and what fees and deadlines apply.
Do not reuse an earlier packet without reviewing the new claim. A previous favorable outcome does not establish that a later stage is also resolved. Equally, do not promise an appeal where the provider treats the decision as final.
Close the Financial and Operational Loop
Match the outcome with the actual balance adjustments. Track disputed funds, partial recovery, refunds, and applicable fees separately. Investigate inconsistencies before classifying the net result.
Then feed verified failures into prevention controls. Use early resolution services for eligible future events and Chargeflow’s automated recovery workflow if evidence preparation and submission need more consistent handling.
A completed merchant case record
The following is a hypothetical training example, not a Chargeflow customer result. An order for $120 is disputed for nonreceipt. The operations owner records the payment ID and case ID, copies the actual provider deadline, checks for existing credits, and compares the promised delivery date with the delivery record.
| Checkpoint | Record to retain |
|---|---|
| Intake | Case ID, payment ID, $120 disputed amount, reason, and displayed due date. |
| Investigation | Order confirmation, promised delivery date, carrier record, destination match, and customer messages. |
| Decision and submission | Written reason to accept or counter; permitted exhibits; final submission confirmation. |
| Outcome and reconciliation | Provider decision, actual balance entries, fees, and any prior credit. |
A saved draft is not the completion record. Retain the provider’s final submission status, then reconcile the outcome separately. Continue with the representment workflow and reason-specific evidence.
Continue learning: Foundations and rules
Use Chargeback Basics and Rules: A Merchant Learning Path to choose the next merchant task in this topic.
- How Does a Chargeback Work? A Step-by-Step Guide: A beginner explanation of the chargeback lifecycle and funds movement.
- Credit Card Chargebacks: Process, Rights and Merchant Evidence: Credit-card dispute concepts, consumer-rights scope, and merchant evidence.
Sources and scope
Source notes updated: October 11, 2026. Card-payment disputes. Identify the network, region, reason and case stage before applying a rule. A cardholder filing window is different from a merchant submission deadline; use the due date and timezone on the merchant case notice.
- Visa: current public rules and editions
- Mastercard: rules and chargeback documents
- Stripe: responding to card disputes
For a live case, retain the governing document’s edition or effective date, the relevant provision, and the provider notice.
Frequently Asked Questions
Does every chargeback follow the same process?
Chargeback stages vary by network, payment method, reason, and provider. Some cases resolve early, and some filed disputes do not allow a challenge.
What is the merchant’s response deadline?
The merchant’s response deadline is the cutoff shown for the specific case and stage. Do not substitute a generic card-brand timeline for that deadline.
Does saving evidence complete the response?
Saving evidence does not by itself establish that a response was submitted. Confirm the final submission status in the provider’s workflow.
Can every lost chargeback be appealed?
A lost chargeback does not always have an appeal path. Confirm the provider’s documented options before planning another submission or escalation.
Chargebacks?
No longer your problem.
Recover 4x more chargebacks and prevent up to 90% of incoming ones, powered by AI and a global network of 20,000 merchants.
.png)
