Insights/Fintech

Money debited but payment failed: how to answer the complaints

Find out what state the money is in, acknowledge fast, keep account details out of public, and know the regulator's clock in each market you serve.

Thinkiyo team··12 min read

Treat every "money debited, payment failed" message as a complaint with a deadline, and answer it in two steps. Acknowledge at once in private, without asking for anything sensitive in public. Then find out which of the possible states the money is really in, and tell the customer that specifically. Never tell someone the money "will be back shortly" until you have looked. A person handles every case involving money.

What has actually happened

The same words from a customer can mean very different things. Your agents need to know which one they are looking at.

Your records showWhat it meansWhat the customer should hear
Authorisation only, nothing settledA hold that should drop offIt's a hold, the money hasn't moved, and the date you will recheck
Debit confirmed, merchant or payee never creditedA true failed paymentIt will be reversed, the clock that applies, and a reference
Debit confirmed, merchant received it, your app showed failureThe payment worked and your status was wrongIt went through, proof it was received, and that they shouldn't pay again
Customer paid again after the failurePossible double paymentOne will be returned, and which one
A debit the customer never madePossible fraudGo straight to your unauthorised transaction process
No trace at your endMay be the bank, or another providerWhat you checked, and what to ask their bank for

Do not skip the third row. A customer who sees "failed" often pays again, and then you have two problems.

The rules by market

The principle that holds almost everywhere: if you are a regulated payment firm, a complaint starts a clock when you receive it, wherever it arrives, and you owe a reasoned answer before it runs out. If the customer isn't satisfied, an outside body can usually take it further. What differs is the length of the clock and whether money or compensation is due automatically.

Many app businesses are not the regulated party. A merchant or software company may sit in front of a bank or licensed provider that holds these duties. Find out who owns what before you need it. This is general information and not legal advice. Check the rules in your own market, and your licence terms.

MarketRuleClock
USRegulation E on electronic fund transfer errors. An enquiry about whether a debit posted, with no error asserted, does not start it10 business days to investigate, or 45 with provisional credit, 90 for point of sale debit. Results in 3 business days, correction in 1 business day
UKFCA rules for payment firms and e-money issuersUnless resolved within 3 business days, the firm must confirm receipt in writing. Normally answer in 15 business days, 35 at most with an explanation. The customer has 6 months from the final response to go to the ombudsman
EUYour Europe summary of EU payment rulesWritten answer in 15 days, 35 in exceptional cases. A new Payment Services Regulation was provisionally agreed in November 2025 and needs formal adoption, so check its status
AustraliaASIC RG 271 for licensed firms. ePayments Code for subscribersAcknowledge within 24 hours or one business day, or as soon as practicable. Answer within 30 calendar days. Then AFCA
IndiaRBI turnaround rules, 2019See the table below. Compensation is credited automatically
CanadaFCAC guideline for banks56 days. A revised guideline issued on 23 June 2026, effective 23 June 2027, says the period will not be paused for any reason. A revised guideline was issued on 23 June 2026, effective 23 June 2027
SingaporeMAS E-Payments User Protection Guidelines, December 2024Unauthorised transaction claims: 21 business days, or 45 for complex cases. Separate duties cover non-card payments sent to the wrong recipient

India's table is unusually specific. From the RBI circular, where T is the calendar date of the transaction:

Payment typeFailureReversal byIf late
UPI transferDebited, payee not creditedT+1₹100 a day
UPI merchant paymentDebited, merchant not confirmedT+5₹100 a day
IMPSDebited, payee not creditedT+1₹100 a day
Card at point of sale or e-commerceDebited, merchant not confirmedT+5₹100 a day
ATMDebited, cash not dispensedT+5₹100 a day

RBI calls these outer limits, and compensation must be credited without the customer asking. If there is no redress in that time, the customer can go to the Integrated Ombudsman. RBI consolidated many of its regulatory circulars into Master Directions in November 2025. We could not confirm whether that touched this circular, so check the current text.

