I am developing for the

market, looking for the

API Documentation.

Home

>

API Products

>

United Kingdom - Confirmation of Funds PSD2 API Documentation

Confirmation of Funds PSD2

Summary

The Funds Confirmation API allows a TPP to check the availability of funds in CPB client's authorized accounts through a secure interface.

The sandbox provides synthetic data to enable a TPP to explore the API and perform preliminary functional testing on a simulated environment. The calls to the API will be validated for correctness and compliance with the API specification to help the TPP uncover issues early when integrating with the API.

Below are some sample test data and unique identifiers that can be used for invoking the APIs and for recreating specific scenarios for validation and testing by the TPP. Some of the characteristics of the sandbox are listed below:

  • It uses a primarily stateless interaction model where some states such as the account balance is kept constant.
  • The sandbox implements an OAuth 2.0 based Authentication and Authorization flow. In addition to using the API Playground to invoke the APIs, the API keys retrieved while registering an application can be used for calling the APIs from any REST client, such as curl, Postman, SoapUI, or programmatically through REST calls using access tokens retrieved either through a Client Credential or Authorization Code grant types depending on the API being invoked.
  • As the sandbox is open to both TPPs and the general public, the following validations will be deferred to the integration environments: verification of TPP identity, SSA, EIDAS, QSEAL, QWAC certificates, mutual TLS. These validations will be available in the fully functional market integrated interfaces with valid Competent Authority issued certificates.
  • 3-legged authentication requests for this API must be of the 'cpb_ob_fundsconfirmations' scope.

Test Data

Consent IDFunds Available
9COF201999664300Yes
9COF201999664302No

The Confirmation of Funds PSD2 API uses the authorization_code grant type, for authorization details CLICK HERE

Want to try this API out on our Playground?

Go play now
Endpoints on this page
post /open-banking/v3.1/cbpii/funds-confirmation-consents Creates funds confirmation consent
get /open-banking/v3.1/cbpii/funds-confirmation-consents/{ConsentId} Retrieve funds confirmation consent
delete /open-banking/v3.1/cbpii/funds-confirmation-consents/{ConsentId} Delete funds confirmation consent
post /open-banking/v3.1/cbpii/funds-confirmations Create funds confirmation

Creates funds confirmation consent

post /open-banking/v3.1/cbpii/funds-confirmation-consents
Description

Request CPB to create a new funds-confirmation-consent resource which effectively allows the TPP to send a copy of the consent to CPB to authorise access to funds confirmation resource. Prior to calling the API, the TPP must have an access token issued by the CPB using a client credentials grant.

Body Parameters
OBFundsConfirmationConsent1Param
required
Default
Show schema
Header Parameters
Accept
string required
application/json
x-fapi-financial-id
string required
The unique id of CPB to which the request is issued. The unique id will be issued by OB.
x-fapi-customer-last-logged-time
string Optional
The time when the PSU last logged in with the TPP. All dates in the HTTP headers are represented as RFC 7231 Full Dates. An example is below: Sun, 10 Sep 2017 19:43:31 UTC
x-fapi-customer-ip-address
string Optional
The PSU's IP address if the PSU is currently logged in with the TPP.
x-fapi-interaction-id
string Optional
An RFC4122 UID used as a correlation id.
Authorization
string required
An Authorisation Token as per https://tools.ietf.org/html/rfc6750
x-customer-user-agent
string Optional
Indicates the user-agent that the PSU is using.
client_id
string required
Client Id generated during application registration
  • cURL
  • Ruby
  • Python
  • PHP
  • Java
  • Node
  • Go
  • Swift

Example Request

Example Request

Example Request

Example Request

Example Request

Example Request

Example Request

Example Request

Responses
201

This operation returns no content.
400

This operation returns no content.
401

This operation returns no content.
403

This operation returns no content.
404

This operation returns no content.
405

This operation returns no content.
406

This operation returns no content.
415

This operation returns no content.
429

This operation returns no content.
500

This operation returns no content.

Retrieve funds confirmation consent

get /open-banking/v3.1/cbpii/funds-confirmation-consents/{ConsentId}
Description

Retrieve funds confirmation consent resource for a given ConsentId. Prior to calling this operation, the TPP must have an access token issued by the CPB using a client credentials grant.

