This page is for Third Party Providers (TPPs) and software developers. Not a developer? Visit our webpage for customers

Open Banking for Third Party Providers

We believe Open Banking can give our customers access to new products and services and will increase innovation in financial services. We’ve already collaborated with TPPs to give our customers access to some of these new services and will continue to increase the APIs and channels we support.

Before we can onboard you, you must be registered with the FCA or another European regulator and enrolled in the Open Banking Directory.

You can find more information on how to get started with us and on the APIs we currently support below.

Getting started

  • Get enrolled

    Get enrolled

    You must be registered with the FCA or another European regulator to enrol in the Open Banking Directory.

    Once you’ve enrolled and signed up for access to Open Banking, you can find our details in the OB Directory by searching ‘Northern Bank Limited t/a Danske Bank’

    In the Directory you can find our well-known /openid configurations for Danske Bank Personal and Danske Bank Business which will show you:

    • Our registration endpoint
    • Supported authorisation methods
    • Authorisation and token endpoint URIs
    • Other information you may find useful.
  • Onboarding with Danske Bank

    Onboarding with Danske Bank

    We support dynamic client registration endpoint to onboard to Danske Bank Personal, Danske Bank Business or both.

    You can get more information on dynamic client registration in the Open Banking specifications.

  • Danske Bank Personal

    Danske Bank Personal

    You can use the links below to find our well-known configurations for Danske Bank Personal in the Open Banking Directory.

    Environment Directory well-known API base path URLs
    Production Link

    V1: https://obp-api.danskebank.com/open-banking/v1.1/

    V2: https://obp-api.danskebank.com/open-banking/v2.0/

  • Danske Bank Business

    Danske Bank Business

    You can use the links below to find our well-known configurations for Danske Bank Business in the Open Banking Directory:

    Environment Directory well-known API base path URLs
    Production Link

    V1: https://obp-api.danskebank.com/open-banking/v1.1/

    V2: https://obp-api.danskebank.com/open-banking/v2.0/

  • Open Data

    Open Data

    You can use the API base path URIs below to get information on the locations of our branches and ATMs and on our financial products:

    Locate all Danske Bank ATMs https://obp-data.danskebank.com/open-banking/v2.2/atms
    Locate all Danske Bank Branches https://obp-data.danskebank.com/open-banking/v2.2/branches
    Discover Danske Bank Financial Products
    • https://obp-data.danskebank.com/open-banking/v2.2/business-current-accounts
    • https://obp-data.danskebank.com/open-banking/v2.2/personal-current-accounts
    • https://obp-data.danskebank.com/open-banking/v2.2/unsecured-sme-loans

Next steps

Once your registration request is received, we’ll respond with your client credentials which will identify you in all future Open Banking requests. You must ensure this information is held securely and not shared with any other companies.

We want to make it as easy as possible for you to onboard with us. You can get more information on the Open Banking Directory specifications and guidelines for Read/Write Participants on the Open Banking Developer Zone.

If you have any issues with onboarding please send an email to: open.banking@danskebank.co.uk

TPP/developer FAQs

  • What Open Banking APIs does Danske Bank provide?

    We support these Open Banking APIs:

    Account and transaction
    Account request POST /account-requests
    GET /account-requests/{AccountRequestId}
    DELETE /account-requests/{AccountRequestId}
    Accounts GET /accounts
    GET /accounts/{AccountId}
    Balances GET /accounts/{AccountId}/balances
    Transactions GET /accounts/{AccountId}/transactions
    Beneficiaries GET /accounts/{AccountId}/beneficiaries
    Direct debits GET /accounts/{AccountId}/direct-debits
    Standing orders GET /accounts/{AccountId}/standing-orders
    Products GET /accounts/{AccountId}/product
    Supporting information for Account and Transaction API
    Transaction data Transaction data will only be returned for a maximum of 25 months from date of request
    Pagination We support pagination on GET /accounts/{AccountId}/transactions API
    API call limits You should adhere to the Open Banking ‘fair usage’ policy of no more than 4 requests for data where the PSU is not present within a 24 hour period.
    Re-authentication

    While the PSU consent to you may be open ended (until revoked), the PSUs will need to re-authenticate with us once every 90 days so that we can continue to share their data.

    In exceptional circumstances or where we think a request may be fraudulent, we may also require the PSU to re-authenticate.



    Payments
    POST /payments}
    POST /payment-submissions
    GET /payments/{PaymentId}
    GET /payment-submissions/{PaymentSubmissionId}
    Supporting Information for Payment API
    Payment type We accept single immediate payments in GBP which will be executed via the Faster Payments Scheme
    FPS limits

    Our faster payment limit for online payments is:

    • Personal : GBP 25,000 daily limit
    • Business : GBP 100,000 per payment
    Payment submission You must submit a payment for execution within 60 minutes of the PSU’s authentication.
  • I received an exception code - what does it mean?

    Standard HTTP codes used within our APIs are:

    Error code Name Explanation
    400 Bad request For example if you have requested a resource with a resource ID that does not exist
    401 Unauthorised Access refused. This might be because of an expired access token. Re-authenticating the PSU and issuing a new token might solve this problem
    403 Forbidden Authenticated user tried to access a forbidden resource. Most likely to happen in authorisation UI.
    404 Not found Request for a resource that is not defined by OB specification or we have not implemented the endpoint
    405 Method not allowed You have tried to access the resource with a HTTP method that is not supported
    406 Not acceptable The request contained an Accept header other than permitted media types and a character set other than UTF-8
    415 Unsupported Media Type The operation was refused because the payload is in a format not supported by this method on the target resource
    429 Too many requests The operation was refused as too many requests have been made within a certain timeframe
    500 Internal Server Error Something went wrong with the API gateway or micro-service
    503 Services unavailable or too busy Server is temporarily unable to handle your request. Try again later.
  • What are your API call limits?

    You should adhere to the Open Banking ‘fair usage’ policy of no more than 4 requests for data where the PSU is not present within a 24 hour period.

  • We provide account information services - how long can we access a customers account information?

    This depends on your agreement with the PSU. If you have a long-lived or open-ended consent then you can access account information as agreed with them unless they revoke their consent. However PSUs will need to re-authenticate with us once every 90 days so that we can continue to share their data.

  • We provide payment initiation services – does the PSU need to be present to make a payment?

    Yes, the PSU must be present when a payment transaction is initiated as they must consent and authorise the payment.

  • Can a PSU cancel their consent with Danske Bank?

    Yes, a PSU can revoke their consent to you in our online banking channel. If they do this, we won’t provide you with any further account information until/unless the PSU gives you their consent again