How a Chargeback Dispute Is Processed

A chargeback is a formal reversal mechanism built into the card payment system. When a cardholder disputes a transaction — because goods were not delivered, the charge was unauthorized, or the amount was incorrect — the dispute does not simply go to the merchant. It travels through a structured chain of institutions, each with defined roles, deadlines, and decision rights prescribed by the card network's operating rules.

The process is distinct from an informal complaint or a refund request. A chargeback invokes a regulatory and contractual framework that can result in a forced transfer of funds from the merchant's bank back to the cardholder's bank. Understanding how that framework operates requires tracing the dispute through each stage in sequence.

The Sequence of Stages in a Chargeback Dispute

Stage 1 — Cardholder initiates the dispute. The cardholder contacts their card-issuing bank and asserts a reason for disputing the charge. The issuer assigns a reason code drawn from the card network's standardized code set. That code determines which evidentiary rules apply and which deadlines govern the rest of the process. Reason codes are grouped into broad categories: fraud (unauthorized use), authorization errors, processing errors, and consumer disputes (such as non-delivery or significantly not-as-described merchandise).

Stage 2 — Issuer provisionally credits the account. Under the Fair Credit Billing Act (FCBA), the issuing bank is required to acknowledge a billing dispute within 30 days and resolve it within two billing cycles, not to exceed 90 days. While the dispute is open, the cardholder is not required to pay the disputed amount, and the issuer may not report that amount as delinquent to a credit bureau. This provisional credit is not a final resolution; it is suspended pending the outcome of the dispute process.

