Skip to main content
POST
/
payment-consents
/
{ConsentId}
/
file
Error
A valid request URL is required to generate request examples
{
  "iss": "c50f0152-49bb-4dc4-b866-b625271c4e78",
  "exp": 3349494246,
  "nbf": 1675765189,
  "aud": [
    "e63df191-5fff-4e9c-bba2-b273c94e87f0"
  ],
  "iat": 1675765189,
  "message": {
    "Errors": [
      {
        "Code": "GenericError",
        "Message": {
          "en": "A mandatory field is missing."
        }
      }
    ]
  }
}

Authorizations

​
Authorization
string
header
required

OAuth2 PAR flow, it is required when the User needs to perform SCA with the LFI when a TPP wants to access an LFI resource owned by the User. Please refer to OpenID FAPI Security Profile 1.0 -Part 2 Advanced - 5.2.2 point 14 - shall authenticate the confidential client using one of the following methods private_key_jwt and OpenID Connect Core 1.0 9. Client Authentication private_key_jwt

Headers

​
authorization
string
required

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

​
x-fapi-auth-date
string

The time when the User 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 2023 19:43:31 UTC

​
x-fapi-customer-ip-address
string

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

​
x-fapi-interaction-id
string

An RFC4122 UID used as a correlation id.

​
x-customer-user-agent
string

Indicates the user-agent that the User is using.

​
x-idempotency-key
string
required

Ensures the LFI processes the resource successfully only once per x-idempotency-key

The TPP must not change the request body while using the same x-idempotency-key, changes to the request body will not result any action on the end resource.

The OFP will treat a request as idempotent if it had received the first request with the same x-idempotency-key from the same TPP in the preceding 24 hours.

Maximum string length: 40

Path Parameters

​
ConsentId
string
required

Unique identification as assigned by the LFI to uniquely identify the Consent resource

Body

*/*

Request Body

Accepts any content type.

Response

200 OK No Content