Consents
Create
The API allows the TPP to ask an ASPSP to create a new funds-confirmation-consent resource.
CURL
![]()
curl -i \
-H "Authorization: Bearer authorization" \
-H "Content-Type: application/json" \
-H "x-fapi-interaction-id: 93bac548-d2de-4546-b106-880a5018460d" \
-H "x-fapi-auth-date: Sun, 10 Sep 2017 19:43:31 GMT" \
-H "x-fapi-customer-ip-address: 104.25.212.99" \
-d 'eyJhbGciOiJQUzI1NiIsImtpZCI6InRlc3QifQ.eyJEYXRhIjp7IkV4cGlyYXRpb25EYXRlVGltZSI6IjIwMTctMDYtMDVUMTU6MTU6MTMrMDA6MDAiLCJEZWJ0b3JBY2NvdW50Ijp7IlNjaGVtZU5hbWUiOiJVSy5PQklFLlNvcnRDb2RlQWNjb3VudE51bWJlciIsIklkZW50aWZpY2F0aW9uIjoiMTEyODAwMDEyMzQ1NjciLCJOYW1lIjoiQW5kcmVhIFNtaXRoIiwiU2Vjb25kYXJ5SWRlbnRpZmljYXRpb24iOiIwMDAyIn19fQ.AnL3CRGO0b2jXGHVohs09WkF3J8i9kAlSf_HMfSROQuiWDA3oTspZoy5fniecs4vIjtzEfbcnurQxCB1bvuolz0LwDXnMCnc33eEWD4P1-8GYkApXJ8j-mxvEAwjgbOy57XDnt2vPqk7Bdr71ubllEG3W6siXccGa8KuHDEWI4wO2r-UV7-bXSf8uISSN4IBtks7PYaarZ2TEXwh0ReaDQlUT5SDPU4P3PmQ7TlLYCdXyn43xZPb-y0uFC7F3OsuerYGsdCFSz7rBMz8wZcifhy2Z8dn6h6azbKn4oSj0aMgid1qZLBjeRtPsvxCf06oLTE6Z_3WMJqQaGKvVA3Daw' \
-X POST "/api/:provider_code/open-banking/v3.1.11/cbpii/funds-confirmation-consents"
Example of request
![]()
{"Data":{"ExpirationDateTime":"2017-06-05T15:15:13+00:00","DebtorAccount":{"SchemeName":"UK.OBIE.SortCodeAccountNumber","Identification":"11280001234567","Name":"Andrea Smith","SecondaryIdentification":"0002"}}}
Example of response
![]()
{"Data":{"ConsentId":"18463","CreationDateTime":"2017-06-05T15:15:13+00:00","Status":"AwaitingAuthorisation","StatusUpdateDateTime":"2017-06-05T15:15:13+00:00","ExpirationDateTime":"2017-06-05T15:15:13+00:00","DebtorAccount":{"SchemeName":"UK.OBIE.SortCodeAccountNumber","Identification":"11280001234567","Name":"Andrea Smith","SecondaryIdentification":"0002"}},"Links":{"Self":"/open-banking/v3.1/cbpii/funds-confirmation-consents/18463"},"Meta":{}}
Request
POST
/api/:provider_code/open-banking/v3.1.11/cbpii/funds-confirmation-consents
Headers
| Header | Type | Description |
|---|---|---|
Accept
|
string, optional | Media type that is acceptable for the response. Default value: application/json |
x-fapi-interaction-id
|
string, optional | An RFC4122 UID used as a correlation Id. |
Content-Type
|
string, optional | The media type of the body of the request. Default value: application/json |
Idempotency-Key
|
string, optional | Unique uuid used to recognize subsequent retries of the same request valid for 24 hours. Allowed length: max: 40 characters |
Authorization
|
string, required | Standard HTTP Header; Allows Credentials to be provided to the Authorisation / Resource Server depending on the type of resource being requested. For OAuth 2.0 / OIDC, this comprises of either the Basic / Bearer Authentication Schemes. Can raise: HeaderMissing, HeaderInvalid, ResourceNotFound, Forbidden |
x-fapi-auth-date
|
string, optional | The time when the PSU last logged in with the TPP. Supplied as HTTP-date (RFC7231), e.g. Sun, 10 Sep 2017 19:43:31 GMT. |
x-fapi-customer-ip-address
|
string, optional | The PSU's IP address if the PSU is currently logged in with the TPP. Identifies user presence for the data fetch. |
Request parameters
Response headers
| Header | Type | Description |
|---|---|---|
Content-Type
|
string, required | The media type of the body of the request. |
x-fapi-interaction-id
|
string, required | An RFC4122 UID used as a correlation Id. If provided, the ASPSP must "play back" this value in the x-fapi-interaction-id response header. |
Retry-After
|
integer, optional | Amount of time in seconds after which Salt Edge PSD2 Compliance Solution resends the previously failed request. |
Response
Upon successful request, 200 status code will be returned. See ‘Related Errors’ table for other possibilities.
Related Errors
| Class | Code | Description |
|---|---|---|
| ResourceNotFound | 400 | Specified resource doesn't exist. |
| FieldInvalidDate | 400 | An invalid date is supplied. |
| FieldInvalid | 400 | An invalid value is supplied in the field. More details in error_message. |
| HeaderMissing | 400 | A required HTTP header has not been provided. |
| HeaderInvalid | 400 | An invalid value is supplied in the HTTP header. |
| Forbidden | 403 | Action is forbidden. More details in error_message. |
Show
The API allows the TPP to ask an ASPSP to show a funds-confirmation-consent resource.
CURL
![]()
curl -i \
-H "Authorization: Bearer authorization" \
-H "Content-Type: application/json" \
-H "x-fapi-interaction-id: 93bac548-d2de-4546-b106-880a5018460d" \
-H "x-fapi-auth-date: Sun, 10 Sep 2017 19:43:31 GMT" \
-H "x-fapi-customer-ip-address: 104.25.212.99" \
-d 'eyJhbGciOiJQUzI1NiIsImtpZCI6InRlc3QifQ.e30.b82Qirl1gC1VWUssXMgXfcBWn-sG3JL0LSfhgbA6wpkJn9HB6FkF2UiWWzu2h13qPqxMjLxs8WVuDWId_9YSTi0Kc_zyfUMMIQUJSwVz36KKguLQx2l7aX3vRzXOdsQuHOGirzLxCnn1TiWhhi1b-VRcyCIrsaj1kuXNm953XOMZfOlBrQBkA4v8NMOyrw65zFAIwzsne8u6LNdtJF5viwtUy9hIFApvH_3HMqPY4WHFQBGk1pxN8QKsJXBq5m8EQhf5CfKGoykuKbko9aion7nS0bkctKwuKqVxzuYMPA2_-O1dhmQQrb4_p-ZohEpeij1jILk8W-khx3gsL356cg' \
-X GET "/api/:provider_code/open-banking/v3.1.11/cbpii/funds-confirmation-consents/:consent_id"
Example of response
![]()
{"Data":{"ConsentId":"18463","CreationDateTime":"2017-06-05T15:15:13+00:00","Status":"AwaitingAuthorisation","StatusUpdateDateTime":"2017-06-05T15:15:13+00:00","ExpirationDateTime":"2017-06-05T15:15:13+00:00","DebtorAccount":{"SchemeName":"UK.OBIE.SortCodeAccountNumber","Identification":"11280001234567","Name":"Andrea Smith","SecondaryIdentification":"0002"}},"Links":{"Self":"/open-banking/v3.1/cbpii/funds-confirmation-consents/18463"},"Meta":{}}
Request
GET
/api/:provider_code/open-banking/v3.1.11/cbpii/funds-confirmation-consents/:consent_id
Headers
| Header | Type | Description |
|---|---|---|
Accept
|
string, optional | Media type that is acceptable for the response. Default value: application/json |
x-fapi-interaction-id
|
string, optional | An RFC4122 UID used as a correlation Id. |
Authorization
|
string, required | Standard HTTP Header; Allows Credentials to be provided to the Authorisation / Resource Server depending on the type of resource being requested. For OAuth 2.0 / OIDC, this comprises of either the Basic / Bearer Authentication Schemes. Can raise: HeaderMissing, HeaderInvalid, ResourceNotFound, Forbidden |
x-fapi-auth-date
|
string, optional | The time when the PSU last logged in with the TPP. Supplied as HTTP-date (RFC7231), e.g. Sun, 10 Sep 2017 19:43:31 GMT. |
x-fapi-customer-ip-address
|
string, optional | The PSU's IP address if the PSU is currently logged in with the TPP. Identifies user presence for the data fetch. |
Request parameters
Response headers
| Header | Type | Description |
|---|---|---|
Content-Type
|
string, required | The media type of the body of the request. |
x-fapi-interaction-id
|
string, required | An RFC4122 UID used as a correlation Id. If provided, the ASPSP must "play back" this value in the x-fapi-interaction-id response header. |
Retry-After
|
integer, optional | Amount of time in seconds after which Salt Edge PSD2 Compliance Solution resends the previously failed request. |
Response
Upon successful request, 200 status code will be returned. See ‘Related Errors’ table for other possibilities.
Related Errors
| Class | Code | Description |
|---|---|---|
| ResourceNotFound | 400 | Specified resource doesn't exist. |
| FieldInvalid | 400 | An invalid value is supplied in the field. More details in error_message. |
| HeaderMissing | 400 | A required HTTP header has not been provided. |
| HeaderInvalid | 400 | An invalid value is supplied in the HTTP header. |
| Forbidden | 403 | Action is forbidden. More details in error_message. |
Destroy
If the PSU revokes consent to confirm funds with the TPP, the TPP must delete the funds-confirmation-consent resource.
CURL
![]()
curl -i \
-H "Authorization: Bearer authorization" \
-H "Content-Type: application/json" \
-H "x-fapi-interaction-id: 93bac548-d2de-4546-b106-880a5018460d" \
-H "x-fapi-auth-date: Sun, 10 Sep 2017 19:43:31 GMT" \
-H "x-fapi-customer-ip-address: 104.25.212.99" \
-d 'eyJhbGciOiJQUzI1NiIsImtpZCI6InRlc3QifQ.e30.BAX4_Q65CJ0lQ9JGG9RsptRej6tPoJtvJMMSzQqDiYCQQmoZ50EjZLJpT_Asfc_aQaAAHvNtkfkj29HZ_EcCq2r4g5FI26RJcbbH0Dn09n_6WsjxE6dosveVwC5UDigP8I8cZbihZgeM7RO2tKWIRgRgCyv_vK8rmGxDbkDKFGgOGq5EMpXZTg7f0tJ11ssS48Ij8GD0A5fA9-2PkJjdYms7RvMWn7lscUGw76BqPMGNgYfD5rTh7hIUqqC2xgPi1d9F5zrdjpRFCufAxw9I7Gqzk9dECBZEU_N-8H6KPYdkkvlUInMLVkvlF2lwvDMWwrvPrxcNOnDUUCseucTGsw' \
-X DELETE "/api/:provider_code/open-banking/v3.1.11/cbpii/funds-confirmation-consents/:consent_id"
Request
DELETE
/api/:provider_code/open-banking/v3.1.11/cbpii/funds-confirmation-consents/:consent_id
Headers
| Header | Type | Description |
|---|---|---|
Accept
|
string, optional | Media type that is acceptable for the response. Default value: application/json |
x-fapi-interaction-id
|
string, optional | An RFC4122 UID used as a correlation Id. |
Authorization
|
string, required | Standard HTTP Header; Allows Credentials to be provided to the Authorisation / Resource Server depending on the type of resource being requested. For OAuth 2.0 / OIDC, this comprises of either the Basic / Bearer Authentication Schemes. Can raise: HeaderMissing, HeaderInvalid, ResourceNotFound, Forbidden |
x-fapi-auth-date
|
string, optional | The time when the PSU last logged in with the TPP. Supplied as HTTP-date (RFC7231), e.g. Sun, 10 Sep 2017 19:43:31 GMT. |
x-fapi-customer-ip-address
|
string, optional | The PSU's IP address if the PSU is currently logged in with the TPP. Identifies user presence for the data fetch. |
Request parameters
Response headers
| Header | Type | Description |
|---|---|---|
Content-Type
|
string, required | The media type of the body of the request. |
x-fapi-interaction-id
|
string, required | An RFC4122 UID used as a correlation Id. If provided, the ASPSP must "play back" this value in the x-fapi-interaction-id response header. |
Retry-After
|
integer, optional | Amount of time in seconds after which Salt Edge PSD2 Compliance Solution resends the previously failed request. |
Response
Upon successful request, 200 status code will be returned. See ‘Related Errors’ table for other possibilities.
Related Errors
| Class | Code | Description |
|---|---|---|
| ResourceNotFound | 400 | Specified resource doesn't exist. |
| FieldInvalid | 400 | An invalid value is supplied in the field. More details in error_message. |
| ResourceInvalidConsentStatus | 400 | The action can't be performed with current status of consent. |
| HeaderMissing | 400 | A required HTTP header has not been provided. |
| HeaderInvalid | 400 | An invalid value is supplied in the HTTP header. |
| Unauthorized | 401 | Unauthorized access. |
| Forbidden | 403 | Action is forbidden. More details in error_message. |
Funds Confirmation
Create
If the TPP would like to confirm funds with the ASPSP, it should create a new funds-confirmation resource, and check the funds available flag in the response.
CURL
![]()
curl -i \
-H "Authorization: Bearer authorization" \
-H "Content-Type: application/json" \
-H "x-fapi-interaction-id: 93bac548-d2de-4546-b106-880a5018460d" \
-H "x-fapi-auth-date: Sun, 10 Sep 2017 19:43:31 GMT" \
-H "x-fapi-customer-ip-address: 104.25.212.99" \
-d 'eyJhbGciOiJQUzI1NiIsImtpZCI6InRlc3QifQ.eyJEYXRhIjp7IkNvbnNlbnRJZCI6IjEyMyIsIlJlZmVyZW5jZSI6IlNvbWUgcmVmIiwiSW5zdHJ1Y3RlZEFtb3VudCI6eyJBbW91bnQiOiIxMTUuMyIsIkN1cnJlbmN5IjoiR0JQIn19fQ.b7pNmZmOIFQZ3qogktTeR5SFtic6BIMTFfo1NIFoDmXFN8qngrgB0-3ffkJtdxkcNqRVULmx3JH4IJbln3dfOOe_D77XQRj7ZhynMZ1gWK_eYHfO1YEUrqMQbYQ320MxbDrlvbgyksg9DJJjAEawwMLfncy7J0R9cKlJ0_DaKF1qdtQWN21sKS7DzgsIb9a8e2k6_KBBXLFm0MArQ849zmnH8hBGjAPNpLfEuv2u7nTqLtwXlBmqpvODrWH3OP2pGS8x95BWBUH8-BDIkOlvWbNubn_FA3vomWf8ejYZ8gM8Yzy7dpnf6sZ0MbLLzLS4WIqAN8WGrx3Fj7UWLxnSiQ' \
-X POST "/api/:provider_code/open-banking/v3.1.11/cbpii/funds-confirmations"
Example of request
![]()
{"Data":{"ConsentId":"123","Reference":"Some ref","InstructedAmount":{"Amount":"115.3","Currency":"GBP"}}}
Example of response
![]()
{"Data":{"FundsConfirmationId":"1321","ConsentId":"22123","CreationDateTime":"2017-06-05T15:15:13+00:00","FundsAvailable":true,"Reference":"Some ref","InstructedAmount":{"Amount":"115.3","Currency":"GBP"}},"Links":{"Self":"/open-banking/v3.1/cbpii/funds-confirmations/1321"},"Meta":{}}
Request
POST
/api/:provider_code/open-banking/v3.1.11/cbpii/funds-confirmations
Headers
| Header | Type | Description |
|---|---|---|
Accept
|
string, optional | Media type that is acceptable for the response. Default value: application/json |
x-fapi-interaction-id
|
string, optional | An RFC4122 UID used as a correlation Id. |
Content-Type
|
string, optional | The media type of the body of the request. Default value: application/json |
Authorization
|
string, required | Standard HTTP Header; Allows Credentials to be provided to the Authorisation / Resource Server depending on the type of resource being requested. For OAuth 2.0 / OIDC, this comprises of either the Basic / Bearer Authentication Schemes. Can raise: HeaderMissing, HeaderInvalid, ResourceNotFound, Forbidden |
Idempotency-Key
|
string, optional | Unique uuid used to recognize subsequent retries of the same request valid for 24 hours. Allowed length: max: 40 characters |
x-fapi-auth-date
|
string, optional | The time when the PSU last logged in with the TPP. Supplied as HTTP-date (RFC7231), e.g. Sun, 10 Sep 2017 19:43:31 GMT. |
x-fapi-customer-ip-address
|
string, optional | The PSU's IP address if the PSU is currently logged in with the TPP. Identifies user presence for the data fetch. |
Request parameters
Response headers
| Header | Type | Description |
|---|---|---|
Content-Type
|
string, required | The media type of the body of the request. |
x-fapi-interaction-id
|
string, required | An RFC4122 UID used as a correlation Id. If provided, the ASPSP must "play back" this value in the x-fapi-interaction-id response header. |
Retry-After
|
integer, optional | Amount of time in seconds after which Salt Edge PSD2 Compliance Solution resends the previously failed request. |
Response
Upon successful request, 200 status code will be returned. See ‘Related Errors’ table for other possibilities.
Related Errors
| Class | Code | Description |
|---|---|---|
| ResourceNotFound | 400 | Specified resource doesn't exist. |
| FieldInvalid | 400 | An invalid value is supplied in the field. More details in error_message. |
| RequestFormatInvalid | 400 | Request format is wrong. Details are stored in error_message
|
| UnsupportedCurrency | 400 | The currency is not supported. |
| HeaderMissing | 400 | A required HTTP header has not been provided. |
| HeaderInvalid | 400 | An invalid value is supplied in the HTTP header. |
| Forbidden | 403 | Action is forbidden. More details in error_message. |