Local evidenceFormat and character rules + Field anatomy and parser evidence
Browser-checkable work only
BoundaryNo live source proof
Official state remains external
Why this exists
Know what can be trusted before wiring the value into production.
SWIFT/BIC structure pages in ValidoHub are tool-first. This reference layer explains the checks, fixtures, developer handoff, and source-system limits so teams can integrate the live workbench output deliberately.
Use forImplementation planning
Choose normalization, storage, masking, and fixture strategy.
Use forQA and CI fixtures
Keep pass, review, malformed, and edge examples beside the code.
Use forDeveloper handoff
Copy the live tool JSON instead of reverse-engineering display text.
Browser checks
Local evidence the workbench can expose.
CheckFormat and character rules
Use the workbench for current evidence.
CheckField anatomy and parser evidence
Use the workbench for current evidence.
CheckMasked and normalized outputs
Use the workbench for current evidence.
Official boundary
Where local validation must stop.
BoundaryAccount, company, person, or ownership status is not proven by browser-only checks.BoundaryNo live network, registry, bank, payment, or tax-office lookup is performed.
Integration traps
Small mistakes that create expensive debugging later.
TrapDo not treat a valid checksum as proof that the value exists in an official registry.TrapKeep display strings, compact storage values, masked output, and exported JSON separate.TrapUse stable machine fields and error codes; do not parse translated UI strings downstream.
Run the workbench
SWIFT / BIC Workbench
Validate, generate, inspect, copy, or export the current value in the browser.