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.hHVq9RBI6sdSeUdItuncyVMK4vknA5I42F06BXWvWtjkZ2U6qYnpNF-8c3VHMPgDwFON99cp00qnNalA6-6yd3eTGAw3JvrpYSD5K4zEUgenVxz7Bv1QEHuXZXqdFQFFFHl6E9R8U7q0qoJmkhtMensFyEirFVpaTkBmoQ4NwatAiM14NBhLW79KIU_PDcDBjwJ_9E6EPSf0QRRlotBr3DdQEDhHgrDVt1ME0mfU5gmAjVe10D8EHk9x_N80RqG2oDtYMt7B0zbtSAITlvKnhExS2-VXL3S52c17BNDHf_EHJNn9qh__op1BAgFestaRWtBmdb2Aq55bv4ZzKrmTiw' \ -X POST "/api/:provider_code/open-banking/v3.1.11/cbpii/funds-confirmation-consents"

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.hHVq9RBI6sdSeUdItuncyVMK4vknA5I42F06BXWvWtjkZ2U6qYnpNF-8c3VHMPgDwFON99cp00qnNalA6-6yd3eTGAw3JvrpYSD5K4zEUgenVxz7Bv1QEHuXZXqdFQFFFHl6E9R8U7q0qoJmkhtMensFyEirFVpaTkBmoQ4NwatAiM14NBhLW79KIU_PDcDBjwJ_9E6EPSf0QRRlotBr3DdQEDhHgrDVt1ME0mfU5gmAjVe10D8EHk9x_N80RqG2oDtYMt7B0zbtSAITlvKnhExS2-VXL3S52c17BNDHf_EHJNn9qh__op1BAgFestaRWtBmdb2Aq55bv4ZzKrmTiw' \ 
-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

provider_code (path)

string, required

Human readable Provider identifier. Can raise: ResourceNotFound

Data

object, required

Wrapper for the data.

ExpirationDateTime

datetime, optional

Specified date and time the funds confirmation authorisation will expire. If this is not populated, the authorisation will be open ended. Values in range between: 2026-10-14T23:37:01+00:00 and 2027-01-12T23:37:01Z Can raise: FieldInvalidDate

DebtorAccount

object, required

Unambiguous identification of the account of the debtor to which a confirmation of funds consent will be applied.

SchemeName

string, required

Name of the identification scheme, in a coded form as published in an external list. Allowed values: UK.OBIE.SortCodeAccountNumber, UK.OBIE.IBAN, UK.OBIE.BBAN Can raise: FieldInvalid

Identification

string, required

Identification assigned by an institution to identify an account. This identification is known by the account owner. Allowed length: max: 256 characters Can raise: FieldInvalid

Name

string, optional

The account name is the name or names of the account owner(s) represented at an account level, as displayed by the ASPSP's online channels. Allowed length: max: 350 characters Can raise: FieldInvalid

SecondaryIdentification

string, optional

This is secondary identification of the account, as assigned by the account servicing institution. Allowed length: max: 34 characters Can raise: FieldInvalid

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.NIRRrpxcbcRffzP8nZdnLmKtpGC0R9SvdjcJeBg-54e7BC_BNcGGMttU_NqP5_h31fC1ZkRmN-HR1qIo37wqnE6Uy1eSA4N3pPxEKsYZbpirplwH_OkSgzIWnFHygYkvLnao-uuUfOuVN-HxpCdN8FkgSOvpqFRyIe3QtH8wdqoEc-qeScXnTwYBvsqFWxZAs4m4xowvrtVh1CvPiZZ9M8XoGHee5Dy33DmmMHTt5XGJOqEgku84WveVBQFP7ClOgLINyAdqyvYmhH0fyYERKq_AXAlMaDKduy_w9VyQ7cAnzMHz8lWt6eIhPh63a9mppECxrBEMpo1i6bUhq6PXqQ' \ -X GET "/api/:provider_code/open-banking/v3.1.11/cbpii/funds-confirmation-consents/:consent_id"

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.NIRRrpxcbcRffzP8nZdnLmKtpGC0R9SvdjcJeBg-54e7BC_BNcGGMttU_NqP5_h31fC1ZkRmN-HR1qIo37wqnE6Uy1eSA4N3pPxEKsYZbpirplwH_OkSgzIWnFHygYkvLnao-uuUfOuVN-HxpCdN8FkgSOvpqFRyIe3QtH8wdqoEc-qeScXnTwYBvsqFWxZAs4m4xowvrtVh1CvPiZZ9M8XoGHee5Dy33DmmMHTt5XGJOqEgku84WveVBQFP7ClOgLINyAdqyvYmhH0fyYERKq_AXAlMaDKduy_w9VyQ7cAnzMHz8lWt6eIhPh63a9mppECxrBEMpo1i6bUhq6PXqQ' \ 
-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

provider_code (path)

string, required

Human readable Provider identifier. Can raise: ResourceNotFound

consent_id (path)

string, required

