bank_iban
Data license: CC-BY-4.0 · Data source: bankproducts.info
1 row where bank_id = "vdkb"
This data as json, CSV (advanced)
Suggested facets: iid_ranges (array)
| bank_id ▼ | clearing_number | iban_pattern | qr_iban_pattern | iid_ranges | qr_iid |
|---|---|---|---|---|---|
| vdkb | 00767 | CHxx 0076 7xxx xxxx xxxx x | CHxx 3076 7xxx xxxx xxxx x | ["00767", "76711", "76712", "76713", "76714", "76715", "76716", "76717", "76718", "76719", "76720", "76721", "76722", "76723", "76724", "76725", "76726", "76727", "76728", "76729", "76730", "76731", "76732", "76733", "76734", "76735", "76736", "76737", "76738", "76739", "76740", "76741", "76742", "76743", "76744", "76745", "76746", "76747", "76748", "76749", "76750", "76751", "76752", "76753", "76754", "76755", "76756", "76758", "76761", "76762", "76763", "76764", "76765", "76766"] | 30767 |
Advanced export
JSON shape: default, array, newline-delimited, object
CREATE TABLE bank_iban (
bank_id TEXT PRIMARY KEY REFERENCES bank(id),
-- 5-digit clearing number / Bankleitzahl (BC). Same as `sic_iid` for most
-- banks but stored separately because:
-- 1. some banks have multiple IIDs (a federation umbrella + its members)
-- 2. sic_iid is the SIX interbank-clearing participant number; clearing_number
-- is the IBAN-routing number — usually equal, occasionally different
clearing_number TEXT,
iban_pattern TEXT, -- "CHxx 0076 1xxx xxxx xxxx x"
qr_iban_pattern TEXT, -- "CHxx 3076 1xxx xxxx xxxx x" (QR-IBAN format)
iid_ranges TEXT, -- JSON array of 5-digit IIDs, e.g. '["00761"]'
-- Multiple values for banks with multiple BC numbers
qr_iid INTEGER -- Numeric QR-IBAN IID, e.g. 30761
-- (Range 30000-31999 is reserved for QR-bills)
);