How Do Chargebacks Work?

The Chargeback Process at a Glance

Every chargeback follows the same broad arc: a cardholder questions a transaction, the issuing bank reviews the claim, the dispute travels through the card network to the merchant's acquirer and processor, and the merchant either accepts the reversal or responds with evidence. The issuer then weighs that response, and if the parties still disagree, the case can escalate to pre-arbitration or arbitration under network rules.

Before walking through each step, one caution: not every card network, processor, issuer, or reason code follows an identical sequence. Visa and Mastercard use different case flows, terminology, and timelines, and processors layer their own portals and cutoffs on top. Treat the steps below as the common shape of the process, and confirm the specifics of any individual case with your processor or acquirer.

Step 1: The Customer Questions the Transaction

The process starts when a cardholder contacts their bank — by phone, in an app, or online — about a charge they believe is unauthorized, unrecognized, incorrect, or unfulfilled. Some banks make this remarkably easy, presenting a "dispute this charge" button next to every transaction.

At this moment the case is still just a claim. Depending on the issuer and network, the inquiry might be answered on the spot (for example, when the bank helps the customer recognize a billing descriptor), routed into a pre-dispute program, or filed as a formal dispute. Not every inquiry becomes a chargeback — and the earlier a merchant can engage, the better the outcome tends to be. If you are new to the terminology, start with what a chargeback is.

Step 2: The Issuer Reviews the Cardholder's Claim

The issuing bank evaluates the claim against network rules. It checks whether the dispute type is valid, whether it falls within the allowed timeframe, and what the cardholder is actually asserting. The issuer then assigns a reason code — a network-defined label such as fraud, item not received, or canceled recurring — that will govern the case from this point forward.

The reason code matters because it determines what the cardholder must show, what the merchant may submit in response, and which deadlines apply. The same underlying situation can produce different codes at different issuers, which is why merchants should always read the code on each case rather than assume. The Reason Codes directory explains how the major networks organize their codes.

In many cases the issuer also gives the cardholder a provisional credit while the dispute is investigated.

Step 3: The Dispute Reaches the Acquirer or Processor

Once the issuer files the dispute, the card network routes it to the merchant's acquiring bank, which passes it to the payment processor. At this stage the disputed funds are debited from the merchant's settlement account, and a chargeback fee is typically assessed.

The dispute is now recorded against the merchant's ratios — a fact that does not change even if the merchant later wins the case. This is one of the most misunderstood points in chargeback management: winning representment recovers the funds, but the dispute still counts toward network monitoring thresholds. Prevention and pre-dispute resolution are the only ways to keep a case out of the count entirely.

Step 4: The Merchant Reviews the Case

The processor notifies the merchant, usually through a dispute portal or API, with the case details: the reason code, the disputed amount, the transaction reference, and the response deadline. The merchant's first job is to match the dispute to its own records — the original order, the authorization result, delivery confirmation, customer communication, and any refunds already issued.

This matching step is where well-organized merchants pull ahead. If the transaction, fulfillment, and customer-service history are already connected, evaluating a case takes minutes. If records live in five disconnected systems, each case becomes an investigation, and deadlines start to slip.

Step 5: The Merchant Accepts or Responds

For each case, the merchant has a decision to make:

• Accept the chargeback. If the dispute is legitimate — genuine fraud, an order that truly failed — accepting is the honest and economical choice. The merchant absorbs the loss and avoids spending effort on a case it should not win.
• Respond with evidence. If the transaction was valid and the records support it, the merchant contests the chargeback through a process called representment.

The right choice depends on the case: the reason code, the strength of the evidence, the amount at stake, and the cost of responding. Merchants who fight everything waste resources and can damage credibility with their acquirer; merchants who fight nothing surrender legitimate revenue and invite repeat abuse.

Step 6: Representment Evidence Is Submitted

In representment, the merchant submits a response package through its processor: a rebuttal addressing the specific reason code, plus supporting records — authorization data, order details, proof of delivery, customer communication, refund history, and any other documentation the code calls for.

What counts as persuasive evidence varies by network, reason code, and the facts of the case. A fraud dispute calls for very different proof than a "not as described" claim. Our guide to chargeback representment and evidence covers how to build a response case by case.

Merchant response options also depend on the case itself — some disputes offer limited response paths, and some evidence types only apply to specific claims.

Step 7: The Issuer Reviews the Response

The issuer examines the merchant's evidence and decides whether the dispute stands. If the evidence is convincing, the chargeback is reversed and the funds return to the merchant. If the issuer maintains the dispute, the reversal stands.

Either way, the decision usually takes weeks rather than days, and the timeline varies by network and case type. Merchants should track outcomes by reason code and case type — win-rate data is one of the most useful inputs for deciding which future cases are worth contesting.

What Happens During Pre-Arbitration or Arbitration?

If the issuer rejects the merchant's representment and the merchant (through its acquirer) still believes the case is wrong, the dispute can escalate. Networks provide a pre-arbitration stage, where the parties exchange positions once more, and finally arbitration, where the card network itself rules on the case.

Escalation is expensive: networks charge significant fees to the losing party, and the standards of review are strict. In practice, most merchants only escalate cases with clear-cut evidence and meaningful amounts at stake. Acquirers and processors typically advise on whether escalation is realistic for a given case.

Where Pre-Dispute Alerts Fit Into the Process

Everything described so far happens after the dispute is formally filed. Pre-dispute programs operate earlier — in the window between the cardholder's complaint and the chargeback itself.

Services built on Verifi and Ethoca data can notify the merchant when a cardholder disputes a transaction, before the case becomes a chargeback. The merchant can then refund the eligible case, stop pending fulfillment, and resolve the matter without a chargeback being counted. Some programs, such as Rapid Dispute Resolution, resolve eligible cases automatically according to rules the merchant configures.

Pre-dispute resolution is the single most direct way to keep an avoidable dispute out of the merchant's ratios — but alerts only help when they are answered quickly and with full payment context. That is the problem chargeback alerts programs and AlertBridge™ are designed to solve.

How Long Does the Chargeback Process Take?

There is no single universal deadline for all disputes, and any resource that publishes one should be treated with caution. Timelines depend on the card network, the reason code, the dispute stage, and the processor's own internal cutoffs, which are often earlier than the network deadline to allow processing time.

As a general shape: cardholders typically have a window measured in months from the transaction (or expected delivery) to dispute; merchants typically have a window measured in days to weeks to respond to a chargeback; and full resolution of a contested case commonly takes one to several months, longer if it escalates. For any specific case, the deadline shown by your processor is the one that matters — and responding early is always safer than responding at the deadline.

How Merchants Can Build a Better Chargeback Workflow

The merchants who handle disputes well treat the process as a repeatable workflow rather than a series of emergencies:

• Centralize the data. Connect gateway transactions, orders, fulfillment, refunds, alerts, and disputes so every case arrives with context. If you process through multiple gateways or MIDs, unify the view.
• Act at the pre-dispute stage. Resolve eligible cases before they become chargebacks, and reconcile refunds so a resolved case never turns into a duplicate credit.
• Triage deliberately. Accept the cases you should lose; contest the ones the evidence supports.
• Standardize evidence. Keep authorization, delivery, and communication records organized so representment packages assemble quickly.
• Track outcomes. Measure win rates by reason code and feed what you learn back into prevention — the subject of our guide on preventing chargebacks.

Payment Defender's platform is built around this workflow: AlertBridge™ for the pre-dispute window, Transaction Proof™ for evidence, and Chargeback Shield™ for organized, on-time responses. Contact Payment Defender to see how it fits your dispute volume.