To track a SWIFT transfer, you use the payment’s Unique End-to-End Transaction Reference (UETR), a 36-character code that follows your wire from your bank to the recipient’s account. You can look it up three ways: through your bank’s online portal, by calling the wire department, or through the SWIFT gpi system that more than 4,000 banks now use.1Swift. Swift GPI Which one gives you the most detail depends on whether your bank is a gpi member, but the UETR is the key to all three.
What to Have in Hand Before You Track
The UETR is the single most important identifier. It’s a 36-character string in a standardized universal identifier format, using hexadecimal characters and hyphens, that stays attached to your payment through every bank that touches it.2Swift. What is a Unique End-to-end Transaction Reference (UETR)?3Oracle. Inbound Cross Border Payments Transaction Input Every bank in the chain uses that code to locate your specific payment.
The other document worth having is the MT103, the standard SWIFT message format for a single customer payment. Think of it as the receipt for your wire. It contains the UETR, the recipient’s Bank Identifier Code (BIC, sometimes called a SWIFT code), the amount, and the routing details your bank used. Most banks make the MT103 available in the international transfers section of the online portal, or you can request a “SWIFT copy” from a bank representative.
Write down the exact amount you sent, including the currency. Intermediary banks along the route can deduct processing fees, so the amount moving through the system may not match what you originally sent. Knowing the original figure helps your bank distinguish your payment from others traveling through the same corridor.
Tracking Through Your Bank
Start with the bank’s online or mobile portal. Most modern banking platforms have a section for international transfers where you can enter your UETR or reference number and see basic status information. Often that’s enough to confirm whether the payment is still in transit, has arrived at the destination bank, or is stuck somewhere along the way.
If the portal shows nothing useful, or the transfer has been moving longer than expected, call or message the wire department directly. An average SWIFT payment reaches the destination within about 27 hours, and roughly two-thirds arrive within 24 hours. A payment that hasn’t moved after five or more business days is worth investigating. Your bank can submit a formal payment investigation, which involves contacting each intermediary bank in the chain to pinpoint exactly where the funds are sitting. SWIFT’s own data suggests these investigations commonly take five to ten working days to resolve.4Swift. Swift Solution for Managing Cross-border Payments Investigations Could Save Industry Millions in Operational Costs
Banks often charge a fee for formal investigations. The amount varies by institution and the complexity of the route, so ask about the cost before authorizing one. The upside is a documented trail showing every stop your payment made, which is useful if a dispute over missing funds later escalates.
Using SWIFT gpi for Real-Time Detail
The Global Payments Innovation (gpi) system is the most powerful tracking tool available for SWIFT transfers. Rather than relying on your bank to manually contact intermediaries, gpi provides a digital view of where your payment sits in real time, which banks have handled it, and what each one deducted along the way.1Swift. Swift GPI
If your bank is a gpi member, you may have direct access to a tracking portal where you can enter your UETR for instant updates. If not, ask your bank to look it up through the gpi Tracker on your behalf. The results show timestamps for each leg of the journey, so you can tell whether a delay comes from regulatory screening, a time-zone mismatch with a bank’s business hours, or a holiday closure in the destination country.
The Basic Tracker
Not every bank subscribes to the full gpi suite. Those that don’t still have access to the Basic Tracker, which offers more limited search and tracking features. The Basic Tracker requires participating banks to confirm receipt of a payment instruction within two business days, a mandate SWIFT enforces through a traffic-light compliance system. Banks that fall out of compliance lose access to tracking features entirely, which pushes institutions to keep confirmations current.5Swift. The Basic Tracker
If your bank is only on the Basic Tracker, you’ll see less detail and may need to rely more on the wire department for specifics about intermediary handling.
Reading the Status Codes
When you check a transfer’s status through gpi or your bank’s portal, you’ll see a four-letter code. Three of them cover almost every situation:
- ACSP (Settlement in Progress). The payment is still moving through the banking chain. It may be sitting at an intermediary bank for processing, undergoing compliance screening, or waiting for the receiving bank to credit the account. This is the status you’ll see most often while a transfer is in flight.
- ACCC (Settlement Completed). The funds have been credited to the recipient’s account. Once you see ACCC, the transfer is done.
- RJCT (Rejected). A bank in the chain refused to process the payment. Something needs to be corrected before the money can reach its destination.
ACSP causes the most anxiety because it can persist for hours or days without changing. Seeing it doesn’t necessarily mean something is wrong. Banks in different time zones process payments during their own business hours, and compliance reviews can add time even to routine transfers. It becomes concerning when it hasn’t changed for several business days and your bank can’t explain why.
When a Transfer Is Stuck or Rejected
A RJCT status means a bank in the chain couldn’t process the payment. The most common reasons are straightforward: a wrong account number, a name that doesn’t match the account on file, or a formatting error in the payment instructions. These are fixable. Your bank can help you correct the details and resubmit.
The more serious cause of rejection is a sanctions hit. U.S. financial institutions must screen wire transfers against lists maintained by the Office of Foreign Assets Control (OFAC). When a transfer matches a name on the Specially Designated Nationals (SDN) list, the bank must either block the funds or reject the transaction and return it to the sender, depending on the circumstances. Blocked funds are held in place and reported to OFAC within ten days. If the screening produces a false positive because a common name triggers a match, OFAC recommends the bank investigate before blocking, but the process still creates delays.6U.S. Department of the Treasury. Office of Foreign Assets Control – Blocking and Rejecting Transactions
When a transfer is rejected for non-sanctions reasons, the funds are returned to the sender’s account. This is not instant. A rejected SWIFT payment can take anywhere from a few days to a full month to work its way back, depending on how many banks handled it before the rejection. If three to four weeks pass with no return, ask your bank to initiate a recall or formal payment investigation.
Compliance screening also explains many stuck-at-ACSP cases. Financial institutions run transfers through anti-money laundering filters and sanctions screening under the Bank Secrecy Act.7FinCEN.gov. The Bank Secrecy Act A transfer that flags during screening gets held until the bank resolves the alert, which can add days to the timeline. There’s nothing you can do to speed this up, but knowing why it’s happening keeps you from making redundant inquiries.
Pre-Validation to Avoid Rejections
SWIFT offers a Payment Pre-validation service that lets banks verify the recipient’s account details before a transfer is sent.8Swift. Payment Pre-validation The service checks whether the account number exists, whether the beneficiary name matches, and whether the payment meets the formatting requirements of the destination country. Not every bank offers this yet. If yours does, it can catch the simple mistakes that cause most rejections. Ask before you send a large transfer.
Your Right to Cancel or Dispute a Transfer
Federal law gives you a short window to change your mind. Under Regulation E, you can cancel a remittance transfer within 30 minutes of making payment, as long as the recipient hasn’t already picked up or received the funds.9Consumer Financial Protection Bureau. Regulation E Section 1005.34 – Procedures for Cancellation and Refund of Remittance Transfers You need to provide your name and enough identifying information for the bank to locate the transfer. If you scheduled the transfer at least three business days in advance, you can cancel up until three business days before the scheduled date.10eCFR. 12 CFR 1005.36 – Transfers Scheduled Before the Date of Transfer
Beyond cancellation, Regulation E provides error resolution rights. If the amount received was wrong, the transfer wasn’t delivered by the promised date, or your bank made a computational error, you have 180 days from the date the problem should have been discovered to file an error claim. Some situations don’t count as errors the bank must remedy: a shortfall caused by the actual exchange rate differing from an estimated rate your bank disclosed, or a delay caused by BSA/AML screening or fraud prevention.11eCFR. 12 CFR 1005.33 – Procedures for Resolving Errors Most senders don’t know these protections exist, and banks aren’t always proactive about mentioning them.