Skip to main content

What's New

Read the latest news and information about system updates.

22.10.2026

ACCC status for private FPS payments, OB UK

Danske Bank wishes to inform about availability of ACCC status for private FPS payments, OB UK.

ACCC - Accepted Settlement Completed Creditor Account.

Change is now available in Production.

21.10.2026

MCP Service is now publicly available

Danske Bank is pleased to announce the public launch of its MCP Service, enabling AI agents to work with our Premium APIs using the Model Context Protocol (MCP).

The MCP Service makes it easier to discover and evaluate Danske Bank APIs, explore their capabilities using mock data, and connect your AI agents to Sandbox and Production APIs.

The MCP Server can be explored without a District agreement, certificate or API subscription. To call Sandbox or Production APIs, your organisation must be a Danske Bank customer and complete the standard onboarding requirements for the relevant Premium APIs, including the required agreement, certificate and API subscriptions.

Learn more about the MCP and how to get started on the MCP Service page.

If you have any questions, contact us at premium-api@danskebank.com.

09.10.2026

v4.0.1 Implementation, Production, UK Open Banking and PSD2

Danske Bank wishes to remind about v4.0.1 release on 25nd of November 2026.

Release notes: https://developers.danskebank.com/whats-new#v401-implementation-sandbox-uk-open-banking-and-psd2

Please note that v4.0.1 will replace the current v4.0.0 version.

14.09.2026

MCP Service pilot announcement

Danske Bank is introducing its MCP Service in pilot, enabling AI agents to work with our Premium APIs using the Model Context Protocol (MCP).

The MCP Service gives selected corporate customers the ability to connect their AI agents with Danske Bank's Premium APIs, allowing them to access and view their own financial data within their preferred agentic AI tool.

To express your interest in participating in the pilot, contact us at premium-api@danskebank.com.

11.09.2026

Changes to SE giro payment initiation, additional clarifications in payment initiation

Danske Bank wishes to inform about upcoming changes related to SE giro payment initiation (domestic and domestic scheduled payments with DK.DanskeBank.SE.GiroTransfer local instrument). Changes are expected to come into effect around the end of November 2026.

Changes are primarily related to the new optional UltimateDebtor and UltimateCreditor data structures.

Domestic and domestic scheduled payments – Business customers:

RemittanceInformation/Unstructured - up to 140 characters of free text (recommended length up to 70 characters).

RemittanceInformation/Structured/CreditorReferenceInformation/Reference - numeric OCR references of up to 25 characters.

New optional SupplementaryData parameters – alternative to RemittanceInformation/Structured/CreditorReferenceInformation/Reference for invoice-related information. All values must be provided together:

  • SupplementaryData/CustomerId – up to 15 characters
  • SupplementaryData/InvoiceNumber – up to 35 characters
  • SupplementaryData/InvoiceDate – YYYY-MM-DD format

Note. RemittanceInformation/Structured/CreditorReferenceInformation/Reference, RemittanceInformation/Unstructured and SupplementaryData usage options are mutually exclusive.

New optional UltimateDebtor object - optional capability to provide UltimateDebtor information:

  • UltimateDebtor/Name – up to 35 characters
  • UltimateDebtor/PostalAddress/StreetName – up to 35 characters
  • UltimateDebtor/PostalAddress/TownName – up to 35 characters
  • UltimateDebtor/PostalAddress/PostCode – up to 9 characters
  • UltimateDebtor/PostalAddress/BuildingNumber – up to 16 characters
  • UltimateDebtor/PostalAddress/Country

New optional UltimateCreditor object - optional capability to provide UltimateCreditor information:

  • UltimateCreditor/Name - up to 35 characters.

Domestic and domestic scheduled payments – Private customers:

RemittanceInformation/Unstructured - up to 140 characters of free text (recommended length up to 70 characters).

RemittanceInformation/Structured/CreditorReferenceInformation/Reference - numeric OCR references of up to 25 characters.

Note. RemittanceInformation/Structured/CreditorReferenceInformation/Reference and RemittanceInformation/Unstructured usage options are mutually exclusive and it is mandatory to provide one of them for private giro transfers.

New optional UltimateDebtor object - optional capability to provide UltimateDebtor information:

  • UltimateDebtor/Name – up to 70 characters
  • UltimateDebtor/PostalAddress/AddressLine – two lines up to 70 characters
  • UltimateDebtor/PostalAddress/StreetName – up to 70 characters
  • UltimateDebtor/PostalAddress/BuildingNumber – up to 16 characters
  • UltimateDebtor/PostalAddress/PostCode – up to 16 characters
  • UltimateDebtor/PostalAddress/TownName – up to 35 characters
  • UltimateDebtor/PostalAddress/CountrySubDivision – up to 35 characters
  • UltimateDebtor/PostalAddress/Country
  • UltimateDebtor/PostalAddress/Department – up to 70 characters
  • UltimateDebtor/PostalAddress/SubDepartment – up to 70 characters
  • UltimateDebtor/PostalAddress/BuildingName – up to 35 characters
  • UltimateDebtor/PostalAddress/Floor – up to 70 characters
  • UltimateDebtor/PostalAddress/PostBox – up to 16 characters
  • UltimateDebtor/PostalAddress/Room – up to 70 characters
  • UltimateDebtor/PostalAddress/TownLocationName – up to 35 characters
  • UltimateDebtor/PostalAddress/DistrictName – up to 35 characters

Note. If UltimateDebtor object is used, then it is mandatory to provide the UltimateDebtor/Name.

25.08.2026

v4.0.1 Implementation, Sandbox, UK Open Banking and PSD2

Danske Bank wishes to inform about the v4.0.1 Sandbox release of UK Open Banking and PSD2 APIs.

The release of v4.0.1 to Production is planned for November 2026.

More information about the UK Open Banking v4.0.1 standard can be found here: https://openbankinguk.github.io/read-write-api-site3/v4.0.1/profiles/read-write-data-api-profile.html

Changelog (highlight of main changes):

Updated specification version from 4.0.0 to 4.0.1, all services.

AIS

  • Additional clarification related to Transactions request parameters fromBookingDateTime and toBookingDateTime: timezone and time component usage.
  • Changes in the structure of the Transactions response, additional explanations regarding the contents of TransactionInformation, additional CRYP value in PaymentPurposeCode enum.
  • Changes in structured RemittanceInformation: ReferredDocumentAmount from an integer to OBActiveCurrencyAndAmount_SimpleType, referred-document LineDetails maximum length to 2048 characters.
  • Clarification in Standing Orders regarding NumberOfPayments parameter.

PIS

  • New HTTP 422 response to specifically address idempotency related errors.
  • Changes in the Refund structure, responses.
  • Changes in structured RemittanceInformation: ReferredDocumentAmount from an integer to OBActiveCurrencyAndAmount_SimpleType, referred-document LineDetails maximum length to 2048 characters.
  • Additional CRYP value in Risk/PaymentPurposeCode enum.
  • Change of ErrorCode reference.
  • Clarification of Risk/PaymentContextCode usage (deprecated values).
  • Additional value in Authorisation/AuthorisationType enum.
  • New initial status (PDNG) in file payments.

COF

  • Consent statuses replaced with corresponding ISO codes.

VRP

  • New HTTP 422 response to specifically address idempotency related errors.
  • Adjusted description of the 204VRPConsentsConsentIdDeleted response.
  • Changes in the Refund structure, responses; Refund account Name adjusted to maximum length of 350 characters.
  • Changes in structured RemittanceInformation: ReferredDocumentAmount from an integer to OBActiveCurrencyAndAmount_SimpleType, referred-document LineDetails maximum length to 2048 characters.
  • Additional CRYP value in Risk/PaymentPurposeCode enum.
  • Change of ErrorCode reference.
  • Clarification of Risk/PaymentContextCode usage (deprecated values).

Payments baskets

  • New HTTP 422 response to specifically address idempotency related errors.
  • Changes in the Refund structure, responses.
  • Changes in structured RemittanceInformation: ReferredDocumentAmount from an integer to OBActiveCurrencyAndAmount_SimpleType, referred-document LineDetails maximum length to 2048 characters, additional parameters to align the structure with PIS.
  • Additional CRYP value in Risk/PaymentPurposeCode enum.
  • Change of ErrorCode reference.
  • Clarification of Risk/PaymentContextCode usage (deprecated values).

