A refund and chargeback affect the same order: prevent a second settlement

When a buyer disputes a payment that support has already agreed to refund, put both cases under one owner. Match the original charge identifier, disputed amount, refund identifier and event dates. Customer name and order amount alone are unreliable when the buyer placed several orders. Pause any additional reimbursement until the provider's record explains which events are pending and which have settled.

Stripe documents the risk of duplicate credits for certain bank-debit refunds and disputes. It also identifies a pending refund disputed by the customer as a refund failure reason requiring the dispute process to be addressed. The correct next step depends on the payment method and current status; use the provider's instructions for the actual transaction.

Save the refund status and its balance transaction, then obtain the dispute debit, any fee and any later reinstatement. A support note saying refunded does not establish a completed processor refund. Similarly, submitting evidence does not establish that a dispute was won. Record the decision status and the cash effect in different fields so each can be reconciled.

Stripe explains that a dispute generally debits the disputed amount and a fee, with the account holder's bank deciding the outcome. Keep those amounts distinct. The accountant needs the facts to assess customer adjustments, recoverable balances and dispute costs under the company's policy, rather than posting every event to a generic sales reduction.

Check for partial amounts. A customer may dispute the entire charge after receiving a partial refund, or a refund may cover only one order line. Calculate the overlap explicitly and include the completed-refund evidence in the provider's permitted response process.

Tell the customer service owner which payment route is handling the resolution and what evidence can be shared. Use the actual status: requested, pending, completed or under dispute. Avoid promising that a bank will release funds by a date the merchant cannot confirm. Any request to change the reimbursement destination should follow the provider's rules and the business's verification process.

If the customer says the dispute was withdrawn, obtain the provider's confirmation before treating the debit as recovered. A customer message and a posted reinstatement are different evidence. Retain both, and continue monitoring the case through the final processor outcome. This prevents a second manual payout based on an incomplete understanding of the first one.

For a hypothetical $100 charge, assume a $40 refund completed and a later dispute removed $60 plus a separately recorded $15 fee. The principal returned or removed totals $100; the additional cost is $15. If the dispute instead removed $100, the $40 overlap requires investigation. These examples describe reconciliation arithmetic, not a prediction of how any particular provider handles partial refunds.

Retain the final dispute decision, refund confirmation and balance postings with the order. Review repeated overlaps by support workflow and notification timing. A short delay between a refund request and a dispute notice may call for clearer case ownership or faster status updates, while repeated unmatched processor events may indicate a connector mapping problem.