How should my business respond to a card-payment dispute?

When a card-payment dispute arrives, verify the notice through your established payment-provider channel, identify the exact transaction and reason, and record the actual response deadline. Reconcile any debit, fee or prior refund. Then decide whether the evidence supports a truthful response or another appropriate resolution, following the applicable process.

I would give the case an owner immediately. Not because every dispute should be fought, but because an unassigned notice can become an expired opportunity to respond. The useful first move is to understand this case, not label the customer dishonest.

Read the case before reacting

Identify the payment reference, amount, currency, transaction date, customer order and dispute reason. Confirm whether the notice concerns an inquiry, a debit already made, a request for evidence or a later decision. Keep those states separate.

Read the actual instructions for this transaction, network and provider. Record the deadline with its time zone, the submission route, required format and any limits. A deadline mentioned in a general online guide is not necessarily the deadline on your case.

The Visa dispute overview describes merchant evidence such as receipts, shipping records and customer communications passing through the acquiring bank for review. It also distinguishes temporary action from a decision. Use your actual provider's case instructions rather than treating a broad overview as a complete rulebook.

Verify an unexpected message through the contact route you already trust. Do not upload customer records or pay an urgent charge through an unfamiliar link merely because it uses a card-network logo. The real case should be identifiable in the appropriate established process.

Reconcile the money first

Check the original charge and settlement, processing fees, disputed amount, any current debit and dispute fee. Look for prior partial or full refunds and any separate customer payment. Preserve references linking those events to the same transaction.

A customer refund and a dispute debit can involve the same underlying purchase without being the same payment event. Before issuing another refund, establish the current case state and the provider's process so you do not accidentally return the same amount twice. This does not make a valid customer remedy optional.

Do not count an amount as restored until the actual credit is supported and available. A submitted response, an acknowledgment and a favorable decision can occur at different times. Your cash plan needs the supported receipt date, not the date you hope the case will end.

The existing processing-quote guide compares fees for a defined ordinary payment record. It explicitly excludes disputes in that case. This guide follows the separate resources and evidence a particular dispute can require.

Match the evidence to the question

Recover the actual order, description shown to the buyer, authorization and payment records available to you, delivery or service evidence, applicable terms and relevant communications. Preserve their original dates and identities. Do not edit a record to make it look contemporaneous or create a customer acknowledgment that never happened.

Ask what each item establishes. A carrier record may support delivery at a particular place without proving every claim about condition, authorization or description. A signed attendance sheet can support attendance without proving that an entirely different promised service was provided.

Respond to the actual reason. If the dispute concerns nonreceipt, explain the relevant fulfillment evidence and any known gap. If it concerns a duplicate charge, reconcile both payment references. If the description or service was wrong, investigate that fact rather than burying it under a large attachment bundle.

Separate supported facts, the customer's account and unresolved questions. A short chronology that points to the right records is easier to assess than an accusation. Include only relevant information through the authorized route and protect unrelated customer or employee data.

Work through the cash exposure

Consider an entirely fictional merchant and one $900 card purchase. The customer has disputed receipt of the goods. The merchant's records contain a completed order and a carrier delivery record, but no decision has been made about the dispute. The case below does not establish fraud, customer fault or a successful defense.

The original processing fee is $27, leaving $873 actually deposited. The merchant paid $320 for materials, $180 for five fulfillment hours at an all-in $36, and $40 for shipping. Complete fulfillment payments total $540. The fee is separate from that amount.

Opening cash assigned to this case is $800, excluding household funds and other business obligations. After receiving $873 and paying $540, the case has $1,133. All these events are supplied completed events inside the fiction, not actual merchant reporting.

Now assume the provider debits the full disputed $900 and a $20 dispute fee before the response. These are this example's terms, not universal network fees or timing. The $920 debit leaves $213.

Scroll horizontally if needed. Response costs are funded even if the merchant receives no recovery.

The response requires two and a half paid hours at $36, costing $90. Those hours are available after accepted work and cover evidence retrieval, checking and submission. They do not include an outside advocate, legal case or later appeal. If any further work is proposed, it needs its own scope and resources.

The plan can make every modeled payment, but it ends with $123 before any recovery. If the owner wants to preserve a $150 case reserve, it misses that chosen target by $27. That reserve is an internal preference, not a bank minimum or regulatory requirement.

Test recovery and no recovery separately

Under a conditional favorable branch, assume a later final decision leads to an actual $900 credit. The original processing fee and $20 dispute fee remain charged under the supplied terms. With no additional case costs, cash becomes $1,023: the $123 remaining plus $900 restored.

That is $223 above the original $800. It agrees with $900 of customer funds less $27 processing, $540 fulfillment, $20 dispute fee and $90 response work. This is a bounded cash case, not the profit of the entire business.

Under a no-recovery branch, cash remains $123. Relative to the assigned $800, the reduction is $677. That equals the $540 fulfillment, $27 original processing, $20 dispute fee and $90 response work. The refunded purchase amount is no longer retained.

There is no probability estimate in either branch. A carrier record does not supply one, and a provider's acceptance of an evidence upload is not a favorable decision. The business needs to fund the case without treating possible recovery as current cash.

Now reduce the opening assignment to $650, keeping every other event unchanged. After settlement and fulfillment it has $983; the $920 dispute debit leaves $63. The $90 response task would then have a $27 funding gap. The merchant needs an actual way to cover that work or a different supported plan, not an assumed victory to pay for the response.

Prepare an honest response

In the fictional case, suppose the verified notice arrives December 10, 2027, and states a response deadline of December 17, 2027, at 6 p.m. Pacific time. Those dates are invented case terms. They are not a claim about any network's standard response period.

The assigned person records the deadline, gathers the actual evidence and checks whether it answers the stated nonreceipt issue. The person might identify a carrier delivery record but discover that the address differs from the accepted order. That discrepancy deserves investigation; it should not be omitted because it weakens the preferred story.

If the evidence supports a response, organize it by transaction and reason. State what was ordered, what fulfillment evidence exists, what the customer reported and what remains unresolved. Submit through the actual required channel and retain the exact submission and confirmation.

If the facts instead support accepting the dispute or another remedy, follow the provider's applicable process and reconcile the result. Do not invent evidence to preserve a sale. Avoid threatening a customer with unsupported accusations or remedies.

Close the record on evidence

After submission, keep a follow-up owner and status. Check requests for further information and any supported decision. Record the actual funds movement and reconcile it to the payment account and books. Mark whether any fee was returned under the real terms.

If a separate refund is proposed while the dispute remains open, coordinate through the established process. In the main fictional cash branch, paying another $900 from the remaining $123 would create a $777 shortfall. That calculation illustrates why payment events must be reconciled; it does not authorize withholding an amount legitimately due.

Once the case is resolved, preserve the relevant records under the actual retention and privacy requirements. Do not retain unnecessary sensitive material simply because it was gathered in a hurry. Establish what can be removed and who is authorized to do so.

Then examine any operating problem the case reveals. A confusing description, missed delivery or poorly recorded refund deserves correction even if the merchant ultimately receives the funds. For recurring patterns, use the repeated-complaints guide rather than treating each case as an isolated annoyance.

Keep a case checklist

1. Verify the notice, transaction, reason and exact response deadline.
2. Assign a responsible person and funded time.
3. Reconcile charge, settlement, fees, refunds and disputed funds.
4. Match original evidence to the actual issue, preserving gaps and uncertainty.
5. Choose a truthful response or other appropriate resolution through the required process.
6. Retain submission evidence and verify the actual decision and cash movement.
7. Correct any underlying operating failure without inventing customer fault.