/stet/psd2/v1/consents

PUT - consentsPut

Abstract

Forwarding the PSU consent (AISP)

Description

Description

• the AISP captures the consent of the PSU
• then it forwards this consent to the ASPSP

Prerequisites

• The TPP has been registered by the Registration Authority for the AISP role.
• The TPP and the PSU have a contract that has been enrolled by the ASPSP
• At this step, the ASPSP has delivered an OAUTH2 "Authorization Code" or "Resource Owner Password" access token to the TPP (cf. § 3.4.2).
• The TPP and the ASPSP have successfully processed a mutual check and authentication
• The TPP has presented its OAUTH2 "Authorization Code" or "Resource Owner Password" access token which allows the ASPSP to identify the relevant PSU and retrieve the linked PSU context (cf. § 3.4.2) if any.
• The ASPSP takes into account the access token that establishes the link between the PSU and the AISP.

Business Flow

Scopes

• extended_transaction_history
• aisp
• piisp

Parameters

{
    "balances (array)": "List of accessible accounts for one given functionality",
    "transactions (array)": "List of accessible accounts for one given functionality",
    "trustedBeneficiaries (boolean)": "Indicator that access to the trusted beneficiaries list was granted or not to the AISP by the PSU\n- true: the access was granted\n- false: the access was not granted\n",
    "psuIdentity (boolean)": "Indicator that access to the PSU identity, first name and last name, was granted or not to the AISP by the PSU\n- true: the access was granted\n- false: the access was not granted\n"
}

{
    "balances": "",
    "transactions": "",
    "trustedBeneficiaries": "",
    "psuIdentity": ""
}

Return codes

Input

application/json

Output

application/hal+json; charset=utf-8

application/json; charset=utf-8

Available authentification

OAuth 2.0