OPopenbankinguk
File Payment Consents

Get a File Payment Consent's Uploaded File

Changed on

Enables a PISP to download a file that has been previously uploaded.

get/file-payment-consents/{ConsentId}/file

Request

  • Base URL
    /open-banking/v4.0/pisp (relative, and the document was published on a file host, not at the API’s origin)
  • URL
    /open-banking/v4.0/pisp/file-payment-consents/{ConsentId}/file
  • Auth
    OAuth 2
    Client credentials
    Token URL: https://authserver.example/token scopes: payments

Path parameters

ConsentIdstring required

ConsentId

Headers

x-fapi-auth-datestring

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

x-fapi-customer-ip-addressstring

The PSU's IP address if the PSU is currently logged in with the TPP.

x-fapi-interaction-idstring

An RFC4122 UID used as a correlation id.

Authorizationstring required

An Authorisation Token as per https://tools.ietf.org/html/rfc6750

x-customer-user-agentstring

Indicates the user-agent that the PSU is using.

x-client-idstring

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

Response

File Payment Consents Read

ASPSP will specify all available content types.

File required

Changes