Recurrent links are supported for any kind of institution.
However, all the business institutions require a fresh MFA (Multi-Factor Authentication) token for any new data refresh, which prevents providing a fully automated recurrent links experience.
You'd be able to create a recurrent link and we'll automatically retrieve fresh data. But with each weekly refresh, you'll be asked for a fresh token to be completed.
For each refresh attempt, you will be receiving a token_required webhook asking for a token. The webhook will provide the token_generation_data information to generate this token. However, this token_generation_data information expires and it can be invalid by the time you ask your users.
Fortunately, we have some strategies that will help you update business bank recurrent links.
In order to provide a good experience with frequent updates of recurrent business bank links, we suggest the following strategies:
Recurrent links with guided updates
Instead of directly asking for a new MFA token as soon as you receive the token_required webhook event, we suggest you wait and ask the final user when you want. This is to avoid excess notifications to the users, as we could send this webhook event multiple times a day depending on your recurrent link refresh policy.
To ask for a new token, we suggest you use our Connect Widget update mode. By providing a link_id to the widget, we'll handle the full process, from asking the token to collecting new data for your link. As soon as the new refresh is made using the new token, will notify you via webhooks with all data available.
Hybrid model single/recurrent
A less recommended strategy is to handle retail banking links as recurrent ones and business banks as single ones.
It could help you control better the business bank updates manually when you need fresh data.
This strategy still involves providing a new MFA token using the widget update mode. Once the new token is provided, you'll be able to retrieve manually new transactions, accounts, and owners.