14.07.2026

ACCC status for private FPS payments, OB UK

Danske Bank wishes to inform about availability of ACCC status for private FPS payments, OB UK.

ACCC - Accepted Settlement Completed Creditor Account.

Change is now available in our Sandbox. The release to Production is planned for middle of October 2026.

03.07.2026

Planned PSD2 / Open Banking / Premium Sandbox Maintenance – July 08 to July 16

Danske Bank wishes to inform you of scheduled maintenance on the PSD2 / Open Banking / Premium Sandbox environment, taking place from 08 July 18.00 CET to 17 July 08.00 CET.

No outages are anticipated during this period. However, intermittent minor degradation may occur, including brief reductions in availability or slower response times.

We appreciate your understanding and cooperation throughout this maintenance window.

25.06.2026

Changes to SE payment initiation, additional clarifications in payment initiation

Danske Bank wishes to inform you about changes related to SE payment initiation (domestic and domestic scheduled payments, standing orders).

Changes are primarily related to the introduction of additional capabilities in RemittanceInformation, the new optional UltimateDebtor and UltimateCreditor data structures, and the length of the CreditorAccount/Name parameter.

Domestic and domestic scheduled payments – Business customers:

RemittanceInformation/Unstructured - up to 140 characters of free text (recommended length up to 70 characters). Can be used together with DK.DanskeBank.SE.AccountTransfer and DK.DanskeBank.SE.Salary local instruments.

RemittanceInformation/Structured/CreditorReferenceInformation/Reference - RF references (numeric references starting with the "RF" prefix) of up to 35 characters. Can be used together with the DK.DanskeBank.SE.AccountTransfer local instrument.

Note. Danske Bank Open Banking will continue to support short texts in the Reference field for DK.DanskeBank.SE.AccountTransfer payments until approximately September/fall 2026, but it is strongly suggested to switch to/use the Unstructured field instead of Reference for text messages to beneficiaries. From fall 2026, only RF references will be supported in the Reference field for DK.DanskeBank.SE.AccountTransfer.

RemittanceInformation/Structured/CreditorReferenceInformation/Reference - following values can be provided: SALA - salary payment; PENS - pension payment. In cases where a value is not provided, the payment will be processed as a salary payment by default. Can be used together with the DK.DanskeBank.SE.Salary local instrument.

SupplementaryData – alternative to RemittanceInformation/Structured/CreditorReferenceInformation/Reference for invoice-related information. All values must be provided together:

  • SupplementaryData/CustomerId – up to 15 characters
  • SupplementaryData/InvoiceNumber – up to 35 characters
  • SupplementaryData/InvoiceDate – YYYY-MM-DD format

Can be used together with DK.DanskeBank.SE.AccountTransfer.

Note. RemittanceInformation/Structured/CreditorReferenceInformation/Reference, RemittanceInformation/Unstructured and SupplementaryData usage options are mutually exclusive, with the exception of DK.DanskeBank.SE.Salary where Reference may be used alongside Unstructured to clarify whether it is a salary or a pension payment.

UltimateDebtor - optional capability to provide UltimateDebtor information:

  • UltimateDebtor/Name – up to 35 characters
  • UltimateDebtor/PostalAddress/StreetName – up to 35 characters
  • UltimateDebtor/PostalAddress/TownName – up to 35 characters
  • UltimateDebtor/PostalAddress/PostCode – up to 9 characters
  • UltimateDebtor/PostalAddress/BuildingNumber – up to 16 characters
  • UltimateDebtor/PostalAddress/Country

Can be used together with DK.DanskeBank.SE.AccountTransfer and DK.DanskeBank.SE.Salary local instruments.

UltimateCreditor - optional capability to provide UltimateCreditor information:

  • UltimateCreditor/Name - up to 70 characters.

Can be used together with the DK.DanskeBank.SE.AccountTransfer local instrument.

Domestic and domestic scheduled payments – Private customers:

RemittanceInformation/Unstructured - up to 140 characters of free text (recommended length up to 70 characters). Can be used together with the DK.DanskeBank.SE.TransferFunds local instrument.

RemittanceInformation/Structured/CreditorReferenceInformation/Reference - RF references (numeric references starting with the "RF" prefix) of up to 35 characters. Can be used together with the DK.DanskeBank.SE.TransferFunds local instrument.

Note. Danske Bank Open Banking will continue to support short texts in the Reference field for DK.DanskeBank.SE.TransferFunds payments until approximately September/fall 2026, but it is strongly suggested to switch to/use the Unstructured field instead of Reference for text messages to beneficiaries. From fall 2026, only RF references will be supported in the Reference field for DK.DanskeBank.SE.TransferFunds.

RemittanceInformation/Structured/CreditorReferenceInformation/Reference and RemittanceInformation/Unstructured usage options are mutually exclusive.

UltimateDebtor - optional capability to provide UltimateDebtor information (domestic payments only, not applicable to domestic scheduled payments):

  • UltimateDebtor/Name – up to 70 characters
  • UltimateDebtor/PostalAddress/AddressLine – two lines up to 70 characters
  • UltimateDebtor/PostalAddress/StreetName – up to 140 characters
  • UltimateDebtor/PostalAddress/BuildingNumber – up to 16 characters
  • UltimateDebtor/PostalAddress/PostCode – up to 16 characters
  • UltimateDebtor/PostalAddress/TownName – up to 35 characters
  • UltimateDebtor/PostalAddress/CountrySubDivision – up to 35 characters
  • UltimateDebtor/PostalAddress/Country
  • UltimateDebtor/PostalAddress/Department – up to 70 characters
  • UltimateDebtor/PostalAddress/SubDepartment – up to 70 characters
  • UltimateDebtor/PostalAddress/BuildingName – up to 35 characters
  • UltimateDebtor/PostalAddress/Floor – up to 70 characters
  • UltimateDebtor/PostalAddress/PostBox – up to 16 characters
  • UltimateDebtor/PostalAddress/Room – up to 70 characters
  • UltimateDebtor/PostalAddress/TownLocationName – up to 35 characters
  • UltimateDebtor/PostalAddress/DistrictName – up to 35 characters

Can be used together with the DK.DanskeBank.SE.TransferFunds local instrument.

Domestic Standing Orders – Business customers:

CreditorAccount/Name - up to 70 characters (was 35).

Domestic Standing Orders – Private customers:

  • DebtorAccount/SchemeName - UK.OBIE.IBAN is not applicable.
  • CreditorAccount/SchemeName - UK.OBIE.IBAN is not applicable.

01.06.2026

Planned PSD2 / Open Banking / Premium Production Maintenance – June 15

Danske Bank wishes to inform you of scheduled maintenance on the PSD2 / Open Banking / Premium Production environment, taking place from 15 June 05.00 CET to 15 June 07.59 CET.

No outages are anticipated during this period. However, intermittent minor degradation may occur, including brief reductions in availability or slower response times.

We appreciate your understanding and cooperation throughout this maintenance window.

29.05.2026

Planned PSD2 / Open Banking / Premium Sandbox Maintenance – June 8

Danske Bank wishes to inform you of scheduled maintenance on the PSD2 / Open Banking / Premium Sandbox environment, taking place from 8 June 06.00 CET to 8 June 10.00 CET.

No outages are anticipated during this period. However, intermittent minor degradation may occur, including brief reductions in availability or slower response times.

We appreciate your understanding and cooperation throughout this maintenance window.

29.05.2026

Planned PSD2 Production Maintenance – June 8

Danske Bank wishes to inform you of planned maintenance on the PSD2 External API license verification provider Production environment, taking place outside of normal business hours for 22:00 UTC on Monday 8th June 2026.

No outages are anticipated during this period. However, intermittent minor degradation may occur, including brief reductions in availability or slower response times.

We appreciate your understanding and cooperation throughout this maintenance window.

16.04.2026

Planned PSD2 / Open Banking / Premium Production and Sandbox Maintenance – April 17-19

Danske Bank wishes to inform you of scheduled maintenance on the PSD2 / Open Banking / Premium Production and Sandbox environment, taking place from 17 April 18.00 CET to 19 April 18.00 CET.