Path Parameters
ConsentId
string required
ConsentId
Header Parameters
Accept
string required
application/json
x-fapi-financial-id
string required
The unique id of CPB to which the request is issued. The unique id will be issued by OB.
x-fapi-customer-last-logged-time
string Optional
The time when the PSU last logged in with the TPP. All dates in the HTTP headers are represented as RFC 7231 Full Dates. An example is below: Sun, 10 Sep 2017 19:43:31 UTC
x-fapi-customer-ip-address
string Optional
The PSU's IP address if the PSU is currently logged in with the TPP.
x-fapi-interaction-id
string Optional
An RFC4122 UID used as a correlation id.
Authorization
string required
An Authorisation Token as per https://tools.ietf.org/html/rfc6750
x-customer-user-agent
string Optional
Indicates the user-agent that the PSU is using.
client_id
string required
Client Id generated during application registration
  • cURL
  • Ruby
  • Python
  • PHP
  • Java
  • Node
  • Go
  • Swift

Example Request

Example Request

Example Request

Example Request

Example Request

Example Request

Example Request

Example Request

Responses
200

This operation returns no content.
400

This operation returns no content.
401

This operation returns no content.
403

This operation returns no content.
404

This operation returns no content.
405

This operation returns no content.
406

This operation returns no content.
429

This operation returns no content.
500

This operation returns no content.

Delete funds confirmation consent

delete /open-banking/v3.1/cbpii/funds-confirmation-consents/{ConsentId}
Description

Request CPB to revoke a given funds confirmation consent for the TPP. TPP must delete the funds-confirmation-consent resource with the CPB after getting confirmation about consent revocation from the CPB client. This is done by making a call to DELETE the funds-confirmation-consent resource. Prior to calling the operation, the TPP must have an access token issued by the CPB using a client credentials grant.

Path Parameters
ConsentId
string required
ConsentId
Header Parameters
Accept
string required
application/json
x-fapi-financial-id
string required
The unique id of CPB to which the request is issued. The unique id will be issued by OB.
x-fapi-customer-last-logged-time
string Optional
The time when the PSU last logged in with the TPP. All dates in the HTTP headers are represented as RFC 7231 Full Dates. An example is below: Sun, 10 Sep 2017 19:43:31 UTC
x-fapi-customer-ip-address
string Optional
The PSU's IP address if the PSU is currently logged in with the TPP.
x-fapi-interaction-id
string Optional
An RFC4122 UID used as a correlation id.
Authorization
string required
An Authorisation Token as per https://tools.ietf.org/html/rfc6750
x-customer-user-agent
string Optional
Indicates the user-agent that the PSU is using.
client_id
string required
Client Id generated during application registration
  • cURL
  • Ruby
  • Python
  • PHP
  • Java
  • Node
  • Go
  • Swift

Example Request

Example Request

Example Request

Example Request

Example Request

Example Request

Example Request

Example Request

Responses
204

This operation returns no content.
400

This operation returns no content.
401

This operation returns no content.
403

This operation returns no content.
404

This operation returns no content.
405

This operation returns no content.
406

This operation returns no content.
429

This operation returns no content.
500

This operation returns no content.

Create funds confirmation

post /open-banking/v3.1/cbpii/funds-confirmations
Description

Request CPB to create the funds-confirmation resource to confirm the funds availability. The TPP must use a token issued via an authorization code grant and specify the ConsentId in the request payload and TPP must use a currency of the account.

Body Parameters
OBFundsConfirmation1Param
required
Default
Show schema
Header Parameters
Accept
string required
application/json
x-fapi-financial-id
string required
The unique id of CPB to which the request is issued. The unique id will be issued by OB.
x-fapi-customer-last-logged-time
string Optional
The time when the PSU last logged in with the TPP. All dates in the HTTP headers are represented as RFC 7231 Full Dates. An example is below: Sun, 10 Sep 2017 19:43:31 UTC
x-fapi-customer-ip-address
string Optional
The PSU's IP address if the PSU is currently logged in with the TPP.
x-fapi-interaction-id
string Optional
An RFC4122 UID used as a correlation id.
Authorization
string required
An Authorisation Token as per https://tools.ietf.org/html/rfc6750
x-customer-user-agent
string Optional
Indicates the user-agent that the PSU is using.
client_id
string required
Client Id generated during application registration
  • cURL
  • Ruby
  • Python
  • PHP
  • Java
  • Node
  • Go
  • Swift

Example Request

Example Request

Example Request

Example Request

Example Request

Example Request

Example Request

Example Request

Responses
201

This operation returns no content.
400

This operation returns no content.
401

This operation returns no content.
403

This operation returns no content.
404

This operation returns no content.
405

This operation returns no content.
406

This operation returns no content.
415

This operation returns no content.
429

This operation returns no content.
500

This operation returns no content.