Chargeback lifecycle
The parties in the payment ecosystem and how a dispute moves from a cardholder complaint to a final decision.
A chargeback is a forced reversal of a card payment. It starts when a cardholder questions a posted transaction and asks their issuing bank to return the money. The issuer routes the case through the card network to the merchant's acquirer, the merchant gets a chance to respond with evidence, and the issuer returns a decision. This page explains who is involved and walks through the lifecycle stage by stage.
The payment ecosystem
Understanding who does what makes disputes easier to navigate. The table below summarizes the key parties and their core responsibilities.
| Party | Description | Primary responsibilities | Examples |
|---|---|---|---|
| Cardholder | The person who owns or uses the payment card. | Makes purchases, provides card details at checkout, and can file a dispute with their bank if they contest a charge. | Buyers, consumers, end customers |
| Merchant | A business that sells goods or services and accepts card payments. | Takes orders, requests payment authorization, fulfills orders, issues refunds, and responds to disputes and chargebacks. | Online stores, physical retailers, SaaS vendors |
| Issuing bank | The bank that issued the card to the cardholder. | Maintains the card account, approves or declines authorizations, posts charges to the cardholder's account, and manages disputes on behalf of the cardholder. | Bank of America, Barclays, local card-issuing banks |
| Acquiring bank | The bank that processes card payments for the merchant. | Provides the merchant account, forwards transactions to the card network, and deposits settlement funds to the merchant (net of fees). | Worldpay, regional acquiring banks |
| Card network | The network that routes messages between issuers and acquirers and sets the rules. | Connects the issuer and acquirer, defines rules and fees, and manages clearing, settlement, and dispute workflows. | Visa, Mastercard, American Express, Discover |
| Payment service provider (PSP) | A provider that helps merchants accept and manage payments. | Supplies gateways, SDKs, risk tools, and reconciliation, and often connects the merchant to one or more acquirers or networks. | Stripe, Adyen, PayPal |
The lifecycle, stage by stage
After a transaction posts, the cardholder has a network-defined window to open a dispute - the exact window depends on the network and reason code (see Network timelines). A dispute moves through the system in a clear sequence.
Cardholder files a dispute
The cardholder contacts their issuing bank, often through the bank's app, to contest a charge. The bank records the reason and starts the dispute process.
Issuer opens a case
The issuing bank creates a formal dispute with a network reason code and sends it through the card network to the merchant's acquirer.
Chargeback posted to the acquirer
The issuer posts a provisional reversal and routes the case to the acquirer. The disputed amount is temporarily removed from the merchant's balance.
Merchant notification
The acquirer or PSP notifies the merchant and provides the dispute data, including the reason code and any supporting details. The merchant can accept the dispute or prepare a rebuttal. Chargeflow ingests disputes from all connected PSPs and presents every case in one place.
Representment (merchant rebuttal)
The merchant gathers evidence and builds a clear, factual narrative to challenge the dispute. Evidence may include receipts, delivery proof, authentication logs, and customer communications. Chargeflow consolidates and enriches the data and drafts a focused rebuttal. See Representment and evidence.
Submission
The merchant submits the evidence and rebuttal to the acquirer or PSP, which forwards it to the issuer for review. Chargeflow submits the rebuttal on the merchant's behalf within the network response window.
Issuer decision
The issuer reviews the submission and issues a ruling: merchant-favored (funds returned) or cardholder-favored (the reversal stands). Chargeflow tracks the outcome and updates case status.
Pre-arbitration and arbitration (optional)
If a decision is contested or network rules require it, the case can escalate to pre-arbitration or arbitration. The card network then adjudicates the dispute. Arbitration is rare, slow, and can be costly.
Timelines vary
Exact timelines and steps vary by card network, reason code, and region - filing windows, merchant response windows, and review periods are all network-defined. The canonical per-network figures live in Network timelines.
Chargeflow exposes these transitions through dispute events so you can act immediately and keep your systems in sync. See Webhooks.