Bank permission for Bank Feed

The connection to Bank Feed falls under the open banking principle and, specifically, the EU revised Payment Services Directive (PSD2). Every bank has rules, user roles and permissions for connections to services link Bank Feed. If these are not addressed correctly when authorizing a connection, a number of issues can arise in Bank Feed transaction processing.

The person who authorizes a Bank Feed connection needs to be the "right" person from the bank's perspective. Salesforce or FinDock user profiles are not relevant for the bank. Your FinDock admin who normally works with org configurations, for instance, is mostly likely not the person who needs to authorizing the connection to Bank Feed.

The user who grants formal consent for a Bank Feed connection needs to be the account holder or otherwise a legal representative of that account at the bank. The user needs to have access to the bank's online banking services. Typically, that user needs to have an explicit permission to share accounts with third parties. This permission may also fall under a general "Open Banking permissions," setting for the user or user role at the bank. Often this is an opt-in setting, that is, PSD2 sharing rights are not granted by default.

Even if you have the right user, that person may have multiple roles with the bank, If the user authenticates a Bank Feed connection with the wrong credentials, the Bank Feed connection may at first appear to be successful, but later fail.

Also note that not all bank accounts are sharable. You may need to change your bank accounts to be able to use PSD2 services.

Please check with your bank for the specific permissions and/or role your bank user needs to have for connecting to Bank Feed. Here we provide a examples to help you ask the relevant questions or check your online banking settings yourself.

Rabobank (NL) explicitly documents a discrete permission called “Rekening delen met derden” (“Share account with third parties”). An Eigenaar or BeheerderPlus must grant this authorization to the user in Rabobank’s business online banking portal. If this permission is missing, PSD2 connection attempts can fail because the user cannot legally/technically share accounts.

SNS (part of Volksbank, NL) has an extra safety step. Before users can give any third party access under PSD2, they must first turn on PSD2 sharing in the SNS app or Mijn SNS. If this is not turned on, the Bank Feed connection flow will eventually be blocked because the user does not have bank-side permission.

UK banks commonly require that the Payment Service User (PSU) is registered for online banking for the relevant bank before open banking connections are allowed. NatWest, for example, has “Third Party Permissions” management for connections to services like Bank Feed.

FinDock Bank Feed only works when your bank confirms two things:

1. The user setting up the connection is authorized to act on the account(s).
2. The user explicitly consents to share account information with the PSD2 service provider via the bank’s authorization flow.

Your bank does not share data automatically; you remain in control of what is shared and for how long.

While details differ by bank, the standard Bank Feed authorization flow goes like this:

1. You start the Bank Feed connection in FinDock.
2. You are redirected to your bank (mobile app or online banking).
3. The bank displays a consent screen listing the third party and the permissions being requested (typically “account information” / “transactions and balances”; sometimes also “payments” or “confirmation of funds”).
4. You select which account(s) to share (where the bank supports per-account selection) and confirm with Strong Customer Authentication (SCA).
5. You are redirected back to FinDock and Bak Feed begins syncing.

It is important to keep in mind that the same applies for re-authorization: the correct user needs to go through the same steps to renew the Bank Feed connection authorization. The duration of an authorization depends on your bank.

Most banks provide an overview in a mobile app or online banking environment. You can use this to confirm connections to Bank Feed as well as revoke authorizations for unused or unneeded connections. Typically these overviews have names like "Open Banking Connections" and "Third Party Permissions," or similar in other languages, like "Koppelingen en machtigingen" in Dutch.