Handling Refresh with or without MFA

After your end-users has linked their account(s), you may need to access data from a utility account every month.

Refreshes can be fully automated without requiring the end-user presence, except in the following two scenarios.

1. MFA requiring end-user presence

In the scenario of a flow involving MFA such as OTP, end-users will have to link their account again in a re-connection flow, and go through the MFA each time you will want them to access refreshed data.

Here's an example of a user-present re-connection flow:

2. End-user password have changed

In the scenario where the end-user changed their password, a successful refresh will require them to link their account again through Deck Link.