No outages are anticipated during this period. However, intermittent minor degradation may occur, including brief reductions in availability or slower response times.

We appreciate your understanding and cooperation throughout this maintenance window.

13.04.2026

Increased number of payments in Payments Baskets, PSD2

Danske Bank wishes to inform about the adjustment to the number of payments accepted via Payments Baskets. The previous limit of 15 payments has been increased to 100 payments.

This change is already available in both Sandbox and Production.

13.04.2026

Adjustments and clarifications in v4.0 documentation, UK Open Banking and PSD2

Danske Bank wishes to inform about various adjustments in v4.0 documentation.

Changelog (highlight of main changes):

  • Removal of v3.1 documentation, as v3.1 services were decommissioned in March 2026 (UK Open Banking and PSD2).
  • Removal of instruments and rules related to Norwegian private customers (PSD2).
  • Clarification of rules regarding CreditorAgent usage in international and international scheduled payments (PSD2).
  • Various adjustments and fixes in API definition descriptions.

18.03.2026

Planned PSD2 / Open Banking Production Maintenance – March 18-26

Danske Bank wishes to inform you of scheduled maintenance on the PSD2 / Open Banking Production environment, taking place from March 18 to March 26.

No outages are anticipated during this period. However, intermittent minor degradation may occur, including brief reductions in availability or slower response times.

We appreciate your understanding and cooperation throughout this maintenance window.

23.02.2026

Planned Open Banking Sandbox Maintenance – March 2-8

Danske Bank wishes to inform you of scheduled maintenance on the Open Banking Sandbox environment, taking place from March 2 to March 8.

No outages are anticipated during this period. However, intermittent minor degradation may occur, including brief reductions in availability or slower response times.

We appreciate your understanding and cooperation throughout this maintenance window.

13.02.2026

Planned Open Banking Sandbox Maintenance – February 17 – 24

Danske Bank wishes to inform you of scheduled maintenance on the Open Banking Sandbox environment, taking place from February 17 to February 24.

No outages are anticipated during this period. However, intermittent minor degradation may occur, including brief reductions in availability or slower response times.

We appreciate your understanding and cooperation throughout this maintenance window.

02.02.2026

Upcoming Changes for OBUK Dynamic Client Registration

Danske Bank wishes to inform you about upcoming change to the Dynamic Client Registration (DCR) process for the OBUK market. This change will take effect from 12 May 2026.

The iss field in OBClientRegistrationRequest must be the software_id as Danske Bank only support SSAs issued by the OB Directory. Above fix is to ensure compliance with OBUK DCR requirements as per OBUK Dynamic Client Registration (DCR).

15.01.2026

Change of 'channel' for certain SME customers

Danske Bank wishes to remind about upcoming and ongoing changes, primarily for SME customers. Those business customers in DK, SE and NO with Danske Bank digital channel 'Business eBanking' will batch-wise during 2025 until Q3 2026 be migrated to new digital channel District. More information about this migration has, and will be, communicated with affected customers.

Same access to accounts and mandates remains for PSU through new digital channel after migration.

The previous digital channel will for customers remain for around 6 months after migration before being terminated, starting April 2025. Until termination both channels will work from TPP perspective. For account consent renewals requiring SCA, the new channel should be used when available.

This migration implies a change in OAuth2 authorization requests for TPPs, changing 'channel' from private to business. Read more on Danske Bank Developers Portal – Open Id Configuration.

As this change happens in batches, the exact timing is not known, hence the TPP needs to provide means allowing PSU to select channel themselves.

09.01.2026

V3.1.11 decommission, Production, UK Open Banking and PSD2

Danske Bank wishes to remind that v3.1.11 Open Banking APIS are scheduled for decommission from 21st of February 2026 and Open Banking consumers are strongly encouraged to switch to v4.0.0 APIS till this date.

08.12.2025

New API Developer Portal is live

Danske Bank is pleased to announce that the move to our refreshed and improved developer portal design is complete.

The updated portal introduces a modernised design while maintaining all the features and functionality you rely on. We hope you enjoy the new experience and look forward to continuing to support your needs through the improved platform.

26.11.2025

QTSP Certificate Compliance

Danske Bank wishes to inform you about an important compliance requirement regarding PSD2 API access.

Recently, one Certificate Authority (CA) previously listed as a Qualified Trust Service Provider (QTSP) has been removed from the EU Trusted List. As a result certificates issued by this CA are no longer considered qualified and requests are being rejected.

Action Required:
If your current certificate was issued by a CA that is no longer a QTSP, you must replace it with a certificate issued by a currently listed QTSP to maintain uninterrupted access to our PSD2 APIs.

For more information check the EU Trusted List for current QTSPs.

10.11.2025

Upcoming changes to Developer Portal

Danske Bank wishes to update about earlier communication regarding an upcoming design change of our developer portal (developers.danskebank.com) in December. While the appearance will be refreshed, all the features and functionality you rely on will remain the same. This change is currently planned to be introduced on 8th December.

To ensure a smooth transition, we now have the shadow production (beta version) available via beta-developers.danskebank.com. We value your feedback and encourage you to share your thoughts on the new design.

13.10.2025

Changes to Developer Portal

Danske Bank would like to inform you that our developer portal developers.danskebank.com would be undergoing a design change in December. While the appearance will be refreshed, all the features and functionality you rely on will remain the same. This change is currently planned to be introduced on 8th December.

To ensure a smooth transition, we would also plan a shadow production period from 7th November. During this period, the new design will be available in parallel with the current one. This would allow you to explore the new design while still having access to the existing portal. We value your feedback and encourage you to share your thoughts on the new design during the shadow production period.

07.10.2025

Upcoming changes to FI and IE payment initiation, additional clarifications in payment initiation

Danske Bank wishes to inform you about changes related to SEPA Instant payments, scheduled for release on 8 October 2025.

New LocalInstruments are being introduced for private and business customers in FI and IE markets, covering domestic and domestic scheduled payments.

Additionally, there are changes to the processing of international and international scheduled payments in FI and IE.

For more details on LocalInstruments, visit: Payment Initiation Details

New LocalInstruments:

  • DK.DanskeBank.FI.TransferFunds.INST – SEPA Instant for FI private customers
  • DK.DanskeBank.FI.AccountTransfer.INST – SEPA Instant for FI business customers
  • DK.DanskeBank.IE.AccountTransfer.INST – SEPA Instant for IE business customers

International payments (FI and IE):

  • Payments in EUR with InstructionPriority set to "Urgent" will be routed to SEPA Instant.

Additional payment status for SEPA Instant payments (domestic and international):

  • ACCC (v4.0); AcceptedCreditSettlementCompleted (v3.1)

Additional adjustments and clarifications

Business domestic and domestic scheduled payments (FI and IE), CreditorAccount/Name length limitations:

FI

  • DK.DanskeBank.FI.AccountTransfer.INST – max 35 characters
  • DK.DanskeBank.FI.AccountTransfer – max 35 characters
  • DK.DanskeBank.FI.AccountTransfer.URGP – max 35 characters
  • DK.DanskeBank.FI.Salary – max 70 characters

IE

  • DK.DanskeBank.IE.AccountTransfer.INST – max 35 characters
  • DK.DanskeBank.IE.AccountTransfer – max 35 characters
  • DK.DanskeBank.IE.AccountTransfer.URGP – max 18 characters

Business domestic and domestic scheduled payments (FI and IE), InstructionIdentification and SupplementaryData/DebtorEntryText:

  • Maximum length of InstructionIdentification: 20 characters
  • If SupplementaryData/DebtorEntryText is provided, it will override the InstructionIdentification value.

Business domestic and domestic scheduled payments (FI), RemittanceInformation:

At least one of the following must be provided:

  • RemittanceInformation/Unstructured

Or

  • RemittanceInformation/Reference (v3.1) or RemittanceInformation/Structured/CreditorReferenceInformation/Reference (v4.0)

Or

  • A combination of SupplementaryData/CustomerId, SupplementaryData/InvoiceNumber, and SupplementaryData/InvoiceDate

CreditorAccount/SchemeName in domestic/domestic scheduled and international/international scheduled payments:

  • IBAN is preferred.
  • If UK.OBIE.SortCodeAccountNumber or DK.DanskeBank.AccountNumber is used in international/international scheduled payments:
  • CreditorAgent/SchemeName (only BICFI for SEPA payments) and CreditorAgent/Identification

