Pre-Arbitration

A phase in the dispute process where an issuer challenges a merchant's second presentment.

Updated March 1, 20263 min read

Pre-Arbitration, often referred to as a "Second Chargeback," is a sophisticated phase in the Dispute lifecycle that occurs after a merchant has successfully challenged an initial claim. It happens when the cardholder's bank (Issuer) rejects the merchant's second presentment and insists on a final resolution.

This stage is a high-severity signal of a persistent dispute. In the deterministic world of payment risk, entering pre-arbitration means the dispute has moved beyond simple clerical errors and into a fundamental disagreement over fulfillment or authorization. Merchants should only proceed to the final Arbitration stage if their Evidence Packet contains indisputable proof of delivery or Liability Shift. Losing at the arbitration level carries extremely heavy network fines (often $500+) and can permanently damage the merchant's standing with their Merchant Acquirer.

Why this term matters for Stripe account risk

Pre-Arbitration is not only a vocabulary item. It is a live risk signal that influences how Stripe evaluates dispute exposure, payout predictability, and verification confidence for your account. When this signal appears together with abnormal refund velocity, delivery uncertainty, or weak policy disclosures, account controls can become stricter. Treat Pre-Arbitration as an operational metric that should be monitored, documented, and explained with evidence.

Diagnostic signals to review weekly

  • Track trend direction, not just a single snapshot. A persistent rise is more important than one isolated spike.
  • Compare this signal with fulfillment timing, support response speed, and billing clarity to identify root causes.
  • Document the exact trigger conditions so your team can reproduce, audit, and resolve the issue consistently.
  • Escalate early when this term appears alongside dispute-heavy reason codes or repeated verification requests.

Practical actions to improve confidence

  1. Define an internal threshold and owner for this signal so actions are not delayed.
  2. Link this signal to a checklist in your operations workflow (checkout, fulfillment, support, and evidence retention).
  3. Update website disclosures and receipts so customer expectations match real delivery and billing behavior.
  4. Keep a short incident log with timeline, root cause, and remediation to support future platform reviews.

Further reading

Where This Appears

Pre-Arbitration commonly appears in the following Stripe risk scenarios:

Related glossary terms

Move from definitions to diagnosis

Once the term makes sense, use the problem library and operational guides to see how it creates real Stripe account pressure.