Payment Verdict
Risk Topics

Pre-dispute

The early window where a customer initiates a claim with their bank but a formal dispute has not yet been processed by the merchant.

Updated March 1, 2026•3 min read

A pre-dispute (or "inquiry") is a critical window of time where a customer contacts their issuing bank to question a specific charge on their statement. Unlike a formal chargeback, a pre-dispute does not immediately result in a financial reversal. Instead, the bank reaches out to the merchant via the payment platform to request more information or clarification before deciding whether a formal, financial dispute is warranted.

From a risk perspective, the pre-dispute phase is your most valuable chance for "early resolution." If you can resolve the customer's concern—often by issuing a full refund or providing clear proof of delivery—during this window, you can prevent a formal Dispute from ever being filed. This is essential because formal disputes, even if won, negatively impact your merchant account health and dispute ratios.

Proactive management of pre-disputes through automated alerts and rapid customer service response is a deterministic way to keep your dispute ratio low and maintain high "risk confidence" with your payment provider, ensuring long-term account stability.

Related reading:

Why this term matters for Stripe account risk

Pre-dispute 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-dispute 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-dispute commonly appears in the following Stripe risk scenarios:

Problems linked to this term

Topic hubs

Refunds and Disputes

How refund friction, customer dissatisfaction, and dispute growth combine into stronger payment-platform risk signals.

Related glossary terms

Dispute

A dispute is a claim that a transaction should be reversed; disputes can escalate to chargebacks and increase platform risk posture.

Retrieval Request

An inquiry from a card issuer asking for more information about a transaction before filing a formal chargeback.

Pre-Arbitration

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

Arbitration

The final and most expensive stage of the dispute process where the card network decides the outcome of a contested transaction.

Liability Shift

A change in responsibility for chargeback costs from the merchant to the card issuer, typically via 3D Secure.

Reason Code

A specific alphanumeric code assigned by a bank to explain the cause of a chargeback or dispute.

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.