Or

  • CreditorAgent/PostalAddress/Country are required.

Business international and international scheduled payments (FI), capital payments:

  • The Purpose value in v4.0 is relocated to Risk/CategoryPurposeCode.

Domestic standing orders (all markets, business and private):

  • SupplementaryData/UnstructuredReference is not supported and will be deprecated from v4.0. Instead, RemittanceInformation/Unstructured should be used.
  • Clarified RemittanceInformation/Unstructured length limitations.

The Payment Initiation Details page and API definitions (Sandbox and PROD, v3.1 and v4.0) have been updated accordingly on the Developers Portal.

01.10.2025

Updated mTLS certificate for PSD2 API access

Danske Bank would like to inform you that a new certificate and certificate chain from a new Certificate Authority (GlobalSign) has been implemented for psd2-api.danskebank.com as per September 29th 2025. Please verify that your systems trust the updated certificate chain to ensure continued secure mTLS connectivity.

12.09.2025

Upcoming changes to Authorization request validation

Danske Bank wishes to update about implementation date for changes related to Authorization request validation.

Please make a note of the revised date as 8 October 2025.

Danske Bank also wishes to remind about this upcoming change related to the consent Authorization request.

The whitespaces in the redirect URL must be encoded as "%20" instead of "+".

Please ensure compliance with this requirement, as support for redirect URL containing "+" will be discontinued.

As a consequence of this change, the parameters returned in the redirect back to the TPPs will be provided in the URI's fragment (#) part instead of the query part (?).

The changes are breaking if the Authorization request is encoded incorrectly.

01.09.2025

Update on the new version of Norwegian BankID in PSD2 PSU authorization

Danske Bank wishes to update about new version of Norwegian BankID, which was implemented across the sector to transition from the BankID server platform to the OpenID Connect (OIDC) platform. The new version was made available as an ID method for customers in the PSD2 consent authorization flows from 25th of August 2025.

Danske Bank wishes to update that from 01st October, the new version will fully replace the current Bank ID solution.

In context of Open Banking, it is advised to reauthorize consents (authorized with Old Bank Id) using the new version, since from 01st October refresh tokens won't be available for consents authorized with old Bank Id.

27.08.2025

Temporary Unavailability of Onboarding API

Danske Bank wishes to inform that Onboarding API will be temporary unavailable for UK Open Banking and PSD2 during the following periods:

  • Sandbox: 6.30pm-7.30pm CET on 9 September 2025
  • Production: 9.30pm-10.30pm CET on 10 September 2025

26.08.2025

Update on the new version of Swedish BankID in PSD2 PSU authorization

Danske Bank wishes to update about new version of Swedish BankID, which contains QR code and made available as an ID method for customers in the PSD2 consent authorization flows from 10th of July 2025.

Danske Bank wishes to update that from 01st October, the QR code based SE Bank ID will fully replace the current Bank ID solution.

In context of Open Banking it is advised to reauthorize consents (authorized with Old Bank Id) using new QR Code based ID method, since from 01st October refresh tokens won't be available for consents authorized with old Bank Id.

21.08.2025

v4.0.0 Implementation, Production, UK Open Banking and PSD2

Danske Bank wishes to inform about v4.0.0 Production release on 21st of August 2025, UK Open Banking and PSD2. The new version is now available in our Production.

The release of v4.0.0 to Production is planned for 21st of August 2025.

Since its a major version release, v4.0 won't be backwards compatible with v3.1.

More information about OB UK v4.0 standard can be found here: https://openbankinguk.github.io/read-write-api-site3/v4.0/profiles/read-write-data-api-profile.html

Changelog (highlight of main changes):

  • Enum values aligned to ISO 20022.
  • Simplified error object; error codes now in ISO 20022 code value format; new StatusReason object.
  • Refactored RemittanceInformation, Domestic Standing Order / Direct Debit frequency, PostalAddress and Risk related objects.
  • Consent and payment statuses aligned to ISO 20022; changes in state machines of different payment types.
  • Various adjustments and fixes in API definition descriptions.

VRP v3.1.11 endpoints will not be supported in the Production from 21st of August 2025; v4.0 Production APIs should be used instead.

VRP consents created via v3.1.11 API can be accessed and used via v4.0 VRP endpoints.

Please, note that v3.1.11 APIS will be deprecated after 6 months (approximately after 21st of February 2026) and consider switching to consumption of v4.0 API during this period.

14.08.2025

New version of Norwegian BankID in PSD2 PSU authorization

Please note that new version of Norwegian BankID, would be available as an ID method for customers in the PSD2 consent authorization flows from 25th of August 2025. The old Norwegian BankID will be removed at the same time.

Above change applies to PSU authorization only and should not require any additional development from TPPs.

10.07.2025

Upcoming changes to redirect URL of Authorization request

Danske Bank wishes to update about implementation date for changes related to redirect URL of Authorization request:

Please make a note of the revised date as 12 August 2025.

Danske Bank also wishes to remind about this upcoming changes related to redirect URL of Authorization request where, whitespaces in the redirect URL must be encoded as "%20" instead of "+".

Please ensure compliance with this requirement, as support for redirect URL containing "+" will be discontinued.

As part of the above change, the query parameter 'code' containing authorization code will only be sent to redirect URI's fragment part instead of as part of query parameter.

01.07.2025

New version of Swedish BankID in PSD2 PSU authorization

Please note that new version of Swedish BankID, which contains QR code, would be available as an ID method for customers in the PSD2 consent authorization flows from 10th of July 2025.

Above change applies to PSU authorization only and should not require any additional development from TPPs.

21.05.2025

v4.0.0 Implementation, Sandbox, UK Open Banking and PSD2

Danske Bank wishes to inform about v4.0.0 Sandbox release on 21st of May 2025, UK Open Banking and PSD2. The new version is now available in our Sandbox. The release of v4.0.0 to Production is planned for 21st of August 2025.

Since its a major version release, v4.0 won't be backwards compatible with v3.1. More information about OB UK v4.0 standard can be found here: https://openbankinguk.github.io/read-write-api-site3/v4.0/profiles/read-write-data-api-profile.html.

Changelog (highlight of main changes):

  • Enum values aligned to ISO 20022.
  • Simplified error object; error codes now in ISO 20022 code value format; new StatusReason object.
  • Refactored RemittanceInformation, Domestic Standing Order / Direct Debit frequency, PostalAddress and Risk related objects.
  • Consent and payment statuses aligned to ISO 20022; changes in state machines of different payment types.
  • Various adjustments and fixes in API definition descriptions.

VRP v3.1.11 will not be supported in the Sandbox from 21st of May 2025; v4.0 Sandbox APIs should be used instead.

22.04.2025

Changes to DK Payment Initiation

Danske Bank has implemented changes to DK payment initiation as of Easter 2025, introducing updates related to instant payments.

DK instant payments can be used:

  • For private customers via the local instrument DK.DanskeBank.DK.TransferFunds.URGP
  • For business customers via the local instrument DK.DanskeBank.DK.AccountTransfer.URGP

For more details, please refer to the API Products documentation.

24.03.2025

Upcoming changes to DK payment initiation

Danske Bank wishes to remind about the upcoming changes in Easter 2025 related to DK instant payments. New LocalInstrument will be introduced for private customers and there will be some changes for business customers using DK instant payments.

The upcoming updates are summarised below:

For business customers:

There will be a change of properties for the DK.DanskeBank.DK.AccountTransfer.URGP LocalInstrument:

  • The Reference and Unstructured fields under RemittanceInformation will become mutually exclusive meaning it will only be possible to fill either the Unstructured field with up to 140 characters or either the Reference field with up to 25 characters starting with 'RF'
  • DK.DanskeBank.DK.AccountTransfer.URGP will not be applicable to Domestic Scheduled Payments
  • For account numbers in the SchemeName field under CreditorAccount IBAN or DK.DanskeBank.AccountNumber shall be used

