How to answer a SaaS customer who was charged twice

Check whether it is a true duplicate, refund before the bank gets involved, give a reference number, and keep amounts out of public replies.

Thinkiyo team··12 min read

If a customer was really charged twice, refund the extra charge now, on the same payment method, and send them the reference number. Do that before anything else, because once they dispute the charge with their bank your options shrink and you pay a fee. If the two charges turn out to be different things, show the customer exactly what each one paid for. Either way, a named person owns it until the money has landed.

First, is it really a duplicate

Card networks use a narrow definition. Visa's dispute guide for merchants says duplicate processing applies when the card, amount and transaction date all match. The same card and amount on different dates, or a different amount on the same day, falls under "paid by other means". Customers do not know this and do not care. Your agent should.

Check these before you reply with anything but an acknowledgement:

  • Pending against settled. One line may be an authorisation that drops off by itself.
  • A failed retry. The first attempt showed an error, the customer tried again, and both went through.
  • Two accounts. A second workspace on the same card, often set up by a colleague.
  • Renewal plus upgrade. An annual renewal and a seat change landing on the same day.
  • Invoice and card. A customer paid the invoice by transfer and the card on file also ran.
  • A real duplicate. A retry bug, a webhook processed twice, or a renewal job that ran two times.

The last one has a cousin worth checking at once: if your system did it to one customer, it may have done it to others. Pull every account in the same renewal batch.

Why speed matters more than usual

These figures are from Stripe's documentation. Other processors differ, so check yours.

What happensDetail
Time a customer has to disputeCard networks typically allow 120 days, sometimes more
When a dispute opensThe amount and a fee leave your balance, and you can't refund outside the dispute process while it is open
Your time to respondUsually 7 to 21 days. Miss it and you lose automatically
Your evidenceOne submission only. It can't be edited afterwards
How long a decision takesUp to three months, and the cardholder's bank decides
Fee if you winThe dispute received fee is not returned unless your contract says so

A refund is the cheap path. Stripe's refund documentation adds details your agents should know:

  • Refunds go back only to the original payment method.
  • The customer sees a card refund about 5 to 10 business days later, depending on the bank.
  • A refund issued shortly after the charge may appear as a reversal. The original charge disappears and no separate credit shows, which confuses people looking for a credit.
  • The acquirer reference number can take up to 7 business days to arrive, and there isn't one for a reversal.
  • On bank debits there is a risk of paying twice, if you refund while the bank also runs a dispute.

Stripe says to correct duplicates immediately and tell the customer. If a dispute arrives anyway, a refund you already issued is one of its listed grounds for overturning it. Visa's guide says to document both transactions, because the outcome turns on whether they were the same purchase.

The rules by market

Almost everywhere, the customer can ask their card issuer or bank to look at a duplicate, and the merchant is expected to return money it took by mistake. What changes is the clock, and who it binds. Most of the deadlines below bind the bank, and not you, but they tell you how long your customer can wait before going elsewhere. Many protect consumers only, so a company card may be treated differently. This is general information and not legal advice. Check the rules in your own market and your processor's terms.

MarketWhat appliesClock
US, credit cardRegulation Z billing errorsCustomer gives written notice within 60 days of the first statement showing it. Issuer acknowledges within 30 days and resolves within two billing cycles, 90 days at most
US, debit cardRegulation E errorsNotice within 60 days of the statement. Bank has 10 business days, or 45 with provisional credit, and 90 for point of sale debit
UKFCA complaint rules for payment firms. Chargeback is a request a provider can refusePayment firms normally answer in 15 business days, 35 at most with an explanation
EUYour Europe guidance under EU payment rules. Chargeback practice varies by countryBank replies in 15 days, 35 in exceptional cases. A mistaken direct debit can be refunded within 8 weeks
AustraliaDuplicate transactions are a listed chargeback ground. Consumer guarantees can cover business buyers under A$100,000Chargebacks usually within 45 to 120 days of the transaction. AFCA can review a wrongly rejected chargeback
IndiaRBI turnaround rules cover e-commerce debits with no merchant confirmation. A merchant billing twice is a different caseAuto-reversal within T+5, then ₹100 a day. We could not confirm whether RBI's November 2025 consolidation affects this 2019 circular, so check the current text
CanadaFCAC guideline for banks56 days for a bank to deal with a complaint. A revised guideline was issued on 23 June 2026 and takes effect on 23 June 2027

