Multiple access
Summary
Multiple access service allows you to get a consent for continuous access to the end-user’s data for up to 180 days without them having to log in to their account each time you request the data.
The service is based on the Banking API, despite having some differences on its own.
How does it work?
In order to use this Multiple access you need to sign a contract for the service, it is a separate feature that is billed differently than regular Banking API service (Single mode access).
Once you’ve done that, you need to:
- Adjust your SignIn Widget code to specify access mode.
- After the user successfully signs in, you will receive multipleAccessId for later use.
- Each time you want to download fresh data, call Reuse Multiple access endpoint to get new session information.
- Import data as you would in Banking API.
You will find more detailed information in our Documentation.
Are there any limitations?
Yes, due to technical reasons and PSD2 as well as RTS regulations, there are some limits involved:
- The access is given for up to 180 days. The period can be shortened if either the bank or the user revoke the access earlier.
- Using Multiple access, the session created right after the first end-user log in allows you to fetch the same amount of transaction history as you would get via Single access. However, each subsequent session within Multiple access will only return data up to the last 90 days.
- Using Multiple access, you can import data up to 4 times in a 24 hour timeframe. This number can be lower if the user gave his account access to another company as well.
Availability
At the moment, Multiple access is available only for select targets in Poland and Czech - you will find them here (the targets using this feature will be marked “Yes” in the “Multiple access” column).
The service will only work with PSD2 API connections so if you’re switched to a fallback version of a given target, even for Single access, it will not work in the multiple access mode.
FAQ
Every Multiple access consent is split into 30-day cycles of availability. At the end of each month you pay a basic fee per each cycle that ended within that month and additional fee for every successful Banking API session within those cycles.
The basic fee for a consent will not apply if all sessions end with an error within a cycle. However, if no import is made within that period or all have been abandoned by you (after using the Reuse Multiple Access endpoint), the basic fee will still apply.
If a consent has been withdrawn before the end of the 30-day cycle (if for example the user withdraws the consent), you will still be charged fully for that cycle.
Contact our Sales team to get more info and a quote for your business.
As we recently launched this service, we don’t have enough production usage to be sure that the service is sufficiently stable. There might be some bugs (including major ones) that we haven’t encountered yet - either in banks’ APIs or on our side.
Additionally, with more clients testing the service, we might make adjustments to fit better the actual usage and improve user experience.
Please note that this also means changes in our API and documentation, some of which will need to be implemented by you more often than when it comes to our stable services. The changes might cover supported banks, integration methods, used parameters, terms of use or any other part of the feature.
We will look into expanding the service as soon as the beta phase concludes.
With that said, we are still limited by some APIs’ basic quality as well as actual demand in certain clients for this service.
If you have any specific banks or countries in mind, contact our Sales team to discuss your needs.
