Other pages in this section Permissions and Data Clusters for AIS journeys Account Information Consent Refreshing AISP access Consent Dashboard & Revocation AIS Access Dashboard & Revocation Access Status notifications by ASPSPs AIS Access for PSUs from Corporate Entities
This content is best viewed on a desktop browser. 1 CX Considerations 1If the customer-facing entity is acting on behalf of an AISP as its agent, the PSU should be made aware that the agent is acting on behalf of the AISP. This can be presented to the PSU by displaying both the agent’s name and the regulated AISP name in the list of providers, where applicable. “Agent” means a person or entity who acts on behalf of an authorised payment institution or a small payment institution in the provision of payment services including account information services. 2 CX Considerations 2ASPSPs should offer a functionality ( e.g. search, sort, filter) to enable a PSU to search for the relevant access. This will be of particular benefit as the number of consents given by a PSU to TPPs increases. 3 CEG Checklist Requirements 3ASPSPs must describe the data being accessed using the structure and language recommended by OBIE following customer research (see Data Cluster Structure & Language below). ASPSPs should present the data at a Data Cluster level and allow the PSU to expand the level of detail to show each Data Permission. The Access Dashboard should also describe: The status of the access e.g. Active/Inactive. When the AISP’s access to the account(s) will expire. The date the authorisation was granted. And may include date of last access The access dashboard must allow a PSU to view or cancel the access they have given consent to. These 2 functions should be given equal prominence when offered to the PSU. 4 CX Considerations 4ASPSPs should make the status of TPP access clear by the use of emboldened words. The ASPSP should also make it clear, which party provided the AISP access, in the case of joint/ multiple account holders. 5 CEG Checklist Requirements 5ASPSPs must advise PSUs that they should contact the associated AISP to inform them of the cancellation of access and/or understand the consequences of doing so. 6 CEG Checklist Requirements 5ASPSPs must advise PSUs that they should contact the associated AISP to inform them of the cancellation of access and/or understand the consequences of doing so. Select to scroll left Select to scroll right
CEG Checklist Requirements & CX Considerations 1 If the customer-facing entity is acting on behalf of an AISP as its agent, the PSU should be made aware that the agent is acting on behalf of the AISP. This can be presented to the PSU by displaying both the agent’s name and the regulated AISP name in the list of providers, where applicable. “Agent” means a person or entity who acts on behalf of an authorised payment institution or a small payment institution in the provision of payment services including account information services. 2 ASPSPs should offer a functionality ( e.g. search, sort, filter) to enable a PSU to search for the relevant access. This will be of particular benefit as the number of consents given by a PSU to TPPs increases. 3 ASPSPs must describe the data being accessed using the structure and language recommended by OBIE following customer research (see Data Cluster Structure & Language below). ASPSPs should present the data at a Data Cluster level and allow the PSU to expand the level of detail to show each Data Permission. The Access Dashboard should also describe: The status of the access e.g. Active/Inactive. When the AISP’s access to the account(s) will expire. The date the authorisation was granted. And may include date of last access. 13a 10 4 ASPSPs should make the status of TPP access clear by the use of emboldened words. The ASPSP should also make it clear, which party provided the AISP access, in the case of joint/ multiple account holders. 5 The access dashboard must allow a PSU to view or cancel the access they have given consent to. These functions “cancel access” and “back” should be given equal prominence when offered to the PSU. ASPSPs must advise PSUs that they should contact the associated AISP to inform them of the cancellation of access and/or understand the consequences of doing so. 10c
Consent Dashboard & Revocation Previous Related articles Please select API specifications Consent Revocation Changes to an Intent's Authorized State Access Status notifications by ASPSPs Next