Stage 3 — Issuer forwards the chargeback to the acquiring bank. The acquiring bank (also called the merchant's bank) receives formal notification of the chargeback along with the assigned reason code. The acquiring bank then notifies the merchant and requests a response. The merchant has a fixed window — typically between 7 and 30 days depending on the network's rules — to submit a rebuttal package.

Stage 4 — Merchant submits a representment. If the merchant believes the chargeback is invalid, it compiles a representment: a documented counter-argument supported by evidence. Depending on the reason code, valid evidence might include signed delivery confirmation, a copy of the terms and conditions the cardholder agreed to, transaction logs, IP address records, or communication history. The acquiring bank reviews the representment for completeness and forwards it to the issuing bank.

Stage 5 — Issuer reviews and decides. The issuing bank evaluates the representment against the reason code's evidentiary requirements. If the representment is sufficient, the provisional credit is reversed and the charge is reinstated. If the representment is insufficient or no representment is filed, the chargeback stands and the funds are permanently transferred from the acquiring bank to the issuing bank.

Stage 6 — Arbitration (if the dispute is escalated). Either bank may escalate to the card network for binding arbitration if it believes the other party misapplied the rules. At this stage, the network itself reviews the documentation and issues a final ruling. Arbitration fees — which can reach several hundred dollars per case — are assessed against the losing party. Because of these fees, most disputes are resolved before arbitration.

The Institutions and Rules That Govern Each Stage

The cardholder's issuing bank is the institution that extended the credit line and issued the card. It receives the dispute, assigns the reason code, issues the provisional credit, and makes the initial ruling on the representment. Its obligations to the cardholder during a dispute are governed by the Fair Credit Billing Act, which is a federal statute, as well as by the card network's operating rules, which are contractual.

The merchant's acquiring bank is the financial institution that processes payments on behalf of the merchant. It is contractually bound to the merchant through a merchant agreement and to the card network through a membership agreement. When a chargeback arrives, the acquiring bank acts as an intermediary, relaying the dispute to the merchant and the representment back to the issuer. The acquiring bank is also financially liable if the merchant cannot cover a lost chargeback — a risk that acquiring banks manage through reserve accounts and underwriting.

The card network publishes and enforces the operating rules that define every reason code, every deadline, and the arbitration procedure. The network does not hold consumer funds, but it sets the procedural framework within which the issuing and acquiring banks operate. It also charges fees to both banks for processing chargeback transactions, separate from any arbitration fees.

The merchant is not a direct party to the banking relationship but bears the financial consequence of a lost chargeback. Beyond the transaction amount itself, merchants typically absorb a chargeback fee charged by the acquiring bank, which ranges from roughly $20 to $100 per incident. Merchants with chargeback rates that exceed the network's threshold — generally around 1% of monthly transactions — may be placed in a monitoring program or lose their ability to accept card payments. Because a chargeback dispute can affect the balance of a credit account in ways that interact with how average daily balance is calculated, the timing of a provisional credit within a billing cycle can affect the interest computation on that account.

Reason codes function as the procedural rulebook for each dispute. Each code specifies what the merchant must prove, what the issuer must evaluate, and how long each party has to act. A chargeback filed under a fraud reason code requires different evidence than one filed under a "services not rendered" code. Mismatches between the actual dispute and the assigned reason code are a common source of procedural failure.

Where the Chargeback Process Produces Unexpected Outcomes

Friendly fraud and its downstream effects. A chargeback filed on a transaction the cardholder actually authorized — sometimes called friendly fraud or first-party misuse — is indistinguishable from a legitimate fraud dispute at the point of initiation. The issuing bank has no independent knowledge of whether the cardholder actually received the goods or authorized the charge. If the merchant fails to submit a timely or sufficiently documented representment, the chargeback succeeds regardless of its legitimacy. Card networks have introduced enhanced fraud-detection tools and updated reason codes to address this, but the structural asymmetry remains: the initial burden of proof falls on the merchant, not the cardholder.

Deadline mismatches. The FCBA's 60-day window for the cardholder to dispute a billing error runs from the date the statement containing the error was sent. Card network rules operate on different timelines, often measured from the transaction date or the settlement date. These two clocks do not always align, meaning a cardholder may still have statutory rights under the FCBA even after the network's chargeback window has closed — and vice versa. Issuers must navigate both frameworks simultaneously.

Representment failures due to reason code mismatch. A merchant may have strong evidence that would defeat the dispute under one reason code but submit evidence that is irrelevant to the code actually assigned. Because the issuing bank evaluates the representment against the specific evidentiary requirements of the assigned code, a technically valid defense can fail on procedural grounds. The reason code assignment — made by the issuer at the outset — therefore has an outsized effect on the outcome.

Provisional credit reversals. If the issuer ultimately rules in the merchant's favor after issuing a provisional credit, the credit is reversed. If the cardholder's account lacks sufficient available credit at the time of reversal, the account may go over its credit limit or reflect a balance the cardholder did not anticipate. This outcome is separate from any question of how credit utilization feeds into a score's calculation — but the mechanics interact, because a sudden balance increase affects the utilization ratio that scoring models read from the account's reported balance.

Arbitration cost asymmetry. Because network arbitration fees are assessed against the losing party, smaller disputed amounts can produce a situation where the fee exceeds the transaction value. In those cases, both the issuing and acquiring banks have a financial incentive to settle rather than escalate, regardless of the merits of either party's position.

What a Statement and Disclosure Show About a Dispute in Progress

During an open dispute, the cardholder's monthly statement reflects the provisional credit as a line item, typically labeled with language indicating the amount is under investigation or has been temporarily credited. The statement does not show the reason code assigned to the dispute, the evidence submitted by either party, or the current stage in the process. Those details exist in the issuer's internal dispute management system and in the card network's case records, neither of which is surfaced on a consumer statement.

The FCBA requires the issuer to provide written acknowledgment of the dispute and, upon resolution, a written explanation of its determination. If the issuer rules against the cardholder, the explanation must state why and must advise the cardholder of the remaining balance owed. What the written explanation does not include is the merchant's representment evidence itself — the cardholder is informed of the outcome but not necessarily shown the documentation that produced it.

A credit report does not reflect an open chargeback dispute as a distinct entry. What a credit report shows is the account's balance and payment status as reported by the issuer. Under the FCBA, the issuer may not report the disputed amount as delinquent while the dispute is open. However, if the dispute is resolved against the cardholder and the balance is reinstated, subsequent reporting will reflect that balance. A credit report reader cannot distinguish a reinstated disputed charge from any other balance — the dispute's history is not part of the tradeline.

Merchants receive a chargeback notification through their acquiring bank, not through the card network directly. The notification specifies the reason code, the disputed amount, and the deadline for representment. It does not include the cardholder's identity beyond what is necessary to identify the transaction. The acquiring bank's chargeback report to the merchant will show cumulative chargeback counts and ratios, which are the figures the card network monitors against its thresholds. Just as a returned payment can trigger fee assessments and account-level consequences that are not immediately visible on a statement, a chargeback's downstream effects on a merchant account may not be fully visible until a monthly reconciliation report is produced.

The chargeback system is a rule-bound procedure rather than a judgment process — its outcomes are determined largely by which party submits the right evidence against the right reason code within the right deadline, not by an independent assessment of the underlying facts of the transaction.

Note: This explains how credit cards work as financial systems. It is not financial advice, it is not a recommendation of any card or provider, and it is not a substitute for the CFPB's own guidance. Check the cited sources for current regulatory detail.