For private customers:

  • DK.DanskeBank.DK.TransferFunds will only provide same day and next banking day payments
  • DK.DanskeBank.DK.TransferFunds.URGP will be introduced as a new LocalInstrument for private customers for instant payments
  • For DK.DanskeBank.DK.TransferFunds.URGP the Reference and Unstructured fields under RemittanceInformation will be mutually exclusive meaning it will only be possible to fill either the Unstructured field with up to 140 characters or the Reference field with up to 25 characters starting with 'RF'
  • DK.DanskeBank.DK.TransferFunds.URGP will not be applicable to Domestic Scheduled Payments
  • For account numbers in the SchemeName field under CreditorAccount IBAN or DK.DanskeBank.AccountNumber shallbe used

Payment Initiation Details page and Sandbox swaggers are updated accordingly on Developers Portal.

20.02.2025

Upcoming Changes for Dynamic Client Registration

Danske Bank wishes to inform you about upcoming changes to the dynamic client registration process for the PSD2 market. These changes will take effect from 21 May 2025 and will ensure compliance with all existing DCR requirements and improved DCR request validation. References and API Product definitions are updated on Developers Portal.

06.02.2025

Documentation update – UK Open Banking / PSD2

Danske Bank wishes to inform about the update of API specifications to OpenAPI v3.0.1.

References and API Product definitions are updated on Developers Portal.

20.01.2025

Upcoming changes to DK payment initiation

Danske Bank wishes to inform about the upcoming changes in Easter 2025 related to DK instant payments. New LocalInstrument will be introduced for private customers and there will be some changes for business customers using DK instant payments.

The upcoming updates are summarised below:

For business customers:

There will be a change of properties for the DK.DanskeBank.DK.AccountTransfer.URGP LocalInstrument:

  • The Reference and Unstructured fields under RemittanceInformation will become mutually exclusive meaning it will only be possible to fill either the Unstructured field with up to 140 characters or either the Reference field with up to 25 characters starting with 'RF'
  • For account numbers in the SchemeName field under CreditorAccount IBAN or DK.DanskeBank.AccountNumber shall be used

For private customers:

  • DK.DanskeBank.DK.TransferFunds will only provide same day and next banking day payments
  • DK.DanskeBank.DK.TransferFunds.URGP will be introduced as a new LocalInstrument for private customers for instant payments
  • For DK.DanskeBank.DK.TransferFunds.URGP the Reference and Unstructured fields under RemittanceInformation will be mutually exclusive meaning it will only be possible to fill either the Unstructured field with up to 140 characters or the Reference field with up to 25 characters starting with 'RF'
  • DK.DanskeBank.DK.TransferFunds.URGP will not be applicable to Domestic Scheduled Payments
  • When using DK.DanskeBank.DK.TransferFunds.URGP, only IBAN account numbers shall be used in the SchemeName field under the CreditorAccount

Payment Initiation Details page and Sandbox swaggers are updated accordingly on Developers Portal.

04.12.2024

Account product usage changes for PSD2 and UK Open Banking market

Danske Bank wishes to inform about certain account product usage changes for PSD2 and UK Open Banking market.

The following changes will apply from 2025-03-20:

  • Account product 'Top account' will be made available in Account and Transaction API
  • Account products 'Mirror Ledger' and 'Mirror Ledger – Currency', will no longer be available in Account and Transaction API, but in Payment Initiation API and Confirmation of Funds API

20.11.2024

NO, personal customers

As of 18th of November 2024, Danske Bank Norway is a dedicated bank for business, corporate and institutional customers. Danske Bank and Nordea have successfully transferred the personal customers business in Norway from Danske Bank to Nordea.

More information: https://danskebank.com/news-and-insights/news-archive/press-releases/2024/pr18112024

23.09.2024

Changes to Danske Bank's corporate visual identity

Danske Bank is making updates to its corporate visual identity to create a more user-friendly experience for its customers in an increasingly digital world.

As part of a renewal that will be rolled out gradually over the next three years, Danske Bank is upgrading its logo, font, colour palette and imagery in ways that enhance readability, user-friendliness and legibility of text and fonts digitally.

The new logo is already available in the "Get started" page and it is advised to start updating the logo on the TPPs side as well.

For more information please visit the Danske Bank homepage.

16.08.2024

Change of 'channel' for certain SME customers

Danske Bank wishes to inform about upcoming change, primarily for SME customers. Those business customers in DK, SE and NO with Danske Bank digital channel 'Business eBanking' will stepwise during Q4 2024 until Q2 2025 be migrated to new digital channel District. More information about this migration will be available on Danske Bank homepage and communicated with affected customers.

Same access to accounts and mandates remain for PSU through new digital channel after migration.

The previous digital channel will for customer remain for around 6 months after migration before being terminated. During this time both channels will work from TPP perspective.

This migration implies a change in OAuth2 authorization requests for TPPs, changing 'channel' from private to business. Read more on Danske Bank Open Banking Developer Portal.

As this change happens in batches, the exact timing is not known, hence the TPP needs to provide means allowing PSU to select channel themselves.

07.08.2024

New ID method in PSD2 PSU authorization - DK, business customers

Please note that new ID method - MitID is available for DK business customers in PSD2 consent authorization flows from 7th of August.

Above change applies to PSU authorization only and should not require any additional development from TPPs.

09.05.2024

Payments Baskets in Sandbox

Danske Bank wishes to inform about availability of Payments Baskets functionality/APIs in Sandbox from May 8th 2024.

Note, that even though Payments Baskets product is available for PSD2 only, in order to use it in Sandbox GB country / scope should be used.

22.04.2024

Account product usage changes for PSD2 market - UPDATE

Danske Bank wishes to inform about certain account product usage changes for PSD2 market.

The announcement as per 2023-12-20 and taken into effect 2024-04-05 has been rolled back.

The following changes will apply from 2024-04-22:

  • Account product 'Top account' will no longer be available as Payment Account through APIs
  • Account products 'Mirror Ledger' and 'Mirror Ledger – Currency', will be available as Payment Account through APIs

04.04.2024

Upcoming changes to the authorization flow

Danske Bank is updating the Open Banking and PSD2 consent authorization flow to be compliant with the Financial Grade API (FAPI) Security Profile 1.0 Advanced and FAPI Conformance Suite.

These changes were made available in our Sandbox on January 10th, 2024 and are about to take effect in production (OB UK and PSD2) on April 10, 2024.

Financial Grade API (FAPI) Security Profile 1.0 Advanced: https://openid.net/specs/openid-financial-api-part-2-1_0.html

Main changes are:

  • fapi1-advanced-final-ensure-request-object-with-exp-over-60-fails Return error if authorization request object 'exp' claim is more than 60 minutes in the future
  • fapi1-advanced-final-ensure-request-object-without-nbf-fails Return error if authorization request object is missing 'nbf' claim
  • fapi1-advanced-final-ensure-request-object-with-nbf-over-60-fails Return error if authorization request object 'nbf' claim is more than 60 minutes in the past
  • Removed nonce parameter from the authorization response redirect URL back to TPP

06.03.2024

Change in Payments Baskets APIs (PSD2)

Danske Bank wishes to inform about the upcoming change in Payments Baskets APIs for PSD2.

Change: Scope of DebtorAccount.Name parameter will be changed to Optional in both consent and initiation requests and responses.

Preliminary change release dates are: 14th of March 2024 (Sandbox) and 20th of March 2024 (Production).

05.03.2024

Payment Initiation and payment status

This is to clarify the upcoming change as per 2024-03-06, related to payment status upon payment initiation.

As part of our continuous work to improve resilience and accuracy of Open Banking systems, payment initiations of Domestic and International payments may, under certain circumstances, stay in AcceptedSettlementInProcess status longer than before – especially during non-office hours.

Always use the GET payment endpoints (GET /domestic-payments, GET /international-payments) for the latest status.

Please refer to Open Banking specification, Payment Status - Open Banking Standards, bullet C to E, where any of AcceptedSettlementCompleted or Rejcted is the final status returned by Danske Bank.

This applies for both Business and Private channel, and for both PSD2 and UK

  • Upon payment initiation, the payment status in response to /POST will be AcceptedSettlementInProcess and in some cases Pending for a short amount of time. These are waiting statuses, to indicate ongoing payment initiation validations
  • After a successful payment initiation validation, the payment processing will return either Rejected or AcceptedSettlementCompleted status

27.02.2024

Changes to error message structure for 403 Forbidden errors

