You are trying to send a USD wire from a small U.S. bank to a beneficiary abroad, and the wire form is asking for an ABA routing number — not a SWIFT/BIC code. The foreign bank only ever gave you a BIC. So how do you bridge the gap between the international SWIFT world and the domestic Fedwire rails? This guide explains why this happens, what an ABA routing number really is in the cross-border context, and how to convert a SWIFT/BIC into the right ABA in seconds.
The Problem: A U.S. Bank That Cannot Speak SWIFT
Not every U.S. bank is a direct member of the SWIFT network. Of the roughly 4,500 commercial banks and credit unions operating in the United States, only a few hundred maintain their own SWIFT/BIC code and run a SWIFT interface in-house. The rest — community banks, regional credit unions, smaller state-chartered institutions — rely entirely on domestic payment rails such as Fedwire and the ACH network. When one of their customers walks in and asks to send money to a supplier in Frankfurt or a freelancer in Manila, the bank cannot simply generate an MT103 and push it into SWIFT. It has no SWIFT terminal.
So how does the payment actually leave the country? The answer is that it does not, at least not in the way you might think. The U.S. bank sends a domestic Fedwire transfer to a larger U.S. bank that does have international reach, and that larger bank takes it from there. To address that Fedwire message, the sending bank needs the receiver’s ABA routing number — not a SWIFT/BIC code. SWIFT/BIC codes are useless on Fedwire. Fedwire understands only ABA routing numbers.
What Is an ABA Routing Number, Exactly?
An ABA Routing Transit Number (often shortened to ABA RTN, ABA number, or simply “routing number”) is a nine-digit code that uniquely identifies a financial institution within the United States. It was created in 1910 by the American Bankers Association — hence the name — to make paper check clearing more efficient. Today the same nine-digit format is used to address electronic payments on three different rails:
- Checks: The number printed at the bottom-left of every U.S. check, used by clearing houses to route the cheque back to the paying bank.
- ACH (Automated Clearing House): Used for direct deposits, recurring debits, and low-value batched transfers. ACH uses its own routing number, which may differ from the wire routing number for the same bank.
- Fedwire: The Federal Reserve’s real-time gross settlement system, used for high-value, time-critical wires. Cross-border USD payments that originate from a non-SWIFT U.S. bank almost always travel over Fedwire to reach an international correspondent.
For international wire purposes, what matters is the Fedwire routing number. This is the address that allows your sending bank to deliver USD into the receiving institution’s account at the Federal Reserve. Once the funds arrive there, the receiving bank can do whatever the payment instructions ask — including forwarding the money on to a foreign beneficiary.
The Hidden Link: Nostro Accounts and U.S. Correspondents
Here is where the cross-border angle becomes interesting. Foreign banks that need to receive USD from the United States do not hold accounts directly at the Federal Reserve. Only U.S.-chartered institutions can. Instead, every foreign bank that handles USD maintains a USD correspondent account — a so-called nostro account — at one or more large U.S. banks. The most common destinations are JPMorgan Chase, Citibank, Bank of New York Mellon, Wells Fargo, Deutsche Bank Trust Company Americas, and a handful of others that dominate the USD clearing business.
So when a Frankfurt bank publishes its SWIFT/BIC code — say, DEUTDEFFXXX — that BIC tells the world how to reach Deutsche Bank in Frankfurt over the SWIFT messaging network. But on Fedwire, that BIC is meaningless. What Fedwire needs is the ABA routing number of the U.S. bank where Deutsche Bank Frankfurt holds its USD nostro — which is typically Deutsche Bank Trust Company Americas in New York, ABA 026003780. The Fedwire message is sent to that ABA, the funds land in the nostro, and the New York correspondent then notifies Frankfurt (over SWIFT, internally) that USD has been received for the benefit of the ultimate customer.
In other words, the ABA routing number you need for an international wire from a non-SWIFT U.S. bank is not the ABA of the foreign bank itself. It is the ABA of the U.S. correspondent that holds the foreign bank’s USD nostro account. This is the single most common point of confusion when small U.S. banks try to send their first international wires.
Why Asking the Foreign Bank Is Often a Dead End
The natural reflex is to email the beneficiary or the foreign bank directly and ask, “What is your ABA routing number?” Unfortunately, the answer you usually get back is one of the following:
- “Please use our SWIFT/BIC code: XXXXXXXXX.”
- “We do not have an ABA routing number, only a BIC.”
- “Send the wire via SWIFT to our BIC, our IBAN is...”
- Silence, because the front-office contact does not know what an ABA is.
None of this helps you. Your originating U.S. bank cannot send anything via SWIFT. You need a domestic Fedwire ABA, and the foreign bank’s payments operations team often does not bother to explain the correspondent banking chain to retail customers. They assume that any U.S. bank can do SWIFT — which is simply not true.
Even when you do escalate to the foreign bank’s treasury or correspondent banking desk, the response can vary by currency, by branch, and even by transaction size. A bank may use one USD correspondent for retail wires and another for high-value treasury flows. Getting the right answer can take days of back-and-forth, by which point the payment is already late.
The Faster Path: Convert SWIFT/BIC to ABA Yourself
The relationship between a foreign BIC and its USD correspondent ABA is not a secret. It is a standing arrangement, registered in SWIFT’s internal directories and usually stable for years at a time. If you know which U.S. correspondent the foreign bank uses, you can address the Fedwire message yourself without ever waiting on a reply from the beneficiary.
This is exactly the gap that ohmyfin.ai/correspondent-banks is built to close. The Ohmyfin database maps every published SWIFT/BIC code to its known USD (and EUR, GBP, and other major currency) correspondent relationships, including the ABA routing number of the U.S. bank that holds the nostro account. You enter the foreign bank’s BIC, and you immediately see:
- The name of the U.S. correspondent bank.
- The correspondent’s SWIFT/BIC code.
- The correspondent’s ABA Fedwire routing number.
- The foreign bank’s account number at that correspondent (the nostro reference) where this is publicly available.
- Alternative correspondents, if the foreign bank maintains more than one USD nostro.
Armed with this information, your originating bank’s wire desk can populate the Fedwire message correctly on the first attempt: route the funds to the U.S. correspondent’s ABA, credit the foreign bank’s nostro account number, and add a “for further credit to” (FFC) instruction naming the ultimate beneficiary, account number or IBAN, and address. The wire arrives the same business day in most corridors, and there is no need to wait for the foreign bank to reply with information they were never going to give you anyway.
What a Correctly Addressed Cross-Border Fedwire Looks Like
To make this concrete, here is the structure of a typical Fedwire instruction sent from a non-SWIFT U.S. community bank to a beneficiary at a German bank:
- Receiver ABA:
026003780(Deutsche Bank Trust Company Americas, New York) - Receiver name: Deutsche Bank Trust Company Americas
- Beneficiary bank: Deutsche Bank AG, Frankfurt — BIC
DEUTDEFF - Beneficiary bank account at receiver (nostro): the account number Deutsche Bank Frankfurt holds at DBTCA
- For further credit to: Final beneficiary name, IBAN
DE89 3704 0044 0532 0130 00, address - Originator: Your customer’s name, address, and account number
- Reference: Invoice number or purpose of payment
The ABA routing number sits at the top of this structure as the destination address on Fedwire, while the SWIFT/BIC sits inside the message as the next-leg routing instruction for the U.S. correspondent. Both pieces of information are required, and getting either one wrong will cause the payment to bounce or sit in a manual repair queue.
For Fintechs: Programmatic BIC-to-ABA Lookup
If you are running a payment product — a remittance app, a B2B payouts platform, a treasury management system, an embedded-finance API — you cannot afford to send users back to email the foreign bank. You need the BIC-to-ABA mapping available as data, in real time, at the moment a user enters a recipient’s SWIFT code.
This is the most common use case for the Ohmyfin correspondent banks dataset. Fintech engineering teams query the API with a SWIFT/BIC and receive a structured JSON response containing the U.S. correspondent details, including the ABA routing number, the correspondent BIC, and any additional nostro metadata. The lookup runs in single-digit milliseconds and is updated continuously as banks switch correspondents or add new relationships.
Typical integrations include:
- Onboarding flows: When a user adds an international payee, the platform validates the BIC and pre-fills the U.S. correspondent ABA so the operations team does not have to reach out to the bank.
- Routing engines: Payment platforms that originate USD wires through multiple settlement banks use the dataset to choose the cheapest or fastest correspondent for each corridor.
- Compliance and reconciliation: Treasury and back-office systems use the BIC-to-ABA mapping to match incoming Fedwire credits against expected SWIFT confirmations from foreign counterparties.
- Customer support: When a wire is delayed, support agents look up the correspondent chain in seconds and can tell the customer exactly which intermediary is holding the payment.
The same dataset that powers the public lookup at ohmyfin.ai/correspondent-banks is available via API for production use, with rate limits, SLAs, and enterprise authentication suited to high-volume payment platforms.
Common Pitfalls When Using ABA for International Wires
Even with the right ABA in hand, there are a few details that trip up wire desks the first few times they handle a cross-border Fedwire:
Confusing ACH and Fedwire Routing Numbers
A bank can have two different routing numbers — one for ACH and one for Fedwire. They look identical (both nine digits) but they address different rails. Sending a Fedwire to an ACH-only routing number will be rejected. Always confirm that the ABA you have is the bank’s Fedwire routing number, not its ACH routing number. The Federal Reserve publishes the official Fedwire participants list, and any reputable lookup service distinguishes between the two.
Routing to the Foreign Bank’s U.S. Branch Instead of the Correspondent
Some large foreign banks have their own licensed U.S. branches with their own ABA routing numbers — for example, BNP Paribas New York Branch or HSBC USA. In those cases, the U.S. branch is the correspondent, and the ABA you need belongs to that branch directly. Smaller foreign banks, however, do not have a U.S. branch and rely on a third-party correspondent. The Ohmyfin lookup will tell you which model applies to a given BIC.
Forgetting the “For Further Credit” Field
If you address the Fedwire to the U.S. correspondent and forget to include a clear FFC instruction with the beneficiary’s name and account or IBAN, the funds will land in the foreign bank’s nostro and stay there until someone manually investigates. This is one of the most common reasons international wires go missing for days. Always include the ultimate beneficiary details, even if they feel redundant.
Currency Mismatches
Fedwire only moves USD. If the foreign beneficiary expects EUR, GBP, or another currency, the U.S. correspondent will perform an FX conversion at its own rate, which may be unfavourable. For non-USD international payments, a non-SWIFT U.S. bank may need to use a separate FX service or an alternative payment provider rather than relying on Fedwire alone.
When ABA Routing Is Not the Right Answer
It is worth being honest about the limits of this approach. ABA routing through a U.S. correspondent works very well for USD payments to major foreign banks that maintain established nostro accounts in New York. It works less well for:
- Small or regional foreign banks that do not have a dedicated USD correspondent and rely on chains of two or three intermediaries.
- Exotic-currency corridors where USD is not the natural settlement currency and FX conversion creates excess cost.
- Sanctioned or high-risk jurisdictions where U.S. correspondents have closed nostro relationships entirely.
- Same-day urgent settlements sent late in the U.S. business day, where the correspondent has already closed its overseas value-date window.
In those cases, the originating bank may need to upgrade to a full SWIFT membership, partner with a payments bank that can act as its SWIFT gateway, or use an alternative cross-border rail. But for the everyday case of “my customer needs to send USD to Europe, and we are not on SWIFT,” the BIC-to-ABA conversion path is fast, cheap, and reliable.
Summary: From BIC to ABA in Three Steps
- Get the foreign bank’s SWIFT/BIC code from the beneficiary. This is the one piece of information they will always provide.
- Look up the BIC-to-ABA mapping at ohmyfin.ai/correspondent-banks — either through the web interface or via API if you are running an automated payment platform. You will get the U.S. correspondent’s name, BIC, ABA routing number, and (where available) the foreign bank’s nostro account number.
- Send the Fedwire from your originating U.S. bank to the correspondent ABA, with the nostro account as the beneficiary bank account and a clear “for further credit to” instruction naming the ultimate beneficiary.
The whole process takes minutes once you know the pattern. The hard part is realising that the ABA routing number you need is not the foreign bank’s — it is the U.S. correspondent’s — and that the SWIFT/BIC the beneficiary keeps quoting is exactly the input you need to find it. Bridge those two worlds and the cross-border USD wire becomes just another domestic Fedwire with a few extra fields filled in.