Playbook, online store
Three lines on the statement and one order that never existed
The message that arrives here is almost never the one the heading suggests. Nobody writes in to report that a card was declined, because they can see that. They write because the payment failed and the money appears to have gone anyway, sometimes two or three times, and no order exists to show for any of it. That is one of the most alarming things a shop can do to somebody, and it is entirely explainable.
Why this is not the general answer
The handling pattern for failed payments holds across every trade. What follows is the part that does not.
- The characteristic complaint is not a decline at all, it is money that looks spent: a failed attempt can leave an authorisation hold sitting on a statement that is visually indistinguishable from a completed payment.
- That hold falls away on the card issuer's schedule rather than the shop's, and nothing anybody at the shop does makes it happen sooner, which is the single sentence these customers need and are almost never given.
- A shop learns almost nothing about why a card was refused, because the issuer returns a refusal and keeps its reasoning, so any explanation offered in a chat window is a guess wearing the clothes of support.
- Repeated attempts actively make it worse, since each try can place another hold, and somebody who tried four times is looking at four pending lines, an empty basket and a growing certainty that they have been robbed.
How it arrives
- my card was declined but the money has gone
- why does it say pending twice
- ive been charged three times for one order
- my payment keeps failing
- it says my address does not match
- do you take any other payment methods
What has to be indexed for this to work
| Authorisation and capture, explained in customer words | What a pending line on a statement is, why a failed attempt can create one, and roughly how these fall away. Written without jargon and without a promised number of days, because the timing belongs to the issuer and varies by card. |
|---|---|
| The checks your checkout runs and what each failure looks like | Whether the billing address or postcode has to match, whether an extra verification step from the bank appears, and what the customer sees when each one fails. Customers describe the symptom rather than the cause, so the material has to be indexed by symptom. |
| Which payment methods you accept, per market | Cards, wallets, instalment options and anything regional, and which of them are unavailable in which countries. A large share of these conversations end with somebody paying a different way, and that only happens if the alternatives are named. |
| What the shop can and cannot see about a failed attempt | Written down explicitly, so the assistant can state the limit as a fact about the shop rather than as an apology about itself. It is also the paragraph that stops the team being asked to release a hold they have no ability to release. |
The reply
What you are almost certainly looking at is an authorisation rather than a charge. When a payment attempt fails, your bank can still place a temporary hold for the amount, and it looks the same as a real payment on a statement or an app, so several failed attempts can show as several pending lines [1]. Those holds are released by your bank, not by us, and we have no way to release one early or to see it at all. If no order confirmation email arrived, no order exists and nothing has been taken. On the decline itself, we only ever receive a refusal without a reason, so your bank is the only party who can say why, and it is worth asking them before trying again, since another attempt can add another pending line [2].
It names the mechanism first because the customer's fear is specific and one accurate sentence dissolves it. It says the release belongs to the bank without offering a number of days, since the assistant cannot know the issuer's schedule. Absence of a confirmation email is used as the test for whether an order exists, which is something the customer can check themselves. The advice not to retry is given with its reason attached, otherwise it reads as the shop refusing money.
Where it stops
The trigger. The visitor says an amount has actually left their account, names a figure, reports duplicate orders, or has an order confirmation alongside a failed payment.
If money has genuinely left your account or you have two confirmation emails for one order, that needs somebody who can open the payment record. Leave your name, the email you used at checkout, the amount and the date, and the team will check it.
It stops answering before it guesses, says who will pick it up, and asks for the one thing that makes a reply possible. Nothing about it reads as a dead end.
Never say this here
Out of bounds
- Never tell a customer they have not been charged, since the assistant cannot see the payment record and the difference between a hold and a charge is exactly what is in dispute.
- Never give a day or a number of days for a hold to clear, because that timing belongs to the card issuer and the customer will hold the shop to whatever number was said.
- Never offer a reason for a decline, since the shop is not told one and a guess about funds or fraud checks is both wrong and insulting.
- Never encourage somebody to keep retrying a card that has failed, because every attempt can add another pending line to the statement they are already frightened of.
Questions
- Can it release a hold or refund a duplicate charge?
- No to both. It cannot see payments and cannot write into any system, so releases, refunds and cancellations are all outside it. What it can do is explain the difference between a hold and a charge, which is what most of these people actually needed.
- Which single document deflects the most volume here?
- The authorisation explainer. It is one short page, it never goes out of date, and it answers the frightened version of this question at eleven at night when the alternative is the customer contacting their bank about a payment that never happened.
- Should it suggest another payment method?
- Yes, if the alternatives are indexed and available in that market. A failed card is often the end of the order otherwise, and naming a second route is the difference between a lost sale and a slightly annoying checkout.
Keep reading
- Everything for a online storeDelivery cut-offs, the returns window and restock questions get asked before purchase. The one thing an assistant cannot do is find an order.
- Handling failed payments in generalThe reason usually sits with the card issuer and is invisible to you. The useless reply, the useful one, and why card details never belong in a chat.
- The marketing list and the sales ledger are not the same dataClosing an account does not remove the sales records a seller has to keep. Separating the two is what makes this answerable at all.
- The size chart is a photograph and the photograph has no wordsSize charts, spec tables and delivery grids are usually pictures. A screen reader gets nothing from them, and neither does an assistant.
- They have read the policy already. Quoting it back is the wrong moveBy the time it is a complaint it is the third contact, the policy has been read, and what is wanted is a name and a decision.
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.