Danske Bank wishes to inform about upcoming corrections of error message structure for status 403 Forbidden.

Planned release date: 2024-03-06

Changes: For error message status 403 Forbidden, the Error message location will change. New Message element will be "Forbidden". In Errors block, predefined UK OBIE ErrorCode and detailed Message will be presented.

The change applies for both PSD2 and UK Open Banking.

22.02.2024

Restrictions in Payment Initiation, FI

Danske Bank wishes to inform about certain product usage restrictions in Payment initiation, FI market.

From 6th of March 2024 usage of Kaupankäynti Online tili in Payment initiation will be blocked since this product is not considered to be a payment account.

13.02.2024

Payment Initiation, status AcceptedSettlementInProcess

As part of our continuous work to improve resilience and accuracy of Open Banking systems, payment initiations of Domestic and International payments may, under certain circumstances, stay in AcceptedSettlementInProcess status longer than before – especially during non-office hours.

Use the GET payment endpoints (GET /domestic-payments, GET /international-payments) for the latest status.

This applies for both Business and Private channel, and for both PSD2 and UK OB

20.12.2023

Account product usage changes for PSD2 market

Danske Bank wishes to inform about certain account product usage changes for PSD2 market.

The following changes will apply from 2024-04-05:

  • Account product 'Top account' will be available as Payment Account through APIs
  • Account products 'Mirror Ledger' and 'Mirror Ledger – Currency', will no longer be available as Payment Account through APIs

30.11.2023

Upcoming changes to the authorization flow

Danske Bank will be updating the Open Banking and PSD2 consent authorization flow to be compliant with the Financial Grade API (FAPI) Security Profile 1.0 Advanced and FAPI Conformance Suite.

These changes will take effect in our Sandbox on January 10th, 2024 and in production (OB UK and PSD2) on April 10, 2024.

Financial Grade API (FAPI) Security Profile 1.0 Advanced: https://openid.net/specs/openid-financial-api-part-2-1_0.html

Main changes are:

  • fapi1-advanced-final-ensure-request-object-with-exp-over-60-fails Return error if authorization request object 'exp' claim is more than 60 minutes in the future
  • fapi1-advanced-final-ensure-request-object-without-nbf-fails Return error if authorization request object is missing 'nbf' claim
  • fapi1-advanced-final-ensure-request-object-with-nbf-over-60-fails Return error if authorization request object 'nbf' claim is more than 60 minutes in the past
  • Removed nonce parameter from the authorization response redirect URL back to TPP

23.11.2023

v3.1.11 Implementation

Danske Bank wishes to inform that v3.1.11 release is now available in Production as of 23rd of November 2023.

Changelog:

  • Updated version numbers
  • Domestic VRP request, Data section, new parameter: "VRPType"
  • VRP ControlParameters validation, new error: UK.OBIE.Rules.FailsControlParameters

18.10.2023

Payments Baskets release for PSD2

Danske Bank wishes to inform about the release of Payments Baskets for PSD2 on October 18th 2023. Functionality is now available in Production.

Documentation, References and swaggers are updated on Developers Portal.

13.10.2023

Payments Baskets release for PSD2

Danske Bank wishes to inform about the release of Payments Baskets for PSD2 as of October 18th 2023.

Payments Baskets API - initiation of multiple (up to 15) payments with one signature / approval. Supports domestic / domestic scheduled payments, private and corporate accounts.

Documentation, References and swaggers are about to be updated on the release day.

12.10.2023

FAQ page update

Danske Bank wishes to inform about the update of the page for frequently asked questions on October 12th 2023.

The renewed page contains new questions which have been categorised for easier navigation.

05.09.2023

v3.1.11 Implementation

Danske Banks wishes to inform about v3.1.11 release on 5th of September 2023. The new version is now available in our Sandbox.

Changelog:

  • Updated version numbers
  • Domestic VRP request, Data section, new parameter: "VRPType"
  • VRP ControlParameters validation, new error: UK.OBIE.Rules.FailsControlParameters

24.07.2023

PSD2, change of 90-day SCA exemption for account access

Danske Bank wishes to inform about the release of change related to PSD2 90-day account access SCA exemption (Article 10 of Commission Delegated Regulation (EU) 2018/389).

Above mentioned 90-day period is about to be extended to 180 days (Commission Delegated Regulation (EU) 2022/2360).

Change release date is 25th of July 2023.

No actions from TPPs are required. After 25th of July new AIS consents will have 180 days SCA exemption. AIS consents authorized before 25th of July will retain 90 days SCA exemption which will be extended to 180 days on next consent re-authorization.

04.07.2023

Variable Recurring Payments/VRP release for UK OB

Danske Bank wishes to inform about the release of Variable Recurring Payments/VRP for UK OB as of July 5th 2023.

Documentation, References and swaggers are updated on Developers Portal.

28.06.2023

Support for Norwegian Straks payments PSD2

Danske Bank wishes to inform about the release of new LocalInstrument DK.DanskeBank.NO.TransferFunds.URGP which supports instant Norwegian payments for Private customers to beneficiaries within banks on Straks clearing infrastructure. Release on June 28th, and for PSD2 flow only.

References and swaggers are updated on Developers Portal.

25.05.2023

PSD2, change of 90-day SCA exemption for account access

Danske Bank wishes to inform about upcoming change related to PSD2 90-day account access SCA exemption (Article 10 of Commission Delegated Regulation (EU) 2018/389).

Above mentioned 90-day period is about to be extended to 180 days (Commission Delegated Regulation (EU) 2022/2360).

Preliminary change release date is 25th of July 2023.

11.04.2023

Payment Initiation, status Pending

Please note that due to upcoming changes in our systems, payment initiations of Domestic and International payments may stay in Pending status longer than before. Use the GET payment endpoints (GET /domestic-payments, GET /international-payments) for the latest status.

This applies for both Business and Private channel, and for both PSD2 and UK OB.

11.04.2023

Restrictions in Payment Initiation, FI

Danske Bank wishes to inform about certain payment product usage restrictions in Payment initiation, FI market.

From 12th of April 2023 usage of MasterCard and MasterCard K-Plussa in Payment initiation will be blocked since those products are not considered to be payment accounts.

26.01.2023

DK Giro for Private and Business customers, SE Giro for Private customers (PSD2) - temporary blocking removed

Danske Banks wishes to inform about release of full support for DK and SE Giro payment initiation for PSD2 on 25th of January 2023.

Temporary blocking for future dated (Domestic Scheduled Payments) DK Giro payments type 01 and 73 , and SE Giro payments (Bankgiro/Plusgiro) for Private customers is now removed. (Please refer to release as of 15th of December 2022).

15.12.2022

DK Giro for Private and Business customers, SE Giro for Private customers (PSD2)

Danske Banks wishes to inform about release of support for DK and SE Giro payment initiation for PSD2 on 15th of December 2022.

  • DK Giro payment types 01, 04, 15, 71, 73 and 75 are now supported for both Private and Business customers. Descriptions and linked PDF documents are updated with relevant information.
  • SE Bankgiro and Plusgiro payment initiations are now supported for Private customers (support for Business customers since 25.05.2021). Descriptions and linked PDF documents are updated with relevant information.

Note: There is currently a temporary validation blocking future dated (Domestic Scheduled Payments) DK Giro payments type 01 and 73 , and SE Giro payments (Bankgiro/Plusgiro) for Private customers.

16.09.2022

v3.1.10 Implementation

Danske Bank wishes to remind about v3.1.10 release on 22nd of September 2022.

Important note. From 22nd of September there will be no 90 days re-authentication requirement for Open Banking UK AISP consents. In order to ensure a smooth operation of consents created before 22nd of September, we recommend TPPs to GET any resource (balances, transactions, party, etc.) related to OB UK AISP consents authorized or re-authorized after 22nd of June 2022. This should be done shortly after the release (22nd of September 08:00 CET).

16.09.2022

Restrictions to customers of Danske Bank A/S (London Branch)

Danske Bank wishes to inform that from 22nd of September customers of Danske Bank A/S (London Branch) won't be restricted to PSD2 services only and will be allowed to use Open Banking services as well.

22.08.2022

v3.1.10 Implementation

Danske Banks wishes to inform about v3.1.10 release on 22nd of September 2022. The new version is now available in our Sandbox.

