Banks trace wire transfers by sending a formal inquiry through the payment network the transfer used, asking each institution in the chain to confirm whether it received the funds, forwarded them, or is holding them. The mechanics differ for domestic wires, international SWIFT payments, and ACH transactions, but the goal is the same: locate the money and find out why it hasn’t landed. Most domestic traces resolve within one to three business days. International traces usually take five to ten, sometimes longer, because the payment may pass through several correspondent banks in different time zones.
When to Ask for a Trace
The usual trigger is that the recipient says the money never arrived and enough time has gone by that it should have. For a domestic wire, that generally means more than 24 hours. For an international transfer, allow a wider window, because the payment may route through two or three intermediary banks before reaching its destination.
Other reasons to open a trace: the recipient got less than you sent (intermediary banks sometimes deduct fees), an ACH payment was rejected without a clear explanation, or a cross-border transfer seems to have vanished between correspondents. Fraud is its own category. If you authorized a transfer under false pretenses or spot an unauthorized payment leaving your account, a trace establishes where the money went, which is the first step toward any recovery attempt.
Information Your Bank Needs to Open a Trace
Vague descriptions give the bank nothing to work with. Have these details ready before you call:
- The date and time you initiated the transfer, as precisely as possible.
- The exact amount. A one-cent difference can point to a different transaction in the system.
- The reference number. This is the identifier that makes a trace possible. For domestic Fedwire transfers, banks assign an IMAD (Input Message Accountability Data) number that tracks the payment through the Federal Reserve. For ACH payments, the trace number is a 15-character code built from the originating bank’s routing number plus a sequence number. For international SWIFT transfers, the identifier is the Unique End-to-End Transaction Reference, or UETR, which follows the payment across every bank in the chain.1Nacha. Transaction Status Documentation2SWIFT. What Is a Unique End-to-End Transaction Reference (UETR)?
- Sender and recipient details: full legal names, account numbers, and routing information for both sides.
- Any intermediary banks you know about. For international wires, these often appear on the original transfer confirmation.
How the Trace Actually Works
Domestic Wires
Domestic wires in the United States typically move through the Fedwire Funds Service, governed by the Federal Reserve’s Regulation J. When you ask your bank to trace one, it uses the IMAD number to contact the Federal Reserve or the receiving bank directly and request confirmation of what happened to the payment.
The receiving bank must respond with one of a few answers: the funds arrived and were credited, the funds arrived but are being held, or the payment was rejected. Because Fedwire settles in real time and involves at most one or two institutions, domestic traces are relatively straightforward and most resolve within one to three business days.
International Wires
Cross-border payments typically travel through the SWIFT network and may pass through two or three intermediary banks before reaching the recipient’s institution. Each bank in that chain is a potential point where funds can stall.
Historically, the tracing bank sent a free-format inquiry (an MT199 or MT299 message) to the next bank in the chain, essentially asking “do you have these funds, and if so, why haven’t you forwarded them?” That bank responded and, if needed, passed the inquiry along. The process was slow and manual.
SWIFT now requires all member banks originating payments to include a UETR, which functions as a universal tracking number for the payment’s entire journey.2SWIFT. What Is a Unique End-to-End Transaction Reference (UETR)? Banks offering gpi-enabled services can see in real time where a payment sits in the chain, whether it has been credited, and if it was rejected at any point. The sender’s bank is automatically notified of status changes, which has shortened the time it takes to locate a stuck payment. Not every bank has fully adopted gpi’s real-time tools, so some traces still fall back on the older message-by-message inquiry.
ACH Payments
ACH transfers move through the Automated Clearing House network in batches rather than individually, which makes them cheaper but slower. If an ACH payment goes missing or gets rejected, your bank uses the 15-character trace number to follow the transaction from the originating bank through the ACH operator (either the Federal Reserve or the Electronic Payments Network) to the receiving bank.1Nacha. Transaction Status Documentation
ACH rejections usually generate a return code that explains why the payment bounced: wrong account number, insufficient funds, closed account. A trace becomes necessary when the payment disappears without generating a return, or when the return code doesn’t match the circumstances. Because ACH processes in batches on a set schedule, traces often take two to four business days.
Why Payments Get Stuck: Compliance Holds
One of the most common reasons an international transfer stalls is compliance screening. Every bank in the payment chain runs the transaction against sanctions lists maintained by the Office of Foreign Assets Control. If a payment triggers a flag, the bank is required to block the funds and report the blocked transaction to OFAC within 10 business days.3eCFR. 31 CFR Part 501 – Reporting, Procedures and Penalties Regulations
A hold can also result from incomplete information. If the payment instruction is missing details that a bank’s anti-money-laundering system requires, the intermediary bank may hold the funds until it gets clarification from the sending institution. Neither the sender nor the recipient may know the payment is stuck at a bank they’ve never heard of. A trace is often the only way to discover that compliance is the problem, and your sending bank can then supply whatever documentation the intermediary needs to release the funds.
What a Trace Turns Up, and What Happens Next
A trace typically ends with one of a few findings, and each one calls for a different next step.
- The funds reached the recipient’s bank but weren’t credited. This is the most common result. The money made it to the right institution but is sitting in a holding account, often because of a name or account number mismatch. The recipient contacts their bank with the trace confirmation to get the funds released.
- An input error was identified. A wrong account number, mismatched routing number, or misspelled name caused the payment to stall or land in the wrong account. Your bank sends a recall or amendment request to correct the problem or retrieve the funds.
- The funds are stuck at an intermediary. A compliance flag, missing information, or currency conversion issue is holding the payment. Your bank works with the intermediary to resolve whatever triggered the hold.
- The transfer was fraudulent. The bank shifts from tracing into recovery mode.
For error-related holds, resolution is usually a matter of days once the trace identifies the problem. Recalls are harder. Once a wire has been credited to the recipient’s account, the sending bank can request a return, but the receiving bank has no legal obligation to comply, and the recipient can refuse. Speed matters enormously. The faster you initiate a trace and a recall, the better your chances that the funds haven’t been withdrawn yet.
Deadlines That Shape How Fast You Need to Move
Federal law provides specific protections depending on the type of transfer, and the clocks are short. For unauthorized electronic fund transfers, including ACH debits, the Electronic Fund Transfer Act caps your liability at $50 if you notify your bank within two business days of learning about the transfer. That cap rises to $500 if you report within 60 days of your statement, and disappears entirely after 60 days for any unauthorized transfers occurring after that deadline.4CFPB. 12 CFR 1005.6 – Liability of Consumer for Unauthorized Transfers5GovInfo. 15 USC 1693f
Traditional bank-to-bank wires sent through Fedwire don’t carry these Regulation E protections. Fedwire payments are generally final once completed, and banks are shielded from liability under UCC Article 4A as long as they followed reasonable security procedures. That legal framework is exactly why tracing and recalling a wire quickly is so important; the law doesn’t do much to help you after the fact.
If the Trace Uncovers Fraud
If the trace confirms that funds were stolen or misdirected, act on several fronts at once. Recovery rates for wire fraud are low, and every hour matters.
Start with your bank. Report the fraud formally and ask it to send a recall request to the receiving institution. Banks can sometimes freeze funds that haven’t been withdrawn yet, but only if you move quickly. File a complaint with the FBI’s Internet Crime Complaint Center at ic3.gov, which has a Recovery Asset Team designed to help financial institutions freeze fraudulent wire transfers. File a report with the FTC at reportfraud.ftc.gov as well, since those reports feed a database shared with over 2,000 law enforcement agencies.6Federal Trade Commission. ReportFraud.ftc.gov A local police report is worth filing too, both for the investigation and because your bank or insurance company may require it.
Be realistic about outcomes. Recovery depends almost entirely on speed. Once a fraudster moves stolen funds to another account, converts them to cryptocurrency, or withdraws cash, the money is effectively gone. The earlier you flag the problem, the more likely the receiving bank still has something to freeze.