One change is coming that affects billing teams. Australia's Unfair Trading Practices Act 2026 received assent on 6 July 2026 and starts on 1 July 2027. It adds subscription rules on disclosure, renewal reminders and online cancellation, covering consumers and small business standard form contracts. Annual renewals are where double charges often surface, so fix both together.

Who does what

SituationOwnerFirst moveNever
Same card, amount, dateBillingRefund, then send confirmation with referenceAsk the customer to prove it
Failed attempt then retryBillingCheck processor status, refund or void the extra oneTell them it will sort itself out unless you have checked
Pending line onlySupportExplain it, name a date to recheckClose the ticket before that date
Two workspaces or a seat changeSupport with billingSend an itemised explanationSay "there is no duplicate" and stop there
Dispute already openBilling leadFollow the dispute processIssue a separate refund and risk paying twice
Many customers in one batchEngineering and billingStop the job, list everyone affectedWait for each person to write in
Public postSupport leadShort reply, move to privateMention amounts, card digits or plan price

Replies you can copy

Change the details. Keep them short.

First reply, before you have checked

Hi Sofia, thanks for flagging this. I'm checking the two payments against our billing records now. You'll hear from me by 2pm today, with either a refund confirmation or a clear explanation of each charge. Please don't send card details here, I don't need them.

Public reply

Sorry about this, Sofia. We've got your case and I've emailed you directly so we can sort it privately.

Update when there is no news

Hi Sofia, no result yet. Our payment provider hasn't confirmed which of the two charges settled, and I don't want to guess. I'll write again by 11am tomorrow, even if nothing has changed.

Closing reply

Hi Sofia, the second charge of $1,188 was our mistake and it's been refunded to the card ending 4417. Your bank should show it in about 5 to 10 business days. Your reference is 74829301. If it hasn't appeared by 24 November, reply here and I'll chase it with that number.

Hard case: it wasn't a duplicate

Hi Sofia, I checked both. The $1,188 on 3 November renewed the Tasksmith workspace. The $396 on the same day was for a second workspace, Tasksmith Client Projects, opened by Tom on 2 October. Invoices are attached. If nobody needs that workspace, I can cancel it today and we can talk about the unused time.

Hard case: dispute already open

Hi Sofia, I can see your bank has opened a dispute on this charge. While that is open I can't send a separate refund, because you could end up credited twice and the bank's process would be left hanging. We're responding to the bank directly, and I'll tell you when we hear back.

A routine to start on Monday

Times are a suggested starting point. They are not a benchmark, so adjust to your volumes.

  1. Add a billing tag and a named owner for each shift.
  2. Acknowledge within one hour during working hours, and give a time for the next update.
  3. Check the payment in your processor within four working hours.
  4. Refund a confirmed duplicate the same day. Let one role approve up to a set amount without escalation.
  5. Send the reference number when it exists, and set a reminder for the day the refund should appear.
  6. Run a batch check when any true duplicate shows up.
  7. If you built your own integration, confirm that charge requests use idempotency keys, which let a retry run safely without charging twice. On Stripe's v1 API keys can be removed after at least 24 hours, so a very late retry can still create a new charge.
  8. Add a line to receipts saying what each payment was for. Stripe lists clear receipts as a way to prevent these disputes.

