# Flow Overview (/es/data-api/guides/link-widget/flow-overview)

Understanding the steps in the Fiskil consent flow



The Fiskil Link widget guides users through a multi-step consent flow. Understanding each step helps you design a better user experience and handle edge cases.

Flow Steps [#flow-steps]

1. Institution Selection [#1-institution-selection]

Users first see a list of available institutions (banks or energy providers) they can connect. The list is filtered based on your account configuration.

2. Authentication [#2-authentication]

After selecting an institution, users authenticate with their existing credentials at that institution. This typically involves:

* Username/password entry
* Multi-factor authentication (SMS, email, or app-based)
* Security questions

3. Account Selection [#3-account-selection]

Once authenticated, users see a list of their accounts at the institution. They select which accounts to share with your application.

4. Consent Confirmation [#4-consent-confirmation]

Users review the data being shared and the consent duration. This screen displays:

* Your company name and logo
* Fiskil's name, identifying it as the accredited party facilitating the connection
* Data types being requested
* Consent period (how long you'll have access)
* Purpose of data access (your configured use cases)

In Australia (CDR), the accredited data recipient facilitating the sharing must be identified to the user, so Fiskil's name appears alongside yours — this can't be configured away.

5. Completion [#5-completion]

After confirming, the SDK returns a `consents` array to your application. Handle every consent ID and use webhooks to confirm when data is ready.

Handling Different Outcomes [#handling-different-outcomes]

Successful Completion [#successful-completion]

The user completed the flow. The SDK resolves with `consents: string[]` and an optional `redirectURL`. See [Handling the Result](/data-api/guides/link-widget/integrating-the-link-sdk#result).

User Cancellation [#user-cancellation]

The SDK rejects with an error. Calling `flow.close()` while the flow is pending returns `LINK_USER_CANCELLED`. Cancellation in the hosted authorisation flow returns `AUTH_SESSION_CANCELLED`; create a new Auth Session before reopening Link.

Authentication Failure [#authentication-failure]

The user entered incorrect credentials or failed multi-factor authentication. They can retry or cancel.

Institution Unavailable [#institution-unavailable]

Occasionally an institution may be temporarily unavailable. The user will see an error message and can try again later.

Best Practices [#best-practices]

1. **Prepare Users**: Explain what data you'll access and why before launching Fiskil Link. See [Fiskil Link messaging](/data-api/guides/link-widget/messaging) for guidance and example screens.
2. **Handle All Outcomes**: Implement proper error handling for cancellations and failures
3. **Listen for Webhooks**: Don't rely solely on the client callback—use webhooks for reliable data sync notifications
4. **Test Thoroughly**: Use the sandbox environment to test various scenarios
5. **Explain Fiskil's Role**: Tell users up front that you use Fiskil, an accredited data recipient, to connect their account — users who see this before the flow starts are less likely to raise a support ticket asking who Fiskil is
