Customer Charged Twice? What to Reply
Copy a reply for a duplicate charge: still checking, a pending authorization, or a confirmed refund or void.

A duplicate charge customer response matters because the first few minutes after the complaint decide whether the issue stays a fixable billing error or becomes a formal bank dispute with higher cost and more distrust.
A duplicate charge customer response is the first message and action path a business uses when a customer says they were billed twice. Small businesses need it because some duplicate-charge complaints are real billing errors, while others are authorization holds, split transactions, or timing confusion that still need a fast explanation.
Part of the complete guides: How to Fight a Chargeback: Evidence and Rebuttal Steps · Failed Payment Recovery: Dunning Playbook
Rules vary by processor, state, and industry, so verify with your attorney or accountant if card-network rules, refund timing, or regulated billing requirements apply in your business.
When the charge was real and you need to say so, the free customer apology email generator drafts the note for a billing error. Confirm the duplicate in your records before you promise a refund.
Three replies to copy
Pick the note that matches the card record. Replace each bracket before you send it.
Still checking
Thank you for flagging this. We are reviewing the transaction now using the charge amount, date, and payment method so we can confirm whether there are two completed charges or one completed charge plus a pending authorization. We will update you by [time] with the result and the exact next step, whether that is a refund, a void, or a clarification on the pending hold.
Pending authorization
Thank you for flagging this. We checked the [amount] charge on [date] for the card ending [last 4 digits]. One charge is complete. The second entry is a pending authorization, not a second completed charge. The hold drops off within the window your card issuer or processor sets. We will recheck on [date] and email you if it is still there.
If the second entry is your own uncaptured authorization, cancel or void it in your payment processor to release the hold sooner.
Confirmed duplicate, refunded or voided
Thank you for flagging this. We confirmed a duplicate charge of [amount] on [date] for the card ending [last 4 digits]. We [refunded or voided] that second charge on [date]. The original charge of [amount] still stands. Reply if the duplicate is still showing on [date], and we will recheck it.
The first mistake is refunding immediately before understanding what happened, which can create a second accounting mess if one of the charges was only pending. The second is becoming defensive and telling the customer to call the bank without checking the transaction history, which almost guarantees the relationship moves from service issue to formal dispute.
A better response starts with facts. Confirm the transaction date, amount, payment method, and merchant descriptor. Then determine whether there are two settled charges, one settled charge plus one pending authorization, or two separate but valid transactions the customer may not recognize yet.
What a duplicate-charge review should confirm
| Review lane | Why it matters | What to confirm |
|---|---|---|
| Transaction status | Pending and settled charges require different responses. | Whether each charge is authorized, captured, or already refunded. |
| Charge source | You need to know how the second entry happened. | Manual retry, terminal glitch, checkout refresh, split invoice, or processor hold. |
| Customer expectation | The explanation should meet the complaint directly. | What the customer saw on the statement and what they believe was wrong. |
| Resolution path | Speed matters once the facts are clear. | Refund, void, explanation, escalation, or processor follow-up. |
The four rules that keep the response credible
The business says it does not see a problem yet, tells the customer to wait, and gives no explanation of what the two charges might actually be.
The business confirms the transaction details, explains whether the second charge is pending or real, and gives one clear resolution path with timing.
Why this complaint escalates so quickly
Money complaints feel personal. Customers may tolerate a service delay longer than they tolerate uncertainty around being charged twice. If the business does not explain what it sees promptly, the customer fills the gap with the worst-case assumption: that the business took money carelessly or is trying to keep it.
A structured response lowers that risk because it shows the issue is being treated as a real case, not brushed aside. It also protects the business from issuing the wrong refund too early. Some duplicate-charge complaints involve one settled charge and one pending authorization that will drop off without a second capture. Others are true operator or system errors that need immediate correction.
When the team knows how to distinguish those lanes fast, the conversation stays practical instead of emotional. That is the difference between a resolved billing case and a preventable chargeback that costs both money and reputation.
Get the free Emergency Triage Sheet
The first three moves for any business emergency, plus one practical fix in your inbox each week.
No spam. Unsubscribe anytime.
Small business example
Say a medspa hears from a client who sees two card entries for one visit. One entry may already be settled, and the other may still be a pending authorization. The reply in that situation would explain the difference and name a date to check the hold again. That is an illustration, not a record of a real complaint.
Checklist for handling a duplicate-charge complaint
- Confirm the amount, date, and payment method the customer is referencing.
- Check whether the charges are pending, settled, voided, or refunded.
- Identify the likely cause before promising the remedy.
- Explain the next step in plain language and give a timing commitment.
- Log the case so repeated billing issues can be traced and reduced.
Separate a duplicate charge from an invoice overpayment
| What the customer sees | What to verify | Right next lane |
|---|---|---|
| Two card entries for one sale | Pending versus settled status, transaction IDs, amount, and terminal or checkout events. | Void, explain, or refund the confirmed duplicate through the processor path. |
| One invoice received too much cash | Cleared receipt, invoice balance, credits, other open items, payer, and customer instruction. | Use the invoice overpayment refund-or-credit workflow. |
| Two receipts for the same invoice | Whether both cleared, whether one belongs elsewhere, and whether fraud or reversal risk is open. | Reconcile both receipts before releasing any money. |
This distinction improves the original intent of the response: a card authorization problem, a duplicate settled charge, and an overpaid accounts-receivable invoice can look similar to the customer while requiring different evidence, approvals, and closeout records.
FAQ: should you always refund the second charge immediately?
Not always. If the second entry is only a pending authorization, a refund may create more confusion instead of less. The better move is to confirm the status first, then act according to what actually settled.
Free version vs. full kit
This article gives you the lightweight version: three replies for a check still open, a pending authorization, and a confirmed duplicate you refunded or voided. The full Refund Request Triage + Resolution Log Kit helps you sort billing complaints, track outcomes, and keep customer-money issues from becoming repeated support fires.
View the Refund Request Triage + Resolution Log Kit
Fix the next one before it starts.
Join the list for the free Emergency Triage Sheet and a new practical fix every week.
No spam. Unsubscribe anytime.