Create a Funds Confirmation Consent
Changed onEnables a CBPII to ask an ASPSP to create a new funds-confirmation-consent resource, by sending a copy of the consent to the ASPSP.
On success (HTTP 201), the response contains a ConsentId, CreationDateTime, the current Status of the consent, StatusUpdateDateTime, and the DebtorAccount associated with the consent. The consent may initially be returned with status AWAU (AwaitingAuthorisation).
Note: Creating this consent does not immediately authorise funds confirmations. The PSU will need to authenticate and authorise the consent with their ASPSP before the consent can be used for funds confirmation requests.
Request
- Base URL/open-banking/v4.0/cbpii (relative, and the document was published on a file host, not at the API’s origin)
- URL/open-banking/v4.0/cbpii/funds-confirmation-consents
- AuthOAuth 2Client credentialsToken URL: https://authserver.example/token scopes: fundsconfirmations
Headers
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
The PSU's IP address if the PSU is currently logged in with the TPP.
An RFC4122 UID used as a correlation id.
An Authorisation Token as per https://datatracker.ietf.org/doc/html/rfc6750
Indicates the user-agent that the PSU is using.
A detached JWS signature of the body of the payload.
Only used if an ASPSP requires the client ID in order to return rate limit headers.
TPPs must refer to ASPSP developer portals for further information on any rate limit policies, if the headers are supported and any additional requirements.
This header must not be used for client authentication
Request body
Example request
{
"Data": {
"ExpirationDateTime": "2026-10-01T10:15:30+00:00",
"DebtorAccount": {
"SchemeName": "UK.OBIE.SortCodeAccountNumber",
"Identification": "30949301273801",
"Name": "Jane Smith",
"SecondaryIdentification": "Roll 56988",
"Proxy": {
"Identification": "+441632960540",
"Code": "TELE",
"Type": "Telephone"
}
}
}
}Response
Funds Confirmation Consent Created
Example response
{
"Data": {
"ConsentId": "FCC-20260401-0001",
"CreationDateTime": "2026-04-01T10:15:30+00:00",
"Status": "AUTH",
"StatusReason": [
{
"StatusReasonCode": "U009",
"StatusReasonDescription": "The consent is not in a status that allows funds confirmation.",
"Path": "Data.ConsentId"
}
],
"StatusUpdateDateTime": "2026-04-01T10:20:30+00:00",
"ExpirationDateTime": "2026-10-01T10:15:30+00:00",
"DebtorAccount": {
"SchemeName": "UK.OBIE.SortCodeAccountNumber",
"Identification": "30949301273801",
"Name": "Jane Smith",
"SecondaryIdentification": "Roll 56988",
"Proxy": {
"Identification": "+441632960540",
"Code": "TELE",
"Type": "Telephone"
}
}
}
}Changes
- info
added the new optional
headerrequest parameterx-jws-signature
- info
- warning
the optional response header
x-jws-signatureremoved for the status201 - warning
the optional response header
x-jws-signatureremoved for the status400 - warning
the optional response header
x-jws-signatureremoved for the status401 - warning
the optional response header
x-jws-signatureremoved for the status403 - warning
the optional response header
x-jws-signatureremoved for the status405 - warning
the optional response header
x-jws-signatureremoved for the status406 - warning
the optional response header
x-jws-signatureremoved for the status415 - warning
the optional response header
x-jws-signatureremoved for the status429 - warning
the optional response header
x-jws-signatureremoved for the status500 - warning
deleted the
headerrequest parameterx-jws-signature
- warning