Customer Experience Guidelines

Account Information Services

This version is:

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

Account Information Service Providers (AISPs) can access account information from online payment accounts held at Account Service Payment Service Providers (ASPSPs), in order to provide account information services to a Payment Service User (PSU).

Other pages in this section

The Open Banking Read/Write API specifications support Account Information Services (AIS). They enable an Account Information Service Provider (AISP) to access account information from online payment accounts held at Account Service Payment Service Providers (ASPSPs), in order to provide account information services to a Payment Service User (PSU), provided they have obtained the PSU’s explicit consent.

This section describes the core journeys that support the set-up and management of AIS. The key components are:

  • Account Information Consent – PSU giving consent to an AISP to request account information from their ASPSP
  • AIS Access for PSUs from Corporate Entities – PSU acting with delegated user authority on behalf of a corporate entity, may only be able to use AISP services if this is permitted within the parameters of that delegated user authority.
  • Permissions and Data clusters

Note: This section does not include guidance around scenarios when more than one TPP is involved in the delivery of a service – sometimes referred to as “Onward Provisioning”. This subject will be addressed as part of the on-going OBL evaluations of eIDAS and Consent/Access Dashboards.

AIS Core Journeys

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.

AIS Access for PSUs from Corporate Entities

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

Permissions & Data Clusters for AIS journeys

In the Open Banking API design, data elements are logically grouped together into 'permissions'. OBL customer research found that grouping permissions together and adding another layer of description aided the PSU’s understanding of the data they were being asked to consent to share.