APIHub
Back to Explore

Confirmation of Funds API Specification

The Confirmation of Funds API lets a third‑party provider create, retrieve, and delete funds‑confirmation consents, and submit a funds‑confirmation request using those consents.

Finance
OAuth
HTTPS
CORS: Unknown
Description enriched …
Visit official documentation

Latency

385ms p95

Uptime

100.0% 30d

Playground

Verified

live

Endpoints

REST · JSON
POST

/funds-confirmation-consents

Create Funds Confirmation Consent

  • x-fapi-auth-date (header) — 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 (header) — The PSU's IP address if the PSU is currently logged in with the TPP.
  • x-fapi-interaction-id (header) — An RFC4122 UID used as a correlation id.
  • Authorization (header, required) — An Authorisation Token as per https://tools.ietf.org/html/rfc6750
  • x-customer-user-agent (header) — Indicates the user-agent that the PSU is using.
DELETE

/funds-confirmation-consents/{ConsentId}

Delete Funds Confirmation Consent

  • ConsentId (path, required) — ConsentId
  • x-fapi-auth-date (header) — 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 (header) — The PSU's IP address if the PSU is currently logged in with the TPP.
  • x-fapi-interaction-id (header) — An RFC4122 UID used as a correlation id.
  • Authorization (header, required) — An Authorisation Token as per https://tools.ietf.org/html/rfc6750
  • x-customer-user-agent (header) — Indicates the user-agent that the PSU is using.
GET

/funds-confirmation-consents/{ConsentId}

Get Funds Confirmation Consent

  • ConsentId (path, required) — ConsentId
  • x-fapi-auth-date (header) — 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 (header) — The PSU's IP address if the PSU is currently logged in with the TPP.
  • x-fapi-interaction-id (header) — An RFC4122 UID used as a correlation id.
  • Authorization (header, required) — An Authorisation Token as per https://tools.ietf.org/html/rfc6750
  • x-customer-user-agent (header) — Indicates the user-agent that the PSU is using.
POST

/funds-confirmations

Create Funds Confirmation

  • x-fapi-auth-date (header) — 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 (header) — The PSU's IP address if the PSU is currently logged in with the TPP.
  • x-fapi-interaction-id (header) — An RFC4122 UID used as a correlation id.
  • Authorization (header, required) — An Authorisation Token as per https://tools.ietf.org/html/rfc6750
  • x-customer-user-agent (header) — Indicates the user-agent that the PSU is using.

4 endpoints auto-detected

Authentication

This API requires authentication: OAuth.

curl -X POST \
  "https://openbanking.org.uk/funds-confirmation-consents"

openbanking.org.uk · HTTPS only