Locate the payment one stage at a time
Funding
Confirm the sender's debit is settled and not merely authorized or pending.
Verification
Check for a request about identity, beneficiary, payment purpose or source of funds.
Provider processing
Ask whether the provider has released the transfer to its payout partner or bank.
Interbank route
For a wire, request the bank reference, UETR and current trace status where available.
Recipient posting
Give the recipient the confirmation so their bank can search by amount, currency, date, sender and reference.
Translate vague statuses into useful questions
| Status shown | Do not assume | Ask instead |
|---|---|---|
| Processing | That the payment has entered the banking network | Which exact prerequisite or internal stage remains? |
| Sent | That the recipient account has been credited | To which institution or payout partner was it released? |
| Completed | That the recipient can use the funds | Does completion mean payout, bank receipt or final account credit? |
| Delayed | That nothing can be done | What exception exists and who owns the next action? |
What the UETR contributes
Swift describes the Unique End-to-end Transaction Reference as a 36-character reference carried in relevant payment instruction messages. It is designed to remain associated with the payment through the chain and support status visibility.
A customer may not have direct access to the institutional tracker. The practical step is to ask the sending bank for the UETR and request that it use the reference to trace the payment. A UETR identifies the transaction; it does not promise that every delay is instantly resolved.
Example: sent is not credited
A bank marks a wire sent on Tuesday. The recipient checks Wednesday and sees nothing. The sender gives the recipient only a screenshot with no bank reference, so the receiving bank cannot reliably search its incoming queue.
The sender requests the formal payment confirmation and UETR. The recipient bank can then match the exact currency, amount, date and reference or explain that it has not received the instruction. The investigation moves from a general complaint to a specific payment record.
Translate every status into evidence and a next owner
Submitted usually means the instruction exists. Funded means the provider matched usable money to it. Processing can cover verification, conversion or preparation for release. Sent can mean the payment left the provider without proving recipient credit. Delivered should be checked against the provider's definition and the recipient's account evidence.
For each status, ask for the timestamp, reference and institution responsible for the next action. A UETR can help participating banks identify a SWIFT payment, while a provider reference may be necessary for a local payout partner. Give support the exact identifier it uses rather than sending screenshots without a transaction key.
Build one timeline from funding through final credit, rejection or return. Add the promised availability date, every support contact and the recipient's evidence. If two institutions give conflicting answers, ask each to state the last confirmed event. Do not start a second transfer until the first is located or formally resolved, because a duplicate introduces a new payment rather than fixing the trace.
When tracking becomes an error case
If the promised window has passed, follow the failed or returned transfer playbook.
To understand possible hand-offs, map correspondent banking.
If a bank sends message details as evidence, read what an MT103 and payment confirmation can prove before treating sent as credited.
Tracking and payment-reference sources
The references explain UETRs, payment-service expectations and evidence used in a trace. Give support the exact transaction reference instead of relying on a generic status label.
Questions that locate a delayed payment
Can I track a Swift payment myself?
Customer access depends on the bank or provider. Ask the sending institution for the UETR and the latest trace information.
Why can the recipient bank not see it?
The payment may not have reached that bank, may be waiting in an exception queue, or may lack enough information for the first-line support search.
Should the recipient open the investigation?
Both sides can ask questions, but the sender generally has the contract, debit record and direct relationship with the originating provider.
This page uses worked reasoning and authoritative references; it does not claim first-hand testing or personalized advice. See our editorial policy.
Place this step in the cross-border payment rails collection to follow routing, references, deductions and returns.