Enable Banking Changelog | August 2025

Written By Fedor Tyurin
 

As always, if you have any questions, feel free to reach out to us at support.api@enablebanking.com.

Significant Changes and Updates

Extended FAQ: Transaction fetching with a continuation key

We’ve added a new FAQ entry explaining how the continuation key mechanism works for transaction fetching. 

As the Enable Banking API does not store the account information it processes, we provide a unified approach for fetching transactions that behaves consistently for all integrated ASPSPs.

If all transactions cannot be returned in a single API call, the response will include  a continuation key. These keys are used in subsequent requests to fetch the remaining entries until the full list is retrieved.

Our extensive FAQ entry helps clarify the logic behind the process and gives developers a clear reference point, making a problem resolution easier.

 

Back office toolset improvements

In addition to maintaining our systems and rolling out new API integrations, we continuously enhance our internal tools to improve  efficiency and reliability. Our back office suite already includes functionality for invoicing, statistics, application management, to name a few.

Recent updates to our backoffice suite include:

Secure credentials management for  ASPSP API dashboards

Many ASPSPs provide dashboards where TPPs register sandbox and production apps, requiring TPP-specific credentials. We’ve implemented a secure system for managing these credentials, ensuring stronger protection and smoother workflows. 

Expanded automated onboarding functions for ASPSPs

Since launching our automated onboarding tool in February, its scope has grown significantly. When ASPSPs support onboarding or certificate renewal programmatically through API endpoints (dynamic client registration) we build support for its functionality directly into our internal tool. Our suite now covers 20+ ASPSPs with automated onboarding functionality. This reduces the friction during certificate changes, and enables a faster, smoother go-live rollout for our licensed clients.

 

Integration Updates

We continue to refine and expand our banking API integration network to ensure robust and efficient banking solutions.  Here are the latest updates across our integrations:

Fixed and Improved Integrations

Alongside the new integrations, we rolled out fixes and improvements to keep performance and reliability high across existing integrations. Updates this month include: 

  • Abanca (ES)

  • Argenta (BE)

  • Arion banki (IS)

  • Atruvia (DE)

  • Banca Transilvania (RO)

  • Banco Posta (IT)

  • Belfius (BE)

  • BNP Paribas Fortis (BE)

  • CIB Bank (HU)

  • Commerzbank (DE)

  • Coop Pank (EE)

  • Crédit Mutuel (FR)

  • DSK Bank (BG)

  • Eurobank (GR)

  • Kvika (IS)

  • Landkreditt Bank (NO)

  • LHV Pank (EE)

  • MBH Bank (HU)

  • Nordea (DK, FI, NO, SE)

  • Revolut (AT, BE, BG, CY, CZ, DE, DK, EE, ES, FI, FR, GB, GR, HR, HU, IE, IS, IT, LI, LT, LU, LV, MT, NL, NO, PL, PT, RO, SE, SI, SK)

  • Skandia (SE)

  • SpareBank 1 (NO)

  • Sparkasse (DE)

  • UniCredit (DE, IT, AT, SI)

  • Vivid Money (DE, LU, IT, ES, FR)

You can find a comprehensive list of integration changes here.

Fedor Tyurin
Next

Enable Banking Changelog | July 2025