Category: Chargebacks and Disputes

Pre-Dispute Inquiry

Also known as: Inquiry, Pre-Dispute Solution, Preliminary Dispute Phase

Simply put

A pre-dispute inquiry is a preliminary step that some card networks use before a formal chargeback is created, giving the merchant and processor a chance to respond to a cardholder's question or concern about a transaction. It is intended to help resolve issues earlier, potentially avoiding a full dispute. The specific handling and terminology vary by card network and by the processor or platform involved.

Formal definition

A pre-dispute inquiry is an optional preliminary phase offered by certain card networks that precedes the creation of a formal dispute and chargeback. As described in payment platform documentation, this phase (referred to by some processors as an 'inquiry') allows a transaction to be reviewed or contextualized before it escalates to a chargeback, which is the mechanism by which merchants must otherwise pursue representment to recover revenue. Pre-dispute solutions are intended to reduce chargeback volume and the associated operational burden of representment, though availability, workflow, and outcomes depend on the specific card network rules and the processor implementation, which vary by network and region. Note that the term applies to payment card disputes and is distinct from consumer credit report disputes filed with credit bureaus under separate legal frameworks.

Why it matters

Chargebacks impose a significant operational and financial burden on merchants. As described in payment platform and industry documentation, dispute representment—the process of responding to chargebacks to recover revenue—places significant demand on merchants' internal resources. A pre-dispute inquiry offers a preliminary window in which a cardholder's question or concern can be reviewed or contextualized before it escalates into a formal dispute and chargeback, which is the mechanism merchants must otherwise use to pursue representment. Resolving an issue at the inquiry stage may reduce chargeback volume and the associated workload.

Because pre-dispute handling and terminology vary by card network and by the processor or platform involved, merchants and their teams should not assume a uniform workflow across networks or regions. What one processor calls an 'inquiry' may be handled differently elsewhere, and availability and outcomes depend on the specific network rules and the processor's implementation. Treating a pre-dispute inquiry as a guaranteed off-ramp from every chargeback would overstate its effect; it is intended to help resolve certain issues earlier, not to eliminate disputes.

It is also important to distinguish this term from consumer credit report disputes. A pre-dispute inquiry concerns a payment card transaction between a cardholder, merchant, and their processors and networks. It is separate from disputes filed with credit bureaus over inaccurate credit report information, which are governed by distinct legal frameworks and processes and are out of scope for payment dispute management.

Who it's relevant to

Merchant Risk and Dispute Teams

Teams responsible for handling cardholder disputes benefit most directly, since resolving a concern during a pre-dispute inquiry may avoid a full chargeback and the resource-intensive representment process. They should understand how their specific processor and the relevant card networks define and handle the inquiry phase, as workflows vary.

Payment Processors and Platforms

Processors and platforms implement and surface pre-dispute inquiries to merchants, and their terminology may differ—one platform, for example, refers to this preliminary phase as an inquiry. Their implementation determines how the phase appears in merchant workflows and what responses are possible before a formal dispute is created.

Acquirers

Acquirers sit between merchants and card networks in the dispute lifecycle and are affected by how pre-dispute phases route and resolve transactions. Because network rules and regional variation shape these processes, acquirers should track the applicable network requirements rather than assume uniform handling.

Fraud Analysts

Analysts investigating disputed transactions may use the pre-dispute inquiry phase as an opportunity to review or contextualize a transaction before it escalates. It is one input into distinguishing legitimate concerns from potential fraud, but it does not by itself determine the nature of a dispute.

Inside Pre-Dispute Inquiry

Transaction Identification Data

Details used to locate the disputed transaction, such as authorization code, transaction date and amount, and merchant reference or order identifiers. This data helps the merchant match the inquiry to a specific sale before a formal dispute is opened.

Cardholder Concern or Reason

A description of why the cardholder or issuer is questioning the transaction, for example an unrecognized charge or a suspected billing error. Note that a pre-dispute inquiry is intended to gather clarification and is distinct from a formal chargeback, which is governed by card brand and network rules that vary by region and change over time.

Supporting Documentation Request

A request for evidence the merchant can supply to explain or substantiate the transaction, such as proof of delivery, order records, or a descriptor explanation. Any records exchanged should follow data handling controls, and sensitive authentication data (such as full track data, CAV2/CVC2/CVV2/CID, or PIN blocks) must not be included, as it must not be stored after authorization.

Response Window

A timeframe within which the merchant is expected to respond to the inquiry. Specific timeframes are defined by the applicable card brand or network program and may differ by region and version of the rules, so practitioners should confirm against the current published program requirements.

Merchant Descriptor Information

The billing descriptor and merchant details that appear to the cardholder. Unclear descriptors are a common driver of inquiries, and clarifying them may help reduce escalation to a formal dispute, though it does not guarantee resolution.

