“It declined, but the money left my account.” What actually happened
Last updated: August 2026
Quick answer:in almost every case, the customer has not been charged. Their bank placed an authorisation hold when the card was presented, the payment then failed, and the hold is still showing as “pending” until the bank releases it, which typically takes a few days and is entirely in the bank’s hands. Check your own settlement history: if the transaction is not there as a completed payment, you were not paid and you should not refund anything. Only if your records show two completed payments for the same sale is it a real double charge, and then you refund one of them through the card system immediately.
This is one of the most stressful moments at a till precisely because both people are telling the truth. Your machine said declined. Their banking app shows the money gone. The missing piece is that card payments happen in two steps, and the customer’s app is showing step one while your terminal is reporting the failure of step two.
Authorisation and capture, in plain English
Authorisationis the question: the terminal asks the customer’s bank “is this money available, and may we take it?” When the bank says yes, it ringfences the amount on the customer’s account. That ringfence is what banking apps show as a pending transaction, and from the customer’s side it looks exactly like being charged: their available balance drops by the amount.
Capture is the collection: the approved amount is claimed and enters settlement to your account, the journey described in our settlement guide. On an in-person sale the two steps normally follow each other so quickly that nobody notices the seam.
The seam becomes visible when something breaks between the two steps: the connection drops mid-transaction, the terminal times out, the customer pulls the card early, or the transaction is declined or cancelled after authorisation was granted. Then you get the classic mismatch: an authorisation hold on the customer’s account with no captured payment behind it. The money has not moved. It is reserved, unclaimed, and it will go back.
Why “declined” and “pending” can both be true
A decline or failure at your end does not always reach the customer’s bank as a tidy cancellation, especially when the cause was a communications failure rather than the bank refusing the payment. The bank granted an authorisation, heard nothing further, and keeps the hold open in case the claim arrives. Unclaimed holds expire and the funds are released back to the customer, but the timing belongs to the card holder’s bank: typically a few days, sometimes faster, occasionally longer. Nothing on your card machine can hurry it, because the hold does not live in your system.
Your two-minute check: were you actually paid?
Before anyone talks about refunds, answer one question from your own records: how many completedpayments exist for this sale? Open your provider’s app or dashboard and look at the transaction or settlement history, not the terminal’s last-screen message.
- No completed payment.The decline was real, you were not paid, and the customer’s pending line is an expiring hold. Nothing to refund. If they still owe you for the goods, take payment again, ideally after explaining the pending line so they understand they are not paying twice.
- One completed payment(often after a retry that “worked the second time”). You were paid once. The customer’s app may show one settled payment plus one pending hold from the failed first attempt; the hold will drop off on its own.
- Two completed payments. A genuine double charge, usually from a retried transaction where the first attempt did in fact go through. Refund one of them now, through the terminal or dashboard, so there is a clean paper trail linking refund to duplicate.
Refund correctly, or wait correctly
The rule that keeps you safe: refund only what your records show you received, and only through the card system.Refunding a pending hold in cash is the classic error; the hold expires back to the customer anyway and you have paid for it out of the till. Conversely, when your records show a true duplicate, do not tell the customer to “wait and see”: you are holding their money, the auto-reversal will not fix a captured payment, and a prompt refund is also your best defence if they later raise a chargeback, which costs you a fee and an argument.
What to tell the customer
A calm script for the counter, which you are welcome to use word for word:
“That payment did not go through to us, so we have not taken your money. What you can see on your app is a hold your bank placed when the card was presented; because the payment failed, the hold is not claimed and your bank will release it back to you automatically, usually within a few days. If it has not dropped off by then, your bank can release it when you call them; unfortunately we cannot release it from our side because it sits with your bank, not with us. Here is my card; if anything looks wrong once it clears, come straight back to me.”
Offering a receipt of the declined attempt, or a note with the date, time and amount, costs you nothing and gives the customer something concrete for their bank.
When to escalate to your provider
Call the number on your terminal or statement, rather than just retrying, when any of these apply: your settlement history and the terminal disagree about whether a transaction completed; you see a duplicate you cannot refund from the dashboard; the same terminal produces failed-then-pending transactions repeatedly; or a customer’s hold has clearly persisted well beyond the usual few days. Have the transaction date, time, amount and the last four digits of the card ready, and ask them to confirm in writing what state the transaction is in on their side.
If this keeps happening, it is a terminal problem, not bad luck
One interrupted transaction a year is life. A steady drip of declined-but-pending incidents usually points at a terminal that keeps losing its connection mid-payment, and every incident costs you twice: the awkwardness at the till, and the customer who quietly decides not to risk your card machine again. The fixes are the same as for any unreliable terminal, and our troubleshooting guide works through them, connection first. If the kit itself is the problem and your provider will not replace it, that is a switching conversation.
Terminal keeps failing mid-payment?
Dropped transactions and awkward till moments are a kit problem, and kit can be replaced. Free Dojo terminal with no monthly rental through MerchantSwitch. We respond in under 5 minutes.
Frequently asked questions
Why does a declined payment still show on my customer’s bank account?
Because authorisation and payment are two separate steps. When the card was presented, the customer’s bank ringfenced the money (an authorisation hold). If the transaction then failed or was declined at your end, that hold can remain visible as a pending transaction until the bank releases it. The money never actually left the account and never reached you; the pending line is a reservation, not a payment.
How long does a pending authorisation take to disappear?
It depends on the customer’s bank, not on you or your card machine. Unclaimed authorisation holds are typically released within a few days, though the exact window varies by bank and card type. If a hold has clearly outstayed its welcome, the fastest route is for the customer to contact their own bank, since only the card issuer can release it early.
The customer says they were charged twice. What do I check first?
Open your settlement or sales history, not the terminal screen, and count how many completed transactions exist for that amount. One completed transaction plus one pending line on the customer’s app means one payment and one expiring hold: no refund is due, the hold will drop off. Two completed transactions in your settlement history means a genuine double charge: refund one of them through your card machine or dashboard straight away.
Should I refund in cash while we wait?
No. If the money never settled to you, a cash refund pays the customer twice at your expense, because the pending hold will also expire back to their account. Only refund through the card system, and only when your own records show you actually received a duplicate payment. If the customer is out of pocket from a stuck hold, the fix sits with their bank, not with your till.
Related reading
Want kit that does not drop payments?
Tell us what keeps going wrong and we will match you with a provider whose terminals and support fit how you trade. Free, no obligation.