Pre-Arbitration in Chargebacks: When to Fight and When to Accept

Chargebacks are a fact of life in online payments. What many merchants don’t fully prepare for, though, is what happens when a dispute doesn’t end at the first rebuttal. Pre-arbitration is that next stage, and it’s where the decision-making gets harder, the timelines get shorter, and the financial exposure starts to compound.

This piece breaks down how the pre-arbitration chargeback fits into the broader chargeback cycle, what merchants are up against when they receive one, and how to figure out whether fighting or accepting is the smarter move.

What Is Pre-Arbitration Chargeback?

Once a merchant submits a representment chargeback, the issuer bank reviews it on the cardholder’s behalf. If the bank sides with the cardholder again, it sends back a pre-arbitration chargeback, essentially a rejection of the merchant’s first rebuttal. So, what is pre-arbitration chargeback in practical terms? It’s the card network’s way of saying the dispute isn’t over yet.

Where does it fall in the chargeback timeline? After the first representment, before formal chargeback arbitration. It’s the last stage where both sides can settle things directly. If neither side backs down here, the dispute goes to the card network, that is, Visa or Mastercard, for a binding decision.

The chargeback cycle in simplified form looks like this: The cardholder files a dispute, the issuer bank initiates the chargeback, the acquiring bank passes it to the merchant, the merchant submits a chargeback response, the issuer reviews and disagrees, and a pre-arbitration notice is issued. From that point, the merchant accepts the loss or escalates. There’s no middle ground.

Why Chargebacks Move to Pre-Arbitration

Most disputes don’t get here. Some start with a retrieval request before a chargeback is even filed, giving merchants an early window to resolve things. Pre-arbitration, though, typically happens when the merchant’s representment didn’t land: The reason code wasn’t addressed cleanly, the documentation had gaps, or the cardholder came back with new information that shifted the issuer bank’s read of the situation.

Reason codes are worth paying attention to throughout this process. Each one defines the nature of the cardholder dispute and sets the terms for what a valid rebuttal looks like. A chargeback response that answers the wrong question or answers the right question with weak evidence gives the issuing bank every reason to push it back.

Merchant Options at the Pre-Arbitration Stage

Two paths come forward: Contest the dispute with a new chargeback response, or accept the loss. Neither one is consequence-free.

Contesting means going through the dispute documentation again: What was submitted the first time, what the issuer is now saying, and whether there’s anything stronger to put forward. The chargeback timeline here is unforgiving. Each dispute stage carries its own dispute deadline, and card networks typically allow around 30 days to respond. That window closes whether the merchant is ready or not.

Accepting means absorbing the loss and moving on. That might sound like giving up, but in some cases it’s the correct call. The merchant chargeback dispute process costs time and internal resources at every stage, and those costs are real, even when a merchant eventually wins.

Fraud-Related Disputes

Fraud-related disputes make up a substantial portion of chargeback volume, but they are not a single category of problem. Visa separates them into conditions covering unauthorized use, EMV liability shifts for counterfeit and non-counterfeit fraud, and exposure to Visa’s fraud monitoring program. Each condition triggers different documentation requirements.

Friendly fraud, where a legitimate cardholder disputes a transaction they actually authorized, is now a significant driver. Visa’s fraud report data shows that 64% of merchants report an increase in first-party misuse. Combined with third-party fraud, Mastercard’s state-of-chargebacks research puts fraudulent disputes at roughly 45% of total merchant chargeback volume. With 63% of merchant transactions being digital purchases, card-not-present fraud continues to dominate.

When It Makes Sense to Fight a Chargeback

Fighting a chargeback at the pre-arbitration level is defensible when the evidence is genuinely strong. Some of the situations where pushing back tends to make sense include:

1. The merchant holds compelling evidence that directly addresses the reason code, like delivery records, authentication logs, signed confirmation, or documented customer communication.
2. The transaction went through, the order was fulfilled, and the cardholder still filed. That’s friendly fraud, and it’s worth pushing back on.
3. The transaction value is high enough that losing it would meaningfully affect the business.
4. There’s no prior dispute history issue that would make a second rebuttal risky from a monitoring standpoint.

Knowing how to win a chargeback dispute at this stage isn’t about volume of paperwork. It’s about relevance. The second rebuttal needs to address what the issuer said in the pre-arbitration notice, not just restate what was in the first response.

When Accepting the Dispute Is the Better Option

There’s a version of chargeback defense where a merchant fights every dispute on principle. It rarely ends well. Some cases genuinely aren’t worth continuing, and it’s useful to be able to spot them early. Consider accepting the loss when:

• the disputed amount is small, and the cost of another rebuttal round eats into any realistic recovery;
• the evidence used in the first representment was the best available, and nothing has changed;
• the reason code points to a merchant liability issue with no clean counter-argument;
• losing at formal chargeback arbitration would mean paying an arbitration fee that exceeds the original chargeback amount.

That last scenario is worth spelling out. When a dispute reaches arbitration, and the merchant loses, the card network charges an arbitration fee, often $500 or more, on top of the original payment reversal. On a $200 transaction, that math doesn’t work. Appeal credit card dispute cases only when the numbers make sense.

Best Practices for Managing Pre-Arbitration Disputes

Strong chargeback defense at the pre-arbitration stage starts well before a pre-arbitration notice ever arrives. Below are a few things that make a practical difference.

Keep dispute documentation organized by reason code from the beginning, not after things escalate. When a pre-arbitration notice comes in, having evidence already sorted by dispute type saves time that merchants usually don’t have.

Monitor the chargeback timeline actively. Setting internal deadlines a week before card-network deadlines is a simple safeguard. One missed response window hands the case to the cardholder automatically, regardless of the merits.

After every lost dispute, look at where the rebuttal fell short. That review is how to respond to chargeback notices more effectively the next time, and it tends to surface patterns that aren’t obvious on a case-by-case basis.

Upstream, a solid chargeback prevention solution reduces how often these decisions come up in the first place. Fewer disputes in the system means fewer pre-arbitration calls to make.

How to Decide Whether to Fight or Accept a Chargeback

There’s no universal answer on whether to continue a merchant chargeback dispute at the pre-arbitration stage. The honest answer is that it depends on the case: the evidence, the transaction value, the reason code, and how much the business can absorb if dispute escalation goes against it. Having a clear dispute strategy before that notice arrives makes the decision a lot less reactive.

What holds consistently: Merchants who treat pre-arbitration as a real decision point, rather than defaulting to “always fight” or “always accept”, tend to protect more revenue over time while keeping dispute costs in check.

For businesses handling high dispute volumes or dealing with recurring escalation patterns, Merchanto’s chargeback protection service provides the structure needed to make those calls efficiently, every time.