Skip to main content
UK Open Banking

Confirmation of Funds - UK OB

Version

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

API Overview

The basic usage scenario for Confirmation of Funds api is shown on this diagram:

cof-overview-img10

When a TPP wants to confirm that PSU has specific funds available it acquires a temporary access token and creates a Funds Confirmation Consent. The consent specifies the PSU’s account that will be used for funds availability checks.

Funds Confirmation 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 perform funds confirmations.

The access tokens for Confirmation of Funds api 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 Confirmation of Funds api endpoints can be found in the reference section: link. In each call to the Confirmation of Funds 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:

POST /funds-confirmations HTTP/1.1
Authorization: Bearer <access token> 
x-fapi-financial-id: 0015800000jf7AeAAI
x-idempotency-key: 30363:29247412262902
x-jws-signature: eyJiNjQiOmZhbH...

{
  "Data": {
    "ConsentId": "urn:cof:v3:2c8c2dc3-1b97-40b9-bc6b-618102df4725",
    "Reference": "Purchase01",
    "InstructedAmount": {
       "Amount": "20.00",
       "Currency": "GBP"
    }
  }
}

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.

Architectural constraints

State
Active

Technical constraints

Static URL
/regulatory-apis/confirmation-of-funds---uk-ob
Environment(s)
SANDBOX