...
AISPs must provide user/customers with a facility to view and revoke on-going consents that they have given to that AISP. They may have consented to share data from several ASPSPs with a single AISP. This section describes how these consents should be displayed and how the customer journey to revoke them should be constructed.
...
1.1.1 Customer Experience Checklist and Customer Experience Considerations
...
This section describes the customer journey when a user/customer needs to re-authenticate AISP consent, so that the AISP can continue to provide the service previously consented to by authenticating again at their ASPSP. All other elements of the consent (data permissions required, purpose for which the data will be used, transaction history period and consent expiration date) remain unchanged. (It should be noted that the API specification allows the AISP to inform the ASPSP that the request is a re-authentication/refresh rather than a new request).
...
1.2.1 Customer Experience Checklist and Customer Experience Considerations
...
ASPSPs must provide user/customers with a facility to view and revoke on-going access that they have given to any AISP for each account held at that ASPSP. This section describes how AISP’s access should be displayed and how the customer journey to revoke them should be constructed.
...
2.1 Customer Experience Checklist and Customer Experience Considerations
...