Fedwire Routing District Decoder
Decode supported ABA routing district-prefix families 01–12, 21–32 and 61–72 separately from checksum; other prefixes stay unclassified and no Fedwire participation or institution assignment is inferred.
Description
Routing-prefix decoding and American Bankers Association (ABA) routing checksum testing answer different questions.
Routing-prefix decoding and American Bankers Association (ABA) routing checksum testing answer different questions. Supported prefix families map to a reserve-district number without establishing network participation.1
The returned values include Observed routing prefix, Decoded reserve district, Supported district prefix family, Routing checksum matches, District decode available. The How section below explains the calculation, input rules and interpretation.
When to use Fedwire Routing District Decoder
Use Fedwire Routing District Decoder when you need to evaluate the supplied records under the calculation and evidence rules below. No Fedwire participation, current institution assignment or account verification is supplied.
Prepare observed financial records and verified caller terms. Use one currency for integer minor-unit money and preserve leading zeros in identifier text. One basis point is 0.01 percentage points. Resolve dates, local clocks, counting rules and evidence flags as specified.
How to use Fedwire Routing District Decoder and understand its results
- Prepare observed financial records and verified caller terms. Use one currency for integer minor-unit money and preserve leading zeros in identifier text. One basis point is 0.01 percentage points. Resolve dates, local clocks, counting rules and evidence flags as specified.
- Enter routingNumberText using the field table and calculation rules, then run the tool.
- Read observedRoutingPrefix, decodedReserveDistrict, supportedDistrictPrefixFamily, routingChecksumMatches, districtDecodeAvailable. The explanation below defines the units, signs, ordering and any flags or placeholder values.
- If the tool reports an input issue, correct the values and run it again. Apply the stated assumptions when interpreting a successfully returned result.
| Input field | Meaning | Value type; see rules below | Requirement |
|---|---|---|---|
| routingNumberText | Routing number text | string | Required |
Enter exactly nine ASCII routing digits without trimming or newline. Decode the first two digits independently of the repeating 3,7,1 checksum. Return original prefix text, district, ordinary/thrift-offset/electronic-offset/unclassified family, checksum flag and decode-availability flag. Unsupported families return −1 and false availability, even with a valid checksum.
district=prefix for 01–12; prefix−20 for 21–32; prefix−60 for 61–72; otherwise −1 Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.
| Output field | Meaning | Value type |
|---|---|---|
| observedRoutingPrefix | Observed routing prefix | string |
| decodedReserveDistrict | Decoded reserve district | number |
| supportedDistrictPrefixFamily | Supported district prefix family | string |
| routingChecksumMatches | Routing checksum matches | boolean |
| districtDecodeAvailable | District decode available | boolean |
{
"input": {
"routingNumberText": "021000021"
},
"output": {
"observedRoutingPrefix": "02",
"decodedReserveDistrict": 2,
"supportedDistrictPrefixFamily": "ordinary",
"routingChecksumMatches": true,
"districtDecodeAvailable": true
}
}Limitations and assumptions
No Fedwire participation, current institution assignment or account verification is supplied.
Numeric inputs, where present, must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Extremely large text inputs are rejected. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors. A successfully returned false flag is an evaluated outcome; its meaning is explained above.
Alternative or Complementary methods
Use MICR Line Routing Account Parser: Normalized MICR notation separates routing, account and check serial text. Explicit delimiters preserve leading zeros without guessing an OCR layout. For a complementary task, use BIC SWIFT Code Structure Validator: A BIC parser separates institution, country, location and optional branch text. A syntactic match does not establish assignment or reachability.
References
-
Fedwire Routing District Decoder — tool.io
Similar or alternative tools
- MICR Line Routing Account Parser
Normalized MICR notation separates routing, account and check serial text. Explicit delimiters preserve leading zeros without guessing an OCR layout.
- BIC SWIFT Code Structure Validator
A BIC parser separates institution, country, location and optional branch text. A syntactic match does not establish assignment or reachability.