The Chargeback Dispute Lifecycle: Every Stage From Sale to Final Ruling
The chargeback dispute lifecycle is the sequence a disputed card payment moves through: an optional inquiry or retrieval request, the first chargeback, the merchant's representment, the issuer's review, then pre-arbitration and arbitration if either side keeps disputing. Each stage has its own decision-maker and deadline, and most cases end at the issuer's review.
The chargeback dispute lifecycle (also written dispute life cycle) is the set of stages a disputed card payment moves through, from the original sale to a final decision. Each stage has a different decision-maker, a different deadline and a different choice for the merchant. If you know which stage a case is in, you know what to do next. This page maps the stages and the decisions at each one. For start-to-finish timing, see how long does a chargeback take. For a step-by-step guide to the first round, see what happens when a customer disputes a charge.
The lifecycle at a glance
- Transaction. The sale is authorized, captured and settled.
- Pre-dispute (optional). The customer contacts you, or an alert or Visa RDR flags the dispute before it becomes a chargeback.
- Inquiry or retrieval request (optional). The issuer asks for information. No money moves yet.
- First chargeback. The issuer reverses the payment, and your account is debited.
- Representment (second presentment). You contest the chargeback with evidence.
- Issuer review. The issuer accepts your evidence (you win) or keeps disputing.
- Pre-arbitration. One side challenges the result once more.
- Arbitration. The card network rules, and the loser pays the fees.
- Final ruling. The case closes, and funds and fees settle.
Very few cases go through every stage. Most end at stage 4 (the merchant accepts) or stage 6 (the issuer decides).
Timeline table: who acts, how long, what to do
| Stage | Who acts | Typical time | What the merchant should do |
|---|---|---|---|
| Pre-dispute / alert | Customer, alert network, or RDR | Hours to a couple of days | Answer support fast. Refund valid complaints. Act on alerts within their window |
| Inquiry / retrieval request | Issuer (Amex and PayPal use inquiries often) | Response window often ~20 days or less | Send order details, tracking and receipts. A complete answer can stop the chargeback |
| First chargeback | Issuer → network → acquirer → you | Notice arrives days after the cardholder files | Read the reason code. Decide to accept or fight. Do not refund now |
| Representment | You, through your processor | Typically 7–21 days to submit | Submit a rebuttal and evidence matched to the reason code before the processor deadline |
| Issuer review | Issuer | Often 30–75 days | Wait. Keep records. Watch for the outcome or a new case |
| Pre-arbitration | Issuer (or your acquirer, for Visa fraud disputes) | ~30 days per side at network level; your deadline is shorter | Weigh amount vs fee exposure. Fight only with decisive or new evidence |
| Arbitration | Card network | Weeks to a few months | Make sure your acquirer filed a complete case. Accept the ruling |
| Final ruling | Network / issuer | — | Reconcile funds and fees. Feed the outcome back into prevention |
These timings are typical ranges, not network guarantees. They vary by network, reason code and processor, and your processor’s deadline is always the one to plan around. The windows by network are in chargeback time limits.
Stage by stage: the decision points
1. Transaction
The lifecycle starts when the payment is made, not when the dispute arrives. The data you capture here is the evidence you will need later: AVS and CVV results, IP address, device, account login, order details, the terms the customer accepted, and shipping and tracking. If you don’t capture it at the sale, you can’t produce it in representment.
Decision point: what to collect and keep. Keep order, delivery and communication records for at least as long as cardholders can dispute, which is generally around 120 days and longer for some reason codes.
2. Pre-dispute: alerts, RDR and refunds
Before a dispute becomes a chargeback, there is often a chance to stop it. The customer may email support first. Alert networks (Ethoca, Verifi CDRN) can tell you the cardholder has contacted their bank, so you can refund before a chargeback is recorded. Visa Rapid Dispute Resolution (RDR) resolves eligible Visa disputes automatically under rules you set. Data-sharing tools such as Visa Order Insight can also show the cardholder order details while they are still talking to their bank. These tools are compared in Ethoca vs Verifi vs RDR.
Decision point: refund or let it proceed. A refund here usually costs only the sale. The same dispute as a chargeback costs the sale, a fee and a mark against your ratio. Refunding is cheaper when the complaint is valid, or when the amount is too small to fight. Prevention at this stage is covered in how to prevent chargebacks.
3. Inquiry or retrieval request
Some disputes begin with a request for information instead of a chargeback. A retrieval request (Visa calls it a “request for copy”) asks for the transaction record. An inquiry, which is common with American Express, asks you to explain the charge. No funds move yet. Visa and Mastercard retrieval requests are less common for ecommerce than they used to be, but Amex inquiries still come up regularly.
Decision point: answer completely or not. A thorough answer with the order, delivery proof and a clear descriptor explanation often closes the case here. Ignoring it makes a chargeback much more likely.
4. First chargeback
The issuer opens the chargeback, assigns a reason code and gives the cardholder a provisional credit. The network routes it to your acquirer, which debits you. A chargeback fee typically comes with it. Your processor notifies you with the reason code, amount and a deadline. What a chargeback is, and who each party is, is covered in what is a chargeback.
Decision point: accept or fight. Accept clear merchant errors, such as a duplicate charge or a refund you promised and never processed. Fight disputes on orders that were legitimate and fulfilled. Do not refund at this stage. The chargeback is already returning the money, and a refund on top risks paying twice (see chargeback after a refund).
5. Representment (second presentment)
This is your one main chance to win. You submit a rebuttal letter and evidence matched to the reason code through your processor. Mastercard calls it the second presentment, and Visa calls it a dispute response. In Visa’s allocation flow (fraud and authorization codes), the merchant’s challenge is technically filed as pre-arbitration. Your processor’s screen often looks the same either way.
Decision point: what evidence to send. The rebuttal should answer the reason code directly: delivery proof for “not received,” identity and history data for “fraud,” and the product page and policies for “not as described.” How to win a chargeback dispute covers the method, and the rebuttal letter template covers the format.
6. Issuer review
The issuer compares your evidence with the cardholder’s claim. If it accepts your case, the provisional credit is reversed and the funds return to you. If it doesn’t, it can close the case in the cardholder’s favor or escalate.
Decision point: none on your side yet. Just don’t treat a win as final. A case can come back as pre-arbitration within the escalation window.
7. Pre-arbitration
If the issuer still disagrees after your representment, it can file pre-arbitration, often with a new cardholder statement or a changed reason code. In Visa’s allocation flow, your acquirer files it to challenge a fraud decision. The other side then accepts liability or rejects it. The full mechanics are in what is pre-arbitration.
Decision point: accept or fight, based on the amount compared with the arbitration fee exposure and on whether you can answer the new claim directly. An order you already refunded is a strong case to fight. Repeating evidence that already failed is a weak one.
8. Arbitration
If pre-arbitration doesn’t settle the case, the filing side can take it to the card network, which reviews both sides and issues a binding ruling. The losing party typically pays the network’s arbitration fees, which are commonly cited in the hundreds of dollars per case, plus processor fees. This is why arbitration is rare for small ecommerce disputes.
Decision point: whether your acquirer files, or whether you accept the escalation. Once arbitration is filed, the case is in the network’s hands.
9. Final ruling
The case closes. Funds settle with the winner, and fees settle with the loser. A separate compliance process exists for rule violations that don’t fit a reason code, but most merchants rarely see it.
Decision point: what to learn from it. Record the reason code, the outcome and the root cause. Recurring patterns, such as an unclear descriptor, missing tracking or repeat disputers, are where prevention pays off.
How the PayPal dispute lifecycle differs
PayPal runs a separate lifecycle for disputes opened inside PayPal:
- Inquiry (dispute). The buyer opens a case in the Resolution Center, usually for Item Not Received or Significantly Not as Described. Buyers generally have up to 180 days from the transaction. At this stage it is a conversation between buyer and seller, and PayPal is not ruling yet.
- Claim. If the dispute isn’t resolved within PayPal’s window (commonly up to 20 days), either side can escalate it. PayPal becomes the decision-maker, and sellers typically get around 10 days to respond with evidence.
- Decision and appeal. PayPal rules. Sellers can generally appeal an adverse decision within a short window.
- Card chargeback (separate path). A buyer who paid with a card can skip PayPal and go to their bank. That creates a card-network chargeback, which follows the card lifecycle above, including possible pre-arbitration and arbitration, with PayPal representing the case for you.
The practical rule: resolve at the inquiry stage whenever you can. It costs no fee and doesn’t count as a chargeback. Details are in PayPal disputes vs chargebacks and how to win a PayPal dispute.
Where refunds fit in the lifecycle
Whether a refund helps or hurts depends on when you issue it.
| When you refund | Effect |
|---|---|
| Before any dispute | Prevents the dispute. Costs only the sale |
| After an alert or RDR, before a chargeback | Usually stops the chargeback. Costs only the sale |
| During an inquiry | Can close the case. Confirm the issuer has recorded it |
| After a chargeback is filed | Risks a double loss. Accept or contest the chargeback instead |
| Before a dispute that comes anyway | Strong evidence in representment or pre-arbitration. Send the refund confirmation |
Automating the lifecycle
The lifecycle has long waits and a few short, decisive windows: representment and, sometimes, pre-arbitration. DisputeDash handles both. It picks up each new dispute when the processor reports it, builds the evidence for the reason code, and submits before the deadline. When a case escalates, it applies your pre-arbitration policy: auto-accept, fight all, or fight above a dollar threshold.
Key takeaways
- The lifecycle runs: transaction, pre-dispute, inquiry, chargeback, representment, issuer review, pre-arbitration, arbitration, final ruling.
- You lose the money at the first chargeback and win it back at representment. Most cases end there.
- Each stage has its own decision: refund, answer, accept or fight, and escalate or settle.
- Refund before a dispute, never after a chargeback exists.
- PayPal’s own path is inquiry, then claim, then decision, with card chargebacks running separately under network rules.
Win more chargebacks, automatically.
DisputeDash gathers the evidence, builds the rebuttal, and submits before the deadline — across Stripe, PayPal, Braintree, PayArc and more. Flat fee, no commission.
Start free trial — keep 100%