Mistakes teams make

  • Replying "refund processed" and closing the ticket. A processed refund can still fail and return to you, up to 30 days later.
  • Giving a date for the money to arrive as a promise. The bank controls that part.
  • Telling the customer to call their bank. They then open a dispute, and you pay for it.
  • Asking for a screenshot of the statement when your processor already shows both charges.
  • Quoting the amount in a public reply. The customer may have typed it, but it should not come from you.
  • Treating the second message as a new ticket. The same person now has two agents and two answers.
  • Fixing the customer who complained and leaving the rest of the batch.

What to measure

  • Duplicates per 1,000 charges, split by true duplicate and lookalike.
  • Time from first message to refund issued.
  • Disputes in the duplicate category. The count should fall as refunds get faster.
  • Reopened billing cases. A reopen often means the refund did not show or the explanation did not land.
  • Share of cases where the customer got a reference number.

It is working when disputes in this category fall and billing cases stop coming back after the closing reply. For a related queue, see late order refunds.

A worked example

This is an example scenario. The product, people and messages are made up to show how Relay works. It is not a customer story.

Tasksmith is a project tool. Its annual renewal job runs twice on one morning.

Sofia Rossi emails at 9:10am: "I was charged twice for our annual plan this morning. Two identical payments on my card. Please refund one." At 11:40am she comments on a Tasksmith LinkedIn post: "Charged twice for our renewal and no reply in two hours. Not great."

One customer, two channels, one case. The comment is linked to her open email, so the agent sees what has been said. The public reply is the short one above. The billing owner finds both $1,188 charges with the same card and date, refunds one in the billing system, and runs the batch check, which finds eleven other accounts. Each gets a proactive email before writing in. Sofia gets the closing reply with her reference. If she writes again about the same charge, the case reopens and counts.

What runs in Relay today

Tagging, urgency, human only topics, routing, SLA clocks, matching a public comment to an open case, drafted public and private replies that a person approves, and reopen rate reporting run in Relay today. Billing is on the human only list, so Relay does not send a billing reply on its own. LinkedIn comment replies need the channel's token. Gmail and Outlook connect once you add an access token. Metrics show sample numbers until you have 20 tickets.

Two parts are on the way: a Stripe connection, so the agent sees the payment inside Relay, and refund actions within limits you set. Until then, the billing owner checks and refunds in the billing system. If billing complaints reach the public before your team sees them, contact us.

Common questions

Should I refund before I have checked whose fault it is?

Check first, but the check should take minutes for a true duplicate. If the card, amount and date all match and only one purchase exists, refund. A pending line that may drop off needs a look at the processor before you act.

Can I still refund if the customer has opened a chargeback?

On Stripe, no, you can't issue a refund outside the dispute process while the dispute is open. Accept it or counter it with evidence through that process. Other processors have their own rules, so check yours.

How long will the refund take to show?

Stripe says about 5 to 10 business days for card refunds, depending on the bank. A refund issued soon after the charge may appear as a reversal, with the original charge simply disappearing. Tell the customer which one to look for.

Do we have to refund a double charge by law?

The rules vary by market, and most of the deadlines bind the bank and not the merchant. Keeping money taken by mistake is hard to defend anywhere, and the customer usually has a dispute route anyway. Take local advice if the amount is large or the contract says something unusual.

Will Relay ever refund a customer on its own?

Not today. Every billing case goes to a person. Refund actions within limits you set are on the way, and anything outside those limits will still go to a person.

Does Relay reply to LinkedIn direct messages?

No. LinkedIn does not allow direct message access for this kind of tool, so Relay replies to comments on your posts and the conversation moves to email.

Sources

See what Relay can do for your customer service

Get a personalised 30 minute demo on your own channels and policies. We show you Relay handling your real conversations, then set it up with you.

  • Built and connected for you
  • Can run in your own cloud
  • A person on every refund

Brands we work with

  • Bolt
  • Dave & Buster's
  • ETV Win
  • Malachite Cars
  • Space Angel
  • Infinity Quest
Made by Thinkiyo© 2026 Thinkiyo. Relay is a Thinkiyo product.Examples use Lumen Parcel, a fictional brand.