Common questions

Answers to the questions practitioners most commonly ask about Pre-Dispute Inquiry.

Is a pre-dispute inquiry the same thing as a chargeback?

No. A pre-dispute inquiry is an informational or resolution step that occurs before a formal dispute (chargeback) is initiated, and it does not by itself move funds or assign liability. A chargeback is a formal reversal governed by card brand and network rules. Treating an inquiry as if it were an already-filed chargeback can lead you to respond incorrectly or miss the opportunity to resolve the matter before it escalates. Confirm the specific handling, timelines, and terminology against the current rules of the relevant card brand and region, as these vary and change.

Does resolving a pre-dispute inquiry guarantee that no chargeback will follow?

No. Successfully addressing an inquiry may reduce the likelihood that a formal dispute is filed, but it does not guarantee that a cardholder or issuer will not proceed to a chargeback. The inquiry and the subsequent dispute are governed by card brand and network rules, and the cardholder generally retains defined dispute rights. Use qualified expectations: an inquiry response is intended to help resolve or clarify a transaction, not to eliminate all downstream dispute risk.

What transaction information should be gathered when responding to a pre-dispute inquiry?

Assemble the records that substantiate the transaction and delivery or service, such as order details, authorization data, and any communications with the customer. When handling this data, avoid retaining or exposing sensitive authentication data, which must not be stored after authorization even when encrypted. Any cardholder data included in the response should be minimized, and where appropriate masked or truncated, consistent with applicable data-protection controls under the current PCI DSS. Confirm the exact evidence expected against the relevant network's inquiry process.

How should pre-dispute inquiry handling be reflected in data retention and PCI DSS scope?

Retain only the data you need to resolve the inquiry and for the period justified by business and legal requirements, and apply defined controls to any stored cardholder data. Where inquiry evidence includes card data, techniques such as truncation or masking may reduce exposure, but their effect on scope depends on implementation and validation, not on the label alone. Sensitive authentication data must not be stored post-authorization. Validate your retention and protection practices against the current published PCI DSS rather than assuming a fixed requirement number.

Who within a merchant or processor organization typically handles pre-dispute inquiries, and how should the workflow be structured?

Handling commonly involves merchant risk, dispute or chargeback operations, and sometimes customer service teams, often coordinating with the acquirer. A practical workflow includes intake of the inquiry, timely gathering of supporting records, a decision to resolve or contest, and documentation of the outcome. Because timelines and required actions are set by card brand and network rules that vary by region, build the workflow around the applicable network's stated deadlines and confirm them against current documentation.

How does a pre-dispute inquiry relate to fraud detection and to distinguishing fraud types?

An inquiry can surface signals relevant to distinguishing, for example, unauthorized card-not-present fraud from friendly or first-party fraud, but the inquiry itself is not a fraud-detection control and does not adjudicate the fraud type. Any conclusions drawn are subject to false-positive and false-negative trade-offs and depend on the evidence available. Liability outcomes tied to the transaction are ultimately governed by card brand and network rules, which vary by region and change over time.

Common misconceptions

A pre-dispute inquiry is the same as a chargeback.

A pre-dispute inquiry is an information-gathering step that occurs before a formal dispute is initiated. A chargeback is a separate, formal reversal process governed by card brand and network rules, which vary by region and change over time. Responding to an inquiry may help avoid a chargeback but is a distinct process.

Responding to a pre-dispute inquiry guarantees the merchant keeps the sale.

Providing a timely, well-documented response is intended to help clarify the transaction and may reduce the likelihood of escalation, but it does not guarantee any outcome. Whether a matter proceeds to a formal dispute depends on the cardholder, issuer, and the applicable network rules.

Any transaction record can be attached to an inquiry response.

Documentation should be limited to what is needed to substantiate the transaction and must follow data protection controls. Sensitive authentication data such as full track data, CVV2/CVC2/CAV2/CID, and PIN blocks must not be stored after authorization and must not be included, while cardholder data should be masked or truncated where full values are not required.

Best practices

Confirm the response window and required content against the current published card brand or network program rules, since timeframes and requirements vary by region and change over time.

Maintain readily retrievable transaction records (authorization code, date, amount, order and delivery details) so inquiries can be matched and answered promptly within the applicable window.

Exclude sensitive authentication data from any inquiry response, and mask or truncate cardholder data such as the PAN so that only what is necessary to substantiate the transaction is shared.

Use clear, recognizable billing descriptors to reduce cardholder confusion, which may help lower the volume of inquiries and their escalation to formal disputes.

Track and analyze inquiry patterns to identify recurring root causes, understanding that this analysis supports process improvement rather than eliminating fraud or disputes.

Document the inquiry handling process and retain evidence in line with your data retention and PCI DSS obligations, confirming controls against the current published standard.