To find a SWIFT code on a bank statement, start by knowing that most U.S. statements don’t display one. Statements are built around domestic activity — your account number, the ABA routing number, balances, debits, and credits — and the SWIFT code only matters when money crosses an international border. If your bank does print it, the two likely spots are the line-item detail for a specific international wire you’ve already received or sent, or a sidebar in the account summary header that lists the bank’s legal name and contact information. If it isn’t in either place, nothing is wrong with your statement; the code simply lives elsewhere.
Why Statements Usually Leave It Off
A SWIFT code, formally a Business Identifier Code (BIC), is an 8 or 11-character identifier that tells the global banking network which institution should receive an international wire. The majority of consumer transactions never touch that network, so most banks don’t bother including the code on routine statements. A few do print it. Some list the BIC alongside the transaction reference number and the name of the corresponding foreign institution when you’ve had an international wire during the statement period. A few others include it in the header block that identifies the bank itself. Both are the exception.
If you’ve scanned your statement front to back and can’t locate anything resembling an 8 or 11-character alphanumeric code, stop looking there and move to a source that reliably has it.
Where to Actually Find Your Bank’s SWIFT Code
Four sources will give you the correct code quickly:
- Your bank’s website. Look for a page titled “Wire Transfer Instructions” or “International Payments.” Many banks keep a dedicated page specifically to list the BIC for incoming foreign currency transactions.
- Your online banking portal. Some banks display wire instructions inside your account details or under a “Receive Money” section once you’ve logged in.
- Customer service. A phone call or secure chat will get you the correct code in minutes, and gives you verbal confirmation that you’re using the right one for your branch.
- SWIFT’s official BIC lookup at swiftref.com. It’s free and draws from the same directory banks use internally.
Whichever route you choose, confirm that the code matches your specific branch or region. Large multinational banks operate in dozens of countries, and each country-level entity has its own SWIFT code. Using the code for Citibank London when your account is at Citibank New York will delay the transfer.
What the Code Looks Like So You Know You’ve Got the Right One
The BIC follows an ISO-maintained international standard. Eight characters identifies the institution at its headquarters level. Eleven characters adds a three-character branch suffix.
- Characters 1–4 are the bank code, a shorthand for the institution’s name. “CHAS” for JPMorgan Chase, for example.
- Characters 5–6 are the two-letter ISO country code: “US” for the United States, “GB” for the United Kingdom.
- Characters 7–8 are the location code, identifying the city or regional office.
- Characters 9–11 are the optional branch code. “XXX” means the head office, and leaving these characters off entirely has the same effect.
So “CHASUS33” identifies Chase’s main U.S. office, and “CHASUS33XXX” means exactly the same thing. If someone gives you an 8-character code, your bank treats it as the head office by default.
SWIFT Code or IBAN?
People hunting for a SWIFT code sometimes actually need an IBAN, or both. They do different jobs. The SWIFT code identifies the bank. An IBAN (International Bank Account Number) identifies the specific account at that bank.
Whether you need an IBAN depends on where the money is going. European countries, along with much of the Middle East and parts of Central Asia, require an IBAN for incoming transfers. Send money to Germany or the UAE without one and the payment will bounce or sit in limbo. The United States, Canada, Australia, and most of Asia don’t use IBANs. For transfers to those countries, the SWIFT code plus the recipient’s domestic account and routing numbers are enough. When you are sending to a country that uses IBANs, you’ll typically need both: the SWIFT code routes the message to the correct bank, and the IBAN tells that bank which account to credit.
What Happens If the Code Is Wrong
An incorrect SWIFT code doesn’t necessarily mean your money vanishes, but it causes problems. If the code doesn’t correspond to any real institution, your bank’s system will typically reject the transfer before the funds leave your account. If the code belongs to a real but wrong bank, that bank will receive the payment message, notice the account details don’t match any of its customers, and send the funds back. The round trip can take a week or more, and you may be charged investigation or return fees by one or both banks.
The real danger is a wrong SWIFT code combined with an account number that happens to exist at the wrong bank. It’s rare, but when it happens, untangling it requires manual intervention from multiple institutions. Verify the code through an official source before sending anything. Copying it from an old email or a previous transfer is how most mistakes happen, because mergers and restructuring can change a bank’s code without notice.
Verify Wire Instructions Before You Send
Wire fraud targeting international transfers is one of the fastest-growing financial crimes, for a straightforward reason: once a wire settles, getting the money back is extraordinarily difficult. Scammers exploit this by inserting themselves into legitimate transaction discussions and swapping real wire instructions with their own.
The common tactic involves compromised email. A scammer gains access to a real email thread about an upcoming payment, then sends updated wire instructions from what looks like the same person. The new instructions appear nearly identical to the originals, but the SWIFT code and account number route funds to an account the scammer controls. Real estate closings and vendor payments are the most frequent targets, because the transfers are large, time-sensitive, and recipients are less likely to question urgency.
How to Verify
The single most effective defense is an out-of-band verification call. Before wiring money, call the recipient at a phone number you already have on file, not one pulled from the email containing the wire instructions. Scammers routinely plant fake phone numbers in email signatures, so an independently verified number is critical. Good sources include a signed contract, the recipient’s verified website, or a contact number from a previous trusted interaction.
Three situations should always trigger a verification call: any transfer above a dollar threshold you’ve set in advance, any change to previously established banking details, and any request that emphasizes unusual urgency. That last one is the classic pressure tactic. If someone insists the wire must go out today or the deal collapses, slow down and verify.
If Something Goes Wrong
Act within minutes, not hours. Contact your bank immediately to request a wire recall, and at the same time notify the receiving bank so they can try to freeze the account before the funds are withdrawn. Recovery rates are low. Once the recipient moves the money to another account, converts it to cryptocurrency, or withdraws cash, the funds are effectively gone. Studies have found that only about a quarter of fraud victims who transferred funds recovered the full amount.
If the transfer went through a remittance provider rather than a direct bank wire, you may have a brief cancellation window of roughly 30 minutes after submitting the transfer. After that window closes, the same near-irreversibility applies. File a report with the FBI’s Internet Crime Complaint Center (IC3) and your local law enforcement. Wire fraud investigations typically take 30 to 90 days, longer if international law enforcement coordination is needed.