finAPI User
- Peter Schöll
Add finAPI access:
From the new release April 2023, a global finAPI user is automatically created for the user's email address and stored in a central database when a new access for finAPI is added
In the Set up access form, you can see under the expert settings (further actions) whether the global finAPI user already exists for the user's current email address
The setup process is the same as before, the accounts imported or accessed with the global user are displayed in online banking. In the event that these accounts have already been set up for finAPI (previously finAPI access was saved per company), in addition to the existing accounts. The accesses can be distinguished from each other via the access name in the online banking form.
The batch updates are of course also set up after adding new accounts with the global finAPI user.
Import finAPI access:
There is a new button "Import finAPI access" in the Online banking access form. This function can be used to import an already created account (bank details) of the global finAPI user of the current user in the Online Banking form (if the account is used for several companies/instances)
If only one account is available for import, it is automatically imported and saved.
If several configured accounts are available for import, these are offered for selection.
After importing the account(s), you can use the "Add/remove online banking accounts" option for each account to select the desired accounts for retrieval in this company's online banking.
Why was this function created and what are the benefits for customers?
In certain cases, there was a problem with so-called consent invalidation. This always occurs when a user accesses different accounts of the same bank in several companies/instances. In such cases, the finAPI access of company 2 invalidated the access of company 1 (i.e. batch updates then no longer work, a new strong authentication with login and TAN entry would be necessary).
This is prevented by creating the global finAPI user for each user, as one finAPI user is used for each user's email address across all companies/instances, so that all retrievals can always be made via the same Consent.
Will finAPI accesses that have already been set up also be converted to global finAPI users?
No. Customers who have set up access per company and who do not have the problem of consent invalidation do not need to do anything and can continue to work with their existing access.
Have there been any functional changes to the retrieval of account movements or transfers (individual transfers or payment runs) as a result of the changeover?
No, only the way in which accounts are created and managed has changed, but not the way in which the functions mentioned above work.
Why has the "Remove unfinished receipts" option been removed from the expert settings?
Under the previous model, unfinished accesses were removed depending on the company. As the logic is now different, unfinished accesses can now be completed via the "Import finAPI access" option and no longer need to be removed.
How is it ensured that finAPI users are deleted again when they are no longer needed?
There is a reference number in the central database that stores the number of activated Scopevisio accesses per mail address. The counter is increased accordingly when new accounts are created or automatically reduced when accounts, companies or instances are deleted. If the last reference is deleted, the finAPI user is also removed from the database and finAPI.