Changelog:

  • Updated version numbers
  • Risk section, PaymentContextCode
  • New enumerations and deprecated values
  • Risk section, four new optional Fields; ContractPresentInidicator, BeneficiaryPrepopulatedIndicator, PaymentPurposeCode, BeneficiaryAccountType
  • Risk section, DeliveryAddress (OBRisk1DeliveryAddress) changes class from PostalAddress18 To PostalAddress2Line
  • Events, new event type code UK.OBIE.Consent-Access-Revoked (an event that indicates a consent has its underlying access revoked. The consent itself remains in authorised state). Event type code UK.OBIE.Consent-Authorization-Revoked is left for backward compatibility.

Note. On 22nd of September there will be no 90 days re-authentication requirement for Open Banking UK AISP consents. The TPPs will not need to re-authorize this kind of consents as long as TPPs have a valid access or refresh token. No additional actions such as re-confirmation from TPPs will be required - user consent re-confirmation is now considered TPP responsibility as described in https://www.fca.org.uk/firms/strong-customer-authentication.

14.06.2022

Update in PSU authentication errors

Danske Bank wishes to inform that additional error „The consent could not be authorized, incorrect authentication channel requested: private" was included into PSU authentication errors. Updated error list can be found in the Consent Journey Error Codes document.

07.06.2022

API rate limits implemented

Danske Bank wishes to inform about implementation of the hard limit of 25 requests per second per one OB UK/PSD2 AIS API per one third party application. Limits will be enabled from 08/06/2022.

07.04.2022

Changes to the usage of CreditorAccount in relation to account transfers in Denmark

Endpoints: POST /DK/domestic-payment-consents, POST /domestic-payment, POST /DK/domestic-scheduled-payment-consents, POST /domestic-scheduled-payment

Change date: 07.07.2022

Change: The full creditor account number (reg. no + account no) must always be provided when initiating account transfers in Denmark

Tags: #Change, #PSD2, #POST/DK/domestic-payment-consents, #POST/domestic-payment, #POST/DK/domestic-scheduled-payment-consents, #POST/domestic-scheduled-payment, #Payments, #AccountTransfer, #Registration_Number, #Creditor_Account_Number, #Denmark, #CreditorAccount_Identification, #DK.DanskeBank.DK.TransferFunds, #DK.DanskeBank.DK.AccountTransfer, #DK.DanskeBank.DK.AccountTransfer.SDCL, #DK.DanskeBank.DK.AccountTransfer.URGP, #DK.DanskeBank.DK.Salary, #07.07.2022

Please note that from 7 July 2022 it is required to use the full creditor account number when initiating domestic account transfers in Denmark. This applies to transfers within Danske Bank and to transfers to any other bank in Denmark. The full account number means that both the registration number (sort code) and the account number must always be stated in the "identification" string in the CreditorAccount object within the Initiation object. Please refer to the affected LocalInstruments/payment types in the 'Tags' section above.

31.03.2022

Planned Open Banking maintenance on 1st of April

Danske Bank wishes to inform about upcoming maintenance of Open Banking systems that will be carried out on 1st of April, between 05:00 and 07:00 CET

During above timeframe degradation and outages of Open Banking services are expected, so, we strongly advise to refrain from using Open Banking services during that time.

Since maintenance activities will also affect Open Banking security layer, we would like to ask Open Banking consumers to consider following:

  • It is expected that validity of refresh tokens acquired before maintenance window will not be affected.
  • Access tokens acquired before maintenance window will be invalidated.
  • Authorization codes acquired and not consumed before maintenance window will be invalidated and related consents will have to be reauthorized afterwards.

23.02.2022

New ID method in PSD2 PSU authorization - DK, private customers

Please note that new ID method - MitID is about to be available for DK private customers in PSD2 consent authorization flows from 28th of February.

Above change applies to PSU authorization only and should not require any additional development from TPPs.

25.10.2021

Length and format of TransactionId (Data/Transaction/TransactionId)

Change date: 04.11.2021

Tags: #Change, #GET/Transactions, #Transactions, #Account_Transactions, #TransactionId, #TransactionId_Lenght, #TransactionId_Format, #04112021

The TransactionId can contain up to 210 characters according to the UK Open Banking standard. The length of TransactionId in our current implementation is 32 characters and the format is like this example:

"TransactionId": "kp58e5c0-7cb4-4831-88ad-c52a03553ae3"

Any account transactions created on the 04.11.2021 at 00:00:00 CET and forward will have a TransactionId length of 64 characters and the format will be like this example:

"TransactionId": AD9A696607745A9AB9B6C73C7D497FB645483AA735471A08E7081B79EE3D6DWE

Please note that a transaction created before the change date e.g. at the 03.11.2021 – e.g. a scheduled payment with booking date 04.11.2021 - will get the current TransactionId format and length.

This also means that any transaction that may already be reported in a GET/Transactions response keeps its current id-format and the actual unique Id related to the transaction. It will thereby not change as the transaction has been created before the change date. A request for transactions spanning dates before and after the change date will therefore contain old and new editions of the TransactionId.

As it is the creation date of the transaction in question and not the booking date that determines the usage of the old and the new TransactionId, it is important that your system caters for both value-types going forward.

23.09.2021

v3.1.8 Implementation

Danske Banks wishes to inform that v3.1.8 release is now available in Production as of 23rd of September 2021.

Changelog:

  • OBReadTransaction6/Data/Transaction/Status is extended with status Rejected Please note – This is s specification update, but due to the design of our systems Danske Bank will never respond with status Rejected.
  • Updated version numbers
  • Please also note that VRP/Sweepings is currently not supported. We will provide more information about implementation date at a later stage.

16.09.2021

v3.1.8 Implementation

Danske Banks wishes to inform that v3.1.8 release will be available in Production with effect from 23rd of September 2021.

Changelog:

  • OBReadTransaction6/Data/Transaction/Status is extended with status Rejected
  • Updated version numbers

14.09.2021

Updated functionalities

Danske Bank wishes to inform about the following recent updates to PSD2 and UK Open Banking API. The updated versions are now available in Production

This includes updates to swaggers/Operational Guidelines

  • Endpoint Get Transactions has an extended response in field TransactionInformation to include further details when applicable. The following fields in the mentioned order are reflected when applicable and dependent on transaction type in question; Short message, Unstructured, Reference, 'EndToEndID:'. EndToEndID will always be presented, and with "NOTPROVIDED" if no value is available.
  • A new (optional) query parameter 'Order' has been added to end-point Get Transaction. Indicates desired date-time order for receival of transactions, either descending (desc) or ascending (asc). If omitted asc is default. Meaning, default (parameter 'Order' is omitted) is getting the oldest transactions first, 'Order=desc' delivers the newest transactions first.
  • Text on sender's account statement - Endpoint Create Domestic Payment and Create Domestic Scheduled Payment, path Data/Initiation/SupplementaryData/DebtorEntryText, offers an opportunity to add an account statement text on debiting account. For Private customers, 70 characters are available, for Business (District) customers 20 characters. Please note, the entry text is displayed differently depending on the market and digital channel used.
  • Expired payment consent status – Documentation has been updated to better reflect status on payment consent expiration.

07.07.2021

Changes to Get Transactions response data

Please note that we pr. 20.07.2021 will introduce changes to the "Get Transactions" response (Account Transaction Data).

We provide Debtor Account Number Information in the account transaction data In relation to some transactions in …/DebtorAccount/Identification. The Debtor Account Number and SchemeName will be removed after the above date if the Debtor Account Number Information on credit transactions is present and if the Debtor Account Number is Finnish. The Debtor Name will still be present if it is part of the data today – otherwise, the whole DebtorAccount element will be removed.

There will be no changes to the current setup if the Debtor Account Number is in other countries.

We request TPPs to delete any Debtor Account Number information in Finland that has been received via the Get Transactions response.

22.06.2021

v3.1.8 Implementation

Danske Banks wishes to inform about v3.1.8 release on 30th of September 2021. The new version is now available in our Sandbox.

Changelog:

  • OBReadTransaction6/Data/Transaction/Status is extended with status Rejected
  • Updated version numbers

22.06.2021

Revocation of OBIE Legacy Certificates

