Package Information
Documentation
n8n-nodes-ibanforge
IBAN validation, BIC/SWIFT lookup, Swiss clearing and compliance pre-checks inside your n8n workflows, backed by the IBANforge API and national bank registers (121k+ BIC entries, 89 IBAN countries).
Typical uses: verify supplier IBANs at onboarding, triage a payout list before the batch leaves, enrich a CRM record with the issuing bank, stop payments whose bank code the national register does not know.
Operations
| Operation | What it does |
|---|---|
| Validate IBAN | Structure + checksum + issuing bank (BIC), bank-code check against the national register (not_in_register means the register allocates the code to nobody), EMI/vIBAN classification, SEPA + VoP reachability |
| Look up BIC | BIC/SWIFT → bank name, city, country, LEI |
| Look up Swiss clearing | BC-Nummer / IID → institution, seat address, SIC/euroSIC/instant rails, QR-IID semantics |
| Compliance check | Bank-level sanctions (OFAC, EU, UN), FATF lists, SEPA/VoP, 0-100 risk score. Bank-level, not name screening |
Example workflow
examples/check-supplier-iban.json is a four-node workflow you can paste into n8n (Workflows → Import from File, or paste it on the canvas): a manual trigger, a field holding a supplier IBAN, the IBANforge node set to Validate IBAN, and an If node that routes on the valid field of the answer. Pick your IBANforge API credentials on the IBANforge node after importing.
Installation
Community nodes panel: Settings → Community nodes → Install → n8n-nodes-ibanforge.
Self-hosted CLI:
npm install n8n-nodes-ibanforge
Credentials
The node needs an IBANforge API key. The quickest one needs no e-mail and no card:
curl -X POST https://api.ibanforge.com/v1/keys/generate \
-H "Content-Type: application/json" \
-d '{"source": "n8n"}'
The answer carries an ifk_… key, shown once, worth 25 requests a month on every endpoint. Paste it into the node's IBANforge API credentials.
To raise that same key to 200 requests a month, claim it once it has served a call: POST https://api.ibanforge.com/v1/keys/claim with the key in the Authorization: Bearer ifk_… header, then the six-digit code mailed to the address you give for this. The steps are in the API keys guide.
Prefer to give an address from the start? Send it in the same call and the key starts at 200 requests a month:
curl -X POST https://api.ibanforge.com/v1/keys/generate \
-H "Content-Type: application/json" \
-d '{"email": "you@company.com", "source": "n8n"}'
The key dialog on ibanforge.com does the same from a browser.
Honest limits
- The bank-code check tells you what the national register says about the code inside the IBAN. It never claims the account exists or matches a name (that is Verification of Payee, a regulated-PSP scheme).
- Sanctions screening is bank-level (BIC8), not name-level, and is not a regulated AML/CFT product.
- Full API reference: ibanforge.com/docs · data provenance: ibanforge.com/docs/data-sources