The consent identifier assigned to the created resource. Can raise: FieldInvalid, ResourceNotFound

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.kSJruqlOeRoo3pxOOoYxn9kHKP6j4hnbNgadeDdn8nPBgBRq4vlchbKoFxUyiCDi8qwFUF6ojBjpoYbBW5Mrh-F72qLWS6jQBtBb8mpSorYb7taQ4Z1I0SIEjuypMPaD1hLfQNaF9UtabmQ7lVW1uACunnwpV05xbiwuaW_JkHhH8TPBqJSec9D7BrtJTUIUQTHgMjGKiTn_CzAYvjKuEYHIn-OrE9JX7Io2wP-25_B3DprzbBToPEuyARQQ522N36gMtX_RjuBWMmVgh3xyr97RJ3iGVLrz0PM4WALrjw67bxm3zvhx1-8jPV0u3TQY7jfaDdUEpNPn8SgEgFBaxA' \ -X DELETE "/api/:provider_code/open-banking/v3.1.11/cbpii/funds-confirmation-consents/:consent_id"

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.kSJruqlOeRoo3pxOOoYxn9kHKP6j4hnbNgadeDdn8nPBgBRq4vlchbKoFxUyiCDi8qwFUF6ojBjpoYbBW5Mrh-F72qLWS6jQBtBb8mpSorYb7taQ4Z1I0SIEjuypMPaD1hLfQNaF9UtabmQ7lVW1uACunnwpV05xbiwuaW_JkHhH8TPBqJSec9D7BrtJTUIUQTHgMjGKiTn_CzAYvjKuEYHIn-OrE9JX7Io2wP-25_B3DprzbBToPEuyARQQ522N36gMtX_RjuBWMmVgh3xyr97RJ3iGVLrz0PM4WALrjw67bxm3zvhx1-8jPV0u3TQY7jfaDdUEpNPn8SgEgFBaxA' \ 
-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

provider_code (path)

string, required

Human readable Provider identifier. Can raise: ResourceNotFound

consent_id (path)

string, required

The consent identifier assigned to the created resource. Can raise: FieldInvalid, ResourceNotFound, Unauthorized, ResourceInvalidConsentStatus

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.Y7gyTaGxE2tWpoyXgXv6itY6jDumrHCubM6krxG50EWnT16ysMeHUeKkbnXvoP16HK-eqRrxhiUE2l9dfyTAdi6AWbLlv0NmZDk6BI7vMg26eXpNL1gS2iyB6r4skgcE3SJXnAaD2xO6PYdfjc7IBPK8YThafxmF5IJ0GgAuRSVNQruyPvUEc31gbT1dtEtw_-hYVYuT-Qu1adeQ3XZsNoR9k4uF_eFyG7WKjr_OlYEWYvnka6OJRv8YaUl9lIjuRYFOkKESyNWJWW0rcydpdAWpEIgk0oC_WxtjQsDHhFO_Su5wcRHa90ywh-0rqLa9L6crjf94t5dYx5nkPNduvg' \ -X POST "/api/:provider_code/open-banking/v3.1.11/cbpii/funds-confirmations"

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.Y7gyTaGxE2tWpoyXgXv6itY6jDumrHCubM6krxG50EWnT16ysMeHUeKkbnXvoP16HK-eqRrxhiUE2l9dfyTAdi6AWbLlv0NmZDk6BI7vMg26eXpNL1gS2iyB6r4skgcE3SJXnAaD2xO6PYdfjc7IBPK8YThafxmF5IJ0GgAuRSVNQruyPvUEc31gbT1dtEtw_-hYVYuT-Qu1adeQ3XZsNoR9k4uF_eFyG7WKjr_OlYEWYvnka6OJRv8YaUl9lIjuRYFOkKESyNWJWW0rcydpdAWpEIgk0oC_WxtjQsDHhFO_Su5wcRHa90ywh-0rqLa9L6crjf94t5dYx5nkPNduvg' \ 
-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

provider_code (path)

string, required

Human readable Provider identifier. Can raise: ResourceNotFound

Data

object, required

Wrapper for the data. Can raise: ResourceNotFound, Unauthorized, ResourceInvalidConsentStatus

ConsentId

string, required

Unique identification as assigned by the ASPSP to uniquely identify the funds confirmation consent resource. Can raise: FieldInvalid

Reference

string, required

Unique reference, as assigned by the TPP, to unambiguously refer to the request related to the payment transaction. Can raise: FieldInvalid

InstructedAmount

object, required

Amount of money to be confirmed as available funds in the debtor account. Contains an Amount and a Currency.

Amount

string, required

A number of monetary units specified in an active currency where the unit of currency is explicit and compliant with ISO 4217. Can raise: FieldInvalid, RequestFormatInvalid

Currency

string, required

A code allocated to a currency by a Maintenance Agency under an international identification scheme, as described in the latest edition of the international standard ISO 4217 "Codes for the representation of currencies and funds". Can raise: FieldInvalid, UnsupportedCurrency

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.
ServiceInvalid	400	Something went wrong on Provider(ASPSP) side.
Forbidden	403	Action is forbidden. More details in `error_message`.
UnprocessableEntity	422	The request was well-formed but the Provider(ASPSP) could not process it. More details in `error_message`.