[Feature]: Add support for open banking synchronization

[gjong]

Summary

As a user
I want to be able to automatically synchronize with my bank
so that I do not need to enter each transaction manually.

There is a ready made solution with openbanking.io that supports most EU banks. It should be possible to set that up as one of the importing sources.

Need to investigate

• how to set this up in code properly along side the already existing CSV import.
• look at integration options with open banking
• create an updated architecture desing

Sub tasks

• purchase account to develop this properly and test it properly
• build the feature
• update documentation

What alternatives have you considered?

• Looked at integration with EU banks. But this requires each user to qualify their installation.
• investigated other API operators, but most require an expensive certificate.

Open questions

Properly mark this as a paid integration for the user. The open banking costs money per account linked.

[john-frandsen]

Hi @gjong — saw this feature request and wanted to help directly, since I maintain open-banking.io.

Quick clarification on the eIDAS certificate concern in "What alternatives have you considered": the reason most EU bank API operators require an expensive certificate is PSD2's eIDAS QWAC + QSeal requirement (typically €2,000–10,000/year). This is the single biggest barrier for self-hosted personal finance projects.

open-banking.io was built specifically to absorb that cost on behalf of developers — so you don't need to qualify your installation or hold a certificate yourself. Each user's bank consent flow goes through our regulated infrastructure.

For the integration alongside your existing CSV import, the practical approach would be:

1. Authentication: Users authorize their bank via a redirect consent flow (standard PSD2 AIS). You get back a consent ID + reusable access token.
2. Transaction sync: A scheduled job calls the transactions endpoint per linked account — similar to how you'd poll a CSV source, but the data is live.
3. Architecture: A new OpenBankingImporter alongside your CSV importer, sharing the same transaction normalization pipeline. The importer calls the API, maps fields, and feeds your existing ingestion layer.

I'm happy to help with:

• API documentation and sandbox credentials for development/testing
• Architecture review for the importer design
• Pricing questions for the "paid integration for the user" open question

Feel free to ping me here or at john@open-banking.io if you'd like to move forward. Happy to get you set up with a test account.