Nine-digit ABA routing transit number identifying a U.S. financial institution or processing point for checks and specified electronic payments.
A routing number, formally an ABA routing transit number (RTN), is a nine-digit identifier used to route U.S. checks and specified electronic payments to the responsible financial institution or processing point. It identifies the institution side of an instruction; the accompanying account number identifies the customer account.
The American Bankers Association describes the nine-digit structure as:
1XXXX YYYY C
| Component | Purpose |
|---|---|
XXXX | Federal Reserve routing symbol |
YYYY | ABA institution identifier |
C | Check digit used to detect certain entry errors |
The first component reflects routing-number policy and historical processing classifications. It should not be decoded casually to infer a bank’s current branch, solvency, charter powers, or payment capabilities.
A routing number is not necessarily a single permanent code for an entire brand. Institutions can have multiple numbers, and a merger can leave legacy numbers in service during a conversion period.
The right number can depend on:
For this reason, a routing number found on a generic search page or an old check should not automatically be reused for a wire transfer.
| Payment type | How the routing number is used | What to verify |
|---|---|---|
| Paper check | Identifies the paying bank or processing point in the MICR line | Current check stock and bank instructions |
| ACH credit | Routes direct deposit or another credit to the receiving depository institution | FedACH participation, account type, and credit instructions |
| ACH debit | Routes an authorized debit to the receiving institution | Routing validity, account validation, authorization, and Nacha rules |
| Fedwire Funds transfer | Identifies a Fedwire participant or receiving endpoint | Wire-specific instructions and Fedwire eligibility |
| International wire | May appear in U.S. beneficiary instructions with BIC and correspondent details | Complete international instructions from the receiving bank |
The Federal Reserve’s E-Payments Routing Directory provides service-specific information for FedACH and Fedwire participants. Presence in one context should not be generalized beyond the directory attributes and the bank’s instructions.
| Identifier | Identifies | Example role in an ACH credit |
|---|---|---|
| Routing number | Receiving financial institution or processing point | Sends the entry to the receiver’s bank |
| Bank account number | Customer account in the bank’s records | Directs posting inside the bank |
| Account type | Checking, savings, or another supported class | Helps the bank interpret the account record |
| Payment reference | Payroll, invoice, customer, or purpose | Supports reconciliation after routing |
All fields can matter. A correct routing number combined with a wrong account number can still misdirect or return the payment.
Assume a company stores these beneficiary instructions:
RTN-A;RTN-W; andACCT-1.The company sends a $120,000 same-day vendor payment through Fedwire but populates the message with RTN-A copied from an old ACH authorization.
Several outcomes are possible: the payment platform can reject the instruction, route it to a different processing endpoint, hold it for repair, or require the sender to submit corrected instructions. The account number alone cannot direct the wire to the right bank.
A stronger workflow would:
Consumers can often find an ACH or check routing number in their bank’s authenticated app, online account, statement, or check. Businesses and financial institutions should use current bank instructions and an authorized routing directory suitable for their payment process.
Useful verification questions include:
Nacha has warned ACH participants that additions, deletions, mergers, and routing changes make regularly updated routing information important. A cached list can become operationally stale even if each entry was once valid.
Routing validation answers whether the institution identifier is plausible and current for a rail. It does not establish:
For certain online consumer ACH debits, Nacha rules require account validation as part of a commercially reasonable fraud-detection system. Even that minimum account validation does not automatically prove ownership. Organizations should understand the exact scope of each vendor or bank response.
After a merger, the surviving institution can maintain, consolidate, or retire routing numbers under applicable policy and transition plans. Old numbers may continue temporarily, but users should not assume an indefinite grace period.
Update:
Monitor bank notices and returned-entry information instead of silently retrying failed payments with the same stored data.
Payment requirements, return rights, and fraud controls vary by rail and account. This page provides general education, not banking operations, legal, compliance, or fraud-recovery advice.