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.fIotCGWjA3Ur9L_UbNULHJaDMR2qYZl4mo6BAocyWTrPlQQY0n1Jptg3DIxAxuqIApEx-KjRZ5rvZEvScmVoNrKHOCjPXG3c361OFbg3kOqg7p7w1Z7Ytm9mlbJiAnZw-fS0Boj5sW6BS-r74V83s1S_ne0r-LrKX1nooBTDWaDDb49iO5bYv8J5f7o05z74nV0s-ywBwmovXdVZCJVO_FERXTGJ-8YLl-POin68y6IFfgMOTcrBozJ5YyPRzzcrJy8dliwuAMcjFu3HXLrgUXkbR__OAFksz-2HEHVTBLu6GDROIUHJoefBpZTaQMVyCA7_8NgJMHq69W_k3Y29iw' \
-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.dWaiod8Kqd5BPpbvbmbSmgtzh38MfY80FnTbd1pNP35V_Fdbt-lzp0xNU3GZOVumRwulJTw-keZLgrfZKGFuMurN_9g1Dqmy7rNMpHAR2BFe_r77LkgtqtorXBI55wxLdpYo2_Wfkd8Pw5kLeGj-sJMS5HUyjoMvTdWy56qDMItC_2UcnZ-EmT7voPl2ZGHv-otpkbRgAUmKRxu-1J7pPEWina7eJraVIbb68I2SjwunqF_lRgeQbqer57klg5YbJzSbsO8W5II693EGOwlFkUPx-H96OHKJ90o5h7YfGjiysSUBvJRDnWQOPJPZEof6nh3954V6lZqRYfINJEYvDw' \
-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.FS0Ltm8F0IzgUb-LfCetbihTFu3aXwcCxJ5y2UV3NxOo_hsJMuNYSFQlv30PQrNhnElpT-GuOKCMBWow2W8v3gnYqxXTiizIsSZ-d43_wzkJt08lKH2CrbqiEJY7Htx60AYwS3ItaZqT7QgUqcnlAGhVK1uhjX_CLl4D3mBEcH4FsrC3KmPlcW31xbIGu09huVRmNO6EN0RKq3o1J_SrBrTudWtLn5BzjmLBF-LJrtlgSw8H_DV2ai4q468n_GJqRulD_HrlHHpYfJkBmyCknY5UM_ZJsbLWEdhu8GLeuLp_s8-UJAKVgPZpZRSCAEx1iC6XCjR-pfAp8aoXKtM2cw' \
-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.gx2cd7c58s3rAKDfkm-VSRwGh5tw1K4Dxpp5Aak19bYx4wwBi-Wk10q_EHknDamjd6s7NIKfh0FhMwz4WGK_h5lA5k-hG4iCfbx1DIizjpxBec-VaLvfbMhCZAMd-VXV9MWRe-aUW6aZFEqGPYMYaVSW9DSW1Yoo03YHoARaYhiFyPrcJaPSPmaeIyTPsU9vTIzId80j8yU84iobvSv3E3r7-bA0UJwbnGv9uAUSN09BlzqSMMZULmko0W3PW-8d_HNg5FeXHcYp2WnEljps35E5FhVj0adSKnQNlHUXuirOdHYPZ_VBu8a81wV5myaYgSjSicQ9FbPXUpfS6vz7kA' \
-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. |