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 1AISPs should ask the PSU to identify their ASPSP before requesting consent so that the consent request can be constructed in line with the ASPSP’s data capabilities (which the ASPSP must make available to all TPPs). ASPSP Implementation guides, which are located on the Open Banking Developer Zone will have information about the ASPSP’s data capabilities. 2 CEG Checklist Requirements 2AISPs must provide PSUs sufficient information to enable PSUs to make an informed decision, for example, detail the purpose for which the data will be used (including whether any other parties will have access to the information) the period over which it has been requested and when the consent for the account information will expire (consent could be on-going or one-off). If the customer-facing entity is acting on behalf of an AISP as its agent, the PSU must be made aware that the agent is acting on behalf of the AISP. 3 CEG Checklist Requirements 3The AISP must provide the PSU with a description of the data being requested using the structure and language recommended by OBIE following customer research (see Data Cluster Structure & Language below) and ensure that this request is specific to only the information required for the provision of their account information service to the PSU. The AISP must present the data at a Data Cluster level and allow the PSU to expand the level of detail to show each Data Permission. The AISP should only present those data clusters relevant for the product type in question. Where the request is for multiple product types then the detail shown in the data cluster should explain to the customer the product types to which it applies or state that it is shared across multiple product types. Once PSU has consented, the PSU will be directed to their ASPSP. Please refer section Effective use of redirection screens for relevant messaging. 4 CX Considerations 4If 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 as: Select and confirm account(s) to share information with , who is acting on behalf of 5 CEG Checklist Requirements 5If the ASPSP provides an option for the PSU to view the data they have consented to share with the AISP as supplementary information, this must be done using the structure and language recommended by OBIE following customer research (see Data Cluster Structure & Language below). Display of such information must not be provided to the PSU as a default. 6 CEG Checklist Requirements 6ASPSPs must not seek confirmation of the consent that has already been provided by the PSU to the AISP. Once the PSU has selected the account(s), refer to section Effective use of redirection screens for redirection messaging. 7 CEG Checklist Requirements 7The AISP should confirm the successful completion of the account information request to the PSU. Select to scroll left Select to scroll right
CEG Checklist Requirements & CX Considerations 1 AISPs should ask the PSU to identify their ASPSP before requesting consent so that the consent request can be constructed in line with the ASPSP’s data capabilities (which the ASPSP must make available to all TPPs). ASPSP Implementation guides, which are located on the Open Banking Developer Zone will have information about the ASPSP’s data capabilities. 2 AISPs must provide PSUs sufficient information to enable PSUs to make an informed decision, for example, detail the purpose for which the data will be used (including whether any other parties will have access to the information) the period over which it has been requested and when the consent for the account information will expire (consent could be on-going or one-off). If the customer-facing entity is acting on behalf of an AISP as its agent, the PSU must be made aware that the agent is acting on behalf of the AISP. 8 12 3 The AISP must provide the PSU with a description of the data being requested using the structure and language recommended by OBIE following customer research (see Data Cluster Structure & Language below) and ensure that this request is specific to only the information required for the provision of their account information service to the PSU. The AISP must present the data at a Data Cluster level and allow the PSU to expand the level of detail to show each Data Permission. The AISP should only present those data clusters relevant for the product type in question. Where the request is for multiple product types then the detail shown in the data cluster should explain to the customer the product types to which it applies or state that it is shared across multiple product types. Once PSU has consented, the PSU will be directed to their ASPSP. Please refer section Effective use of redirection screens for relevant messaging. 13b 4 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 as: Select and confirm account(s) to share information with <agent>, who is acting on behalf of <TPP> 5 If the ASPSP provides an option for the PSU to view the data they have consented to share with the AISP as supplementary information, this must be done using the structure and language recommended by OBIE following customer research (see Data Cluster Structure & Language below). Display of such information must not be provided to the PSU as a default. 13a 6 ASPSPs must not seek confirmation of the consent that has already been provided by the PSU to the AISP. Once the PSU has selected the account(s), refer to section Effective use of redirection screens for redirection messaging. 2 7 The AISP should confirm the successful completion of the account information request to the PSU. 18
Permissions and Data Clusters for AIS journeys Previous Related articles Please select API specifications Refreshing AISP access Next