Chargeback pre-arbitration is a post-representment stage in which the dispute is renewed or contested after the first defense was reviewed. Your actual options may be to submit another response, accept or decline the case, contact your provider, or take no action at all. The live case workflow—not the stage name—controls what the merchant can do.
Start with the availability gate
Do not assume that seeing “pre-arbitration” creates a merchant right to escalate. Provider implementations differ even when they use similar card-network terminology.
| Documented platform example | Merchant-facing action | Operating boundary |
|---|---|---|
| Adyen | Some eligible flows can expose accept or decline. | The choice requires a supported flow, configuration, and Adyen approval. A decline can proceed to scheme arbitration. |
| Shopify Payments | A renewed dispute after an initial win can return to the Chargeback response form for the strongest evidence. | Use the deadline and fields shown on the order. The initial win does not guarantee the next result. |
| Stripe | Stripe documents the normal issuer decision as final in its platform. | Stripe does not support merchant escalation to arbitration through its platform. |
Copy the exact status, available buttons, deadline, reason, new issuer material, and provider instructions into the case record. If the workflow offers no merchant action, stop the decision model and follow the provider's support route.
Run four gates before calculating value
Confirm whether this case permits a response, an accept-or-decline choice, provider review, or no merchant action.
Identify the new issuer claim or evidence. Do not resend the first packet unchanged.
Verify the original response, required documents, submission time, and proof of receipt before relying on a rebuttal.
Model only case-specific recoverable value, remaining work, fixed escalation cost, and adverse-outcome cost.
Answer the new claim, not the old reason code
The reason code explains the dispute category; the pre-arbitration material explains why the first defense did not end the case. Build a delta log before choosing an action.
| Delta question | Record to capture | Decision effect |
|---|---|---|
| What is newly alleged? | Issuer comments, cardholder statement, or new document | Defines the rebuttal that must be answered directly. |
| What did the first packet establish? | Submitted response and provider confirmation | Prevents repetition and exposes any unsupported assumption. |
| Was required evidence omitted? | Reason-specific requirement list and original file set | May make the case unsuitable for escalation if the applicable rules do not allow the omission to be repaired later. |
| Is the new proof admissible now? | Live form fields and provider guidance | Separates a usable rebuttal from internal context only. |
Mastercard's current merchant guide repeatedly distinguishes a rebuttal that addresses the pre-arbitration material from documents that should have been supplied at second presentment. It also states in multiple flows that required earlier documentation might not be considered if first added later. Treat that as a record-quality gate, then follow the processor's case instructions for the transaction in front of you.
Use expected incremental value only when a choice exists
- Pkeep — probability that value is retained: estimate from mature internal cases with the same provider, network, stage, reason, and evidence pattern.
- R — recoverable amount: use only the value that the live case and contract say can return or remain with the merchant.
- Padverse — probability of adverse escalation cost:estimate separately from Pkeep because a case can close without both outcomes occurring as simple opposites.
- A — contract-specific adverse cost: include only a documented cost triggered by the adverse escalation outcome.
- H and F — remaining handling and fixed escalation cost:count future analyst/reviewer work and any fixed amount triggered by the choice. Exclude sunk costs shared by accepting and contesting.
When you do not have a reliable internal probability range, do not borrow a provider's portfolio-wide result. Record the case as needing specialist judgment and use the inequality below only to show what the evidence would need to overcome.
Contesting has positive modeled value only when Pkeep × R is greater than Padverse × A + H + F. Passing that threshold does not create a response right or predict a network decision.
Worked example: when the range crosses zero
Use normalized ledger units when a public example should not imply a provider price. This hypothetical case has 100 units of recoverable value, 60 units of documented adverse-outcome cost, 8 units of remaining handling, and 5 units of fixed escalation cost. The probabilities are illustrative scenario inputs, not benchmarks.
| Scenario | Pkeep | Padverse | Expected incremental value |
|---|---|---|---|
| Conservative | 20% | 60% | 20 − 36 − 8 − 5 = −29 units |
| Working | 45% | 40% | 45 − 24 − 8 − 5 = 8 units |
| Upper | 65% | 20% | 65 − 12 − 8 − 5 = 40 units |
The range runs from −29 to 40 units. That does not support an automatic accept or contest rule. Route the case to the named dispute specialist, verify the contract costs and the evidence delta, and save the approved judgment with the case.
Use a three-way operating rule
- Accept: the claim is valid, the workflow does not allow a response, the original record has a fatal gap, or every reasonable scenario is negative.
- Respond or decline: the live workflow permits it, the claim appears invalid, the delta is directly rebutted, the original record is complete, and all reasonable scenarios are positive.
- Escalate internally: the value range crosses zero, a cost or deadline is unverified, or the merchant-facing action is unclear. Internal escalation means a named reviewer—not an assumption that network arbitration is available.
Pre-arbitration case-record checklist
- Exact provider status and merchant-facing action
- Case deadline, internal cutoff, owner, and backup owner
- Network, processor, region, reason, and transaction type
- Original response file, submission time, and confirmation
- New issuer claim or evidence copied into a delta log
- Rebuttal record mapped to each new point
- Contract source for fixed and adverse-outcome costs
- Low, working, and high scenario inputs with approver
- Final action, submission receipt, and mature outcome
Limitations to keep visible
Card-network guides often describe issuer and acquirer rights rather than a button a merchant can press. Visa's merchant guidance also notes that rules can vary by region and dispute condition. Availability, deadlines, evidence fields, cost exposure, and escalation rights must therefore come from the current processor or acquirer workflow and the merchant's contract.
This framework does not provide a universal fee, deadline, win rate, or recommendation to arbitrate. Adyen's documented fee exposure is one provider example, not a portable price. Shopify's response flow and Stripe's no-arbitration boundary are also platform-specific. The issuer, applicable network process, or other authorized decision-maker controls the outcome.
For the first response decision, use the guide to fight or accept a chargeback. When a response is appropriate, build a reason-matched evidence packet. If the event has not yet become a formal dispute, compare alerts and representment.
Check what the live case allows, isolate what changed, verify the original record, and model only documented incremental economics. When any of those four gates fails, do not automate the response.