Account Information Services

AIS Access for PSUs from Corporate Entities

This version is:

This is the latest version Published 3 months ago 28 Jun 2024

In this journey, the AISP presents to the PSU a description of the data that it requires in order to support its service proposition.

Other pages in this section

User Journey

Main content image

PSUs, with delegated user authority on behalf of corporates who are authorised to receive corporate account information via AISPs, will be able to provide consent to the AISPs using the standard AIS journey shown in section Account Information Consent.

In this journey, the AISP presents to the PSU a description of the data that it requires in order to support its service proposition.

PSU selects the ASPSP(s) where their payment account(s) is held. The PSU is then directed to the domain of its ASPSP for authentication and to select the account(s) they want to give access. Once the PSU has been authenticated, their ASPSP will be able to respond to the AISP’s request by providing an appropriate message to inform the corporate PSU that request to access via AISP is received but is subject to further authorisation. Please note that it is in the domain of the ASPSPs to determine how to do this in alignment with their own corporate journeys.

Wireframes

To demonstrate an app based redirection part of the journey we have used one variation of PIS journey (section Single Domestic Payments – a/c selection @ PISP) as an example, where the ASPSP receives all the details of the payment order from the PISP.

This redirection flow applies to other variations of PIS journeys covered in detail under section Payment Initiation Services (PIS).

This content is best viewed on a desktop browser.

2

CEG Checklist Requirements 2
The AISP must provide the PSU sufficient information to enable the PSU 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). AISPs must display the company’s trading name/brand name (i.e. the Client Name) to the PSU during the setup and revocation of consent. If the AISP is only trading with its registered company name then it must display that name to the PSU.

3

CEG Checklist Requirements 3
The AISP must provide the PSU with a description of the data being requested using the structure and language recommended by OBL following customer research (see Data Cluster Structure & Language below) and ensure 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 type 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 2.2.5 for relevant messaging.

6

CEG Checklist Requirements 6
The AISP must confirm to the PSU: The successful completion of the account information request The request for access has been received by their ASPSP but is subject to further internal authorisation.

CEG Checklist Requirements & CX Considerations
CEG Checklist Reference

AISP should ask 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

The AISP must provide the PSU sufficient information to enable the PSU 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).

AISPs must display the company’s trading name/brand name (i.e. the Client Name) to the PSU during the setup and revocation of consent. If the AISP is only trading with its registered company name then it must display that name to the PSU.

If the AISP is not the customer-facing entity and there is an Agent who is acting on behalf of the AISP, then the Agent must make the PSU aware that they are acting as an agent on behalf of the AISP and must also, display the AISP’s full trading name/brand name or registered company name whichever is the customer-facing brand of the AISP.

AISPs must also, populate the Agent company name in the ‘On behalf of’ field of the software statement, in order to inform the ASPSP about the agency relationship and allow the ASPSP to be able to display this information to the PSU. Only in instances where there is an Agent acting on behalf of the AISP, the ‘On Behalf of’ name must be displayed to the PSU. AISPs must not populate the ‘ On behalf of’ field with the details of their TSP.

The customer-facing entity must provide PSUs with sufficient information to enable them 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 ongoing or one-off).

For examples of what names should be displayed, please refer to AIS Consent Dashboard & Revocation Examples.

8 12

3

The AISP must provide the PSU with a description of the data being requested using the structure and language recommended by OBL following customer research (see Data Cluster Structure & Language below) and ensure 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 type 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 to section Effective use of redirection screens for relevant messaging.

13b

The AISP should make the PSU aware that every 90 days the PSU need to reconfirm their consent to the AISP in order to continue to use their service.

The AISP should also inform the PSU that they no longer are required to re-authenticate with their bank unless there are permitted circumstances.

ASPSPs must display the TPPs’ trading name/brand name (i.e. the Client Name in the software statement) to the PSU during authentication screens and on any Access Dashboards. They do not need to display the registered company name of the TPP even if it is different.

If there is an Agent acting on behalf of the TPP, ASPSPs must also display the Agent company name (as captured in the ‘On behalf of’ field of the software statement) to the PSU. (Please note that ASPSPs can show the Agency/On Behalf field only in cases where this information has been provided by AISPs).

For examples of what names should be displayed, please refer to AIS Access Dashboard & Revocation Examples.

6

The AISP must confirm to the PSU:

  • The successful completion of the account information request
  • The request for access has been received by their ASPSP but is subject to further internal authorisation.

13a

What the research says

 

Click for customer research