Chloe M.Google reviewOrder arrived damaged and nobody has replied to my email in three days.

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.
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:
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.
These figures are from Stripe's documentation. Other processors differ, so check yours.
| What happens | Detail |
|---|---|
| Time a customer has to dispute | Card networks typically allow 120 days, sometimes more |
| When a dispute opens | The amount and a fee leave your balance, and you can't refund outside the dispute process while it is open |
| Your time to respond | Usually 7 to 21 days. Miss it and you lose automatically |
| Your evidence | One submission only. It can't be edited afterwards |
| How long a decision takes | Up to three months, and the cardholder's bank decides |
| Fee if you win | The 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:
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.
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.
| Market | What applies | Clock |
|---|---|---|
| US, credit card | Regulation Z billing errors | Customer 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 card | Regulation E errors | Notice within 60 days of the statement. Bank has 10 business days, or 45 with provisional credit, and 90 for point of sale debit |
| UK | FCA complaint rules for payment firms. Chargeback is a request a provider can refuse | Payment firms normally answer in 15 business days, 35 at most with an explanation |
| EU | Your Europe guidance under EU payment rules. Chargeback practice varies by country | Bank replies in 15 days, 35 in exceptional cases. A mistaken direct debit can be refunded within 8 weeks |
| Australia | Duplicate transactions are a listed chargeback ground. Consumer guarantees can cover business buyers under A$100,000 | Chargebacks usually within 45 to 120 days of the transaction. AFCA can review a wrongly rejected chargeback |
| India | RBI turnaround rules cover e-commerce debits with no merchant confirmation. A merchant billing twice is a different case | Auto-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 |
| Canada | FCAC guideline for banks | 56 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.
| Situation | Owner | First move | Never |
|---|---|---|---|
| Same card, amount, date | Billing | Refund, then send confirmation with reference | Ask the customer to prove it |
| Failed attempt then retry | Billing | Check processor status, refund or void the extra one | Tell them it will sort itself out unless you have checked |
| Pending line only | Support | Explain it, name a date to recheck | Close the ticket before that date |
| Two workspaces or a seat change | Support with billing | Send an itemised explanation | Say "there is no duplicate" and stop there |
| Dispute already open | Billing lead | Follow the dispute process | Issue a separate refund and risk paying twice |
| Many customers in one batch | Engineering and billing | Stop the job, list everyone affected | Wait for each person to write in |
| Public post | Support lead | Short reply, move to private | Mention amounts, card digits or plan price |
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.
Times are a suggested starting point. They are not a benchmark, so adjust to your volumes.
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.
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.
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.
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.
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.
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.
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.
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.
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.
SaaSHow to handle a spike of support tickets during a SaaS outageDeclare early, name one person to speak, post one update everywhere on a fixed rhythm, and write to everyone who complained once it is fixed.8 November 2026 · 12 min read
GuidesIntroducing Relay: your online reputation in one placeWhat Relay is, the gap it was built for, what it does today, what it does not do yet, and who should choose something else.29 October 2026 · 6 min read
GuidesHow to do online reputation management, step by stepFind what people say about your business, answer it within the rules, fix what caused it. A plan, a triage table and replies you can copy.9 November 2026 · 11 min readGet 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.
Brands we work with


