Question handling
Failed payment questions and the answer that actually helps
A declined payment is one of the few support questions where the business genuinely does not know the answer either. The issuing bank decided, and it told the payment provider almost nothing about why. That makes the useful reply a checklist rather than a diagnosis, and it makes honesty about the limit part of the answer.
What they are really asking
Why was I refused, is my money at risk, and what do I do right now to get this paid.
- my card was declined
- why wont my payment go through
- the payment failed but i was still charged
- can i pay another way
- my subscription payment didnt go through
- i keep getting an error at checkout
- will you try my card again
- how long do i have before my account is suspended
- do you take paypal
- money left my account but the order didnt appear
The material that answers it
An assistant is only as good as the document behind it, and for this question the document usually exists but is written in the wrong shape. What each one has to contain to be answerable:
| The payment methods you actually accept | Card types, wallets, bank transfer, direct debit, invoice terms, and any that differ by country or by order size. This is the single most useful answer here because a declined card is very often solved by a different method, not by fixing the card. |
|---|---|
| A plain language decline checklist | The ordinary causes: expiry date, the billing address not matching what the bank holds, an authentication step abandoned before it finished, a bank blocking an unfamiliar or international merchant, a card with a lower limit than the total, a spending cap on a company card. Written as things to check, not as reasons you are asserting. |
| Your retry and reminder schedule | For anything recurring: how many times a failed payment is retried, over how many days, when the customer is emailed, and at what point access changes. Customers ask because they want to know how much time they have, and this is a fact about your setup rather than about their bank. |
| What a pending charge is, in your words | A failed attempt often leaves a hold on the account that looks exactly like a charge, and it usually clears on its own within a few days. Nothing causes more alarm than this and nothing is easier to explain in advance. |
| The route for anything urgent | Who to reach when a payment failure is about to interrupt something time critical, and how fast. A declined renewal at the wrong moment is an operational problem, not a billing one. |
How to handle it
Say what you cannot see, first
The decline reason belongs to the issuing bank and is not passed on in any useful detail. That is not evasive, it is how card authorisation works, and saying it plainly is more credible than a confident guess.
The honest opener also prevents the worst version of this conversation, where the assistant asserts a cause, the customer rings their bank to argue about it, and the bank tells them something different.
Give the checklist, ordered by how often it works
Expiry and card number typed correctly. Billing address exactly as the bank holds it, including the postcode. The authentication step from the bank completed rather than closed. Enough available balance or headroom on a company card. Then, if it is still failing, a different card or a different method.
This is where the value is. Most declines are resolved by the customer without anybody at your business doing anything, and the only reason they escalate is that nobody gave them the list.
Explain the hold that looks like a charge
A failed attempt can leave a pending authorisation that shows in an account and disappears later. Somebody who has tried three times may be looking at three of them and reasonably concluding they have been charged three times.
Explain what a pending item is, that it is not a completed payment, and that it usually falls away by itself. If money genuinely settled and nothing was delivered, that is a person, immediately.
Refuse card details in the same message, every time
People will offer. They will type a long number into a chat box because they want the problem solved and it feels like the fastest route. The assistant must decline clearly and point at the payment page or the phone line.
Say why, briefly: card details do not belong in a chat transcript. Put this in your refusal wording rather than leaving it to be composed, because it needs to appear the instant somebody starts typing digits.
When it stops being an answer
Money left the account and nothing arrived
This is the one that must move fastest. Whether it is a settled charge with a missing order, a duplicate, or a hold being misread, it needs somebody who can look at the transaction. The assistant should capture the amount, the date and the last four digits at most, and hand over.
Anything about to be suspended or cut off
A failed renewal with a deadline attached is a time critical problem wearing billing clothes. If access is about to change, the customer needs a person and a way to pay, not an explanation of retry logic.
Suspected fraud on either side
A customer saying they did not make a payment, or a pattern that looks like card testing, stops being a support conversation. Route it to whoever handles this at your business and do not let the assistant discuss what your fraud rules are.
How this one goes wrong
The reply that blamed the card and stopped
Your payment was declined by your bank, please contact them. It is true, it is useless, and it is what most businesses send. The customer already knew it was declined. They now ring a call centre that will tell them to contact the merchant, and the loop costs everybody an afternoon and often costs you the sale.
The opposite failure is worse: an assistant that names a cause it cannot know. Insufficient funds is an accusation, and getting it wrong on somebody who had plenty of money is a conversation you do not recover. The checklist sits between the two, and it is the only shape of this answer that actually resolves anything.
The same question, trade by trade
The pattern above holds everywhere. The wording, the escalation line and the material behind it do not, so there is a page per trade.
- For a accounting firmWhy a bounced monthly payment matters more near a filing date, and the confusion between paying the practice and paying the authority.
- For a insurance brokerA missed premium instalment runs a clock that ends in cover being cancelled, and reinstating it afterwards is an underwriting decision.
- For a marketing agencyA retainer invoice that bounces is a finance matter. A card declining on an advertising account stops live delivery within hours.
- For a online storeA failed attempt can still leave a pending line on a statement. It clears on the issuer's schedule and nobody at the shop can release it.
- For a gymThe bank says returned, the club says unpaid and the fob stops at the barrier. What can be explained without seeing an account.
- For a online courseThree payments toward one total is not a subscription. What a decline does to access, and the retry window a learner needs the date of.
- For a SaaS companyDunning, grace periods and the annual renewal that declines. What can be explained from policy when nobody in chat can see the payment.
- For a developer tools companyA billing suspension ends up as a rejected call in somebody's alerting. The retry schedule and the error string are the whole answer.
- For a fintech appCut off times, corridor delays and issuer declines are publishable. The specific payment in front of the customer is not.
- For a healthtech appA declined card on a health service is a continuity problem. The retry dates, what stops working on each of them, and the part that cannot wait.
Questions
- Can it see why a payment failed?
- No, and neither can most businesses. It answers from documents you index, so it can explain the common causes and your own retry and reminder schedule, but nothing about one person's transaction.
- What if somebody pastes their card number into the chat anyway?
- Write the refusal so it triggers on the attempt and says clearly that card details cannot be handled here, then names the payment page or the phone number. Treat that wording as a safety control rather than as copy.
- Is publishing our retry schedule risky?
- It is mostly the opposite. The reason people escalate a failed renewal is uncertainty about when something stops working. Saying how many attempts happen, over what period, and when access changes removes the panic and buys you the time to actually collect.
Keep reading
- Handling refund requestsA refund question is really about eligibility and timing. What to index, what the reply may promise, and where it has to reach a person.
- Handling cancellationsCancellation content is hard to find on purpose. What it costs to answer plainly, how notice periods work, and what happens to data on the way out.
- Handling pricing questionsPublished price versus the price for this buyer. Bands, ranges and from pricing, and why a firm number for unscoped work is the damaging failure.
- Every question typeHandling patterns for the questions every support inbox gets.
Try it on your own material
Upload a document or point it at your site, paste one line of HTML, then ask it something only your business could answer.