Create a Funds Confirmation Consent
Enables a CBPII to ask an ASPSP to create a new funds-confirmation-consent resource, by sending a copy of the consent to the ASPSP.
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://tools.ietf.org/html/rfc6750
Indicates the user-agent that the PSU is using.
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
Response
Funds Confirmation Consent Created
Example response
{
"Data": {
"StatusReason": [
{
"StatusReasonCode": "ERIN"
}
]
}
}