Enable Banking Changelog | March 2024

Written By Fedor Tyurin

If you have any questions, do not hesitate to get in touch with us at support.api@enablebankig.com.

Major Changes or Updates

Statuses of Bulk Payments

Bulk payments, also known as batch payments, is a way of creating a single payment composed of payments for multiple recipients. The benefit of a bulk payment is that multiple payments can be confirmed with a single Strong Customer Authentication (SCA). 

While bulk payments were supported by Enable Banking already previously, we now introduced the possibility of following statuses for each payment transaction in the bulk payment batch.

Initiating a bulk payment is the same as initiating a single-transaction payment, but providing multiple payment transactions inside the credit_transfer_transaction array. This is supported for payment types BULK_SEPA or BULK_DOMESTIC and you can get the maximum supported number of transactions for each payment type in the max_transactions field available in response to the GET /aspsps request.

If the payment transaction statuses for a bulk payment are immediately available, they will be returned in response to the GET /payments/{paymentId} request inside the payment_details.credit_transfer_transaction[*].transaction_status field. If not, you would need to request status for each payment transaction individually by sending requests to the new endpoint GET /payments/{paymentId}/transactions/{transactionId} .

Debtor Account Details for Executed Payments

This change adds support for capturing debtor account details after payments are confirmed by an end-user.

A possible use case could be, where the debtor needs to be reimbursed for whatever reason. Without debtor account details available upon payment confirmation, it would be only possible to get them from the creditor account statement after payment settlement is complete.

The details are returned in response to the GET /payments/{paymentId} request inside the payment_details.debtor_account field.

Payment Status Webhook

The Payment Status Webhook provides notifications about changes in the status of payments. To use the webhook, the webhook_url field is included in the request body for the POST /payments endpoint. The URL passed into the webhook_url is triggered whenever the status of the payment changes or when it is no longer expected to change.

You’ll find more information on how to use webhooks here.

Documentation updates

We added a detailed explanation on how the Enable Banking API statuses are connected. Check it out at here .

Core aggregation changes

  • Add creditor/debtor IBAN validation for payments

New integrations

  • Abanca (ES): Added an integration for access to business accounts.

Fixed and improved integrations

  • Abanca (ES): Fixed the remittance information mapping.

  • Banque Populaire Bourgogne Franche Comté (FR): No "?" character allowed in the successfulReportUrl.

  • Banque Populaire Bourgogne Franche Comté (FR): Fix the creationDateTime format.

  • Bred Banque Populaire (FR): Fix modifying consent path.

  • Citadele (EE, LT, LV): Enabled support of 180 days max consent validity.

  • Danske Bank (DK, FI, NO, SE): Defined supported reference number schemas for SEPA payments.

  • Danske Bank (DK, FI, IE, NO, PL, SE): Defined supported reference number schemas for SEPA payments.

  • Handelsbanken (FI, NL, SE): Defined supported reference number schemas for SEPA payments.

  • Handelsbanken (FI, NL, SE): Defined supported reference number schemas for SEPA payments.

  • K&H (HU): Fix IBAN regexp.

  • Luminor (EE, LV, LT): Enabled support of 180 days max consent validity.

  • Mediobanca Premier (IT): Fix the redirect_uri.

  • Medicinos Bankas (LT): Enabled support of 180 days max consent validity.

  • MBH Bank (ex-MKB Bank) (HU): Added support for Access.validUntil, improved expired consent validation.

  • N26 (EEA): Enabled support of 180 days max consent validity.

  • Nordea (DK, FI, NO, SE): Defined supported reference number schemas for SEPA payments.

  • Nordea (DK, FI, NO, SE): Added support for DK domestic payments.

  • Nordea Corporate (DK, FI, NO, SE): Fixed authorization flow handling when only one approval is required.

  • Nordea (DK, FI, NO, SE): Initiate multiple signing basket payments in parallel (previously initiated consecutively).

  • Oma Säästöpankki (FI): Defined supported reference number schemas for SEPA payments.

  • OP (FI): Added support for BULK_SEPA payments.

  • OP (FI): Defined supported reference number schemas for SEPA payments.

  • OTP Bank (HU): Fix the validation for refreshing token.

  • Permanent TSB (IE): Added the self-generated entryReference.

  • POP Pankki (FI): Defined supported reference number schemas for SEPA payments.

  • Postepay (IT): Fix account transactions request.

  • Säästöpankki (FI): Defined supported reference number schemas for SEPA payments.

  • SBAB Bank (SE): Removed sign from transaction amounts.

  • SBAB Bank (SE): Improved data mapping for remittance information and internal notes.

  • SEB (EE, LT, LV): Enabled support of 180 days max consent validity.

  • Šiaulių Bankas (LT): Enabled support of 180 days max consent validity.

  • UniCredit Bank Romania (RO): Enabled production environment.

  • UniCredit Bulbank (BG): Enabled production environment.

  • Van Lanschot (BE, NL): Fix the validator for refreshing token.

Fedor Tyurin
Previous

Open Banking Glossary: A Deep Dive into Key Acronyms
Next

Enable Banking Changelog | February 2024