VR-Bank Würselen API Access & Open Banking

Reaching your VR-Bank Würselen accounts programmatically usually means TPP licences, eIDAS certificates and a lot of PSD2 paperwork. open-banking.io removes all of that. You get a single dashboard for VR-Bank Würselen (BIC GENODED1WUR) covering both business and personal accounts, with a consent that stays valid for up to 180 days before you renew it. Everything your bank returns is encrypted and only ever readable with a key that lives on your own device.

How to connect VR-Bank Würselen

Connecting happens entirely inside the open-banking.io dashboard — there is no API call, code or key involved in this step.

  1. Sign up for open-banking.io and set your encryption passphrase. Your key pair is generated locally on your device; open-banking.io only ever stores your public key.
  2. In the dashboard, search for VR-Bank Würselen and choose the account type you need (business or personal).
  3. You are redirected to VR-Bank Würselen's own secure login and consent screen, where you approve access under PSD2 — your credentials go only to the bank.
  4. Once approved, your accounts and transactions sync straight into your open-banking.io dashboard.

Because approval takes place on the bank's own consent page, open-banking.io never sees your login details, and no certificate of your own is required.

Access your data

Want to pull VR-Bank Würselen data into your own code? That is an optional step you take after connecting. On the Developers page, create an API key and export a credentials.json — it bundles the API key together with your private decryption key. Then use the CLI (openbanking accounts, openbanking transactions, openbanking sync), an SDK, or the REST API. Requests authenticate with the X-Api-Key header, and every response is decrypted locally with your own key. The CLI and SDK only read and sync connections that already exist — there is no connect command.

This is what zero-knowledge means in practice: an API key alone returns only ciphertext, because the servers hold your public key and nothing that can decrypt it. All of this runs for roughly EUR 3/month.

Is a bank certificate or TPP licence required?

No. open-banking.io is certificate-free — you connect through VR-Bank Würselen's standard consent flow, no eIDAS certificate needed.

Can open-banking.io read my VR-Bank Würselen transactions?

No. Data is decrypted only on your device with a key you alone hold. The service stores your public key, never anything that can reveal your data.

How long does access last before I reconnect?

VR-Bank Würselen consent is valid for up to 180 days, after which you re-approve on the bank's consent screen.

Start at open-banking.io.