United StatesFederal regulator recordsComplete Data Health Report
A readable view of database integrity, verified coverage, routing provenance, release gates, and evidence-dependent advisories.
0 failures · 0 warnings · 2 advisories
Verified dataset coverage
Licensed ABA coverage remains intentionally visible when incomplete.
Payments Canada electronic-routing coverage across Canadian locations.
Official location records with a usable street address and city.
Canonical institutions retaining the complete official source record.
Locations retaining a complete regulator/source payload.
Active ABA provenance and activation state
- Active source
- Sentinel verified ABA baseline
- Source type
- single_record_verification
- Source version
- 2026-07-20
- Provider
- Bank Finder Pro verified routing evidence
- Activated records
- 1
- Schema version
- v1
- Last activation
- 2026-07-21T00:34:28.899590+00:00
- Dataset fingerprint
- MATCH
- Dataset SHA-256
724ac742fe8f0d5671199354fd725814be39eb229dfa4326559412a430b9fef9- License/evidence reference
- Per-record official-institution verification retained from Sentinel; no complete ABA dataset license claimed.
Every Health Center check
SQLite integrityRelease gate
The complete live database must pass SQLite's structural integrity check.
Verified directory scaleRelease gate
A release is blocked if institution or location counts collapse below the verified baseline.
Routing data foundation schemaRelease gate
The canonical ABA table must be protected by the versioned staging, provenance, activation-history, and rollback schema.
Active routing dataset provenanceRelease gate
The active ABA dataset requires a named provider, source type, version, license reference, artifact hash, and activation record.
Active routing dataset fingerprintRelease gate
The live aba_routing rows must match the immutable dataset fingerprint and record count stored at activation.
Staged routing candidate blockers
Candidate imports remain isolated from live search until every format, checksum, duplicate, conflict, linkage, provenance, and count gate passes.
Active routing source scopeAdvisory
The current single-record verification baseline is honest but incomplete; complete coverage requires an authorized complete dataset.
ABA routing dataset loadedRelease gate
U.S. routing-number search is blocked when this table is empty.
FAIRWINDS routing regressionRelease gate
263181368 must exist exactly once and remain linked to NCUA institution 68417.
Exact routing-address map inputRelease gate
Google Maps must receive the routing record's exact 3087 N Alafaya Trail address.
Orphan relationship protectionRelease gate
Routing, location, ATM, and source records must retain valid parent relationships.
ABA format and checksum validationRelease gate
Every ABA record must contain nine digits and pass the routing checksum.
Canadian routing format
Electronic routing identifiers should use the nine-digit 0YYYXXXXX representation.
U.S. ABA relationship coverageAdvisory
Coverage is reported honestly; incomplete licensed ABA data does not silently appear complete.
Location map readiness
A location is map-ready when the official record contains a street address and city.
Unresolved exact duplicate records
Exact duplicate locations are merged automatically only when every canonical field and source record agrees; any unresolved identity conflict remains in the evidence queue.
Canonical institution identityRelease gate
Every canonical institution requires a name and country.
Relationship and source-record counts
- U.S. institutions
- 8,638
- Canadian institutions
- 403
- U.S. locations
- 101,011
- Canadian locations
- 20,498
- Orphan locations
- 0
- Orphan ATMs
- 0
- Orphan ABA records
- 0
- Unresolved exact duplicates
- 0
- Verified source families
- 4
- Generated
- 2026-09-09T06:43:22.897754+00:00
CanadaOfficial institution records