Australia has two details worth copying anywhere. Under RG 271, a post on a social channel the firm owns or controls counts as a complaint if the author is identifiable and contactable, and the firm must protect the customer's privacy when it answers. Firms are also expected to spot complaints without being told. The ePayments Code, last updated in June 2022, says a holder is not liable for loss caused by a failure of a system or equipment to complete a transaction it accepted. The Code is voluntary today. Treasury's March 2026 factsheet proposes a rule-making power for a mandatory, revised Code, and said legislation would be finalised for introduction in 2026.

Who does what

SituationOwnerFirst moveNever
Single debit-and-fail reportPayments agentAcknowledge, check the ledgerSay "it will be back soon" before checking
Same failure from many customersPayments lead and engineeringRaise an incident, find the route that failedAnswer each as a one-off
Payment worked, app showed failedPayments agentShow proof, warn against paying againRefund without confirming
Customer paid twicePayments agentReturn the extra paymentAsk them to wait for the first to resolve itself
Unauthorised debit claimFraud teamSecure the account, follow fraud processTreat it as a failed payment
Public postSupport, trained on privacyShort reply, move to privateAsk for account or transaction numbers
Customer in hardship or distressSenior agentPrioritise, offer a personSend a template

Replies you can copy

Write these in the customer's language when you can. Have a person check anything that mentions money.

First reply, private

Hi Jun, I'm sorry, that's stressful when it's your bill money. I've passed this to our payments team and I'm checking what happened to the $240. To find it I need the date and the last 4 digits of the payment reference in your app. Please don't send your full card number or PIN, we'll never ask for those. You'll hear from me by 6pm.

Public reply

Sorry about this, Layla. Please don't share account details here. We've messaged you privately and our payments team is on it.

Update when there is no news

Hi Jun, no result yet. The bank has not confirmed whether the $240 was credited or returned, and I don't want to guess. I've asked again and will write to you by noon tomorrow, even if nothing has changed.

Closing reply, money returned

Hi Jun, the payment failed at the bank's end and the $240 was returned on 7 November. Your reference is 58120. It should show in your account now, or within a day or two depending on your bank. If it isn't there by 11 November, reply and I'll chase it with that reference.

Hard case: the payment actually went through

Hi Jun, I've checked this and I'm sorry for the confusion. Our app showed "failed", but the electricity company received your $240 on 6 November, reference 58120. Please don't pay again. The error was on our side, and we've fixed the status in your app. If they say they haven't got it, send me their message and I'll deal with them directly.

Hard case: you can't give the money today

Hi Layla, I know you need this today and I wish I could send it now. The reversal has to come back through your bank, and it has until 12 November. I can't speed that up, but I'm tracking it and I'll tell you the moment it lands. If it hasn't by then, I'll escalate it and tell you what happens next.

Formal answer, when the clock requires one

Dear Layla, this is our final response to your complaint of 3 November. We found [what happened]. We have [what we did]. If you are not satisfied, you can contact [the ombudsman or external scheme for your market], at [contact details].

Check what your regulator requires in that letter. RG 271, for one, sets minimum content for the response.

A routine to start on Monday

Times are a suggested starting point. They are not a benchmark, and any regulatory deadline in your market overrides them.

  1. Write the state table above against your own ledger, in your own words.
  2. Give agents read access to transaction status.
  3. Tag every message mentioning money, and route it to a named payments owner.
  4. Acknowledge within one hour during working hours.
  5. Check the ledger state within four working hours.
  6. Add the regulatory date for that market to each case when it opens.
  7. Alert engineering when several reports name one route within an hour.
  8. Keep a list of what you may ask for in each channel. Nothing sensitive in public, ever.
  9. Review each case that hit its date, and each one that went to an ombudsman.

