When a customer says “my payment failed”, start by identifying the attempt and checking its status. A checkout error, a pending amount in a banking app and a completed payment are not interchangeable. Giving the wrong answer can prompt an unnecessary second payment or an incorrect refund.
Ask for a reference, not sensitive card details
Use the order reference, approximate time, amount and a description of what the customer saw. Confirm identity before sharing order information. Never ask for a full card number, security code, password or banking login in a support conversation.
If there is no order, use the approved payment-support process to locate the attempt. Do not create a new order or take another payment simply because the first record is hard to find.
Check the situation before drafting a reply
| Situation | What to verify | Avoid saying |
|---|---|---|
| Payment declined | The specific attempt and the status returned | “Your account has insufficient funds” without evidence |
| Pending amount, no order | Whether an authorisation exists and whether an order was created | “You have definitely been charged” based on the customer’s screenshot |
| Two visible attempts | The separate references and whether either was captured | “We will refund both” before checking |
| Order confirmed, payment unclear | Order history and current payment record | “Please pay again” while the original attempt is unresolved |
Payment providers distinguish authorisation, capture, cancellation and refund. For an example of those states, see the payment lifecycle documentation . Use the definitions and latest records from the provider in the actual setup; do not infer the final outcome from an old message.
Example: one order, two payment attempts
A customer tries to buy an item for NOK 1,200. The first checkout attempt appears to stop, so they try again. They now see two amounts in their banking app but have only one order confirmation.
The support task is to match both attempts, not to assume there are two completed charges. One attempt might still be pending while the other is completed. A payment specialist should verify the records and decide whether any action is needed.
A useful reply can say:
“I have found your order and am checking the two payment references. Please hold off on another attempt while we confirm their status. We will update you through this conversation.”
Use that wording only after finding the order and assigning the follow-up. Do not promise when a bank will release a pending amount unless that timing has been confirmed for the case.
Give the next team a usable handover
Include the order reference, payment references, confirmed statuses, timestamp of the check and unresolved question. Name the person responsible for the next update.
Ailyz’s ReAI integration is relevant when customer service needs context from commerce and accounting. If the issue is a mismatch between an invoice and a received payment, ReAI’s payment-discrepancy guide covers the accounting side.
Automate preparation, control financial actions
AI can help organise the evidence and draft a reply. Configure human approval for changes to orders or money, and stop automated handling when records conflict. A resolved ticket does not prove that a refund or cancellation has completed.
Review repeat contacts, unnecessary retries and time to a confirmed answer. For adjacent cases, see checkout support and returns and exchanges . Contact Ailyz to scope the handover for your setup.