Terminal said declined but the customer sees a debit
Check your merchant transaction history before making another payment attempt. A declined or interrupted terminal result can sit beside a pending entry in the customer's bank app. That entry alone does not prove you received the money. Establish the provider's final result, record any uncertainty and give a further attempt its own reference so you can detect a duplicate if one appears.
What you’ll get from this guide: Resolve conflicting payment evidence without creating an unnoticed second collection.
Check your merchant transaction history before making another payment attempt. A declined or interrupted terminal result can sit beside a pending entry in the customer's bank app. That entry alone does not prove you received the money. Establish the provider's final result, record any uncertainty and give a further attempt its own reference so you can detect a duplicate if one appears.
Give staff time to check the records while the customer is at the counter. The outcome and the time a bank takes to release a hold need to be confirmed for the actual attempt.
Start with the merchant status, not the screen you remember
Save the terminal receipt and check the exact amount, time, location and payment ID in the provider's history. A connection timeout and an issuer decline are different events. A screen may also be showing the result of a later attempt, so match the time carefully.
Square says cancelled, interrupted or declined payments can leave pending charges. It sends a void notification when a payment is voided; the issuing bank controls release of the hold. Keep that provider explanation distinct from the result of this customer's particular payment.
Route the case by the evidence
| Merchant evidence | Customer reports | Next check |
|---|---|---|
| Payment completed: PAY-64 | Debit shown | Match PAY-64 to this order; do not repeat it |
| Attempt declined: ATT-64 | Pending debit | Confirm the declined attempt and explain issuer follow-up |
| No final result after timeout | Debit shown, status unknown | Ask provider to trace the attempt before a further collection |
| Two completed payments | Two posted debits | Investigate duplicate collection against one order |
Original ASBG status checklist. The amount and references are fictional; use the actual provider result.
A missing record needs care. Check filters and the right merchant location before concluding that no payment exists. If the device was offline, use the offline-payments guide and retain the pending data. Don't reset the device as a shortcut to a clean screen.
Make any further attempt traceable
When the outcome is clear and a further payment is appropriate, explain it to the customer and record the new attempt separately. If you accept another tender while the first result remains unresolved, flag the order for follow-up and tell the customer how a later duplicate will be handled. Your business still needs a documented decision about releasing the goods.
Avoid repeatedly tapping the same card while staff disagree about the first result. One person should own the case, including the later reconciliation. Use the duplicate-payment checklist if two collections are subsequently confirmed.
Use a calm confirmation script
Fictional wording: “The terminal returned a decline, and I am checking the provider's transaction record now. The bank entry you can see may be pending, but I cannot confirm that from our screen. I will record this attempt and give you its reference before we decide on another payment.”
The American Express explanation of pending duplicates can help explain why bank entries and completed payments may differ. Let the customer use their issuer's secure support channel for account-specific information; don't ask them to email card credentials.
Close the loop after the queue has cleared
Recheck unresolved attempts against the provider history and match successful receipts to orders once. Record the final outcome and update the customer even if no correction is needed. For a wider outage, use the payment-outage procedure. The payments hub has the other investigations.
Key takeaways
- Check the actual merchant record and the correct location.
- Make retries and alternate tenders visible against the order.
- Keep one owner responsible until the outcome is confirmed.
Print or copy the evidence checklist
Copy this blank template into your own files. Your records stay with you.
Where to get help
Where to go from here
Authorised, captured and settled: understand card payment statuses
Identify which payment stage has actually completed.
3 min readCustomer sees two card charges: investigate a possible duplicate
Check for a second completed charge before arranging a correction.
3 min readCard chargeback evidence pack: respond to the reason given
Continue the “find a payment problem” reading sequence.
3 min read
General information only. This guide doesn't take your personal or business circumstances into account and isn't financial, legal or tax advice. Rates and thresholds change — check the official sources linked in this guide and get qualified advice where your circumstances require it.