Skip to main content

Overview

The Banking Connect Flows enable seamless integration of bank accounts into your application, allowing users to connect their financial institutions securely and efficiently. This overview provides a high-level understanding of the key components and processes involved in the connect flows.

Key Components​

  • Connect User Session: This is the initial step where a user initiates the connection process. A session is created to manage the user's interaction with the banking interface.

  • Management Session: After the initial connection, users can manage their connected bank accounts through a management session. This session provides an overview of all linked accounts and allows for additional connections.

  • Banking Interface: While we aim to provide a seamless experience, parts of the connection - especially authentication and consent - are handled directly by the bank. These steps follow the bank’s own technical standards and regulatory requirements (such as PSD2). Please note, that different interfaces at the same bank can lead to different available account types and different user experiences during the connection process.

  • Bank Login: This represents the user's connection to their bank account and the consent granted for accessing their bank data.

  • Recurring User: Users can be marked as recurring (recurring=true) for automatic synchronization of their bank data at regular intervals. Automatic synchronization requires storeSecrets=true on the same connect request (default: true); if explicitly set to false, transactions only refresh when a synchronization session is triggered manually.

  • Consent: User consent is crucial for accessing bank data. The system manages consent expiration and renewal to ensure compliance with regulations.

  • Strong Customer Authentication (SCA): The connect flows incorporate SCA mechanisms to enhance security during the authentication process.