Skip to main content

Webhooks and Bank Data Delivery

In combination with both procedures for importing bank data, the system provides multiple mechanisms to ensure that the retrieved bank data is delivered to you in a timely and efficient manner. Of course, there are several endpoints available to retrieve the bank data on demand, but we also provide mechanisms to automatically send the bank data to you without the need for you to trigger a request. This is especially useful for recurring connections, where the bank data is automatically synchronized on a regular basis, and you want to receive the updated data immediately after each synchronization. For this very reason, we provide webhooks:

Webhook Call After Bank Account Integration​

Once a bank account is successfully connected, the system automatically sends bank data via webhook - provided that the configuration is correct. For more information on how to set up webhooks, please refer to our webhooks specification. For this type of webhook there is no more differentiation between recurring and non-recurring users, as the webhook is triggered immediately after the connection process is completed, regardless of the user's recurring status.

Automatic Synchronization via Scheduler​

This webhook type works only with recurring users, as it is triggered after each successful synchronization of the bank connection. After each successful synchronization, the system automatically sends the updated bank data via webhook, ensuring that you receive the most recent data without any delay. This is especially useful for use cases that require regular updates of bank data, such as financial management applications, budgeting tools, or any other application that relies on up-to-date financial information. Please note that the synchronization is executed automatically at regular intervals, there is no configuration available to change the synchronization frequency or schedule.

Synchronization Frequency and Scheduling Behavior​

The automatic synchronization is executed twice daily. Each sync cycle processes all eligible recurring users sequentially. The following scheduling characteristics apply:

  • Newly created recurring users are enrolled in the next available sync cycle. Depending on when the user was created relative to the current cycle, the first synchronization may occur in the subsequent cycle rather than the current one.
  • Execution order and timing within a sync cycle depend on the number of enrolled users and their distribution. This means that individual sync executions may experience slight delays depending on the overall queue position.
  • There is no guaranteed fixed time at which a specific user's synchronization will be executed. The system processes all users within the cycle window, but the exact timing for each user may vary.

To verify that synchronization has been completed for a specific user, use the Get Logins Synchronization Status endpoint and check the lastSynchronization timestamp.

Manual Synchronization​

As mentioned before, you can also trigger a manual synchronization for a specific bank login using our Create Synchronization Session endpoint. For recurring connections, the synchronization is executed immediately provided there is still a valid consent available. For non-recurring connections, the synchronization requires explicit end-user consent and is executed asynchronously, as the user needs to complete the necessary Strong Customer Authentication (SCA) steps to grant a new consent. Once the bank data has been successfully retrieved, the system delivers the updated data via webhook.