Description
Check a supplied BBAN width and count preserved leading zeros without selecting a country format.
Identifier validation can involve several distinct questions: whether text has the expected shape, whether a checksum is consistent, and whether an authority actually assigned the identifier. Formatting and field extraction address narrower questions. Each result must be read according to the particular property the tool checks.
Check a supplied BBAN width and count preserved leading zeros without selecting a country format.
When to use this tool
Use Iban BBAN Leading Zero Width Check when you need the particular shape, formatting, field, or checksum property as one explicit stage in an identifier workflow.
How to use the tool and how it works
- Enter bban, expectedWidth. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read valid, leadingZeros. Inspect valid before interpreting the associated values.
Require expectedWidth from one through 30 and uppercase alphanumeric bban, allowing an empty token through the lexical gate. Return valid for matching width and leadingZeros as the count of initial zero characters.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| bban | Bban | Required. Text; maximum UTF-16 length 8192. |
| expectedWidth | Expected Width | Required. Safe integer; minimum 1; maximum 30. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| valid | Whether this tool’s particular check passes; does not imply broader identifier or protocol validity. | Required. Boolean. |
| leadingZeros | Leading Zeros | Required. Safe integer. |
{
"input": {
"bban": "001234",
"expectedWidth": 6
},
"output": {
"valid": true,
"leadingZeros": 2
}
}Limitations and assumptions
- The width is supplied rather than selected from a country registry. Leading zeros remain text, and checksum, bank routing, national account structure, and actual account existence are not verified.
- The field tables state structural bounds; the mechanics also specify cross-field constraints. Malformed inputs and unsupported domains cause errors. A successful false flag, empty branch value, or zero placeholder has the meaning stated above and is distinct from an input error.
Alternative or Complementary methods
Use a complete format and checksum validator when required, then consult the issuing registry or verification process for assignment and identity. Preserve meaningful leading zeros as text.
References
Similar or alternative tools
- GS1 AI Fixed Field Leading Zero Preserver
Preserve a supplied field verbatim while checking numeric fixed width and counting its leading zeros.
- GTIN Leading Zero Preservation Rule
Pad an accepted GTIN-length digit string to 14 characters and count its original leading zeros.