Yes, as far as the bank's own systems reach, and it prepares the request for the rest. An AI agent can follow a payment through the bank's records, find where it stopped, explain why, and draft the enquiry to the other bank at depth 2. Resending, recalling or crediting the customer stays with a named person.
Where do payments go missing?
A payment the customer says "never arrived" has usually stopped at one of a few points. It never left: held by a fraud check, blocked by a limit, or rejected for a format error. It left and was returned: the receiving account was closed or the details were wrong. It left and arrived, but the receiving bank has not credited it: held for its own checks, or applied to the wrong account. Or it arrived and was credited, and the recipient has not noticed.
The first two are visible in the sending bank's systems. The last two are not. That is the boundary of what the agent can find by itself and the point where it needs the other bank.
What decides how far the agent goes?
The deciding factor is whether the next step reads information or acts on money. Reading payment status, return messages and fraud holds is depth 1. Explaining them to the customer is low risk, with care about what may be said about a fraud hold. Drafting an enquiry to the receiving bank is depth 2: it goes to another institution in the bank's name, so a person or an approved scheme process sends it.
Acting on money is a different matter. If a payment failed, the obvious fix seems to be sending it again. But if the first payment is still in flight, a resend pays the recipient twice. Resending, recalling and crediting the customer for a lost payment all need a person who has confirmed where the original is.
What may the agent do, and where must it stop?
| Step | The agent | Where it stops |
|---|---|---|
| Finding the payment in the bank's records | Reads status and history, depth 1 | Nothing |
| Explaining a rejection or return | Gives the reason in plain words | Nothing routine |
| Explaining a fraud hold | Says it is being checked, in approved wording | Discussing the reasons |
| Drafting an enquiry to the receiving bank | Drafts it, depth 2 | Sending it outside an approved process |
| Telling the customer what happens next | Gives expected timings | Promising an outcome |
| Resending a failed payment | Never on its own | The customer re-instructs, or a person acts |
| Recalling or refunding | Prepares the case | A person decides |
A recall asks for money back; it is not a trace. The distinction is explained in what a payment recall is, and the stronger action in what a payment reversal is.
An example: a payment that "vanished"
Take a customer who paid 1,500 to a furniture shop four days ago. The shop says nothing has arrived. The customer asks the bank where the money is.
The agent finds the payment. It left the same day and settled. No return message has come back. The agent explains that the money reached the shop's bank and that the next step is to ask that bank whether it was credited. It drafts an enquiry with the payment reference, amount, date and the details the customer used. A person in payment operations reviews and sends it.
Two days later the receiving bank replies: the payment was credited to the shop's account on the day it was sent. The shop had been checking a different account. The agent tells the customer, with the receiving bank's confirmation, and suggests the customer give the shop the reference so it can find the payment.
What controls make it safe?
- Status read from the rail. Payment status and return messages are sealed facts from the payment systems, not the agent's assumptions.
- No resend capability. The agent cannot send a replacement payment while the original's fate is unknown.
- Enquiries drafted to a template. Each enquiry follows the bank's standard format and is sent by a person or approved process.
- Fraud holds handled carefully. The agent states that a check is under way and passes the conversation to the fraud team.
- Cases tracked to closure. Each trace stays open until the payment is found, returned or recalled.
Incoming payments the customer is expecting follow a different route, covered in tracing missing incoming payments with an AI agent. Payments that failed outright are covered in investigating failed payments with an AI agent. If the customer wants the money back rather than traced, see whether an AI agent can reverse a payment. The general limits are in AI agents in banking: what they may and may not do.
Questions people ask
Can the agent tell the customer the recipient's account details?
It can confirm the details the customer entered. It cannot share information about the recipient's account that the receiving bank provides in confidence.
How long does a trace take?
The bank's own checks take minutes. Enquiries to other banks depend on their response times, and international payments usually take longer.
What if the payment went to the wrong account because the customer made a mistake?
That becomes a recall request, prepared by the agent and handled by a person, with no guarantee of success.