Bank connection finAPI
Purpose
Account transactions should reach the system without anyone typing them in. This connection fetches them through finAPI, a licensed PSD2 aggregator.
Scope
- Set up a bank connection through the provider's web form — bank credentials are never entered
here.
- Fetch accounts and transactions for further processing.
- One finAPI user per link, not one per installation.
Interplay
Fetched transactions land in accounting and serve payment reconciliation there. The aggregator's credentials live as an integration under Integrations.
Limits
- Why an aggregator and not our own bank connection: accessing someone else's bank account is a
licensed activity in the EU. Through a licensed aggregator the licence stays with the provider — not convenience but the only route without a supervisory permission of our own.
- One user per link is deliberate. A shared user would hold all consents in one pot: a revocation
would drag other bank connections with it, and one link's account list would contain everyone else's accounts.
- The real run is still outstanding. Built against the documented endpoints, verified against a
stubbed client — not against a real finAPI environment. A real run follows once credentials are available.
- The provider's service is chargeable and is contracted directly with them.