Following on from previous communications, Northern bank t/a Danske Bank would like to advise we will be removing support for OBIE legacy certificates for PSD2 purposes from our Sandbox and Production environment used for Open Banking UK.

We intend to remove support for OBIE legacy certificates as advised by the FCA and we are currently targeting 30th June 2021 for implementation of this change

Following this change, Northern bank t/a Danske Bank will only support the use of the following certificates in our Open Banking UK environments:

  • EIDAS Certificates (QWAC and QSEAL)
  • OBIE Certificates (OBWAC and OBSEAL)

01.06.2021

v3.1.7 Implementation

Danske Banks wishes to inform that v3.1.7 release will be available in Production with effect from 10th of June 2021.

Changelog:

  • Payment Initiation API – adjusted Debtor object in payment initiation responses.
  • Payment Initiation API – adjusted CountrySubDivision field type in Risk block.
  • Accounts and Transactions API – adjusted scope of parameters in GET /accounts/ response for accounts that were switched.
  • Accounts and Transactions API – UK Open Banking only, adjusted length of Party.Name parameter in GET /party/ response.
  • Update of API versions from 3.1.6 to 3.1.7
  • Various adjustments and fixes in API definition descriptions.

25.05.2021

Updated functionalities

Danske Bank wishes to inform the following updates to PSD2 API. The updated version is now available in Production

This includes updates to swaggers/Operational Guidelines

  • Possible to initiate Swedish giro payments (Bankgiro/Plusgiro) for Business customers. (only PSD2)

24.05.2021

Updated functionalities

Danske Bank wishes to inform the following updates to OBIE and PSD2 API. The updated version is now available in our Sandbox.

This includes updates to swaggers/Operational Guidelines

  • Endpoint GET /Transactions will extend the response in field TransactionInformation to include further details when applicable, like long message, reference and end-to-end-id. Will be released into production August 20th 2021.
  • Possible to initiate Swedish giro payments (Bankgiro/Plusgiro) for Business customers. Will be released into production May 25th 2021. (only PSD2)

12.05.2021

Restrictions to customers of Northern Bank Limited

From 13th May Open Banking services will be restricted to customers of Northern Bank Limited (trading as Danske Bank) only. For Danske Bank A/S (London Branch) customers please use PSD2 services.

10.03.2021

v3.1.7 Implementation

Danske Banks wishes to inform about v3.1.7 release on 10th of June 2021. The new version is now available in our Sandbox.

Changelog:

  • Payment Initiation API – adjusted Debtor object in payment initiation responses.
  • Payment Initiation API – adjusted CountrySubDivision field type in Risk block.
  • Accounts and Transactions API – adjusted scope of parameters in GET /accounts/ response for accounts that were switched.
  • Accounts and Transactions API – UK Open Banking only, adjusted length of Party.Name parameter in GET /party/ response.
  • Update of API versions from 3.1.6 to 3.1.7
  • Various adjustments and fixes in API definition descriptions.

23.02.2021

Adjustments in payments, PSD2

Danske Bank wishes to inform about the adjustments:

If you have any questions or queries, please refer to developer portal developers.danskebank.com alternatively email open.banking@danskebank.co.uk

  • PSD2 Payments, DK - adjusted validation of DebtorsAccount.Identification if it's submitted in API request: DebtorsAccountIdentification for scheme DK.DanskeBank.AccountNumber should include bank branch code.
  • Fixed self link issue in PSD2 GET/accounts/{AccountId}
  • Various bugfixes

11.12.2020

Restrictions on date formats

On 10 December 2020 we released changes for version 3.1.6. As part of the change we introduced tighter restrictions on date formats, but it looks like we misunderstood the specification and requests with a timezone are getting rejected instead of the timezone being ignored.

We are planning to release a fix on 15.12.2020 for this. As a workaround the TPP can request transaction information without a timezone.

02.12.2020

v3.1.6 in Production

Danske Banks wishes to inform that v3.1.6 will be available with effect from 10th December 2020, this includes changes to Operational Guidelines.

If you have any questions or queries, please refer to developer portal developers.danskebank.com alternatively email open.banking@danskebank.co.uk.

01.12.2020

EBA is revoking eIDAS certificates for UK third party providers

If you're currently using an eIDAS certificate for identification purposes, you'll need to obtain OBWACs and OBSeals certificates by 31 December 2020 to continue to access our data. This is because the EBA is revoking eIDAS certificates for UK third party providers on this date.

If you're currently using a legacy certificate for identification purposes, you'll need to obtain OBWACs and OBSeals certificates by the end of June 2021. This is because, while the Brexit transition period ends on 31 December 2020, the FCA is offering third party providers an additional six months to obtain new certificates.

Link to Open Banking UK Transparency calendar

23.11.2020

App-to-App implementation

On 10 December we will implement a new app-to-app solution to accomodate requirements from Third Party Providers (TPPs).

With the introduction of app-to-app for all markets, the customers of Danske Bank will be able to use their Mobile Bank application to authenticate during the PSD2 consent authorization journey using the same credentials/methods as normally used for accessing their accounts.

30.09.2020

Upcoming adjustment in SE domestic payments, PSD2

Danske Bank wishes to inform about the upcoming adjustment of Remittance Information related rules for SE domestic payments, private customers:

If you have any questions or queries, please refer to developer portal developers.danskebank.com alternatively email open.banking@danskebank.co.uk.

  • Remittance Information, Reference field length – max 12 characters.
  • Remittance Information, Unstructured – not supported.
  • The change will take effect from 8th of October 2020.

17.09.2020

v3.1.5 in Production

Danske Banks wishes to inform that v3.1.5 will be available with effect from 24th September 2020, this includes changes to MI and Operational Guidelines. Note from this date we will only support tls_client authentication method.

If you have any questions or queries, please refer to developer portal developers.danskebank.com alternatively email open.banking@danskebank.co.uk.

10.09.2020

v3.1.6 Implementation

Danske Banks wishes to inform v3.1.6 release on 10th December 2020, this includes changes to Operational Guidelines. The new version is now available in our Sandbox.

If you have any questions or queries, please refer to developer portal developers.danskebank.com alternatively email open.banking@danskebank.co.uk.

31.07.2020

v3.1.5 Implementation

Danske Banks wishes to inform v3.1.5 release on 24th September 2020 this includes MI and Operational Guidelines.

If you have any questions or queries, please refer to developer portal developers.danskebank.com alternatively email open.banking@danskebank.co.uk

20.07.2020

Decommission of v1.1 and v2.0 endpoints

Danske Banks wishes to inform all TPPs that with effect from 23 July 2020 v1.1 PIS or v2.0 AIS endpoints will no longer be available and you should move to a minimum of v3.0.

If you have any questions or queries, please refer to developer portal developers.danskebank.com alternatively email open.banking@danskebank.co.uk

19.06.2020

Upcoming changes to the authorization flow

Following the Open Banking UK security definitions, Danske Bank will be updating the Open Banking and PSD2 consent authorization flow to be compliant with the Financial Grade API (FAPI) Profile and FAPI Conformance Suite. Amongst others, the update will include much stricter validations as well as enhanced error messages returned to the TPP when the authorization request does not comply with the FAPI guidelines.

These changes will take effect in our Sandbox on June 23rd and in production for Open Banking UK on July 28th and for PSD2 on September 24th. You can read more about our updated authorization flow in our documentation: /regulatory-apis/overview

In short, the main changes are:

  • Dropping support for RS256 – in the future only PS256 is allowed
  • Dropping support for client_secret_post authentication – only tls_client_auth will be allowed
  • Strict hybrid flow validations following the FAPI conformance suite guidelines
  • Redirect back to TPPs on all authorization request errors (non PSU related)

25.03.2020

Decommission of v1.1 and v2.0 endpoints

Danske Banks wishes to notifying all TPPs that are still using v1.1 PIS or v2.0 AIS endpoints that with effect from 23 July 2020 these endpoints will no longer be available and you should move to a minimum of v3.0.

14.09.2019

PSD2 and legacy access

In order to ensure a robust roll out of the Danske Bank PSD2 API's and minimize disruption for third party providers - Danske Bank will keep the legacy access to PSU Payment accounts in place until further notice. Any removal of the legacy access to PSU Payment accounts will be notified here.