Payments Baskets - PSD2

IMPORTANT! All the documentation related with this API authorization can now be find in a separate documentation page.

API Overview

The basic usage scenario for Payments Basket Initiation is shown on this diagram:

When a TPP wants to initiate a batch (basket) of payments (with PSU being the payer) it acquires a TPP access token and creates a payments basket consent. The consent contains details about the payments to be processed. The available types of payments that can be included into the basket are:

• domestic payment / domestic scheduled payment.

Payments basket may contain up to 100 payments of above stated types (same type payments or combination of types).

Payments basket consent needs to be confirmed by the PSU (OpenID Connect Hybrid Flow). If PSU approves it, then TPP will receive an access token that will allow him to create a payments basket request and thus submit the payments for processing. Each payments basket request has a unique resource id that can be used for checking the basket and payments processing status. The access tokens for Payments Basket Initiation API cannot be refreshed or reused. The Authorization steps need to be repeated for each payments basket. Next sections provide a more detailed description for the steps mentioned above.

Making API calls

Technical description of Payment Initiation api endpoints can be found in the reference section: link. In each call to the Payment Initiation api these are obligatory:

• MTLS connection (with the Network certificate used during TPP onboarding: link).

• Valid access token (acquired as described in the Authorization section: link).

Additionally the following headers may apply for api calls involving a payload (please check reference section to see if they’re required):

• Valid x-fapi-financial-id value in header (for Danske Bank it’s 0015800000jf7AeAAI),

• An x-idempotency-key header with a random value that will prevent multiple processing of the same request,

• An x-jws-signature header with detached JWS signature of the payload.

A sample request might look like this:

GET /domestic-payments/123 HTTP/1.1
Authorization: Bearer <access token>
x-fapi-financial-id: 0015800000jf7AeAAI

Sandbox test data

The following test customers can be used for authenticating in Sandbox authorization flows:

Login / Password

8195475386 / xUKSWPgHy2H2XBt8cv

If you find the test data not matching your needs please contact us.

TPP Documentation

Trade Mark License Agreement

For all TPPs wanting to use Danske Bank logo’s on their websites, documentation or communications we require you to sign and return the Trademark Licence agreement found here to us at open.banking@danskebank.co.uk. This document contains the brand guidelines and official logo’s for you to use once we are in receipt of your signed Licence agreement.

App to App Guide

Our new Open Banking App to App is live for TPPs and customers to use from 13th September 2019. Please feel free to familiarize with our guides here.