Mistakes teams make

  • Telling everyone "5 to 7 business days" without looking. It may be the wrong rail and the wrong answer.
  • Letting the app say "failed" when the status is unknown. "Pending, don't pay again" prevents a lot of double payments.
  • Asking for a transaction ID in a public thread.
  • Treating a social post as outside the complaints process. In some markets it counts.
  • Starting the clock when an agent picks it up. Most rules start it on receipt.
  • Sending a bot to a customer who has just lost their rent money.
  • Closing the case when the reversal is issued, before it lands.
  • Fixing a failing route with nobody telling the customers who were caught by it.

What to measure

  • Share of cases acknowledged within your target.
  • Time from complaint to confirmed money state.
  • Cases past the regulatory date, which should be zero.
  • Repeat payments after a failure, as a test of your in-app wording.
  • Complaints escalated to an external body.
  • Reopened cases. A case that reopens usually means the money did not arrive when you said it would.

It is working when customers get a specific answer about their own money on the first proper reply, and no case gets close to its deadline unnoticed.

A worked example

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

Pocketpay is a payments app. One evening a payment route starts failing.

Jun writes on WhatsApp in Mandarin: "我的账户被扣了240美元,但是应用显示付款失败。" ($240 was taken from my account but the app shows the payment as failed.) Layla posts on X in Arabic: "تم خصم المبلغ من حسابي لكن الدفع فشل. @pocketpay" (The amount was taken from my account but the payment failed.) A Google review says: "Paid my bill, money gone, app says failed. Third time this month."

Each message is tagged as a failed payment with money debited and marked for a person. Each customer gets an agent-approved acknowledgement that moves them to a private channel, with no request for card or account numbers in public. Each case goes to the payments team with a summary, so nobody has to repeat themselves.

Reports climb, all naming the same failure, and the theme crosses its normal level. An alert reaches the people named for it, and engineering finds the failing route. Every money case has a response deadline. If one is missed, the escalation ladder moves it up until someone owns it. The payments agent checks each transaction in Pocketpay's own system and sends the customer the specific result.

What runs in Relay today

Tagging, theme grouping, crisis alerts, routing to the payments team, SLA clocks, the escalation ladder and drafted replies that a person approves run in Relay today. Sending on WhatsApp, X, Google reviews and email needs each channel's token. Every money case goes to a person. Relay does not move money.

Payment and transaction lookups are on the way. Refunds and reversals stay with a person. Today the payments agent checks the transaction in your own system and uses Relay to reply and track the case. SLA clocks are ones you set, so enter your regulatory dates yourself. If failed payment complaints are your hardest queue, contact us. For a merchant's double charge, see the charged twice guide. For when one failure hits many customers, see handling a ticket spike.

Common questions

When does the complaint clock start?

Under most of the rules above it runs from when the firm receives the complaint. ASIC counts from the day after receipt, for example, and Canada's revised guideline, effective 23 June 2027, starts it the day the complaint is first communicated, by any channel. Check how your regulator counts.

Does a social media post count as a complaint?

It depends on the market. In Australia, RG 271 treats a post on a firm's own channel as a complaint if the author is identifiable and contactable. Even where it isn't required, handle it the same way, because it is the same customer with the same problem.

Can we say how long a reversal will take?

Say what your records and the rules show for that payment type, and give a date you will check. India's RBI timelines are specific, but other markets depend on the bank and the rail. Don't quote a blanket number.

We aren't a bank. Do these rules apply to us?

Possibly not directly, but they probably apply to someone in your payment chain, and your contract with them may pass duties to you. Find out which entity holds the licence and who must answer complaints. Take advice if you are unsure.

Can Relay refund a failed payment?

No. Relay sends every money case to a person. Refund actions within limits a business sets are on the way, and even then a person decides anything outside those limits.

Does Relay ask customers for card or account details?

Never in public. When a detail is needed, the draft asks for it in a direct message or other private channel. A person approves each draft before it goes out.

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.