Account and Transaction - 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 Account / Transaction api is shown on this diagram:

When a TPP wants to have access to PSU’s account / transaction information it acquires a temporary access token and creates an account access consent. The consent lists in detail all the various types of information TPP wants to have access to. Account access consent needs to be confirmed by the PSU (OpenID Connect Hybrid Flow).  If PSU approves then TPP will receive an access token that will allow him to call the Account and Transaction api and retrieve PSU related information. The access tokens for Account / Transaction apis can be refreshed multiple times so the Authorization steps will be performed rarely. Next sections provide a more detailed description for the steps mentioned above. The Openbanking UK reference documentation can be found here: link.

Making API calls

Technical description of Account / Transaction api endpoints can be found in the reference section: link. In each call to the Accounts / Transaction 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 /accounts 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.