Chargeback, Dispute, or Inquiry? A Plain Guide for Sellers

If you sell online long enough, you'll run into the vocabulary of payment disputes — chargeback, dispute, inquiry, representment, reason code. The terms get used loosely, which makes a stressful situation more confusing than it needs to be. This is a plain-language explainer so you can read a notice clearly and organize the right records.

Two notes up front. First, this is general education, not legal, financial, or payment-processor advice. Second, nothing here changes who decides an outcome — that's your payment provider and the card networks. Understanding the terms just helps you respond clearly.

The core idea

When a customer questions a charge, it travels back through a chain: the customer's card issuer (their bank), the card network, and then your payment provider (such as your processor or platform), which notifies you. Different stages and providers use different words for it.

The terms you'll see

Inquiry / retrieval request. Sometimes the first step is a request for more information rather than a formal reversal. It's an opportunity to provide records early — and the words and process vary by provider.

Dispute. A broad term for a customer formally questioning a charge. Many platforms simply call the whole thing a "dispute."

Chargeback. The mechanism by which a charge is reversed through the card network at the customer's bank's instruction. Often used as a catch-all, but technically it's the reversal itself.

Reason code. A short code the card network attaches that describes why the charge is being questioned — for example, a delivery-related reason like "merchandise not received." The reason code tells you which records matter.

Response / representment. The stage where you submit your records back through your provider. You're presenting evidence; you are not the decision-maker.

Why the distinctions matter to you

You don't need to memorize the taxonomy. You need two things from any notice:

1. The reason — so you know which records to organize. A "not received" reason points to tracking and delivery proof; a different reason would point to different records.
2. The deadline — the date by which your response must be submitted. Miss it and the records never get seen.

Everything else is vocabulary.

What stays the same across all of them

Whatever the notice is called, your job is the same: organize the genuine records you already have into a clear, indexed package — order details, the shipping timeline, delivery confirmation, the policy in effect at purchase, and customer communication — and submit it yourself through your provider before the deadline.

And whatever it's called, the same boundaries apply. Organizing evidence clearly is legitimate and useful. Creating, altering, backdating, or hiding records is not — and it undermines your own credibility.

Where to go next

If you're staring at a delivery-related notice right now, start with the records: our guide on responding to an "item not received" dispute walks through exactly what to gather, and the free Delivery Dispute Checklist is a one-page starting point. For provider-specific pointers, see the dispute guides by payment provider — Stripe, PayPal, Shopify Payments, and more.

Merchant Casefile provides organizational tools and educational resources. It does not provide legal, financial, banking, or payment-processor advice, and does not guarantee dispute outcomes.