Enable Banking Changelog | May 2026
This month brought a new way to control when payments are submitted for execution, a migration of our UI widgets to a new origin, and the usual round of integration updates across Europe.
Significant Changes and Updates
UI Widgets Origin Changes
Our UI widgets for ASPSP selection and consent now load from https://auth.enablebanking.com/lib/widgets.umd.min.js. The previous location is deprecated and will be removed in January 2027.
This is part of a broader move from tilisy.enablebanking.com to auth.enablebanking.com across our systems. As a result, the origin attribute is now required on enablebanking-consent and enablebanking-auth-flow elements. It should contain the origin ("https://" + the domain) extracted from the URL returned in response to POST /auth.
Deferred Payment Submission for Execution
By default, the Enable Banking API submits a payment for execution at the ASPSP as soon as the PSU completes authorisation. This works for straightforward flows, but leaves no window for applications that need to run additional checks before funds move. For example, an application may want to confirm that the debtor's name returned by the ASPSP after authorisation matches the identity of the authenticated user, a common requirement for fraud prevention and internal compliance.
To address this, we have introduced a deferred payment submission flow. When enabled for a payment, the API holds back the submission step after PSU authorisation and returns control back to your application. This gives you the opportunity to inspect the payment details, including the debtor's name and account number (where the ASPSP provides them), before you decide to proceed.
What's New in the API
defer_submission Parameter on POST /payments
When you create a payment with "defer_submission": true, the payment is authorised by the PSU but not automatically submitted for execution afterwards. Your application remains in control of when (and whether) to finalise it. The default value is false, so existing integrations are completely unaffected.
New POST /payments/{payment_id}/submit Endpoint
Once your application has completed its checks and is ready to proceed, a single call to the new submit endpoint finalises the payment and sends it for execution at the ASPSP. The response contains the updated payment status. If you do not call this endpoint, the payment remains in the authorised-but-unexecuted state indefinitely.
deferred_submission_supported Field in GET /aspsps
Not all ASPSPs support deferred submission yet. Each payment type object returned in the GET /aspsps now includes a deferred_submission_supported field. When this field is true for the payment type you intend to use, you can create payments with "defer_submission": true. Attempting to use deferred submission with a payment type that does not support it will result in a PAYMENT_SUBMISSION_NOT_SUPPORTED error.
Initial Integration Support
The first integration to support deferred submission is OP Bank (FI) for SEPA Credit Transfers. If your application initiates SEPA payments for Finnish users via OP, you can start using the deferred submission flow today.
Looking Ahead
Support for deferred submission will be rolled out to additional ASPSPs and payment types as connectors are updated. We will announce new integrations as they become available. For the current state of each integration, the deferred_submission_supported field in the GET /aspsps reflects the current state of each integration.
Related Documentation
We've added the following documentation to support this launch:
New identification hash
For cases when an ASPSP doesn't explicitly provide a currency for an account, we've introduced a new identification hash based on the account number alone. This makes it easier to distinguish accounts when the currency dimension isn't available. The previous identification hash remains available in the identification_hashes list if your integration depends on it.
Integration Updates
New Integrations
We’ve added support for the following institutions:
Banca di Credito Popolare (IT)
Erste Bank Polska (PL) – Rebranded from Santander Bank Polska
M.M. Warburg & CO (DE)
Marcard, Stein & Co Bankiers (DE)
Millennium BCP (PT) – Additional brand along with Banco Comercial Portugues
MoraBanc (ES) – Rebranded from Banco Europeo de Finanzas
Partners Banka (CZ)
Tyche Bank (IT)
And released new integrations for the following institutions:
Ferratum Bank (BG, CZ, DE, DK, EE, ES, FI, FR, HR, LV, MT, NL, NO, RO, SE) – Migrated to the new API
POP Pankki (FI) – Migrated to the new API
Extended Integrations
The following integrations have been extended:
Bank Norwegian (DE, ES) – Added support for DE and ES markets
Credit Agricole (IT) – Added card accounts support
ICA Banken (SE) – Added support for decoupled authentication
Mediobanca Premier (IT) – Added card account support
Svea Bank (SE) – Added payment initiation (PIS) support
Fixed and Improved Integrations
We’ve rolled out reliability and performance improvements across multiple ASPSPs, including:
Air Bank (CZ)
Aktia (FI)
ASN Bank (NL)
Banca Comercială Română (RO)
Banca di Credito Popolare (IT)
Banca Monte dei Paschi di Siena (IT)
Banca Popolare dell'Alto Adige (IT)
Banca Popolare di Puglia e Basilicata (IT)
Banca Popolare Pugliese (IT)
Banca Sella group (IT)
Banca Territori del Monviso (IT)
Banca Transilvania (RO)
Banca Widiba (IT)
Banco BPM (IT)
Bank of Cyprus (CY)
Bank-Verlag group (DE)
BAWAG (AT)
Belfius (BE)
Boursorama (FR)
BRD (RO)
Bred Banque Populaire (FR)
Citi Handlowy (PL)
comdirect (DE)
Delavska Hranilnica (SI)
Deutsche Bank (DE)
Erste Bank (AT)
Erste Bank (HU)
Gruppo BCC Iccrea (IT)
HPB (HR)
HYPE (IT)
HYPO OOE (AT)
illimity Bank (IT)
ING Bank Śląski (PL)
Intesa Sanpaolo (IT)
KBC (BE)
Knab (NL)
Länsförsäkringar Bank (SE)
Millennium BCP (PT)
NLB (SI)
Nykredit Bank (DK)
OP (FI)
OTP banka (HR)
Raiffeisen (HR, RO, SK)
S-Pankki (FI)
SEB (SE)
Sparda-Bank Nürnberg (DE)
Sparkasse (DE)
SumUp (EU)
Sydbank (DK)
Tatra banka (SK)
UniCredit (BG)
Volksbank Group banks (AT)
VÚB banka (SK)
Wise (EU)
Ålandsbanken (FI, SE)
Integrations Removed
The following integrations have been removed:
BCC Nettuno (IT)
VR Bank HessenLand (DE)
For a comprehensive list of integration changes, clickhere
As always, if you have any questions, feel free to reach out to us at support.api@enablebanking.com.
