Enable Banking Changelog | January 2026
As always, if you have any questions, feel free to reach out to us at support.api@enablebanking.com.
Significant Changes and Updates
QWAC Renewal and Related ASPSPs Re-onboarding
At the end of January, we migrated to a renewed QWAC certificate. Thanks to improved automation and our operations dashboard, the renewal process was completed in record time.
Unfortunately, some ASPSPs bind account information consents to specific certificates. As a result, certain account information sessions expired prematurely following the certificate update.
For more details, please refer to our FAQ:
Why does the API return "expired session" when the session has a valid-until date in the future?
Improved Instance Spin-up Time
Some TPPs reported timeouts for applications connected to their dedicated infrastructure during high volumes of parallel requests.
After investigation, we identified that this was caused by a relatively long spin-up time of the computational instances used by dedicated infrastructures. The root cause was linked to suboptimal loading of an open-source library.
By eliminating the need to load this library, we achieved reduced instance spin-up time by nearly 10x, effectively resolving scaling-related timeouts during sudden traffic spikes.
Enhanced PSU Headers Validation and Handling
We have enhanced the validation and handling of PSU headers passed by client applications to the Enable Banking API. These headers indicate the presence of the end user (i.e., that the user is actively interacting with the application when requests are sent).
Validation now occurs at the API gateway level, ensuring that client applications immediately receive an error if:
A required PSU header is missing
A PSU header value is in an invalid format
Further details are available in our FAQs:
What are the PSU headers used for in account details, balances, and transactions endpoints?
Why am I receiving a 422 response with the "PSU header not provided" error?
Markets Specifics Documentation Updates
We’ve updated the Market Specifics documentation to provide clearer guidance on the limitations of major ASPSPs.
For instance, we now explain why American Express does not provide Account Information Services in certain markets, including Finland and Sweden: American Express – Market Limitations
Browse the full documentation here: Open Banking Specifics by Country
GET /payments/{payment-id} Now Returns Payment Type and ASPSP
The Enable Banking API response for payment details now includes:
ASPSP name and country
Payment type
This enhancement was requested by TPPs using our Infrastructure-as-a-Service for payment initiation and simplifies the implementation of application-level business logic.
New Integrations
We’ve expanded AIS/PIS coverage with new integrations:
Banco Desio (IT): AIS integration supporting business accounts, supporting CoRe Banking and Web Remote Banking
Creand (ES): AIS integration
Intesa Sanpaolo (IT): AIS integration supporting business accounts available to Inbiz users
Wamo (EU): AIS integration (business)
Extended Integrations
We’ve extended the following:
Bigbank (EE): Added PIS integration
SEB (SE): Added support for bulk payment initiation (BULK_SEPA, BULK_DOMESTIC, and BULK_DOMESTIC_SE_GIRO payment types)
Fixed and Improved Integrations
We’ve rolled out reliability and performance improvements across multiple ASPSPs, including:
Aachener Bank (DE)
Abanca (ES)
Abanca (PT)
Alisa Bank (DE, DK, PL)
Alisa Pankki (FI)
Argenta (BE)
Banca del Piemonte (IT)
Banco Desio (IT)
Berliner Sparkasse (DE)
CBC (BE)
CIC Banque Privée (FR)
DNB (DE, DK, FI, NO, SE)
Delavska Hranilnica (SI)
Erste Bank (AT)
Erste Bank (HU)
Eurocard (DK, FI, NO, SE)
Intesa Sanpaolo (IT)
Intesa Sanpaolo Bank (SI)
KBC (BE)
KBC Brussels (BE)
Knab (NL)
LKU (LT)
MagNet Bank (HU)
Mediobanca Premier (IT)
Nest Bank (PL)
PBZ (HR)
Paysera (EE, LT, LV)
Piraeus Bank (GR)
Qonto (DE, ES, FR, IT)
S-Pankki (FI)
Slovenská sporiteľňa (SK)
Sudtirol VolksBank (IT)
SumUp (EU)
Swedbank (SE)
Urbo (LT)
Integrations removed
SweepBank (FI): Removed integration due to brand discontinuation in favour of FerratumBank
For a comprehensive list of integration changes, click here
At Enable Banking, we built an internal AI chatbot that lets our team talk to our documentation. Using a Retrieval-Augmented Generation (RAG) setup, we taught AI to fetch the right answers from our docs, fast, accurate, and with real business value. Here’s how we did it, what we learned, and why we believe AI can make internal knowledge tools both smarter and more human.