Enable Banking Changelog | September 2024

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

Significant Changes and Updates

Multi-Factor Authentication (MFA) - Enhanced Security of Developer Accounts

We've made enhanced security a top priority, especially for developers managing applications approved through automation. To enhance protection, we've introduced the following measures:

MFA for User Accounts: We've added support for MFA to user accounts on the Enable Banking Control Panel. To activate MFA, simply log in to your EB account, navigate to the "Profiles" tab and register your phone number to receive MFA codes.

MFA Requirement for Application Sharing: When sharing applications with other users, we now verify that both parties have the same level of account protection. Meaning, if you have MFA enabled, the other user will also be required to activate it before accessing the shared application.

To enable MFA, click here and select "Enable." You will be guided through a quick process to secure your account and applications with MFA.

Information About PSU and Payment Support Types in the Open Banking APIs List

Banks provide a variety of payment types tailored to individual markets and use cases. Our revamped Open Banking APIs page now offers a comprehensive view of all available payment options for each ASPSP. This resource makes it easier to assess payment possibilities across different markets and banks.

eIDAS Broker Security Updates

We’ve upgraded several outdated vulnerable dependencies and released new docker images. Additionally, you can now provide keys and certificates as environment variables. To enable this functionality, pass the KEY_LOADER=ENV environment variable when starting the container. The environment variables should be named with _CRED suffix. For example, the QWAC private key should be provided in the QWAC_KEY_CRED environment variable.

Integration Updates

Our ongoing efforts to refine and expand our banking API integration network ensure robust and efficient banking solutions. Check out the latest updates across our connectors:

New Integrations

The following AIS integrations have been added:

  • Shine (FR)

Also actualized the list of brands supported by the integrations for Sparkasse and National Association of German Cooperative Banks (Volks- und Raiffeisen banks).

Fixed and Improved Integrations

Integrations towards the following ASPSPs received various improvements and fixes: 

  • Arkea Banking Services (FR): Fixed transactions filtering by date

  • Banca Transilvania (RO): Fixed authorization issues

  • Bank Norwegian (NO): Fixed transaction entry reference mapping

  • Bankhaus Faisst (DE): Bankhaus Faisst changed name to Yapi Kredi

  • Danske Bank (DK): Fixed initiation of scheduled payment

  • Danske Bank (DK): Improve transaction entry reference mapping

  • Eika (NO): Sandnes Sparebank and Hjelmeland Sparebank merge to Rogaland Sparebank

  • Erste Bank (AT): Improved consent creation to fetch detailed account data

  • ING (BE, DE, ES, IT, LU, NL, RO): Removed Bank Mendes Gans from supported ASPSPs

  • KBC (BE), CBC (BE), KBC Brussels (BE): Increased maximum consent validity to 180 days

  • Marginalen Bank (SE): Fixed the BankId App redirect

  • Nordea Corporate (DK, FI, NO, SE): Improved timeout error handling

  • Piraeus Bank (GR): Migrated to use API v3.1, fixed authorization and added PAN mapping for card accounts

  • Postbank (BG): Fixed accounts fetching

  • Société Générale Global Cash (EU): Fixed authorization issues

  • Skandia Bank (SE): Handling account not found error

  • Swedbank (SE): Improved online transaction parsing

The complete list of integration changes can be found here.

Integrations Removed

  • Degussa Bank (DE): Removed as it is merged with Oldenburgische Landesbank (OLB) and API is used.

Previous
Previous

The Future of Loyalty - SAS EuroBonus and the Power of Open Banking

Next
Next

How Enable Banking and Orka Ventures Are Pioneering Open Banking Innovation in Iceland