Webank API Access & Open Banking Integration
Webank is an Italian online bank offering personal current accounts, and open-banking.io lets you reach its data without wrestling with eIDAS certificates or a PSD2 sandbox. You connect once through a guided dashboard, and from then on your Webank balances and transactions live alongside every other account you hold across the 2,600+ European banks the service supports.
What makes the approach different is where the trust sits. open-banking.io is zero-knowledge: encryption keys are generated on your own device and only the public half ever reaches the servers. Nothing readable is stored centrally, so your Webank statements stay yours in the strongest sense.
How to connect Webank
Connecting is done entirely in the open-banking.io dashboard — there is no API call, code, or key involved in this step.
- Sign up for open-banking.io and set an encryption passphrase. Your keys are created locally, on your device.
- In the dashboard, search for Webank (BIC WEBNITMMXXX) and choose the personal account type.
- You are redirected to Webank's own secure login, where you approve access under PSD2 — your credentials are only ever entered on the bank's page.
- Consent runs for up to 180 days, after which you simply re-approve on Webank's screen.
- Your accounts sync back into the dashboard and stay up to date.
Access your data
Reading Webank data programmatically is an optional step you take after connecting. From the Developers page, create an API key and export a credentials.json — this bundles the API key together with your private decryption key. With it you can use the CLI (openbanking accounts, openbanking transactions, openbanking sync), an SDK, or the REST API directly.
Every request carries the X-Api-Key header, and each response is decrypted locally with your own key. An API key on its own only ever returns ciphertext — without your private key, nobody, including open-banking.io, can read a single transaction.
The whole service costs around EUR 3/month.
Can I connect Webank with the CLI or an API call?
No. Connecting always happens in the dashboard, where you approve access on Webank's own consent screen. The CLI and SDK only read and sync connections that already exist.
Does open-banking.io store my Webank login or data?
No. Your login is entered solely on Webank's page, and the platform holds only your public key — it cannot decrypt anything you sync.
How long does access last before I re-approve?
Webank consent is valid for up to 180 days. When it lapses, you renew it in seconds through the bank's consent flow.
Ready to start? Visit open-banking.io.